On 2011-08-25, at 12:40 AM, Dave Chinner wrote: > On Thu, Aug 25, 2011 at 02:06:32AM -0400, Christoph Hellwig wrote: >> On Tue, Jun 28, 2011 at 11:33:19AM -0400, Josef Bacik wrote: >>> This is a test to make sure seek_data/seek_hole is acting like it does on >>> Solaris. It will check to see if the fs supports finding a hole or not and will adjust as necessary. >> >> Can you resend this with any updates that happened in the meantime? >> >> Dave also still had some comments about semantics, so it might be worth >> to incorporate that as well. > > The main questions I had when looking at this was how we should > handle unwritten extents - the only answer I got was along the lines > of "we'll deal with that once filesystems have implemented > something". That's a bit of a chicken-and-egg situation, and doesn't > help me decide what is the best thing to do. I don't want to have to > re-implement this code when it's decided i did the wrong thing > initially. Let's first clarify what you mean by an unwritten extent? Do you mean a preallocated extent that returns 0 when read, or do you mean a delayed allocation extent that was written by the application that is still in memory but not yet written to disk? Unfortunately, ZFS has no concept of preallocated extents, so we can't look to it for precedent, but it definitely has delayed allocation. Possibly if UFS on Solaris has SEEK_HOLE and also preallocated extents (I have no idea) it could be tested? > The most basic question I really want answered is this: > > - is preallocated space a HOLE, or is it DATA? > > Whatever the answer, I think it should be consistently > presented by all filesystems that support preallocation, and it > should be encoded into the generic SEEK_HOLE/SEEK_DATA tests.... My thought would be that a preallocated extent is still a HOLE, because it doesn't contain data that an application actually cares about. On the other hand, a delalloc extent is DATA because it has something that an application cares about. The original reason SEEK_HOLE/SEEK_DATA were brought up over FIEMAP was "cp" being able to consistently access delalloc data that was only in the page cache, so if we don't get that right it will have been a pointless exercise. > Answering that question then helps answer the more complex questions > I had, like: > > - what does SEEK_DATA return when you have a file layout > like "hole-prealloc-data"? I would think only the "data" part, since that is what the definition of "SEEK_DATA" is IMHO. > Answers to that sort of question need to be known so we can write > corner-case tests to correctly verify the filesystem implementation. > > I like to do better than present userspace with an interface that > behaves vastly different depending on the underlying filesystem, but > if the answer is "definition and implementation is entirely > filesystem specific" then I'll just go make something up.... > > Cheers, > > Dave. > -- > Dave Chinner > david@xxxxxxxxxxxxx > -- > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html Cheers, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
