From owner-freebsd-scsi Sun Jul 1 13:48:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from guru.mired.org (okc-27-141-144.mmcable.com [24.27.141.144]) by hub.freebsd.org (Postfix) with SMTP id 79EAC37B405 for ; Sun, 1 Jul 2001 13:48:07 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 12867 invoked by uid 100); 1 Jul 2001 20:48:06 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15167.35974.774198.722692@guru.mired.org> Date: Sun, 1 Jul 2001 15:48:06 -0500 To: "Jamil Taylor" Cc: scsi@freebsd.org Subject: RE: System Hang During tar Backup In-Reply-To: References: X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [Moved from -stable to -scsi, as that seems to be where the problem is.] Jamil Taylor types: > I attempted this one more time and got it to work. What I had to do this > time was reboot the machine in single user mode. I entered the following > commands after pressing space during boot: > > unload > load kernel > boot -s > > After boot, I mounted all drives and successfully used tar to backup all > files. I used the same tar syntax, with the exception of running it verbose. > > If I now have to use tar in single user mode, so be it. I did not have to do > this previously though. Having updated today - or rather tried to - I'm now seeing similar problems. Keyboard input is obviously active, and the console driver will let me switch virtual ttys, but no user processes seem to be getting any cpu. There's no tape drive involved in freezing the system, just disk activity across multiple devices on the controller. In particular, I've got: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) attached to: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 10 at device 14.0 on pci0 I can get it to freeze reliably - meaning every time I tried to start X - on a kernel supped earlier today, wherease the one from June 24th has no problems. I've got a debugging kernel built, but don't know if I'll have time to do any work on this in the next two weeks. I should be dealing with email, though. James, you might report your hardware configuration as well. -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Jamil Taylor > Sent: Saturday, June 30, 2001 1:43 PM > To: stable@FreeBSD.ORG > Subject: System Hang During tar Backup > > > I am encountering a problem when using tar to backup the files on my system. > I am uncertain of when this problem began, but this worked a month ago. The > backup seems to run for at least ten minutes, but the system seems to hang > after a period of time. Keyboard input appears on the screen, but control-C > has no effect. Control-Alt-Delete has no effect either, and my only option > is to press the reset button or power down the machine. No services are > active when the system is in this state (i.e., I cannot make a remote > connection to the machine). > > I am running 4.3-STABLE that was built after a cvsup of RELENG_4 as of > yesterday. > > I am using the following syntax: > > tar --create --totals --absolute-paths --file /dev/rsa0 / > > My hardware is a Seagate Scorpion STD2401LW. This is a DDS4 DAT drive. > > Is anyone else experiencing a similar problem? > > Thanks. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Mike Meyer http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message