From owner-freebsd-fs@FreeBSD.ORG Wed Mar 8 18:29:21 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 3AD1716A420 for ; Wed, 8 Mar 2006 18:29:21 +0000 (GMT) (envelope-from pm940@yahoo.com) Received: from web54007.mail.yahoo.com (web54007.mail.yahoo.com [206.190.36.231]) by mx1.FreeBSD.org (Postfix) with SMTP id 5B61043D69 for ; Wed, 8 Mar 2006 18:29:19 +0000 (GMT) (envelope-from pm940@yahoo.com) Received: (qmail 69868 invoked by uid 60001); 8 Mar 2006 18:29:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bhyQiClToyFymYhJDu+OJcESSVrV+BJKG4ApRCjcvMYC4pzGFacFo2Q3lIUFzACgRdAWZd2PdJeGEtHCQl7+M2Vy8PB3aRrIuaquLlStdpgbSYg6B0EuJSrvBgPpi01pHhSUW3gXdL+U5fauAvtszzyj0ZoLl5RFAaF7cSjuUvY= ; Message-ID: <20060308182918.69866.qmail@web54007.mail.yahoo.com> Received: from [71.140.186.33] by web54007.mail.yahoo.com via HTTP; Wed, 08 Mar 2006 10:29:18 PST Date: Wed, 8 Mar 2006 10:29:18 -0800 (PST) From: Paul Marciano To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Getting EBUSY upon unmount ATA disk... 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: Wed, 08 Mar 2006 18:29:21 -0000 I am running FreeBSD-5.4 with root on md0. I am seeing the following problem: # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0 17370 15810 172 99% / devfs 1 1 0 100% /dev /dev/md1 3694 16 3384 0% /var /dev/md2 31470 8 28946 0% /tmp /dev/md3.uzipc 20808 18890 254 99% /usr # mount /dev/ad0s1a /flash # : > /flash/foobar # umount /flash umount: unmount of /flash failed: Device busy Waiting doesn't help. I can repeat the unmount command after a time and it still reports EBUSY. ad0 is a SanDisk Compact Flash card. So far I've traced the unmount op to ffs_flushfiles() in ffs_vfsops.c: /* * Flush all the files. */ if ((error = vflush(mp, 0, flags, td)) != 0) return (error); Still trying to track it down, but I'm not an fs guy and so I'm asking for a little help. Some more background: My system uses a Compact Flash card to store configuration information. It's seldom accessed and it would be nice to support controlled removing/replacing during operation. It looks like it is possible using atacontrol to detach the channel and then reattach when the card is inserted. I can: insert, attach, mount, read, umount, remove all day long without problems. But now as soon as I do one write the drive doesn't want to unmount. No processes are camping on the mount point. manually typing "sync" doesn't help. unmount -f succeeds. I hope someone can advise me. Thanks, Paul. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-fs@FreeBSD.ORG Wed Mar 8 18:52:45 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 B26CD16A422 for ; Wed, 8 Mar 2006 18:52:45 +0000 (GMT) (envelope-from pm940@yahoo.com) Received: from web54004.mail.yahoo.com (web54004.mail.yahoo.com [206.190.36.228]) by mx1.FreeBSD.org (Postfix) with SMTP id D380043D45 for ; Wed, 8 Mar 2006 18:52:44 +0000 (GMT) (envelope-from pm940@yahoo.com) Received: (qmail 71184 invoked by uid 60001); 8 Mar 2006 18:52:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=GLNbzRHxeUFGf8ryQdiwrxKVUmXJolt6VIhWraGzAEidAeMqd70e//fYMNTXS4tYtj7BCZ2QxitrJ8/9aXQbTCSEcICoBsDI4i7knnpsr2iS0Z2DKYx0DiOgRVZegeFKf2x3Uzlcw75hGNjIzccZSp3VsZmm7beI6ksVT26OXVs= ; Message-ID: <20060308185239.71182.qmail@web54004.mail.yahoo.com> Received: from [71.140.186.33] by web54004.mail.yahoo.com via HTTP; Wed, 08 Mar 2006 10:52:39 PST Date: Wed, 8 Mar 2006 10:52:39 -0800 (PST) From: Paul Marciano To: freebsd-questions@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Getting EBUSY upon unmount ATA disk... 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: Wed, 08 Mar 2006 18:52:45 -0000 I said: > # mount /dev/ad0s1a /flash > # : > /flash/foobar > # umount /flash > umount: unmount of /flash failed: Device busy Then I said: > No processes are camping on the mount point. I didn't realize /bin/sh doesn't close the fd. Man, I feel so dumb. Paul. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-fs@FreeBSD.ORG Wed Mar 8 23:55:22 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 6E87616A420 for ; Wed, 8 Mar 2006 23:55:22 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [69.43.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1889943D46 for ; Wed, 8 Mar 2006 23:55:22 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.12.11/8.12.11) with ESMTP id k28NtNq3037338 for ; Wed, 8 Mar 2006 15:55:23 -0800 (PST) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.12.11/8.12.11/Submit) with ESMTP id k28NtNc8037335 for ; Wed, 8 Mar 2006 15:55:23 -0800 (PST) (envelope-from john@kozubik.com) Date: Wed, 8 Mar 2006 15:55:23 -0800 (PST) From: John Kozubik To: freebsd-fs@freebsd.org Message-ID: <20060308151738.L55438@kozubik.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: UFS2 snapshots - comments requested 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: Wed, 08 Mar 2006 23:55:22 -0000 I just hung up a completely idle 6.0-RELEASE system by deleting a large number of files on a snapshotted filesystem (it had seven snapshots running on it). I have never seen snapshots work reliably in FreeBSD. I suspect that if you are using snapshots and they seem reliable, it is because you aren't doing much with them, or running enough of them. Since the first of the year, I have submitted two PRs detailing erratic behavior with snapshots: kern/92272 kern/92292 and these PRs only represent the behavior that I could isolate and define - I am regularly seeing system hangs resulting from any number of seemingly innocuous activities. My questions: - is this instability (circa 6.0) acknowledged ? - is there a large, known problem that, when fixed, will cause all of these little problems to go away, or should I keep submitting PRs when I verify misc. problems ? - can any visibility be offered as to the possible future viability of UFS2 snapshots in 6.0 ? Many thanks. ----- John Kozubik - john@kozubik.com - http://www.kozubik.com From owner-freebsd-fs@FreeBSD.ORG Thu Mar 9 00:28:53 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 54C5716A422 for ; Thu, 9 Mar 2006 00:28:53 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [69.43.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C137143D7B for ; Thu, 9 Mar 2006 00:28:51 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.12.11/8.12.11) with ESMTP id k290SrwG037682 for ; Wed, 8 Mar 2006 16:28:53 -0800 (PST) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.12.11/8.12.11/Submit) with ESMTP id k290SruO037679 for ; Wed, 8 Mar 2006 16:28:53 -0800 (PST) (envelope-from john@kozubik.com) Date: Wed, 8 Mar 2006 16:28:53 -0800 (PST) From: John Kozubik To: freebsd-fs@freebsd.org In-Reply-To: <20060308151738.L55438@kozubik.com> Message-ID: <20060308162731.P55438@kozubik.com> References: <20060308151738.L55438@kozubik.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: UFS2 snapshots - comments requested 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: Thu, 09 Mar 2006 00:28:53 -0000 On Wed, 8 Mar 2006, John Kozubik wrote: > My questions: > > - is this instability (circa 6.0) acknowledged ? > > - is there a large, known problem that, when fixed, will cause all of > these little problems to go away, or should I keep submitting PRs when I > verify misc. problems ? > > - can any visibility be offered as to the possible future viability of > UFS2 snapshots in 6.0 ? A quick follow-up - I forgot the most important question: - should these problems with UFS2 snapshots only concern me as regards uptime, or should I be concerned about data integrity as well ? Again, thanks. From owner-freebsd-fs@FreeBSD.ORG Thu Mar 9 22:09:35 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 1FC8A16A420 for ; Thu, 9 Mar 2006 22:09:35 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D26E843D49 for ; Thu, 9 Mar 2006 22:09:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id BCD871A4DA5; Thu, 9 Mar 2006 14:09:34 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0144D51CF4; Thu, 9 Mar 2006 17:09:33 -0500 (EST) Date: Thu, 9 Mar 2006 17:09:33 -0500 From: Kris Kennaway To: John Kozubik Message-ID: <20060309220933.GA97622@xor.obsecurity.org> References: <20060308151738.L55438@kozubik.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <20060308151738.L55438@kozubik.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 snapshots - comments requested 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: Thu, 09 Mar 2006 22:09:35 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 08, 2006 at 03:55:23PM -0800, John Kozubik wrote: > - is this instability (circa 6.0) acknowledged ? Yes > - is there a large, known problem that, when fixed, will cause all of > these little problems to go away, or should I keep submitting PRs when I > verify misc. problems ? >=20 > - can any visibility be offered as to the possible future viability of > UFS2 snapshots in 6.0 ? Recent (and near future) commits to RELENG_6 should help a lot, so 6.1-RELEASE will hopefully be (more) usable in this regard. Kris --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEEKedWry0BWjoQKURAtSqAJ4pPsqbmCEDhLQMNqStJMvRrW6zIgCgzEOn zJ9+QlP5kgb+fXpM9kFIGmM= =seYa -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 02:13:58 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 C548C16AB47 for ; Sat, 11 Mar 2006 02:13:55 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F35AC467E1 for ; Fri, 10 Mar 2006 16:07:31 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k2AG7UwS068713 for ; Fri, 10 Mar 2006 10:07:31 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4411A43E.5080500@centtech.com> Date: Fri, 10 Mar 2006 10:07:26 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1321/Thu Mar 9 22:54:15 2006 on mh2.centtech.com X-Virus-Status: Clean Subject: Snapshot ufs blocking 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: Sat, 11 Mar 2006 02:13:58 -0000 Since there's been some chatter about snapshots recently, I thought I'd give more snapshots a try along with some quick tests. I've recently updated my server to 6.1-PRERELEASE (as of yesterday), and am running happily. Now, for the snapshot information. While creating a snapshot (on a rather large 2tb volume that is 94% used), using: mksnap_ffs /vol1 /vol1/.snap/2006-03-10.snap I can move around /vol1, ls, df, etc. I can cd to /vol1/.snap/, and do an ls, and the snapshot continues just fine. However, as soon as I do a ls -al against the /vol1/.snap/2006-03-10.snap file (in this case, my cwd is /vol1/.snap/ and I do an ls -al), the ls blocks on ufs, and then subsequent ls -al's of the root (/), the partition (/vol1/), all block in 'ufs'. Also, once this has happened, my mksnap_ffs stops, also blocked in 'ufs', and my ls's don't return (I've only waited about 20 minutes though). I could see the stat on the snapshot file itself blocking, but the rest of the system shouldn't block, should it? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 04:37:08 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 C097116A432 for ; Sat, 11 Mar 2006 04:37:08 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90A7943D69 for ; Sat, 11 Mar 2006 04:37:00 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 1DF291A4D82; Fri, 10 Mar 2006 20:37:00 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id EF88C51601; Fri, 10 Mar 2006 23:36:58 -0500 (EST) Date: Fri, 10 Mar 2006 23:36:58 -0500 From: Kris Kennaway To: Eric Anderson Message-ID: <20060311043658.GA39298@xor.obsecurity.org> References: <4411A43E.5080500@centtech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline In-Reply-To: <4411A43E.5080500@centtech.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org Subject: Re: Snapshot ufs blocking 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: Sat, 11 Mar 2006 04:37:08 -0000 --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 10, 2006 at 10:07:26AM -0600, Eric Anderson wrote: > Since there's been some chatter about snapshots recently, I thought I'd= =20 > give more snapshots a try along with some quick tests.=20 Per my message yesterday, not all known snapshot bugs are fixed in 6.x yet. Kris --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEElPqWry0BWjoQKURAsKTAJ9VzgoLtw+r/mIPBT14d8JkrC92GgCgphSf lWAvHyL0W+e1fszCIxXGz10= =TOEK -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 04:52:22 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 4137D16A41F for ; Sat, 11 Mar 2006 04:52:22 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC98643D53 for ; Sat, 11 Mar 2006 04:52:19 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.22] (andersonbox2.centtech.com [192.168.42.22]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k2B4qHZw084654; Fri, 10 Mar 2006 22:52:17 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4412576E.2030505@centtech.com> Date: Fri, 10 Mar 2006 22:51:58 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Kris Kennaway References: <4411A43E.5080500@centtech.com> <20060311043658.GA39298@xor.obsecurity.org> In-Reply-To: <20060311043658.GA39298@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1323/Fri Mar 10 18:22:41 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: Snapshot ufs blocking 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: Sat, 11 Mar 2006 04:52:22 -0000 Kris Kennaway wrote: > On Fri, Mar 10, 2006 at 10:07:26AM -0600, Eric Anderson wrote: > >> Since there's been some chatter about snapshots recently, I thought I'd >> give more snapshots a try along with some quick tests. >> > > Per my message yesterday, not all known snapshot bugs are fixed in 6.x > yet. > Right - I was expecting that. I'm mostly trying to offer some details on what is not working - if this is already clearly known, and no further debugging is needed, then I'll drift off into silence. However, if more debugging is needed, including dumps, etc, I can provide those, as I have a real 2TB volume essentially empty I can do hard testing on during daytime hours right now. I'm certainly not complaining - just trying to help in the way that I can. Eric From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 05:32:04 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 0608016A41F for ; Sat, 11 Mar 2006 05:32:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D41743D64 for ; Sat, 11 Mar 2006 05:32:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0F4DE1A4D7A; Fri, 10 Mar 2006 21:32:02 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 322FE51601; Sat, 11 Mar 2006 00:32:01 -0500 (EST) Date: Sat, 11 Mar 2006 00:32:01 -0500 From: Kris Kennaway To: Eric Anderson Message-ID: <20060311053201.GB40172@xor.obsecurity.org> References: <4411A43E.5080500@centtech.com> <20060311043658.GA39298@xor.obsecurity.org> <4412576E.2030505@centtech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GRPZ8SYKNexpdSJ7" Content-Disposition: inline In-Reply-To: <4412576E.2030505@centtech.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: Snapshot ufs blocking 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: Sat, 11 Mar 2006 05:32:04 -0000 --GRPZ8SYKNexpdSJ7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 10, 2006 at 10:51:58PM -0600, Eric Anderson wrote: > Kris Kennaway wrote: > >On Fri, Mar 10, 2006 at 10:07:26AM -0600, Eric Anderson wrote: > > =20 > >>Since there's been some chatter about snapshots recently, I thought I'd= =20 > >>give more snapshots a try along with some quick tests.=20 > >> =20 > > > >Per my message yesterday, not all known snapshot bugs are fixed in 6.x > >yet. > > =20 >=20 > Right - I was expecting that. I'm mostly trying to offer some details=20 > on what is not working - if this is already clearly known, and no=20 > further debugging is needed, then I'll drift off into silence. However,= =20 > if more debugging is needed, including dumps, etc, I can provide those,= =20 > as I have a real 2TB volume essentially empty I can do hard testing on=20 > during daytime hours right now. >=20 > I'm certainly not complaining - just trying to help in the way that I can. Thanks. There is an uncommitted patch being circulated that is believed to address all remaining problems. It relies on other fixes in -CURRENT that are not yet merged, but if you're able to test it let me know and I'll forward. Kris --GRPZ8SYKNexpdSJ7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEEmDQWry0BWjoQKURAqjcAJ9VgnXuvxqBouH1GbGwDH9q5gDbHwCgs4zJ KsDAL42Nxj+rTyyfkR0kD14= =1See -----END PGP SIGNATURE----- --GRPZ8SYKNexpdSJ7-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 08:49:52 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 3EE0B16A41F for ; Sat, 11 Mar 2006 08:49:52 +0000 (GMT) (envelope-from genie@geniechka.ru) Received: from turists.ru (turists.ru [83.222.5.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99E6943D46 for ; Sat, 11 Mar 2006 08:49:49 +0000 (GMT) (envelope-from genie@geniechka.ru) Received: from genie (genie.yauza.ru [85.192.18.27]) (authenticated bits=0) by turists.ru (8.13.1/8.13.1) with ESMTP id k2B8nkn7046807 for ; Sat, 11 Mar 2006 11:49:46 +0300 (MSK) (envelope-from genie@geniechka.ru) X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.2.02271, virus records: 105810, updated: 10.02.2006] Message-ID: <004c01c644e8$c05c8c70$1b12c055@genie> From: "Eugene" To: Date: Sat, 11 Mar 2006 11:49:26 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Dump/snapshot problems 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: Sat, 11 Mar 2006 08:49:52 -0000 Hi people, Sometimes I have strange problems with dump -- or, rather, with snapshot it makes. System is FreeBSD 5.3, default kernel configuration Two types of problems: 1) System hangs or at least not accessible over the network and has to be physically reset. Last message on console Collecting pv entries -- suggest increasing PMAP_SHPGPERPROó maxproc limit exceeded by id(0), please see tuning(7) and login.conf(5) Question: what exactly should I tune? 2) Dump process dies with message mksnap_ffs: Cannot create //.snap/dump_snapshot: Resource temporarily unavailable dump: Cannot create //.snap/dump_snapshot: No such file or directory dmesg message fsync: giving up on dirty: 0xc57b5d68: tag devfs, type VCHR, usecount 60263, writecount 0, refcount 960, flags (VV_OBJBUF), lock type devfs: EXCL (count 1) by thread 0xc610f7d0 (pid 87575) dev ad4s1a What is wrong? What is '0xc57b5d68' (number is repeating)? Thanks in advance Eugene From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 09:05:38 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 503E016A427 for ; Sat, 11 Mar 2006 09:05:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4068443D45 for ; Sat, 11 Mar 2006 09:05:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 1F0E81A4D83; Sat, 11 Mar 2006 01:05:34 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0D52851743; Sat, 11 Mar 2006 04:05:33 -0500 (EST) Date: Sat, 11 Mar 2006 04:05:32 -0500 From: Kris Kennaway To: Eugene Message-ID: <20060311090532.GA43378@xor.obsecurity.org> References: <004c01c644e8$c05c8c70$1b12c055@genie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: <004c01c644e8$c05c8c70$1b12c055@genie> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org Subject: Re: Dump/snapshot problems 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: Sat, 11 Mar 2006 09:05:38 -0000 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 11, 2006 at 11:49:26AM +0300, Eugene wrote: > Hi people, >=20 > Sometimes I have strange problems with dump -- or, rather, with snapshot = it > makes. > System is FreeBSD 5.3, default kernel configuration >=20 > Two types of problems: > 1) System hangs or at least not accessible over the network and has to be > physically reset. Last message on console > Collecting pv entries -- suggest increasing PMAP_SHPGPERPRO? > maxproc limit exceeded by id(0), please see tuning(7) and login.conf(5) >=20 > Question: what exactly should I tune? The value of PMAP_SHPGPERPROC in your kernel config, and the maxproc limit as described in those two manpages. > 2) Dump process dies with message > mksnap_ffs: Cannot create //.snap/dump_snapshot: Resource temporarily > unavailable > dump: Cannot create //.snap/dump_snapshot: No such file or directory >=20 > dmesg message > fsync: giving up on dirty: 0xc57b5d68: tag devfs, type VCHR, usecount 602= 63, > writecount 0, refcount 960, flags (VV_OBJBUF), lock type devfs: EXCL > (count 1) by thread 0xc610f7d0 (pid 87575) > dev ad4s1a >=20 > What is wrong? What is '0xc57b5d68' (number is repeating)? You can ignore the fsync message, it's a side-effect of the snapshot operation not succeeding. Just retry the dump. Kris --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEEpLcWry0BWjoQKURAij0AKDUC1sX92Gg3ikvCff9Hd46nuuRBwCgld08 9hb/qo+AP1vthTkXj7c2u5A= =f3S3 -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 09:37:31 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 1C8AB16A41F for ; Sat, 11 Mar 2006 09:37:31 +0000 (GMT) (envelope-from genie@geniechka.ru) Received: from turists.ru (turists.ru [83.222.5.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 721FE43D45 for ; Sat, 11 Mar 2006 09:37:27 +0000 (GMT) (envelope-from genie@geniechka.ru) Received: from genie (genie.yauza.ru [85.192.18.27]) (authenticated bits=0) by turists.ru (8.13.1/8.13.1) with ESMTP id k2B9bPVH057672; Sat, 11 Mar 2006 12:37:25 +0300 (MSK) (envelope-from genie@geniechka.ru) X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.2.02271, virus records: 105810, updated: 10.02.2006] Message-ID: <001e01c644ef$68a76070$1b12c055@genie> From: "Eugene" To: "Kris Kennaway" References: <004c01c644e8$c05c8c70$1b12c055@genie> <20060311090532.GA43378@xor.obsecurity.org> Date: Sat, 11 Mar 2006 12:37:03 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: freebsd-fs@freebsd.org Subject: Re: Dump/snapshot problems 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: Sat, 11 Mar 2006 09:37:31 -0000 Hi! ----- Original Message ----- From: "Kris Kennaway" To: "Eugene" Cc: Sent: Saturday, March 11, 2006 12:05 Subject: Re: Dump/snapshot problems > > 1) System hangs or at least not accessible over the network and has to > > be > > physically reset. Last message on console > > Collecting pv entries -- suggest increasing PMAP_SHPGPERPRO? > > maxproc limit exceeded by id(0), please see tuning(7) and login.conf(5) > > Question: what exactly should I tune? > > The value of PMAP_SHPGPERPROC in your kernel config, and the maxproc > limit as described in those two manpages. Well, I can read -) I would like to know why it fails in virtually unloaded system (except for dump) and what parameters/values _in particular_ should be tweaked. > > 2) Dump process dies with message > > mksnap_ffs: Cannot create //.snap/dump_snapshot: Resource temporarily > > unavailable > > dump: Cannot create //.snap/dump_snapshot: No such file or directory > > > > dmesg message > > fsync: giving up on dirty: 0xc57b5d68: tag devfs, type VCHR, usecount > > 60263, > > writecount 0, refcount 960, flags (VV_OBJBUF), lock type devfs: EXCL > > (count 1) by thread 0xc610f7d0 (pid 87575) > > dev ad4s1a > > > > What is wrong? What is '0xc57b5d68' (number is repeating)? > You can ignore the fsync message, it's a side-effect of the snapshot > operation not succeeding. Just retry the dump. That's very comforting but why is it not succeding? And I would really like the dump to work automatically (as it did for more than a year before these problems started to appear recently). Eugene From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 09:45:45 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 9742316A41F for ; Sat, 11 Mar 2006 09:45:45 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5523043D45 for ; Sat, 11 Mar 2006 09:45:45 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 37B4A1A4D87; Sat, 11 Mar 2006 01:45:45 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 474B4515BE; Sat, 11 Mar 2006 04:45:44 -0500 (EST) Date: Sat, 11 Mar 2006 04:45:44 -0500 From: Kris Kennaway To: Eugene Message-ID: <20060311094543.GA43910@xor.obsecurity.org> References: <004c01c644e8$c05c8c70$1b12c055@genie> <20060311090532.GA43378@xor.obsecurity.org> <001e01c644ef$68a76070$1b12c055@genie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <001e01c644ef$68a76070$1b12c055@genie> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: Dump/snapshot problems 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: Sat, 11 Mar 2006 09:45:45 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 11, 2006 at 12:37:03PM +0300, Eugene wrote: > Hi! >=20 > ----- Original Message -----=20 > From: "Kris Kennaway" > To: "Eugene" > Cc: > Sent: Saturday, March 11, 2006 12:05 > Subject: Re: Dump/snapshot problems >=20 > >> 1) System hangs or at least not accessible over the network and has to= =20 > >> be > >> physically reset. Last message on console > >> Collecting pv entries -- suggest increasing PMAP_SHPGPERPRO? > >> maxproc limit exceeded by id(0), please see tuning(7) and login.conf(5) > >> Question: what exactly should I tune? > > > >The value of PMAP_SHPGPERPROC in your kernel config, and the maxproc > >limit as described in those two manpages. >=20 > Well, I can read -) I would like to know why it fails in virtually unload= ed=20 > system (except for dump) and what parameters/values _in particular_ shoul= d=20 > be tweaked. See the NOTES file for discussion of the former, and please read the manpages. > >You can ignore the fsync message, it's a side-effect of the snapshot > >operation not succeeding. Just retry the dump. >=20 > That's very comforting but why is it not succeding? And I would really li= ke=20 > the dump to work automatically (as it did for more than a year before the= se=20 > problems started to appear recently). I don't know. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEEpxHWry0BWjoQKURArO1AKD9EBOb+OhnRFnc+UOnV+n5H8HKQACg8rRV Eq4bRt3qPaQs1Z4SaJ2bcrs= =O4x1 -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--