Package: attr
Version: 2.4.32-1
Severity: important
llistxattr() and therfore
getfattr -h <existing symbolic link>
fail under certain circumstances with "No such file or directory"
test case:
fuse.encfs is mounted on ~/backup and contains a "rsync --fake-super" backup of
(an) /etc,
so ./etc/motd is symbolic link to /var/run/motd
bk...@dlman:~/backup$ id
uid=1250(bk007) gid=34(backup) groups=34(backup),106(fuse)
bk...@dlman:~/backup$ mount |grep backup
encfs on /srv/backup/zdo/backup type fuse.encfs
(rw,nosuid,nodev,default_permissions,user=bk007)
bk...@dlman:~/backup$ file etc/motd
etc/motd: symbolic link to `/var/run/motd'
bk...@dlman:~/backup$ ls -l etc/motd
lrwxrwxrwx 1 bk007 backup 25 2009-02-21 18:39 etc/motd -> /var/run/motd
bk...@dlman:~/backup$ getfattr etc/motd
bk...@dlman:~/backup$ getfattr -h etc/motd
getfattr: etc/motd: No such file or directory
test with a regular file:
bk...@dlman:~/backup$ getfattr etc/passwd
# file: etc/passwd
user.rsync.%stat
bk...@dlman:~/backup$ getfattr -h etc/passwd
# file: etc/passwd
user.rsync.%stat
additional observations:
rsync warning when updating the backup copy:
rsync: get_xattr_names: llistxattr("etc/motd",1024) failed: No such file or
directory (2)
... which shows that the problem might origin in
extern ssize_t llistxattr (const char *__path, char *__list, size_t __size)
__THROW;
... or some permission related problem, because (as root)
dlman:~# file ~bk007/backup/etc/motd
/srv/backup/zdo/backup/etc/motd: ERROR: cannot open
`/srv/backup/zdo/backup/etc/motd' (Permission denied)
-- System Information:
Debian Release: 4.0
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.26-bpo.1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages attr depends on:
ii libattr1 2.4.32-1 Extended attribute shared library
ii libc6 2.3.6.ds1-13etch9 GNU C Library: Shared libraries
attr recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
