** Description changed: I'm opening this against cloud-init, but I do not actually think that is valid. In an ec2 instance for test of alpha-1 images [1], we saw errors on boot like: - Loading, please wait... - [1342606.840604] udevd[81]: starting version 175 - Begin: Loading essential drivers ... done. - Begin: Running /scripts/init-premount ... done. - Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. - Begin: Running /scripts/local-premount ... done. - [1342607.148903] EXT4-fs (xvda1): mounted filesystem with ordered data mode. Opts: (null) - Begin: Running /scripts/local-bottom ... done. - done. - Begin: Running /scripts/init-bottom ... done. - lxcmount stop/pre-start, process 178 - fsck from util-linux 2.19.1 - fsck from util-linux 2.19.1 - fsck: fsck.swap: not found - fsck: Error 2 while executing fsck.swap for /dev/xvda3 - fsck.ext3: Device or resource busy while trying to open /dev/xvda2 - Filesystem mounted or opened exclusively by another program? - cloud-init start-local running: Wed, 30 Nov 2011 19:25:20 +0000. up 3.98 seconds - no instance data found in start-local + Loading, please wait... + [1342606.840604] udevd[81]: starting version 175 + Begin: Loading essential drivers ... done. + Begin: Running /scripts/init-premount ... done. + Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. + Begin: Running /scripts/local-premount ... done. + [1342607.148903] EXT4-fs (xvda1): mounted filesystem with ordered data mode. Opts: (null) + Begin: Running /scripts/local-bottom ... done. + done. + Begin: Running /scripts/init-bottom ... done. + lxcmount stop/pre-start, process 178 + fsck from util-linux 2.19.1 + fsck from util-linux 2.19.1 + fsck: fsck.swap: not found + fsck: Error 2 while executing fsck.swap for /dev/xvda3 + fsck.ext3: Device or resource busy while trying to open /dev/xvda2 + Filesystem mounted or opened exclusively by another program? + cloud-init start-local running: Wed, 30 Nov 2011 19:25:20 +0000. up 3.98 seconds + no instance data found in start-local The swap errors are due to bug 898365. The cloud-config given to the instance included: - mounts: - - [ ephemeral0, /opt , auto, "defaults,noexec" ] - - [ swap, null ] + mounts: + - [ ephemeral0, /opt , auto, "defaults,noexec" ] + - [ swap, null ] And given that bug, the /etc/fstab during this reboot probably had: - /dev/xvda2 /opt auto defaults,noexec,comment=cloudconfig 0 2 - /dev/xvda3 None auto defaults,nobootwait,comment=cloudconfig 0 2 + /dev/xvda2 /opt auto defaults,noexec,comment=cloudconfig 0 2 + /dev/xvda3 None auto defaults,nobootwait,comment=cloudconfig 0 2 The thing that confuses me, and the reason I do not think this is cloud- init's fault is that this happens prior to cloud-init start-local. So, yes, there is a broken fstab, but not for /dev/xvda2. The errors listed above are on first reboot after cloud-init wrote those fstab entries, and then issued 'mount -a' from a upstart job (cloud-config.conf) launched at: - start on (filesystem and started rsyslog) + start on (filesystem and started rsyslog) -- [1] https://jenkins.qa.ubuntu.com/job/precise-server-ec2/ARCH=i386,REGION=us-west-1,STORAGE=instance-store,TEST=cloud-config,label=ubuntu-server-ec2-testing/1/artifact/None/i386/m1.small/instance-store/i-835a3dc4/uec2-20111130-1920-5d6ee3bc489541-terminated.console.txt ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cloud-init 0.6.2-0ubuntu1 [modified: usr/share/pyshared/cloudinit/CloudConfig/cc_mounts.py] ProcVersionSignature: User Name 3.2.0-2.5-virtual 3.2.0-rc3 Uname: Linux 3.2.0-2-virtual i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Wed Nov 30 21:44:25 2011 Ec2AMI: ami-a7cc07ce Ec2AMIManifest: ubuntu-us-east-1/images-testing/ubuntu-precise-daily-i386-server-20111130.manifest.xml Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) + + + Related bugs: + * bug 928990: fsck / dirty filesystem on instance is death
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/898373 Title: fsck.ext3: Device or resource busy while trying to open /dev/xvda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/898373/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
