From: "Ken Schneider" <suse-list@bout-tyme.net>
Just did a mtst -f /dev/st0 densities and the correct setting for DDS-4 should be 0x26. The OP I believe had a code of 0x8c EXB-8505 compressed. Perhaps that is why he is having problems fitting all of his data on a single tape.
Yes, that's exactly the problem... Yesterday I connected another DAT, that was in another Solaris box. Under Solaris I do a mt status and it says DDS-4. Under Suse, it says EXB-8505, just like the other DAT. I already tryied to use 0x26 density, but it seems to have no effect, because I do a status again and I keep seeing EXB-8505. What I was asking for was the DDS-4 density in bpi, so I can pass it to dump as a command line parameter. Also tryied with stinit, but didn't work. I could change between "default" (0x0) and EXB-8505 (0x8c) densities, and between compression on and off, but no DDS-4 at all. Anyway, I'm already working on a three-levels dump backup schedule :( I'm starting to give up with this... It could be the kernel scsi drivers or the scsi controller (but I don't think so). I already downloaded new "drivers" from HP, but I don't think they are actually "drivers". It's more like a diagnostic application, that didn't help at all... Thanks to all BTW: Ciro, I prefer mtst too :)