On Wednesday 26 July 2006 10:11, Anne Wilson wrote: >On Wednesday 26 July 2006 14:48, Gene Heskett wrote: >> >Using >> > >> >mkisofs -joliet -uid 0 -gid 0 -file-mode 444 -dir-mode 555 >> >-output /Backup/mybackup.iso >> > >> >I get 'mkisofs: Missing pathspec.' >> > >> >What am I doing wrong? >> > >> >Anne >> > >> >From the manpage: >> >> SYNOPSIS >> mkisofs [ options ] [ -o filename ] pathspec [pathspec ...] >> >> You gave it the filename you wanted to build as an iso, but the not >> src file pathlist to put in that iso. > >OK, but > >cdrecord dev=cdrom -sao /Backup/mybackup.iso > /Backup/amandatapes/Dailys/slot9 Cdrecord-Clone 2.01-dvd > (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling >Note: This version is an unofficial (modified) version with DVD > support Note: and therefore may have bugs that are not present in the > original. Note: Please send bug reports or support requests to >http://bugzilla.redhat.com/bugzilla >Note: The author of cdrecord should not be bothered with problems in > this version. >cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). >cdrecord: WARNING: This causes a high risk for buffer underruns. >cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler >cdrecord: Permission denied. WARNING: Cannot set priority using > setpriority(). cdrecord: WARNING: This causes a high risk for buffer > underruns. scsidev: '/dev/cdrom' >devname: '/dev/cdrom' >scsibus: -2 target: -2 lun: -2 >Linux sg driver version: 3.5.27 >Using libscg version 'schily-0.8'. >cdrecord: Warning: using inofficial libscg transport code version > (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c > 1.83 04/05/20 Copyright 1997 J. Schilling'). >Device type : Removable CD-ROM >Version : 0 >Response Format: 2 >Capabilities : >Vendor_info : 'LITE-ON ' >Identifikation : 'DVDRW SOHW-1213S' >Revision : 'TS09' >Device seems to be: Generic mmc2 DVD-R/DVD-RW. >cdrecord: Found DVD media: using cdr_mdvd. >Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd). >Driver flags : SWABAUDIO BURNFREE >Supported modes: PACKET SAO >cdrecord: Track 2 has unknown length. >cdrecord: Use tsize= option in SAO mode to specify track size. > >So it looks as though this is more or less what's needed, but that > last line is worrying. > >In this directory, every other file is in the region of 12-14 B long. > And it will be like that in every single backup made. Is it possible > that each file is being treated as a separate track, and cdrecord > can't make a track so small? > >Anne Humm, a possibily I suppose, due to the size of a 'sector' on a iso9660 filesystem. But here, you are asking cdrecord to do the collection which I've little experience with myself. I think the use of growisofs, letting it collect the files, might still be the best way. I've burnt iso's of nearly 3 GB (generated and burnt with k3b) so I know it will go past the magic 2GB point that used to break all file systems, but have not attempted to make or burn one that might go past the 4GB point (given 1024 byte kilobytes) which is a hair more than 4.3GB in decimal sizes. I'd give it a shot here just to waste a disk, but no one slot of my vtapes setup is less than about 6.5GB, which won't fit on one disk :(. On checking, I do have one thats only about 2.6GB. However, that one only has a total of 5 files as thats the one where amanda got a tummy ache and upchucked nearly all the run the other night, so that would be a highly non-normal situation with only one of those 10-14 byte files. I'm afraid I'm not that much help after all. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
