Re: [nfsv4] New version of sparse draft(draft-hildebrand-nfsv4-read-sparse-01.txt)

Hi,

Just relative to pNFS, my immediate reaction was that a DS might have the relevant file allocation information, and the MDS might not.  With READZ (is that the current operation name?), this doesn't seem to present a problem.  It would, I guess, perhaps also not present a problem if clients could get a hole map from a DS, but I think that's not what the prior email seemed to be describing?

Thanks,

Matt

----- "J. Bruce Fields" <bfields@fieldses.org> wrote:

> 
> A few questions about a map:
> 
> 	- What is its lifetime?  Will it be a recallable object like a
> 	  layout, or does the client invalidate it normally whenever it
> 	  would invalidate its data cache?
> 	- Does requesting the block map break write delegations, or (on
> 	  servers that support atime) update the atime?
> 	- How does a request for a map they interact with mandatory
> 	  locks?
> 
> --b.
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4

-- 

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309