Distribution: debian sid Hardware Environment: liteon CD burner Mount Rainier capable Software Environment: Problem Description: I prepared a CD on Windows with InCD. The tools used mounr Rainier and a UDF 2.50 file system type. Unfortunately, UDF read is supported up to 2.01 specs not 2.50. Steps to reproduce: Use InCD tools on WIndows and select UDF 2.50 file system when peparing the CDRW. Then try to read it on Linux.
Eric, har it been resolved in recent kernel? are you still using this hardware? Thanks.
bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=3300 > > > protasnb@gmail.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |protasnb@gmail.com > > > > > ------- Comment #1 from protasnb@gmail.com 2007-09-19 05:52 ------- > Eric, har it been resolved in recent kernel? are you still using this > hardware? > Thanks. > > > This is not a hardware problem but a problem with the in kernel implementation that does not support some udf version. If you use nero and set explicitely the UDF version, linux just cannot mount it... -- eric
bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=3300 > > > protasnb@gmail.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |protasnb@gmail.com > > > > > ------- Comment #1 from protasnb@gmail.com 2007-09-19 05:52 ------- > Eric, har it been resolved in recent kernel? are you still using this > hardware? > Thanks. > > > Checked the source in 2.6.23-rc6-git7 answer is no. udf_sb.h #define UDF_MAX_READ_VERSION 0x0201 #define UDF_MAX_WRITE_VERSION 0x0201 -- eric
Wow it's an old problem... I will try to get help from developers. Thanks Eric.
Yes, I know we don't support UDF 2.50 :). I have a patch and plan on merging it soon (probably will get to 2.6.26).
The patch went into Linus's 2.6.26-rc1 so you can try it if you are brave enough :) If it doesn't work for you, please reopen the bug. Thanks.