[Top][All Lists]

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

Re: [Libcdio-devel] can files in UDF be fragmented?

From: Shaya Potter
Subject: Re: [Libcdio-devel] can files in UDF be fragmented?
Date: Thu, 21 Oct 2010 10:53:07 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5

On 10/21/2010 05:11 AM, Rocky Bernstein wrote:
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:
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.

then does libcdio work? it would seem from my reading that every udf_read_block() is basically made as an offset to the start of the file.


1) it calls offset_to_lba to find start sector and length
2) computed max # of blocks
3) calls udf_read_sectors() w/ that information


translated the call into a

cdio_stream_read() or cdio_read_data_sectors() call (as I'm dealing with image files, I'll just deal with stream_read()

and cdio_read_data_sectors() seems like its just a sequential read.

so am I right to understand that libudf would (could?) fail on these files if they are guaranteed to be sequential?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]