Paul Slootman wrote:
> On Sat 06 Sep 2008, Sven Hartge wrote:
>> It dies inside while rsyncing my cowbuilder chroot(), to my totally
>> uneducated
>> eye (and brain) this looks like a problem with -X, because rsync is able to
>> complete the job while not using -X.
>>
>> Kernel is configured with XATTR support:
>>
>> CONFIG_EXT3_FS=y
>> CONFIG_EXT3_FS_XATTR=y
>> CONFIG_EXT3_FS_POSIX_ACL=y
>> CONFIG_EXT3_FS_SECURITY=y
>>
>> but the mount of the target filesystem does not use it:
>>
>> /mnt/mybook/backup/hild-backup.img on /mnt/backup type ext3
>> (rw,loop=/dev/loop0)
>
> How about the source directory, / ?
No ACLs or other funky stuff there:
/dev/hda1 on / type ext3 (rw,relatime,errors=remount-ro,barrier=1)
>> (gdb) bt
>> #0 0x08080403 in xattr_diff (file=0xb534a220, sxp=0xbfbab7fc, find_all=1)
>> at xattrs.c:445
> [...]
>> (gdb) bt full
>> #0 0x08080403 in xattr_diff (file=0xb534a220, sxp=0xbfbab7fc, find_all=1)
>> at xattrs.c:445
>> lst = (item_list *) 0x80cdc80
>> snd_rxa = (rsync_xa *) 0x807e240
>> rec_rxa = (rsync_xa *) 0xbfbaa79c
>> snd_cnt = 1
>> rec_cnt = 0
>> cmp = 1
>> same = 135028592
>> xattrs_equal = 1
>
> Could you also do a "p *sxp" and "p *(sxp->xattr)" (if it's not null) ?
> I'm wondering wondering whether something there might be null
> unexpectedly...
(gdb) p *sxp
$1 = {st = {st_dev = 1792, __pad1 = 0, __st_ino = 1119785, st_mode = 33261,
st_nlink = 2,
st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, st_size = 14112,
st_blksize = 4096,
st_blocks = 32, st_atim = {tv_sec = 1221055064, tv_nsec = 0}, st_mtim =
{tv_sec = 1218054609,
tv_nsec = 0}, st_ctim = {tv_sec = 1221055064, tv_nsec = 0}, st_ino =
1119785},
acc_acl = 0x8324ee8, def_acl = 0x0, xattr = 0x4}
(gdb) p *(sxp->xattr)
Cannot access memory at address 0x4
Hmm. Interesting.
Grüße,
Sven.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
