flexbackup-help

[flexbackup-help] Version 1.01 and mt setblk in Linux

[Douglas B. <dc...@sd...>]

I've been using the flexbackup script for a long time.  Love it!

In the latest update, my system has been having trouble,

I need to have blocks set to 512, but the script takes the 512*1024.  This
doesn't work for me.  Output of the flexbackup error:

Neither of these commands worked:
  mt -f /dev/nst0 setblk 524288
  mt -f /dev/nst0 defblksize 524288

But, if I do this manually:

rodan:~# mt -f /dev/nst0 setblk 524288
mt: /dev/nst0: Input/output error
rodan:~# mt -f /dev/nst0 setblk 512   
rodan:~#

You can see, I need the blocks in k's, not multiplied by 1024.  In the
script I had to change line 2251:

#   $main::mt_blksize = $cfg::blksize * 1024;
    $main::mt_blksize = $cfg::blksize;

And now it works.

I'm using Debian Woody with a IDE tape drive run through SCSI emulation.

-- 
You can rent this space for only $5 a week.

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Edwin H. <ed...@co...>]

[ Douglas Bollinger wrote: ]
> I've been using the flexbackup script for a long time.  Love it!

Thanks!

> In the latest update, my system has been having trouble,

(Strange, as recent changes haven't touched mt blocksize that I recall)

> I need to have blocks set to 512, but the script takes the 512*1024.  This
> doesn't work for me.  Output of the flexbackup error:
> 
> Neither of these commands worked:
>   mt -f /dev/nst0 setblk 524288
>   mt -f /dev/nst0 defblksize 524288
> 
> But, if I do this manually:
> 
> rodan:~# mt -f /dev/nst0 setblk 524288
> mt: /dev/nst0: Input/output error
> rodan:~# mt -f /dev/nst0 setblk 512   
> rodan:~#
> 
> You can see, I need the blocks in k's, not multiplied by 1024.  In the
> script I had to change line 2251:
> 
> #   $main::mt_blksize = $cfg::blksize * 1024;
>     $main::mt_blksize = $cfg::blksize;
> 
> And now it works.


I bet you can set $blksize=1 and you'd be fine.  A multiple of the
hardware block size is OK in my experience and testing.  

I think the problem you ran into is that 512k is huge and over a limit
somewhere.

Also, does $mt_var_blksize='true' work for you?  That's more often
recommended and is easier than trying to find the right blocksize for your
tape drive.

At any rate, please report back.  I may need to adjust so non-multiples of
1024 bytes can be used.


Thanks, 
  -Edwin


-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Luis C. <ad...@co...>]

I have been having a similar problem.  I haven't tried this fix yet, but I
hope this does it for me.

My problem is that I set the default to 64 blocks.  I am guessing that the
default block size is 512 bytes.  But when I try to list anything, it either
says something about the first block all null or that the archive is not
correctly terminated and false to list anything.



----- Original Message -----
From: "Edwin Huffstutler" <ed...@co...>
To: "Douglas Bollinger" <dc...@sd...>
Cc: <fle...@li...>
Sent: Saturday, February 15, 2003 2:22 PM
Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux


>
> [ Douglas Bollinger wrote: ]
> > I've been using the flexbackup script for a long time.  Love it!
>
> Thanks!
>
> > In the latest update, my system has been having trouble,
>
> (Strange, as recent changes haven't touched mt blocksize that I recall)
>
> > I need to have blocks set to 512, but the script takes the 512*1024.
This
> > doesn't work for me.  Output of the flexbackup error:
> >
> > Neither of these commands worked:
> >   mt -f /dev/nst0 setblk 524288
> >   mt -f /dev/nst0 defblksize 524288
> >
> > But, if I do this manually:
> >
> > rodan:~# mt -f /dev/nst0 setblk 524288
> > mt: /dev/nst0: Input/output error
> > rodan:~# mt -f /dev/nst0 setblk 512
> > rodan:~#
> >
> > You can see, I need the blocks in k's, not multiplied by 1024.  In the
> > script I had to change line 2251:
> >
> > #   $main::mt_blksize = $cfg::blksize * 1024;
> >     $main::mt_blksize = $cfg::blksize;
> >
> > And now it works.
>
>
> I bet you can set $blksize=1 and you'd be fine.  A multiple of the
> hardware block size is OK in my experience and testing.
>
> I think the problem you ran into is that 512k is huge and over a limit
> somewhere.
>
> Also, does $mt_var_blksize='true' work for you?  That's more often
> recommended and is easier than trying to find the right blocksize for your
> tape drive.
>
> At any rate, please report back.  I may need to adjust so non-multiples of
> 1024 bytes can be used.
>
>
> Thanks,
>   -Edwin
>
>
> --
>  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
>
>
>

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Luis C. <ad...@co...>]

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,
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?



