http://bugzilla.kernel.org/show_bug.cgi?id=6957
------- Comment #10 from dgc@xxxxxxx 2007-10-04 14:39 -------
Following up from Nathan's original comments, I see that the original
report showed:
Filesystem "dm-4": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-4
Starting XFS recovery on filesystem: dm-4 (logdev: internal)
Ending XFS recovery on filesystem: dm-4 (logdev: internal)
Access to block zero: fs: <dm-4> inode: 131 start_block : 0 start_off : 0
blkcnt : 0 extent-state : 0
That barriers were disabled on block device you were using. This could lead
to the sort of problem that you re seeing.
Can this be reproduced on a filesystem that mounts with barriers (should
happen by default) and does not produce the "barriers disabled" warning
on mount?
Also, from comment #9, this is from an extent btree block full of
zeros, which again implies a log recovery problem which initially points
back to the above question about barriers....
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|