From owner-freebsd-current@FreeBSD.ORG Mon Aug 18 13:39:01 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 773B137B401 for ; Mon, 18 Aug 2003 13:39:01 -0700 (PDT) Received: from frost.ath.cx (BSN-95-242-77.dsl.siol.net [193.95.242.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC2D143FBF for ; Mon, 18 Aug 2003 13:38:59 -0700 (PDT) (envelope-from bfg@noviforum.si) Received: from MORDOR (mordor.lucky.si [192.168.200.250]) by frost.ath.cx (ESMTP) with SMTP id 37468A1 for ; Mon, 18 Aug 2003 22:39:16 +0200 (CEST) Message-ID: <003e01c365c8$b9a1a930$fac8a8c0@MORDOR> From: =?iso-8859-2?Q?Branko_F._Gra=E8nar?= To: Date: Mon, 18 Aug 2003 22:38:47 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: mksnap_ffs, snapshot issues, again X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 20:39:01 -0000 I have 900G array on a promise sx6000 controller This is freshly formatted filesystem (newfs -L export -O 2 -U -g 48000 = -i 2048 -m 0 -o space /dev/pst0s2d) # df -i /export /dev/pst0s2d 778742004 216194 778525810 0% 2 445159292 0% = /export # mount | grep export /dev/pst0s2d on /export (ufs, local, soft-updates) let's try to create a snapshot of empty filesystem # cd /export # mksnap_ffs /export aaa.snap ... after 30 minutes ... snapshot was not created (!!! On a empty = filesystem !!!)... Ok, long snapshot creation would be fine if it would = not hang all processes, which would like to do something on /export (ls = /export for example.). Filesystem cannot be unmounted. mksnap_ffs = process cannot be killed. Reboot and foreground fsck helps. This is 5.1-RELEASE (without patches, with custom kernel -> just picked = up generic kernel and removed uneeded stuff.).... Any ideas, why is this happening? As i mentioned before, this prevents = background fsck to make his job done (machine hangs.) I would really like to solve this issue.... Brane