[OpenAFS] tapeconfig settings for LTO-5 tape drive
John Sopko
sopko@cs.unc.edu
Fri, 31 May 2013 08:09:33 -0400
--001a11c231deee0f7c04de027c1d
Content-Type: text/plain; charset=ISO-8859-1
I believe the tape label command is reporting 2 TB not 2PB:
2147483648 <2147483648> x 1k = a 2 followed by 12 digits or Terabytes.
Anyway I did some testing to prove the limit is 2TB's and also to test out
my new LTO5 tape
under Red Hat 6.4 and compression is working and the performance seems ok.
I Created a partitions with 10 volumes each containing one 10GB text file
which gives a partition with 100GB of data. The text file contains the
same character and is highly compressible. Did repeated appended dumps
to the same lto5 tape. The tape did stop at 2TB after 21 full dumps and a
partial dump
on the 22 dump.
Here is the backup command status:
backup> stat 3
Task 3023: Dump: 2147483664 Kbytes transferred, volume NB.usr1.backup
[operator wait]
and as expected butc prompts for a tape:
******* OPERATOR ATTENTION *******
Device : /dev/st0
Please put in tape crow_daily.Full.2 (1369966302) for writing and hit
return when done
On Tue, May 28, 2013 at 2:39 PM, chas williams - CONTRACTOR <
chas@cmf.nrl.navy.mil> wrote:
> On Tue, 28 May 2013 13:56:07 -0400
> John Sopko <sopko@cs.unc.edu> wrote:
>
> > According to the docs and the output from butc the max tape size
> > in the /usr/afs/backup/tapeconfig file is 2TB. I set to 8TB and labeled
> > a tape and it appears to be limited to 2TB as shown below.
>
> There are a few afs_int32's hanging around in that code that should
> probably should be afs_uint32's. This would possibly double tape
> capacity to 4TB without too much work I think. A real fix for this
> problem would require quite a bit more work.
>
> > Tape blocks read in 10240 Byte chunks.
> > Labelled tape <NULL> size 2147483648 Kbytes
>
> Cleverly, this is reporting 2PB but I think the programmer meant bytes
> here.
>
--
John W. Sopko Jr. University of North Carolina
email: sopko AT cs.unc.edu Computer Science Dept., CB 3175
Phone: 919-962-1844 Fred Brooks Building; Room 140
Fax: 919-962-1799 Chapel Hill, NC 27599-3175
--001a11c231deee0f7c04de027c1d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I believe the tape label command is reporting 2 TB not 2PB=
:<div><br></div><div>2<a href=3D"tel:2147483648" value=3D"+12147483648">147=
483648</a>=A0x 1k =3D a 2 followed by 12 digits or Terabytes.</div><div><br=
></div>
<div>Anyway I did some testing to prove the limit is 2TB's and =A0also =
to test out my new LTO5 tape</div><div>under Red Hat 6.4 and compression is=
working and the performance seems ok.</div><div><br></div><div><div>I Crea=
ted a partitions with 10 volumes each containing one 10GB text file</div>
<div>which gives a partition with 100GB of data. The text file contains the=
</div><div>same character and is highly compressible. Did repeated appended=
dumps</div><div>to the same lto5 tape. The tape did stop at 2TB after 21 f=
ull dumps and a partial dump</div>
<div>on the 22 dump.</div><div><br></div><div>Here is the backup command st=
atus:</div><div><br></div><div>backup> stat 3</div><div>Task 3023: Dump:=
2147483664 Kbytes transferred, volume NB.usr1.backup</div><div>[operator w=
ait]</div>
<div><br></div><div>and as expected butc prompts for a tape:</div><div><br>=
</div><div>******* OPERATOR ATTENTION *******</div><div>Device : =A0/dev/st=
0=A0</div><div>Please put in tape crow_daily.Full.2 (1369966302) for writin=
g and hit</div>
<div>return when done</div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Tue, May 28, 2013 at 2:39 PM, chas williams - CONTRACTOR <=
span dir=3D"ltr"><<a href=3D"mailto:chas@cmf.nrl.navy.mil" target=3D"_bl=
ank">chas@cmf.nrl.navy.mil</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im">On Tue, 28 May 2013 13:56:07 -0400<br>
John Sopko <<a href=3D"mailto:sopko@cs.unc.edu">sopko@cs.unc.edu</a>>=
wrote:<br>
<br>
> According to the docs and the output from butc the max tape size<br>
> in the /usr/afs/backup/tapeconfig file is 2TB. I set to 8TB and labele=
d<br>
> a tape and it appears to be limited to 2TB as shown below.<br>
<br>
</div>There are a few afs_int32's hanging around in that code that shou=
ld<br>
probably should be afs_uint32's. =A0This would possibly double tape<br>
capacity to 4TB without too much work I think. =A0A real fix for this<br>
problem would require quite a bit more work.<br>
<div class=3D"im"><br>
> Tape blocks read in 10240 Byte chunks.<br>
> Labelled tape <NULL> size <a href=3D"tel:2147483648" value=3D"+1=
2147483648">2147483648</a> Kbytes<br>
<br>
</div>Cleverly, this is reporting 2PB but I think the programmer meant byte=
s<br>
here.<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>John W. Sopk=
o Jr. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0University of North Carolina<b=
r>email: sopko AT <a href=3D"http://cs.unc.edu" target=3D"_blank">cs.unc.ed=
u</a> =A0 =A0 =A0Computer Science Dept., CB 3175<br>
Phone: 919-962-1844 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Fred Brooks Building; Ro=
om 140<br>Fax: =A0 919-962-1799 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Chapel Hill=
, NC 27599-3175
</div></div></div>
--001a11c231deee0f7c04de027c1d--