Subject: Re: multi-volume dump fails, problem with st driver?
To: Scott Presnell <srp@zgi.com>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: tech-kern
Date: 10/03/2002 22:49:07
On Thu, Oct 03, 2002 at 05:28:50PM +0000, Scott Presnell wrote:
> Hi Folks, 
> 	I'm using NetBSD/i386 1.5.2 (patched heavily for security issues) and a
> HP T4000...
> 
> ahc0 at pci1 dev 10 function 0
> ahc0: interrupting at irq 10
> ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
> scsibus0 at ahc0 channel 0: 16 targets, 8 luns per target
> scsibus0: waiting 2 seconds for devices to settle...
> ahc0: target 5 using 8bit transfers
> ahc0: target 5 using asynchronous transfers
> st0 at scsibus0 target 5 lun 0: <HP, T4000s, 1.10> SCSI2 1/sequential removable
> st0: rogue, drive empty
> 
> ... with quirks as follows:
> 
> 	{{T_SEQUENTIAL, T_REMOV,
> 	 "HP      ", "T4000s          ", ""},     {ST_Q_UNIMODAL|ST_Q_NOPREVENT, 0, {
> 		{0, 0, QIC_3095},			/* minor 0-3 */
> 		{0, 0, QIC_3095},			/* minor 4-7 */
> 		{0, 0, QIC_3095},			/* minor 8-11 */
> 		{0, 0, QIC_3095},			/* minor 12-15 */
> 	}}},
> 
> I added the ST_Q_NOPREVENT code to the 1.5.2 st.c (revision 1.124.2.1)
> recently, but before that I had been using ADEV_NODOORLOCK to get the same
> effect, the device got pretty confused without it.
> 
> Normal dumps, even multi session dumps work fine, but recently I've been
> trying to perform multi-volume dumps of a filesystem...
> 
> Everything is fine until I insert the second tape: dump thinks it's already
> at the EOT and aborts (but it's certainly not, since I just rewound it).

Did you try 'mt eew' before dump ? I had to use this for multidumps on
hexabyte ...

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--