------- Additional Comments From nathans@xxxxxxx 2006-07-31 16:08 CST -------
| Production board based on iop80321 Xscale CPU (ARM).
Is this reproducible on other platforms? We've seen problems with
compilers on ARM in the past, not properly manipulating 64 bit
numbers... if this can't be reproduced anywhere else, odds are good
that this is another ARM platform/compiler bug.
------- Additional Comments From akulbe@xxxxxxxxx 2006-08-14 09:26 CST -------
Nathan, let me add my two cents.
I run Linux on the AMD64 platform. I see the same behavior as described in this
I am on kernel 18.104.22.168
I have experienced what amounts to a near complete data loss as a result of this
bug. All attempts at recovery have been unsuccessful so far. FS recovery using
xfs_repair results in errors.
Now before you ask, I'm not a novice. I had a RAID1 setup. Mirror is corrupted
too, obviously. I had backups as well. The point is, my love affair with XFS is
*OVER*. It is clear that she is not a partner that is safe to be with, she
carries and spreads disease.
I was attempting to copy stuff off onto another volume, which eventually
Filesystem "dm-14": XFS internal error xfs_da_do_buf(2) at line 2212 of file
fs/xfs/xfs_da_btree.c. Caller 0xc0159a0c <-- the hex value I saw was different,
as well as the previous "linux 2212". for me it was 2128
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.