[linux-cifs-client] Re: proposed new Unix QFS Info level
Steve French
smfrench at gmail.com
Tue Feb 6 23:33:56 GMT 2007
I thought that some backup applications can use this, but also vaguely
remember
the problem that NFS has with generation numbers and the suggestion to use
this
ioctl (IOC_GETVERSION) to determine if a file (inode) was deleted and
recreated.
googling for this IOCTL I noticed that straces of multiple applications
generate this
so it is clearly used outside of the lsattr call.
On 2/6/07, James Peach <jorgar at gmail.com> wrote:
>
> On 06/02/07, Steve French <smfrench at gmail.com> wrote:
> >
> >
> > On 2/6/07, Volker Lendecke <Volker.Lendecke at sernet.de> wrote:
> > > On Tue, Feb 06, 2007 at 04:48:06PM -0600, Steve French wrote:
> > > > To do gid and uid mappings to/from SIDS e.g. to aid in ACL
> management
> > > > is probably better done via Volker's UnixInfo pipe.
> > >
> > > Not sure the UnixInfo pipe is ever going to make it. I
> > > recently looked more closely at the registry API. This would
> > > give us quite a bit of what we need as well from a data
> > > model point of view.
> > >
> > > Volker
> > >
> > >
> >
> > Do you think that there is a need to support
> > "lsattr -v"
> > (or BSD equivalent) over the network? This returns the version number
> > of a file (via a "well known" ioctl number that multiple fs support).
>
> Are there applications that depend on this (other than lsattr)?
>
> --
> James Peach | jorgar at gmail.com
>
--
Thanks,
Steve
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the linux-cifs-client
mailing list