Solaris 8 st.conf with no density bits?

I was looking for the latest info on supporting some Sony AIT2 drives now that I have installed the latest st patch on my Solaris 8 backup hosts (we are still keeping Netbackup 3.4 in production!), and the recommended config from Sony (in a manual dated Feb 2007) recommends this line for the st.conf entry:

SONY_AIT = 1, 0x36, 0, 0x19639, 4, 0x00, 0x00, 0x00, 0x00, 0;

The density flags are all zero. Is the st driver smart enough now to enable maximum density and compression if I specify /dev/rmt/0ubn? Or do I still need to tweak these settings?

The old entry in the legacy st.conf file had this:

SONY_AIT = 1, 0x36, 0, 0x19639, 4, 0x00, 0x00, 0x00, 0x00, 0;

Thanks --w

[710 byte] By [GOTOMOJOa] at [2007-11-27 2:59:44]
# 1

They're not density "bits" per se (like bit flags). It's just a one byte identifier for the device on a setting. So it only makes sense if the device has such settings.

For AIT, yes this is normal. Unlike DLT/LTO stuff, AIT does not seem to support writing old densities on new tapes for compatibility with older drives. Because of that, you don't need to select the density at all. It will simply write at the one density that is supported on your tape.

While compression *can* be handled with the density settings, there are alternate ways. See the 'st' man page for ST_MODE_SEL_COMP. You have that bit (x10000) set in the device settings. That indicates that the u/c device will enable compression, while the other devices (l,m,h) will not.

--

Darren

Darren_Dunhama at 2007-7-12 3:40:22 > top of Java-index,General,Talk to the Sysop...