On Thu, Jul 01, 2010 at 10:25:03AM +0200, Michael Monnerie wrote:
> On Donnerstag, 1. Juli 2010 Dave Chinner wrote:
> > > From another Linux ("saturn"), I do an rsync via an rsync-module,
> > > and have already 4 Versions where the ".vhd" file of that Windows
> > > Backup is destroyed on "saturn". So the corruption happens when
> > > starting rsync @saturn, copying orion->saturn, both having XFS.
> > Are you running rsync locally on saturn (i.e. pulling data)? If so,
> > can you get an strace of the rsync of that file so we can see what
> > the order or operations being done on the file is. If you are
> > pushing data to saturn, does the problem go away if you pull it (and
> > vice versa)?
> Oh dear, I made a mistake. It's a push @orion, doing
> rsync -aPvHAXy / saturn::orionbackup/
> The problem is: I cannot 100% replicate it. I found the problem once,
> moved the dir with the broken file away and synced again. Again broken.
> Then I reported here. Meanwhile, Windows has done a new backup, that
> file doesn't seem to get broken. But with another fresh Windows backup,
> it came again. I don't know if it depends on the file, it happened 4
> times until now.
So it's the rsync daemon on saturn that is doing all the IO?
> I rsynced today 3 times, twice with the openSUSE kernel and once with
> 2.6.34, no problem. Sorry (or maybe "lucky me"?).
> > > 852c268f-cf1a-11de-b09b-806e6f6e6963.vhd* ??????????? ? ? ?
> > > ? ? 852c2690-cf1a-11de-b09b-806e6f6e6963.vhd
> > On the source machine, can you get a list of the xattrs on the
> > inode?
> How would I do that? "getfattr" on that file gives no return, does that
> mean it doesn't have anything to say? I never do that things, so there
> shouldn't be any attributes set.
> > > and on dmesg:
> > > [125903.343714] Filesystem "dm-0": corrupt inode 649642 ((a)extents
> > > = 5). Unmount and run xfs_repair. [125903.343735]
> > > ffff88011e34ca00: 49 4e 81 c0 02 02 00 00 00 00 03 e8 00 00 00 64
> > > IN.............d [125903.343756] Filesystem "dm-0": XFS internal
> > > error xfs_iformat_extents(1) at line 558 of file
> > > /usr/src/packages/BUILD/kernel-desktop-220.127.116.11/linux-2.6.31/fs/xf
> > >s/xfs_inode.c. Caller 0xffffffffa032c0ad
> > That seems like a different problem to what linda is seeing
> > because this is on-disk corruption. can you dump the bad inode via:
> > # xfs_db -x -r -c "inode 649642" -c p <dev>
> Uh, that's a long output.
> # xfs_db -x -r -c "inode 649642" -c p /dev/swraid0/backup
> u.bmx[0-4] = [startoff,startblock,blockcount,extentflag] 0:
> [0,549849376,2097151,0] 1:[2097151,551946527,2097151,0] 2:
> [4194302,554043678,2097151,0] 3:[6291453,556140829,2097151,0] 4:
> a.sfattr.hdr.totsize = 4
> a.sfattr.hdr.count = 40
> a.sfattr.list.namelen = 35
> a.sfattr.list.valuelen = 136
> a.sfattr.list.root = 1
> a.sfattr.list.secure = 0
> a.sfattr.list.name =
> a.sfattr.list.value =
>From the metadump, I can see that other valid .vhd files are in
local format with:
core.forkoff = 9
a.sfattr.hdr.totsize = 83
a.sfattr.hdr.count = 1
a.sfattr.list.namelen = 12
a.sfattr.list.valuelen = 64
a.sfattr.list.root = 1
a.sfattr.list.secure = 0
a.sfattr.list.name = "SGI_ACL_FILE"
a.sfattr.list.value = <snipped>
All the broken inodes are in the same format as the valid .vhd files,
but the shortform attribute header is completely toast. Once I correct the
header and the lengths, the only thing that looks wrong is:
xfs_db> p a.sfattr.list.name
a.sfattr.list.name = "\035GI_ACL_FILE"
The first character of the name is bad, everything after that -
including the attribute value - is identical to that on other
inodes. What this implies is that we've overwritten the start of
the attribute fork with something, and that looks exactly like the
swap extents problems that we've fixed recently....
> > Hmmmm - do you run xfs_fsr? The errors reported and the corrutpion
> > above are exactly what I'd expect from the swap extent bugs we fixed
> > a while back....
> Yes, xfs_fsdr was running. Disabled it now, and compiled and changed to
> kernel 2.6.34 now. Hope that's OK ;-)
Ok, so we have identified a potential cause. Either disabling fsr or
upgrading to 2.6.34 should be sufficient to avoid the problem. If no
problem show up now you are on 2.6.34, then I'd switch fsr back on
and see if they show up again...