>>>>> " " == Stephen C Tweedie <sct@redhat.com> writes:
> What is the problem? You just cannot assume that the pointer
> progresses in a nice, arithmetic patter in directories. If you
> are at lseek() point P and read Q bytes, you are not going to
> end up at P+Q: the actual file location you end up at depends
> on how much padding there was in the directory and how much
> extra filesystem metadata was there that didn't get returned to
> user space. It's not just odd cases like NFS that have this
> property: even ext2 does.
Indeed, NFS currently (for 2.3.99-pre4 at least) just mirrors whatever
assumptions the server has. If the latter does whatever the underlying
filesystem does --as is the case for knfsd-- then the NFS client will
too...
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:13 EST