As the header in include/cdio/ecma_167.h suggests, the code should be following the ECMA-167 specifications, 3rd edition, June 1997. A URL for the PDF is given: http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-167.pdfand that still works.
Section 4 has information on how files are laid out. I don't see the guarantees, you are looking for, but you should read it yourself. On Thu, Oct 21, 2010 at 2:02 AM, Shaya Potter <[email protected]> wrote: > I'm just wondering if a file in a UDF file system can be fragmented? > > i.e. if I know the start block of a file is X and that the files is Y > blocks long, am I guaranteed that the file is then stored from X->X+Y-1? > > from reading the code, it seems that's what the code assumes, but don't > know 1) if my reading of the code is correct and 2) even if my reading is > correct, if it's possible for the code to be wrong (just in practice doesn't > impact much?) > > just wondering, as i'm mostly reading the disk straight, not through > libudf, just using it to get where I believe the file is delimited, but > wondering if my assumption of non fragments is correct. Mostly brought > about by a a DVD that I see that has a bunch of 0 length files located in > what I'd assume to be the location of a longer file. > >
