2343 2012-04-19 04:02:43 +0000 sugarbay/huronriver/crownbay: abnormal filesystem-related messages in dmesg 2012-06-14 20:28:18 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-configuration unspecified x86 Multiple RESOLVED OBSOLETE (P2) Medium normal 1.3 1 tom.zanussi yang.shi dvhart yp.bsp.watcher yp.watcher --- --- --- oldest_to_newest 20699 0 tom.zanussi 2012-04-19 04:02:43 +0000 On a couple different machines, I've been noticing some abnormal filesystem-related messages after booting from a live image. On all of them, I see this message: mount: sending ioctl 5310 to a partition! And on huronriver and crownbay, but not sugarbay (same USB stick as on huronriver) I've seen messages like: EXT3-fs (sda3): error: unable to read superblock EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240) attempt to access beyond end of device sda3: rw=0, want=4, limit=2 EXT2-fs (sda3): error: unable to read superblock EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240) EXT3-fs (sda5): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda5): error: couldn't mount because of unsupported optional features (240) mount: sending ioctl 5310 to a partition! mount: sending ioctl 5310 to a partition! attempt to access beyond end of device sda3: rw=0, want=66, limit=2 isofs_fill_super: bread failed, dev=sda3, iso_blknum=16, block=32 attempt to access beyond end of device sda3: rw=0, want=4, limit=2 EXT3-fs (sda3): error: unable to read superblock attempt to access beyond end of device sda3: rw=0, want=4, limit=2 EXT2-fs (sda3): error: unable to read superblock EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240) EXT3-fs (sda5): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240) attempt to access beyond end of device sda3: rw=0, want=4, limit=2 MINIX-fs: unable to read superblock EXT2-fs (sda5): error: couldn't mount because of unsupported optional features (240) attempt to access beyond end of device sda3: rw=0, want=4, limit=2 EXT3-fs (sda3): error: unable to read superblock attempt to access beyond end of device sda3: rw=0, want=4, limit=2 EXT2-fs (sda3): error: unable to read superblock EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240) EXT3-fs (sda5): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda5): error: couldn't mount because of unsupported optional features (240) mount: sending ioctl 5310 to a partition! mount: sending ioctl 5310 to a partition! attempt to access beyond end of device These messages didn't exist with 1.1. Normally you get these kinds of messages with bad media, but they seem to be too consistent for that explanation (and the fact that the same media on different machines doesn't show this on one but does on the other). Not sure of the significance, the operation of the system seems normal otherwise, but it needs to be investigated. 20757 1 bruce.ashfield 2012-04-20 03:49:18 +0000 This is likely triggered by unionfs as well, see bug 2331. 22219 2 dvhart 2012-06-14 20:24:56 +0000 With Union FS reverted, do we close this bug? There isn't anything to do here other than reimplement UnionFS with this in mind. 22220 3 dvhart 2012-06-14 20:25:09 +0000 . 22221 4 yang.shi 2012-06-14 20:25:53 +0000 Yes, I agree. 22224 5 dvhart 2012-06-14 20:28:18 +0000 Marking as obsolete as the unionfs causing the bug has been reverted.