Re: File Read Returns Non-existent Null Bytes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> However if you are asking us for an extensive list of "this is what I
> can expect if I ignore these rules", then I don't think you will find
> much traction. Such a list would be committing us to defining a model
> for "non-close-to-open" semantics, which isn't of interest to me at
> least, and I doubt anyone else is interested in committing to
> maintaining that.

One more point on this.  I wasn't really asking for a list of what I
can expect if I ignore the rules (although I think pointing out that
reading corrupt data from the cache is worth mentioning), I was asking
what the rules for close-to-open consistency were so I can follow
them.  I now know one of them is that if a file is open for writing on
one client then it can't be read on another.  Are there others?
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux