Date: Sun, 19 Jul 2009 13:56:25 -0700 (PDT) From: mahlerrd@yahoo.com To: freebsd-questions@freebsd.org Subject: Odd behavior after installing a tape drive Message-ID: <195035.41847.qm@web51008.mail.re2.yahoo.com>
next in thread | raw e-mail | index | archive | help
After installing a tape drive and SCSI card in my home system, I got some s= trange behavior that I think isn't directly related, but would like to get = an expert opinion about.=0A=0Amobius# uname -a=0AFreeBSD mobius 7.1-PRERELE= ASE FreeBSD 7.1-PRERELEASE #0: Fri Sep=A0 5 02:34:20 CDT 2008=A0 =A0=A0=A0r= ich@mobius:/usr/obj/usr/src/sys/GENERIC=A0 i386=0A=0AOn July 7, I turned of= f the system, installed the SCSI card, connected the drive and turned it al= l back on.=A0 This all got correctly detected as (select lines from /var/lo= g/messages):=0A=0AJul=A0 7 03:10:40 mobius kernel: asr0: <Adaptec Caching S= CSI RAID> mem 0xf4000000-0xf5ffffff irq 17 at device 12.1 on pci2=0AJul=A0 = 7 03:10:40 mobius kernel: asr0: [GIANT-LOCKED]=0AJul=A0 7 03:10:40 mobius k= ernel: asr0: [ITHREAD]=0AJul=A0 7 03:10:40 mobius kernel: asr0:=A0=A0=A0ADA= PTEC 2100S FW Rev. 370F, 1 channel, 256 CCBs, Protocol I2O=0AJul=A0 7 03:10= :40 mobius kernel: sa0 at asr0 bus 0 target 11 lun 0=0AJul=A0 7 03:10:40 mo= bius kernel: sa0: <EXABYTE VXA-172 3206> Removable Sequential Access SCSI-3= device=0A=0AI stuck in a tape, did a level 0 dump of /home and tested a re= store, both of which worked perfectly.=0A=0AOnly July 8, I ejected the tape= via the button on the front, and then turned off the tape drive so the vis= iting relatives wouldn't complain about the fan noise (more from /var/log/m= essages):=0AJul=A0 8 02:27:01 mobius kernel: (sa0:asr0:0:11:0): lost device= =0A=0AThat next week, I tried to SSH to this box from work to do some minor= random thing or another, and I got this sort of error message:=0AJul 14 15= :27:16 mobius sshd[64290]: error: openpty: Invalid argument=0AJul 14 15:27:= 16 mobius sshd[64293]: error: session_pty_req: session 0 alloc failed=0A=0A= I believe I had SSHed to it at least twice over the preceding week, on July= 10 and early in the day on July 14.=0A=0AAs the system was running perfect= ly in all other ways (well, at least the wife hadn't complained her network= files were offline, which is the only important thing!), it took a few day= s before I finally got around to logging in at the console and rebooting it= after which it has seemed to be fine. The system has been eminently stabl= e other than this one issue one time. =0A=0AI have not been able to find m= uch from Google about this other than the following two items-=0A=0AA) very= specific bugs against different SSH versions than I am using. Doubt this = is the problem.=0A=0AB) some issues some folks have had with needing to cre= ate /dev/pty or similar items. While it seems far fetched, this is the fir= st time the system was up with a new device and ... I don't know. New devi= ce in the system and an old device goes wonky within a week seems to be a b= it of a coincidence. =0A=0A** Does anyone have any thoughts if these are r= elated or not? **=0A=0AAlso, any tips, tricks or sites with working with t= ape drives on FreeBSD would be appreciated! (The handbook is a bit sparse = on this point and I'm used to autoloaders and better under Windows/Backup E= xec). I'm learning my way around camcontrol and mt, but should only need s= uch things in certain circumstances, like to get the tape drive "back" afte= r turning it off for a while, right?=0A=0A=0A=0A=0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?195035.41847.qm>