I guess that's right. I don't think it helps consistency, but once the client marks its entry as potentially inconsistent, it won't be able to make use of an XCB update anyway.
Matt ----- "Jeffrey Altman" <[email protected]> wrote: > On 4/18/2013 12:01 PM, Simon Wilkinson wrote: > > > > On 18 Apr 2013, at 16:58, Matt W. Benjamin wrote: > > > >> What is the scope of the proposed invalidation? > > > > Clearing the Statd flag on all of the vnodes which the RPC might > affect. So you have to do a FetchStatus to discover whether the RPC > succeeded or not. > > > > S. > > And in a XCB world potentially issuing a GiveUpCallBack to notify the > file server that you are no longer in sync. -- 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 _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
