Public bug reported:
Hi,
I have had this bug since end of intrepid/beginning of jaunty I think. I have
two similar jaunty setups; one boots fine, the other keeps failing the fsck on
boot:
bee# fsck -C -R -a /boot
fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Device or resource busy while trying to open /dev/sda2
Filesystem mounted or opened exclusively by another program?
(actually what runs on boot is fsck -C -R -a -A which fails with the
same error message)
The "device or resource busy" is due to /boot being on /dev/md1 which is
made of /dev/sda2 and /dev/sdb2.
This behavior is racy; I ran blkid:
bee# blkid
/dev/mapper/bee--raid1-refuge: UUID="cfa891cf-6b4b-4c7d-90df-98f9be721cbe"
SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--raid1-home: UUID="2fd30976-f849-458a-94d7-c00e9fdcbe4d"
SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--raid1-ubuntu--root:
UUID="6ec6b99f-415b-45fc-8efe-c6a016984b5b" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--raid1-swap: TYPE="swap"
UUID="e8a8ba4e-a0cb-43c4-b160-363949e4600f"
/dev/sda1: UUID="db18614f-1cbd-9225-4561-bc10b69bf963" TYPE="mdraid"
/dev/sda2: UUID="b1a8d7aa-5aab-41ab-a326-e0350c018764" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sdb1: UUID="659550dd-fb28-4f7d-9904-9cdcb4fa228f" SEC_TYPE="ext2"
TYPE="ext3"
/dev/md0: UUID="659550dd-fb28-4f7d-9904-9cdcb4fa228f" SEC_TYPE="ext2"
TYPE="ext3"
/dev/mapper/bee--raid1-debian--root:
UUID="2d99500c-fa17-4587-a059-23b48aa7e08d" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--sata-var: UUID="9260b9f1-d6f4-48bd-80ce-97758cc4c1f7"
SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--sata-home: UUID="7950ce8f-615a-4392-bb7a-fda5baaeb93e"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: UUID="40a955ce-5f05-b4fc-7477-72897565b642" TYPE="mdraid"
/dev/sdb3: UUID="60b75582-1b75-c2bc-286c-ebc612c886d3" TYPE="mdraid"
/dev/sda3: UUID="60b75582-1b75-c2bc-286c-ebc612c886d3" TYPE="mdraid"
/dev/md2: UUID="gy0khl-tC2g-N50w-0Dyk-bwZP-DnpD-yQqSYn" TYPE="lvm2pv"
/dev/md1: UUID="b1a8d7aa-5aab-41ab-a326-e0350c018764" TYPE="ext3"
and now suddenly fsck knows that /boot is /dev/md1 and not /dev/sda2!
bee# fsck -C -R -A -a
fsck 1.41.3 (12-Oct-2008)
/dev/md1 is mounted. e2fsck: Cannot continue, aborting.
/dev/mapper/bee--raid1-home is mounted. e2fsck: Cannot continue, aborting.
/dev/mapper/bee--raid1-refuge is mounted. e2fsck: Cannot continue, aborting.
I think this is due to /etc/blkid.tab; a cache of device information.
Bye
** Affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Hi,
I have had this bug since end of intrepid/beginning of jaunty I think. I
have two similar jaunty setups; one boots fine, the other keeps failing the
fsck on boot:
bee# fsck -C -R -a /boot
fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Device or resource busy while trying to open /dev/sda2
Filesystem mounted or opened exclusively by another program?
(actually what runs on boot is fsck -C -R -a -A which fails with the
same error message)
The "device or resource busy" is due to /boot being on /dev/md1 which is
made of /dev/sda2 and /dev/sdb2.
This behavior is racy; I ran blkid:
bee# blkid
/dev/mapper/bee--raid1-refuge: UUID="cfa891cf-6b4b-4c7d-90df-98f9be721cbe"
SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--raid1-home: UUID="2fd30976-f849-458a-94d7-c00e9fdcbe4d"
SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--raid1-ubuntu--root:
UUID="6ec6b99f-415b-45fc-8efe-c6a016984b5b" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--raid1-swap: TYPE="swap"
UUID="e8a8ba4e-a0cb-43c4-b160-363949e4600f"
/dev/sda1: UUID="db18614f-1cbd-9225-4561-bc10b69bf963" TYPE="mdraid"
/dev/sda2: UUID="b1a8d7aa-5aab-41ab-a326-e0350c018764" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sdb1: UUID="659550dd-fb28-4f7d-9904-9cdcb4fa228f" SEC_TYPE="ext2"
TYPE="ext3"
/dev/md0: UUID="659550dd-fb28-4f7d-9904-9cdcb4fa228f" SEC_TYPE="ext2"
TYPE="ext3"
/dev/mapper/bee--raid1-debian--root:
UUID="2d99500c-fa17-4587-a059-23b48aa7e08d" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--sata-var: UUID="9260b9f1-d6f4-48bd-80ce-97758cc4c1f7"
SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/bee--sata-home: UUID="7950ce8f-615a-4392-bb7a-fda5baaeb93e"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: UUID="40a955ce-5f05-b4fc-7477-72897565b642" TYPE="mdraid"
/dev/sdb3: UUID="60b75582-1b75-c2bc-286c-ebc612c886d3" TYPE="mdraid"
/dev/sda3: UUID="60b75582-1b75-c2bc-286c-ebc612c886d3" TYPE="mdraid"
/dev/md2: UUID="gy0khl-tC2g-N50w-0Dyk-bwZP-DnpD-yQqSYn" TYPE="lvm2pv"
/dev/md1: UUID="b1a8d7aa-5aab-41ab-a326-e0350c018764" TYPE="ext3"
- and now suddenly fsck knows what /boot is /dev/md1 and not /dev/sda2!
+ and now suddenly fsck knows that /boot is /dev/md1 and not /dev/sda2!
bee# fsck -C -R -A -a
fsck 1.41.3 (12-Oct-2008)
/dev/md1 is mounted. e2fsck: Cannot continue, aborting.
/dev/mapper/bee--raid1-home is mounted. e2fsck: Cannot continue, aborting.
/dev/mapper/bee--raid1-refuge is mounted. e2fsck: Cannot continue, aborting.
I think this is due to /etc/blkid.tab; a cache of device information.
Bye
** Summary changed:
- Wrong type in blkid causes fsck on boot to fail
+ Wrong type in blkid cache causes fsck on boot to fail
--
Wrong type in blkid cache causes fsck on boot to fail
https://bugs.launchpad.net/bugs/316322
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
