Date: Fri, 21 Jan 2011 20:59:47 +0200 From: Alexander Motin <mav@FreeBSD.org> To: "G. Paul Ziemba" <pz-freebsd-scsi@ziemba.us>, freebsd-scsi@freebsd.org Subject: Re: rescan causes offlined tape to reload Message-ID: <4D39D7A3.7000304@FreeBSD.org> In-Reply-To: <mailpost.1295628140.241503.7070.mailing.freebsd.scsi@FreeBSD.cs.nctu.edu.tw> References: <mailpost.1295628140.241503.7070.mailing.freebsd.scsi@FreeBSD.cs.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
G. Paul Ziemba wrote: > mav@FreeBSD.org (Alexander Motin) writes: > >> G. Paul Ziemba wrote: > >>> # camcontrol rescan all >>> >>> Jan 20 21:08:40 hairball kernel: (probe4:sym0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 >>> Jan 20 21:08:44 hairball kernel: (probe4:sym0:0:4:0): LOAD UNLOAD. CDB: 1b 0 0 0 3 0 >>> Jan 20 21:09:34 hairball kernel: sym0:4:control msgout: 80 6. >>> Jan 20 21:09:34 hairball kernel: (probe4:sym0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 >>> Jan 20 21:09:34 hairball kernel: (probe4:sym0:0:4:0): INQUIRY. CDB: 12 0 0 0 24 0 >>> Jan 20 21:09:34 hairball kernel: (probe4:sym0:0:4:0): INQUIRY. CDB: 12 1 0 0 ff 0 >>> Jan 20 21:09:34 hairball kernel: (probe4:sym0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 >>> Jan 20 21:09:34 hairball kernel: (probe0:sym0:0:4:1): INQUIRY. CDB: 12 20 0 0 24 0 >>> Jan 20 21:09:34 hairball kernel: (probe0:sym0:0:4:2): INQUIRY. CDB: 12 40 0 0 24 0 >>> Jan 20 21:09:34 hairball kernel: (probe0:sym0:0:4:3): INQUIRY. CDB: 12 60 0 0 24 0 >>> Jan 20 21:09:34 hairball kernel: (probe0:sym0:0:4:4): INQUIRY. CDB: 12 80 0 0 24 0 >>> Jan 20 21:09:34 hairball kernel: (probe0:sym0:0:4:5): INQUIRY. CDB: 12 a0 0 0 24 0 >>> Jan 20 21:09:34 hairball kernel: (probe0:sym0:0:4:6): INQUIRY. CDB: 12 c0 0 0 24 0 >>> Jan 20 21:09:34 hairball kernel: (probe0:sym0:0:4:7): INQUIRY. CDB: 12 e0 0 0 24 0 > >> For the full picture it would be nice to see responses device sent. I >> suppose that in response to TUR device returns some status that implies >> tray closing/load. > > Yes, it would be useful/interesting to see the responses. I didn't > see a way to cause the responses to be logged - is there a tool/flag > to do it? Try set debug.bootverbose sysctl or boot with verbose kernel messages. Not sure about sense data, but it should give some more info. Proposed by Kenneth `camcontrol tur sa0 -v` should also help probably. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D39D7A3.7000304>