Andreas Dilger wrote: > On Feb 07, 2008 17:14 +0000, Ricardo Correia wrote: >> On Qui, 2008-02-07 at 09:44 -0700, Mark Shellenbaum wrote: >>> Section 2.2.4 >>> >>> Not sure what you mean by storing all xattrs in a single object? Are you >>> saying all of the Lustre attributes would be stored in a single Solaris >>> extended attribute file? >> Yes. The benefit of this approach is that it would greatly reduce the >> number of seeks (which are always in short supply) in a Lustre metadata >> server in the case where the xattrs won't fit in the dnode. > > To clarify, this is a desirable approach for the "spill over" case where > the small attributes don't fit into the dnode bonus buffer. The current > situation is that every xattr needs a ZAP entry + dnode + block, no matter > what size it is. The "EA in dnode" change moves these attributes into > the dnode
Not as I read it. Solaris extended attributes will continue to be stored as they are today -- as separate files in an xattr directory hung of the main file. The proposal is for some new system-interpreted attributes to be stored in the dnode. This is a different namespace with different requirements and different semantics. You don't need to set an ACL on your lustre metadata, do you? --matt
