On Fri, 2010-06-25 at 12:53 -0500, Richard Shaw wrote: > On Fri, Jun 25, 2010 at 12:37 PM, Linuxguy123 <linuxguy123@xxxxxxxxx> > wrote: > > On Fri, 2010-06-25 at 08:57 -0600, Linuxguy123 wrote: > >> On Mon, 2010-06-14 at 15:37 -0500, Richard Shaw wrote: > >> > Let me know if you have any issues. > >> > >> Just one: > >> > >> Ready to burn disc 1/4. > >> The disc capacity of the disc in /dev/sr0 (BD ROM BC-5500A) is > 4.38G. > >> growisofs -Z /dev/sr0 -speed=16 -use-the-force-luke=notray > >> -use-the-force-luke=tty -V DiscSpan1 -A DiscSpan -p Unknown > -iso-level > >> 4 -l -r -hide-rr-moved -J -joliet-long -graft-points > >> -path-list /tmp/tmpOKxvoj.discspanlist > >> Executing 'mkisofs -V DiscSpan1 -A DiscSpan -p Unknown -iso-level 4 > -l > >> -r -hide-rr-moved -J -joliet-long -graft-points > >> -path-list /tmp/tmpOKxvoj.discspanlist | builtin_dd of=/dev/sr0 > obs=32k > >> seek=0' > >> Warning: Creating ISO-9660:1999 (version 2) filesystem. > >> Warning: ISO-9660 filenames longer than 31 may cause buffer > overflows in > >> the OS. > >> genisoimage: No such file or directory. Invalid node - > >> > '33B6018B5B284AA3487EA8F5BB393C6E/ka_prepostroll.sol=/media/%/brenda/Documents and Settings/Server Server/Application Data/Macromedia/Flash Player/#SharedObjects/EF6WTTFH/affiliate.kickapps.com/kickapps/flash/premium_drop_v3.swf;jsessionid=33B6018B5B284AA3487EA8F5BB393C6E/ka_prepostroll.sol'. > >> :-( write failed: Input/output error > > > > Why does this -iso-level 4 as described in man mkisofs ? > > > > I'm obviously backing up data from a Windows machine. There is > nothing > > I can do about those file names if I am to preserve their meaning. > > I think you're asking, why does it use --iso-level4? From what I can > tell it is the least stringent as far as special characters, directory > depth, and filename length. If the files you want to backup can't be > written with --iso-level4, then you're pretty much out of luck and > need to pursue a different backup method. I'm asking why the file names are generating an error under level 4. >From what I can tell, it seems they should pass. I wish K3B could handle splitting data... ie give it a hunk of data larger than a single disk and it would let the user divy it up into multiple disks. I've run into this before with other data. Manual data splitting is a pain. THanks for the reply, btw. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
