One PC has NFS shares being mounted with system.nfs4_acl= attribute. Others do not.
by allend from LinuxQuestions.org on (#6NSZ4)
I am sure that this is a local issue, but I am hoping that other eyes might help.
In a small local LAN, on one PC, when an NFS share is mounted then files are being with a system.nfs4_acl= attribute.
Code:# getfattr -d -m "-" /mnt/tmp/root/unmanaged.sh
getfattr: Removing leading '/' from absolute path names
# file: mnt/tmp/root/unmanaged.sh
system.nfs4_acl=0sAAAAAwAAAAAAAAAAABYBpwAAAAZPV05FUkAAAAAAAAAAAAAAABIAoQAAAAZHUk9VUEAAAAAAAAAAAAAAABIAoQAAAAlFVkVSWU9ORUAAAAA=No such attribute appears when mounting NFS shares on the other PCs. All are running Slackware64-15.0 and get updates in unison.
This is not a show stopper, but leads to error messages like
Quote:
when running 'cp -av' that I would like to go away.
Somehow I have flicked something, but so far I cannot find the cause. Any ideas?
In a small local LAN, on one PC, when an NFS share is mounted then files are being with a system.nfs4_acl= attribute.
Code:# getfattr -d -m "-" /mnt/tmp/root/unmanaged.sh
getfattr: Removing leading '/' from absolute path names
# file: mnt/tmp/root/unmanaged.sh
system.nfs4_acl=0sAAAAAwAAAAAAAAAAABYBpwAAAAZPV05FUkAAAAAAAAAAAAAAABIAoQAAAAZHUk9VUEAAAAAAAAAAAAAAABIAoQAAAAlFVkVSWU9ORUAAAAA=No such attribute appears when mounting NFS shares on the other PCs. All are running Slackware64-15.0 and get updates in unison.
This is not a show stopper, but leads to error messages like
Quote:
| cp: preserving permissions for i<filename>i: Operation not supported |
Somehow I have flicked something, but so far I cannot find the cause. Any ideas?