Bug 2343

Summary:	sugarbay/huronriver/crownbay: abnormal filesystem-related messages in dmesg
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Tom Zanussi <tom.zanussi>
Component:	bsps-configuration	Assignee:	Yang Shi <yang.shi>
Status:	RESOLVED OBSOLETE	QA Contact:
Severity:	normal
Priority:	Medium	CC:	dvhart, yp.bsp.watcher, yp.watcher
Version:	unspecified
Target Milestone:	1.3
Hardware:	x86
OS:	Multiple
Whiteboard:	(P2)
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Tom Zanussi 2012-04-19 04:02:43 UTC

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.

Comment 1 Bruce Ashfield 2012-04-20 03:49:18 UTC

This is likely triggered by unionfs as well, see bug 2331.

Comment 2 Darren Hart 2012-06-14 20:24:56 UTC

With Union FS reverted, do we close this bug? There isn't anything to do here other than reimplement UnionFS with this in mind.

Comment 3 Darren Hart 2012-06-14 20:25:09 UTC

Comment 4 Yang Shi 2012-06-14 20:25:53 UTC

Yes, I agree.

Comment 5 Darren Hart 2012-06-14 20:28:18 UTC

Marking as obsolete as the unionfs causing the bug has been reverted.