[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#579005: XFS internal error xfs_da_do_buf(2) at line 2085 of file fs/xfs/xfs_da_btree.c.

Jonathan Nieder wrote:

> Interesting.  So this might be a case of the kernel not coping well
> with previous filesystem corruption.

Some reading: [1]

>From similar symptoms at [2]:

| This indicates filesystem corruption, which may be caused by a hardware/media
| fault.
| I suggest you run xfs_repair and then xfs_db to dump any inodes that may have
| problems.
| Also check smartctl, dmesg etc for any hardware errors.
| This class of fault is typically very hard to track down, the corruption
| (whether caused by software or hardware) may have happened a week ago and
| its only now you have read that part of the filesystem again.

Apparently one cause of this in olden days was [3] (probably not
what's happening here, since that got fixed a while ago).  Another was
running with write cache enabled but without barriers which didn't
work over the device mapper.

In any case, I think reporting "XFS internal error" rather than
something more enlightening like "magic number is wrong - filesystem
is probably corrupt" is a bug in itself.  So it would be nice to
figure out what happened and at least fix this that much.

Hope that helps,

[1] http://oss.sgi.com/bugzilla/buglist.cgi?field0-0-0=short_desc&type0-0-0=substring&value0-0-0=xfs_da_do_buf&field0-0-1=longdesc&type0-0-1=substring&value0-0-1=xfs_da_do_buf
[2] http://oss.sgi.com/bugzilla/show_bug.cgi?id=736
[3] http://www.xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F

Reply to: