From owner-freebsd-current@FreeBSD.ORG Fri May 9 11:54:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D994337B401 for ; Fri, 9 May 2003 11:54:03 -0700 (PDT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 0511243FBF for ; Fri, 9 May 2003 11:54:02 -0700 (PDT) (envelope-from me@farid-hajji.de) Received: (qmail 25889 invoked by uid 505); 9 May 2003 18:54:06 -0000 Received: from me@farid-hajji.de by dsl-mail by uid 502 with qmail-scanner-1.14 (spamassassin: 2.43. Clear:. Processed in 0.190976 secs); 09 May 2003 18:54:06 -0000 Received: from unknown (HELO reverse-213-146-115-183.dialin.kamp-dsl.de) (213.146.115.183) by dsl-mail.kamp.net with SMTP; 9 May 2003 18:54:06 -0000 From: Farid Hajji To: freebsd-current@freebsd.org Date: Fri, 9 May 2003 20:54:32 +0200 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305092054.32885.me@farid-hajji.de> Subject: Lockups with dump(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: me@farid-hajji.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2003 18:54:04 -0000 I can nearly reliably crash 5.1-BETA #2: Fri May 9 19:46:44 CEST 2003 when using dump(8) like this: # dump -0aun -L -f - /usr | gzip2 | \ > ssh -c blowfish voyager@dumphost.domain.tld \ > dd of=/dumps/voyager/usr-fs.l0.gz Somewhere between 10% and 80% of the dump, this message pops up: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. and the system locks up. I cannot switch consoles, but can still ping the box from the outside. This doesn't happen on smaller filesystems like / or /var, only with /usr (and here only in approx. 95% of cases). It does happen in multiuser _and_ singleuser mode. I've fsck -f all filesystems before. There is only one disk on ata0, nothing more. I've swapped drives, controllers and motherboards. Same problem on all machines. -Farid. -- Farid Hajji -- Unix Systems and Network Management. http://www.farid-hajji.net/address.html Quoth the Raven, "Nevermore." --Edgar Allan Poe.