On Thu, Jul 19, 2007 at 01:40:01PM -0600, Robert Thurlow wrote: > Albert Chin wrote: > > We can "zfs set xattr=off" on the ZFS filesystems as, according to > > zfs(1m): > > xattr=on | off > > Controls whether extended attributes are enabled for > > this file system. The default value is "on". > > Does this actually help you at all? If so, do you know why? I don't > see a connection to extended attributes here.
No, it doesn't help. > > However, this isn't enough. Is it possible to disable the extra > > attribute bits used by NFS when NFSv3 is being used by the client? We > > don't need any extra attribute bits more than the standard UNIX > > permissions. > > The root cause of the bug you're fighting is that the HP client is > programmed to use a "guard" - it echos a server-generated time and > asks the server to make sure it's correct. The problem is that the > HP-UX client is storing that value with only microsecond precision, > so the fact that ZFS has nanosecond precision means the client's > request doesn't match and needs to be rejected. This is referring > to the sattrguard3 field for SETATTR in /usr/include/rpcsvc/nfs_prot.x > if you want to have a look. With this kind of problem, the only two > options are to change the way the client is coded or to make the > server either throw away precision or accept a value that's actually > incorrect. There's no server side workaround that I could recommend > here; sorry about that :-( Sigh. Ok, thanks. -- albert chin (china at thewrittenword.com)
