From: Luis C. <ad...@co...> - 2003-02-19 23:44:29
|
My Perl is REAL rusty, can anyone tell me what to change in flexbackup to get it to change from: cpio -t -v -C 32768 to cpio -t -v --block-size=64 Thanks ahead of time for any help, Luis. -----Original Message----- From: fle...@li... [mailto:fle...@li...] On Behalf Of Luis Cortes Sent: Monday, February 17, 2003 11:08 AM To: fle...@li... Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux Okay here is the error I get: flexbackup version 1.0.1 (http://flexbackup.sourceforge.net) /etc/flexbackup.conf syntax OK |------------------------------------------------------------ | Checking /bin/sh on this machine... bash2 |------------------------------------------------------------ | Logging output to "flexbackup.list.200302171143.log" | Trying "mt defblksize" instead of "mt setblk" | Reading from current tape position |------------------------------------------------------------ At block 134227397. |------------------------------------------------------------ | dd ibs=32k obs=32k conv=noerror,sync if="/dev/nst0" | cpio -t -v -C |32768 |------------------------------------------------------------ 1+0 records in 1+0 records out cpio: premature end of archive |------------------------------------------------------------ At block 134227401. |------------------------------------------------------------ When I change the cpio command to block-size=64 instead of C, then it works: cpio -t -v --block-size=64 I think it is just my tape is real finicky about blocks. I guess I will need to do with same with gzip. ----- Original Message ----- From: "Edwin Huffstutler" <ed...@co...> To: "Luis Cortes" <ad...@co...> Cc: <fle...@li...> Sent: Sunday, February 16, 2003 8:37 AM Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux > > [ Luis Cortes wrote: ] > > Okay, let me clarify my own response. I believe that for programs > > like tar > > or cpio, the default block size is 512. When you specify 64 blocks, > > Nope. > > tar and many others default to 10k. cpio does default to 512 bytes. > We don't use defaults for anything anyway, so it doesn't matter. > > > flexbackup thinks it's 1024 * 64. If you specify 64 blocks for cpio > > it means 512 * 64. It seems to me that there is a logic problem > > somewhere. Am > > I right about this? > > Nope. > > The config file says "Block size (k)" for $blksize, and that's what it > means. It's converted for whichever archiver as needed. > > Flexbackup sets the flags are all set so units are consistent. Check > the manpages and code. > > > tar: > -b, --block-size N > block size of Nx512 bytes (default N=20) > > cpio: (flexbackup uses the -C flag!) > -C IO-SIZE, --io-size=IO-SIZE > Set the I/O block size to IO-SIZE bytes. > > dump: > -b blocksize > The number of kilobytes per dump record. Since the IO system > slices all requests into chunks of MAXBSIZE (typically > 64kB), it > is not possible to use a larger blocksize without having problems > later with restore(8). Therefore dump will constrain > writes to > MAXBSIZE. The default blocksize is 10. > > afio: > -b size Read or write size-character archive blocks. Suffices of > b, k, m and g denote multiples of 512, kilobytes, > megabytes and gigabytes, respectively. Defaults to 5120 > for compatibility with cpio(1). In some cases, notably > when using ftape with some tape drives, -b 10k is needed > for compatibility. Note that -b 10k is the default block > size used by tar(1), so it is usually a good choice if the > tape setup is known to work with tar(1). > > etc.. > > -- > Edwin Huffstutler Linux - because reboots are for hardware changes > ed...@co... GnuPG Key ID: AE782DC9 > > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ flexbackup-help mailing list fle...@li... https://lists.sourceforge.net/lists/listinfo/flexbackup-help |