Is it possible that your 2.1 filesystem was formatted with an older version of mke2fs that
didn't set the persistent mount options in the superblock? You could compare the two
MDTs with "dumpe2fs -h" and look for the mount options stored in the superblock.
On Mar 3, 2015, at 17:51, Chris Hunter <chris.hunter(a)yale.edu>
I did some testing locally, the user_xattr mount option works for lustre 2.5.3 but does
not work for version 2.1. It could there was some mkfs option passed to the 2.1 filesystem
that is preventing user extended attributes.
yale hpc group
> On 02/27/2015 11:05 AM, Chris Hunter wrote:
> Hi Andreas,
> Thanks for the response. I know user_xattr is part of persistant mount
> options for mdt volumes.
> Does it also need to be explicitly included at mount-time (eg. mount -t
> lustre -o user_xattr /dev/mdt /mnt/mdt) ?
> Perhaps there is some additional requirement on the client side ?
> Whenever we try add user_xattr option on the client, we recieve this
>> Lustre: Disabling user_xattr feature because it is not supported on
>> the server
> Any suggestions ?
> chris hunter
>> On 02/26/2015 06:45 PM, Dilger, Andreas wrote:
>>> On 2015/02/26, 8:49 AM, "Chris Hunter"
>>> Anyone know which version of lustre started supporting user extended
>>> file attributes ?
>>> These are the file attributes set with the "setfattr" command
>>> eg) setfattr -n user.comment -v "this is a comment" file.test
>> This has been supported forever (e.g. since 1.4 or something).
>> The main issue is that it needs to be explicitly enabled on the MDS,
>> the total size of xattrs in ext4 is limited. Some sites may want to keep
>> this limited xattr space for e.g. ACLs or something.
>> To enable this you need to add "-o user_xattr" to the mount options
>> the MDT.
>> Cheers, Andreas