Re: ISO9660 4GB directory structures boundary limit and growisofs
On 4/19/10, Paul B Mahol one...@gmail.com wrote: On 4/19/10, Tom Evans tevans...@googlemail.com wrote: On Mon, Apr 19, 2010 at 1:48 PM, Paul B Mahol one...@gmail.com wrote: On 4/17/10, Paul B Mahol one...@gmail.com wrote: On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. Update: Linux shows all sessions and Windows 7 shows only first one. From the source code of groisofs.c: * - DVD+R Double Layer support; * - -use-the-force-luke=4gms to allow ISO9660 directory structures * to cross 4GB boundary, the option is effective only with DVD+R DL * and for data to be accessible under Linux isofs a kernel patch is * required; So I'm guessing it does something non standard, particularly if windows also refuses to see the data. That is pretty old, from 2.4 era, it was added after it was found that isofs had bug. Windows at least try to show something - only one session, but fourth and not second session crossed 4GB limit. The source also claims that in BD case there is no need for _force_ switch at all. Mounting with -norrip shows all sessions. Kernel displays RRIP without PX field? if I try to mount normal way. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
Hi, Paul B Mahol wrote: On 4/19/10, Paul B Mahol one...@gmail.com wrote: On 4/19/10, Tom Evans tevans...@googlemail.com wrote: On Mon, Apr 19, 2010 at 1:48 PM, Paul B Mahol one...@gmail.com wrote: On 4/17/10, Paul B Mahol one...@gmail.com wrote: On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. Update: Linux shows all sessions and Windows 7 shows only first one. From the source code of groisofs.c: * - DVD+R Double Layer support; * - -use-the-force-luke=4gms to allow ISO9660 directory structures * to cross 4GB boundary, the option is effective only with DVD+R DL * and for data to be accessible under Linux isofs a kernel patch is * required; So I'm guessing it does something non standard, particularly if windows also refuses to see the data. That is pretty old, from 2.4 era, it was added after it was found that isofs had bug. Windows at least try to show something - only one session, but fourth and not second session crossed 4GB limit. The source also claims that in BD case there is no need for _force_ switch at all. Mounting with -norrip shows all sessions. Kernel displays RRIP without PX field? if I try to mount normal way. Might this help ? Kernel config /sys/conf/NOTES options UDF #Universal Disk Format My config notes /* Allows DVDs with files 2 Gig, to avoid: * ls: file_about_2.5gig.ts: * Value too large to be stored in data type * ports/sysutils/k3b can use it to write eg 4G+ files. */ Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text, Not HTML quoted-printable Base64 http://www.asciiribbon.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
On 4/17/10, Paul B Mahol one...@gmail.com wrote: On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. Update: Linux shows all sessions and Windows 7 shows only first one. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
on 17/04/2010 19:31 Tim Kientzle said the following: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I don't think that the problem is with limit on sector count here. I think it's a limitation with size/offset in bytes somewhere in cd9660 fs driver. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
On Mon, Apr 19, 2010 at 1:48 PM, Paul B Mahol one...@gmail.com wrote: On 4/17/10, Paul B Mahol one...@gmail.com wrote: On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. Update: Linux shows all sessions and Windows 7 shows only first one. From the source code of groisofs.c: * - DVD+R Double Layer support; * - -use-the-force-luke=4gms to allow ISO9660 directory structures * to cross 4GB boundary, the option is effective only with DVD+R DL * and for data to be accessible under Linux isofs a kernel patch is * required; So I'm guessing it does something non standard, particularly if windows also refuses to see the data. Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
On 4/19/10, Tom Evans tevans...@googlemail.com wrote: On Mon, Apr 19, 2010 at 1:48 PM, Paul B Mahol one...@gmail.com wrote: On 4/17/10, Paul B Mahol one...@gmail.com wrote: On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. Update: Linux shows all sessions and Windows 7 shows only first one. From the source code of groisofs.c: * - DVD+R Double Layer support; * - -use-the-force-luke=4gms to allow ISO9660 directory structures * to cross 4GB boundary, the option is effective only with DVD+R DL * and for data to be accessible under Linux isofs a kernel patch is * required; So I'm guessing it does something non standard, particularly if windows also refuses to see the data. That is pretty old, from 2.4 era, it was added after it was found that isofs had bug. Windows at least try to show something - only one session, but fourth and not second session crossed 4GB limit. The source also claims that in BD case there is no need for _force_ switch at all. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
on 17/04/2010 02:07 Paul B Mahol said the following: Hi, It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Is it expected that everyone knows what -use-the-force-luke=4gms is? Should we allow it like linux does? What exactly is disallowed on FreeBSD? -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
On 4/17/10, Andriy Gapon a...@icyb.net.ua wrote: on 17/04/2010 02:07 Paul B Mahol said the following: Hi, It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Is it expected that everyone knows what -use-the-force-luke=4gms is? Should we allow it like linux does? What exactly is disallowed on FreeBSD? http://fy.chalmers.se/~appro/linux/DVD+RW/ search for 4gms :) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). Tim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ISO9660 4GB directory structures boundary limit and growisofs
On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
