Public bug reported:
blkid detects a JFS partition as FAT32. Thus fsck fails on this partition
unless the file system is specified explicitly or by device name (rather than
UUID) in fstab. This causes automatic fsck on startup failures resulting in
boot failures.
E.g.:
[EMAIL PROTECTED]:~$ sudo blkid -c /dev/null
/dev/sda1: UUID="d7e37603-b7ee-4994-add8-db53b71e6dd5" TYPE="jfs"
/dev/sdb1: SEC_TYPE="msdos" LABEL="DOS" UUID="E7D3-A415" TYPE="vfat"
/dev/sdb3: UUID="42d7432e-3d38-4ac4-ae08-706c8bf3e64f" TYPE="ext3"
/dev/sdb5: SEC_TYPE="msdos" UUID="5593-65BD" TYPE="vfat"
/dev/sdb6: TYPE="swap" UUID="629513d4-df93-48c5-be48-2e7314262747"
/dev/sdc1: SEC_TYPE="msdos" UUID="479E-4CF4" TYPE="vfat"
/dev/sdb5 is a JFS partition indeed. Strangely /dev/sda1 which is also a
JFS partition is detected correctly. However the difference is that
/dev/sda1 is formatted without -O option (case sensitive) whereas
/dev/sda5 is formatted with -O option (case insensitive)
** Affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
--
blkid library detects JFS partition as FAT32
https://bugs.launchpad.net/bugs/255255
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
