Activity log for bug #1726818

Date Who What changed Old value New value Message
2017-10-24 11:23:57 Berislav Lopac bug added bug
2017-10-24 12:40:35 Berislav Lopac tags artful64 vagrant artful64 vagrant virtualbox
2017-10-24 14:27:16 Berislav Lopac attachment added cloud-init.log https://bugs.launchpad.net/cloud-images/+bug/1726818/+attachment/4991377/+files/cloud-init.log
2017-10-24 15:48:24 Scott Moser bug task added linux (Ubuntu)
2017-10-24 15:48:44 Scott Moser bug task added e2fsprogs (Ubuntu)
2017-10-24 16:00:08 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2017-10-24 16:00:10 Ubuntu Kernel Bot tags artful64 vagrant virtualbox artful artful64 vagrant virtualbox
2017-10-24 16:03:34 Berislav Lopac attachment added dmesg.log https://bugs.launchpad.net/cloud-images/+bug/1726818/+attachment/4991630/+files/dmesg.log
2017-10-24 17:56:46 Scott Moser bug added subscriber Scott Moser
2017-10-24 17:57:11 Scott Moser tags artful artful64 vagrant virtualbox apport-collected artful artful64 ec2-images vagrant virtualbox
2017-10-24 17:57:13 Scott Moser attachment added Dependencies.txt https://bugs.launchpad.net/bugs/1726818/+attachment/4992312/+files/Dependencies.txt
2017-10-24 17:57:15 Scott Moser attachment added ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1726818/+attachment/4992313/+files/ProcCpuinfoMinimal.txt
2017-10-24 17:57:39 Scott Moser linux (Ubuntu): status Incomplete Confirmed
2017-10-24 17:57:52 Scott Moser bug task deleted e2fsprogs (Ubuntu)
2017-11-15 22:22:36 Yasuo Honda bug added subscriber Yasuo Honda
2017-11-17 15:47:50 Scott Moser cloud-images: status New Confirmed
2017-11-20 11:37:27 Berislav Lopac attachment added Vagrantfile https://bugs.launchpad.net/cloud-images/+bug/1726818/+attachment/5011641/+files/Vagrantfile
2017-11-20 21:05:18 Colin Ian King linux (Ubuntu): importance Undecided High
2017-11-20 21:05:21 Colin Ian King linux (Ubuntu): status Confirmed In Progress
2017-11-20 21:05:23 Colin Ian King linux (Ubuntu): assignee Colin Ian King (colin-king)
2017-11-21 16:58:45 Colin Ian King 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. [SRU Justfication, Artful] [Impact] Booting the 4.13 Artful kernel with vagrant using VirtualBox trips the warning: [ 61.010337] VFS: brelse: Trying to free free buffer [ 61.114875] ------------[ cut here ]------------ [ 61.114886] WARNING: CPU: 0 PID: 683 at /build/linux-XO_uEE/linux-4.13.0/fs/buffer.c:1205 __brelse+0x21/0x30 and a failed resize of a partition. The root cause has been bisected down to the following commmit: commit c20cfc27a47307e811346f85959cf3cc07ae42f9 Author: Christoph Hellwig <hch@lst.de> Date: Wed Apr 5 19:21:07 2017 +0200 block: stop using blkdev_issue_write_same for zeroing [Fix] The Upstream commit directly fixes this issue: commit d5ce4c31d6df518dd8f63bbae20d7423c5018a6c Author: Ilya Dryomov <idryomov@gmail.com> Date: Mon Oct 16 15:59:10 2017 +0200 block: cope with WRITE ZEROES failing in blkdev_issue_zeroout() ..however we also require a backport of the following upstream commit to apply the above commit cleanly. commit 425a4dba7953e35ffd096771973add6d2f40d2ed Author: Ilya Dryomov <idryomov@gmail.com> Date: Mon Oct 16 15:59:09 2017 +0200 block: factor out __blkdev_issue_zero_pages() [Testscase] On Ubuntu Xenial: 1. sudo apt-get install virtualbox vagrant 2. edit /etc/group and add one's user name to the vboxusers group 3. log out log back 4. vagrant init ubuntu/artful64 5. vagrant up 6. vagrant ssh 7. dmesg | grep "VFS: brelse" without the fix one will see the VFS brelse warning message and the / partition will not have been resized. with a fixed system there is is no VFS vbrelse warning and / as been resized as expected. [Regresion potential] These patches touch the blk library so potentially it could break the block layer and corrupt data on disk. However these are upstream fixes that address the buggy commit c20cfc27a47307e811346f85959cf3cc07ae42f9 and are known to address the bug. ------------------------------- 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.
2017-11-29 23:30:17 Gary Stewart bug added subscriber Gary Stewart
2017-12-06 03:19:57 Maverick Woo bug added subscriber Maverick Woo
2017-12-20 05:15:09 Chen-Han Hsiao (Stanley) bug added subscriber Chen-Han Hsiao (Stanley)
2018-01-03 18:17:44 Jarl bug added subscriber Jarl
2018-01-18 16:20:19 Anastasios Andronidis bug added subscriber Anastasios Andronidis
2018-02-01 20:27:34 Khaled El Mously linux (Ubuntu): status In Progress Fix Committed
2018-02-16 15:30:54 Dan Watkins cloud-images: importance Undecided High
2018-02-23 09:03:55 lo bug added subscriber lo
2018-02-26 11:20:05 Alan Franzoni bug added subscriber Alan Franzoni
2018-03-14 11:50:50 Stefan Bader nominated for series Ubuntu Artful
2018-03-14 11:50:50 Stefan Bader bug task added linux (Ubuntu Artful)
2018-03-14 11:51:01 Stefan Bader linux (Ubuntu Artful): status New Fix Committed
2018-03-19 10:57:21 Stefan Bader tags apport-collected artful artful64 ec2-images vagrant virtualbox apport-collected artful artful64 ec2-images vagrant verification-needed-artful virtualbox
2018-03-19 15:04:38 Yasuo Honda tags apport-collected artful artful64 ec2-images vagrant verification-needed-artful virtualbox apport-collected artful artful64 ec2-images vagrant verification-done-artful virtualbox
2018-04-03 14:10:10 Launchpad Janitor linux (Ubuntu Artful): status Fix Committed Fix Released
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-0861
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-1000407
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-15129
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-16994
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-17448
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-17450
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-17741
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-17805
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-17806
2018-04-03 14:10:10 Launchpad Janitor cve linked 2017-17807
2018-04-03 14:10:10 Launchpad Janitor cve linked 2018-1000026
2018-04-03 14:10:10 Launchpad Janitor cve linked 2018-5332
2018-04-03 14:10:10 Launchpad Janitor cve linked 2018-5333
2018-04-03 14:10:10 Launchpad Janitor cve linked 2018-5344
2018-04-04 10:04:55 Colin Ian King linux (Ubuntu): status Fix Committed Fix Released
2018-10-01 20:21:38 Dan Watkins cloud-images: status Confirmed Fix Released
2019-07-24 20:20:44 Brad Figg tags apport-collected artful artful64 ec2-images vagrant verification-done-artful virtualbox apport-collected artful artful64 cscc ec2-images vagrant verification-done-artful virtualbox