From: Tom Jones (tjones@statesman.com)
Date: Wed Aug 07 2002 - 12:40:31 EDT
I failed to mention that I've tried using a device of /0un
but had the same EOT results. The Exabyte docs state to use
the default device for maximum compression, therefore I'm
using /dev/rmt/0n and not 0cn or 0un
Thanks
Tom
----- Original Message -----
From: Tom Jones <tjones@statesman.com>
To: Sun Managers List <sun-managers@sunmanagers.ececs.uc.edu>
Sent: Wednesday, August 07, 2002 10:21 AM
Subject: Exabyte Mammoth2 Compression Problem-ns
> 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