From owner-freebsd-fs@FreeBSD.ORG Sun Sep 13 16:09:43 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 186DC106568D; Sun, 13 Sep 2009 16:09:43 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E354C8FC15; Sun, 13 Sep 2009 16:09:42 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8DG9g8N097037; Sun, 13 Sep 2009 16:09:42 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8DG9gop097033; Sun, 13 Sep 2009 16:09:42 GMT (envelope-from pjd) Date: Sun, 13 Sep 2009 16:09:42 GMT Message-Id: <200909131609.n8DG9gop097033@freefall.freebsd.org> To: info-gentoo@mark.thompson.bz, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/118320: [zfs] [patch] NFS SETATTR sometimes fails to set file mode on ZFS partition 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: Sun, 13 Sep 2009 16:09:43 -0000 Synopsis: [zfs] [patch] NFS SETATTR sometimes fails to set file mode on ZFS partition State-Changed-From-To: open->feedback State-Changed-By: pjd State-Changed-When: ndz 13 wrz 2009 16:08:52 UTC State-Changed-Why: Is this still a problem with FreeBSD 8? Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: ndz 13 wrz 2009 16:08:52 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=118320 From owner-freebsd-fs@FreeBSD.ORG Sun Sep 13 16:28:32 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D54631065693; Sun, 13 Sep 2009 16:28:32 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AC0328FC36; Sun, 13 Sep 2009 16:28:32 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8DGSWnK017070; Sun, 13 Sep 2009 16:28:32 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8DGSWxq017066; Sun, 13 Sep 2009 16:28:32 GMT (envelope-from pjd) Date: Sun, 13 Sep 2009 16:28:32 GMT Message-Id: <200909131628.n8DGSWxq017066@freefall.freebsd.org> To: james-freebsd-current@jrv.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/138709: [zfs] zfs recv hangs, pool accesses hang in rrl->rr_cv state 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: Sun, 13 Sep 2009 16:28:32 -0000 Synopsis: [zfs] zfs recv hangs, pool accesses hang in rrl->rr_cv state State-Changed-From-To: closed->feedback State-Changed-By: pjd State-Changed-When: ndz 13 wrz 2009 16:26:24 UTC State-Changed-Why: I don't think it hasanything to do with kern/138220. This would be great if you could provide a way to reproduce this. It might be related to one of my recent commits. Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: ndz 13 wrz 2009 16:26:24 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=138709 From owner-freebsd-fs@FreeBSD.ORG Sun Sep 13 18:13:09 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67118106566B; Sun, 13 Sep 2009 18:13:09 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 069228FC0C; Sun, 13 Sep 2009 18:13:08 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjIFAEfTrEqDaFvG/2dsb2JhbACQPgHHcoQYBYFW X-IronPort-AV: E=Sophos;i="4.44,379,1249272000"; d="scan'208";a="46123651" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 13 Sep 2009 14:13:08 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id F1E2C2100BD; Sun, 13 Sep 2009 14:13:07 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOc3nrfEjsKu; Sun, 13 Sep 2009 14:13:07 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 303A721009D; Sun, 13 Sep 2009 14:13:07 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8DIIPf17114; Sun, 13 Sep 2009 14:18:25 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Sun, 13 Sep 2009 14:18:25 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, qing.li@bluecoat.com Subject: NFS client defaults to a mix of UDP and TCP 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: Sun, 13 Sep 2009 18:13:09 -0000 I had thought that I had posted w.r.t. before, but can't find it in the archive (which might explain why I didn't get any responses:-). The current mount_nfs defaults to using UDP for the mount protocol and then switches to using TCP for the actual mount. (When neither "udp" nor "tcp" mount options are specified.) I don't think I changed it to be this way, because I recall noticing it when I added changes for the experimental NFS client and thought it was "weird", but assumed that it had been that way for a long time. It now appears that it was introduced post-FreeBSD7 at r176198, which changed the default for NFS to TCP, but didn't switch the default for the mount protocol to TCP. The ancient history of this is that "once upon a time" there were NFS servers that could do NFS over TCP, but only supported UDP for the mount protocol and there was an option called "mntudp" for that case. I can't imagine that any server still needs this case, but it appears to have become the default. The default works fine for servers that support both UDP and TCP, but result in a non-functional mount point when the server only supports UDP. (See recent email thread on freebsd-stable called "NFS issues on 8.0-BETA4".) Is this something that should be changed? rick From owner-freebsd-fs@FreeBSD.ORG Sun Sep 13 20:24:02 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A598A106568B for ; Sun, 13 Sep 2009 20:24:02 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id 3EFDB8FC0C for ; Sun, 13 Sep 2009 20:24:01 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 8275945CA6; Sun, 13 Sep 2009 22:24:00 +0200 (CEST) Received: from localhost (chello087206049004.chello.pl [87.206.49.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 8002945C9C for ; Sun, 13 Sep 2009 22:23:55 +0200 (CEST) Date: Sun, 13 Sep 2009 22:23:50 +0200 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20090913202350.GE2091@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xJK8B5Wah2CMJs8h" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: Subject: Review request for NFS readdirplus change. 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: Sun, 13 Sep 2009 20:24:02 -0000 --xJK8B5Wah2CMJs8h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. I'm looking for a review of the following patch: http://people.freebsd.org/~pjd/patches/nfs_serv.c.3.patch The main purpose of this patch is to support stuff like ZFS, where using VFS_VGET() might be tricky on .zfs/ directory and friends. When VFS_VGET() is not supported be the underlying file system, we switch to VOP_LOOKUP(). Note that OpenSolaris NFS server implementation always uses lookup for readdirplus. I also modified the code to use shared-locking, there is no need to exclusively lock the vnodes. The patch removes an assert which doesn't hold for ZFS when we go into =2Ezfs/snapshot// directory, which is separate mount point, but we don't want to export it separately, so we still return it on lookup. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --xJK8B5Wah2CMJs8h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKrVTWForvXbEpPzQRApcpAKCjYe9Fx6bqf04Ox7DhNUEfnwgKyACfQHe+ EccHmQhVFlUAxYn7OY3KaNI= =IrPL -----END PGP SIGNATURE----- --xJK8B5Wah2CMJs8h-- From owner-freebsd-fs@FreeBSD.ORG Sun Sep 13 21:32:27 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E92061065679; Sun, 13 Sep 2009 21:32:27 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BF1698FC16; Sun, 13 Sep 2009 21:32:27 +0000 (UTC) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8DLWR6g025978; Sun, 13 Sep 2009 21:32:27 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8DLWRT7025974; Sun, 13 Sep 2009 21:32:27 GMT (envelope-from gavin) Date: Sun, 13 Sep 2009 21:32:27 GMT Message-Id: <200909132132.n8DLWRT7025974@freefall.freebsd.org> To: klaas@kite.ping.de, gavin@FreeBSD.org, gavin@FreeBSD.org, freebsd-fs@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/112640: [ext2fs] [hang] Kernel freezes when writing a file to an ex2fs filesystem on a usb 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: Sun, 13 Sep 2009 21:32:28 -0000 Old Synopsis: [usb] [ext2fs] [hang] Kernel freezes when writing a file to an ex2fs filesystem on a usb disk New Synopsis: [ext2fs] [hang] Kernel freezes when writing a file to an ex2fs filesystem on a usb disk State-Changed-From-To: feedback->open State-Changed-By: gavin State-Changed-When: Sun Sep 13 21:31:16 UTC 2009 State-Changed-Why: Submitter has provided feedback. The problem still exists on 7.2, and USB has been ruled out. Responsible-Changed-From-To: gavin->freebsd-fs Responsible-Changed-By: gavin Responsible-Changed-When: Sun Sep 13 21:31:16 UTC 2009 Responsible-Changed-Why: Over to maintaner(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=112640 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 06:39:32 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C4BE1065670; Mon, 14 Sep 2009 06:39:32 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 72BA48FC13; Mon, 14 Sep 2009 06:39:32 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8E6dWXm072596; Mon, 14 Sep 2009 06:39:32 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8E6dVbd072592; Mon, 14 Sep 2009 06:39:31 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 06:39:31 GMT Message-Id: <200909140639.n8E6dVbd072592@freefall.freebsd.org> To: eso3@mail.ru, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/128514: [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Adapter 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: Mon, 14 Sep 2009 06:39:32 -0000 Synopsis: [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Adapter State-Changed-From-To: open->feedback State-Changed-By: pjd State-Changed-When: pon 14 wrz 2009 06:38:38 UTC State-Changed-Why: Could you try adding vfs.zfs.cache_flush_disable=1 to your /boot/loader.conf and see i that helps? It will prevent ZFS from sending write flush requests to the disks. Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: pon 14 wrz 2009 06:38:38 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=128514 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 07:03:32 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BA391065672; Mon, 14 Sep 2009 07:03:32 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5270E8FC14; Mon, 14 Sep 2009 07:03:32 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8E73VNU000592; Mon, 14 Sep 2009 07:03:32 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8E73VH1000588; Mon, 14 Sep 2009 07:03:31 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 07:03:31 GMT Message-Id: <200909140703.n8E73VH1000588@freefall.freebsd.org> To: swell.k@gmail.com, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/129148: [zfs] [panic] panic on concurrent writing & rollback 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: Mon, 14 Sep 2009 07:03:32 -0000 Synopsis: [zfs] [panic] panic on concurrent writing & rollback State-Changed-From-To: open->patched State-Changed-By: pjd State-Changed-When: pon 14 wrz 2009 07:02:21 UTC State-Changed-Why: I believe it is already fixed in HEAD. Could you verify? If you can't try HEAD, it sould be in 8 soon. Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: pon 14 wrz 2009 07:02:21 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=129148 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 08:08:18 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 655E91065693; Mon, 14 Sep 2009 08:08:18 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3DAF98FC0A; Mon, 14 Sep 2009 08:08:18 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8E88GBH089786; Mon, 14 Sep 2009 08:08:16 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8E88GlL089782; Mon, 14 Sep 2009 08:08:16 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 08:08:16 GMT Message-Id: <200909140808.n8E88GlL089782@freefall.freebsd.org> To: james-freebsd-current@jrv.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/138656: [zfs] [panic] ZFS panic "lock &arg.lock already initialized" during zfs recv 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: Mon, 14 Sep 2009 08:08:18 -0000 Synopsis: [zfs] [panic] ZFS panic "lock &arg.lock already initialized" during zfs recv State-Changed-From-To: open->closed State-Changed-By: pjd State-Changed-When: pon 14 wrz 2009 08:01:07 UTC State-Changed-Why: Duplicate of kern/135480. Problem already fixed in HEAD. Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: pon 14 wrz 2009 08:01:07 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=138656 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 11:06:59 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04C8F106568B for ; Mon, 14 Sep 2009 11:06:59 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E6F268FC1C for ; Mon, 14 Sep 2009 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8EB6wpP072312 for ; Mon, 14 Sep 2009 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8EB6w7u072308 for freebsd-fs@FreeBSD.org; Mon, 14 Sep 2009 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Sep 2009 11:06:58 GMT Message-Id: <200909141106.n8EB6w7u072308@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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: Mon, 14 Sep 2009 11:06:59 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/138764 fs [zfs] [panic] ZFS panic: "panic: dirtying snapshot!" o kern/138524 fs [msdosfs] disks and usb flashes/cards with Russian lab o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138367 fs [tmpfs] [panic] 'panic: Assertion pages > 0 failed' wh o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/138109 fs [extfs] [patch] Minor cleanups to the sys/gnu/fs/ext2f f kern/137037 fs [zfs] [hang] zfs rollback on root causes FreeBSD to fr o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic o kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/136218 fs [zfs] Exported ZFS pools can't be imported into (Open) o kern/135594 fs [zfs] Single dataset unresponsive with Samba o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o bin/135314 fs [zfs] assertion failed for zdb(8) usage o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot f kern/134496 fs [zfs] [panic] ZFS pool export occasionally causes a ke o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133980 fs [panic] [ffs] panic: ffs_valloc: dup alloc o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [smbfs] [panic] panic: ffs_truncate: read-only filesys o kern/133373 fs [zfs] umass attachment causes ZFS checksum errors, dat o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132597 fs [tmpfs] [panic] tmpfs-related panic while interrupting o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes f kern/132068 fs [zfs] page fault when using ZFS over NFS on 7.1-RELEAS o kern/131995 fs [nfs] Failure to mount NFSv4 server o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/131086 fs [ext2fs] [patch] mkfs.ext2 creates rotten partition o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129059 fs [zfs] [patch] ZFS bootloader whitelistable via WITHOUT f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127659 fs [tmpfs] tmpfs memory leak o kern/127492 fs [zfs] System hang on ZFS input-output o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/125644 fs [zfs] [panic] zfs unfixable fs errors caused panic whe f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o kern/122047 fs [ext2fs] [patch] incorrect handling of UF_IMMUTABLE / o kern/122038 fs [tmpfs] [panic] tmpfs: panic: tmpfs_alloc_vp: type 0xc o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F f kern/119735 fs [zfs] geli + ZFS + samba starting on boot panics 7.0-B o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o kern/116913 fs [ffs] [panic] ffs_blkfree: freeing free block p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/115645 fs [snapshots] [panic] lockmgr: thread 0xc4c00d80, not ex o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o usb/112640 fs [ext2fs] [hang] Kernel freezes when writing a file to o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] mount_msdosfs: msdosfs_iconv: Operation not o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/105093 fs [ext2fs] [patch] ext2fs on read-only media cannot be m o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [iso9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna f kern/91568 fs [ufs] [panic] writing to UFS/softupdates DVD media in o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/89991 fs [ufs] softupdates with mount -ur causes fs UNREFS o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o kern/85326 fs [smbfs] [panic] saving a file via samba to an overquot o kern/84589 fs [2TB] 5.4-STABLE unresponsive during background fsck 2 o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o kern/77826 fs [ext2fs] ext2fs usb filesystem will not mount RW o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 144 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 12:40:10 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85CFB106568B; Mon, 14 Sep 2009 12:40:10 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5B0808FC1A; Mon, 14 Sep 2009 12:40:10 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8ECeAes070051; Mon, 14 Sep 2009 12:40:10 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8ECe9re070015; Mon, 14 Sep 2009 12:40:09 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 12:40:09 GMT Message-Id: <200909141240.n8ECe9re070015@freefall.freebsd.org> To: mandrews@fark.com, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/125644: [zfs] [panic] zfs unfixable fs errors caused panic when trying to destroy filesystem 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: Mon, 14 Sep 2009 12:40:10 -0000 Synopsis: [zfs] [panic] zfs unfixable fs errors caused panic when trying to destroy filesystem State-Changed-From-To: open->closed State-Changed-By: pjd State-Changed-When: pon 14 wrz 2009 12:38:47 UTC State-Changed-Why: Strange panic on old ZFS version. If it will happen again on FreeBSD 8, please let me know. http://www.freebsd.org/cgi/query-pr.cgi?pr=125644 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 12:40:26 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D48A1065672; Mon, 14 Sep 2009 12:40:26 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 72B7A8FC12; Mon, 14 Sep 2009 12:40:26 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8ECeQiN072794; Mon, 14 Sep 2009 12:40:26 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8ECeQLn072790; Mon, 14 Sep 2009 12:40:26 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 12:40:26 GMT Message-Id: <200909141240.n8ECeQLn072790@freefall.freebsd.org> To: pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/125644: [zfs] [panic] zfs unfixable fs errors caused panic when trying to destroy filesystem 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: Mon, 14 Sep 2009 12:40:26 -0000 Synopsis: [zfs] [panic] zfs unfixable fs errors caused panic when trying to destroy filesystem Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: pon 14 wrz 2009 12:40:13 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=125644 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 12:44:23 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1BF310656C4; Mon, 14 Sep 2009 12:44:23 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B65A18FC14; Mon, 14 Sep 2009 12:44:23 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8ECiNFr079105; Mon, 14 Sep 2009 12:44:23 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8ECiNiL079101; Mon, 14 Sep 2009 12:44:23 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 12:44:23 GMT Message-Id: <200909141244.n8ECiNiL079101@freefall.freebsd.org> To: stas@net.utcluj.ro, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/136218: [zfs] Exported ZFS pools can't be imported into (Open)Solaris 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: Mon, 14 Sep 2009 12:44:24 -0000 Synopsis: [zfs] Exported ZFS pools can't be imported into (Open)Solaris State-Changed-From-To: open->closed State-Changed-By: pjd State-Changed-When: pon 14 wrz 2009 12:42:24 UTC State-Changed-Why: Problem solved by the author. Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: pon 14 wrz 2009 12:42:24 UTC Responsible-Changed-Why: I'll take that one. http://www.freebsd.org/cgi/query-pr.cgi?pr=136218 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 12:47:05 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1ED01065693; Mon, 14 Sep 2009 12:47:05 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 873878FC0C; Mon, 14 Sep 2009 12:47:05 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8ECl5LQ079182; Mon, 14 Sep 2009 12:47:05 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8ECl5Vd079178; Mon, 14 Sep 2009 12:47:05 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 12:47:05 GMT Message-Id: <200909141247.n8ECl5Vd079178@freefall.freebsd.org> To: tim@bishnet.net, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/138764: [zfs] [panic] ZFS panic: "panic: dirtying snapshot!" 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: Mon, 14 Sep 2009 12:47:05 -0000 Synopsis: [zfs] [panic] ZFS panic: "panic: dirtying snapshot!" State-Changed-From-To: open->suspended State-Changed-By: pjd State-Changed-When: pon 14 wrz 2009 12:46:18 UTC State-Changed-Why: At least backtrace is needed to start working on this problem. Suspend PR until backtrace is provided. Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: pon 14 wrz 2009 12:46:18 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=138764 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 13:07:47 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92903106568B; Mon, 14 Sep 2009 13:07:47 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6745C8FC16; Mon, 14 Sep 2009 13:07:47 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8ED7lmS098001; Mon, 14 Sep 2009 13:07:47 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8ED7k3C097997; Mon, 14 Sep 2009 13:07:46 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 13:07:46 GMT Message-Id: <200909141307.n8ED7k3C097997@freefall.freebsd.org> To: titov-av@ptt.spb.ru, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/127492: [zfs] System hang on ZFS input-output 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: Mon, 14 Sep 2009 13:07:47 -0000 Synopsis: [zfs] System hang on ZFS input-output State-Changed-From-To: open->feedback State-Changed-By: pjd State-Changed-When: pon 14 wrz 2009 13:07:16 UTC State-Changed-Why: Can you still see this behaviour with FreeBSD 8? Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: pon 14 wrz 2009 13:07:16 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=127492 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 13:13:29 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AF17106566B; Mon, 14 Sep 2009 13:13:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id EFC0B8FC0C; Mon, 14 Sep 2009 13:13:28 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 8FB9E46B1A; Mon, 14 Sep 2009 09:13:28 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id D2ADF8A01B; Mon, 14 Sep 2009 09:13:27 -0400 (EDT) From: John Baldwin To: freebsd-fs@freebsd.org Date: Mon, 14 Sep 2009 08:32:27 -0400 User-Agent: KMail/1.9.7 References: <20090913202350.GE2091@garage.freebsd.pl> In-Reply-To: <20090913202350.GE2091@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909140832.27956.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 14 Sep 2009 09:13:27 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Pawel Jakub Dawidek Subject: Re: Review request for NFS readdirplus change. 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: Mon, 14 Sep 2009 13:13:29 -0000 On Sunday 13 September 2009 4:23:50 pm Pawel Jakub Dawidek wrote: > Hi. > > I'm looking for a review of the following patch: > > http://people.freebsd.org/~pjd/patches/nfs_serv.c.3.patch > > The main purpose of this patch is to support stuff like ZFS, where using > VFS_VGET() might be tricky on .zfs/ directory and friends. When > VFS_VGET() is not supported be the underlying file system, we switch to > VOP_LOOKUP(). Note that OpenSolaris NFS server implementation always > uses lookup for readdirplus. > > I also modified the code to use shared-locking, there is no need to > exclusively lock the vnodes. > > The patch removes an assert which doesn't hold for ZFS when we go into > .zfs/snapshot// directory, which is separate mount point, but we > don't want to export it separately, so we still return it on lookup. I don't think you need the trailing '\' before a split expression when building cn_flags. Other than that I think it looks ok from what I can see (but I am far less familiar with the NFS server than the NFS client). Also, you might want to patch the new NFS server as well as the old one (or ask Rick about the new one). -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 13:13:39 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DBF21065672; Mon, 14 Sep 2009 13:13:39 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DFC0D8FC19; Mon, 14 Sep 2009 13:13:38 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 931AD46B06; Mon, 14 Sep 2009 09:13:38 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id A9C268A01F; Mon, 14 Sep 2009 09:13:36 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 14 Sep 2009 08:58:33 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909140858.34592.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 14 Sep 2009 09:13:37 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-fs@freebsd.org, qing.li@bluecoat.com Subject: Re: NFS client defaults to a mix of UDP and TCP 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: Mon, 14 Sep 2009 13:13:39 -0000 On Sunday 13 September 2009 2:18:25 pm Rick Macklem wrote: > I had thought that I had posted w.r.t. before, but can't find it in > the archive (which might explain why I didn't get any responses:-). > > The current mount_nfs defaults to using UDP for the mount protocol > and then switches to using TCP for the actual mount. (When neither > "udp" nor "tcp" mount options are specified.) I don't think I > changed it to be this way, because I recall noticing it when I > added changes for the experimental NFS client and thought it was > "weird", but assumed that it had been that way for a long time. > > It now appears that it was introduced post-FreeBSD7 at r176198, > which changed the default for NFS to TCP, but didn't switch the > default for the mount protocol to TCP. > > The ancient history of this is that "once upon a time" there were > NFS servers that could do NFS over TCP, but only supported UDP for > the mount protocol and there was an option called "mntudp" for that > case. I can't imagine that any server still needs this case, but > it appears to have become the default. > > The default works fine for servers that support both UDP and TCP, > but result in a non-functional mount point when the server only > supports UDP. (See recent email thread on freebsd-stable called > "NFS issues on 8.0-BETA4".) > > Is this something that should be changed? rick Yes. I know of folks would love to have NFS use only TCP, including the initial RPC portmapper requests. IMO an NFS mount should use TCP for everything and a UDP mount should use UDP for everything by default. -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 13:22:41 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 388F61065694; Mon, 14 Sep 2009 13:22:41 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0CC148FC18; Mon, 14 Sep 2009 13:22:41 +0000 (UTC) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8EDMeuJ017934; Mon, 14 Sep 2009 13:22:40 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8EDMeJ2017930; Mon, 14 Sep 2009 13:22:40 GMT (envelope-from pjd) Date: Mon, 14 Sep 2009 13:22:40 GMT Message-Id: <200909141322.n8EDMeJ2017930@freefall.freebsd.org> To: 7ogcg7g02@sneakemail.com, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/132068: [zfs] page fault when using ZFS over NFS on 7.1-RELEASE/amd64 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: Mon, 14 Sep 2009 13:22:41 -0000 Synopsis: [zfs] page fault when using ZFS over NFS on 7.1-RELEASE/amd64 State-Changed-From-To: feedback->patched State-Changed-By: pjd State-Changed-When: pon 14 wrz 2009 13:22:15 UTC State-Changed-Why: Fixed in HEAD. Thanks for the report! Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: pon 14 wrz 2009 13:22:15 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=132068 From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 13:28:56 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 206201065672; Mon, 14 Sep 2009 13:28:56 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E95CB8FC33; Mon, 14 Sep 2009 13:28:54 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA29779; Mon, 14 Sep 2009 16:28:51 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AAE4513.6030701@icyb.net.ua> Date: Mon, 14 Sep 2009 16:28:51 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: John Baldwin References: <200909140858.34592.jhb@freebsd.org> In-Reply-To: <200909140858.34592.jhb@freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, qing.li@bluecoat.com, freebsd-current@freebsd.org Subject: Re: NFS client defaults to a mix of UDP and TCP 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: Mon, 14 Sep 2009 13:28:56 -0000 on 14/09/2009 15:58 John Baldwin said the following: > > Yes. I know of folks would love to have NFS use only TCP, including the > initial RPC portmapper requests. IMO an NFS mount should use TCP for > everything and a UDP mount should use UDP for everything by default. > And another fact - it seems that NFS umount unconditionally uses UDP for "something": /* * Report to mountd-server which nfsname * has been unmounted. */ if (ai != NULL && !(fflag & MNT_FORCE) && do_rpc) { clp = clnt_create(hostp, MOUNTPROG, MOUNTVERS, "udp"); ... -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 15:40:04 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE6F11065670 for ; Mon, 14 Sep 2009 15:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AB3CE8FC15 for ; Mon, 14 Sep 2009 15:40:04 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8EFe432048928 for ; Mon, 14 Sep 2009 15:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8EFe40O048927; Mon, 14 Sep 2009 15:40:04 GMT (envelope-from gnats) Date: Mon, 14 Sep 2009 15:40:04 GMT Message-Id: <200909141540.n8EFe40O048927@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Aditya Sarawgi Cc: Subject: Re: usb/112640: [ext2fs] [hang] Kernel freezes when writing a file to an ex2fs filesystem on a usb disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Aditya Sarawgi List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2009 15:40:04 -0000 The following reply was made to PR usb/112640; it has been noted by GNATS. From: Aditya Sarawgi To: klaas@kite.ping.de, gavin@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: usb/112640: [ext2fs] [hang] Kernel freezes when writing a file to an ex2fs filesystem on a usb disk Date: Mon, 14 Sep 2009 21:02:33 +0000 Hi, I think this problem persists only on amd64. I have rewritten some parts of ext2fs and I feel this problem will not occur in the new implementation. I don't have a merge for 7.x release for the new code but if you want to try the code on 8.x mail me. Thanks! -- Aditya Sarawgi From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 16:16:14 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30DD81065693; Mon, 14 Sep 2009 16:16:14 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id AC8618FC1A; Mon, 14 Sep 2009 16:16:13 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAKYIrkqDaFvK/2dsb2JhbADdIoQYBQ X-IronPort-AV: E=Sophos;i="4.44,384,1249272000"; d="scan'208";a="46238684" Received: from fraser.cs.uoguelph.ca ([131.104.91.202]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 14 Sep 2009 12:16:12 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 9E765109C271; Mon, 14 Sep 2009 12:16:12 -0400 (EDT) X-Virus-Scanned: amavisd-new at fraser.cs.uoguelph.ca Received: from fraser.cs.uoguelph.ca ([127.0.0.1]) by localhost (fraser.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4a2DbWRUbBE; Mon, 14 Sep 2009 12:16:12 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id F3FC0109C2CB; Mon, 14 Sep 2009 12:16:11 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8EGLXP20407; Mon, 14 Sep 2009 12:21:33 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 14 Sep 2009 12:21:33 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: John Baldwin In-Reply-To: <200909140832.27956.jhb@freebsd.org> Message-ID: References: <20090913202350.GE2091@garage.freebsd.pl> <200909140832.27956.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, Pawel Jakub Dawidek Subject: Re: Review request for NFS readdirplus change. 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: Mon, 14 Sep 2009 16:16:14 -0000 On Mon, 14 Sep 2009, John Baldwin wrote: > On Sunday 13 September 2009 4:23:50 pm Pawel Jakub Dawidek wrote: >> Hi. >> >> I'm looking for a review of the following patch: >> >> http://people.freebsd.org/~pjd/patches/nfs_serv.c.3.patch >> [good stuff snipped] > > I don't think you need the trailing '\' before a split expression when > building cn_flags. Other than that I think it looks ok from what I can see > (but I am far less familiar with the NFS server than the NFS client). Also, > you might want to patch the new NFS server as well as the old one (or ask > Rick about the new one). > Looks fine to me, too (although I'm not particularily familiar with the flags for VOP_LOOKUP()). I can do a similar change to the experimental server once it goes in. rick From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 16:22:34 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5740106566B; Mon, 14 Sep 2009 16:22:34 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 5C3418FC17; Mon, 14 Sep 2009 16:22:34 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAP8KrkqDaFvK/2dsb2JhbADdJYQYBQ X-IronPort-AV: E=Sophos;i="4.44,384,1249272000"; d="scan'208";a="47975773" Received: from fraser.cs.uoguelph.ca ([131.104.91.202]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 14 Sep 2009 12:22:12 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 5B0F6109C271; Mon, 14 Sep 2009 12:22:12 -0400 (EDT) X-Virus-Scanned: amavisd-new at fraser.cs.uoguelph.ca Received: from fraser.cs.uoguelph.ca ([127.0.0.1]) by localhost (fraser.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bB7R+FrdmaAJ; Mon, 14 Sep 2009 12:22:11 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id ABBA3109C2BA; Mon, 14 Sep 2009 12:22:11 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8EGRWW21507; Mon, 14 Sep 2009 12:27:33 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 14 Sep 2009 12:27:32 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Andriy Gapon In-Reply-To: <4AAE4513.6030701@icyb.net.ua> Message-ID: References: <200909140858.34592.jhb@freebsd.org> <4AAE4513.6030701@icyb.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, qing.li@bluecoat.com, freebsd-current@freebsd.org Subject: Re: NFS client defaults to a mix of UDP and TCP 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: Mon, 14 Sep 2009 16:22:34 -0000 On Mon, 14 Sep 2009, Andriy Gapon wrote: > on 14/09/2009 15:58 John Baldwin said the following: >> >> Yes. I know of folks would love to have NFS use only TCP, including the >> initial RPC portmapper requests. IMO an NFS mount should use TCP for >> everything and a UDP mount should use UDP for everything by default. >> > > And another fact - it seems that NFS umount unconditionally uses UDP for "something": > > /* > * Report to mountd-server which nfsname > * has been unmounted. > */ > if (ai != NULL && !(fflag & MNT_FORCE) && do_rpc) { > clp = clnt_create(hostp, MOUNTPROG, MOUNTVERS, "udp"); > ... > Yep. This one is somewhat less critical IMO, since this RPC is just fyi for the mountd on the server and, if it fails for any reason, only normally affects the output of "showmount" and doesn't break the umount. (That doesn't mean I don't think it should be fixed, but it can be done separately from resolving what mount_nfs needs to default to.) rick From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 18:09:21 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFB0F106566B for ; Mon, 14 Sep 2009 18:09:21 +0000 (UTC) (envelope-from mel.flynn+fbsd.fs@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id C32948FC0C for ; Mon, 14 Sep 2009 18:09:20 +0000 (UTC) Received: from smoochies.rachie.is-a-geek.net (mailhub.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 355DB7E821 for ; Mon, 14 Sep 2009 10:09:33 -0800 (AKDT) From: Mel Flynn To: freebsd-fs@freebsd.org Date: Mon, 14 Sep 2009 20:09:17 +0200 User-Agent: KMail/1.12.1 (FreeBSD/8.0-BETA4; KDE/4.3.1; i386; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200909142009.17782.mel.flynn+fbsd.fs@mailing.thruhere.net> Subject: Question about struct vop_*_args 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: Mon, 14 Sep 2009 18:09:22 -0000 Hi, find+grep isn't able to tell me where the struct vop_rename_args and friends are defined. Is this done dynamically somewhere and can anyone point to the location? -- Mel From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 18:13:14 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31745106566C for ; Mon, 14 Sep 2009 18:13:14 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id B68288FC21 for ; Mon, 14 Sep 2009 18:13:13 +0000 (UTC) Received: by ewy4 with SMTP id 4so3316361ewy.36 for ; Mon, 14 Sep 2009 11:13:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :date:in-reply-to:message-id:user-agent:mime-version:content-type; bh=SxNA2n2RLITNyz4Gtf9eQVEzX6/ALDulk1K5FTqnrDE=; b=WvqXK4YLmZyuu1DxAdESImns2rf2HFLd8pXjtJjpMVyV5d+PrznpIPA5PLWQenr5Bn S8Hk22movWPK+T6BhHPhKTEQJZLpC+Vm5q1ku5JP2tGOrfLKd5nIpOSHc55V2LPhggFy zzqDO8VDJV+uSygoGIdRvkpL9v6qqfM/kzgpQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=gGJnPt3VJILTDxRoO8i6YeB0pACVqEYuQg2A5lPK4cz6TTC+xs7Ew7U8LMtqrbSazY +XIEd2tCr1eUuI02e8eOAv1sMKibiH8Fs9aNxDd8DPx9lZIfaCxJrM69+0uDgFLXH6/A NYLde2lYsNqoNDhNuNqzc/4M/eWJdzVQleQmQ= Received: by 10.211.145.11 with SMTP id x11mr7138110ebn.74.1252950784606; Mon, 14 Sep 2009 10:53:04 -0700 (PDT) Received: from localhost (95-24-81-232.broadband.corbina.ru [95.24.81.232]) by mx.google.com with ESMTPS id 7sm1972286eyb.5.2009.09.14.10.53.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 14 Sep 2009 10:53:03 -0700 (PDT) From: Anonymous To: pjd@FreeBSD.org References: <200909140703.n8E73VH1000588@freefall.freebsd.org> Date: Mon, 14 Sep 2009 21:51:57 +0400 In-Reply-To: <200909140703.n8E73VH1000588@freefall.freebsd.org> (pjd@freebsd.org's message of "Mon, 14 Sep 2009 07:03:31 GMT") Message-ID: <86ab0xqurm.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@FreeBSD.org, bug-followup@freebsd.org Subject: Re: kern/129148: [zfs] [panic] panic on concurrent writing & rollback 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: Mon, 14 Sep 2009 18:13:14 -0000 pjd@FreeBSD.org writes: > Synopsis: [zfs] [panic] panic on concurrent writing & rollback > > State-Changed-From-To: open->patched > State-Changed-By: pjd > State-Changed-When: pon 14 wrz 2009 07:02:21 UTC > State-Changed-Why: > I believe it is already fixed in HEAD. Could you verify? > If you can't try HEAD, it sould be in 8 soon. I'm no longer able to reproduce it on r197192M neither with the script nor with patch & rollback & patch sequence. From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 18:27:33 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B251106566B for ; Mon, 14 Sep 2009 18:27:33 +0000 (UTC) (envelope-from mdounin@mdounin.ru) Received: from mdounin.cust.ramtel.ru (mdounin.cust.ramtel.ru [81.19.69.81]) by mx1.freebsd.org (Postfix) with ESMTP id BCFEB8FC16 for ; Mon, 14 Sep 2009 18:27:32 +0000 (UTC) Received: from mdounin.ru (mdounin.cust.ramtel.ru [81.19.69.81]) by mdounin.cust.ramtel.ru (Postfix) with ESMTP id 090D01703B; Mon, 14 Sep 2009 22:27:30 +0400 (MSD) Date: Mon, 14 Sep 2009 22:27:30 +0400 From: Maxim Dounin To: Mel Flynn Message-ID: <20090914182730.GF4917@mdounin.ru> References: <200909142009.17782.mel.flynn+fbsd.fs@mailing.thruhere.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909142009.17782.mel.flynn+fbsd.fs@mailing.thruhere.net> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: Question about struct vop_*_args 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: Mon, 14 Sep 2009 18:27:33 -0000 Hello! On Mon, Sep 14, 2009 at 08:09:17PM +0200, Mel Flynn wrote: > Hi, > > find+grep isn't able to tell me where the struct vop_rename_args and friends > are defined. Is this done dynamically somewhere and can anyone point to the > location? Yes, it's defined in vnode_if.h which is dynamically generated by src/sys/tools/vnode_if.awk from src/sys/kern/vnode_if.src. Maxim Dounin From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 18:45:15 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FEE21065670 for ; Mon, 14 Sep 2009 18:45:15 +0000 (UTC) (envelope-from scjamorim@bsd.com.br) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 425038FC12 for ; Mon, 14 Sep 2009 18:45:14 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so759574eyf.9 for ; Mon, 14 Sep 2009 11:45:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.211.174.15 with SMTP id b15mr3433524ebp.22.1252951954218; Mon, 14 Sep 2009 11:12:34 -0700 (PDT) In-Reply-To: <200909142009.17782.mel.flynn+fbsd.fs@mailing.thruhere.net> References: <200909142009.17782.mel.flynn+fbsd.fs@mailing.thruhere.net> Date: Mon, 14 Sep 2009 15:12:34 -0300 Message-ID: <5859850b0909141112q5409e660qba85bca99b8b3eeb@mail.gmail.com> From: Sylvio Cesar To: Mel Flynn Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: Question about struct vop_*_args 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: Mon, 14 Sep 2009 18:45:15 -0000 Hi, Uses: find with xargs and grep. i.e: find / | xargs grep name_args Regards, Sylvio Cesar 2009/9/14 Mel Flynn : > Hi, > > find+grep isn't able to tell me where the struct vop_rename_args and friends > are defined. Is this done dynamically somewhere and can anyone point to the > location? > -- > Mel > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 18:59:38 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1C6F106568B for ; Mon, 14 Sep 2009 18:59:38 +0000 (UTC) (envelope-from mel.flynn+fbsd.fs@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id A31B98FC14 for ; Mon, 14 Sep 2009 18:59:38 +0000 (UTC) Received: from smoochies.rachie.is-a-geek.net (mailhub.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id E861A7E818; Mon, 14 Sep 2009 10:59:49 -0800 (AKDT) From: Mel Flynn To: freebsd-fs@freebsd.org Date: Mon, 14 Sep 2009 20:59:34 +0200 User-Agent: KMail/1.12.1 (FreeBSD/8.0-BETA4; KDE/4.3.1; i386; ; ) References: <200909142009.17782.mel.flynn+fbsd.fs@mailing.thruhere.net> <20090914182730.GF4917@mdounin.ru> In-Reply-To: <20090914182730.GF4917@mdounin.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200909142059.34881.mel.flynn+fbsd.fs@mailing.thruhere.net> Cc: Subject: Re: Question about struct vop_*_args 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: Mon, 14 Sep 2009 18:59:38 -0000 On Monday 14 September 2009 20:27:30 Maxim Dounin wrote: > Hello! > > On Mon, Sep 14, 2009 at 08:09:17PM +0200, Mel Flynn wrote: > > Hi, > > > > find+grep isn't able to tell me where the struct vop_rename_args and > > friends are defined. Is this done dynamically somewhere and can anyone > > point to the location? > > Yes, it's defined in vnode_if.h which is dynamically generated by > src/sys/tools/vnode_if.awk from src/sys/kern/vnode_if.src. Ah, thank you very much. Now I know where to start reading. -- Mel From owner-freebsd-fs@FreeBSD.ORG Mon Sep 14 18:59:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FF98106568D; Mon, 14 Sep 2009 18:59:49 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 56FB38FC15; Mon, 14 Sep 2009 18:59:47 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id VAA06392; Mon, 14 Sep 2009 21:59:43 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1MnGm7-0001fq-0L; Mon, 14 Sep 2009 21:59:43 +0300 Message-ID: <4AAE929E.3040904@icyb.net.ua> Date: Mon, 14 Sep 2009 21:59:42 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090823) MIME-Version: 1.0 To: Rick Macklem References: <200909140858.34592.jhb@freebsd.org> <4AAE4513.6030701@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, qing.li@bluecoat.com, freebsd-current@freebsd.org Subject: Re: NFS client defaults to a mix of UDP and TCP 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: Mon, 14 Sep 2009 18:59:49 -0000 on 14/09/2009 19:27 Rick Macklem said the following: > > > On Mon, 14 Sep 2009, Andriy Gapon wrote: > >> on 14/09/2009 15:58 John Baldwin said the following: >>> >>> Yes. I know of folks would love to have NFS use only TCP, including the >>> initial RPC portmapper requests. IMO an NFS mount should use TCP for >>> everything and a UDP mount should use UDP for everything by default. >>> >> >> And another fact - it seems that NFS umount unconditionally uses UDP >> for "something": >> >> /* >> * Report to mountd-server which nfsname >> * has been unmounted. >> */ >> if (ai != NULL && !(fflag & MNT_FORCE) && do_rpc) { >> clp = clnt_create(hostp, MOUNTPROG, MOUNTVERS, "udp"); >> ... >> > Yep. This one is somewhat less critical IMO, since this RPC is just > fyi for the mountd on the server and, if it fails for any reason, only > normally affects the output of "showmount" and doesn't break the umount. > (That doesn't mean I don't think it should be fixed, but it can be done > separately from resolving what mount_nfs needs to default to.) I agree. It's just that given the nature of UDP it takes a very long while for umount to re-alize that nobody's listening in some situations. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Tue Sep 15 00:47:00 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB8F11065695; Tue, 15 Sep 2009 00:47:00 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B297C8FC1D; Tue, 15 Sep 2009 00:47:00 +0000 (UTC) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8F0l00k096717; Tue, 15 Sep 2009 00:47:00 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8F0l0MS096713; Tue, 15 Sep 2009 00:47:00 GMT (envelope-from linimon) Date: Tue, 15 Sep 2009 00:47:00 GMT Message-Id: <200909150047.n8F0l0MS096713@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/138790: [zfs] ZFS ceases caching when mem demand is high 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, 15 Sep 2009 00:47:01 -0000 Old Synopsis: ZFS ceases caching when mem demand is high New Synopsis: [zfs] ZFS ceases caching when mem demand is high Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Sep 15 00:46:39 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=138790 From owner-freebsd-fs@FreeBSD.ORG Tue Sep 15 01:28:33 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1060) id 07899106566C; Tue, 15 Sep 2009 01:28:33 +0000 (UTC) Date: Tue, 15 Sep 2009 01:28:33 +0000 From: Craig Rodrigues To: Rick Macklem Message-ID: <20090915012833.GA54756@crodrigues.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, qing.li@bluecoat.com, freebsd-current@freebsd.org Subject: Re: NFS client defaults to a mix of UDP and TCP 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, 15 Sep 2009 01:28:33 -0000 On Sun, Sep 13, 2009 at 02:18:25PM -0400, Rick Macklem wrote: > Is this something that should be changed? rick Go ahead and clean this up. I worked with Doug Rabson to re-do a lot of the mount_nfs code to use nmount(), and this UDP/TCP thing for the RPC transport slipped through. There is no good reason for keeping things the way they are. Thanks for all your work beating the FreeBSD NFS implementation into shape! I sat next to you at the Italian restaurant at BSDCan 2009. :) -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-fs@FreeBSD.ORG Tue Sep 15 18:38:02 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66BA9106568B for ; Tue, 15 Sep 2009 18:38:02 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id 9B38F8FC37 for ; Tue, 15 Sep 2009 18:38:01 +0000 (UTC) Received: by ewy4 with SMTP id 4so4352034ewy.36 for ; Tue, 15 Sep 2009 11:38:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=WyusQeGrGkDcoX8aM3k6lLvrY2Bdldpv3kzcW+FncQg=; b=wb7v9iv4V4HHD0aFzninfISsSbgHILkEZH4MrITUyQzXp4dQWq+KKywZdLA/k3EN6q caLsDhR3El9Zf4o8Oys9GJJcorUygny1k9wv/ZdUbxaOeDk4PO4ih7j1YrzLfJcTIx0H PK7MjmTqRiKDUShr0r3Scx3QCK2tTaJUbcYi0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=q7l4XFM9zVC/9CR67zBGY9VclT6/IY8wrF7yLLEE/DxJP1IzIUsM0+KlkjDMyi/CZe OzGCjKX3jtycop750a895HtGXSkh6R5Lw2NpCT4cDDGGMrB76WkcNbypukykJjKKZG2+ 4j5A+i0RsyV0ZzoxHveOujcNrFFR8ehcrIPBQ= MIME-Version: 1.0 Received: by 10.216.71.133 with SMTP id r5mr1348002wed.180.1253039880206; Tue, 15 Sep 2009 11:38:00 -0700 (PDT) In-Reply-To: <200909150047.n8F0l0MS096713@freefall.freebsd.org> References: <200909150047.n8F0l0MS096713@freefall.freebsd.org> Date: Tue, 15 Sep 2009 14:38:00 -0400 Message-ID: <5f67a8c40909151138l4c4fcd3cnc31bf3f59a781052@mail.gmail.com> From: Zaphod Beeblebrox To: linimon@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/138790: [zfs] ZFS ceases caching when mem demand is high 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, 15 Sep 2009 18:38:02 -0000 On Mon, Sep 14, 2009 at 8:47 PM, wrote: > Old Synopsis: ZFS ceases caching when mem demand is high > New Synopsis: [zfs] ZFS ceases caching when mem demand is high > > Responsible-Changed-From-To: freebsd-bugs->freebsd-fs > Responsible-Changed-By: linimon > Responsible-Changed-When: Tue Sep 15 00:46:39 UTC 2009 > Responsible-Changed-Why: > Over to maintainer(s). > I have a question on this: Are we back to the old fight on dividing the system memory resource between cache and paging again? This seems like a major regression for using ZFS over UFS. The idea that this might be happening has caused me to regard my ZFS store as a largely nfs/smb appliance. Certainly it does well in this role --- and dedicating a system to many terrabytes of store isn't the end-of-the-world, but having used ZFS on my laptop --- and all the pain that incurs --- I'm shy about using ZFS on anything that isn't essentially a disk appliance. ZFS should be better than that. If the cache/VM aren't integrated on FreeBSD, are they integrated in OpenSolaris? From owner-freebsd-fs@FreeBSD.ORG Tue Sep 15 18:40:11 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5667C106568B for ; Tue, 15 Sep 2009 18:40:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 459698FC22 for ; Tue, 15 Sep 2009 18:40:11 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8FIeB1i019384 for ; Tue, 15 Sep 2009 18:40:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8FIeBGX019383; Tue, 15 Sep 2009 18:40:11 GMT (envelope-from gnats) Date: Tue, 15 Sep 2009 18:40:11 GMT Message-Id: <200909151840.n8FIeBGX019383@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Jaakko Heinonen Cc: Subject: Re: usb/112640: [ext2fs] [hang] Kernel freezes when writing a file to an ex2fs filesystem on a usb disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jaakko Heinonen List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2009 18:40:11 -0000 The following reply was made to PR usb/112640; it has been noted by GNATS. From: Jaakko Heinonen To: klaas@kite.ping.de, Aditya Sarawgi Cc: bug-followup@FreeBSD.org, gavin@FreeBSD.org Subject: Re: usb/112640: [ext2fs] [hang] Kernel freezes when writing a file to an ex2fs filesystem on a usb disk Date: Tue, 15 Sep 2009 21:39:14 +0300 On 2009-09-14, Aditya Sarawgi wrote: > I think this problem persists only on amd64. I was unable reproduce the problem with the command give in audit trail. Are you sure that the problem is reproducible after r186740 (head) or r187386 (stable/7)? Those revisions fixed a bug with identical symptoms. -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Tue Sep 15 18:44:42 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79DD61065696; Tue, 15 Sep 2009 18:44:42 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from spirit.gamesnet.de (spirit.gamesnet.de [87.230.101.86]) by mx1.freebsd.org (Postfix) with ESMTP id 2F2738FC1E; Tue, 15 Sep 2009 18:44:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTP id 0A1A229B013; Tue, 15 Sep 2009 20:44:10 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.gamesnet.de Received: from spirit.gamesnet.de ([127.0.0.1]) by localhost (spirit.gamesnet.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5sNF3e4jZxG6; Tue, 15 Sep 2009 20:44:06 +0200 (CEST) Received: from sub.han.vpn.gamesnet.de (sub.han.vpn.gamesnet.de [192.168.1.101]) by spirit.gamesnet.de (Postfix) with ESMTPSA id DB15729B00F; Tue, 15 Sep 2009 20:44:05 +0200 (CEST) Date: Tue, 15 Sep 2009 20:44:04 +0200 From: Tobias Lott To: "Pawel Jakub Dawidek" Message-ID: <20090915204404.79cf9325@sub.han.vpn.gamesnet.de> In-Reply-To: <102295df02d347c97bd098dc89ccb534.squirrel@mail.gamesnet.de> References: <200909011005.18200.jhb@freebsd.org> <20090908214402.43009577@sub.han.vpn.gamesnet.de> <20090909001942.0affc96c@sub.han.vpn.gamesnet.de> <20090909054249.GH1539@garage.freebsd.pl> <20090909101346.01887a02@sub.han.vpn.gamesnet.de> <20090910215254.GD2718@garage.freebsd.pl> <102295df02d347c97bd098dc89ccb534.squirrel@mail.gamesnet.de> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Problems with ZFS on AMD64 (and i386 now) 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, 15 Sep 2009 18:44:42 -0000 On Fri, 11 Sep 2009 11:51:25 +0200 tlott@gamesnet.de wrote: > > On Wed, Sep 09, 2009 at 10:13:46AM +0200, Tobias Lott wrote: > >> > >> > >> On Wed, 9 Sep 2009 07:42:49 +0200 > >> Pawel Jakub Dawidek wrote: > >> > >> > On Wed, Sep 09, 2009 at 12:19:42AM +0200, Tobias Lott wrote: > >> > > Hey Everyone > >> > > > >> > > I've managed to get some Output for this, using BETA2 LiveCD > >> > > (gonna try using BETA4 CD Tomorrow). > >> > > > >> > > 'zfs import -f poolname' triggered this, Booting kernel.old > >> > > (BETA3) and today built BETA4 Kernel Panic mounting zfs > >> > > Volumes. Booting single user mode I get output of zfs list and > >> > > so on but mounting whatever volume also Panics. > >> > > >> > Why -f? Were there a poblem in importing pool? > >> > > >> > > Stack output, if there's more you need I'll gladly help > >> > > http://i27.tinypic.com/2d78qpd.jpg > >> > > http://i31.tinypic.com/oqhv2w.jpg > >> > > http://i28.tinypic.com/oktsag.jpg > >> > > >> > Could you also provide top part of the backtrace? > >> > > >> Oh yeah my bad > >> > >> http://i29.tinypic.com/nqwxo2.jpg > >> http://i26.tinypic.com/209hanm.jpg > > > > Seems that one of the vdevs is NULL. Could you tell me why you > > decided to use -f option for importing the pool? > > > > -- > > Pawel Jakub Dawidek http://www.wheel.pl > > pjd@FreeBSD.org http://www.FreeBSD.org > > FreeBSD committer Am I Evil? Yes, I Am! > > > > Because zpool import tank says: > cannot import 'tank': pool may be in use from other system > use '-f' to import anyway > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" Any news on this? -- Tobias Lott From owner-freebsd-fs@FreeBSD.ORG Tue Sep 15 21:41:53 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D5A01065694; Tue, 15 Sep 2009 21:41:53 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id A4FD68FC2E; Tue, 15 Sep 2009 21:41:52 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 30AEE45C8C; Tue, 15 Sep 2009 23:41:49 +0200 (CEST) Received: from localhost (chello087206049004.chello.pl [87.206.49.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 362AE45683; Tue, 15 Sep 2009 23:41:44 +0200 (CEST) Date: Tue, 15 Sep 2009 23:41:42 +0200 From: Pawel Jakub Dawidek To: Tobias Lott Message-ID: <20090915214142.GA2063@garage.freebsd.pl> References: <200909011005.18200.jhb@freebsd.org> <20090908214402.43009577@sub.han.vpn.gamesnet.de> <20090909001942.0affc96c@sub.han.vpn.gamesnet.de> <20090909054249.GH1539@garage.freebsd.pl> <20090909101346.01887a02@sub.han.vpn.gamesnet.de> <20090910215254.GD2718@garage.freebsd.pl> <102295df02d347c97bd098dc89ccb534.squirrel@mail.gamesnet.de> <20090915204404.79cf9325@sub.han.vpn.gamesnet.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <20090915204404.79cf9325@sub.han.vpn.gamesnet.de> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Problems with ZFS on AMD64 (and i386 now) 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, 15 Sep 2009 21:41:53 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 15, 2009 at 08:44:04PM +0200, Tobias Lott wrote: > Any news on this? Not really. I'm out of ideas. A way to repoduce it would be of course best. If you can't provide one maybe you remember something strange just before panic, like disk disappeared or something? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKsAoWForvXbEpPzQRAjFrAJ9OFfG3UhOjQwdFHnr5uuRXXCp3bACgojIJ q/FQI5qacrDpmCa2iztEyno= =dPaN -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- From owner-freebsd-fs@FreeBSD.ORG Tue Sep 15 21:55:48 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7AE9106566B; Tue, 15 Sep 2009 21:55:48 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from spirit.gamesnet.de (spirit.gamesnet.de [87.230.101.86]) by mx1.freebsd.org (Postfix) with ESMTP id 5BBBE8FC21; Tue, 15 Sep 2009 21:55:48 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTP id 4F3EB29B015; Tue, 15 Sep 2009 23:55:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.gamesnet.de Received: from spirit.gamesnet.de ([127.0.0.1]) by localhost (spirit.gamesnet.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id goSTy6HYeUgW; Tue, 15 Sep 2009 23:55:12 +0200 (CEST) Received: from sub.han.vpn.gamesnet.de (sub.han.vpn.gamesnet.de [192.168.1.101]) by spirit.gamesnet.de (Postfix) with ESMTPSA id 8262E29B013; Tue, 15 Sep 2009 23:55:12 +0200 (CEST) Date: Tue, 15 Sep 2009 23:55:11 +0200 From: Tobias Lott To: Pawel Jakub Dawidek Message-ID: <20090915235511.559550e5@sub.han.vpn.gamesnet.de> In-Reply-To: <20090915214142.GA2063@garage.freebsd.pl> References: <200909011005.18200.jhb@freebsd.org> <20090908214402.43009577@sub.han.vpn.gamesnet.de> <20090909001942.0affc96c@sub.han.vpn.gamesnet.de> <20090909054249.GH1539@garage.freebsd.pl> <20090909101346.01887a02@sub.han.vpn.gamesnet.de> <20090910215254.GD2718@garage.freebsd.pl> <102295df02d347c97bd098dc89ccb534.squirrel@mail.gamesnet.de> <20090915204404.79cf9325@sub.han.vpn.gamesnet.de> <20090915214142.GA2063@garage.freebsd.pl> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Problems with ZFS on AMD64 (and i386 now) 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, 15 Sep 2009 21:55:48 -0000 On Tue, 15 Sep 2009 23:41:42 +0200 Pawel Jakub Dawidek wrote: > On Tue, Sep 15, 2009 at 08:44:04PM +0200, Tobias Lott wrote: > > Any news on this? > > Not really. I'm out of ideas. A way to repoduce it would be of course > best. If you can't provide one maybe you remember something strange > just before panic, like disk disappeared or something? > Looks like I've found whats causing it by mounting all ZFS Volumes one by one. It was a Volume used by a Jail running nginx, nagios and some other stuff. Weird but luckily not that important since its a Test Machine, can I provide anything that you could figure out whats wrong with that Volume so it can be fixed? Cause I triggered this only by upgrading BETA3->4 #3 r196936. Cheers. -- Tobias Lott From owner-freebsd-fs@FreeBSD.ORG Wed Sep 16 00:53:47 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF772106566B for ; Wed, 16 Sep 2009 00:53:47 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 70B1F8FC08 for ; Wed, 16 Sep 2009 00:53:46 +0000 (UTC) Received: by email.octopus.com.au (Postfix, from userid 1002) id 3978D17323; Wed, 16 Sep 2009 10:55:21 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.4.19] (138.21.96.58.static.exetel.com.au [58.96.21.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 203F317DB6; Wed, 16 Sep 2009 10:55:17 +1000 (EST) Message-ID: <4AB03659.9060703@modulus.org> Date: Wed, 16 Sep 2009 10:50:33 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.6 (X11/20070926) MIME-Version: 1.0 To: Zaphod Beeblebrox References: <200909150047.n8F0l0MS096713@freefall.freebsd.org> <5f67a8c40909151138l4c4fcd3cnc31bf3f59a781052@mail.gmail.com> In-Reply-To: <5f67a8c40909151138l4c4fcd3cnc31bf3f59a781052@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: kern/138790: [zfs] ZFS ceases caching when mem demand is high 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, 16 Sep 2009 00:53:47 -0000 Zaphod Beeblebrox wrote: > Are we back to the old fight on dividing the system memory resource between > cache and paging again? This seems like a major regression for using ZFS > over UFS. > The idea that this might be happening has caused me to regard my ZFS store > as a largely nfs/smb appliance. > ZFS should be better than that. Why? ZFS is designed for systems with large amounts of memory to spare - I don't think it should be used for any system with less than 2GB. Most brand new systems bought these days will have at least 2GB, if not 4 or 8GB. UFS isn't going away, it is still the filesystem preferred for embedded and low-end systems. - Andrew From owner-freebsd-fs@FreeBSD.ORG Wed Sep 16 06:35:27 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0627B1065676 for ; Wed, 16 Sep 2009 06:35:27 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id 7E8568FC17 for ; Wed, 16 Sep 2009 06:35:26 +0000 (UTC) Received: by ewy4 with SMTP id 4so4779358ewy.36 for ; Tue, 15 Sep 2009 23:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=H8mQXUw1wUgUGeWtnFGArYHOa+gHvDrvrUjPUvcFZFE=; b=ZG0iXytYMDCXVlOkJp+KgQxDzquulSW/LJVQJTnrMvZ6p+BL6mh87xo4ohWzH98xdM R+eg6Xq7oCmJXoj1Tvy4u7YewS2soqy0xF2s02NtFa6rAlWUxu7irYBsCA0nZUei4anK 9QopWaYHqGJFwuf1iFnAid4Act4LieEw+U/Vo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ptVFPGqW5wdqalJZ0b/PJqbO5x05Qop+iHojjq5kYVecmvjyqdFz1y8+MN3AG3TcXl 78K1ZeY0cB5l8D4tcVfBKf2OKZ9HFWTzTu9w+TlsyKbNOtqcbbBEwXe5uqniSlrnN2kG 4HjQpTmpfagudtRi0xR4cGY0zuQRheJlArCIc= MIME-Version: 1.0 Received: by 10.216.17.78 with SMTP id i56mr1961165wei.80.1253082925552; Tue, 15 Sep 2009 23:35:25 -0700 (PDT) In-Reply-To: <4AB03659.9060703@modulus.org> References: <200909150047.n8F0l0MS096713@freefall.freebsd.org> <5f67a8c40909151138l4c4fcd3cnc31bf3f59a781052@mail.gmail.com> <4AB03659.9060703@modulus.org> Date: Wed, 16 Sep 2009 02:35:25 -0400 Message-ID: <5f67a8c40909152335k747dc9eao5d56f3cfdc77d3e4@mail.gmail.com> From: Zaphod Beeblebrox To: Andrew Snow Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: kern/138790: [zfs] ZFS ceases caching when mem demand is high 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, 16 Sep 2009 06:35:27 -0000 On Tue, Sep 15, 2009 at 8:50 PM, Andrew Snow wrote: > Zaphod Beeblebrox wrote: > > ZFS should be better than that. >> > > Why? ZFS is designed for systems with large amounts of memory to spare - I > don't think it should be used for any system with less than 2GB. > > Most brand new systems bought these days will have at least 2GB, if not 4 > or 8GB. > I don't see why that has to be the case. ZFS is certainly _tuned_ for large filesystems, but it's feature set has many more uses. Pretty much the entire world got the memo that unified buffercache was good. As I understand the stuff I've read, the fact that ZFS (in FreeBSD) isn't unified is largely due to making it easier to import (sure... fine... but) --- meaning that it's an item that should be fixed. As I understand it, ZFS is unified on OpenSolaris. > UFS isn't going away, it is still the filesystem preferred for embedded and > low-end systems. > What... snapshots are suddenly unhelpful on smaller systems? I think not. From owner-freebsd-fs@FreeBSD.ORG Wed Sep 16 15:46:26 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A01FB1065672; Wed, 16 Sep 2009 15:46:26 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id DD4558FC12; Wed, 16 Sep 2009 15:46:25 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 6357945E5C; Wed, 16 Sep 2009 17:46:23 +0200 (CEST) Received: from localhost (mail.garage.freebsd.pl [10.0.4.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id D2DDE45CD8; Wed, 16 Sep 2009 17:46:17 +0200 (CEST) Date: Wed, 16 Sep 2009 17:46:16 +0200 From: Pawel Jakub Dawidek To: Tobias Lott Message-ID: <20090916154616.GC1656@garage.freebsd.pl> References: <200909011005.18200.jhb@freebsd.org> <20090908214402.43009577@sub.han.vpn.gamesnet.de> <20090909001942.0affc96c@sub.han.vpn.gamesnet.de> <20090909054249.GH1539@garage.freebsd.pl> <20090909101346.01887a02@sub.han.vpn.gamesnet.de> <20090910215254.GD2718@garage.freebsd.pl> <102295df02d347c97bd098dc89ccb534.squirrel@mail.gamesnet.de> <20090915204404.79cf9325@sub.han.vpn.gamesnet.de> <20090915214142.GA2063@garage.freebsd.pl> <20090915235511.559550e5@sub.han.vpn.gamesnet.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="orO6xySwJI16pVnm" Content-Disposition: inline In-Reply-To: <20090915235511.559550e5@sub.han.vpn.gamesnet.de> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=4.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Problems with ZFS on AMD64 (and i386 now) 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, 16 Sep 2009 15:46:26 -0000 --orO6xySwJI16pVnm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 15, 2009 at 11:55:11PM +0200, Tobias Lott wrote: >=20 >=20 > On Tue, 15 Sep 2009 23:41:42 +0200 > Pawel Jakub Dawidek wrote: >=20 > > On Tue, Sep 15, 2009 at 08:44:04PM +0200, Tobias Lott wrote: > > > Any news on this? > >=20 > > Not really. I'm out of ideas. A way to repoduce it would be of course > > best. If you can't provide one maybe you remember something strange > > just before panic, like disk disappeared or something? > >=20 >=20 > Looks like I've found whats causing it by mounting all ZFS Volumes one > by one. It was a Volume used by a Jail running nginx, nagios and some > other stuff. > Weird but luckily not that important since its a Test Machine, can I > provide anything that you could figure out whats wrong with that Volume s= o it can be fixed? Cause I triggered > this only by upgrading BETA3->4 #3 r196936. What do you mean by 'ZFS Volume' here? You mean ZVOL as created with 'zfs create -V' command? Could you tell me exactly what steps should I take to reproduce the problem? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --orO6xySwJI16pVnm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKsQhIForvXbEpPzQRAlYtAKDIMK/l3IiNsfAI/1f4bTbA5KGlSACgk5Jf JGRpc0OVMe4rMy1R84EvOaw= =fbEN -----END PGP SIGNATURE----- --orO6xySwJI16pVnm-- From owner-freebsd-fs@FreeBSD.ORG Wed Sep 16 16:43:12 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F1531065672; Wed, 16 Sep 2009 16:43:12 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from spirit.gamesnet.de (spirit.gamesnet.de [87.230.101.86]) by mx1.freebsd.org (Postfix) with ESMTP id F2CBB8FC19; Wed, 16 Sep 2009 16:43:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTP id 112C829B013; Wed, 16 Sep 2009 18:42:40 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.gamesnet.de Received: from spirit.gamesnet.de ([127.0.0.1]) by localhost (spirit.gamesnet.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8TB7RT3eJ-oy; Wed, 16 Sep 2009 18:42:35 +0200 (CEST) Received: from mail.gamesnet.de (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTPA id 6030829B014; Wed, 16 Sep 2009 18:42:35 +0200 (CEST) Received: from 87.154.175.113 (proxying for 87.154.175.113) (SquirrelMail authenticated user tlott@gamesnet.de) by mail.gamesnet.de with HTTP; Wed, 16 Sep 2009 18:42:35 +0200 Message-ID: In-Reply-To: <20090916154616.GC1656@garage.freebsd.pl> References: <200909011005.18200.jhb@freebsd.org> <20090908214402.43009577@sub.han.vpn.gamesnet.de> <20090909001942.0affc96c@sub.han.vpn.gamesnet.de> <20090909054249.GH1539@garage.freebsd.pl> <20090909101346.01887a02@sub.han.vpn.gamesnet.de> <20090910215254.GD2718@garage.freebsd.pl> <102295df02d347c97bd098dc89ccb534.squirrel@mail.gamesnet.de> <20090915204404.79cf9325@sub.han.vpn.gamesnet.de> <20090915214142.GA2063@garage.freebsd.pl> <20090915235511.559550e5@sub.han.vpn.gamesnet.de> <20090916154616.GC1656@garage.freebsd.pl> Date: Wed, 16 Sep 2009 18:42:35 +0200 From: tlott@gamesnet.de To: "Pawel Jakub Dawidek" User-Agent: SquirrelMail/1.4.20 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Problems with ZFS on AMD64 (and i386 now) 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, 16 Sep 2009 16:43:12 -0000 > On Tue, Sep 15, 2009 at 11:55:11PM +0200, Tobias Lott wrote: >> >> >> On Tue, 15 Sep 2009 23:41:42 +0200 >> Pawel Jakub Dawidek wrote: >> >> > On Tue, Sep 15, 2009 at 08:44:04PM +0200, Tobias Lott wrote: >> > > Any news on this? >> > >> > Not really. I'm out of ideas. A way to repoduce it would be of course >> > best. If you can't provide one maybe you remember something strange >> > just before panic, like disk disappeared or something? >> > >> >> Looks like I've found whats causing it by mounting all ZFS Volumes one >> by one. It was a Volume used by a Jail running nginx, nagios and some >> other stuff. >> Weird but luckily not that important since its a Test Machine, can I >> provide anything that you could figure out whats wrong with that Volume >> so it can be fixed? Cause I triggered >> this only by upgrading BETA3->4 #3 r196936. > > What do you mean by 'ZFS Volume' here? You mean ZVOL as created with > 'zfs create -V' command? Could you tell me exactly what steps should I > take to reproduce the problem? > > -- > Pawel Jakub Dawidek http://www.wheel.pl > pjd@FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil ? Yes, I Am! > No sorry bad wording from my Side, its just a normal ZFS Filesystem (zfs create tank/filesystem) created some more Filesystem for more Jails on the same Machine yesterday. Couldn't reproduce it so far, so I guess it was just an update gone wrong with the result of one corrupted Filesystem. From owner-freebsd-fs@FreeBSD.ORG Thu Sep 17 07:44:17 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3CDA1065676 for ; Thu, 17 Sep 2009 07:44:17 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 732868FC19 for ; Thu, 17 Sep 2009 07:44:17 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id n8H7iCou019158 for ; Thu, 17 Sep 2009 09:44:13 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 3D66F24 for ; Thu, 17 Sep 2009 09:44:12 +0200 (CEST) Date: Thu, 17 Sep 2009 09:44:12 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-fs@freebsd.org Message-Id: <20090917094412.962e8729.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.9.17.73050 Subject: Fw: Linux/KDE and NFS locking on 7-stable 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, 17 Sep 2009 07:44:18 -0000 Hi, since I got exactly no reply on -stable, I try it again here. Please let me know if (and how :-) I can provide more information on this. cu Gerrit Begin forwarded message: Date: Mon, 14 Sep 2009 16:53:04 +0200 From: Gerrit K=FChn To: freebsd-stable@freebsd.org Subject: Linux/KDE and NFS locking on 7-stable Hi all, I upgraded a FreeBSD fileserver last week from 7.0-stable to 7.2-stable and experience some weird problems now with Linux NFS clients. The Linux Clients mount their home directories via nfs. I usually use "nolock" on the client side, because file locking was always troublesome in the past. On the Clients the users run kde 3.5 or 4.2. After the update of the server kde 3.5 quit starting up (after logging in with kdm) on the spalsh screen and comes up with some kind of I/O error when writing to the home dir. At the same time the server complains about kernel: NLM: failed to contact remote rpcbind, stat =3D 5, port =3D 28416 Any other window manager (xfce, icewm, mwm, twm) seems to work fine. Playing around with locking, udp/tcp, rebooting some times then somehow magically made it work with kde 3.5 again (although I am using the same mount options in the and as I used before): mclane:/tank/home/gco /tank/home/ghf nfs nfsvers=3D3,rw,nolock,nordirplus 0 0 Turning locking on definitely does not work (tried it three times). rcp.lockd and rpc.statd are running on the server side, no further tuning done there. KDE 4.2 seems to have better, I have been able to get it working with locking turned on (but it refused to work without locking with the same errors as described above for kde 3.5). I find the whole situation a bit unattractive. Can anybody here give me a hint which combination of mount options should work for a FreeBSD Server running 7.2-stable and Linux clients running 2.6.29 and KDE3/4? I am not that much into performance here, I want a stable working solution. And why, after all, is KDE so picky about locking and nfs homedirs anyway? All other environments appear not to show these problems. cu Gerrit _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Thu Sep 17 14:58:29 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C27B106580F for ; Thu, 17 Sep 2009 14:58:29 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 2B2188FC0C for ; Thu, 17 Sep 2009 14:58:28 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAM7rsUqDaFvJ/2dsb2JhbADfa4QYBQ X-IronPort-AV: E=Sophos;i="4.44,404,1249272000"; d="scan'208";a="48376373" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 17 Sep 2009 10:58:28 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 3ACC2FB80D6; Thu, 17 Sep 2009 10:58:28 -0400 (EDT) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2H-RHJ7nVgr; Thu, 17 Sep 2009 10:58:27 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 29FC2FB80A1; Thu, 17 Sep 2009 10:58:27 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8HF3t203162; Thu, 17 Sep 2009 11:03:55 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Thu, 17 Sep 2009 11:03:55 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: =?utf-8?B?R2Vycml0IEvDvGhu?= In-Reply-To: <20090917094412.962e8729.gerrit@pmp.uni-hannover.de> Message-ID: References: <20090917094412.962e8729.gerrit@pmp.uni-hannover.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-1253199835=:1169" Cc: freebsd-fs@freebsd.org Subject: Re: Fw: Linux/KDE and NFS locking on 7-stable 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, 17 Sep 2009 14:58:29 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-851401618-1253199835=:1169 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 17 Sep 2009, Gerrit K=C3=BChn wrote: > > I upgraded a FreeBSD fileserver last week from 7.0-stable to 7.2-stable > and experience some weird problems now with Linux NFS clients. > The Linux Clients mount their home directories via nfs. I usually use > "nolock" on the client side, because file locking was always troublesome > in the past. On the Clients the users run kde 3.5 or 4.2. > After the update of the server kde 3.5 quit starting up (after logging > in with kdm) on the spalsh screen and comes up with some kind of I/O erro= r > when writing to the home dir. At the same time the server complains about > > kernel: NLM: failed to contact remote rpcbind, stat =3D 5, port =3D 28416 > I think this happens when the nlm in the server tries to contact the client. I believe setting the following in the server's /etc/rc.conf and rebooting the server (or just killing off lockd on the server), combined with "nolock" as you have on the above Linux mount, might work ok: =09rpc_lockd_enable=3D"NO" =09rpc_statd_enable=3D"NO" Imo, the nlm protocol was poorly designed and has always resulted in interoperability problems. Although I fiddle with NFS, I avoid the NLM like the plague:-) Good luck with it, rick ps: If you need to run the lockd on the server, starting the lockd in the Linux client might help, although I'd still use "nolock" on the Linux mount. ---559023410-851401618-1253199835=:1169-- From owner-freebsd-fs@FreeBSD.ORG Thu Sep 17 18:14:12 2009 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 957431065672 for ; Thu, 17 Sep 2009 18:14:12 +0000 (UTC) (envelope-from mattjreimer@gmail.com) Received: from mail-px0-f192.google.com (mail-px0-f192.google.com [209.85.216.192]) by mx1.freebsd.org (Postfix) with ESMTP id 726218FC08 for ; Thu, 17 Sep 2009 18:14:12 +0000 (UTC) Received: by pxi30 with SMTP id 30so224397pxi.7 for ; Thu, 17 Sep 2009 11:14:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=I9AuUj9euB3/LQ44TfpzHVlVU2lcGWIhsvGNYN/jwjo=; b=fdNBjfbzF/tH414GrS5DKZF/ReF1AGO9FqgAN2eiQkSWtR1hZk5qNCBCvAIa91UOD2 tLfSUSGN13Vf927Kbml6YwA94vs/09ZP25encsV8PxELt/kdY0x+BxK9NtACG2mnwWM0 udOq0a+JJkIHVKe123Yql5USblo3CdVe03OAs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hehkc8J6/6WqqGNaFjKQxgmMYWDvuXvOcOhFapUonVjm4j1D5jHVsmAUxcu5jSlOtx LP/B44agvJq5V/B8/NH2pjpNpIWpOYua0GgQq9gLy/wT6Oj1JH91n69u4wS6GdbQ2res j2axVL6AWnbpzDqlzkV2/tWG+9jUd8/Vq4Muk= MIME-Version: 1.0 Received: by 10.142.151.16 with SMTP id y16mr18426wfd.46.1253209274268; Thu, 17 Sep 2009 10:41:14 -0700 (PDT) Date: Thu, 17 Sep 2009 10:41:14 -0700 Message-ID: From: Matt Reimer To: fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Can FreeBSD boot from a pool comprised of multiple vdevs? 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, 17 Sep 2009 18:14:12 -0000 Is FreeBSD able to boot from a pool comprised of multiple vdevs? If not, what would it take to get it working? I got 8.0-BETA4 booting from a pool comprised of a single raidz vdev, but when I added another raidz vdev it fails to boot with this error: ZFS: i/o error - all block copies unavailable ZFS: can't read object set for dataset lld Can't find root filesystem - giving up ZFS: unexpected object set type lld ZFS: unexpected object set type lld FreeBSD/i386 boot Default: glamdring:/boot/kernel/kernel boot: ZFS: unexpected object set type lld (Apparently loader's printf() doesn't understand %lld.) Boots successfully with gptzfsboot: # zpool status pool: glamdring state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM glamdring ONLINE 0 0 0 raidz1 ONLINE 0 0 0 label/glamdring-0.0 ONLINE 0 0 0 label/glamdring-0.1 ONLINE 0 0 0 label/glamdring-0.2 ONLINE 0 0 0 errors: No known data errors Does not boot: # zpool status pool: glamdring state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM glamdring ONLINE 0 0 0 raidz1 ONLINE 0 0 0 label/glamdring-0.0 ONLINE 0 0 0 label/glamdring-0.1 ONLINE 0 0 0 label/glamdring-0.2 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 label/glamdring-1.0 ONLINE 0 0 0 label/glamdring-1.1 ONLINE 0 0 0 label/glamdring-1.2 ONLINE 0 0 0 errors: No known data errors Thanks in advance. Matt From owner-freebsd-fs@FreeBSD.ORG Thu Sep 17 19:43:36 2009 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42FD6106566C for ; Thu, 17 Sep 2009 19:43:36 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-yw0-f191.google.com (mail-yw0-f191.google.com [209.85.211.191]) by mx1.freebsd.org (Postfix) with ESMTP id EDFA58FC20 for ; Thu, 17 Sep 2009 19:43:35 +0000 (UTC) Received: by ywh29 with SMTP id 29so595699ywh.7 for ; Thu, 17 Sep 2009 12:43:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=n1CR7y6FJuc/sYX2p1BS9ahzylOijC0JgKoYRjPn/U8=; b=W2LpMyKlFW4Q0ZWrQBjNMCK1pwlK8muLLAwdvn1JkKb8VJxSaTJ9P+1P2wmd1REUR3 X0K6igjrFgycjfg9qVID1C4Gi74iErXt0DZ4q4RCpew5Ie4V5C5BAN1Zac6REt7tNsxP BaL4x8ttaCblmJC1c6Gbb0IVDq+XNR3zNunfw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=j3bXuwMGMqX3XndHxC/9oEVMpQ43D5aV7Amo6qJhn47TtTeEMhBH4E1oNef1lKBVwV dSEsYR00YYIqX/w05ABFlZ9HoqjRa8mAmbZhSdaNcArAzX5NW8/DWycCBOqdAcCgI61F v72oKeyHVrQqFs+6iZtPHAtXmqnsemilapfzs= MIME-Version: 1.0 Sender: artemb@gmail.com Received: by 10.91.141.6 with SMTP id t6mr566023agn.49.1253214988196; Thu, 17 Sep 2009 12:16:28 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Sep 2009 12:16:28 -0700 X-Google-Sender-Auth: 355b581d86a78d88 Message-ID: From: Artem Belevich To: Matt Reimer , fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Can FreeBSD boot from a pool comprised of multiple vdevs? 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, 17 Sep 2009 19:43:36 -0000 Hi, I've just spent a bit of time investigating the same issue. There was a thread on -current in June that discussed ZFS booting issue and this email suggested that zfsboot does not support gang blocks. http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008589.html If I understand it correctly, gang blocks are used when ZFS can't (or does not want to) allocate contiguous block of required size, so the block is split in sub-blocks that in turn may be gang blocks. I.e. we're looking at a tree of blocks. If that's indeed the case, it implies that even on a single-disk system we may eventually run into a situation when newly installed kernel will be written using gang block and thus would not be handled correctly by zfsboot. That said, I've tried many possible combinations on a VirtualBox running 8.0BETA4 and most of them didn't work. Here's the summary: Zpool configurations I was able to boot from: * 1 disk * 1 mirror of 2 disks * 2 mirrors of 2 disks each * 2-disk raidz (kind of pointless, but..) Configurations that didn't work: * RAIDZ2 with 8 disks * RAIDZ2 with 4 disks * RAIDZ2 with 3 disks * RAIDZ with 8 disks * RAIDZ with 3 disks * 4 mirrors of 2 disks each * 3 mirrors of 3 disks each. Usually gptzfsboot complains that it can't read MOS. Striped multi-disk setups resulted in "can't find dsl_dir". I did some digging in case of RAIDZ2 booting failure and it does look that the failure happens because calculated checksum does not match expected one. Due to lack of my ZFS knowlegde I didn't get deeper than that. --Artem On Thu, Sep 17, 2009 at 10:41 AM, Matt Reimer wrote= : > Is FreeBSD able to boot from a pool comprised of multiple vdevs? If > not, what would it take to get it working? > > I got 8.0-BETA4 booting from a pool comprised of a single raidz vdev, > but when I added another raidz vdev it fails to boot with this error: > > ZFS: i/o error - all block copies unavailable > ZFS: can't read object set for dataset lld > Can't find root filesystem - giving up > ZFS: unexpected object set type lld > ZFS: unexpected object set type lld > > FreeBSD/i386 boot > Default: glamdring:/boot/kernel/kernel > boot: > ZFS: unexpected object set type lld > > (Apparently loader's printf() doesn't understand %lld.) > > Boots successfully with gptzfsboot: > > # zpool status > =A0pool: glamdring > =A0state: ONLINE > =A0scrub: none requested > config: > > =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 STATE =A0 =A0= READ WRITE CKSUM > =A0 =A0 =A0 =A0glamdring =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0ONLINE =A0 =A0 = =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0raidz1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ONLINE =A0 =A0 = =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-0.0 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-0.1 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-0.2 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > > errors: No known data errors > > Does not boot: > > # zpool status > =A0pool: glamdring > =A0state: ONLINE > =A0scrub: none requested > config: > > =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 STATE =A0 =A0= READ WRITE CKSUM > =A0 =A0 =A0 =A0glamdring =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0ONLINE =A0 =A0 = =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0raidz1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ONLINE =A0 =A0 = =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-0.0 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-0.1 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-0.2 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0raidz1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ONLINE =A0 =A0 = =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-1.0 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-1.1 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0label/glamdring-1.2 =A0ONLINE =A0 =A0 =A0 0 =A0 = =A0 0 =A0 =A0 0 > > errors: No known data errors > > Thanks in advance. > > Matt > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Fri Sep 18 07:14:38 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCDF31065679 for ; Fri, 18 Sep 2009 07:14:38 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7918FC14 for ; Fri, 18 Sep 2009 07:14:38 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id n8I7EZFU004020; Fri, 18 Sep 2009 09:14:36 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 47E5024; Fri, 18 Sep 2009 09:14:35 +0200 (CEST) Date: Fri, 18 Sep 2009 09:14:35 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Rick Macklem Message-Id: <20090918091435.465bfc1e.gerrit@pmp.uni-hannover.de> In-Reply-To: References: <20090917094412.962e8729.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.9.18.70621 Cc: freebsd-fs@freebsd.org Subject: Re: Fw: Linux/KDE and NFS locking on 7-stable 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: Fri, 18 Sep 2009 07:14:38 -0000 On Thu, 17 Sep 2009 11:03:55 -0400 (EDT) Rick Macklem wrote about Re: Fw: Linux/KDE and NFS locking on 7-stable: RM> > I upgraded a FreeBSD fileserver last week from 7.0-stable to RM> > 7.2-stable and experience some weird problems now with Linux NFS RM> > clients. The Linux Clients mount their home directories via nfs. I RM> > usually use "nolock" on the client side, because file locking was RM> > always troublesome in the past. On the Clients the users run kde 3.5 RM> > or 4.2. After the update of the server kde 3.5 quit starting up RM> > (after logging in with kdm) on the spalsh screen and comes up with RM> > some kind of I/O error when writing to the home dir. At the same RM> > time the server complains about RM> > kernel: NLM: failed to contact remote rpcbind, stat = 5, port = 28416 RM> I think this happens when the nlm in the server tries to contact the RM> client. ??? My NFS-Clients are accessing the server via a NAT router. There is no way the server could contact the clients. RM> I believe setting the following in the server's /etc/rc.conf RM> and rebooting the server (or just killing off lockd on the server), RM> combined with "nolock" as you have on the above Linux mount, might RM> work ok: RM> rpc_lockd_enable="NO" RM> rpc_statd_enable="NO" I did not try that so far, as there are some clients which seem to work fine with locking. RM> Imo, the nlm protocol was poorly designed and has always resulted in RM> interoperability problems. Although I fiddle with NFS, I avoid the NLM RM> like the plague:-) Seems so. Why would one want to have a server contact a client anyway? :-) Yesterday I played around with it some more, and have a solution now (at least I hope so :-) with combining "nolock" with "tcp" on the client side. I read some oder mails (from you?) here that stated problems with the new server and strange combinations of mounting via udp and accessing via tcp (although I did not look up what the Linux clients actually do). Before I had either no protocol setting for the clients or they were explicitely using udp (because that solved the problems I had with locking when I was still using 7.0-stable :-). RM> Good luck with it, rick RM> ps: If you need to run the lockd on the server, starting the lockd in RM> the Linux client might help, although I'd still use "nolock" on RM> the Linux mount. I think statd is running on the Linux client anyway. Will have to look for lockd. Thanks for the hints. I still wonder a bit why nfs/locking is often so much of a hassle. Shouldn't it be some kind of established standard technique after all the years? Not that I would want to use smb instead, but still... btw: are there any alternatives? cu Gerrit From owner-freebsd-fs@FreeBSD.ORG Fri Sep 18 13:42:25 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 462061065670; Fri, 18 Sep 2009 13:42:25 +0000 (UTC) (envelope-from ed@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1CE8A8FC0C; Fri, 18 Sep 2009 13:42:25 +0000 (UTC) Received: from freefall.freebsd.org (ed@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8IDgPH2085979; Fri, 18 Sep 2009 13:42:25 GMT (envelope-from ed@freefall.freebsd.org) Received: (from ed@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8IDgOH3085975; Fri, 18 Sep 2009 13:42:24 GMT (envelope-from ed) Date: Fri, 18 Sep 2009 13:42:24 GMT Message-Id: <200909181342.n8IDgOH3085975@freefall.freebsd.org> To: ed@FreeBSD.org, freebsd-fs@FreeBSD.org, rmacklem@FreeBSD.org From: ed@FreeBSD.org Cc: Subject: Re: kern/131995: [nfs] Failure to mount NFSv4 server 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: Fri, 18 Sep 2009 13:42:25 -0000 Synopsis: [nfs] Failure to mount NFSv4 server Responsible-Changed-From-To: freebsd-fs->rmacklem Responsible-Changed-By: ed Responsible-Changed-When: Fri Sep 18 13:41:51 UTC 2009 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=131995 From owner-freebsd-fs@FreeBSD.ORG Fri Sep 18 13:42:56 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CEF8106568D; Fri, 18 Sep 2009 13:42:56 +0000 (UTC) (envelope-from ed@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 73B8A8FC1E; Fri, 18 Sep 2009 13:42:56 +0000 (UTC) Received: from freefall.freebsd.org (ed@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8IDgu47086030; Fri, 18 Sep 2009 13:42:56 GMT (envelope-from ed@freefall.freebsd.org) Received: (from ed@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8IDgunf086026; Fri, 18 Sep 2009 13:42:56 GMT (envelope-from ed) Date: Fri, 18 Sep 2009 13:42:56 GMT Message-Id: <200909181342.n8IDgunf086026@freefall.freebsd.org> To: ed@FreeBSD.org, rmacklem@FreeBSD.org, freebsd-fs@FreeBSD.org From: ed@FreeBSD.org Cc: Subject: Re: kern/131995: [nfs] Failure to mount NFSv4 server 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: Fri, 18 Sep 2009 13:42:56 -0000 Synopsis: [nfs] Failure to mount NFSv4 server Responsible-Changed-From-To: rmacklem->freebsd-fs Responsible-Changed-By: ed Responsible-Changed-When: Fri Sep 18 13:42:28 UTC 2009 Responsible-Changed-Why: Woops! Better put it back on fs@. It looks like this has something to do with the old NFS implementation. http://www.freebsd.org/cgi/query-pr.cgi?pr=131995 From owner-freebsd-fs@FreeBSD.ORG Fri Sep 18 14:51:31 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA7741065679 for ; Fri, 18 Sep 2009 14:51:31 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 78B468FC15 for ; Fri, 18 Sep 2009 14:51:31 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAPc6s0qDaFvI/2dsb2JhbADPSYQcBYFY X-IronPort-AV: E=Sophos;i="4.44,410,1249272000"; d="scan'208";a="46792361" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 18 Sep 2009 10:51:29 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 9FEB394006C; Fri, 18 Sep 2009 10:51:29 -0400 (EDT) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zCw2Cl5NtlP2; Fri, 18 Sep 2009 10:51:28 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id E7BCD940063; Fri, 18 Sep 2009 10:51:27 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8IEuxi24876; Fri, 18 Sep 2009 10:56:59 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 18 Sep 2009 10:56:59 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: =?utf-8?B?R2Vycml0IEvDvGhu?= In-Reply-To: <20090918091435.465bfc1e.gerrit@pmp.uni-hannover.de> Message-ID: References: <20090917094412.962e8729.gerrit@pmp.uni-hannover.de> <20090918091435.465bfc1e.gerrit@pmp.uni-hannover.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1903590565-1253285819=:15785" Cc: freebsd-fs@freebsd.org Subject: Re: Fw: Linux/KDE and NFS locking on 7-stable 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: Fri, 18 Sep 2009 14:51:31 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-1903590565-1253285819=:15785 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 18 Sep 2009, Gerrit K=C3=BChn wrote: > > ??? > My NFS-Clients are accessing the server via a NAT router. There is no way > the server could contact the clients. > First off, I'll note that I'm not particularily familiar with the NLM and NSM protocols, so take all of this with a grain of salt. My understanding is: - The server calls does a callback to the client when a blocking lock can be granted, if there was a conflicting lock held at the time of the lock request. - The NSM protocol tries to determine when machines have crashed. When a server reboots it will try to notify clients that it has rebooted. (I don't know the protocol well enough to know if there is any other time the server needs to be able to contact the client.) > RM> I believe setting the following in the server's /etc/rc.conf > RM> and rebooting the server (or just killing off lockd on the server), > RM> combined with "nolock" as you have on the above Linux mount, might > RM> work ok: > RM> =09rpc_lockd_enable=3D"NO" > RM> =09rpc_statd_enable=3D"NO" > > I did not try that so far, as there are some clients which seem to work > fine with locking. > > RM> Imo, the nlm protocol was poorly designed and has always resulted in > RM> interoperability problems. Although I fiddle with NFS, I avoid the NL= M > RM> like the plague:-) > > Seems so. Why would one want to have a server contact a client anyway? :-= ) For locking correctness, I would agree. For NFSv4, locking should work correctly without a callback network path. For blocking locks, the client must retry the lock request until it succeeds. For recovery, the client discovers that the server has rebooted via error codes returned from the server for open/byte range lock operations. My issues w.r.t. the NLM are: - For the blocking lock, the client is depending on the server to do a callback to let it know when it has the lock. Beyond your NAT case, there are issues related to network partitioning, server crashes,... - It also depends on the NSM to notify it that a server/client has crashed, rebooted, been network partitioned,... (my understanding of it is that a machine basically sends a notify of state to other machines that it thinks cares. If the messages get lost...) > Yesterday I played around with it some more, and have a solution now (at > least I hope so :-) with combining "nolock" with "tcp" on the client side= =2E > I read some oder mails (from you?) here that stated problems with the new > server and strange combinations of mounting via udp and accessing via tcp > (although I did not look up what the Linux clients actually do). > Before I had either no protocol setting for the clients or they were > explicitely using udp (because that solved the problems I had with lockin= g > when I was still using 7.0-stable :-). > > RM> Good luck with it, rick > RM> ps: If you need to run the lockd on the server, starting the lockd in > RM> the Linux client might help, although I'd still use "nolock" on > RM> the Linux mount. > > I think statd is running on the Linux client anyway. Will have to look fo= r > lockd. Thanks for the hints. I still wonder a bit why nfs/locking is ofte= n > so much of a hassle. Shouldn't it be some kind of established standard > technique after all the years? Not that I would want to use smb instead, > but still... btw: are there any alternatives? > NFSv2 and 3 are stateless server protocols (no state to recover after a server crash/reboot) and since file locking is by definition "state", there was no locking support. Sun added the separate protocols NLM and=20 NSM to provide locking support for NFS mounted volumes. These were all that was available prior to NFSv4 (which has integrated byte range=20 locking and is not a stateless server). Beyond the fact that I think they= =20 were poorly designed protocols, they weren't well published. The only=20 description I am aware of is in "Protocols for X/Open Internetworking:=20 XNFS, Issue 4", which I had to buy for around $75 in 1993. I don't know if= =20 it has ever been put online and even it didn't describe the semantics very= =20 well, imho. (This delay in publication combined with my opinion on the protocols was why I never implemented them.) rick ---559023410-1903590565-1253285819=:15785-- From owner-freebsd-fs@FreeBSD.ORG Fri Sep 18 17:57:11 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E54901065670 for ; Fri, 18 Sep 2009 17:57:10 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 75B8D8FC19 for ; Fri, 18 Sep 2009 17:57:10 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 16so502212fgg.13 for ; Fri, 18 Sep 2009 10:57:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=MOXvSDyQ0R08x+JzI2vqJgVIOOtDYws5AuI91kn8FEo=; b=wDCn1ppEU30t5OWr99ANBTLyRo+I9HQ6SXvKvtC+xwaHf4j/xTNXpynP1hMpA9u6V9 GAwW91++w/4W5e+bSrgaKuLXs7in6ce9V+B1l1EAXWcsXmeNydZWCGSAJaTrlOdV9MRJ UxTgpAH71QiTbyIaaxzO21sAxy/+2Wke+vnD8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=lbOgeBRP4RDrl68JfkCH2owuKQX9yKd+K7WVExnPj9fjYXROTjzXw3b0ENzqZ3bTri kOyqCTsg7WUrXg+oXjMlV89ZrMtqwOym0tpv6Zqlonz7UfnyX1pqTq/4Z/xmLS21Iznc kFMC5uX38RPceUZLsDTsBSZ/j1HYHF31jbP7s= Received: by 10.86.18.34 with SMTP id 34mr2007250fgr.2.1253294914345; Fri, 18 Sep 2009 10:28:34 -0700 (PDT) Received: from localhost (lan-78-157-90-54.vln.skynet.lt [78.157.90.54]) by mx.google.com with ESMTPS id l12sm111061fgb.20.2009.09.18.10.28.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 18 Sep 2009 10:28:33 -0700 (PDT) Date: Fri, 18 Sep 2009 20:28:16 +0300 From: Gleb Kurtsou To: freebsd-fs@freebsd.org Message-ID: <20090918172816.GA1449@tops> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Pawel Jakub Dawidek Subject: [patch] tmpfs mmap sync bug fix 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: Fri, 18 Sep 2009 17:57:11 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline [ pjd@ CCed to make sure it doesn't apply to zfs ] Mmaped pages can get out of sync in tmpfs. The bug is 100% reproducible by: # fsx -S 125 -d /tmpfs/file It breaks at operation 42. Fix is inspired by zfs, it calls vm_page_cache_free(). Reading zfs sources, it looks like it doesn't check v_object->cache, but never the less bug never shows up on there. Probably it's because of zfs using VOP_BMAP to do page mapping. tmpfs uses default vop_getpages/vop_putpages which invokes vop_read/vop_write accordingly. Removing v_object->cache == NULL checks breaks things again. I'm not entirely sure if it's correct fix and would appreciate vm guru having a look at it, because I do the same thing in my pefs filesystem and It works as expected for me: http://blogs.freebsdish.org/gleb/2009/09/16/pefs-benchmark/ Thank, Gleb. --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=utf-8 Content-Disposition: attachment; filename="tmpfs-mmap-sync.patch.txt" diff --git a/sys/fs/tmpfs/tmpfs_vnops.c b/sys/fs/tmpfs/tmpfs_vnops.c index db8ceea..59d94d7 100644 --- a/sys/fs/tmpfs/tmpfs_vnops.c +++ b/sys/fs/tmpfs/tmpfs_vnops.c @@ -444,7 +444,8 @@ tmpfs_mappedread(vm_object_t vobj, vm_object_t tobj, size_t len, struct uio *uio offset = addr & PAGE_MASK; tlen = MIN(PAGE_SIZE - offset, len); - if ((vobj == NULL) || (vobj->resident_page_count == 0)) + if ((vobj == NULL) || + (vobj->resident_page_count == 0 && vobj->cache == NULL)) goto nocache; VM_OBJECT_LOCK(vobj); @@ -555,7 +556,8 @@ tmpfs_mappedwrite(vm_object_t vobj, vm_object_t tobj, size_t len, struct uio *ui offset = addr & PAGE_MASK; tlen = MIN(PAGE_SIZE - offset, len); - if ((vobj == NULL) || (vobj->resident_page_count == 0)) { + if ((vobj == NULL) || + (vobj->resident_page_count == 0 && vobj->cache == NULL)) { vpg = NULL; goto nocache; } @@ -573,6 +575,8 @@ lookupvpg: VM_OBJECT_UNLOCK(vobj); error = uiomove_fromphys(&vpg, offset, tlen, uio); } else { + if (__predict_false(vobj->cache != NULL)) + vm_page_cache_free(vobj, idx, idx + 1); VM_OBJECT_UNLOCK(vobj); vpg = NULL; } --Qxx1br4bt0+wmkIi-- From owner-freebsd-fs@FreeBSD.ORG Fri Sep 18 22:39:15 2009 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D743C106566B for ; Fri, 18 Sep 2009 22:39:15 +0000 (UTC) (envelope-from Ektron@weic15.com) Received: from wic120.worldatamail.com (wic120.worldatamail.com [198.172.143.120]) by mx1.freebsd.org (Postfix) with ESMTP id 896178FC1C for ; Fri, 18 Sep 2009 22:39:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=dk1; d=weic15.com; h=Content-type:From:To:Subject:Date; i=Ektron@weic15.com; bh=CP07DjGkpfHxmDcT5LIG2ciug78=; b=XrbEvajjEym1xDBgBMUYModIlnlS4sUpEmzyDH0gdvvIqWt+VK13AxjwWnhnFzjp/2vArLhke/k4 QUzLKhJvyKJbWUSs0+0id4653lp5nOMM5hUlquH9R+/DQOpr/1d3PlMTNXEUsNdxU0Vt52P7t0uX 2x3z6dPBWSVp+UjgBxo= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=dk1; d=weic15.com; b=Qx/LrDXoMkZtk25T4GeAkkKvPP7ijvUAyzksWehYppYI6ESMhxk7CPrBGGy2A9yo1fmf6kaKILl9 Xy+luBz5VctF4kbSUWtXr3gRb/vvadCjKXwuvCwoC6wQBCFL2V0MVuflktLSjJ31E/nSfnIQSrJ9 7GWMBRz4WR2E/BM6GZw=; Received: from weic15.com (192.168.200.81) by wic120.worldatamail.com (PowerMTA(TM) v3.5r8) id hmg5pe0jg446 for ; Fri, 18 Sep 2009 16:31:45 -0400 (envelope-from ) From: "Ektron" To: fs@freebsd.org Date: Fri, 18 Sep 2009 16:31:45 -0400 Message-Id: <20090918223915.D743C106566B@hub.freebsd.org> Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Download this Web 2.0 Solution for your site - Instant Demo 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: Fri, 18 Sep 2009 22:39:15 -0000 Ektron CMS400.NET provides a complete content management platform with built in SEO management features to ensure your Web site is prepared for the search engines! --------------------------- Register Now for an Instant Demo! (http://www.weic15.com/ets/clk.asp?82255X1M1883803) --------------------------- What if you could... Empower marketing teams to build Web pages on the fly, without sacrificing feature set or control Utilize the extensive out-of-the box features or take advantage of the open architecture Easily build and offer wikis, blogs, forums and the latest in social networking Eliminate risky glue code and make the most of your WCM investment with an integrated e-commerce platform Provide top tier results with our new enterprise search Easily offer RSS, secure subscriptions and web alerts Synchronize content, functionality and membership data securely, from staging to production and back. --------------------------- Register Now for an Instant Demo! (http://www.weic15.com/ets/clk.asp?82255X1M1883803) --------------------------- If you do not want to receive emails from Ektron, please send an email by clicking here (mailto:optout@ektron.com?subject=remove). Ektron, Inc . 542 Amherst Street . Nashua, NH 03063 . +1 (866) 4-EKTRON BizProGuide.com - The Resource for Business Professionals [ fs@freebsd.org ] The preceding is vendor information. If you no longer want to receive this type of information you may indicate that here http://www.weic15.com/r/rm.asp?m=fqqCqKC&o=qZZYY&j=gnKqZb&t=2&e=fs@freebsd.org 1883803