Exabyte M2 compression problem

From: Tom Jones (tjones@statesman.com)
Date: Wed Aug 07 2002 - 11:50:08 EDT


I'm having a problem with compression on an Mammoth2
tape drive (firmware v05c) connected to an
Enterprise E420R running Solaris 2.6

ufsdump has recently started hitting EOT and requesting
a 2nd tape to be inserted. The largest filesystem being
backed up to that tape is just over 65GB containing user's
mailboxes (i.e. text files - should be good compression)
The native capacity of the M2 drive is 60GB so I should not
be hitting EOT at 65GB.

The st.conf setting is set to the Exabyte recommended
setting:

"EXABYTE Mammoth2", "Exabyte Mammoth2", "EXB-M2";
EXB-M2 = 1,0x35,0,0x1de39,1,0x28,0;

The ufsdump command I'm using (inside a shell script) is:
ufsdump 0ubf 512 /dev/rmt/0n /dev/md/rdsk/d13

Has anyone seen this compression problem before? Anyone
with different st.conf settings? I found a webpage with
test comparison results between DLT and M2 that had
a minor difference in the st.conf setting.

Thanks
Tom Jones
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:43 EDT