From owner-freebsd-fs@FreeBSD.ORG Sun Mar 11 07:10:50 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 23C311065670 for ; Sun, 11 Mar 2012 07:10:50 +0000 (UTC) (envelope-from markm-lists@intellasoft.net) Received: from mail.mystoragebox.com (mail.mystoragebox.com [64.27.7.19]) by mx1.freebsd.org (Postfix) with ESMTP id 103F08FC19 for ; Sun, 11 Mar 2012 07:10:49 +0000 (UTC) Received: from cpe-67-240-79-210.nycap.res.rr.com ([67.240.79.210] helo=[192.168.35.110]) by mail.mystoragebox.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1S6cbj-0008Uk-LQ for freebsd-fs@freebsd.org; Sun, 11 Mar 2012 01:50:19 -0500 Message-ID: <4F5C4FF8.7080000@intellasoft.net> Date: Sun, 11 Mar 2012 03:10:48 -0400 From: Mark Murawski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: How to change a guid of a zfs device? 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, 11 Mar 2012 07:10:50 -0000 How would I go about changing a guid of a zfs physical device? There doesn't seem to be any options in zpool or zdb for doing guid changes. It's a long story, but through a series of drive swaps I've managed to really screw stuff up. Here's my current status NAME STATE READ WRITE CKSUM zstorage UNAVAIL 0 0 0 mirror-0 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada3 ONLINE 0 0 0 mirror-1 UNAVAIL 0 0 0 14791054479353866913 UNAVAIL 0 0 0 was /dev/ada4s4 5249816505308091368 UNAVAIL 0 0 0 was /dev/ada1 mirror-2 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada10 ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada8 ONLINE 0 0 0 mirror-4 ONLINE 0 0 0 ada7 ONLINE 0 0 0 ada9 ONLINE 0 0 0 14791054479353866913 is really /dev/ada1s4 now 5249816505308091368 is really /dev/ada0 now the problem is, zdb tells me that /dev/ada1 has a guid of 3184618752700174674 and zdb says /dev/ada0 has a guid of 16592948394566938185 I need to get these to match so that I can reconstruct the pool again From owner-freebsd-fs@FreeBSD.ORG Sun Mar 11 08:05:14 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 279D6106564A for ; Sun, 11 Mar 2012 08:05:14 +0000 (UTC) (envelope-from kevlo@kevlo.org) Received: from ns.kevlo.org (kevlo.org [220.128.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id 349888FC12 for ; Sun, 11 Mar 2012 08:05:08 +0000 (UTC) Received: from [127.0.0.1] (git.kevlo.org [220.128.136.52]) by ns.kevlo.org (8.14.5/8.14.5) with ESMTP id q2B7u467013307; Sun, 11 Mar 2012 15:56:05 +0800 (CST) (envelope-from kevlo@kevlo.org) Message-ID: <1331452568.2105.7.camel@nsl> From: Kevin Lo To: George Neville-Neil Date: Sun, 11 Mar 2012 15:56:08 +0800 In-Reply-To: <0826905E-32FE-4F44-923F-220D7A11E65C@neville-neil.com> References: <0826905E-32FE-4F44-923F-220D7A11E65C@neville-neil.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.2- Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Cc: freebsd-fs@freebsd.org Subject: Re: RFC: FUSE kernel module for the kernel... 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, 11 Mar 2012 08:05:14 -0000 George Neville-Neil wrote: > On Mar 9, 2012, at 13:44 , Mark Felder wrote: > > > The true test for me is "can you run mp3fs without causing kernel panics now?" as I'm told that's why it's not in ports anymore. > > At the moment I'm only using the FUSE example, but I have run glusterfs on it, and also sshfs. There's a known problem about exporting fuse file system export over nfs. I'm wondering if your patch will fix that. > Best, > George Kevin From owner-freebsd-fs@FreeBSD.ORG Sun Mar 11 11:58:08 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2284D106566B; Sun, 11 Mar 2012 11:58:08 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from dash.upc.es (dash.upc.es [147.83.2.50]) by mx1.freebsd.org (Postfix) with ESMTP id 96CC68FC08; Sun, 11 Mar 2012 11:58:06 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by dash.upc.es (8.14.1/8.13.1) with ESMTP id q2BAhifj008127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 11 Mar 2012 11:43:44 +0100 Received: from portgus.lan (170.Red-83-44-99.dynamicIP.rima-tde.net [83.44.99.170]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id q2BAhhIp025495 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 11 Mar 2012 11:43:44 +0100 Message-ID: <4F5C81BA.1050001@entel.upc.edu> Date: Sun, 11 Mar 2012 11:43:06 +0100 From: =?ISO-8859-1?Q?Gustau_P=E9rez?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120226 Thunderbird/10.0.2 MIME-Version: 1.0 To: George Neville-Neil References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dash.upc.es [147.83.2.50]); Sun, 11 Mar 2012 11:43:45 +0100 (CET) Cc: FreeBSD current , fs@freebsd.org Subject: Re: RFC: FUSE kernel module for the kernel... 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, 11 Mar 2012 11:58:08 -0000 On 08/03/2012 22:20, George Neville-Neil wrote: > Howdy, > > I've taken the GSoC work done with the FUSE kernel module, and created a patch against HEAD > which I have now subjected to testing using tools/regression/fsx. > > The patch is here: http://people.freebsd.org/~gnn/head-fuse-1.diff > > I would like to commit this patch in the next few days, so, please, if you care > about this take a look and get back to me. > > Thanks, > George Hi, I'm running HEAD r232383 (as of 2 March) + head-fuse-2.diff in AMD64. I've been able to use some fuse fs. I run fsx for a while without problems with some of them (ext4fuse is readonly). Then ones working were: sshfs ntfs-3g ext4fuse others like: truecrypt gvfs (gnome fuse daemon) do fail. I tried fsx with gvfs, that's what I got: [gus@portgus ~]$ /root/deviant2/tools/regression/fsx/fsx .gvfs/multimedia\ a\ harkserver/prova no extend on truncate! not posix! They (truecrypt and gvfs) fail when doing setattr/getattr syscalls. truecrypt complains about not being able to find the recently created encrypted volume (a simple one like $HOME/Desktop/prova). With gvfs, the nautilus (or the application trying to use the file) tries to setattr the file causing gvfs to get an I/O. It happens with nearly all kind of files opened with gvfs, although there are some that are useable. With those files useable with gvfs, when the application closes them causes gvfs to block somewhere, rendering gvfs unuseable. Those two filesystems can be very useful in the desktop, I guess PCBSD could benefit from them. I would say there is something blocking in fuse_vnop_setattr/fuse_vnop_getattr, but I'm not sure how to debug it. Thanks for your help. From owner-freebsd-fs@FreeBSD.ORG Sun Mar 11 22:50:44 2012 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 0B3EB1065674 for ; Sun, 11 Mar 2012 22:50:44 +0000 (UTC) (envelope-from jhellenthal@dataix.net) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id B4C668FC08 for ; Sun, 11 Mar 2012 22:50:43 +0000 (UTC) Received: by iahk25 with SMTP id k25so7644242iah.13 for ; Sun, 11 Mar 2012 15:50:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataix.net; s=rsa; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; bh=7ZtH+vkWiB0q0pE6486CSZAcICsZJX5xzRttmS1++J8=; b=cJcMttxUpPPJNRx994sBEQojrKsUud9aUr6rU41QifEXEjyAkDJKJeAw/dCT2Cf1rd mhI0GA3V5WkV2T55SZ5aOzYxae2t5rjY7fY8JYzNHfE9lE1IyDthIt+A88e6GbBrtfjO xeUkYF5Ec2BxTbgLEHrgFRWdIU3XEanadrs7E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-gm-message-state; bh=7ZtH+vkWiB0q0pE6486CSZAcICsZJX5xzRttmS1++J8=; b=TFMHrJ7QtoY5YBnT0k6SVu/HQOB++QW02T7iAhyN+wGmIVcsvA35TQ0jMOUvviSNVq 9fNnkw9eBlN+z8JrD/Yxy6RFlbrfWgQfwLJXcPwLbfoDjVWYbPu3G2XsmFHTq+kRhVJI fNVwJmp1SdLDVmx1DHTn0tO9UrFIVRjVPGhIRUdn4nTOpQKCJf7UBeJU93yN1m9icpfk bj0TDgg8wNVPmS8TrLmYBzYXjTrf+6fzMZEDWf9BaWKiOYSJgR7/96NkMoeyCHBR99hj 7unZ+X8RiU+dTpioQGJCo7GFflXFmJm+mvPyVBzl4GdWi3gi2bjdIkbXwauhDzxsJYTz Yy+w== Received: by 10.50.94.200 with SMTP id de8mr6874326igb.21.1331506237388; Sun, 11 Mar 2012 15:50:37 -0700 (PDT) Received: from DataIX.net ([99.112.214.173]) by mx.google.com with ESMTPS id wp4sm6280909igc.3.2012.03.11.15.50.36 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 11 Mar 2012 15:50:36 -0700 (PDT) Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.5/8.14.5) with ESMTP id q2BMoXTL036380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Mar 2012 18:50:33 -0400 (EDT) (envelope-from jhellenthal@DataIX.net) Received: (from jhellenthal@localhost) by DataIX.net (8.14.5/8.14.5/Submit) id q2BMoWbj036249; Sun, 11 Mar 2012 18:50:32 -0400 (EDT) (envelope-from jhellenthal@DataIX.net) Date: Sun, 11 Mar 2012 18:50:32 -0400 From: Jason Hellenthal To: Mark Murawski Message-ID: <20120311225032.GA19883@DataIX.net> References: <4F5C4FF8.7080000@intellasoft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F5C4FF8.7080000@intellasoft.net> X-Gm-Message-State: ALoCoQlYE/92ISJgCt+ysJMmFwqp/WHDf68Wa0PfwJIq//iyVOb/+PZHDoxY9DkkHIF8eYvyTYqU Cc: freebsd-fs@freebsd.org Subject: Re: How to change a guid of a zfs device? 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, 11 Mar 2012 22:50:44 -0000 Remove the device from the pool and zero the disk out and add it back to the pool... On Sun, Mar 11, 2012 at 03:10:48AM -0400, Mark Murawski wrote: > How would I go about changing a guid of a zfs physical device? There > doesn't seem to be any options in zpool or zdb for doing guid changes. > > It's a long story, but through a series of drive swaps I've managed to > really screw stuff up. > > Here's my current status > > NAME STATE READ WRITE CKSUM > zstorage UNAVAIL 0 0 0 > mirror-0 ONLINE 0 0 0 > ada4 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 > mirror-1 UNAVAIL 0 0 0 > 14791054479353866913 UNAVAIL 0 0 0 was > /dev/ada4s4 > 5249816505308091368 UNAVAIL 0 0 0 was /dev/ada1 > mirror-2 ONLINE 0 0 0 > ada5 ONLINE 0 0 0 > ada10 ONLINE 0 0 0 > mirror-3 ONLINE 0 0 0 > ada6 ONLINE 0 0 0 > ada8 ONLINE 0 0 0 > mirror-4 ONLINE 0 0 0 > ada7 ONLINE 0 0 0 > ada9 ONLINE 0 0 0 > > > > 14791054479353866913 is really /dev/ada1s4 now > 5249816505308091368 is really /dev/ada0 now > > the problem is, zdb tells me that /dev/ada1 has a guid of > 3184618752700174674 > and zdb says /dev/ada0 has a guid of 16592948394566938185 > > I need to get these to match so that I can reconstruct the pool again > > > > > > > > > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" -- ;s =; From owner-freebsd-fs@FreeBSD.ORG Sun Mar 11 23:55:28 2012 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 831E31065670 for ; Sun, 11 Mar 2012 23:55:28 +0000 (UTC) (envelope-from markm-lists@intellasoft.net) Received: from mail.mystoragebox.com (mail.mystoragebox.com [64.27.7.19]) by mx1.freebsd.org (Postfix) with ESMTP id 6A2878FC12 for ; Sun, 11 Mar 2012 23:55:28 +0000 (UTC) Received: from cpe-67-240-79-210.nycap.res.rr.com ([67.240.79.210] helo=[192.168.35.110]) by mail.mystoragebox.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1S6sHu-00050y-6n for freebsd-fs@freebsd.org; Sun, 11 Mar 2012 19:34:54 -0400 Message-ID: <4F5D3B70.3010607@intellasoft.net> Date: Sun, 11 Mar 2012 19:55:28 -0400 From: Mark Murawski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 CC: freebsd-fs@freebsd.org References: <4F5C4FF8.7080000@intellasoft.net> <20120311225032.GA19883@DataIX.net> In-Reply-To: <20120311225032.GA19883@DataIX.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: How to change a guid of a zfs device? 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, 11 Mar 2012 23:55:28 -0000 That would imply data loss. I did some digging and found some specs on the zfs metadata. There's four copies of the zfs metadata on the disk, two in the beginning, two at the end. I disk-edited and changed the guid stored in the zfs vdev headers and that did the trick, it made the pool come back online for the (was /dev/ada1 disk). The problem remains of getting the other (was /dev/ada4s4) disk to sync back in so it can repair some damaged files. On 03/11/12 18:50, Jason Hellenthal wrote: > > Remove the device from the pool and zero the disk out and add it back to > the pool... > > On Sun, Mar 11, 2012 at 03:10:48AM -0400, Mark Murawski wrote: >> How would I go about changing a guid of a zfs physical device? There >> doesn't seem to be any options in zpool or zdb for doing guid changes. >> >> It's a long story, but through a series of drive swaps I've managed to >> really screw stuff up. >> >> Here's my current status >> >> NAME STATE READ WRITE CKSUM >> zstorage UNAVAIL 0 0 0 >> mirror-0 ONLINE 0 0 0 >> ada4 ONLINE 0 0 0 >> ada3 ONLINE 0 0 0 >> mirror-1 UNAVAIL 0 0 0 >> 14791054479353866913 UNAVAIL 0 0 0 was >> /dev/ada4s4 >> 5249816505308091368 UNAVAIL 0 0 0 was /dev/ada1 >> mirror-2 ONLINE 0 0 0 >> ada5 ONLINE 0 0 0 >> ada10 ONLINE 0 0 0 >> mirror-3 ONLINE 0 0 0 >> ada6 ONLINE 0 0 0 >> ada8 ONLINE 0 0 0 >> mirror-4 ONLINE 0 0 0 >> ada7 ONLINE 0 0 0 >> ada9 ONLINE 0 0 0 >> >> >> >> 14791054479353866913 is really /dev/ada1s4 now >> 5249816505308091368 is really /dev/ada0 now >> >> the problem is, zdb tells me that /dev/ada1 has a guid of >> 3184618752700174674 >> and zdb says /dev/ada0 has a guid of 16592948394566938185 >> >> I need to get these to match so that I can reconstruct the pool again >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Mon Mar 12 00:36:42 2012 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 471B61065674; Mon, 12 Mar 2012 00:36:42 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 24CEC8FC14; Mon, 12 Mar 2012 00:36:41 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id B6131561EC; Sun, 11 Mar 2012 19:36:41 -0500 (CDT) Date: Sun, 11 Mar 2012 19:36:41 -0500 From: Mark Linimon To: bug-followup@FreeBSD.org Message-ID: <20120312003641.GA7675@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@FreeBSD.org Subject: [luis.garces@gmail.com: kern/164445: [zfs][patch] WAS: lseek(2) always returns ENXIO with SEEK_DATA/SEEK_HOLE on 9.0 64bit ZFS] 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, 12 Mar 2012 00:36:42 -0000 ----- Forwarded message from Luis Garces-Erice ----- Date: Wed, 7 Mar 2012 20:53:35 +0100 From: Luis Garces-Erice To: freebsd-bugs@freebsd.org Subject: kern/164445: [zfs][patch] WAS: lseek(2) always returns ENXIO with SEEK_DATA/SEEK_HOLE on 9.0 64bit ZFS Hi all after digging a bit more into this (http://www.freebsd.org/cgi/query-pr.cgi?pr=164445), I've found the problem to be in ZFS or below. The patch attached addresses the symptom, but the problem remains. When invoking SEEK_DATA/SEEK_HOLE on a file on ZFS in FreeBSD 9.0 64 bit, the functions ddi_copyin and ddi_copyout in zfs_ioctl() do not copy the offset passed from the application to the ioctl. The offset is passed correctly to zfs_ioctl(), though, but those functions copy garbage into the offset used by zfs_holey(). The corrupted offset is often bigger than the file, and thus the ioctl returns ENXIO. The patch does the copy of the offset passed from the application correctly, and allows lseek(2) with SEEK_DATA/SEEK_HOLE to be used on ZFS, but it is not a solution. I couldn't see a problem in the assembler of the copyin and copyout functions in sys/amd64/amd64/support.S, but I might be wrong, I'm no assembler expert. -- Luis **** diff -w -u -r sys.orig/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c --- sys.orig/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c 2012-01-03 04:27:03.000000000 +0100 +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c 2012-03-06 11:26:27.000000000 +0100 @@ -296,6 +296,8 @@ if (ddi_copyin((void *)data, &off, sizeof (off), flag)) return (EFAULT); + // ddi_copyin did not copy the offset + off = (offset_t)*((offset_t *)data); zp = VTOZ(vp); zfsvfs = zp->z_zfsvfs; ZFS_ENTER(zfsvfs); @@ -308,6 +310,8 @@ return (error); if (ddi_copyout(&off, (void *)data, sizeof (off), flag)) return (EFAULT); + // ddi_copyout did not copy the offset + *((offset_t *)data)=off; return (0); } return (ENOTTY); ----- End forwarded message ----- From owner-freebsd-fs@FreeBSD.ORG Mon Mar 12 00:43:53 2012 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 28CC31065670; Mon, 12 Mar 2012 00:43:53 +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 EF9808FC21; Mon, 12 Mar 2012 00:43:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2C0hqRi065177; Mon, 12 Mar 2012 00:43:52 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2C0hqoF065173; Mon, 12 Mar 2012 00:43:52 GMT (envelope-from linimon) Date: Mon, 12 Mar 2012 00:43:52 GMT Message-Id: <201203120043.q2C0hqoF065173@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/165923: [nfs] Writing to NFS-backed mmapped files fails if flushed automatically 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, 12 Mar 2012 00:43:53 -0000 Old Synopsis: Writing to NFS-backed mmapped files fails if flushed automatically New Synopsis: [nfs] Writing to NFS-backed mmapped files fails if flushed automatically Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 12 00:43:35 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=165923 From owner-freebsd-fs@FreeBSD.ORG Mon Mar 12 00:45:23 2012 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 C1BCA1065672; Mon, 12 Mar 2012 00:45:23 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 1F7118FC15; Mon, 12 Mar 2012 00:45:22 +0000 (UTC) Received: by wibhq7 with SMTP id hq7so2371143wib.13 for ; Sun, 11 Mar 2012 17:45:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FS8egJgIcKD7ZFlC1mE7peMrK/AdnuV2UVbW50iKNsA=; b=YIUZtncOWMAuQfCTK+iCR9CjpoD7C8Rvzoh5NCztPtEJ25S3kGfwbBD1iEZ+yiCeuB y6YMgzAG5Kgif0wU+M/6heADr/91oCgnjtMJ51Dei+cwq/xkom9SIzil2PZnLpbJWjYc 8TT4qpgnzPSczMvQzEEv6PrlAIlVG5nN3gmX15lRFhZh97F6cokH7TlSjhkHPldo9Qk9 RfmvGmlz4z/GoF05tYcmFZ0i665jCL7qd6O8GXDgZTSbxtwOJ1CLny2ATzNSnhvswDgR GtJpr0kA2Kyr+TcRTb1fRmQKZKlDhqry1v0yEhvusRoSmb9L6hQnfLU14YahY31QJj69 M9tA== MIME-Version: 1.0 Received: by 10.216.132.30 with SMTP id n30mr5999626wei.52.1331513121922; Sun, 11 Mar 2012 17:45:21 -0700 (PDT) Received: by 10.216.229.10 with HTTP; Sun, 11 Mar 2012 17:45:21 -0700 (PDT) In-Reply-To: References: Date: Mon, 12 Mar 2012 11:15:21 +1030 Message-ID: From: Matt Thyer To: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: growfs remove ufs/label and can't reset it with tunefs 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, 12 Mar 2012 00:45:23 -0000 2012/3/9 Olivier Cochard-Labb=E9 > Hi all, > > once run growfs on a partition that had an UFS label, this label is > removed and it's no more possible to re-set it with tunefs. > Here is how to reproduce (tested on 8.3 and 9.0): > > mdconfig -a -t malloc -s 10MB > gpart create -s mbr /dev/md0 > gpart add -t freebsd -s 5MB /dev/md0 > newfs -L THELABEL /dev/md0s1 > glabel status | grep THELABEL > =3D> Label is present, now we resize the slice: > gpart resize -i 1 /dev/md0 > glabel status | grep THELABEL > =3D> Label is still present, now we growfs the slice: > growfs /dev/md0s1 > glabel status | grep THELABEL > =3D> UFS label disapear ! > Ok, I will try to re-set it: > tunefs -L THELABEL /dev/md0s1 > glabel status | grep THELABEL > =3D> Still no label !?! > > Should I create a PR about this problem ? > > Regards, > > Olivier > Yes, It is important to record this problem in the PR system. I suspect that the problem is with growfs as it needs to be taught to not overwrite the end of the volume where the label information is stored. (It will need to examine the volume to see if GEOM has information stored at the end of the volume such that the grow should not overwrite the GEOM metadata). Matthew From owner-freebsd-fs@FreeBSD.ORG Mon Mar 12 01:01:06 2012 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 30DED106566B; Mon, 12 Mar 2012 01:01:06 +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 03F2A8FC1D; Mon, 12 Mar 2012 01:01:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2C115YO076917; Mon, 12 Mar 2012 01:01:05 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2C115CU076909; Mon, 12 Mar 2012 01:01:05 GMT (envelope-from linimon) Date: Mon, 12 Mar 2012 01:01:05 GMT Message-Id: <201203120101.q2C115CU076909@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/165950: [ffs] SU+J and fsck problem 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, 12 Mar 2012 01:01:06 -0000 Old Synopsis: SU+J and fsck problem New Synopsis: [ffs] SU+J and fsck problem Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 12 01:00:07 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=165950 From owner-freebsd-fs@FreeBSD.ORG Mon Mar 12 07:24:03 2012 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 A78F01065672; Mon, 12 Mar 2012 07:24:03 +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 7AC158FC0A; Mon, 12 Mar 2012 07:24:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2C7O3xK039134; Mon, 12 Mar 2012 07:24:03 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2C7O3lr039130; Mon, 12 Mar 2012 07:24:03 GMT (envelope-from linimon) Date: Mon, 12 Mar 2012 07:24:03 GMT Message-Id: <201203120724.q2C7O3lr039130@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/165962: [ufs] growfs remove ufs label and it's no more possible to reset it with tunefs 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, 12 Mar 2012 07:24:03 -0000 Old Synopsis: growfs remove ufs label and it's no more possible to reset it with tunefs New Synopsis: [ufs] growfs remove ufs label and it's no more possible to reset it with tunefs Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 12 07:23:27 UTC 2012 Responsible-Changed-Why: sounds like something for freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=165962 From owner-freebsd-fs@FreeBSD.ORG Mon Mar 12 11:07:11 2012 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 24401106564A for ; Mon, 12 Mar 2012 11:07:11 +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 122628FC1E for ; Mon, 12 Mar 2012 11:07:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2CB7BMr072320 for ; Mon, 12 Mar 2012 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2CB7Aw4072318 for freebsd-fs@FreeBSD.org; Mon, 12 Mar 2012 11:07:10 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Mar 2012 11:07:10 GMT Message-Id: <201203121107.q2CB7Aw4072318@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, 12 Mar 2012 11:07:11 -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/165962 fs [ufs] growfs remove ufs label and it's no more possibl o kern/165950 fs [ffs] SU+J and fsck problem o kern/165923 fs [nfs] Writing to NFS-backed mmapped files fails if flu o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/162362 fs [snapshots] [panic] ufs with snapshot(s) panics when g o kern/162083 fs [zfs] [panic] zfs unmount -f pool o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161897 fs [zfs] [patch] zfs partition probing causing long delay o kern/161864 fs [ufs] removing journaling from UFS partition fails on o bin/161807 fs [patch] add option for explicitly specifying metadata o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161511 fs [unionfs] Filesystem deadlocks when using multiple uni o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic o kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159663 fs [socket] [nullfs] sockets don't work though nullfs mou o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs f kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa 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/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 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/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors 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 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 f bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev 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 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 bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR 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/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/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 p 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/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb 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 p 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/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/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/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero 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 o kern/123939 fs [msdosfs] corrupts new files f sparc/123566 fs [zfs] zpool import issue: EOVERFLOW 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/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F 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 [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount 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/116583 fs [ffs] [hang] System freezes for short time when using 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] [iconv] mount_msdosfs: msdosfs_iconv: Operat 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/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 s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' 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 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/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits 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 bin/70600 fs fsck(8) throws files away when it can't grow lost+foun 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 bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 264 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Mar 12 18:10:33 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 94DC5106566B; Mon, 12 Mar 2012 18:10:33 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6C7AD8FC29; Mon, 12 Mar 2012 18:10:33 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2CIAXT9068487; Mon, 12 Mar 2012 18:10:33 GMT (envelope-from trasz@freefall.freebsd.org) Received: (from trasz@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2CIAX0Z068478; Mon, 12 Mar 2012 18:10:33 GMT (envelope-from trasz) Date: Mon, 12 Mar 2012 18:10:33 GMT Message-Id: <201203121810.q2CIAX0Z068478@freefall.freebsd.org> To: trasz@FreeBSD.org, freebsd-fs@FreeBSD.org, trasz@FreeBSD.org From: trasz@FreeBSD.org Cc: Subject: Re: kern/165962: [ufs] growfs remove ufs label and it's no more possible to reset it with tunefs 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, 12 Mar 2012 18:10:33 -0000 Synopsis: [ufs] growfs remove ufs label and it's no more possible to reset it with tunefs Responsible-Changed-From-To: freebsd-fs->trasz Responsible-Changed-By: trasz Responsible-Changed-When: Mon Mar 12 18:10:32 UTC 2012 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=165962 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 00:28:35 2012 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 F38321065673 for ; Tue, 13 Mar 2012 00:28:34 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) by mx1.freebsd.org (Postfix) with ESMTP id BC0698FC15 for ; Tue, 13 Mar 2012 00:28:34 +0000 (UTC) Received: from [209.249.190.124] (helo=[10.2.210.29]) by vps.hungerhost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1S75YB-0006jy-AQ; Mon, 12 Mar 2012 09:44:35 -0400 Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: George Neville-Neil In-Reply-To: <1331452568.2105.7.camel@nsl> Date: Mon, 12 Mar 2012 09:44:40 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <0C9EC90B-8846-4C19-A744-F1ABEFB180D6@neville-neil.com> References: <0826905E-32FE-4F44-923F-220D7A11E65C@neville-neil.com> <1331452568.2105.7.camel@nsl> To: Kevin Lo X-Mailer: Apple Mail (2.1257) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com Cc: freebsd-fs@freebsd.org Subject: Re: RFC: FUSE kernel module for the kernel... 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, 13 Mar 2012 00:28:35 -0000 On Mar 11, 2012, at 03:56 , Kevin Lo wrote: > George Neville-Neil wrote: >> On Mar 9, 2012, at 13:44 , Mark Felder wrote: >>=20 >>> The true test for me is "can you run mp3fs without causing kernel = panics now?" as I'm told that's why it's not in ports anymore. >>=20 >> At the moment I'm only using the FUSE example, but I have run = glusterfs on it, and also sshfs. >=20 > There's a known problem about exporting fuse file system export=20 > over nfs. I'm wondering if your patch will fix that. >=20 I have not tried this. I'll put it on my list of things to check. Best, George From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 16:09:05 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F2C4106566B for ; Tue, 13 Mar 2012 16:09:05 +0000 (UTC) (envelope-from markm-lists@intellasoft.net) Received: from mail.mystoragebox.com (mail.mystoragebox.com [64.27.7.19]) by mx1.freebsd.org (Postfix) with ESMTP id EF6C78FC16 for ; Tue, 13 Mar 2012 16:09:04 +0000 (UTC) Received: from cpe-67-240-79-210.nycap.res.rr.com ([67.240.79.210] helo=[192.168.35.110]) by mail.mystoragebox.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1S7TxR-0006rN-Gn for freebsd-fs@freebsd.org; Tue, 13 Mar 2012 11:48:17 -0400 Message-ID: <4F5F7116.3020400@intellasoft.net> Date: Tue, 13 Mar 2012 12:08:54 -0400 From: Mark Murawski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ZFS file corruption problem 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, 13 Mar 2012 16:09:05 -0000 So I have this zpool with corrupted files running on freebsd 9-release amd64. The corrupted files can go away, that's not a big deal Here's the problem. $ ls -al /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 No errors in dmesg, the process is now stuck in the D state, and is also unkillable. A clean shutdown is also not possible as trying to kill processes using the pool and access the pool to unmount it will block. What's a good starting point to resolve this problem? Also... note that this was happening even before I started playing with the guids to try and get the pool back up. Here's the scenario that lead up to the problem: mirror-1 was consisting of a 120gig drive and an 80 gig drive I shut down, physically replaced the 80 with a 500, zpool attached it to /dev/ada2 as a mirror, and let zpool resilver. Resilver completed, I physically replaced the 120 with a 500, zpool attached it to the new 500 and waited for a resilver. Due to bugs in the promise sata300 tx4 drivers, the resilver started having problems, one of the 500's dropped out of the pool with ata2: timeout waiting to issue command ata2: error issuing ATA_IDENTIFY command ata2: SIGNATURE: ffffffff ata2: timeout waiting to issue command ata2: error issuing ATA_IDENTIFY command ata2: SIGNATURE: ffffffff Upon reboot I now had corrupted files. The pool auto expanded and now I can't re attach the 80 or 120 to recover corrupted files. So the main problem is the total usability of the pool when hitting a corrupted file. pool: zstorage state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scan: resilvered 22.5G in 0h47m with 29682 errors on Mon Mar 12 02:20:56 2012 config: NAME STATE READ WRITE CKSUM zstorage DEGRADED 29.0K 0 0 mirror-0 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada3 ONLINE 0 0 0 mirror-1 DEGRADED 58.0K 0 0 17331410140726386358 UNAVAIL 0 0 0 was /dev/ada1s4 ada2 ONLINE 0 0 58.0K mirror-2 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada10 ONLINE 0 0 0 mirror-3 DEGRADED 0 0 0 14693115181240286208 REMOVED 0 0 0 was /dev/ada6 ada8 ONLINE 0 0 0 mirror-4 DEGRADED 0 0 0 ada7 ONLINE 0 0 0 83782446513674500 REMOVED 0 0 0 was /dev/ada9 errors: Permanent errors have been detected in the following files: /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 /storage/zfs/Johns Stuff/gallery/._IMG_1225.psd /storage/zfs/Johns Stuff/gallery/._IMG_1226.psd /storage/zfs/Johns Stuff/gallery/._IMG_1243.psd /storage/zfs/Johns Stuff/gallery/._a.jpg ...etc, and 500 more From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 17:56:52 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 014D6106564A; Tue, 13 Mar 2012 17:56:52 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) by mx1.freebsd.org (Postfix) with ESMTP id B96688FC0A; Tue, 13 Mar 2012 17:56:51 +0000 (UTC) Received: from [209.249.190.124] (helo=punk.neville-neil.com.neville-neil.com) by vps.hungerhost.com with esmtpa (Exim 4.69) (envelope-from ) id 1S7Vxb-0007y4-Sq; Tue, 13 Mar 2012 13:56:40 -0400 Date: Tue, 13 Mar 2012 13:56:35 -0400 Message-ID: <86ehswtmek.wl%gnn@neville-neil.com> From: gnn@freebsd.org To: Gustau =?UTF-8?B?UMOpcmV6?= In-Reply-To: <4F5C81BA.1050001@entel.upc.edu> References: <4F5C81BA.1050001@entel.upc.edu> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/23.3 (amd64-portbld-freebsd9.0) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com Cc: FreeBSD current , fs@freebsd.org Subject: Re: RFC: FUSE kernel module for the kernel... 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, 13 Mar 2012 17:56:52 -0000 At Sun, 11 Mar 2012 11:43:06 +0100, Gustau Pérez wrote: >=20 > On 08/03/2012 22:20, George Neville-Neil wrote: > > Howdy, > > > > I've taken the GSoC work done with the FUSE kernel module, and created = a patch against HEAD > > which I have now subjected to testing using tools/regression/fsx. > > > > The patch is here: http://people.freebsd.org/~gnn/head-fuse-1.diff > > > > I would like to commit this patch in the next few days, so, please, if = you care > > about this take a look and get back to me. > > > > Thanks, > > George >=20 > Hi, >=20 > I'm running HEAD r232383 (as of 2 March) + head-fuse-2.diff in AMD64. >=20 > I've been able to use some fuse fs. I run fsx for a while without=20 > problems with some of them (ext4fuse is readonly). Then ones working were: >=20 > sshfs > ntfs-3g > ext4fuse >=20 > others like: >=20 > truecrypt > gvfs (gnome fuse daemon) >=20 > do fail. I tried fsx with gvfs, that's what I got: >=20 > [gus@portgus ~]$ /root/deviant2/tools/regression/fsx/fsx=20 > .gvfs/multimedia\ a\ harkserver/prova > no extend on truncate! not posix! >=20 > They (truecrypt and gvfs) fail when doing setattr/getattr syscalls.=20 > truecrypt complains about not being able to find the recently created=20 > encrypted volume (a simple one like $HOME/Desktop/prova). >=20 > With gvfs, the nautilus (or the application trying to use the file)=20 > tries to setattr the file causing gvfs to get an I/O. It happens with=20 > nearly all kind of files opened with gvfs, although there are some that=20 > are useable. With those files useable with gvfs, when the application=20 > closes them causes gvfs to block somewhere, rendering gvfs unuseable. >=20 > Those two filesystems can be very useful in the desktop, I guess=20 > PCBSD could benefit from them. >=20 > I would say there is something blocking in=20 > fuse_vnop_setattr/fuse_vnop_getattr, but I'm not sure how to debug it. >=20 > Thanks for your help. >=20 Thanks for the detailed report. I'll look into this in a bit, I'm traveling for two weeks. Best, George From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 18:21:30 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 837651065675 for ; Tue, 13 Mar 2012 18:21:30 +0000 (UTC) (envelope-from mjl@luckie.org.nz) Received: from caida.org (rommie.caida.org [192.172.226.78]) by mx1.freebsd.org (Postfix) with ESMTP id 6B3188FC1A for ; Tue, 13 Mar 2012 18:21:30 +0000 (UTC) Received: from sorcerer.caida.org (sorcerer.caida.org [192.172.226.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by caida.org (Postfix) with ESMTP id 3534BB980 for ; Tue, 13 Mar 2012 11:21:30 -0700 (PDT) Received: from localhost.caida.org ([127.0.0.1] helo=sorcerer.caida.org) by sorcerer.caida.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1S7WLi-000Mp9-4K for freebsd-fs@freebsd.org; Tue, 13 Mar 2012 11:21:30 -0700 Message-ID: <4F5F902A.2030108@luckie.org.nz> Date: Tue, 13 Mar 2012 11:21:30 -0700 From: Matthew Luckie User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20120218 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: freebsd 9.0R panic in vfs_cache.c:364 cache_zap() 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, 13 Mar 2012 18:21:30 -0000 Hi This is likely to be a useless report because I don't have a crash dump. I upgraded to freebsd 9.0R on Friday night and last night (Monday) it panicked during a nightly rsync. First time I've had a panic during a nightly rsync on this machine, which has been running for about two years. I searched lists to see if there was a known problem but didn't come across anything, and I'm not sure what to search for. There seem to have been a few commits on RELENG_9 to vfs_cache.c since release, is it worthwhile upgrading to a 9-stable? $ addr2line -e /boot/kernel/kernel.symbols 0xc0a9754d /usr/src/sys/kern/vfs_cache.c:364 The numbers marked with # correspond to the frames below $ addr2line -e /boot/kernel/kernel.symbols 0xc0a977e8 0xc0aabe89 0xc0ab061b 0xc0ab0769 0xc0c5f589 0xc0c5fa5e 0xc0c6d7dc 0xc0c6d86a 0xc0d772e2 0xc0a99206 0xc0d791e6 #6 /usr/src/sys/kern/vfs_cache.c:816 #7 /usr/obj/usr/src/sys/spandex/./machine/pcpu.h:244 #8 /usr/obj/usr/src/sys/spandex/./vnode_if.h:879 #9 /usr/src/sys/kern/vfs_subr.c:994 #10 /usr/src/sys/ufs/ffs/ffs_vfsops.c:1616 #11 /usr/src/sys/ufs/ffs/ffs_vfsops.c:1561 #12 /usr/src/sys/ufs/ufs/ufs_lookup.c:749 #13 /usr/src/sys/ufs/ufs/ufs_lookup.c:215 #14 /usr/obj/usr/src/sys/spandex/vnode_if.c:187 #15 /usr/obj/usr/src/sys/spandex/./vnode_if.h:80 #16 /usr/obj/usr/src/sys/spandex/vnode_if.c:123 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x15 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0a9754d stack pointer = 0x28:0xed94f744 frame pointer = 0x28:0xed94f758 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 78950 (rsync) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xc0a4e9d7 at kdb_backtrace+0x47 #1 0xc0a1bf37 at panic+0x117 #2 0xc0d57013 at trap_fatal+0x323 #3 0xc0d570cd at trap_pfault+0xad #4 0xc0d57e55 at trap+0x465 #5 0xc0d40dac at calltrap+0x6 #6 0xc0a977e8 at cache_purge+0x68 #7 0xc0aabe89 at vgonel+0x2d9 #8 0xc0ab061b at vnlru_free+0x2bb #9 0xc0ab0769 at getnewvnode+0x69 #10 0xc0c5f589 at ffs_vgetf+0x109 #11 0xc0c5fa5e at ffs_vget+0x2e #12 0xc0c6d7dc at ufs_lookup_ino+0xaec #13 0xc0c6d86a at ufs_lookup+0x2a #14 0xc0d772e2 at VOP_CACHEDLOOKUP_APV+0x42 #15 0xc0a99206 at vfs_cache_lookup+0xd6 #16 0xc0d791e6 at VOP_LOOKUP_APV+0x46 Matthew From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 18:53:27 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C734106566C for ; Tue, 13 Mar 2012 18:53:27 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from mo-p05-ob6.rzone.de (mo-p05-ob6.rzone.de [IPv6:2a01:238:20a:202:53f5::1]) by mx1.freebsd.org (Postfix) with ESMTP id 6B5C58FC08 for ; Tue, 13 Mar 2012 18:53:26 +0000 (UTC) X-RZG-AUTH: :LWIKdA2leu0bPbLmhzXgqn0MTG6qiKEwQRWfNxSw4HzYIwjsnvdDt2oX8drk23mo3jRFKXso X-RZG-CLASS-ID: mo05 Received: from [192.168.179.39] (hmbg-5f764cd6.pool.mediaWays.net [95.118.76.214]) by post.strato.de (mrclete mo23) (RZmta 28.1 DYNA|AUTH) with (DHE-RSA-AES128-SHA encrypted) ESMTPA id I013c9o2DIAB4u for ; Tue, 13 Mar 2012 19:53:25 +0100 (MET) Message-ID: <4F5F97A4.6070000@brockmann-consult.de> Date: Tue, 13 Mar 2012 19:53:24 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F5F7116.3020400@intellasoft.net> In-Reply-To: <4F5F7116.3020400@intellasoft.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: ZFS file corruption problem 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, 13 Mar 2012 18:53:27 -0000 Am 13.03.2012 17:08, schrieb Mark Murawski: > So I have this zpool with corrupted files running on freebsd 9-release > amd64. The corrupted files can go away, that's not a big deal > > Here's the problem. > > $ ls -al /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 > Since this is one of the corrupt files, I guess ZFS would like to block until it can return a good copy (such as if you put the mirror disk back in)... so to fix this, you need to remove the file or restore from backup (or add that mirror disk back in, which I will assume you can't): rm /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 (in the case of a file that should exist empty instead of being removed, eg. a log where the log writer does not have write permission to the directory, do touch also) or maybe this works: mv /somewhere_with_backup/IMG_5576.CR2 /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 And if there are more errors, you probably need to scrub to expand the pool or for "zpool clear" to work. > block> > > No errors in dmesg, the process is now stuck in the D state, and is > also unkillable. A clean shutdown is also not possible as trying to > kill processes using the pool and access the pool to unmount it will > block. > > What's a good starting point to resolve this problem? > > Also... note that this was happening even before I started playing > with the guids to try and get the pool back up. > > Here's the scenario that lead up to the problem: > > mirror-1 was consisting of a 120gig drive and an 80 gig drive > I shut down, physically replaced the 80 with a 500, zpool attached it > to /dev/ada2 as a mirror, and let zpool resilver. > > Resilver completed, I physically replaced the 120 with a 500, zpool > attached it to the new 500 and waited for a resilver. > > Due to bugs in the promise sata300 tx4 drivers, the resilver started > having problems, one of the 500's dropped out of the pool with > > ata2: timeout waiting to issue command > ata2: error issuing ATA_IDENTIFY command > ata2: SIGNATURE: ffffffff > ata2: timeout waiting to issue command > ata2: error issuing ATA_IDENTIFY command > ata2: SIGNATURE: ffffffff > > Upon reboot I now had corrupted files. The pool auto expanded and now > I can't re attach the 80 or 120 to recover corrupted files. > > So the main problem is the total usability of the pool when hitting a > corrupted file. > > > pool: zstorage > state: DEGRADED > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: http://www.sun.com/msg/ZFS-8000-8A > scan: resilvered 22.5G in 0h47m with 29682 errors on Mon Mar 12 > 02:20:56 2012 > config: > > NAME STATE READ WRITE CKSUM > zstorage DEGRADED 29.0K 0 0 > mirror-0 ONLINE 0 0 0 > ada4 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 > mirror-1 DEGRADED 58.0K 0 0 > 17331410140726386358 UNAVAIL 0 0 0 was > /dev/ada1s4 > ada2 ONLINE 0 0 58.0K > mirror-2 ONLINE 0 0 0 > ada5 ONLINE 0 0 0 > ada10 ONLINE 0 0 0 > mirror-3 DEGRADED 0 0 0 > 14693115181240286208 REMOVED 0 0 0 was > /dev/ada6 > ada8 ONLINE 0 0 0 > mirror-4 DEGRADED 0 0 0 > ada7 ONLINE 0 0 0 > 83782446513674500 REMOVED 0 0 0 was > /dev/ada9 > > > errors: Permanent errors have been detected in the following files: > > /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 > /storage/zfs/Johns Stuff/gallery/._IMG_1225.psd > /storage/zfs/Johns Stuff/gallery/._IMG_1226.psd > /storage/zfs/Johns Stuff/gallery/._IMG_1243.psd > /storage/zfs/Johns Stuff/gallery/._a.jpg > ...etc, and 500 more > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 22:37:01 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05DA4106564A for ; Tue, 13 Mar 2012 22:37:01 +0000 (UTC) (envelope-from peter@pean.org) Received: from system.jails.se (system.jails.se [IPv6:2001:16d8:cc1e:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id AB1178FC12 for ; Tue, 13 Mar 2012 22:37:00 +0000 (UTC) Received: from localhost (system.jails.se [91.205.63.85]) by system.jails.se (Postfix) with SMTP id 90472223E4C for ; Tue, 13 Mar 2012 23:36:58 +0100 (CET) Received: from [172.25.0.21] (c-1105e155.166-7-64736c14.cust.bredbandsbolaget.se [85.225.5.17]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by system.jails.se (Postfix) with ESMTPSA id CECA1223E46 for ; Tue, 13 Mar 2012 23:36:57 +0100 (CET) From: =?iso-8859-1?Q?Peter_Ankerst=E5l?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 13 Mar 2012 23:37:03 +0100 Message-Id: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> To: fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) X-DSPAM-Result: Innocent X-DSPAM-Processed: Tue Mar 13 23:36:58 2012 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 4f5fcc0a26811708714271 X-DSPAM-Factors: 27, could, 0.40000, but, 0.40000, but, 0.40000, Subject*raidz., 0.40000, Received*cipher+AES128, 0.40000, just, 0.40000, Received* List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 22:37:01 -0000 Hi, I have a newly installed 3 disk raidz but I just got this: # uname -a FreeBSD torus 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 = UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC = amd64 # zpool status -v pool: store state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scan: scrub repaired 0 in 1h50m with 0 errors on Tue Mar 13 23:02:53 = 2012 config: NAME STATE READ WRITE CKSUM store ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 ada2 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: <0x7e>:<0x1f3> The <0x7e>:<0x1f3> was store/backup:somefile but then I first removed = the file and <0x1f3> appeared and then I removed the whole zfs filesystem and the <0x7e> appeared..=20 First of all, how could I get this type of error when I have a redundant = disk setup, also it doesn't show any checksum errors. And second, is = there a way to clear this error? After all only one file was affected = and is now removed. Actually the whole filesystem is removed.= From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 22:41:12 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BBCBB106566B; Tue, 13 Mar 2012 22:41:12 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from dash.upc.es (dash.upc.es [147.83.2.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3B2908FC08; Tue, 13 Mar 2012 22:41:11 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by dash.upc.es (8.14.1/8.13.1) with ESMTP id q2DMf3sP013249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 13 Mar 2012 23:41:03 +0100 Received: from portgus.lan (170.Red-83-44-99.dynamicIP.rima-tde.net [83.44.99.170]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id q2DMf0uE024989 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 13 Mar 2012 23:41:02 +0100 Message-ID: <4F5FCCD7.7070609@entel.upc.edu> Date: Tue, 13 Mar 2012 23:40:23 +0100 From: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120226 Thunderbird/10.0.2 MIME-Version: 1.0 To: gnn@freebsd.org References: <4F5C81BA.1050001@entel.upc.edu> <86ehswtmek.wl%gnn@neville-neil.com> In-Reply-To: <86ehswtmek.wl%gnn@neville-neil.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dash.upc.es [147.83.2.50]); Tue, 13 Mar 2012 23:41:03 +0100 (CET) Cc: FreeBSD current , fs@freebsd.org Subject: Re: RFC: FUSE kernel module for the kernel... 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, 13 Mar 2012 22:41:12 -0000 On 13/03/2012 18:56, gnn@freebsd.org wrote: > At Sun, 11 Mar 2012 11:43:06 +0100, > Gustau Pérez wrote: >> On 08/03/2012 22:20, George Neville-Neil wrote: >>> Howdy, >>> >>> I've taken the GSoC work done with the FUSE kernel module, and created a patch against HEAD >>> which I have now subjected to testing using tools/regression/fsx. >>> >>> The patch is here: http://people.freebsd.org/~gnn/head-fuse-1.diff >>> >>> I would like to commit this patch in the next few days, so, please, if you care >>> about this take a look and get back to me. >>> >>> Thanks, >>> George >> Hi, >> >> I'm running HEAD r232383 (as of 2 March) + head-fuse-2.diff in AMD64. >> >> I've been able to use some fuse fs. I run fsx for a while without >> problems with some of them (ext4fuse is readonly). Then ones working were: >> >> sshfs >> ntfs-3g >> ext4fuse >> >> others like: >> >> truecrypt >> gvfs (gnome fuse daemon) >> >> do fail. I tried fsx with gvfs, that's what I got: >> >> [gus@portgus ~]$ /root/deviant2/tools/regression/fsx/fsx >> .gvfs/multimedia\ a\ harkserver/prova >> no extend on truncate! not posix! >> >> They (truecrypt and gvfs) fail when doing setattr/getattr syscalls. >> truecrypt complains about not being able to find the recently created >> encrypted volume (a simple one like $HOME/Desktop/prova). >> >> With gvfs, the nautilus (or the application trying to use the file) >> tries to setattr the file causing gvfs to get an I/O. It happens with >> nearly all kind of files opened with gvfs, although there are some that >> are useable. With those files useable with gvfs, when the application >> closes them causes gvfs to block somewhere, rendering gvfs unuseable. >> >> Those two filesystems can be very useful in the desktop, I guess >> PCBSD could benefit from them. >> >> I would say there is something blocking in >> fuse_vnop_setattr/fuse_vnop_getattr, but I'm not sure how to debug it. >> >> Thanks for your help. >> > Thanks for the detailed report. I'll look into this in a bit, I'm > traveling for two weeks. > > Best, > George Hi, testing ntfs-3g, after doing a bit large transfer with rsync, I found I couldn't unmount the filesystem. After some tries and before checking that no process was accessing the filesystem I tried to force the unmont. After that the system paniced instantly. I'm running HEAD/AMD64 r232862+head-fuse-2.diff. I have a dump of it, but it would seem that fuse is missing debug symbols (I don't know why), so the backtrace is incomplete. I compiled fuse just by doing make on $SRCDIR/sys/modules/fuse. I'll try to reproduce the panic and figure out what happens. Any help would be also appreciated on this other issue. Gustau From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 22:54:02 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 214CF106566C for ; Tue, 13 Mar 2012 22:54:02 +0000 (UTC) (envelope-from peter@pean.org) Received: from system.jails.se (system.jails.se [IPv6:2001:16d8:cc1e:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id C372A8FC0C for ; Tue, 13 Mar 2012 22:54:01 +0000 (UTC) Received: from localhost (system.jails.se [91.205.63.85]) by system.jails.se (Postfix) with SMTP id 858BD223F94 for ; Tue, 13 Mar 2012 23:54:00 +0100 (CET) Received: from [172.25.0.21] (c-1105e155.166-7-64736c14.cust.bredbandsbolaget.se [85.225.5.17]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by system.jails.se (Postfix) with ESMTPSA id D4B74223F90 for ; Tue, 13 Mar 2012 23:53:59 +0100 (CET) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1251.1) From: =?iso-8859-1?Q?Peter_Ankerst=E5l?= In-Reply-To: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> Date: Tue, 13 Mar 2012 23:54:05 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <207A0A74-ECF2-4EBA-BB7B-337372CFBD44@pean.org> References: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> To: fs@freebsd.org X-Mailer: Apple Mail (2.1251.1) X-DSPAM-Result: Innocent X-DSPAM-Processed: Tue Mar 13 23:54:00 2012 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 4f5fd00826812009221729 X-DSPAM-Factors: 27, could, 0.40000, but, 0.40000, but, 0.40000, Subject*raidz., 0.40000, reports, 0.40000, Received*cipher+AES128, 0.40000, In-Reply-To*4425+9338, 0.40000, just, 0.40000, Received*, 0.40000, "freebsd, 0.40000, or, 0.40000, >+status, 0.40000, Received*Tue, 0.40000, 23+02, 0.40000, an, 0.40000, Received*[172.25.0.21], 0.40000, http+//lists, 0.40000, state+ONLINE, 0.40000, pool+from, 0.40000 Cc: Subject: Re: Problem with corrupted file on raidz. 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, 13 Mar 2012 22:54:02 -0000 And oh.=20 scrub runs fine and reports 0 errors. But zpool clear does not clear = these errors but from what I've read this is expected behavior.=20 On Mar 13, 2012, at 11:37 PM, Peter Ankerst=E5l wrote: > Hi, I have a newly installed 3 disk raidz but I just got this: >=20 > # uname -a > FreeBSD torus 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 = UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC = amd64 >=20 > # zpool status -v > pool: store > state: ONLINE > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore = the > entire pool from backup. > see: http://www.sun.com/msg/ZFS-8000-8A > scan: scrub repaired 0 in 1h50m with 0 errors on Tue Mar 13 23:02:53 = 2012 > config: >=20 > NAME STATE READ WRITE CKSUM > store ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > ada0 ONLINE 0 0 0 > ada1 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 >=20 > errors: Permanent errors have been detected in the following files: >=20 > <0x7e>:<0x1f3> >=20 >=20 > The <0x7e>:<0x1f3> was store/backup:somefile but then I first removed = the file and <0x1f3> appeared and then I removed > the whole zfs filesystem and the <0x7e> appeared..=20 >=20 > First of all, how could I get this type of error when I have a = redundant disk setup, also it doesn't show any checksum errors. And = second, is there a way to clear this error? After all only one file was = affected and is now removed. Actually the whole filesystem is removed. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >=20 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 13 22:54:31 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F1AB5106564A for ; Tue, 13 Mar 2012 22:54:31 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id AF1998FC1F for ; Tue, 13 Mar 2012 22:54:31 +0000 (UTC) Received: by vcmm1 with SMTP id m1so1634298vcm.13 for ; Tue, 13 Mar 2012 15:54:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m4aOc6pa8m0wU3cSTvbz51wllsuo4qZKpQ6QHgAd/Mg=; b=WH+GlJlloaabWzSDGIUMlwXKefWLVFrf2SWY+u303tdYwXfogjEEpeLZQ2NuY7qpq8 Qz89k7cJu69wgVVoQ62F4RUR7fI54T/XavTfY9PWzqpLn4StWCzHGOLMvqq5aprFMtGO eW7IAGEIHLoEFKwTXmeXWCucQl4w0LMHENnKIPmtXOUWNQnKiHLEGDbI5pT39pTxfWgD Q0sn0d8Fw330TU8G+BwdUrHAMTA6JWXy0lWck8HeR1QhusUaNsNEQecZFNPk/QNxEmEL vFnWqE6ybCBfA2Ncqk9WlokdSGChVmLURlujXxJ2CPjISa0s9ILhqD5UpdfI8ZZywhfX mzsw== MIME-Version: 1.0 Received: by 10.52.93.77 with SMTP id cs13mr240927vdb.71.1331679270638; Tue, 13 Mar 2012 15:54:30 -0700 (PDT) Received: by 10.220.178.74 with HTTP; Tue, 13 Mar 2012 15:54:30 -0700 (PDT) In-Reply-To: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> References: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> Date: Tue, 13 Mar 2012 15:54:30 -0700 Message-ID: From: Freddie Cash To: =?UTF-8?Q?Peter_Ankerst=C3=A5l?= Content-Type: text/plain; charset=UTF-8 Cc: fs@freebsd.org Subject: Re: Problem with corrupted file on raidz. 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, 13 Mar 2012 22:54:32 -0000 Remove any snapshots pointing to the filesystem (although there shouldn't be any if the entire filesystem is gone). Then scrub the pool. That should remove the error message, as that znode/block pointer/whatever is removed. From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 01:02:35 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A25E1065670; Wed, 14 Mar 2012 01:02:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1B3DC8FC17; Wed, 14 Mar 2012 01:02:34 +0000 (UTC) Received: by ggnk4 with SMTP id k4so1525741ggn.13 for ; Tue, 13 Mar 2012 18:02:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=J+LubNwGcjs3nuBIZcEg2iLS9iEMWucclNdL8FQu8hg=; b=rJzJzmL2r/MxUFMaB1TjEzTWecYfdvfSlW2BfqW5VneHm6BEIXtFhGEN24uVg8Q9Qo BWvHzmk0ydVvNoqhKis2x1gYSYbJLFbTPdx3jO9HvJB39fpGV5rmX9bAKNvSr8BSlpTz Tw4iffCafVWSXshzlboeNwf7PDrOqopOxTnv00kzdXWVfWHUUNlfVglQ8CyipY8T2Hg7 f6IxsrKMrjsZSwDy2HSuNeuiUR2EPA6OjKcmZK6pxOIPY3Zjcjrupugi6RDKEQagNB74 5t58CaYAgBZudFJhl2W5o9o+rXuitM3geKQPoi1KSWmQyO5YPUb/58BfTb++inaW/Asn lWNw== MIME-Version: 1.0 Received: by 10.68.232.2 with SMTP id tk2mr1060708pbc.68.1331686954250; Tue, 13 Mar 2012 18:02:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.33.5 with HTTP; Tue, 13 Mar 2012 18:02:34 -0700 (PDT) In-Reply-To: <4F5FCCD7.7070609@entel.upc.edu> References: <4F5C81BA.1050001@entel.upc.edu> <86ehswtmek.wl%gnn@neville-neil.com> <4F5FCCD7.7070609@entel.upc.edu> Date: Tue, 13 Mar 2012 18:02:34 -0700 X-Google-Sender-Auth: 7CkHKcmfXcbUefK7ksOFZ8qUlHY Message-ID: From: Adrian Chadd To: =?ISO-8859-1?Q?Gustau_P=E9rez?= Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD current , fs@freebsd.org Subject: Re: RFC: FUSE kernel module for the kernel... 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, 14 Mar 2012 01:02:35 -0000 Hm, try: make KERNBUILDDIR=/usr/src/sys/i386/compile/KERNNAME clean all install Adrian From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 04:52:55 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59CA01065673 for ; Wed, 14 Mar 2012 04:52:55 +0000 (UTC) (envelope-from peter@pean.org) Received: from system.jails.se (system.jails.se [IPv6:2001:16d8:cc1e:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 023208FC20 for ; Wed, 14 Mar 2012 04:52:54 +0000 (UTC) Received: from localhost (system.jails.se [91.205.63.85]) by system.jails.se (Postfix) with SMTP id D23F3223499 for ; Wed, 14 Mar 2012 05:52:52 +0100 (CET) Received: from [172.25.0.21] (c-1105e155.166-7-64736c14.cust.bredbandsbolaget.se [85.225.5.17]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by system.jails.se (Postfix) with ESMTPSA id C1A4C223493; Wed, 14 Mar 2012 05:52:50 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: =?iso-8859-1?Q?Peter_Ankerst=E5l?= In-Reply-To: Date: Wed, 14 Mar 2012 05:52:58 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <545ACC9D-EB12-4F8F-B8A9-5706AE57296E@pean.org> References: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> To: Freddie Cash X-Mailer: Apple Mail (2.1251.1) X-DSPAM-Result: Innocent X-DSPAM-Processed: Wed Mar 14 05:52:52 2012 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 4f60242426819188212429 X-DSPAM-Factors: 27, Date*05+52, 0.40000, could, 0.40000, That, 0.40000, Subject*raidz., 0.40000, Received*cipher+AES128, 0.40000, Message-Id*B8A9+5706AE57296E, 0.40000, any+snapshots, 0.40000, Mime-Version*Message, 0.40000, happened+in, 0.40000, shouldn't+be, 0.40000, Remove, 0.40000, Received*[172.25.0.21], 0.40000, gone), 0.40000, pool+That, 0.40000, the+tricks, 0.40000, of, 0.40000, error+message, 0.40000, In-Reply-To*mail.gmail.com>, 0.40000, But, 0.40000, tricks, 0.40000, Received*2012, 0.40000, is+removed, 0.40000, filesystem+(although, 0.40000, how+this, 0.40000, Received*client+certificate, 0.40000, >+shouldn't, 0.40000, message, 0.40000 Cc: fs@freebsd.org Subject: Re: Problem with corrupted file on raidz. 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, 14 Mar 2012 04:52:55 -0000 Ok, yes. Removing the file and THEN scrub did the tricks here. But I'm = still confused how this could have happened in the first place.=20 Kind of worrying. On Mar 13, 2012, at 11:54 PM, Freddie Cash wrote: > Remove any snapshots pointing to the filesystem (although there > shouldn't be any if the entire filesystem is gone). Then scrub the > pool. That should remove the error message, as that znode/block > pointer/whatever is removed. >=20 From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 05:02:40 2012 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 4FE3110656A3 for ; Wed, 14 Mar 2012 05:02:40 +0000 (UTC) (envelope-from markm-lists@intellasoft.net) Received: from mail.mystoragebox.com (mail.mystoragebox.com [64.27.7.19]) by mx1.freebsd.org (Postfix) with ESMTP id 357828FC08 for ; Wed, 14 Mar 2012 05:02:39 +0000 (UTC) Received: from cpe-67-240-79-210.nycap.res.rr.com ([67.240.79.210] helo=[192.168.35.110]) by mail.mystoragebox.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1S7g2B-0001AP-IS for freebsd-fs@freebsd.org; Wed, 14 Mar 2012 00:41:59 -0400 Message-ID: <4F60266D.1090302@intellasoft.net> Date: Wed, 14 Mar 2012 01:02:37 -0400 From: Mark Murawski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> In-Reply-To: <4F5F97A4.6070000@brockmann-consult.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS file corruption problem 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, 14 Mar 2012 05:02:40 -0000 On 03/13/12 14:53, Peter Maloney wrote: > Am 13.03.2012 17:08, schrieb Mark Murawski: >> So I have this zpool with corrupted files running on freebsd 9-release >> amd64. The corrupted files can go away, that's not a big deal >> >> Here's the problem. >> >> $ ls -al /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 >> > Since this is one of the corrupt files, I guess ZFS would like to block > until it can return a good copy (such as if you put the mirror disk back > in)... so to fix this, you need to remove the file or restore from > backup (or add that mirror disk back in, which I will assume you can't): > > rm /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 > (in the case of a file that should exist empty instead of being removed, > eg. a log where the log writer does not have write permission to the > directory, do touch also) > > or maybe this works: > > mv /somewhere_with_backup/IMG_5576.CR2 > /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 > > > And if there are more errors, you probably need to scrub to expand the > pool or for "zpool clear" to work. > Oh wow. For some reason I never thought of rm. That works on getting rid of the file. Why would the whole pool now become available upon access to a bad file? From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 05:08:05 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B2552106566C for ; Wed, 14 Mar 2012 05:08:05 +0000 (UTC) (envelope-from markm-lists@intellasoft.net) Received: from mail.mystoragebox.com (mail.mystoragebox.com [64.27.7.19]) by mx1.freebsd.org (Postfix) with ESMTP id 979EA8FC0A for ; Wed, 14 Mar 2012 05:08:05 +0000 (UTC) Received: from cpe-67-240-79-210.nycap.res.rr.com ([67.240.79.210] helo=[192.168.35.110]) by mail.mystoragebox.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1S7g7R-0001EC-1l for freebsd-fs@freebsd.org; Wed, 14 Mar 2012 00:47:25 -0400 Message-ID: <4F6027B3.5080006@intellasoft.net> Date: Wed, 14 Mar 2012 01:08:03 -0400 From: Mark Murawski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net> In-Reply-To: <4F60266D.1090302@intellasoft.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS file corruption problem 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, 14 Mar 2012 05:08:05 -0000 On 03/14/12 01:02, Mark Murawski wrote: > On 03/13/12 14:53, Peter Maloney wrote: >> Am 13.03.2012 17:08, schrieb Mark Murawski: >>> So I have this zpool with corrupted files running on freebsd 9-release >>> amd64. The corrupted files can go away, that's not a big deal >>> >>> Here's the problem. >>> >>> $ ls -al /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 >>> >> Since this is one of the corrupt files, I guess ZFS would like to block >> until it can return a good copy (such as if you put the mirror disk back >> in)... so to fix this, you need to remove the file or restore from >> backup (or add that mirror disk back in, which I will assume you can't): >> >> rm /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 >> (in the case of a file that should exist empty instead of being removed, >> eg. a log where the log writer does not have write permission to the >> directory, do touch also) >> >> or maybe this works: >> >> mv /somewhere_with_backup/IMG_5576.CR2 >> /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 >> >> >> And if there are more errors, you probably need to scrub to expand the >> pool or for "zpool clear" to work. >> > > Oh wow. For some reason I never thought of rm. That works on getting rid > of the file. > > Why would the whole pool now become available upon access to a bad file? Also... isn't this pretty terrible behavior that the process accessing the bad file is unkillable? From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 09:50:32 2012 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 9D8751065672 for ; Wed, 14 Mar 2012 09:50:32 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 2D3C08FC08 for ; Wed, 14 Mar 2012 09:50:31 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC423CA.dip.t-dialin.net [79.196.35.202]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id B1BA68446F8; Wed, 14 Mar 2012 10:50:17 +0100 (CET) Received: from webmail.leidinger.net (webmail.Leidinger.net [IPv6:fd73:10c7:2053:1::3:102]) by outgoing.leidinger.net (Postfix) with ESMTPS id 0230C2399; Wed, 14 Mar 2012 10:50:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1331718615; bh=aOCZ8V2P6t6P16xduDNdXM+4OUqEQevEiBHYO4vf8Eg=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=yCClkPFv1X0zlNbsN0o/ukU257/QCbdRhHm5YmLJ3Eq5icaW8VOyUGGFocAWvVFmn ig8V6EGZE7B3D+bzkH397glg/wUoxaSke1S8QxiepCm0W1yDW2Nj5JJoeD1Tk/k3pT 4rNE2R/CuTmc64kDYT8J1WKWRoq6d7RwAOz9iFl39OdwK6xc0CX8x6bpn4inwiImWI BYJc43OJUPEyENBvfLSl/vROXh9iyMr1F4EkzBpd5UyJe+k6TuPhaUrxvNhutiLuNg +vY0/raDEETxLwRAd/wf4QSBR977jCBRKcNJSIo6GpIv8btoOP3nRSyrvC/Wu8l7b5 kdU+dst2XK+yA== Received: (from www@localhost) by webmail.leidinger.net (8.14.5/8.14.4/Submit) id q2E9oEs6017378; Wed, 14 Mar 2012 10:50:14 +0100 (CET) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: webmail.leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from 85.94.224.20 ([85.94.224.20]) by webmail.leidinger.net (Horde Framework) with HTTP; Wed, 14 Mar 2012 10:50:14 +0100 Date: Wed, 14 Mar 2012 10:50:11 +0100 Message-ID: <20120314105011.Horde.mYG5YpjmRSRPYGnT6OFEHuA@webmail.leidinger.net> From: Alexander Leidinger To: Mark Murawski References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net> <4F6027B3.5080006@intellasoft.net> In-Reply-To: <4F6027B3.5080006@intellasoft.net> User-Agent: Internet Messaging Program (IMP) H4 (5.0.19) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: B1BA68446F8.A1FC2 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=0.385, required 6, autolearn=disabled, AWL -1.72, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, J_CHICKENPOX_84 0.60, RCVD_IN_SORBS 1.00, RCVD_IN_SORBS_WEB 0.61, T_RP_MATCHES_RCVD -0.01) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1332323419.65587@Ej7PyRuKocxzBE1yoQI8nw X-EBL-Spam-Status: No Cc: freebsd-fs@freebsd.org Subject: Re: ZFS file corruption problem 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, 14 Mar 2012 09:50:32 -0000 Quoting Mark Murawski (from Wed, 14 Mar 2012 01:08:03 -0400): > On 03/14/12 01:02, Mark Murawski wrote: >> Why would the whole pool now become available upon access to a bad file? Because you configured it like this (respectively didn't configure a different behavior). > Also... isn't this pretty terrible behavior that the process > accessing the bad file is unkillable? If you are in an environment where the disks are not local (ZFS is designed with corporate environments in mind), you do not want to fail on an application level or panic because of a small hickup in the network. man zpool: ---snip--- failmode=wait | continue | panic Controls the system behavior in the event of catastrophic pool fail? ure. This condition is typically a result of a loss of connectivity to the underlying storage device(s) or a failure of all devices within the pool. The behavior of such an event is determined as fol? lows: wait Blocks all I/O access until the device connectivity is recov? ered and the errors are cleared. This is the default behav? ior. continue Returns EIO to any new write I/O requests but allows reads to any of the remaining healthy devices. Any write requests that have yet to be committed to disk would be blocked. panic Prints out a message to the console and generates a system crash dump. ---snip--- It is up to you to switch to 'continue' or 'panic' for local disks. Bye, Alexander. -- In Seattle, Washington, it is illegal to carry a concealed weapon that is over six feet in length. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 12:30:05 2012 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 23A3E106566B for ; Wed, 14 Mar 2012 12:30: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 0E7918FC08 for ; Wed, 14 Mar 2012 12:30:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2ECU4gD046344 for ; Wed, 14 Mar 2012 12:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2ECU4J0046341; Wed, 14 Mar 2012 12:30:04 GMT (envelope-from gnats) Date: Wed, 14 Mar 2012 12:30:04 GMT Message-Id: <201203141230.q2ECU4J0046341@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andrey Simonenko Cc: Subject: Re: kern/136865: [nfs] [patch] NFS exports atomic and on-the-fly atomic updates X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrey Simonenko List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 12:30:05 -0000 The following reply was made to PR kern/136865; it has been noted by GNATS. From: Andrey Simonenko To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/136865: [nfs] [patch] NFS exports atomic and on-the-fly atomic updates Date: Wed, 14 Mar 2012 14:23:56 +0200 List of important changes from nfse-20100507 to nfse-20120310. Improved integration with /etc/rc.d, improved compatibility mode with mountd(8) ("nfse -C ..."), changes for the 10-CURRENT kernel. Now specifications (credentials and security flavors) for export entities (host or network) are given by array of user specified size. This change to NFSE API allows to change number and types of specifications without changing kernel ABI. Added new NFSE_CMD_SPECS command to NFSE API that allows to load specifications (credentials and security flavors) separately from export settings. Several options were converted to boolean datatype and now can be set independently for each address specification, they are -nfsv2, -nfsv3, -nfsv4, -mnt_dump and -mnt_export (boolean values "yes" and "no"). Added two new commands "set" and "unset" to nfse(8), these commands are relaxed versions of "add/update" and "delete" commands. Added new option -mnt_export_brief to nfs.exports(5). Added nfse(8) support to zfs(8), if /etc/nfs.exports exists, then "zfs sharenfs ..." and "zfs unshare ..." use nfse(8) commands. URL: http://nfse.sourceforge.net/ From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 12:34:34 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 258AC1065680 for ; Wed, 14 Mar 2012 12:34:34 +0000 (UTC) (envelope-from markm-lists@intellasoft.net) Received: from mail.mystoragebox.com (mail.mystoragebox.com [64.27.7.19]) by mx1.freebsd.org (Postfix) with ESMTP id 096328FC1A for ; Wed, 14 Mar 2012 12:34:33 +0000 (UTC) Received: from cpe-67-240-79-210.nycap.res.rr.com ([67.240.79.210] helo=[192.168.35.9]) by mail.mystoragebox.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1S7n5R-00078n-MC for freebsd-fs@freebsd.org; Wed, 14 Mar 2012 08:13:50 -0400 Message-ID: <4F609052.5010300@intellasoft.net> Date: Wed, 14 Mar 2012 08:34:26 -0400 From: Mark Murawski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net> <4F6027B3.5080006@intellasoft.net> <20120314105011.Horde.mYG5YpjmRSRPYGnT6OFEHuA@webmail.leidinger.net> In-Reply-To: <20120314105011.Horde.mYG5YpjmRSRPYGnT6OFEHuA@webmail.leidinger.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS file corruption problem 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, 14 Mar 2012 12:34:34 -0000 On 03/14/2012 05:50 AM, Alexander Leidinger wrote: > Quoting Mark Murawski (from Wed, 14 Mar > 2012 01:08:03 -0400): > >> On 03/14/12 01:02, Mark Murawski wrote: > >>> Why would the whole pool now become available upon access to a bad file? > > Because you configured it like this (respectively didn't configure a > different behavior). > >> Also... isn't this pretty terrible behavior that the process accessing >> the bad file is unkillable? > > If you are in an environment where the disks are not local (ZFS is > designed with corporate environments in mind), you do not want to fail > on an application level or panic because of a small hickup in the network. > > man zpool: > ---snip--- > failmode=wait | continue | panic > Controls the system behavior in the event of catastrophic pool fail? > ure. This condition is typically a result of a loss of connectivity > to the underlying storage device(s) or a failure of all devices > within the pool. The behavior of such an event is determined as fol? > lows: > > wait Blocks all I/O access until the device connectivity is recov? > ered and the errors are cleared. This is the default behav? > ior. > > continue > Returns EIO to any new write I/O requests but allows reads to > any of the remaining healthy devices. Any write requests that > have yet to be committed to disk would be blocked. > > panic Prints out a message to the console and generates a system > crash dump. > ---snip--- > > It is up to you to switch to 'continue' or 'panic' for local disks. > > Bye, > Alexander. > Oh... wow. It's not that I've configured if that way in particular, it's more of a matter of the default settings came like that. But anyway, thanks a ton. I had no idea that was configurable. I was even thinking that "you know, it would be nice if that behavior was configurable". Once I started running into these problems I started losing faith in zfs and its design. I've been dealing with this corrupt files problem for about a week now. Finding out the fix was as simple as deleting the file and setting a new config option has reaffirmed my belief in zfs. From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 14:03:27 2012 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 297CB106564A for ; Wed, 14 Mar 2012 14:03:27 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id E16AA8FC1E for ; Wed, 14 Mar 2012 14:03:26 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q2EE3JYj013694; Wed, 14 Mar 2012 09:03:20 -0500 (CDT) Date: Wed, 14 Mar 2012 09:03:19 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Mark Murawski In-Reply-To: <4F60266D.1090302@intellasoft.net> Message-ID: References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Wed, 14 Mar 2012 09:03:20 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS file corruption problem 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, 14 Mar 2012 14:03:27 -0000 On Wed, 14 Mar 2012, Mark Murawski wrote: > > Why would the whole pool now become available upon access to a bad file? A disk drive (or HBA) may be hanging (e.g. endless retries) when the bad file is accessed. This is a common problem with consumer disks or HBAs which believe they are the top level authority when it comes to data integrity. Zfs itself does not include any timers to decide to stop waiting. Zfs depends on the lower-level OS & drivers to decide to stop waiting on a stalled device. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Wed Mar 14 17:37:05 2012 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 01D871065672 for ; Wed, 14 Mar 2012 17:37:05 +0000 (UTC) (envelope-from markm-lists@intellasoft.net) Received: from mail.mystoragebox.com (mail.mystoragebox.com [64.27.7.19]) by mx1.freebsd.org (Postfix) with ESMTP id D842E8FC15 for ; Wed, 14 Mar 2012 17:37:04 +0000 (UTC) Received: from cpe-67-240-79-210.nycap.res.rr.com ([67.240.79.210] helo=[192.168.35.110]) by mail.mystoragebox.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1S7roE-0002vk-E6 for freebsd-fs@freebsd.org; Wed, 14 Mar 2012 13:16:22 -0400 Message-ID: <4F60D73F.2010201@intellasoft.net> Date: Wed, 14 Mar 2012 13:37:03 -0400 From: Mark Murawski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS file corruption problem 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, 14 Mar 2012 17:37:05 -0000 On 03/14/12 10:03, Bob Friesenhahn wrote: > On Wed, 14 Mar 2012, Mark Murawski wrote: >> >> Why would the whole pool now become available upon access to a bad file? > > A disk drive (or HBA) may be hanging (e.g. endless retries) when the bad > file is accessed. This is a common problem with consumer disks or HBAs > which believe they are the top level authority when it comes to data > integrity. Zfs itself does not include any timers to decide to stop > waiting. Zfs depends on the lower-level OS & drivers to decide to stop > waiting on a stalled device. > > Bob Ah okay. And you assumed correctly that I had meant "become unavailable upon access". This is probably related to the bug I'm experiencing on my Promise SATA 300 TX4 controller (http://lists.freebsd.org/pipermail/freebsd-bugs/2012-March/047998.html) From owner-freebsd-fs@FreeBSD.ORG Thu Mar 15 09:51:39 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E20B1065674 for ; Thu, 15 Mar 2012 09:51:39 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 56E708FC14 for ; Thu, 15 Mar 2012 09:51:38 +0000 (UTC) Received: by vcmm1 with SMTP id m1so4024051vcm.13 for ; Thu, 15 Mar 2012 02:51:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=DdgX6kbFCrdmBatY9kkkT3TCfspWl9kJ7U4kYrH7+lA=; b=t58R1395qDg1XKhXTClXJtaH8oHYXBb/pi0ArbJ/7OZtw1+t9CyaI85h6K26Jbrm9u O2nmi/lb4DFAkaImXfMlFj+17AtwpcquqvS4gDB5SS9Y0Jp4lrcoimuQb7WwI1s+Mjir HnK8JYZv61W+7nlMaLhtYv+Nc5Z/YVx31vcu3asDgUflfsIHWlckVygpi1pDBp2UV7pA yUGgNpRbKTRoJCZOvX8kOs0lQtJFQmKYdYEcPDzp9jgatT808x1i4PTsA73ifkdJRPeW FITnmaevBc5KAwUnjeenKdBwIx4iLUTYu4R7bul4Gyxixtt9J7rKCMSllHQKllvAlkL7 VQZw== MIME-Version: 1.0 Received: by 10.52.72.74 with SMTP id b10mr4348060vdv.85.1331805098374; Thu, 15 Mar 2012 02:51:38 -0700 (PDT) Received: by 10.220.38.67 with HTTP; Thu, 15 Mar 2012 02:51:38 -0700 (PDT) In-Reply-To: <4F60D73F.2010201@intellasoft.net> References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net> <4F60D73F.2010201@intellasoft.net> Date: Thu, 15 Mar 2012 11:51:38 +0200 Message-ID: From: George Kontostanos To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: ZFS file corruption problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 09:51:39 -0000 On Wed, Mar 14, 2012 at 7:37 PM, Mark Murawski wrote: > On 03/14/12 10:03, Bob Friesenhahn wrote: >> >> On Wed, 14 Mar 2012, Mark Murawski wrote: >>> >>> >>> Why would the whole pool now become available upon access to a bad file= ? >> >> >> A disk drive (or HBA) may be hanging (e.g. endless retries) when the bad >> file is accessed. This is a common problem with consumer disks or HBAs >> which believe they are the top level authority when it comes to data >> integrity. Zfs itself does not include any timers to decide to stop >> waiting. Zfs depends on the lower-level OS & drivers to decide to stop >> waiting on a stalled device. >> >> Bob > > > > Ah okay. =A0And you assumed correctly that I had meant "become unavailabl= e > upon access". > > This is probably related to the bug I'm experiencing on my Promise SATA 3= 00 > TX4 controller > (http://lists.freebsd.org/pipermail/freebsd-bugs/2012-March/047998.html) > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" Yes, as a matter of fact: http://www.aisecure.net/2011/07/07/promise-pdc40718-sata300-junk/ --=20 George Kontostanos Aicom telecoms ltd http://www.aisecure.net From owner-freebsd-fs@FreeBSD.ORG Thu Mar 15 21:25:38 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 11B32106566B for ; Thu, 15 Mar 2012 21:25:38 +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 DE12F8FC15 for ; Thu, 15 Mar 2012 21:25:37 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 9448846B2A; Thu, 15 Mar 2012 17:25:37 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F188EB942; Thu, 15 Mar 2012 17:25:36 -0400 (EDT) From: John Baldwin To: freebsd-fs@freebsd.org Date: Thu, 15 Mar 2012 13:33:22 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <4F5F902A.2030108@luckie.org.nz> In-Reply-To: <4F5F902A.2030108@luckie.org.nz> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203151333.22242.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 15 Mar 2012 17:25:37 -0400 (EDT) Cc: Matthew Luckie Subject: Re: freebsd 9.0R panic in vfs_cache.c:364 cache_zap() X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 21:25:38 -0000 On Tuesday, March 13, 2012 2:21:30 pm Matthew Luckie wrote: > Hi > > This is likely to be a useless report because I don't have a crash dump. > > I upgraded to freebsd 9.0R on Friday night and last night (Monday) it > panicked during a nightly rsync. First time I've had a panic during a > nightly rsync on this machine, which has been running for about two > years. I searched lists to see if there was a known problem but didn't > come across anything, and I'm not sure what to search for. There seem > to have been a few commits on RELENG_9 to vfs_cache.c since release, is > it worthwhile upgrading to a 9-stable? Hmm, I have seen a similar panic (albeit in this case the vdropl() from cache_zap() panic'd due to the refcount underflowing) on two different boxes running 8, so I don't think this is specific to 9. -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Fri Mar 16 17:06:08 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5436D106564A for ; Fri, 16 Mar 2012 17:06:08 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from mo-p05-ob6.rzone.de (mo-p05-ob6.rzone.de [IPv6:2a01:238:20a:202:53f5::1]) by mx1.freebsd.org (Postfix) with ESMTP id AC6F48FC15 for ; Fri, 16 Mar 2012 17:06:07 +0000 (UTC) X-RZG-AUTH: :LWIKdA2leu0bPbLmhzXgqn0MTG6qiKEwQRWfNxSw4HzYIwjsnvdDt2oX8drk23mo2zRGKX0o X-RZG-CLASS-ID: mo05 Received: from [192.168.179.39] (hmbg-5f764970.pool.mediaWays.net [95.118.73.112]) by smtp.strato.de (fruni mo10) (RZmta 28.1 DYNA|AUTH) with (DHE-RSA-AES128-SHA encrypted) ESMTPA id 904941o2GFWB26 for ; Fri, 16 Mar 2012 18:06:05 +0100 (MET) Message-ID: <4F6372FC.5060507@brockmann-consult.de> Date: Fri, 16 Mar 2012 18:06:04 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> <545ACC9D-EB12-4F8F-B8A9-5706AE57296E@pean.org> In-Reply-To: <545ACC9D-EB12-4F8F-B8A9-5706AE57296E@pean.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Problem with corrupted file on raidz. 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, 16 Mar 2012 17:06:08 -0000 Am 14.03.2012 05:52, schrieb Peter Ankerstål: > Ok, yes. Removing the file and THEN scrub did the tricks here. But I'm still confused how this could have happened in the first place. Confused about what part? ZFS handling it, or what caused your file to get damaged despite redundancy? Did you have checksum/other errors on other devices? If multiple had damage just by chance in the same spot, it would damage a file... but did this unlikely occurance actually occur? eg. NAME STATE READ WRITE CKSUM store ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 5 ada2 ONLINE 0 0 7 Perhaps one device was offline/unavail while the file was created and damaged so the offline disk had no redundancy? eg. NAME STATE READ WRITE CKSUM store DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 5 ada2 OFFLINE 0 0 0 > Kind of worrying. > > On Mar 13, 2012, at 11:54 PM, Freddie Cash wrote: > >> Remove any snapshots pointing to the filesystem (although there >> shouldn't be any if the entire filesystem is gone). Then scrub the >> pool. That should remove the error message, as that znode/block >> pointer/whatever is removed. >> > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Fri Mar 16 18:06:34 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 637C8106566C; Fri, 16 Mar 2012 18:06:33 +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 8093E8FC08; Fri, 16 Mar 2012 18:06:33 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 1E7F846B0A; Fri, 16 Mar 2012 14:06:33 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 997B3B93E; Fri, 16 Mar 2012 14:06:32 -0400 (EDT) From: John Baldwin To: freebsd-fs@freebsd.org Date: Fri, 16 Mar 2012 14:06:27 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201203071318.08241.jhb@freebsd.org> <20120308223919.GU75778@deviant.kiev.zoral.com.ua> <201203091059.29342.jhb@freebsd.org> In-Reply-To: <201203091059.29342.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201203161406.27549.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 16 Mar 2012 14:06:32 -0400 (EDT) Cc: pho@freebsd.org, fs@freebsd.org Subject: Re: close() of an flock'd file is not atomic 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, 16 Mar 2012 18:06:34 -0000 On Friday, March 09, 2012 10:59:29 am John Baldwin wrote: > On Thursday, March 08, 2012 5:39:19 pm Konstantin Belousov wrote: > > On Thu, Mar 08, 2012 at 03:39:07PM -0500, John Baldwin wrote: > > > On Wednesday, March 07, 2012 1:18:07 pm John Baldwin wrote: > > > > So I ran into this problem at work. Suppose you have a process that opens a > > > > read-write file descriptor with O_EXLOCK (so it has an flock()). It then > > > > writes out a binary into that file. Another process wants to execve() the > > > > file when it is ready, so it opens the file with O_EXLOCK (or O_SHLOCK), and > > > > will call execve() once it has locked the file. In theory, what should happen > > > > is that the second process should wait until the first process has finished > > > > and called close(). In practice what happens is that I occasionally see the > > > > second process fail with ETXTBUSY. > > > > > > > > The bug is that the vn_closefile() does the VOP_ADVLOCK() to unlock the file > > > > separately from the call to vn_close() which drops the writecount. Thus, the > > > > second process can do an open() and flock() of the file and subsequently call > > > > execve() after the first process has done the VOP_ADVLOCK(), but before it > > > > calls into vn_close(). In fact, since vn_close() requires a write lock on the > > > > vnode, this turns out to not be too hard to reproduce at all. Below is a > > > > simple test program that reproduces this constantly. To use, copy /bin/test > > > > to some other file (e.g. /tmp/foo) and make it writable (chmod a+w), then run > > > > ./flock_close_race /tmp/foo. > > > > > > > > The "fix" I came up with is to defer calling VOP_ADVLOCK() to release the lock > > > > until after vn_close() executes. However, even with that fix applied, my test > > > > case still fails. Now it is because open() with a given lock flag is > > > > non-atomic in that the open(O_RDWR) will call vn_open() and bump v_writecount > > > > before it blocks on the lock due to O_EXLOCK, so even though the 'exec_child' > > > > process has the fd locked, the writecount can still be bumped. One gross hack > > > > would be to defer the bump of the writecount to the caller of vn_open() if the > > > > caller passes in O_EXLOCK or O_SHLOCK, but that's a really gross kludge, plus > > > > it doesn't actually work. I ended up moving acquiring the lock into > > > > vn_open_cred(). The current patch I'm testing has both of these approaches, > > > > but the first one is #if 0'd out, and the second is #if 1'd. > > > > > > > > http://www.freebsd.org/~jhb/patches/flock_open_close.patch > > > > > > Based on some feedback from Konstantin, I've fixed some issues in the failure > > > path handling for VOP_ADVLOCK(). I've also removed the #if 0'd code mentioned > > > above, so the patch is now the actual change that I'm testing. So far it > > > handles both my workload at work and my test program without any issues. > > > > I think a comment is needed for a reason to call vn_writechk() second time. > > Fixed. > > > Could you, please, point me, where the FHASLOCK is set for O_EXLOCK | O_SHLOCK > > case in the patched kernel ? > > It wasn't. :( I wonder how this was even working since close shouldn't have > been unlocking. I'll need to do some more testing. BTW, I ran into fhopen() > and found that I would need to put all this same logic into that, so I've split > the common code from fhopen() and vn_open_cred() into a new vn_open_vnode(). > I think in general it improves both sets of code. > > I'll upate the patch once I've done some more testing. So the current patch I'm testing is at http://www.FreeBSD.org/~jhb/patches/flock_open_close2.patch This includes the aforementioned vn_open_vnode(). There are a few #if 0 debugging nits that would be removed before committing. The one in fhopen() is an open question if it should be non-restartable the way open() is. I've also had to update my test case to work around a race between it's two "threads" where the read/write open could complete before the other child had finished exit() resulting in a correct ETXTBSY error. The first process just ignores ETXTBSY for errors to workaround. It is included below. #include #include #include #include #include #include #include #include #include #include static void usage(void) { fprintf(stderr, "Usage: flock_close_race [args]\n"); exit(1); } static void child(const char *binary) { int fd; /* Exit as soon as our parent exits. */ while (getppid() != 1) { fd = open(binary, O_RDWR | O_EXLOCK); if (fd < 0) { /* * This may get ETXTBSY since exit() will * close its open fd's (thus releasing the * lock), before it releases the vmspace (and * mapping of the binary). */ if (errno == ETXTBSY) continue; err(1, "can't open %s", binary); } close(fd); } exit(0); } static void exec_child(char **av) { int fd, value, save; fd = open(av[0], O_RDONLY | O_SHLOCK); execv(av[0], av); save = errno; value = 0; sysctlbyname("debug.ktr.mask", NULL, NULL, &value, sizeof(value)); errno = save; err(127, "execv"); } int main(int ac, char **av) { struct stat sb; pid_t pid; if (ac < 2) usage(); if (stat(av[1], &sb) != 0) err(1, "stat(%s)", av[1]); if (!S_ISREG(sb.st_mode)) errx(1, "%s not an executable", av[1]); pid = fork(); if (pid < 0) err(1, "fork"); if (pid == 0) child(av[1]); for (;;) { pid = fork(); if (pid < 0) err(1, "vfork"); if (pid == 0) exec_child(av + 1); wait(NULL); } return (0); } -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Fri Mar 16 18:06:34 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 637C8106566C; Fri, 16 Mar 2012 18:06:33 +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 8093E8FC08; Fri, 16 Mar 2012 18:06:33 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 1E7F846B0A; Fri, 16 Mar 2012 14:06:33 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 997B3B93E; Fri, 16 Mar 2012 14:06:32 -0400 (EDT) From: John Baldwin To: freebsd-fs@freebsd.org Date: Fri, 16 Mar 2012 14:06:27 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201203071318.08241.jhb@freebsd.org> <20120308223919.GU75778@deviant.kiev.zoral.com.ua> <201203091059.29342.jhb@freebsd.org> In-Reply-To: <201203091059.29342.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201203161406.27549.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 16 Mar 2012 14:06:32 -0400 (EDT) Cc: pho@freebsd.org, fs@freebsd.org Subject: Re: close() of an flock'd file is not atomic 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, 16 Mar 2012 18:06:34 -0000 On Friday, March 09, 2012 10:59:29 am John Baldwin wrote: > On Thursday, March 08, 2012 5:39:19 pm Konstantin Belousov wrote: > > On Thu, Mar 08, 2012 at 03:39:07PM -0500, John Baldwin wrote: > > > On Wednesday, March 07, 2012 1:18:07 pm John Baldwin wrote: > > > > So I ran into this problem at work. Suppose you have a process that opens a > > > > read-write file descriptor with O_EXLOCK (so it has an flock()). It then > > > > writes out a binary into that file. Another process wants to execve() the > > > > file when it is ready, so it opens the file with O_EXLOCK (or O_SHLOCK), and > > > > will call execve() once it has locked the file. In theory, what should happen > > > > is that the second process should wait until the first process has finished > > > > and called close(). In practice what happens is that I occasionally see the > > > > second process fail with ETXTBUSY. > > > > > > > > The bug is that the vn_closefile() does the VOP_ADVLOCK() to unlock the file > > > > separately from the call to vn_close() which drops the writecount. Thus, the > > > > second process can do an open() and flock() of the file and subsequently call > > > > execve() after the first process has done the VOP_ADVLOCK(), but before it > > > > calls into vn_close(). In fact, since vn_close() requires a write lock on the > > > > vnode, this turns out to not be too hard to reproduce at all. Below is a > > > > simple test program that reproduces this constantly. To use, copy /bin/test > > > > to some other file (e.g. /tmp/foo) and make it writable (chmod a+w), then run > > > > ./flock_close_race /tmp/foo. > > > > > > > > The "fix" I came up with is to defer calling VOP_ADVLOCK() to release the lock > > > > until after vn_close() executes. However, even with that fix applied, my test > > > > case still fails. Now it is because open() with a given lock flag is > > > > non-atomic in that the open(O_RDWR) will call vn_open() and bump v_writecount > > > > before it blocks on the lock due to O_EXLOCK, so even though the 'exec_child' > > > > process has the fd locked, the writecount can still be bumped. One gross hack > > > > would be to defer the bump of the writecount to the caller of vn_open() if the > > > > caller passes in O_EXLOCK or O_SHLOCK, but that's a really gross kludge, plus > > > > it doesn't actually work. I ended up moving acquiring the lock into > > > > vn_open_cred(). The current patch I'm testing has both of these approaches, > > > > but the first one is #if 0'd out, and the second is #if 1'd. > > > > > > > > http://www.freebsd.org/~jhb/patches/flock_open_close.patch > > > > > > Based on some feedback from Konstantin, I've fixed some issues in the failure > > > path handling for VOP_ADVLOCK(). I've also removed the #if 0'd code mentioned > > > above, so the patch is now the actual change that I'm testing. So far it > > > handles both my workload at work and my test program without any issues. > > > > I think a comment is needed for a reason to call vn_writechk() second time. > > Fixed. > > > Could you, please, point me, where the FHASLOCK is set for O_EXLOCK | O_SHLOCK > > case in the patched kernel ? > > It wasn't. :( I wonder how this was even working since close shouldn't have > been unlocking. I'll need to do some more testing. BTW, I ran into fhopen() > and found that I would need to put all this same logic into that, so I've split > the common code from fhopen() and vn_open_cred() into a new vn_open_vnode(). > I think in general it improves both sets of code. > > I'll upate the patch once I've done some more testing. So the current patch I'm testing is at http://www.FreeBSD.org/~jhb/patches/flock_open_close2.patch This includes the aforementioned vn_open_vnode(). There are a few #if 0 debugging nits that would be removed before committing. The one in fhopen() is an open question if it should be non-restartable the way open() is. I've also had to update my test case to work around a race between it's two "threads" where the read/write open could complete before the other child had finished exit() resulting in a correct ETXTBSY error. The first process just ignores ETXTBSY for errors to workaround. It is included below. #include #include #include #include #include #include #include #include #include #include static void usage(void) { fprintf(stderr, "Usage: flock_close_race [args]\n"); exit(1); } static void child(const char *binary) { int fd; /* Exit as soon as our parent exits. */ while (getppid() != 1) { fd = open(binary, O_RDWR | O_EXLOCK); if (fd < 0) { /* * This may get ETXTBSY since exit() will * close its open fd's (thus releasing the * lock), before it releases the vmspace (and * mapping of the binary). */ if (errno == ETXTBSY) continue; err(1, "can't open %s", binary); } close(fd); } exit(0); } static void exec_child(char **av) { int fd, value, save; fd = open(av[0], O_RDONLY | O_SHLOCK); execv(av[0], av); save = errno; value = 0; sysctlbyname("debug.ktr.mask", NULL, NULL, &value, sizeof(value)); errno = save; err(127, "execv"); } int main(int ac, char **av) { struct stat sb; pid_t pid; if (ac < 2) usage(); if (stat(av[1], &sb) != 0) err(1, "stat(%s)", av[1]); if (!S_ISREG(sb.st_mode)) errx(1, "%s not an executable", av[1]); pid = fork(); if (pid < 0) err(1, "fork"); if (pid == 0) child(av[1]); for (;;) { pid = fork(); if (pid < 0) err(1, "vfork"); if (pid == 0) exec_child(av + 1); wait(NULL); } return (0); } -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Fri Mar 16 20:01:58 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C81C106564A for ; Fri, 16 Mar 2012 20:01:58 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 25A948FC20 for ; Fri, 16 Mar 2012 20:01:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=Message-Id:From:Mime-Version:Date:Subject:To:Content-Type; bh=zUjNvBX0ZuEkNTe0cL+fpJBGZRzLWXakFh1XWDfRvaU=; b=gj22EQm7chEDX/zPQMevXzFOD6+naXzx10rcnCrAyjwhbYfgBrozt9oTcIWw4OauOinKNttF3soPEQ7ujSZGnrTnbHMiHcAEcSxNWh/9uYpRDLEp4SRFl4S0FI6U1PzR; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1S8dLY-0006Zn-Fl for freebsd-fs@freebsd.org; Fri, 16 Mar 2012 15:01:57 -0500 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1331928109-34990-34989/5/31; Fri, 16 Mar 2012 20:01:49 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-fs@freebsd.org Date: Fri, 16 Mar 2012 15:01:49 -0500 Mime-Version: 1.0 From: Mark Felder Message-Id: User-Agent: Opera Mail/11.62 (FreeBSD) X-SA-Score: -1.0 Subject: zfs send progress? 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, 16 Mar 2012 20:01:58 -0000 According to this link, zfs send progress exists somewhere in the universe: "Matt Ahrens added the ability to get estimated progress for zfs send and receive (! )" http://www.usenix.org/events/lisa11/tech/slides/cantrill.pdf I can't seem to find more info on this. Did this trickle into FreeBSD? Thanks, Mark From owner-freebsd-fs@FreeBSD.ORG Sat Mar 17 01:39:28 2012 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 071DC106566C for ; Sat, 17 Mar 2012 01:39:28 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id B967E8FC0A for ; Sat, 17 Mar 2012 01:39:27 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1S8ic5-0006cA-1a for freebsd-fs@freebsd.org; Sat, 17 Mar 2012 02:39:21 +0100 Received: from ip-89-102-199-219.net.upcbroadband.cz ([89.102.199.219]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 17 Mar 2012 02:39:20 +0100 Received: from gamato by ip-89-102-199-219.net.upcbroadband.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 17 Mar 2012 02:39:20 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: martinko Date: Sat, 17 Mar 2012 02:39:10 +0100 Lines: 31 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ip-89-102-199-219.net.upcbroadband.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.18) Gecko/20110424 SeaMonkey/2.0.13 Cc: freebsd-stable@freebsd.org Subject: booting from ZFS hangs and system does not respond 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, 17 Mar 2012 01:39:28 -0000 Hi, Booting from ZFS hangs and system gets unresponsive. Details follow.. My system is an older installation where I have two 1TB disks with several smaller partitions for testing and then a big one for FreeBSD. The latter is comprised of 1GB UFS + swap + ZFS. UFS is used for booting and then the whole system is on ZFS (as it used to be standard before booting from ZFS was available). ZFS set up as mirror. Now all ran happily until one day PC-BSD 8.2 was installed into one of the small partitions. No idea why but since then FreeBSD wouldn't boot. It started displaying the prompt below but either keyboard is ignored or the system hangs, as nothing can be done at that point. GEOM_LABEL: Label for provider ... is ... Trying to mount root from zfs:tank/ROOT Manual root filesystem specification: [...] mountroot> Now my question is what might have possibly gone wrong and how to fix it ? And by fixing I mean either making system run again (preferably) or at least saving data (getting them of ZFS). Thanks in advance! M. PS: I forgot to mention that this is FreeBSD 7.2 installation. From owner-freebsd-fs@FreeBSD.ORG Sat Mar 17 04:42:20 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EB616106566B; Sat, 17 Mar 2012 04:42: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 C3F4F8FC12; Sat, 17 Mar 2012 04:42:20 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2H4gK9C006085; Sat, 17 Mar 2012 04:42:20 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2H4gKaP006081; Sat, 17 Mar 2012 04:42:20 GMT (envelope-from linimon) Date: Sat, 17 Mar 2012 04:42:20 GMT Message-Id: <201203170442.q2H4gKaP006081@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/166193: [ufs] [hang] FB 8.0 freeze during the kernel dump 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, 17 Mar 2012 04:42:21 -0000 Old Synopsis: FB 8.0 freeze during the kernel dump New Synopsis: [ufs] [hang] FB 8.0 freeze during the kernel dump Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Mar 17 04:41:07 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). Apparently the fix is simple (patch doadump). http://www.freebsd.org/cgi/query-pr.cgi?pr=166193