anybody an idea?
[root@fileserver:~]$ setfattr -n harry -v test /mnt/storage/test setfattr: /mnt/storage/test: Operation not supported
[root@fileserver:~]$ tune2fs -l /dev/mapper/StorageVolume-StorageVolumeLogical tune2fs 1.42.3 (14-May-2012) Filesystem volume name: /mnt/storage Last mounted on: /mnt/storage Filesystem UUID: 0e3b09c7-c488-486f-97b8-013e8d01037c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: journal_data_writeback user_xattr acl
hi
possibly better suited to the devel-list
setfattr does not work here on F17/F18 with the latest kernels which is a huge problem with netatalk, especially if you try to build and get working netatalk-3.0.x
the machines are booted with "selinux=0" at the kernel-line but this should and must not be the reason to break support of extended attributes
F17: attr-2.4.46-5.fc17.x86_64 / 3.7.10-101.fc17.x86_64 F18: attr-2.4.46-7.fc18.x86_64 / 3.8.2-201.fc18.x86_64
-------- Original-Nachricht -------- Betreff: problem with extended attributes Datum: Wed, 06 Mar 2013 15:36:24 +0100 Von: Reindl Harald h.reindl@thelounge.net Antwort an: Community support for Fedora users users@lists.fedoraproject.org Organisation: the lounge interactive design An: Mailing-List fedora-users users@lists.fedoraproject.org
anybody an idea?
[root@fileserver:~]$ setfattr -n harry -v test /mnt/storage/test setfattr: /mnt/storage/test: Operation not supported
[root@fileserver:~]$ tune2fs -l /dev/mapper/StorageVolume-StorageVolumeLogical tune2fs 1.42.3 (14-May-2012) Filesystem volume name: /mnt/storage Last mounted on: /mnt/storage Filesystem UUID: 0e3b09c7-c488-486f-97b8-013e8d01037c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: journal_data_writeback user_xattr acl
Reindl Harald writes:
[root@fileserver:~]$ setfattr -n harry -v test /mnt/storage/test setfattr: /mnt/storage/test: Operation not supported
Extended attributes must use a specific namespace, such as "user." or "system."
Try setfattr -n user.harry -v test /mnt/storage/test
Perhaps pre 3.8 kernels allowed any namespace to be used; if so, this must've been undocumetned, because attr(5) was quite explicit, about this, for a long time.
Am 08.03.2013 00:57, schrieb Sam Varshavchik:
Reindl Harald writes:
[root@fileserver:~]$ setfattr -n harry -v test /mnt/storage/test setfattr: /mnt/storage/test: Operation not supported
Extended attributes must use a specific namespace, such as "user." or "system."
Try setfattr -n user.harry -v test /mnt/storage/test
Perhaps pre 3.8 kernels allowed any namespace to be used; if so, this must've been undocumetned, because attr(5) was quite explicit, about this, for a long time
yes i realized this shortly after my post by anoterh answer netatalk upstream asked "does setfattr work on the FS" and sicne i am not intersted in this details and there was error messages from netatalk ACl related i got alarmed
however, we still do not know what netatalk3 hates on existing shares while upgrade from 2.2.x but thats a different story and has to be cleared with netafp.com
On 03/06/13 22:36, Reindl Harald wrote:
anybody an idea?
[root@fileserver:~]$ setfattr -n harry -v test /mnt/storage/test setfattr: /mnt/storage/test: Operation not supported
[root@fileserver:~]$ tune2fs -l /dev/mapper/StorageVolume-StorageVolumeLogical tune2fs 1.42.3 (14-May-2012) Filesystem volume name: /mnt/storage Last mounted on: /mnt/storage Filesystem UUID: 0e3b09c7-c488-486f-97b8-013e8d01037c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: journal_data_writeback user_xattr acl
[egreshko@f18x tmp]$ setfattr -n user.harry -v test /home/egreshko/poc [egreshko@f18x tmp]$ getfattr /home/egreshko/poc getfattr: Removing leading '/' from absolute path names # file: home/egreshko/poc user.harry
Too late in the day to recall where I learned this and/or why.....
Am 06.03.2013 16:23, schrieb Ed Greshko:
On 03/06/13 22:36, Reindl Harald wrote:
anybody an idea?
[root@fileserver:~]$ setfattr -n harry -v test /mnt/storage/test setfattr: /mnt/storage/test: Operation not supported
[root@fileserver:~]$ tune2fs -l /dev/mapper/StorageVolume-StorageVolumeLogical tune2fs 1.42.3 (14-May-2012) Filesystem volume name: /mnt/storage Last mounted on: /mnt/storage Filesystem UUID: 0e3b09c7-c488-486f-97b8-013e8d01037c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: journal_data_writeback user_xattr acl
[egreshko@f18x tmp]$ setfattr -n user.harry -v test /home/egreshko/poc [egreshko@f18x tmp]$ getfattr /home/egreshko/poc getfattr: Removing leading '/' from absolute path names # file: home/egreshko/poc user.harry
Too late in the day to recall where I learned this and/or why.....
aaaaaaahhhh thank you!
currently i try to debug Netatalk3 and such errors below and wanted to make sure EA-support works at all on the volume sys_lsetxattr("/mnt/storage/timemachine/."): Operation not permitted
-
Ed Greshko -
Reindl Harald -
Sam Varshavchik