----- Original Message -----
From: "Luis Cortes" <ad...@co...>
To: <fle...@li...>
Sent: Saturday, February 15, 2003 8:16 PM
Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux


> I have been having a similar problem.  I haven't tried this fix yet, but I
> hope this does it for me.
>
> My problem is that I set the default to 64 blocks.  I am guessing that the
> default block size is 512 bytes.  But when I try to list anything, it
either
> says something about the first block all null or that the archive is not
> correctly terminated and false to list anything.
>
>
>
> ----- Original Message -----
> From: "Edwin Huffstutler" <ed...@co...>
> To: "Douglas Bollinger" <dc...@sd...>
> Cc: <fle...@li...>
> Sent: Saturday, February 15, 2003 2:22 PM
> Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux
>
>
> >
> > [ Douglas Bollinger wrote: ]
> > > I've been using the flexbackup script for a long time.  Love it!
> >
> > Thanks!
> >
> > > In the latest update, my system has been having trouble,
> >
> > (Strange, as recent changes haven't touched mt blocksize that I recall)
> >
> > > I need to have blocks set to 512, but the script takes the 512*1024.
> This
> > > doesn't work for me.  Output of the flexbackup error:
> > >
> > > Neither of these commands worked:
> > >   mt -f /dev/nst0 setblk 524288
> > >   mt -f /dev/nst0 defblksize 524288
> > >
> > > But, if I do this manually:
> > >
> > > rodan:~# mt -f /dev/nst0 setblk 524288
> > > mt: /dev/nst0: Input/output error
> > > rodan:~# mt -f /dev/nst0 setblk 512
> > > rodan:~#
> > >
> > > You can see, I need the blocks in k's, not multiplied by 1024.  In the
> > > script I had to change line 2251:
> > >
> > > #   $main::mt_blksize = $cfg::blksize * 1024;
> > >     $main::mt_blksize = $cfg::blksize;
> > >
> > > And now it works.
> >
> >
> > I bet you can set $blksize=1 and you'd be fine.  A multiple of the
> > hardware block size is OK in my experience and testing.
> >
> > I think the problem you ran into is that 512k is huge and over a limit
> > somewhere.
> >
> > Also, does $mt_var_blksize='true' work for you?  That's more often
> > recommended and is easier than trying to find the right blocksize for
your
> > tape drive.
> >
> > At any rate, please report back.  I may need to adjust so non-multiples
of
> > 1024 bytes can be used.
> >
> >
> > Thanks,
> >   -Edwin
> >
> >
> > --
> >  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
> >
> >
> >
>
>
>
> -------------------------------------------------------
> 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
>
>
>

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Edwin H. <ed...@co...>]

[ 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

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Luis C. <ad...@co...>]

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
>
>
>

RE: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Luis C. <ad...@co...>]

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

RE: [flexbackup-help] Version 1.01 and mt setblk in Linux

[John R. <jo...@re...>]

[ On Wednesday, February 19, Luis Cortes wrote: ]
> 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.
> 

at line 2266 put

	$main::cpio_blk_flag = "--block-size=$main::cpio_blk_flag";

(you can either add that line into the code after the line that says
$main::cpio_blk_flag = "-C $main::cpio_blk_flag"; and the cpio_blk_flag
variable will just get overriden, or you can comment out the "-C" line with
a '#' and then add the --block-size line).

Hope this helps. If it does, maybe there's some things that Edwin and I can do
to "steer" flexbackup to do the right thing given a config knob or something.

-Jr

-- 
John & Jennifer Reynolds  jo...@re...  http://www.reynoldsnet.org/
Sr. Component Design Engineer, ICG, Intel Corp.    jre...@se...
Running FreeBSD since 2.1.5-RELEASE.               FreeBSD: The Power to Serve!
"Unix is user friendly, it's just particular about the friends it chooses."