Activity log for bug #649591

Date Who What changed Old value New value Message
2010-09-28 07:01:24 Scott Moser bug added bug
2010-09-28 07:01:24 Scott Moser attachment added console log with mountall --verbose --debug https://bugs.launchpad.net/bugs/649591/+attachment/1647417/+files/maverick-debug-mountall.log
2010-09-28 07:01:24 Scott Moser attachment added Dependencies.txt https://bugs.launchpad.net/bugs/649591/+attachment/1647418/+files/Dependencies.txt
2010-09-28 07:02:01 Scott Moser bug added subscriber Simon de Boer
2010-09-28 07:02:50 Scott Moser mountall (Ubuntu): importance Undecided Critical
2010-09-28 07:02:50 Scott Moser mountall (Ubuntu): status New Confirmed
2010-09-28 07:02:50 Scott Moser mountall (Ubuntu): milestone ubuntu-10.10
2010-09-28 07:03:19 Scott Moser nominated for series Ubuntu Maverick
2010-09-28 07:05:43 Jonathan Riddell bug task added mountall (Ubuntu Maverick)
2010-09-28 07:54:34 Colin Watson mountall (Ubuntu Maverick): assignee Colin Watson (cjwatson)
2010-09-28 08:34:33 Colin Watson summary mountall spins eating cpu when 'nobootwait' option exists in fstab mountall spins eating cpu when 'nobootwait' option exists in fstab followed by a comma
2010-09-28 08:34:50 Colin Watson nominated for series Ubuntu Lucid
2010-09-28 08:34:50 Colin Watson bug task added mountall (Ubuntu Lucid)
2010-09-28 08:36:06 Colin Watson mountall (Ubuntu Maverick): status Confirmed Fix Committed
2010-09-28 08:36:10 Colin Watson mountall (Ubuntu Lucid): importance Undecided High
2010-09-28 08:36:13 Colin Watson mountall (Ubuntu Lucid): status New Triaged
2010-09-28 08:36:16 Colin Watson mountall (Ubuntu Lucid): assignee Colin Watson (cjwatson)
2010-09-28 08:36:20 Colin Watson mountall (Ubuntu Lucid): milestone ubuntu-10.04.2
2010-09-28 08:36:28 Launchpad Janitor branch linked lp:ubuntu/mountall
2010-09-28 09:00:41 Launchpad Janitor mountall (Ubuntu Maverick): status Fix Committed Fix Released
2010-09-29 02:15:48 Eric Hammond bug added subscriber Eric Hammond
2010-09-30 06:54:45 Jonathan Weiss bug added subscriber Jonathan Weiss
2010-09-30 07:06:19 Thierry bug added subscriber Thierry
2010-09-30 07:35:32 Launchpad Janitor branch linked lp:~smoser/ubuntu/lucid/mountall/bug649591
2010-09-30 07:50:17 Scott Moser description Binary package hint: mountall As reported at [1], mountall is eating cpu cycles on reboot of both 10.04 (images 20100923 and later) and 10.10. I believe the issue is related to changes made under bug 634102. Here is what happens: - The images are created with an fstab like: | proc /proc proc nodev,noexec,nosuid 0 0 | LABEL=uec-rootfs / ext4 defaults 0 0 - On first boot, cloud-init writes additional entries like: | /dev/sda2 /mnt auto defaults,nobootwait,comment=cloudconfig 0 2 | /dev/sda3 none swap sw,comment=cloudconfig 0 0 - On reboot, mountall will be eating CPU. and /mnt will *not* be mounted. - removing the 'nobootwait' flag, and rebooting will result in system functioning properly I've modified /etc/init/mountall and added '--debug' and '--verbose', and rebooted and collected the console log. I believe the issue only presents itself when the device exists at boot and the 'nobootwait' flag is present. I can boot 2 different instance types, m1.small : has /dev/sda2 and /dev/sda3 t1.micro : does not have /dev/sda2 or /dev/sda3 mountall will spin in m1.small, but not in t1.micro. I'm attaching the output of debug boot on m1.small (where /dev/sda2 does exist and mountall spins). -- [1] http://groups.google.com/group/ec2ubuntu/browse_thread/thread/d415746dff066f06 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: mountall 2.17 ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Tue Sep 28 06:45:14 2010 Ec2AMI: ami-307d8859 Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-maverick-daily-i386-server-20100927.manifest.xml Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mountall Binary package hint: mountall As reported at [1], mountall is eating cpu cycles on reboot of both 10.04 (images 20100923 and later) and 10.10. I believe the issue is related to changes made under bug 634102. Here is what happens: - The images are created with an fstab like:  | proc /proc proc nodev,noexec,nosuid 0 0  | LABEL=uec-rootfs / ext4 defaults 0 0 - On first boot, cloud-init writes additional entries like:  | /dev/sda2 /mnt auto defaults,nobootwait,comment=cloudconfig 0 2  | /dev/sda3 none swap sw,comment=cloudconfig 0 0 - On reboot, mountall will be eating CPU. and /mnt will *not* be mounted. - removing the 'nobootwait' flag, and rebooting will result in system functioning properly I've modified /etc/init/mountall and added '--debug' and '--verbose', and rebooted and collected the console log. I believe the issue only presents itself when the device exists at boot and the 'nobootwait' flag is present. I can boot 2 different instance types,  m1.small : has /dev/sda2 and /dev/sda3  t1.micro : does not have /dev/sda2 or /dev/sda3 mountall will spin in m1.small, but not in t1.micro. I'm attaching the output of debug boot on m1.small (where /dev/sda2 does exist and mountall spins). -- [1] http://groups.google.com/group/ec2ubuntu/browse_thread/thread/d415746dff066f06 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: mountall 2.17 ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Tue Sep 28 06:45:14 2010 Ec2AMI: ami-307d8859 Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-maverick-daily-i386-server-20100927.manifest.xml Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ProcEnviron:  LANG=en_US.UTF-8  SHELL=/bin/bash SourcePackage: mountall ==== SRU Information ==== - Impact: On EC2 or UEC, due to how cloud-init writes fstab entries, on first reboot mountall will eat all CPU cycles. On other systems, a user who updates /e c/fstab seemingly correct will have mountall spin the first time it runs. - How it was addressed: Logic error in cut_options routine in mountall was fixe . The code segment was easily removed and tested against different strings to verify no regressions. - Patch: A branch has been linked with the same patch as used in maverick. lp:~smoser/ubuntu/lucid/mountall/bug649591 - How to reproduce: Edit an existing entry in /etc/fstab for which there is an existing device. Change the options field to contain 'nobootwait,' in front of what was previously there. Reboot. You will now see mountall consuming resources. - Regression: The most likely regression would be either failure of mountall to mount a device or segfault in mountall. That said, the patch was tested well, and Collin had a strong understanding of the cause. ==== End SRU Information ====
2010-09-30 07:51:37 Scott Moser bug added subscriber Ubuntu Stable Release Updates Team
2010-09-30 07:52:53 Scott Moser bug added subscriber Ubuntu Sponsors Team
2010-09-30 07:59:13 Tom Ellis bug added subscriber Tom Ellis
2010-09-30 11:44:22 Colin Watson description Binary package hint: mountall As reported at [1], mountall is eating cpu cycles on reboot of both 10.04 (images 20100923 and later) and 10.10. I believe the issue is related to changes made under bug 634102. Here is what happens: - The images are created with an fstab like:  | proc /proc proc nodev,noexec,nosuid 0 0  | LABEL=uec-rootfs / ext4 defaults 0 0 - On first boot, cloud-init writes additional entries like:  | /dev/sda2 /mnt auto defaults,nobootwait,comment=cloudconfig 0 2  | /dev/sda3 none swap sw,comment=cloudconfig 0 0 - On reboot, mountall will be eating CPU. and /mnt will *not* be mounted. - removing the 'nobootwait' flag, and rebooting will result in system functioning properly I've modified /etc/init/mountall and added '--debug' and '--verbose', and rebooted and collected the console log. I believe the issue only presents itself when the device exists at boot and the 'nobootwait' flag is present. I can boot 2 different instance types,  m1.small : has /dev/sda2 and /dev/sda3  t1.micro : does not have /dev/sda2 or /dev/sda3 mountall will spin in m1.small, but not in t1.micro. I'm attaching the output of debug boot on m1.small (where /dev/sda2 does exist and mountall spins). -- [1] http://groups.google.com/group/ec2ubuntu/browse_thread/thread/d415746dff066f06 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: mountall 2.17 ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Tue Sep 28 06:45:14 2010 Ec2AMI: ami-307d8859 Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-maverick-daily-i386-server-20100927.manifest.xml Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ProcEnviron:  LANG=en_US.UTF-8  SHELL=/bin/bash SourcePackage: mountall ==== SRU Information ==== - Impact: On EC2 or UEC, due to how cloud-init writes fstab entries, on first reboot mountall will eat all CPU cycles. On other systems, a user who updates /e c/fstab seemingly correct will have mountall spin the first time it runs. - How it was addressed: Logic error in cut_options routine in mountall was fixe . The code segment was easily removed and tested against different strings to verify no regressions. - Patch: A branch has been linked with the same patch as used in maverick. lp:~smoser/ubuntu/lucid/mountall/bug649591 - How to reproduce: Edit an existing entry in /etc/fstab for which there is an existing device. Change the options field to contain 'nobootwait,' in front of what was previously there. Reboot. You will now see mountall consuming resources. - Regression: The most likely regression would be either failure of mountall to mount a device or segfault in mountall. That said, the patch was tested well, and Collin had a strong understanding of the cause. ==== End SRU Information ==== Binary package hint: mountall As reported at [1], mountall is eating cpu cycles on reboot of both 10.04 (images 20100923 and later) and 10.10. I believe the issue is related to changes made under bug 634102. Here is what happens: - The images are created with an fstab like:  | proc /proc proc nodev,noexec,nosuid 0 0  | LABEL=uec-rootfs / ext4 defaults 0 0 - On first boot, cloud-init writes additional entries like:  | /dev/sda2 /mnt auto defaults,nobootwait,comment=cloudconfig 0 2  | /dev/sda3 none swap sw,comment=cloudconfig 0 0 - On reboot, mountall will be eating CPU. and /mnt will *not* be mounted. - removing the 'nobootwait' flag, and rebooting will result in system functioning properly I've modified /etc/init/mountall and added '--debug' and '--verbose', and rebooted and collected the console log. I believe the issue only presents itself when the device exists at boot and the 'nobootwait' flag is present. I can boot 2 different instance types,  m1.small : has /dev/sda2 and /dev/sda3  t1.micro : does not have /dev/sda2 or /dev/sda3 mountall will spin in m1.small, but not in t1.micro. I'm attaching the output of debug boot on m1.small (where /dev/sda2 does exist and mountall spins). -- [1] http://groups.google.com/group/ec2ubuntu/browse_thread/thread/d415746dff066f06 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: mountall 2.17 ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Tue Sep 28 06:45:14 2010 Ec2AMI: ami-307d8859 Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-maverick-daily-i386-server-20100927.manifest.xml Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ProcEnviron:  LANG=en_US.UTF-8  SHELL=/bin/bash SourcePackage: mountall ==== SRU Information ==== - Impact: On EC2 or UEC, due to how cloud-init writes fstab entries, on first reboot mountall will eat all CPU cycles. On other systems, a user who updates /e c/fstab seemingly correct will have mountall spin the first time it runs. - How it was addressed: Logic error in cut_options routine in mountall was fixe . The code segment was easily removed and tested against different strings to verify no regressions. - Patch: A branch has been linked with the same patch as used in maverick.   lp:~smoser/ubuntu/lucid/mountall/bug649591 - How to reproduce:   Edit an existing entry in /etc/fstab for which there is an existing device. Change the options field to contain 'nobootwait,' in front of what was previously there. Reboot. You will now see mountall consuming resources. - Regression: The most likely regression would be either failure of mountall to mount a device or segfault in mountall. That said, the patch was tested well, and Colin had a strong understanding of the cause. ==== End SRU Information ====
2010-09-30 15:09:26 GavinC bug added subscriber GavinC
2010-10-06 17:06:24 Dustin Kirkland  mountall (Ubuntu Lucid): assignee Colin Watson (cjwatson) Dustin Kirkland (kirkland)
2010-10-06 17:06:28 Dustin Kirkland  mountall (Ubuntu Lucid): status Triaged In Progress
2010-10-06 17:11:12 Dustin Kirkland  mountall (Ubuntu Lucid): status In Progress Fix Committed
2010-10-06 21:52:51 GavinC removed subscriber GavinC
2010-10-07 10:00:43 Martin Pitt bug added subscriber SRU Verification
2010-10-07 10:00:49 Martin Pitt tags apport-bug ec2-images i386 maverick apport-bug ec2-images i386 maverick verification-needed
2010-10-07 22:39:25 Launchpad Janitor branch linked lp:ubuntu/lucid-proposed/mountall
2010-10-13 19:21:50 Scott Moser tags apport-bug ec2-images i386 maverick verification-needed apport-bug ec2-images i386 maverick verification-done
2010-10-14 06:36:31 Launchpad Janitor mountall (Ubuntu Lucid): status Fix Committed Fix Released
2010-10-14 20:46:22 Launchpad Janitor branch linked lp:ubuntu/lucid-updates/mountall
2010-10-18 23:22:23 Benjamin Drung removed subscriber Ubuntu Sponsors Team
2010-10-29 22:59:03 Jack Murgia bug added subscriber cloudcontrol
2011-07-19 18:19:56 Marjo F. Mercado bug added subscriber Marjo F. Mercado