From owner-freebsd-fs@FreeBSD.ORG Tue Sep 5 08:50:57 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA3B216A4DD for ; Tue, 5 Sep 2006 08:50:57 +0000 (UTC) (envelope-from db@spearburn.danielbond.org) Received: from spearburn.danielbond.org (ti221110a080-2410.bb.online.no [83.109.137.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4D1443D4C for ; Tue, 5 Sep 2006 08:50:56 +0000 (GMT) (envelope-from db@spearburn.danielbond.org) Received: by spearburn.danielbond.org (Postfix, from userid 1001) id 022605C49; Tue, 5 Sep 2006 10:53:27 +0200 (CEST) Date: Tue, 5 Sep 2006 10:53:27 +0200 From: Daniel Bond To: freebsd-fs@freebsd.org Message-ID: <20060905085327.GA6405@spearburn.danielbond.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GPG-Key-Id: 37898D6C X-GPG-Key-Server: http://pgp.mit.edu X-GPG-Key-FingerPrint: DA2F 6D5F 052B 0180 6E12 F62D 85E6 9276 59CC E5B6 User-Agent: mutt-ng/devel-r804 (FreeBSD) Subject: UFS/mksnap/softupdates deadlock issue X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2006 08:50:57 -0000 Hi, anyone know the status of this? http://www.mail-archive.com/freebsd-stable@freebsd.org/msg74035.html Every system we have after RELENG_5 has a issue with mksnap (dump/fsck) on UFS2-partitions larger than say 800GB. This means we cannot use dump, which is our main backup-strategy, and we have to fsck in single-user mode if theese systems for some reason crash. This happens via ATA/SCSI-CAM/SCSI-NONCAM (like ServeRaid). I have seen many other users having issues with this, even big companies like UPS, and quite frankly I am a little suprised that it still exists in 6.1-RELEASE. How to reproduce: run dump/fsck on live filesystem, ufs2 with softupdates over 800GB (I think arround 600GB is enough, but I'm certain with 800GB). What happens: A deadlock like Tor Egge describes in his post above. The company I work for has been using FreeBSD for more than 10 years, and we are supprised how stable and easy to administrate it is. It's a really great OS and we love it, but lately we have had to turn to commersial Linux vendors (SuSE) for storage servers due to this issue. We are all using it against our will. If anyone needs a enviroment for testing/reproducing this error, I can setup our old storage server her, and give access to any freebsd commiter. If anyone knows a patch/sollution to this, please let me know, and I will report back results. I have not yet tested if this problem exists in 7-Current, but I could if anyone wants me too. -- Med vennlig hilsen / Best regards, ------------------------------------------ Daniel Bond PGP: C822C4BD ------------------------------------------