>From the fs/buffer.c:1205 __brelse+0x21/0x30 it is impossible to deduce what is broken. I'm trying to reproduce this using vagrant and VirtualBox. Can you inform me of the vagrant box you are using and the full set of instructions on how one can reproduce this. Some pertinent facts to help me reproduce this are:
1. What host system are you using? 2. What vagrant box are you using? (any URLs or copies of the .box file or would be handy) 3. Exactly what is the vagrant setup being used. I'm not totally familiar with using vagrant, so clear instructions so I can set up a reproducer to help me debug this further would be very helpful. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1726818 Title: vagrant artful64 box filesystem too small Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After building a new vagrant instance using the ubuntu/artful64 box (v20171023.1.0), the size of the filesystem seems to be much too small. Here's the output of `df -h` on the newly built instance: vagrant@ubuntu-artful:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 991M 0 991M 0% /dev tmpfs 200M 3.2M 197M 2% /run /dev/sda1 2.2G 2.1G 85M 97% / tmpfs 999M 0 999M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 999M 0 999M 0% /sys/fs/cgroup vagrant 210G 182G 28G 87% /vagrant tmpfs 200M 0 200M 0% /run/user/1000 For comparison, here is the same from the latest zesty64 box: ubuntu@ubuntu-zesty:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 992M 0 992M 0% /dev tmpfs 200M 3.2M 197M 2% /run /dev/sda1 9.7G 2.5G 7.3G 26% / tmpfs 999M 0 999M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 999M 0 999M 0% /sys/fs/cgroup vagrant 210G 183G 28G 88% /vagrant tmpfs 200M 0 200M 0% /run/user/1000 With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 97% of disk usage immediately after building, even though the disk size is 10G, as reported by the fdisk: vagrant@ubuntu-artful:~$ sudo fdisk -l Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x4ad77c39 Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 20971486 20969439 10G 83 Linux Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Almost any additional installation results in a "No space left on device" error. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
