On Friday 27 August 2004 08:21, Corinna Vinschen wrote:
> So you didn't look into the `mt status 3' output? I've marked it in
> my original reply. It's the Windows driver value for the maximum
> block size. That has nothing to do with Cygwin.
I did but was not sure if that meant that it was a W
On Aug 27 07:13, Bill Nugent wrote:
> Hi Corinna,
>
> Setting tar's -b size up resulted in a radical increase. Still not
> streaming but real close and workable. Reading in a 100GB tape with
> 500MB to 1,500MB files should take about three or four hours instead of
> three weeks! I'm going to
Hi Corinna,
Setting tar's -b size up resulted in a radical increase. Still not
streaming but real close and workable. Reading in a 100GB tape with
500MB to 1,500MB files should take about three or four hours instead of
three weeks! I'm going to keep experimenting to see if I can get it to
s
On Aug 24 12:04, Corinna Vinschen wrote:
> On Aug 23 18:40, Bill Nugent wrote:
> > mt -f /dev/nst0 setblk 8192
> > tar -tf /dev/nst0 -b 32
>
> tar --help, especially the -b option.
Uhm... sorry, scratch that.
> > Block size does not seem to be a factor. I've tried 8k, 16k and 32k
> > (over 3
On Aug 23 18:40, Bill Nugent wrote:
> mt -f /dev/nst0 setblk 8192
> tar -tf /dev/nst0 -b 32
tar --help, especially the -b option.
> Block size does not seem to be a factor. I've tried 8k, 16k and 32k
> (over 32k doesn't work for some reason).
Did you have a look into the `mt status 3' output
5 matches
Mail list logo
