From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 00:32:19 2010 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 4CC051065677 for ; Sun, 1 Aug 2010 00:32:19 +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 0541A8FC1C for ; Sun, 1 Aug 2010 00:32:18 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEANddVEyDaFvO/2dsb2JhbACDE54FrTKQTYEmgyBzBIh/ X-IronPort-AV: E=Sophos;i="4.55,296,1278302400"; d="scan'208";a="86942036" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 31 Jul 2010 20:32:14 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 0E17EB3E96; Sat, 31 Jul 2010 20:32:17 -0400 (EDT) Date: Sat, 31 Jul 2010 20:32:16 -0400 (EDT) From: Rick Macklem To: Joe Auty Message-ID: <763314735.215468.1280622736448.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4C4FDCCD.1080904@netmusician.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: NFSv4 permissions issues 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, 01 Aug 2010 00:32:19 -0000 From: "Joe Auty" > To: freebsd-fs@freebsd.org > Sent: Wednesday, July 28, 2010 3:31:25 AM > Subject: NFSv4 permissions issues > > Hello, > > In FreeBSD 8.1 when mounting an NFSv4 share (hosted by Solaris 10/ZFS) I > cannot create or alter any files on this share nor any other share > mounted from this same ZFS server. When I try to do so I get permission > denied error messages. This same share does not give me any problems > when mounted with identical mount options except for specifying NFSv3 > rather than NFSv4... i.e. > > mount -t nfs -o rw,tcp,intr,noatime,nfsv3 myip:/path /path > > works fine, and: > > mount -t nfs -o rw,tcp,intr,noatime,nfsv4 myip:/path /path > > exhibits the above problems... > > > Any idea why this is so and what I ought to do to test using NFSv4 on > this machine? 1 - look to see if the username/groupname mappings are working. (NFSv4 uses name and not#s.) - just do an "ls -lg" on some NFSv4 mounted dir. to see if they look ok. (lotsa "nobdy"'s --> busted) If it's busted, look at the setup of nfsuserd and the "domain" specified, which is usually the domain part of the host's name, but can be overridden by a flag option on nfsuserd and in a config file on Solaris10. 2 - Make sure you user/group names and uid/gid numbers are consistent between client and server. NFSv4 always specifies the groupname of a newly created file object, so those groups/gids must be correct. If the above doesn't resolve it, look at a snoop trace for the failed access and see what the user/group names (and uid/gid #s in the RPC header) look like. This is most likely something related to the user/group name and number mapping, rick From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 01:07:47 2010 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 AA13B1065674 for ; Sun, 1 Aug 2010 01:07:47 +0000 (UTC) (envelope-from joe@netmusician.org) Received: from mail.netmusician.org (dorian.netmusician.org [66.244.95.101]) by mx1.freebsd.org (Postfix) with ESMTP id 6E8818FC0C for ; Sun, 1 Aug 2010 01:07:47 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by mail.netmusician.org (Postfix) with ESMTP id 9AE6EB8A6; Sat, 31 Jul 2010 21:07:46 -0400 (EDT) X-Virus-Scanned: amavisd-new at netmusician.org Received: from mail.netmusician.org ([127.0.0.1]) by localhost (dorian.netmusician.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 5y-GDoxZskjh; Sat, 31 Jul 2010 21:07:46 -0400 (EDT) Received: from Shakti.local (c-67-176-145-181.hsd1.in.comcast.net [67.176.145.181]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.netmusician.org (Postfix) with ESMTPSA id B816EB8A5; Sat, 31 Jul 2010 21:07:45 -0400 (EDT) Message-ID: <4C54C8E0.8020504@netmusician.org> Date: Sat, 31 Jul 2010 21:07:44 -0400 From: Joe Auty User-Agent: Postbox 1.1.5 (Macintosh/20100613) MIME-Version: 1.0 To: Rick Macklem References: <763314735.215468.1280622736448.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <763314735.215468.1280622736448.JavaMail.root@erie.cs.uoguelph.ca> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: NFSv4 permissions issues 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, 01 Aug 2010 01:07:47 -0000 Rick Macklem wrote: > From: "Joe Auty" > >> To: freebsd-fs@freebsd.org >> Sent: Wednesday, July 28, 2010 3:31:25 AM >> Subject: NFSv4 permissions issues >> >> Hello, >> >> In FreeBSD 8.1 when mounting an NFSv4 share (hosted by Solaris 10/ZFS) I >> cannot create or alter any files on this share nor any other share >> mounted from this same ZFS server. When I try to do so I get permission >> denied error messages. This same share does not give me any problems >> when mounted with identical mount options except for specifying NFSv3 >> rather than NFSv4... i.e. >> >> mount -t nfs -o rw,tcp,intr,noatime,nfsv3 myip:/path /path >> >> works fine, and: >> >> mount -t nfs -o rw,tcp,intr,noatime,nfsv4 myip:/path /path >> >> exhibits the above problems... >> >> >> Any idea why this is so and what I ought to do to test using NFSv4 on >> this machine? >> > > 1 - look to see if the username/groupname mappings are working. (NFSv4 > uses name and not#s.) > - just do an "ls -lg" on some NFSv4 mounted dir. to see if they > look ok. (lotsa "nobdy"'s --> busted) If it's busted, look at > the setup of nfsuserd and the "domain" specified, which is > usually the domain part of the host's name, but can be overridden > by a flag option on nfsuserd and in a config file on Solaris10. > > 2 - Make sure you user/group names and uid/gid numbers are consistent > between client and server. NFSv4 always specifies the groupname > of a newly created file object, so those groups/gids must be > correct. > > If the above doesn't resolve it, look at a snoop trace for the failed > access and see what the user/group names (and uid/gid #s in the RPC > header) look like. > > This is most likely something related to the user/group name and > number mapping, rick > At the time the user/groups were showing up as root:joe. Doing a chown as root would not generate an error message, it just simply did not work. There are no numbers appearing the user/group assignments, and these same permissions work fine when the share is mounted as NFSv3, for whatever reason. Because I gave root read and write permissions, I should be able to change the permissions to whatever I want on the client end, right? Is snoop trace an strace? -- Joe Auty, NetMusician NetMusician helps musicians, bands and artists create beautiful, professional, custom designed, career-essential websites that are easy to maintain and to integrate with popular social networks. www.netmusician.org joe@netmusician.org From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 01:58:02 2010 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 D89661065672 for ; Sun, 1 Aug 2010 01:58:02 +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 94E798FC12 for ; Sun, 1 Aug 2010 01:58:02 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAFVxVEyDaFvO/2dsb2JhbACDE54FrHmQRoEmgyBzBIh/ X-IronPort-AV: E=Sophos;i="4.55,296,1278302400"; d="scan'208";a="89097351" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 31 Jul 2010 21:57:59 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id C8BACB3F11; Sat, 31 Jul 2010 21:58:01 -0400 (EDT) Date: Sat, 31 Jul 2010 21:58:01 -0400 (EDT) From: Rick Macklem To: Joe Auty Message-ID: <235033195.215985.1280627881678.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4C54C8E0.8020504@netmusician.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - FF3.0 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: NFSv4 permissions issues 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, 01 Aug 2010 01:58:02 -0000 [stuff snipped for brevity] > At the time the user/groups were showing up as root:joe. > Ok, so an "ls -lg" on the NFSv4 mounted volume showed the files owned by root/joe? If so, nfsuserd seems to be working. Does root and joe have the same uid and gid #s on the client and server. NFSv4 will be pickier about the gid, so make sure joe is in both the client and server as the same gid#. > Is snoop trace an strace? > I was referring to using snoop to capture packets and then look at them. On Solaris I use something like: # snoop -q -o xx.cap host - I run an offending command(s), then kill the above and: # snoop -t r -v -i xx.cap > xx The file "xx" now has a verbose description of the packets. Take a look at the AUTH_SYS part of the RPC header (where the uid and gids live) and the various attributes in the request that probably failed with NFS4ERR_ACCESS. Alternately, you can use wireshark. (tcpdump knows diddly about NFSv4, so it can only be used for the packet capture and not the analysis. rick From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 16:42:09 2010 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 7E39A1065673; Sun, 1 Aug 2010 16:42:09 +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 542818FC12; Sun, 1 Aug 2010 16:42:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o71Gg9r9034618; Sun, 1 Aug 2010 16:42:09 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o71Gg9Dn034614; Sun, 1 Aug 2010 16:42:09 GMT (envelope-from linimon) Date: Sun, 1 Aug 2010 16:42:09 GMT Message-Id: <201008011642.o71Gg9Dn034614@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/149173: [patch] [zfs] make OpenSolaris installable 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, 01 Aug 2010 16:42:09 -0000 Synopsis: [patch] [zfs] make OpenSolaris installable Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sun Aug 1 16:41:53 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=149173 From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 18:54:53 2010 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 21A8C106566C for ; Sun, 1 Aug 2010 18:54:53 +0000 (UTC) (envelope-from scottj75074@yahoo.com) Received: from web110705.mail.gq1.yahoo.com (web110705.mail.gq1.yahoo.com [67.195.13.212]) by mx1.freebsd.org (Postfix) with SMTP id E536F8FC1C for ; Sun, 1 Aug 2010 18:54:52 +0000 (UTC) Received: (qmail 58568 invoked by uid 60001); 1 Aug 2010 18:28:11 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1280687291; bh=m6c7LTztEhC1bJxu1X7IRdb/1xdJYLdNvilLmTCbRGw=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=c+sjaH7MAGyW7aI9YGcJTBuVDv5hdOEM8azr0bRw5717yLQ/GjqEpxazyN+QKrNYUvkzKGiA+agTMG6mcwcasCku3BccxqydA9GpZFyqVaWBM6IOUz7WVnnBTBTp+TF+7Qvh0YGta+0w6nMlzsdnGhq05ktvZfiugLy1psGB42Y= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=JqTVPs1PVm4UCiGqOZfmf/fqG6MOglO6kmJQRQaHjoaXUPNEbEw6InvFYv7WJJJqkrlTHw7YvP98HeJ0eCqkQLiw2cGZMU+KoIN6n3mIjhzAk3VghRckXjD9RRAyGLSaWvLDlmwPN7VKlgiOya25M3YDr6cgCZ+IlclWdtUNhPs=; Message-ID: <106301.57870.qm@web110705.mail.gq1.yahoo.com> X-YMail-OSG: ZEAVLbwVM1ksCQHc.aTixLQVoNfH5wfAZeDskZH6Ac6ydlK fmSU0fAyVoXpEVUU7EujPDX_ujo.qpLahzjwdLVDzc8DytOUPnMhu6QWYwD2 RwLJoPqzbhUR0eJqb0CfCcNVZLyUHBYSkD_XoBeM8JtmaCcHcvzm3V.XbFgL o92IBXUxgzmiEGyvxqsdQmnIZ11FRp66keOO697BQbraGaiPexosrqQHLot1 kyAp5YdRRzFALHZQ1.Z2vH8IAJT6XsoXNBA0U38pHKZi3_MtmoQ9bjoE3osu 6MeY5b0NySYbA9ByRXm7uCrm6BJKkU8wvHP0qUE2uiBo4IUs4FZZbYdakSU3 GqP_TCq5xI7eneZcnc.WSuu7mxvNO Received: from [24.6.145.200] by web110705.mail.gq1.yahoo.com via HTTP; Sun, 01 Aug 2010 11:28:10 PDT X-Mailer: YahooMailRC/420.4 YahooMailWebService/0.8.105.279950 Date: Sun, 1 Aug 2010 11:28:10 -0700 (PDT) From: Scott Johnson To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ZFS mirror boot: cannot boot from 2nd 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, 01 Aug 2010 18:54:53 -0000 I installed 8.1-RELEASE onto two identical drives in a mirror, following the "Installing FreeBSD Root on ZFS (Mirror) using GPT" guide here: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror I can boot from either disk by changing the boot priority in the BIOS, so long as both disks are connected. I swapped the sata ports, and I can still boot from either disk. I can disconnect drive #2 and boot from drive #1 just fine, whether drive #1 is plugged into sata0 or sata1. However when I disconnect drive #1 and try to boot from drive #2, on either sata0 or sata1, I get errors: error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 No ZFS pools located, can't boot It looks like a hardware problem, but then why does disk #2 work when disk #1 is connected? (Note, if both are plugged in, everything works fine; zpool status is clean, zpool scrub is clean, SMART status is good after long self-test.) From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 19:09:45 2010 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 B7D101065674 for ; Sun, 1 Aug 2010 19:09:45 +0000 (UTC) (envelope-from prvs=1829ff4ae6=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 4F58F8FC08 for ; Sun, 1 Aug 2010 19:09:45 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Sun, 01 Aug 2010 19:58:20 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 01 Aug 2010 19:58:19 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50010936058.msg for ; Sun, 01 Aug 2010 19:58:19 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1829ff4ae6=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@FreeBSD.ORG Message-ID: From: "Steven Hartland" To: Date: Sun, 1 Aug 2010 19:58:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 Cc: Subject: ZFS diff support on FreeBSD 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, 01 Aug 2010 19:09:45 -0000 I cant seem to track down the correlation of various ZFS features that are present in Solaris and the corresponding FreeBSD versions. I'm interested in the zfs diff command. Could anyone tell me where this info is, or do they know off hand when we're likely to see this added to the FreeBSD implementation of zfs? http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 19:23:57 2010 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 CA6271065670 for ; Sun, 1 Aug 2010 19:23:57 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id B13A18FC0C for ; Sun, 1 Aug 2010 19:23:57 +0000 (UTC) Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta14.emeryville.ca.mail.comcast.net with comcast id p6vL1e0041ZMdJ4AE7PxEC; Sun, 01 Aug 2010 19:23:57 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta16.emeryville.ca.mail.comcast.net with comcast id p7Pw1e0053LrwQ28c7Pwvn; Sun, 01 Aug 2010 19:23:56 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 0D3039B425; Sun, 1 Aug 2010 12:23:56 -0700 (PDT) Date: Sun, 1 Aug 2010 12:23:56 -0700 From: Jeremy Chadwick To: Scott Johnson Message-ID: <20100801192355.GA77061@icarus.home.lan> References: <106301.57870.qm@web110705.mail.gq1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <106301.57870.qm@web110705.mail.gq1.yahoo.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS mirror boot: cannot boot from 2nd 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, 01 Aug 2010 19:23:57 -0000 On Sun, Aug 01, 2010 at 11:28:10AM -0700, Scott Johnson wrote: > I installed 8.1-RELEASE onto two identical drives in a mirror, following the > "Installing FreeBSD Root on ZFS (Mirror) using GPT" guide here: > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror > > I can boot from either disk by changing the boot priority in the BIOS, so long > as both disks are connected. I swapped the sata ports, and I can still boot from > either disk. > > I can disconnect drive #2 and boot from drive #1 just fine, whether drive #1 is > plugged into sata0 or sata1. > > However when I disconnect drive #1 and try to boot from drive #2, on either > sata0 or sata1, I get errors: > > error 1 lba 32 > error 1 lba 1 > error 1 lba 32 > error 1 lba 1 > error 1 lba 32 > error 1 lba 1 > error 1 lba 32 > error 1 lba 1 > error 1 lba 32 > error 1 lba 1 > error 1 lba 32 > error 1 lba 1 > No ZFS pools located, can't boot > > It looks like a hardware problem, but then why does disk #2 work when disk #1 is > connected? It's not a hardware problem. > (Note, if both are plugged in, everything works fine; zpool status is clean, > zpool scrub is clean, SMART status is good after long self-test.) The problem is known, but I haven't seen any word from developers on the lists as to whether or not a fix is underway. PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=148655 Post: http://lists.freebsd.org/pipermail/freebsd-fs/2010-July/009008.html I expect more users to start reporting this issue, as it's quite major/serious. It should probably be added to the 8.1-RELEASE Errata given its severity. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 19:52:30 2010 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 34C5E106566B for ; Sun, 1 Aug 2010 19:52:30 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id DDE508FC20 for ; Sun, 1 Aug 2010 19:52:29 +0000 (UTC) Received: by qwk3 with SMTP id 3so1349190qwk.13 for ; Sun, 01 Aug 2010 12:52:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=sM7L2NtL9r7TpI1Y/xF7ahigX+H2Jxv6ZyLFvCmgj8U=; b=ISzxbYitqCS00sO1Xa29MFkuvpurLAfxRvSUOqJV47wqnqaoET/+LcA8jB3MJrDO2i 86e4MqVYKq3udBj5Q+pdHu6nN18ErqwvXpGAOuzsbXSnbDDh+/qp101iRbs6cv6OIKua GRcIlDVJKtfMV/DKS/XMBenK785OJm5eSRgSg= 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=WHYYSH5XoX5u1zX7kDAwLjm6OogjgLdsHiHmXDQPw5HbaphzoutcbL/j006hE3gTNg njssCpVBKNU5JmnSj/BP3hnTBdma3AR9wu8VTxVufdu0pj+N5pZBPWdeMScPMhqFFLfz yMW32zDUkK8mvv/VU2vJ4J3D2FdeBKmJ7BGNk= MIME-Version: 1.0 Received: by 10.220.124.193 with SMTP id v1mr1747319vcr.220.1280690553292; Sun, 01 Aug 2010 12:22:33 -0700 (PDT) Received: by 10.220.188.4 with HTTP; Sun, 1 Aug 2010 12:22:33 -0700 (PDT) In-Reply-To: References: Date: Sun, 1 Aug 2010 15:22:33 -0400 Message-ID: From: Zaphod Beeblebrox To: Steven Hartland Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS diff support on FreeBSD 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, 01 Aug 2010 19:52:30 -0000 On Sun, Aug 1, 2010 at 2:58 PM, Steven Hartland wrote: > I cant seem to track down the correlation of various ZFS features > that are present in Solaris and the corresponding FreeBSD versions. > > I'm interested in the zfs diff command. Could anyone tell me where > this info is, or do they know off hand when we're likely to see this > added to the FreeBSD implementation of zfs? > > http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley This sounds pretty much exactly like diffdir (just applied in a script to snapshots). From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 20:30:06 2010 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 BE8B0106566C for ; Sun, 1 Aug 2010 20:30:06 +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 91C118FC21 for ; Sun, 1 Aug 2010 20:30:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o71KU6KH047190 for ; Sun, 1 Aug 2010 20:30:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o71KU6Rq047185; Sun, 1 Aug 2010 20:30:06 GMT (envelope-from gnats) Date: Sun, 1 Aug 2010 20:30:06 GMT Message-Id: <201008012030.o71KU6Rq047185@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Scott Johnson Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Scott Johnson List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2010 20:30:06 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Scott Johnson To: bug-followup@FreeBSD.org, am@raisa.eu.org Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Sun, 1 Aug 2010 13:00:26 -0700 (PDT) --0-22506440-1280692826=:68914 Content-Type: text/plain; charset=us-ascii Another data point. I had a similar problem with mirrored boot disks. I installed 8.1-RELEASE onto two identical drives in a mirror, following the "Installing FreeBSD Root on ZFS (Mirror) using GPT" guide here: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror I can boot from either disk by changing the boot priority in the BIOS, so long as both disks are connected. I swapped the sata ports, and I can still boot from either disk. I can disconnect drive #2 and boot from drive #1 just fine, whether drive #1 is plugged into sata0 or sata1. However when I disconnect drive #1 and try to boot from drive #2, on either sata0 or sata1, I get errors: error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 No ZFS pools located, can't boot --0-22506440-1280692826=:68914 Content-Type: text/html; charset=us-ascii
Another data point. I had a similar problem with mirrored boot disks.

I installed 8.1-RELEASE onto two identical drives in a mirror, following the
"Installing FreeBSD Root on ZFS (Mirror) using GPT" guide here:
http:// wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror

I can boot from either disk by changing the boot priority in the BIOS, so long
as both disks are connected. I swapped the sata ports, and I can still boot from
either disk.

I can disconnect drive #2 and boot from drive #1 just fine, whether drive #1 is
plugged into sata0 or sata1.

However when I disconnect drive #1 and try to boot from drive #2, on either
sata0 or sata1, I get errors:

error 1 lba 32
error 1 lba 1
error 1 lba 32
error 1 lba 1
error 1 lba 32
error 1 lba 1
error 1 lba 32
error 1 lba 1
error 1 lba 32
error 1 lba 1
error 1 lba 32
error 1 lba 1
No ZFS pools located, can't boot

--0-22506440-1280692826=:68914-- From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 21:10:05 2010 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 D7CEE1065674 for ; Sun, 1 Aug 2010 21:10:05 +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 AC2538FC0A for ; Sun, 1 Aug 2010 21:10:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o71LA5wg085362 for ; Sun, 1 Aug 2010 21:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o71LA522085361; Sun, 1 Aug 2010 21:10:05 GMT (envelope-from gnats) Date: Sun, 1 Aug 2010 21:10:05 GMT Message-Id: <201008012110.o71LA522085361@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Shigeya Suzuki Cc: Subject: Re: kern/148709: [zfs] [panic] running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Shigeya Suzuki List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2010 21:10:05 -0000 The following reply was made to PR kern/148709; it has been noted by GNATS. From: Shigeya Suzuki To: bug-followup@FreeBSD.org, shigeya@wide.ad.jp Cc: Subject: Re: kern/148709: [zfs] [panic] running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id Date: Mon, 02 Aug 2010 06:02:21 +0900 Same reason, different usage caused panic: I'm now trying to "zfs send - zfs recv" from OpenSolaris file system onto FreeBSD box. This also cause same panic, when there is a filesystem which has sharesmb=ON. I will test the proposed patch. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 1 22:10:06 2010 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 19BFA1065672 for ; Sun, 1 Aug 2010 22:10:06 +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 E2AFE8FC18 for ; Sun, 1 Aug 2010 22:10:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o71MA5dU043140 for ; Sun, 1 Aug 2010 22:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o71MA5U3043139; Sun, 1 Aug 2010 22:10:05 GMT (envelope-from gnats) Date: Sun, 1 Aug 2010 22:10:05 GMT Message-Id: <201008012210.o71MA5U3043139@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: George Kontostanos Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: George Kontostanos List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2010 22:10:06 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: George Kontostanos To: bug-followup@FreeBSD.org, am@raisa.eu.org Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Mon, 2 Aug 2010 00:36:51 +0300 Hi, I was able to reproduce this on a VM with ZFS GPT mirror setup running = also 8.1 release. Regards, George= From owner-freebsd-fs@FreeBSD.ORG Mon Aug 2 11:07:00 2010 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 B71C0106566B for ; Mon, 2 Aug 2010 11:07:00 +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 899238FC22 for ; Mon, 2 Aug 2010 11:07:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o72B70hH035090 for ; Mon, 2 Aug 2010 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o72B6xtb035088 for freebsd-fs@FreeBSD.org; Mon, 2 Aug 2010 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Aug 2010 11:06:59 GMT Message-Id: <201008021106.o72B6xtb035088@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, 02 Aug 2010 11:07:00 -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/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149022 fs [hang] File system operations hangs with suspfs state o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148709 fs [zfs] [panic] running du with zfs filesystem with shar o kern/148655 fs [zfs] Booting from a degraded raidz no longer works in o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o bin/148296 fs [zfs] [loader] [patch] Very slow probe in /usr/src/sys o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/147292 fs [nfs] [patch] readahead missing in nfs client options o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server o kern/146375 fs [nfs] [patch] Typos in macro variables names in sys/fs o kern/145778 fs [zfs] [panic] panic in zfs_fuid_map_id (known issue fi s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o kern/145309 fs [disklabel]: Editing disk label invalidates the whole o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c o kern/144458 fs [nfs] [patch] nfsd fails as a kld p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o kern/143345 fs [ext2fs] [patch] extfs minor header cleanups to better o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142924 fs [ext2fs] [patch] Small cleanup for the inode struct in o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142401 fs [ntfs] [patch] Minor updates to NTFS from NetBSD o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs o bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/139363 fs [nfs] diskless root nfs mount from non FreeBSD server o kern/138790 fs [zfs] ZFS ceases caching when mem demand is high o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb 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/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 kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [panic] panic: ffs_truncate: read-only filesystem 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/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 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/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/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour 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 o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS p 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/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 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 conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with 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 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/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk 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/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 bin/86765 fs [patch] bsdlabel(8) assigning wrong fs type. 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/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/33464 fs [ufs] soft update inconsistencies after system crash o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 189 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 2 17:40:09 2010 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 AB07B106564A for ; Mon, 2 Aug 2010 17:40:09 +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 7F7538FC15 for ; Mon, 2 Aug 2010 17:40:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o72He9AL023598 for ; Mon, 2 Aug 2010 17:40:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o72He9KG023597; Mon, 2 Aug 2010 17:40:09 GMT (envelope-from gnats) Date: Mon, 2 Aug 2010 17:40:09 GMT Message-Id: <201008021740.o72He9KG023597@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Dan Naumov Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dan Naumov List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Aug 2010 17:40:09 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Dan Naumov To: bug-followup@FreeBSD.org, am@raisa.eu.org Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Mon, 2 Aug 2010 20:06:24 +0300 A few more people are also confirming this issue here: http://forums.freebsd.org/showthread.php?t=16556 From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 00:22:20 2010 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 E29311065673; Tue, 3 Aug 2010 00:22:20 +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 B8E078FC12; Tue, 3 Aug 2010 00:22:20 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o730MK9B020781; Tue, 3 Aug 2010 00:22:20 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o730MKuK020777; Tue, 3 Aug 2010 00:22:20 GMT (envelope-from linimon) Date: Tue, 3 Aug 2010 00:22:20 GMT Message-Id: <201008030022.o730MKuK020777@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/149215: [panic] gpart(8): Delete linux's slice via Gpart - get kernel panic 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, 03 Aug 2010 00:22:21 -0000 Old Synopsis: Delete linux's slice via Gpart - get kernel panic New Synopsis: [panic] gpart(8): Delete linux's slice via Gpart - get kernel panic Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Aug 3 00:21:19 UTC 2010 Responsible-Changed-Why: Not sure exactly how to classify this, but perhaps someone on fs@ can evalute it. http://www.freebsd.org/cgi/query-pr.cgi?pr=149215 From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 02:21:04 2010 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 B166D106564A for ; Tue, 3 Aug 2010 02:21:03 +0000 (UTC) (envelope-from lnkstern@yahoo.com) Received: from web110507.mail.gq1.yahoo.com (web110507.mail.gq1.yahoo.com [67.195.8.112]) by mx1.freebsd.org (Postfix) with SMTP id 835898FC17 for ; Tue, 3 Aug 2010 02:21:03 +0000 (UTC) Received: (qmail 87629 invoked by uid 60001); 3 Aug 2010 01:54:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1280800463; bh=BJYMJx1Qvsd/9aBTx/XkdN1JASHjwKMUOtVNLJFIaRk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=kWhsPCVY4mSvGwhg9rm5NSggn7JRShtxJfHdALYNVEjIsjAuKF3klUUNnUfyWnOaqAE5G611mWykgpHTIBoKxTjKmy6NprZmamjog380HcSJSxexnbkk2URMOLf76VeUgVWKCQpcUQuFwBNH/1uHu6UrAQOnQ+lefbJSsvCYpSE= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=yJVw17qacoUu+oaMZjwLmbaSP2+5rLRQ73RSh/HTzQi69hMudhrakOVvnk4Fkikm9X12opW+6pUGMJAk0LcGmfZIbvltnqEO01EnMbvOiBW0DTwZXPn0AT8Sp0rZ9Zcz4xR/rAegtax0tw0MffT1Aeh1078zrzTlYvG7dFrxC8w=; Message-ID: <718713.86541.qm@web110507.mail.gq1.yahoo.com> X-YMail-OSG: HoboHu4VM1l3RS6qtJ3xZcQiucexlHS_pt7p5a6E0q_YKuU w1c3iuqgJktmkxmFApLopSCeUp3KmBnJqoVan_knqocP9PwYjzTLvfMtYs2I pMPhr5BWQCR1MRVjobq5zo5nyoj9KfpiGmtax1DjC5N.flLCJbBFzrM4ep5s oGRjgRAv_ju4opW_wufr_8TAiiQ1PbMcxcdxukUJg24ZKGkPkpMkviuPSZBb w3dOYrf3KpbSBkZpDqunMupyd3znP7STTCkUFdLz_TAXefrY1CGoVLNSqnQF dbhS2Y_GnHBoeXwHVQR8VmlYZPVwC6f67gGZkoKyFINLYX1T_8z93s_Aq6n1 aMYhp0NMEVX..IRfdEHAvWLglnw-- Received: from [70.59.222.158] by web110507.mail.gq1.yahoo.com via HTTP; Mon, 02 Aug 2010 18:54:23 PDT X-Mailer: YahooMailRC/420.4 YahooMailWebService/0.8.105.279950 Date: Mon, 2 Aug 2010 18:54:23 -0700 (PDT) From: "Lincoln F. Sternn" To: freebsd-i386@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org Subject: Fw: [303] Details on ZFS tuning on FreeBSD 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, 03 Aug 2010 02:21:04 -0000 ----- Forwarded Message ---- From: Lincoln F. Sternn To: 303 <303@infosyndicate.net> Cc: jon@kozubik.com Sent: Mon, August 2, 2010 12:23:37 PM Subject: [303] Details on ZFS tuning on FreeBSD All (especially Teabag!), I am still getting kernel panics while using ZFS on FreeBSD 8.0. I am currently using the following parmeters on 303jose: /sys/i386/conf/JOSE: options KVA_PAGES=512 /boot/loader.conf: vm.kmem_size="1024M" vm.kmem_size_max="1024M" vfs.zfs.arc_max="512M" vfs.zfs.vdev.cache.size="256M" vfs.zfs.prefetch_disable=0 Ideally, I would like to dedicate 3 Gigs of memory to dedicated ZFS use. I am still trying to figure out which parameters I can safely increase without panic'ing the kernel on boot. Linc From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 02:23:04 2010 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 5D408106564A for ; Tue, 3 Aug 2010 02:23:04 +0000 (UTC) (envelope-from lnkstern@yahoo.com) Received: from web110508.mail.gq1.yahoo.com (web110508.mail.gq1.yahoo.com [67.195.8.113]) by mx1.freebsd.org (Postfix) with SMTP id 146E48FC14 for ; Tue, 3 Aug 2010 02:23:03 +0000 (UTC) Received: (qmail 3677 invoked by uid 60001); 3 Aug 2010 01:56:22 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1280800582; bh=RAQykc3v5/wPbsT/e85OLjE2tevM7tsSSw560S10NrA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=dI6KpESXL3X9kWf48Nn39l6RMTRhY2T01uwPeos2yV1Wkjhto3LfzZW3DyXCu5SX6FYL02Vfwcow2yzIjdTY09kyFei0r6JtdSPVv6H6lJGd+ebSErj/4oI5nVLeVYANCwrH0Egsc1w3E+N8oFIxglNrHBPl8RCQY7WfokekZAY= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=lmdIgBeXcumvmbz85pb5vKLLz48NBxsgW8kvtzE4nGf4gaRnRSIn38f0I34ttyBaF6cCK9rX2+D+/uTkvzWXpmzqkNLyCwTmj0jIbTofcfQdHC1SkzjHKrVpgbwUuDc7tf0qxkIpJS3Sl20bRA/Iesu6M8d331vmff77ecDS690=; Message-ID: <168579.89470.qm@web110508.mail.gq1.yahoo.com> X-YMail-OSG: 5ZIBGCQVM1mfBQcxRczmesMHeXXVRSXWGM3YNef2rjEb9It ADmsHlF8wJhQTwro4Adf4tRQ.e_h8kvZXTa1lPEnOIKRY03JfYhqgpf.zb9E oMf5jI2IXr9FcYL9gd.016ZwVkD2X98U0x7B5.7k8icZmzfIudSbT5_MLjgd F27mhuGYJVj.yOlbvMVnNHMv1oJyOwCsLhtR0ikgNMhDSxAMzm2Bvb6VxAZB BVHHVW6N_GvpRnADA6bZYXMDJXVdxQuRSXMDgCZedc_gGBuO_OCGfWtq92.n XMxcHAAF6rL3Unpm8Ht6Bo.Nzl0DMht9sC_yFfvnj8nv1.YO4KKStX0W6wgN n1syfFMmnehyjI9.ZPe41qEuZUcZ2FjXiz3ui7g-- Received: from [70.59.222.158] by web110508.mail.gq1.yahoo.com via HTTP; Mon, 02 Aug 2010 18:56:21 PDT X-Mailer: YahooMailRC/420.4 YahooMailWebService/0.8.105.279950 Date: Mon, 2 Aug 2010 18:56:21 -0700 (PDT) From: "Lincoln F. Sternn" To: 303@infosyndicate.net MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org, freebsd-i386@freebsd.org Subject: Re: [303] Details on ZFS tuning on FreeBSD 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, 03 Aug 2010 02:23:04 -0000 Despite the sarcasm question, I still need help tuning ZFS on FreeBSD. I want to optimally use 3 out of 4GB on FBSD 8.0. It keeps panicing the (custom-compiled) kernel, based on all of the previously-posted memory parameters. Linc ----- Original Message ---- From: "sushi-k@dominance.org" To: 303@infosyndicate.net Sent: Mon, August 2, 2010 4:13:46 PM Subject: Re: [303] Details on ZFS tuning on FreeBSD On Mon, 2 Aug 2010, Lincoln F. Sternn wrote: > Sweet! Thanks. I have lost the ability to discern between sarcasm and authenticity on this list. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 07:13:47 2010 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 5E42F1065672; Tue, 3 Aug 2010 07:13:47 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 348868FC13; Tue, 3 Aug 2010 07:13:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o737DlQX029388; Tue, 3 Aug 2010 07:13:47 GMT (envelope-from ae@freefall.freebsd.org) Received: (from ae@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o737Dlse029384; Tue, 3 Aug 2010 07:13:47 GMT (envelope-from ae) Date: Tue, 3 Aug 2010 07:13:47 GMT Message-Id: <201008030713.o737Dlse029384@freefall.freebsd.org> To: ae@FreeBSD.org, freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org From: ae@FreeBSD.org Cc: Subject: Re: bin/149215: [panic] gpart(8): Delete linux's slice via Gpart - get kernel panic 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, 03 Aug 2010 07:13:47 -0000 Synopsis: [panic] gpart(8): Delete linux's slice via Gpart - get kernel panic Responsible-Changed-From-To: freebsd-fs->freebsd-geom Responsible-Changed-By: ae Responsible-Changed-When: Tue Aug 3 07:13:09 UTC 2010 Responsible-Changed-Why: Seems geom-related. http://www.freebsd.org/cgi/query-pr.cgi?pr=149215 From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 09:49:10 2010 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 7F6211065673 for ; Tue, 3 Aug 2010 09:49:10 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [213.150.42.155]) by mx1.freebsd.org (Postfix) with ESMTP id ED5588FC26 for ; Tue, 3 Aug 2010 09:49:09 +0000 (UTC) Received: from [10.10.1.176] (1503026959.dong.dbnet.dk [89.150.95.15]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id A4E5C638DFC for ; Tue, 3 Aug 2010 11:32:09 +0200 (CEST) X-DKIM: OpenDKIM Filter v1.1.2 mail.tyknet.dk A4E5C638DFC DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1280827929; bh=wQmoprczNLz9v7tUwaNzRK4sS5AqG/KGQ7hYoT/5HME=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=vj3/nMRjmr94NXwmGOkoNKbPFbCHbiACyU4ryTz/jcTMNaRf92jcUEQ0gfQl7C6nY 8p38CByNRTevv+a6rlQWT6JK98eN6jEx/+4buPiFXiXiai6Iqey8QsHD9gjPWWAegZ TJP92kG18nTHzIVpCKmXPnm7ytbAVsc0zxUb/VXo= Message-ID: <4C57E20E.2030908@gibfest.dk> Date: Tue, 03 Aug 2010 11:31:58 +0200 From: Thomas Rasmussen User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100725 Thunderbird/3.0.6 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: HAST initial sync speed 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, 03 Aug 2010 09:49:10 -0000 Hello list, I finally got my ZFS/HAST setup up and running, or trying to at least. I am wondering how fast the initial HAST sync normally is - I created these 4 HAST providers yesterday on 4 146 gig drives, and they still each have over 90 gigabytes 'dirty' today. The machines are powerful (dell r710) and are otherwise idle, and they are connected to the same gigabit switch. I can supply details about any part of the configuration if needed, but I just wanted to ask if you guys believe something is wrong here. I can't help but think, if the initial sync takes 24+ hours, then if I ever need to replace one of the servers, I will be without redundancy until the new server reaches 0 'dirty' bytes, correct ? Thank you in advance for any input, Best regards, Thomas Steen Rasmussen From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 12:20:09 2010 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 0D2B6106567D for ; Tue, 3 Aug 2010 12:20:09 +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 D5DE28FC17 for ; Tue, 3 Aug 2010 12:20:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o73CK8Z0050858 for ; Tue, 3 Aug 2010 12:20:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o73CK8lM050839; Tue, 3 Aug 2010 12:20:08 GMT (envelope-from gnats) Date: Tue, 3 Aug 2010 12:20:08 GMT Message-Id: <201008031220.o73CK8lM050839@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Shigeya Suzuki Cc: Subject: Re: kern/148709: [zfs] [panic] running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Shigeya Suzuki List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Aug 2010 12:20:09 -0000 The following reply was made to PR kern/148709; it has been noted by GNATS. From: Shigeya Suzuki To: bug-followup@FreeBSD.org, shigeya@wide.ad.jp Cc: Subject: Re: kern/148709: [zfs] [panic] running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id Date: Tue, 03 Aug 2010 21:16:01 +0900 I have applied the patch, and tested it with "zfs send" from OpenSolaris box (zfs v13) into "ssh zfs recv" (FreeBSD 8.1) It looks like working fine. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 12:51:47 2010 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 D129F106566C for ; Tue, 3 Aug 2010 12:51:47 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 82A2B8FC15 for ; Tue, 3 Aug 2010 12:51:46 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id 39C413B9096; Tue, 3 Aug 2010 14:51:45 +0200 (CEST) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000239, version=1.2.2 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 6.6921] X-CRM114-CacheID: sfid-20100803_14513_F29A1961 X-CRM114-Status: Good ( pR: 6.6921 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Tue Aug 3 14:51:44 2010 X-DSPAM-Confidence: 0.7565 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4c5810e0158328221480714 X-DSPAM-Factors: 27, From*Attila Nagy , 0.00098, FreeBSD, 0.00254, STABLE, 0.01000, ls, 0.01000, ls, 0.01000, reproduce, 0.01000, Subject*file, 0.01000, Subject*file, 0.01000, Subject*can+be, 0.99000, one+is, 0.01000, mount, 0.01000, Subject*but, 0.99000, cache, 0.01000, machines, 0.01000, reproduce+the, 0.01000, behaviour, 0.01000, FreeBSD+8, 0.01000, May+3, 0.01000, bugs, 0.02192, Date*34+0200, 0.02305, Received*with+ESMTPSA, 0.02726, Received*ESMTPSA+id, 0.02726, Received*ESMTPSA, 0.02726, pretty, 0.03103, whether, 0.03103, doesn't, 0.03214, X-Spambayes-Classification: ham; 0.10 Received: from japan.t-online.private (japan.t-online.co.hu [195.228.243.99]) by people.fsn.hu (Postfix) with ESMTPSA id D8A5B3B907C for ; Tue, 3 Aug 2010 14:51:34 +0200 (CEST) Message-ID: <4C5810D6.9060605@fsn.hu> Date: Tue, 03 Aug 2010 14:51:34 +0200 From: Attila Nagy User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.10) Gecko/20100629 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 03 Aug 2010 12:51:47 -0000 Hello, I have two FreeBSD 8.x machines, one is the NFS server (8-STABLE, about one week old), the other is the client (8.1-PRERELEASE from May). The strange thing is this, happening on the NFS mount, client side: # ls -la 1083536654.80433.be03,S=7592 -rw------- 1 mail mail 7592 May 3 2004 1083536654.80433.be03,S=7592 # ls | grep 1083536654 ls doesn't find that file... Are there any known bugs regarding bad NFS client behaviour (caching maybe) in the above timeframe in stable/8? The machine does high amounts of NFS copying, and I can reproduce the above any time, so if it's cache related, it's pretty weird... I'm currently upgrading to see whether that helps. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 13:57:22 2010 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 624A810656F7 for ; Tue, 3 Aug 2010 13:57:22 +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 3311B8FC26 for ; Tue, 3 Aug 2010 13:57:22 +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 C59F246B8C; Tue, 3 Aug 2010 09:57:21 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 0AED38A050; Tue, 3 Aug 2010 09:57:16 -0400 (EDT) From: John Baldwin To: freebsd-fs@freebsd.org Date: Tue, 3 Aug 2010 09:44:59 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100217; KDE/4.4.5; amd64; ; ) References: <4C5810D6.9060605@fsn.hu> In-Reply-To: <4C5810D6.9060605@fsn.hu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Message-Id: <201008030944.59286.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 03 Aug 2010 09:57:16 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 03 Aug 2010 13:57:22 -0000 On Tuesday, August 03, 2010 8:51:34 am Attila Nagy wrote: > Hello, > > I have two FreeBSD 8.x machines, one is the NFS server (8-STABLE, about > one week old), the other is the client (8.1-PRERELEASE from May). > > The strange thing is this, happening on the NFS mount, client side: > # ls -la 1083536654.80433.be03,S=7592 > -rw------- 1 mail mail 7592 May 3 2004 1083536654.80433.be03,S=7592 > # ls | grep 1083536654 > ls doesn't find that file... > > Are there any known bugs regarding bad NFS client behaviour (caching > maybe) in the above timeframe in stable/8? > The machine does high amounts of NFS copying, and I can reproduce the > above any time, so if it's cache related, it's pretty weird... > > I'm currently upgrading to see whether that helps. Does touching the parent directory on another client "fix" it? -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 14:13:33 2010 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 20EBE106567B for ; Tue, 3 Aug 2010 14:13:33 +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 D25B58FC15 for ; Tue, 3 Aug 2010 14:13:32 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAI/AV0yDaFvO/2dsb2JhbACDFZ1msVqSEoEmgyBzBIkC X-IronPort-AV: E=Sophos;i="4.55,309,1278302400"; d="scan'208";a="89288412" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 03 Aug 2010 10:13:29 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id DFA98B3EA3; Tue, 3 Aug 2010 10:13:31 -0400 (EDT) Date: Tue, 3 Aug 2010 10:13:31 -0400 (EDT) From: Rick Macklem To: Attila Nagy Message-ID: <1147918452.245970.1280844811813.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4C5810D6.9060605@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 03 Aug 2010 14:13:33 -0000 > From: "Attila Nagy" > To: freebsd-fs@freebsd.org > Sent: Tuesday, August 3, 2010 8:51:34 AM > Subject: NFS problem: file doesn't appear in file listing, but can be accessed directly > Hello, > > I have two FreeBSD 8.x machines, one is the NFS server (8-STABLE, > about > one week old), the other is the client (8.1-PRERELEASE from May). > > The strange thing is this, happening on the NFS mount, client side: > # ls -la 1083536654.80433.be03,S=7592 > -rw------- 1 mail mail 7592 May 3 2004 1083536654.80433.be03,S=7592 > # ls | grep 1083536654 > ls doesn't find that file... > > Are there any known bugs regarding bad NFS client behaviour (caching > maybe) in the above timeframe in stable/8? > The machine does high amounts of NFS copying, and I can reproduce the > above any time, so if it's cache related, it's pretty weird... > > I'm currently upgrading to see whether that helps. > The only thing I am aware of the "might" cause this is a bug in the regular server when used with ZFS and the client uses the "rdriplus" option (pjd has a patch, but I don't think it has ever been committed). So, if your mount uses the "rdirplus" option, try it without that. Otherwise, I suspect that it is a bug in either the client or server. You can try replacing the client and server with the experimental ones and see if that fixes the problem. For the client: mount with "-t newnfs" instead of "-t nfs" For the server: start both mountd and nfsd with the "-e" option rick From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 14:18:42 2010 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 5D16F106564A for ; Tue, 3 Aug 2010 14:18:42 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 0DDC28FC13 for ; Tue, 3 Aug 2010 14:18:41 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id 1043D3BA0A7; Tue, 3 Aug 2010 16:18:40 +0200 (CEST) X-Bogosity: Ham, tests=bogofilter, spamicity=0.045546, version=1.2.2 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 8.8658] X-CRM114-CacheID: sfid-20100803_16182_F2FD7E11 X-CRM114-Status: Good ( pR: 8.8658 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Tue Aug 3 16:18:39 2010 X-DSPAM-Confidence: 0.6959 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4c58253f638781577250925 X-DSPAM-Factors: 27, From*Attila Nagy , 0.00097, wrote, 0.00263, wrote+>, 0.00290, 8+STABLE, 0.01000, to+8, 0.01000, STABLE, 0.01000, ls, 0.01000, ls, 0.01000, Subject*file, 0.01000, Subject*file, 0.01000, Subject*can+be, 0.99000, >+#, 0.01000, >+#, 0.01000, mount, 0.01000, mount, 0.01000, Subject*but, 0.99000, Nagy, 0.01000, zfs, 0.01000, Date*16+18, 0.99000, May+3, 0.01000, >+The, 0.01108, Received*with+ESMTPSA, 0.02726, Received*ESMTPSA+id, 0.02726, Received*ESMTPSA, 0.02726, 51, 0.02902, Subject*Re, 0.03056, X-Spambayes-Classification: unsure; 0.37 Received: from japan.t-online.private (japan.t-online.co.hu [195.228.243.99]) by people.fsn.hu (Postfix) with ESMTPSA id DC4963BA093 for ; Tue, 3 Aug 2010 16:18:27 +0200 (CEST) Message-ID: <4C582533.4070009@fsn.hu> Date: Tue, 03 Aug 2010 16:18:27 +0200 From: Attila Nagy User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.10) Gecko/20100629 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4C5810D6.9060605@fsn.hu> In-Reply-To: <4C5810D6.9060605@fsn.hu> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 03 Aug 2010 14:18:42 -0000 On 08/03/10 14:51, Attila Nagy wrote: > The strange thing is this, happening on the NFS mount, client side: > # ls -la 1083536654.80433.be03,S=7592 > -rw------- 1 mail mail 7592 May 3 2004 1083536654.80433.be03,S=7592 > # ls | grep 1083536654 > ls doesn't find that file... Additional info: - upgrading the client to 8-STABLE doesn't help - rebooting the client doesn't help - on the server side, there is zfs beneath the mount From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 14:18:55 2010 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 DA574106566B for ; Tue, 3 Aug 2010 14:18:55 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id A8C518FC17 for ; Tue, 3 Aug 2010 14:18:54 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id 7C4333BA0B4; Tue, 3 Aug 2010 16:18:52 +0200 (CEST) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.2 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 9.5611] X-CRM114-CacheID: sfid-20100803_16184_C68FBD6E X-CRM114-Status: Good ( pR: 9.5611 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Tue Aug 3 16:18:52 2010 X-DSPAM-Confidence: 0.7005 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4c58254b99976373653561 X-DSPAM-Factors: 27, From*Attila Nagy , 0.00097, FreeBSD, 0.00254, wrote, 0.00263, wrote, 0.00263, wrote+>, 0.00290, >+On, 0.00925, STABLE, 0.01000, ls, 0.01000, ls, 0.01000, reproduce, 0.01000, Subject*file, 0.01000, Subject*file, 0.01000, wrote+>>, 0.01000, Subject*can+be, 0.99000, one+is, 0.01000, mount, 0.01000, Subject*but, 0.99000, cache, 0.01000, machines, 0.01000, Nagy, 0.01000, reproduce+the, 0.01000, behaviour, 0.01000, Date*16+18, 0.99000, FreeBSD+8, 0.01000, May+3, 0.01000, >>+>>, 0.01230, X-Spambayes-Classification: ham; 0.01 Message-ID: <4C58253B.4010605@fsn.hu> Date: Tue, 03 Aug 2010 16:18:35 +0200 From: Attila Nagy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090817 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0 MIME-Version: 1.0 To: John Baldwin References: <4C5810D6.9060605@fsn.hu> <201008030944.59286.jhb@freebsd.org> In-Reply-To: <201008030944.59286.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 03 Aug 2010 14:18:55 -0000 On 08/03/2010 03:44 PM, John Baldwin wrote: > On Tuesday, August 03, 2010 8:51:34 am Attila Nagy wrote: >> Hello, >> >> I have two FreeBSD 8.x machines, one is the NFS server (8-STABLE, about >> one week old), the other is the client (8.1-PRERELEASE from May). >> >> The strange thing is this, happening on the NFS mount, client side: >> # ls -la 1083536654.80433.be03,S=7592 >> -rw------- 1 mail mail 7592 May 3 2004 1083536654.80433.be03,S=7592 >> # ls | grep 1083536654 >> ls doesn't find that file... >> >> Are there any known bugs regarding bad NFS client behaviour (caching >> maybe) in the above timeframe in stable/8? >> The machine does high amounts of NFS copying, and I can reproduce the >> above any time, so if it's cache related, it's pretty weird... >> >> I'm currently upgrading to see whether that helps. > Does touching the parent directory on another client "fix" it? > No. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 14:36:39 2010 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 52229106566B for ; Tue, 3 Aug 2010 14:36:39 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id AD58A8FC29 for ; Tue, 3 Aug 2010 14:36:38 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id E77E33BA5F6; Tue, 3 Aug 2010 16:36:36 +0200 (CEST) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.2 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 17.4355] X-CRM114-CacheID: sfid-20100803_16362_43A39A40 X-CRM114-Status: Good ( pR: 17.4355 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Tue Aug 3 16:36:36 2010 X-DSPAM-Confidence: 0.8516 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4c582974615151562336186 X-DSPAM-Factors: 27, From*Attila Nagy , 0.00096, FreeBSD, 0.00254, FreeBSD, 0.00254, wrote, 0.00263, >+>, 0.00519, >+>, 0.00519, patch, 0.00794, fsn+hu>, 0.00823, flags, 0.01000, see+if, 0.01000, it's+the, 0.01000, STABLE, 0.01000, ls, 0.01000, ls, 0.01000, reproduce, 0.01000, Subject*file, 0.01000, Subject*file, 0.01000, I've+tried, 0.01000, wrote+>>, 0.01000, Subject*can+be, 0.99000, ZFS, 0.01000, >+You, 0.01000, >+For, 0.01000, >+For, 0.01000, it+>, 0.01000, one+is, 0.01000, X-Spambayes-Classification: ham; 0.00 Message-ID: <4C582968.9000303@fsn.hu> Date: Tue, 03 Aug 2010 16:36:24 +0200 From: Attila Nagy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090817 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0 MIME-Version: 1.0 To: Rick Macklem References: <1147918452.245970.1280844811813.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1147918452.245970.1280844811813.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 03 Aug 2010 14:36:39 -0000 On 08/03/2010 04:13 PM, Rick Macklem wrote: >> From: "Attila Nagy" >> To: freebsd-fs@freebsd.org >> Sent: Tuesday, August 3, 2010 8:51:34 AM >> Subject: NFS problem: file doesn't appear in file listing, but can be accessed directly >> Hello, >> >> I have two FreeBSD 8.x machines, one is the NFS server (8-STABLE, >> about >> one week old), the other is the client (8.1-PRERELEASE from May). >> >> The strange thing is this, happening on the NFS mount, client side: >> # ls -la 1083536654.80433.be03,S=7592 >> -rw------- 1 mail mail 7592 May 3 2004 1083536654.80433.be03,S=7592 >> # ls | grep 1083536654 >> ls doesn't find that file... >> >> Are there any known bugs regarding bad NFS client behaviour (caching >> maybe) in the above timeframe in stable/8? >> The machine does high amounts of NFS copying, and I can reproduce the >> above any time, so if it's cache related, it's pretty weird... >> >> I'm currently upgrading to see whether that helps. >> > The only thing I am aware of the "might" cause this is a bug > in the regular server when used with ZFS and the client uses > the "rdriplus" option (pjd has a patch, but I don't think it > has ever been committed). > > So, if your mount uses the "rdirplus" option, try it without that. The mount is used with this: be01:/home/hm01 /home/hm01 nfs rw 0 0 So no special flags. I've tried with rdirplus anyways (maybe it's the opposite), the file can't be seen. I've mounted the share from an old Solaris box, which sees the file. > Otherwise, I suspect that it is a bug in either the client or server. > > You can try replacing the client and server with the experimental > ones and see if that fixes the problem. > For the client: mount with "-t newnfs" instead of "-t nfs" > For the server: start both mountd and nfsd with the "-e" option Sure. It works with the newnfs client, so it must be either a weird interaction between the FreeBSD server and client (old), or a client bug. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 21:00:33 2010 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 5C95E1065675 for ; Tue, 3 Aug 2010 21:00:33 +0000 (UTC) (envelope-from markus.gebert@hostpoint.ch) Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch [217.26.48.124]) by mx1.freebsd.org (Postfix) with ESMTP id 201D78FC1F for ; Tue, 3 Aug 2010 21:00:32 +0000 (UTC) Received: from 77-58-137-22.dclient.hispeed.ch ([77.58.137.22]:37624 helo=[172.16.1.3]) by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1OgOOh-0007aH-GH; Tue, 03 Aug 2010 22:47:39 +0200 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Markus Gebert In-Reply-To: <4C582968.9000303@fsn.hu> Date: Tue, 3 Aug 2010 22:47:38 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1147918452.245970.1280844811813.JavaMail.root@erie.cs.uoguelph.ca> <4C582968.9000303@fsn.hu> To: Attila Nagy X-Mailer: Apple Mail (2.1081) Cc: freebsd-fs@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 03 Aug 2010 21:00:33 -0000 On 03.08.2010, at 16:36, Attila Nagy wrote: >> You can try replacing the client and server with the experimental >> ones and see if that fixes the problem. >> For the client: mount with "-t newnfs" instead of "-t nfs" >> For the server: start both mountd and nfsd with the "-e" option > Sure. It works with the newnfs client, so it must be either a weird = interaction between the FreeBSD server and client (old), or a client = bug. Have you tried comparing on-the-wire NFS requests and responses between = newnfs and legacy nfs clients for your test case? Maybe you can rule out = the former like this. Or at least prove that the server actually = responds correctly to the READDIR request. Markus From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 00:33:01 2010 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 47DA91065673 for ; Wed, 4 Aug 2010 00:33:01 +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 00DF68FC1F for ; Wed, 4 Aug 2010 00:32:58 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAB1SWEyDaFvO/2dsb2JhbACDFZ14shKSDYEmgyBzBIkP X-IronPort-AV: E=Sophos;i="4.55,312,1278302400"; d="scan'208";a="89372274" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 03 Aug 2010 20:32:54 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id BB32DB3F0E; Tue, 3 Aug 2010 20:32:56 -0400 (EDT) Date: Tue, 3 Aug 2010 20:32:56 -0400 (EDT) From: Rick Macklem To: Markus Gebert Message-ID: <1431295206.277532.1280881976627.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 04 Aug 2010 00:33:01 -0000 > From: "Markus Gebert" > To: "Attila Nagy" > Cc: freebsd-fs@freebsd.org > Sent: Tuesday, August 3, 2010 4:47:38 PM > Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly > On 03.08.2010, at 16:36, Attila Nagy wrote: > > >> You can try replacing the client and server with the experimental > >> ones and see if that fixes the problem. > >> For the client: mount with "-t newnfs" instead of "-t nfs" > >> For the server: start both mountd and nfsd with the "-e" option > > Sure. It works with the newnfs client, so it must be either a weird > > interaction between the FreeBSD server and client (old), or a client > > bug. > > Have you tried comparing on-the-wire NFS requests and responses > between newnfs and legacy nfs clients for your test case? Maybe you > can rule out the former like this. Or at least prove that the server > actually responds correctly to the READDIR request. > Yep, it would be nice to see what went across the wire, particularly the case that fails (the regular client). I've got a hunch that the clients use different readdir sizes by default which will make comparison tough. Maybe you could try both clients using "readdirsize=32768" as an argument, so that they're at least reading the dir. in chunks of the same size. You can probably tell if the reply on the wire is legit by pulling it into wireshark. If wireshark thinks the readdir replies are ok and the filename exists in an entry on it (when the client fails to find it), that would indicate that the regular client has a bug, I think? If "-t newnfs" breaks when you change the readdirsize, then it suggests the server is busted. If you can capture the failing case with something like: tcpdump -s 0 -w xxx host (if run on the client) and then email me "xxx" as an attachment, that would be appreciated. (basically tcpdump the "ls" command that fails.) rick From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 03:27:47 2010 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 398791065677; Wed, 4 Aug 2010 03:27:47 +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 0F8A78FC0C; Wed, 4 Aug 2010 03:27:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o743RkY7037820; Wed, 4 Aug 2010 03:27:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o743Rk0G037816; Wed, 4 Aug 2010 03:27:46 GMT (envelope-from linimon) Date: Wed, 4 Aug 2010 03:27:46 GMT Message-Id: <201008040327.o743Rk0G037816@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/146941: [zfs] [panic] Kernel Double Fault - Happens constantly 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, 04 Aug 2010 03:27:47 -0000 Old Synopsis: Kernel Double Fault - Happens constantly New Synopsis: [zfs] [panic] Kernel Double Fault - Happens constantly Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 4 03:26:07 UTC 2010 Responsible-Changed-Why: possibly a ZFS issue. http://www.freebsd.org/cgi/query-pr.cgi?pr=146941 From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 03:28:52 2010 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 F38EC1065675; Wed, 4 Aug 2010 03:28:51 +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 C9A0B8FC1E; Wed, 4 Aug 2010 03:28:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o743Sptw037895; Wed, 4 Aug 2010 03:28:51 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o743Spe2037891; Wed, 4 Aug 2010 03:28:51 GMT (envelope-from linimon) Date: Wed, 4 Aug 2010 03:28:51 GMT Message-Id: <201008040328.o743Spe2037891@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/146786: [zfs] zpool import hangs with checksum errors 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, 04 Aug 2010 03:28:52 -0000 Old Synopsis: zpool import hangs with checksum errors New Synopsis: [zfs] zpool import hangs with checksum errors Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 4 03:28:30 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=146786 From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 07:18:40 2010 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 C85E01065672; Wed, 4 Aug 2010 07:18:40 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5CC9D8FC18; Wed, 4 Aug 2010 07:18:38 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o747IcbB072892; Wed, 4 Aug 2010 07:18:38 GMT (envelope-from mm@freefall.freebsd.org) Received: (from mm@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o747IcTc072888; Wed, 4 Aug 2010 07:18:38 GMT (envelope-from mm) Date: Wed, 4 Aug 2010 07:18:38 GMT Message-Id: <201008040718.o747IcTc072888@freefall.freebsd.org> To: mm@FreeBSD.org, freebsd-fs@FreeBSD.org, mm@FreeBSD.org From: mm@FreeBSD.org Cc: Subject: Re: kern/148709: [zfs] [panic] running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id 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, 04 Aug 2010 07:18:40 -0000 Synopsis: [zfs] [panic] running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id Responsible-Changed-From-To: freebsd-fs->mm Responsible-Changed-By: mm Responsible-Changed-When: Wed Aug 4 07:18:37 UTC 2010 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=148709 From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 09:10:12 2010 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 BC2F3106566B for ; Wed, 4 Aug 2010 09:10:12 +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 907888FC14 for ; Wed, 4 Aug 2010 09:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o749ACHf006593 for ; Wed, 4 Aug 2010 09:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o749ACBK006592; Wed, 4 Aug 2010 09:10:12 GMT (envelope-from gnats) Date: Wed, 4 Aug 2010 09:10:12 GMT Message-Id: <201008040910.o749ACBK006592@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Birgmeier Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Birgmeier List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2010 09:10:12 -0000 The following reply was made to PR kern/131360; it has been noted by GNATS. From: Martin Birgmeier To: bug-followup@FreeBSD.org Cc: Peter Keel Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load Date: Wed, 04 Aug 2010 10:42:18 +0200 You can probably close this, I cannot reproduce it any more on the current setup: RELENG_7_3_0_RELEASE. Regards, Martin From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 11:00:31 2010 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 1D3CE106566C for ; Wed, 4 Aug 2010 11:00:31 +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 E59638FC08 for ; Wed, 4 Aug 2010 11:00:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o74B0UMe017932 for ; Wed, 4 Aug 2010 11:00:30 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o74B0Uxh017923; Wed, 4 Aug 2010 11:00:30 GMT (envelope-from gnats) Date: Wed, 4 Aug 2010 11:00:30 GMT Message-Id: <201008041100.o74B0Uxh017923@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Lars Flatmo Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lars Flatmo List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2010 11:00:31 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Lars Flatmo To: bug-followup@FreeBSD.org, am@raisa.eu.org Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Wed, 4 Aug 2010 12:23:36 +0200 I have the exact same problem with fresh installed 8.1. also reproduced = it in vmware fusion= From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 11:40:05 2010 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 EED57106564A for ; Wed, 4 Aug 2010 11:40:05 +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 C2CFA8FC0C for ; Wed, 4 Aug 2010 11:40:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o74Be5Sv059409 for ; Wed, 4 Aug 2010 11:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o74Be5w1059407; Wed, 4 Aug 2010 11:40:05 GMT (envelope-from gnats) Date: Wed, 4 Aug 2010 11:40:05 GMT Message-Id: <201008041140.o74Be5w1059407@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2010 11:40:06 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@FreeBSD.org, am@raisa.eu.org Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Wed, 04 Aug 2010 14:33:08 +0300 I would like to ask those who can reproduce the problem to try to use head (CURRENT) version, manually compile sys/boot/zfs/zfstest.c and try to use it to debug what exactly fails. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 11:50:05 2010 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 808A11065675 for ; Wed, 4 Aug 2010 11:50:05 +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 54AE28FC08 for ; Wed, 4 Aug 2010 11:50:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o74Bo5AS068679 for ; Wed, 4 Aug 2010 11:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o74Bo5eO068677; Wed, 4 Aug 2010 11:50:05 GMT (envelope-from gnats) Date: Wed, 4 Aug 2010 11:50:05 GMT Message-Id: <201008041150.o74Bo5eO068677@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/146941: [zfs] [panic] Kernel Double Fault - Happens constantly X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2010 11:50:05 -0000 The following reply was made to PR kern/146941; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@FreeBSD.org, martin.minkus@punz.co.nz Cc: Subject: Re: kern/146941: [zfs] [panic] Kernel Double Fault - Happens constantly Date: Wed, 04 Aug 2010 14:48:26 +0300 Doublefault is often a stack overflow problem, not sure if this is the case here. Can you try to recompile kernel with larger stack size and test again (bump KSTACK_PAGES)? -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 13:31:27 2010 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 B4E281065677; Wed, 4 Aug 2010 13:31:27 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1CF118FC15; Wed, 4 Aug 2010 13:31:26 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id o74DUH7r026432; Wed, 4 Aug 2010 15:30:32 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id o74DUGM5026426; Wed, 4 Aug 2010 15:30:16 +0200 (CEST) (envelope-from olli) From: Oliver Fromme Message-Id: <201008041330.o74DUGM5026426@lurza.secnetix.de> To: bug-followup@FreeBSD.org, freebsd-fs@FreeBSD.org, rowi@free.de Date: Wed, 4 Aug 2010 15:30:16 +0200 (CEST) X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.4 (lurza.secnetix.de [127.0.0.1]); Wed, 04 Aug 2010 15:30:32 +0200 (CEST) Cc: Subject: Re: kern/116913: [ffs] [panic] ffs_blkfree: freeing free block 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, 04 Aug 2010 13:31:27 -0000 Hello Rolf, I just stumbled across this old PR. If I'm not mistaken, this particular problem was fixed long ago. It certainly didn't happen anymore to me after rev. 1.386 of sys/vm/vm_object.c, almost 3 years ago. Do you agree that the PR can be closed? Best regards Oliver http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/116913 -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "C++ is over-complicated nonsense. And Bjorn Shoestrap's book a danger to public health. I tried reading it once, I was in recovery for months." -- Cliff Sarginson From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 13:40:08 2010 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 42976106566B for ; Wed, 4 Aug 2010 13:40:08 +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 30E958FC08 for ; Wed, 4 Aug 2010 13:40:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o74De8Cr077148 for ; Wed, 4 Aug 2010 13:40:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o74De8ja077147; Wed, 4 Aug 2010 13:40:08 GMT (envelope-from gnats) Date: Wed, 4 Aug 2010 13:40:08 GMT Message-Id: <201008041340.o74De8ja077147@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Oliver Fromme Cc: Subject: Re: kern/116913: [ffs] [panic] ffs_blkfree: freeing free block X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Oliver Fromme List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2010 13:40:08 -0000 The following reply was made to PR kern/116913; it has been noted by GNATS. From: Oliver Fromme To: bug-followup@FreeBSD.org, freebsd-fs@FreeBSD.org, rowi@free.de Cc: Subject: Re: kern/116913: [ffs] [panic] ffs_blkfree: freeing free block Date: Wed, 4 Aug 2010 15:30:16 +0200 (CEST) Hello Rolf, I just stumbled across this old PR. If I'm not mistaken, this particular problem was fixed long ago. It certainly didn't happen anymore to me after rev. 1.386 of sys/vm/vm_object.c, almost 3 years ago. Do you agree that the PR can be closed? Best regards Oliver http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/116913 -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "C++ is over-complicated nonsense. And Bjorn Shoestrap's book a danger to public health. I tried reading it once, I was in recovery for months." -- Cliff Sarginson From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 15:41:05 2010 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 83598106568B; Wed, 4 Aug 2010 15:41:05 +0000 (UTC) (envelope-from olli@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 586098FC26; Wed, 4 Aug 2010 15:41:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o74Ff5Gn003629; Wed, 4 Aug 2010 15:41:05 GMT (envelope-from olli@freefall.freebsd.org) Received: (from olli@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o74Ff4Ne003527; Wed, 4 Aug 2010 15:41:04 GMT (envelope-from olli) Date: Wed, 4 Aug 2010 15:41:04 GMT Message-Id: <201008041541.o74Ff4Ne003527@freefall.freebsd.org> To: rowi@free.de, olli@FreeBSD.org, freebsd-fs@FreeBSD.org From: olli@FreeBSD.org Cc: Subject: Re: kern/116913: [ffs] [panic] ffs_blkfree: freeing free block 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, 04 Aug 2010 15:41:05 -0000 Synopsis: [ffs] [panic] ffs_blkfree: freeing free block State-Changed-From-To: open->closed State-Changed-By: olli State-Changed-When: Wed Aug 4 15:40:10 UTC 2010 State-Changed-Why: Originator agrees that the problem is fixed. http://www.freebsd.org/cgi/query-pr.cgi?pr=116913 From owner-freebsd-fs@FreeBSD.ORG Wed Aug 4 20:42:19 2010 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 CA8811065673; Wed, 4 Aug 2010 20:42:19 +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 A0DC58FC13; Wed, 4 Aug 2010 20:42:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o74KgJu1005539; Wed, 4 Aug 2010 20:42:19 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o74KgJoi005535; Wed, 4 Aug 2010 20:42:19 GMT (envelope-from linimon) Date: Wed, 4 Aug 2010 20:42:19 GMT Message-Id: <201008042042.o74KgJoi005535@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/149297: [zfs] zpool iostat fails to show 666GB 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, 04 Aug 2010 20:42:19 -0000 Old Synopsis: zpool iostat fails to show 666GB New Synopsis: [zfs] zpool iostat fails to show 666GB Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 4 20:42:05 UTC 2010 Responsible-Changed-Why: This does not sound amd64-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=149297 From owner-freebsd-fs@FreeBSD.ORG Thu Aug 5 08:20:09 2010 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 981B3106567A for ; Thu, 5 Aug 2010 08:20:09 +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 86A908FC08 for ; Thu, 5 Aug 2010 08:20:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o758K9HX009655 for ; Thu, 5 Aug 2010 08:20:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o758K9xE009654; Thu, 5 Aug 2010 08:20:09 GMT (envelope-from gnats) Date: Thu, 5 Aug 2010 08:20:09 GMT Message-Id: <201008050820.o758K9xE009654@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Matuska Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Matuska List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Aug 2010 08:20:09 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Martin Matuska To: bug-followup@FreeBSD.org, Andriy Gapon Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Thu, 05 Aug 2010 10:19:37 +0200 I can confirm this behaviour, easily reproducable in virtualbox. The problem must be in the internal logic of zfsboot, because the lba errors reported are from function: drvread() in sys/boot/i386/zfsboot/zfsboot.c, line #1079: if (V86_CY(v86.efl)) { printf("error %u lba %u\n", v86.eax >> 8 & 0xff, lba); return -1; } drvread() is called from vdev_read() (line #315) From owner-freebsd-fs@FreeBSD.ORG Thu Aug 5 09:00:20 2010 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 AB5091065674 for ; Thu, 5 Aug 2010 09:00:20 +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 99C4B8FC0C for ; Thu, 5 Aug 2010 09:00:20 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o7590KEV049582 for ; Thu, 5 Aug 2010 09:00:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o7590K52049581; Thu, 5 Aug 2010 09:00:20 GMT (envelope-from gnats) Date: Thu, 5 Aug 2010 09:00:20 GMT Message-Id: <201008050900.o7590K52049581@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Aug 2010 09:00:20 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Andriy Gapon To: Martin Matuska Cc: bug-followup@FreeBSD.org Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Thu, 05 Aug 2010 11:51:23 +0300 on 05/08/2010 11:19 Martin Matuska said the following: > I can confirm this behaviour, easily reproducable in virtualbox. > > The problem must be in the internal logic of zfsboot, because the lba > errors reported are from function: > > drvread() in sys/boot/i386/zfsboot/zfsboot.c, line #1079: > if (V86_CY(v86.efl)) { > printf("error %u lba %u\n", v86.eax >> 8 & 0xff, lba); > return -1; > } > > drvread() is called from vdev_read() (line #315) Right, and this is the reason why I asked to try zfstest, because it would be interesting to see the whole stack trace to determine which high-level zfs operation fails. Thanks! -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Thu Aug 5 12:00:23 2010 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 E3AE110656AB for ; Thu, 5 Aug 2010 12:00:23 +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 D18398FC23 for ; Thu, 5 Aug 2010 12:00:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o75C0N8t028008 for ; Thu, 5 Aug 2010 12:00:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o75C0NFF028007; Thu, 5 Aug 2010 12:00:23 GMT (envelope-from gnats) Date: Thu, 5 Aug 2010 12:00:23 GMT Message-Id: <201008051200.o75C0NFF028007@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Matuska Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Matuska List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Aug 2010 12:00:24 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Martin Matuska To: bug-followup@FreeBSD.org, Andriy Gapon Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Thu, 05 Aug 2010 13:53:44 +0200 So I have done more code reading and debugging with mfsBSD in virtualbox and I came to the following conclusion: sys/boot/zfs/zfsimpl.c reads vdev information from the pool but there is no check if these vdevs do exist on physical devices. In other words, if the pool has last seen its vdevs as HEALTHY, gptzfsboot assumes all of them are available. So this way e.g. in case of a mirror, the vdev_mirror_read() tries to read from the first "healthy" vdev in its list. If the first vdev is the missing vdev (e.g. a disconnected or failed drive), it just cannot read from it so you are unable to boot. In my test setup, vdev_mirror_read() reported two healty kids and tried to read from the non-existing vdev. I think in the boot case, we should first scan for all physically available vdevs, then scan for children from their configuration. All child vdevs that cannot be physically opened (do not have a representation from the previous scan) should be set to state VDEV_STATE_CANT_OPEN and not assumed as VDEV_STATE_HEALTHY. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 5 12:30:10 2010 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 DF6341065674 for ; Thu, 5 Aug 2010 12:30:10 +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 B2FBD8FC0A for ; Thu, 5 Aug 2010 12:30:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o75CUAmF057375 for ; Thu, 5 Aug 2010 12:30:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o75CUA3h057372; Thu, 5 Aug 2010 12:30:10 GMT (envelope-from gnats) Date: Thu, 5 Aug 2010 12:30:10 GMT Message-Id: <201008051230.o75CUA3h057372@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Aug 2010 12:30:11 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Andriy Gapon To: Martin Matuska Cc: bug-followup@FreeBSD.org Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Thu, 05 Aug 2010 15:21:06 +0300 on 05/08/2010 14:53 Martin Matuska said the following: > In my test setup, vdev_mirror_read() reported two healty kids and tried > to read from the non-existing vdev. What happened next? If I read vdev_mirror_read() code correctly it should continue to the next device if reading from the current device fails. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Thu Aug 5 16:30:11 2010 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 A3974106567C for ; Thu, 5 Aug 2010 16:30: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 777358FC13 for ; Thu, 5 Aug 2010 16:30:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o75GUBh9092788 for ; Thu, 5 Aug 2010 16:30:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o75GUBig092787; Thu, 5 Aug 2010 16:30:11 GMT (envelope-from gnats) Date: Thu, 5 Aug 2010 16:30:11 GMT Message-Id: <201008051630.o75GUBig092787@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Matuska Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Matuska List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Aug 2010 16:30:11 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Martin Matuska To: bug-followup@FreeBSD.org, am@raisa.eu.org Cc: Andriy Gapon , Pawel Jakub Dawidek , Xin LI Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Thu, 05 Aug 2010 18:23:43 +0200 This is a multi-part message in MIME format. --------------050900020709060502070203 Content-Type: text/plain; charset=windows-1250 Content-Transfer-Encoding: 7bit A proposed patch is attached. The function vdev_read_phys() (sys/boot/zfs/zfsimpl.c, #325) does call vdev->v_phys_read() without checking if that function is registered. This check should be done in vdev_read_phys before doing anything else. vdev_create initializes vdev->v_phys_read as 0 and unavailable vdevs keep this value. --------------050900020709060502070203 Content-Type: text/plain; name="head-zfsimpl.c.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="head-zfsimpl.c.patch" Index: sys/boot/zfs/zfsimpl.c =================================================================== --- sys/boot/zfs/zfsimpl.c (revision 210854) +++ sys/boot/zfs/zfsimpl.c (working copy) @@ -328,6 +328,9 @@ size_t psize; int rc; + if (!vdev->v_phys_read) + return (EIO); + if (bp) { psize = BP_GET_PSIZE(bp); } else { --------------050900020709060502070203-- From owner-freebsd-fs@FreeBSD.ORG Thu Aug 5 16:40:12 2010 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 CCAD2106566C for ; Thu, 5 Aug 2010 16:40:12 +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 BAE758FC0C for ; Thu, 5 Aug 2010 16:40:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o75GeC88003676 for ; Thu, 5 Aug 2010 16:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o75GeCR1003675; Thu, 5 Aug 2010 16:40:12 GMT (envelope-from gnats) Date: Thu, 5 Aug 2010 16:40:12 GMT Message-Id: <201008051640.o75GeCR1003675@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Aug 2010 16:40:12 -0000 The following reply was made to PR kern/148655; it has been noted by GNATS. From: Andriy Gapon To: Martin Matuska Cc: bug-followup@FreeBSD.org, am@raisa.eu.org, Pawel Jakub Dawidek , Xin LI Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Date: Thu, 05 Aug 2010 19:38:17 +0300 on 05/08/2010 19:23 Martin Matuska said the following: > A proposed patch is attached. > > The function vdev_read_phys() (sys/boot/zfs/zfsimpl.c, #325) does call > vdev->v_phys_read() without checking if that function is registered. > > This check should be done in vdev_read_phys before doing anything else. > > vdev_create initializes vdev->v_phys_read as 0 and unavailable vdevs > keep this value. Looks very good. Thanks! -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Aug 6 13:49:04 2010 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 231A3106567D for ; Fri, 6 Aug 2010 13:49:04 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello089077043238.chello.pl [89.77.43.238]) by mx1.freebsd.org (Postfix) with ESMTP id 6DE6D8FC0A for ; Fri, 6 Aug 2010 13:48:53 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id D838A45E49; Fri, 6 Aug 2010 15:48:51 +0200 (CEST) Received: from localhost (pdawidek.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 1C60B45CD8 for ; Fri, 6 Aug 2010 15:48:47 +0200 (CEST) Date: Fri, 6 Aug 2010 15:48:40 +0200 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20100806134840.GE1710@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VUDLurXRWRKrGuMn" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 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: Subject: Converting sysinstalled FreeBSD into ZFS-only 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, 06 Aug 2010 13:49:04 -0000 --VUDLurXRWRKrGuMn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In case you are interested: http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-con= figuration/ --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --VUDLurXRWRKrGuMn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkxcErcACgkQForvXbEpPzSr8QCgrXlADciAlFel23jwlCQpxOwt 3BMAn13nL1U709QrMQwpEI/+qrA7P8nS =/kNs -----END PGP SIGNATURE----- --VUDLurXRWRKrGuMn-- From owner-freebsd-fs@FreeBSD.ORG Fri Aug 6 13:50:14 2010 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 0FD311065677 for ; Fri, 6 Aug 2010 13:50:14 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello089077043238.chello.pl [89.77.43.238]) by mx1.freebsd.org (Postfix) with ESMTP id 4E4988FC21 for ; Fri, 6 Aug 2010 13:50:13 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id BBEF345E49; Fri, 6 Aug 2010 15:50:11 +0200 (CEST) Received: from localhost (pdawidek.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id CC21D45CD8; Fri, 6 Aug 2010 15:50:07 +0200 (CEST) Date: Fri, 6 Aug 2010 15:50:01 +0200 From: Pawel Jakub Dawidek To: Thomas Rasmussen Message-ID: <20100806135001.GF1710@garage.freebsd.pl> References: <4C57E20E.2030908@gibfest.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5Mfx4RzfBqgnTE/w" Content-Disposition: inline In-Reply-To: <4C57E20E.2030908@gibfest.dk> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 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 Subject: Re: HAST initial sync speed 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, 06 Aug 2010 13:50:14 -0000 --5Mfx4RzfBqgnTE/w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 03, 2010 at 11:31:58AM +0200, Thomas Rasmussen wrote: > Hello list, >=20 > I finally got my ZFS/HAST setup up and running, or trying to at least. > I am wondering how fast the initial HAST sync normally is - I created > these 4 HAST providers yesterday on 4 146 gig drives, and they still each > have over 90 gigabytes 'dirty' today. The machines are powerful (dell > r710) and are otherwise idle, and they are connected to the same gigabit > switch. >=20 > I can supply details about any part of the configuration if needed, but I > just wanted to ask if you guys believe something is wrong here. I can't h= elp > but think, if the initial sync takes 24+ hours, then if I ever need to > replace one of the servers, I will be without redundancy until the new > server reaches 0 'dirty' bytes, correct ? Correct, but synchronizartion should take much, much less time. Is dirty count actually decreasing? --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --5Mfx4RzfBqgnTE/w Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkxcEwgACgkQForvXbEpPzQbmwCdEpUp8qj2YlQKkwLMLCkbxabk 4lUAnA+XsmraWYclHht0q2wAXFLI7t3A =inN/ -----END PGP SIGNATURE----- --5Mfx4RzfBqgnTE/w-- From owner-freebsd-fs@FreeBSD.ORG Fri Aug 6 14:15:22 2010 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 540461065675 for ; Fri, 6 Aug 2010 14:15:22 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by mx1.freebsd.org (Postfix) with ESMTP id 3C28A8FC2A for ; Fri, 6 Aug 2010 14:15:22 +0000 (UTC) Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta09.emeryville.ca.mail.comcast.net with comcast id r0oE1e0010QkzPwA92FMLg; Fri, 06 Aug 2010 14:15:21 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta02.emeryville.ca.mail.comcast.net with comcast id r2FL1e0073LrwQ28N2FMke; Fri, 06 Aug 2010 14:15:21 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8BBE19B423; Fri, 6 Aug 2010 07:15:20 -0700 (PDT) Date: Fri, 6 Aug 2010 07:15:20 -0700 From: Jeremy Chadwick To: Pawel Jakub Dawidek Message-ID: <20100806141520.GA38940@icarus.home.lan> References: <20100806134840.GE1710@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100806134840.GE1710@garage.freebsd.pl> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@FreeBSD.org, randi@freebsd.org Subject: Re: Converting sysinstalled FreeBSD into ZFS-only 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, 06 Aug 2010 14:15:22 -0000 On Fri, Aug 06, 2010 at 03:48:40PM +0200, Pawel Jakub Dawidek wrote: > In case you are interested: > > http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ Are there efforts underway to make sysinstall ZFS-aware on FreeBSD? I believe the PC-BSD folks did this but I haven't checked it out. CC'ing Randi since she might know. :-) -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Aug 6 21:38:32 2010 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 2C9C2106568A; Fri, 6 Aug 2010 21:38:32 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [204.109.60.94]) by mx1.freebsd.org (Postfix) with ESMTP id 08D908FC1A; Fri, 6 Aug 2010 21:38:31 +0000 (UTC) Received: from unknown (client-86-31-3-93.midd.adsl.virginmedia.com [86.31.3.93]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id A2EC35C01; Fri, 6 Aug 2010 21:38:00 +0000 (UTC) Date: Fri, 6 Aug 2010 22:38:25 +0100 From: Bruce Cran To: Jeremy Chadwick Message-ID: <20100806223825.000062d5@unknown> In-Reply-To: <20100806141520.GA38940@icarus.home.lan> References: <20100806134840.GE1710@garage.freebsd.pl> <20100806141520.GA38940@icarus.home.lan> X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, Pawel Jakub Dawidek , randi@freebsd.org Subject: Re: Converting sysinstalled FreeBSD into ZFS-only 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, 06 Aug 2010 21:38:32 -0000 On Fri, 6 Aug 2010 07:15:20 -0700 Jeremy Chadwick wrote: > On Fri, Aug 06, 2010 at 03:48:40PM +0200, Pawel Jakub Dawidek wrote: > > In case you are interested: > > > > http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ > > Are there efforts underway to make sysinstall ZFS-aware on FreeBSD? I > believe the PC-BSD folks did this but I haven't checked it out. ae@ is working on geom-ifying and adding support for ZFS to sade. I've started working on making sysinstall grok geom, but getting it to the stage of understanding ZFS is a long way away, and will need new partitioning code based around gpart. I believe the plan for 9.0 is to have pc-sysinstall from the PC-BSD project be available as one of the installers; the backend has already been committed and there's work going on to add an ncurses frontend. -- Bruce Cran From owner-freebsd-fs@FreeBSD.ORG Sat Aug 7 00:35:35 2010 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 71AC11065675 for ; Sat, 7 Aug 2010 00:35:35 +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 28B6E8FC08 for ; Sat, 7 Aug 2010 00:35:34 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEANdGXEyDaFvO/2dsb2JhbACDFZ4ntC+RfIEmgyFzBIk3 X-IronPort-AV: E=Sophos;i="4.55,331,1278302400"; d="scan'208";a="87611589" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 06 Aug 2010 20:35:34 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 290A6B3EA3; Fri, 6 Aug 2010 20:35:34 -0400 (EDT) Date: Fri, 6 Aug 2010 20:35:34 -0400 (EDT) From: Rick Macklem To: Markus Gebert Message-ID: <507225020.401114.1281141334084.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Aug 2010 00:35:35 -0000 > Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly > On 03.08.2010, at 16:36, Attila Nagy wrote: > > >> You can try replacing the client and server with the experimental > >> ones and see if that fixes the problem. > >> For the client: mount with "-t newnfs" instead of "-t nfs" > >> For the server: start both mountd and nfsd with the "-e" option > > Sure. It works with the newnfs client, so it must be either a weird > > interaction between the FreeBSD server and client (old), or a client > > bug. > > Have you tried comparing on-the-wire NFS requests and responses > between newnfs and legacy nfs clients for your test case? Maybe you > can rule out the former like this. Or at least prove that the server > actually responds correctly to the READDIR request. > Well, I looked at a packet capture emailed to me by Attila Nagy and the filename shows up in the Lookup near the end (the "ls -la"), but is not in any of the readdir replies (a search from the start of the capture in wireshark only finds it at the Lookup). Therefore, I think the problem is w.r.t. the server. (He did this failed case with the "newnfs", so both clients see the problem.) Attila, could you by any chance try switching to the experimental server ("-e" on both mountd and nfsd) and see if the problem persists? (The experimental server may replace the regular one relatively soon, so if the problem doesn't exist in the experimental one, I'm tempted to leave it at that. If both servers have a problem, it definitely needs further investigation.) rick From owner-freebsd-fs@FreeBSD.ORG Sat Aug 7 13:11:06 2010 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 B130C1065673 for ; Sat, 7 Aug 2010 13:11:06 +0000 (UTC) (envelope-from markus.gebert@hostpoint.ch) Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch [217.26.48.124]) by mx1.freebsd.org (Postfix) with ESMTP id 723278FC0A for ; Sat, 7 Aug 2010 13:11:06 +0000 (UTC) Received: from 77-58-137-22.dclient.hispeed.ch ([77.58.137.22]:43069 helo=[172.16.1.3]) by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1OhjB2-000HZi-Kw; Sat, 07 Aug 2010 15:11:04 +0200 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Markus Gebert In-Reply-To: <507225020.401114.1281141334084.JavaMail.root@erie.cs.uoguelph.ca> Date: Sat, 7 Aug 2010 15:11:03 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <507225020.401114.1281141334084.JavaMail.root@erie.cs.uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.1081) Cc: freebsd-fs@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Aug 2010 13:11:06 -0000 On 07.08.2010, at 02:35, Rick Macklem wrote: >> Subject: Re: NFS problem: file doesn't appear in file listing, but = can be accessed directly >> On 03.08.2010, at 16:36, Attila Nagy wrote: >>=20 >>>> You can try replacing the client and server with the experimental >>>> ones and see if that fixes the problem. >>>> For the client: mount with "-t newnfs" instead of "-t nfs" >>>> For the server: start both mountd and nfsd with the "-e" option >>> Sure. It works with the newnfs client, so it must be either a weird >>> interaction between the FreeBSD server and client (old), or a client >>> bug. >>=20 >> Have you tried comparing on-the-wire NFS requests and responses >> between newnfs and legacy nfs clients for your test case? Maybe you >> can rule out the former like this. Or at least prove that the server >> actually responds correctly to the READDIR request. >>=20 > Well, I looked at a packet capture emailed to me by Attila Nagy and > the filename shows up in the Lookup near the end (the "ls -la"), but > is not in any of the readdir replies (a search from the start of the > capture in wireshark only finds it at the Lookup). Therefore, I think > the problem is w.r.t. the server. (He did this failed case with the > "newnfs", so both clients see the problem.) I agree, this must be some kind of server issue then. Still, I wonder = why the solaris client didn't show the problem... Markus