From owner-freebsd-fs@FreeBSD.ORG Sun Dec 27 14:58:01 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28D191065672; Sun, 27 Dec 2009 14:58:01 +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 009818FC1E; Sun, 27 Dec 2009 14:58:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBREw0VQ041123; Sun, 27 Dec 2009 14:58:00 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBREw0Jg041119; Sun, 27 Dec 2009 14:58:00 GMT (envelope-from linimon) Date: Sun, 27 Dec 2009 14:58:00 GMT Message-Id: <200912271458.nBREw0Jg041119@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/142068: [ufs] BSD labels are got deleted spontaneously 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, 27 Dec 2009 14:58:01 -0000 Old Synopsis: BSD labels are got deleted spontaneously New Synopsis: [ufs] BSD labels are got deleted spontaneously Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sun Dec 27 14:56:06 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=142068 From owner-freebsd-fs@FreeBSD.ORG Sun Dec 27 21:05:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AF2B1065672 for ; Sun, 27 Dec 2009 21:05:49 +0000 (UTC) (envelope-from stevenschlansker@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id 1FC898FC1B for ; Sun, 27 Dec 2009 21:05:49 +0000 (UTC) Received: by yxe1 with SMTP id 1so9098858yxe.3 for ; Sun, 27 Dec 2009 13:05:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=O5wfgCRqDQ42P4zaWo5J/uPr4uylK4gre/wyZtjPuzo=; b=nKT8E9iYbzUIc1SZIv/wz7zChAeKNGvYRb5xRIpzXCa6rc3V0lb+Ts4gq4uxIhRdg/ 1D4SpHNHhgBMiZAUzfp1ehWamnDEcG2UZqJCc71pb5I5pLta99pij1rO8PHG77sH6Qg8 +Xh0cgMSIHa2CSe2WegQVY9r9lb8PxZiOy5yA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=wvrVdpr4UVvNI/0n5UKcVXxdfuiP3pihcxXiR7xPg6RELfbQBjRQYEtv+8kCeSlt2Q 2dvUUjWYPWE3itALgfpfCmOcT2KKWgTmoiaZ42P3eGSTMrT8YnMCBIimw06pAA2UH3BK fImq69yQ9P1e6VJRP7k04eiz+6f+Hx9/sAC9M= Received: by 10.150.119.3 with SMTP id r3mr11425068ybc.324.1261947941527; Sun, 27 Dec 2009 13:05:41 -0800 (PST) Received: from ?192.168.1.114? (adsl-75-41-56-45.dsl.pltn13.sbcglobal.net [75.41.56.45]) by mx.google.com with ESMTPS id 20sm3868283ywh.17.2009.12.27.13.05.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 27 Dec 2009 13:05:40 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Steven Schlansker In-Reply-To: Date: Sun, 27 Dec 2009 13:05:37 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <5565955F-482A-4628-A528-117C58046B1F@gmail.com> References: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> <4B315320.5050504@quip.cz> <5da0588e0912221741r48395defnd11e34728d2b7b97@mail.gmail.com> <9CEE3EE5-2CF7-440E-B5F4-D2BD796EA55C@gmail.com> To: Wes Morgan X-Mailer: Apple Mail (2.1077) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Can't repair raidz2 (Cannot replace a replacing 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, 27 Dec 2009 21:05:49 -0000 On Dec 24, 2009, at 5:17 AM, Wes Morgan wrote: > On Wed, 23 Dec 2009, Steven Schlansker wrote: >>=20 >> Why has the replacing vdev not gone away? I still can't detach - >> [steven@universe:~]% sudo zpool detach universe 6170688083648327969 >> cannot detach 6170688083648327969: no valid replicas >> even though now there actually is a valid replica (ad26) >=20 > Try detaching ad26. If it lets you do that it will abort the = replacement and then you just do another replacement with the real = device. If it won't let you do that, you may be stuck having to do some = metadata tricks. >=20 Sadly, no go: pool: universe state: DEGRADED scrub: none requested config: NAME STATE READ WRITE CKSUM universe DEGRADED 0 0 0 raidz2 DEGRADED 0 0 0 ad16 ONLINE 0 0 0 replacing DEGRADED 0 0 5.04K ad26 ONLINE 0 0 0 6170688083648327969 UNAVAIL 0 1.08M 0 was = /dev/ad12 ad8 ONLINE 0 0 0 concat/back2 ONLINE 0 0 0 ad10 ONLINE 0 0 0 concat/ad4ex ONLINE 0 0 0 ad24 ONLINE 0 0 0 concat/ad6ex ONLINE 0 0 0 errors: No known data errors [steven@universe:~]% sudo zpool detach universe ad26 cannot detach ad26: no valid replicas [steven@universe:~]% sudo zpool offline -t universe ad26 cannot offline ad26: no valid replicas From owner-freebsd-fs@FreeBSD.ORG Mon Dec 28 01:24:05 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41B2D1065672 for ; Mon, 28 Dec 2009 01:24:05 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-yw0-f197.google.com (mail-yw0-f197.google.com [209.85.211.197]) by mx1.freebsd.org (Postfix) with ESMTP id 058048FC1B for ; Mon, 28 Dec 2009 01:24:04 +0000 (UTC) Received: by ywh35 with SMTP id 35so1734836ywh.7 for ; Sun, 27 Dec 2009 17:23:57 -0800 (PST) Received: by 10.91.50.3 with SMTP id c3mr2873881agk.71.1261963437775; Sun, 27 Dec 2009 17:23:57 -0800 (PST) Received: from ?10.0.1.198? (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id 15sm5066227gxk.8.2009.12.27.17.23.55 (version=SSLv3 cipher=RC4-MD5); Sun, 27 Dec 2009 17:23:56 -0800 (PST) Date: Sun, 27 Dec 2009 15:25:35 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: patpro In-Reply-To: <3ea87f5f62bb8ba30d798d4605a64c83@localhost> Message-ID: References: <32CA2B73-3412-49DD-9401-4773CC73BED0@patpro.net> <4B3283F2.7060804@barryp.org> <3ea87f5f62bb8ba30d798d4605a64c83@localhost> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: snapshot implementation 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, 28 Dec 2009 01:24:05 -0000 On Fri, 25 Dec 2009, patpro wrote: > > On Wed, 23 Dec 2009 14:56:18 -0600, Barry Pederson wrote: >> "...there's virtually no overhead at all due to the copy-on-write >> architecture. In fact, sometimes it is faster to take a snapshot rather >> than free the blocks containing the old data!" >> >> That's certainly not the case with UFS snapshots, which can take a long >> time to complete (we're talking freezing your machine's disk activity >> for many minutes), and are limited to 20 total. > > > UFS uses copy on write. But you say many minutes to complete? Don't you > speak about dump(1), that uses snapshot as a basis to dump a live file > system? > I agree, UFS snapshot creation is not lightning-fast, but many minutes > seems a lot to me, and I never experienced such a long creation time. It can take some time depending on fs activity on the machine. There are ways to continue to optimize it within the existing infrastructure. It only requires someone willing to expend the time. Jeff > > patpro > _______________________________________________ > 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 Dec 28 04:27:39 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E8CD1065694 for ; Mon, 28 Dec 2009 04:27:39 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 90D338FC08 for ; Mon, 28 Dec 2009 04:27:38 +0000 (UTC) Received: from volatile.chemikals.org (adsl-67-124-163.shv.bellsouth.net [98.67.124.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 0DFA1A1ED712; Sun, 27 Dec 2009 22:27:36 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id nBS4RXqY004745; Sun, 27 Dec 2009 22:27:33 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Sun, 27 Dec 2009 22:27:33 -0600 (CST) From: Wes Morgan X-X-Sender: morganw@volatile To: Steven Schlansker In-Reply-To: <5565955F-482A-4628-A528-117C58046B1F@gmail.com> Message-ID: References: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> <4B315320.5050504@quip.cz> <5da0588e0912221741r48395defnd11e34728d2b7b97@mail.gmail.com> <9CEE3EE5-2CF7-440E-B5F4-D2BD796EA55C@gmail.com> <5565955F-482A-4628-A528-117C58046B1F@gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.95.2 at warped X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Can't repair raidz2 (Cannot replace a replacing 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: Mon, 28 Dec 2009 04:27:39 -0000 On Sun, 27 Dec 2009, Steven Schlansker wrote: > > On Dec 24, 2009, at 5:17 AM, Wes Morgan wrote: > >> On Wed, 23 Dec 2009, Steven Schlansker wrote: >>> >>> Why has the replacing vdev not gone away? I still can't detach - >>> [steven@universe:~]% sudo zpool detach universe 6170688083648327969 >>> cannot detach 6170688083648327969: no valid replicas >>> even though now there actually is a valid replica (ad26) >> >> Try detaching ad26. If it lets you do that it will abort the replacement and then you just do another replacement with the real device. If it won't let you do that, you may be stuck having to do some metadata tricks. >> > > Sadly, no go: > > pool: universe > state: DEGRADED > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > universe DEGRADED 0 0 0 > raidz2 DEGRADED 0 0 0 > ad16 ONLINE 0 0 0 > replacing DEGRADED 0 0 5.04K > ad26 ONLINE 0 0 0 > 6170688083648327969 UNAVAIL 0 1.08M 0 was /dev/ad12 > ad8 ONLINE 0 0 0 > concat/back2 ONLINE 0 0 0 > ad10 ONLINE 0 0 0 > concat/ad4ex ONLINE 0 0 0 > ad24 ONLINE 0 0 0 > concat/ad6ex ONLINE 0 0 0 > > errors: No known data errors > [steven@universe:~]% sudo zpool detach universe ad26 > cannot detach ad26: no valid replicas > [steven@universe:~]% sudo zpool offline -t universe ad26 > cannot offline ad26: no valid replicas > Hmm. Looking through the spa_vdev_detach() code in sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c it is "failing" on either line 3046 or 3072. If it's failing on 3046, the bug would appear to be that it doesn't count the missing device as a child and allow you to detach it. In that case, a "hack" might be to bypass it by changing line 3045 to: if (pvd->vdev_children == 0) If the failure is on 3072, then somehow the original device is not being counted as a valid copy, so it won't allow you to detach. That check looks like it would be dangerous to bypass. Based on my experience with this failure, I'm betting the device counting is off and it's returning on line 3045. You might try inserting some debugging kernel printf's there or using kdb to step through it and see. If it is, I think bypassing 3045 might let you detach the nonexistent device. Of course, back up your data before attempting anything of the sort!! From owner-freebsd-fs@FreeBSD.ORG Mon Dec 28 04:59:39 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDE741065694 for ; Mon, 28 Dec 2009 04:59:39 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1A81C8FC0A for ; Mon, 28 Dec 2009 04:59:39 +0000 (UTC) Received: from volatile.chemikals.org (adsl-67-124-163.shv.bellsouth.net [98.67.124.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 27D40A1ED70F; Sun, 27 Dec 2009 22:59:38 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id nBS4xYLZ014138; Sun, 27 Dec 2009 22:59:35 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Sun, 27 Dec 2009 22:59:34 -0600 (CST) From: Wes Morgan X-X-Sender: morganw@volatile To: Steven Schlansker In-Reply-To: <5565955F-482A-4628-A528-117C58046B1F@gmail.com> Message-ID: References: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> <4B315320.5050504@quip.cz> <5da0588e0912221741r48395defnd11e34728d2b7b97@mail.gmail.com> <9CEE3EE5-2CF7-440E-B5F4-D2BD796EA55C@gmail.com> <5565955F-482A-4628-A528-117C58046B1F@gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.95.2 at warped X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Can't repair raidz2 (Cannot replace a replacing 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: Mon, 28 Dec 2009 04:59:39 -0000 On Sun, 27 Dec 2009, Steven Schlansker wrote: > > On Dec 24, 2009, at 5:17 AM, Wes Morgan wrote: > >> On Wed, 23 Dec 2009, Steven Schlansker wrote: >>> >>> Why has the replacing vdev not gone away? I still can't detach - >>> [steven@universe:~]% sudo zpool detach universe 6170688083648327969 >>> cannot detach 6170688083648327969: no valid replicas >>> even though now there actually is a valid replica (ad26) >> >> Try detaching ad26. If it lets you do that it will abort the replacement and then you just do another replacement with the real device. If it won't let you do that, you may be stuck having to do some metadata tricks. >> > > Sadly, no go: > > pool: universe > state: DEGRADED > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > universe DEGRADED 0 0 0 > raidz2 DEGRADED 0 0 0 > ad16 ONLINE 0 0 0 > replacing DEGRADED 0 0 5.04K > ad26 ONLINE 0 0 0 > 6170688083648327969 UNAVAIL 0 1.08M 0 was /dev/ad12 > ad8 ONLINE 0 0 0 > concat/back2 ONLINE 0 0 0 > ad10 ONLINE 0 0 0 > concat/ad4ex ONLINE 0 0 0 > ad24 ONLINE 0 0 0 > concat/ad6ex ONLINE 0 0 0 > > errors: No known data errors > [steven@universe:~]% sudo zpool detach universe ad26 > cannot detach ad26: no valid replicas > [steven@universe:~]% sudo zpool offline -t universe ad26 > cannot offline ad26: no valid replicas > I just tried to re-create this scenario with some sparse files and I was able to detach it completely (below). There is one difference, however. Your array is returning checksum errors for the ad26 device. Perhaps this is making the system think that there is no sibling device in the replacement node that has all the data, so it denies the detach. Even though logically the data will be recovered by a scrub later.. Interesting. If you can determine where the detach is failing, that will help paint the complete picture. [root@catalyst:~#]: zpool status testz2 pool: testz2 state: DEGRADED scrub: none requested config: NAME STATE READ WRITE CKSUM testz2 DEGRADED 0 0 0 raidz2 DEGRADED 0 0 0 md1 ONLINE 0 0 0 md2 ONLINE 0 0 0 replacing DEGRADED 0 0 0 md3 ONLINE 0 0 0 8502561034916233095 UNAVAIL 0 323 0 was /dev/md7 md4 ONLINE 0 0 0 md5 ONLINE 0 0 0 md6 ONLINE 0 0 0 errors: No known data errors [root@catalyst:~#]: zpool detach testz2 8502561034916233095 [root@catalyst:~#]: zpool status testz2 pool: testz2 state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM testz2 ONLINE 0 0 0 raidz2 ONLINE 0 0 0 md1 ONLINE 0 0 0 md2 ONLINE 0 0 0 md3 ONLINE 0 0 0 md4 ONLINE 0 0 0 md5 ONLINE 0 0 0 md6 ONLINE 0 0 0 errors: No known data errors [root@catalyst:~#]: From owner-freebsd-fs@FreeBSD.ORG Mon Dec 28 11:06:58 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FE20106566B for ; Mon, 28 Dec 2009 11:06:58 +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 556088FC13 for ; Mon, 28 Dec 2009 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBSB6wM0079466 for ; Mon, 28 Dec 2009 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBSB6vrX079462 for freebsd-fs@FreeBSD.org; Mon, 28 Dec 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Dec 2009 11:06:57 GMT Message-Id: <200912281106.nBSB6vrX079462@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, 28 Dec 2009 11:06:58 -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/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141992 fs [ufs] fsck cannot repair file system in which it finds o kern/141950 fs [unionfs] [lor] ufs/unionfs(/ufs) o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141800 fs [zfs] [patch] zfs pool update to v14 o kern/141718 fs [zfs] [panic] kernel panic when 'zfs rename' is used o o kern/141685 fs [zfs] zfs corruption on adaptec 5805 raid controller 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/141257 fs [gvinum] No puedo crear RAID5 por SW con gvinum o kern/141235 fs [disklabel] 8.0 no longer provides /dev entries for al o kern/141194 fs [tmpfs] tmpfs treats the size option as mod 2^32 o kern/141177 fs [zfs] fsync() on FIFO causes panic() on zfs 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/140682 fs [netgraph] [panic] random panic in netgraph o kern/140661 fs [zfs] /boot/loader fails to work on a GPT/ZFS-only sys o kern/140640 fs [zfs] snapshot crash o kern/140433 fs [zfs] [panic] panic while replaying ZIL after crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs o bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/139363 fs [nfs] diskless root nfs mount from non FreeBSD server o kern/138790 fs [zfs] ZFS ceases caching when mem demand is high o kern/138524 fs [msdosfs] disks and usb flashes/cards with Russian lab o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138367 fs [tmpfs] [panic] 'panic: Assertion pages > 0 failed' wh o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/138109 fs [extfs] [patch] Minor cleanups to the sys/gnu/fs/ext2f f kern/137037 fs [zfs] [hang] zfs rollback on root causes FreeBSD to fr o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic o kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135594 fs [zfs] Single dataset unresponsive with Samba o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133980 fs [panic] [ffs] panic: ffs_valloc: dup alloc o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [panic] panic: ffs_truncate: read-only filesystem o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132597 fs [tmpfs] [panic] tmpfs-related panic while interrupting o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131995 fs [nfs] Failure to mount NFSv4 server o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129059 fs [zfs] [patch] ZFS bootloader whitelistable via WITHOUT f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/127659 fs [tmpfs] tmpfs memory leak o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS p kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F f kern/119735 fs [zfs] geli + ZFS + samba starting on boot panics 7.0-B o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o kern/116913 fs [ffs] [panic] ffs_blkfree: freeing free block p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/115645 fs [snapshots] [panic] lockmgr: thread 0xc4c00d80, not ex o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] mount_msdosfs: msdosfs_iconv: Operation not o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [iso9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna f kern/91568 fs [ufs] [panic] writing to UFS/softupdates DVD media in o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o kern/85326 fs [smbfs] [panic] saving a file via samba to an overquot o kern/84589 fs [2TB] 5.4-STABLE unresponsive during background fsck 2 o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 155 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Dec 28 20:43:16 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 931951065695; Mon, 28 Dec 2009 20:43:16 +0000 (UTC) (envelope-from delphij@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6BF408FC0A; Mon, 28 Dec 2009 20:43:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBSKhGuv019593; Mon, 28 Dec 2009 20:43:16 GMT (envelope-from delphij@freefall.freebsd.org) Received: (from delphij@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBSKhG5B019589; Mon, 28 Dec 2009 20:43:16 GMT (envelope-from delphij) Date: Mon, 28 Dec 2009 20:43:16 GMT Message-Id: <200912282043.nBSKhG5B019589@freefall.freebsd.org> To: delphij@FreeBSD.org, freebsd-fs@FreeBSD.org, delphij@FreeBSD.org From: delphij@FreeBSD.org Cc: Subject: Re: kern/141800: [zfs] [patch] zfs pool update to v14 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, 28 Dec 2009 20:43:16 -0000 Synopsis: [zfs] [patch] zfs pool update to v14 Responsible-Changed-From-To: freebsd-fs->delphij Responsible-Changed-By: delphij Responsible-Changed-When: Mon Dec 28 20:41:40 UTC 2009 Responsible-Changed-Why: I'll handle this. http://www.freebsd.org/cgi/query-pr.cgi?pr=141800 From owner-freebsd-fs@FreeBSD.ORG Mon Dec 28 23:25:47 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E12810656A3 for ; Mon, 28 Dec 2009 23:25:47 +0000 (UTC) (envelope-from marco@tols.org) Received: from tols.org (goofy.tols.org [83.163.60.200]) by mx1.freebsd.org (Postfix) with ESMTP id BF6418FC12 for ; Mon, 28 Dec 2009 23:25:46 +0000 (UTC) Received: from donald.home.tols.org (localhost [127.0.0.1]) by donald.home.tols.org (8.14.3/8.14.3) with ESMTP id nBSMqSIn006569 for ; Mon, 28 Dec 2009 22:52:28 GMT (envelope-from marco@donald.home.tols.org) Received: (from marco@localhost) by donald.home.tols.org (8.14.3/8.14.3/Submit) id nBSMqSOZ006568 for freebsd-fs@freebsd.org; Mon, 28 Dec 2009 23:52:28 +0100 (CET) (envelope-from marco) Date: Mon, 28 Dec 2009 23:52:28 +0100 From: Marco van Tol To: freebsd-fs@freebsd.org Message-ID: <20091228225228.GA1114@donald.home.tols.org> Mail-Followup-To: freebsd-fs@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: zfs sharenfs to multiple subnets - found a dirty looking hack 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, 28 Dec 2009 23:25:47 -0000 Hi there, I would like to refer to a thread in this list about zfs exporting to multiple subnets using sharenfs. The thread I mean is this one: http://lists.freebsd.org/pipermail/freebsd-fs/2008-September/005158.html I wasn't subscribed at the time, so I'm just referencing to the thread. I was testing and needed to also export a filesystem to multiple subnets, and found something out that may or may not be allowed. What happens is you start to type zfs set sharenfs=" and don't close the double quote. The result on the following lines will literally make it to /etc/zfs/exports, and make it work as desired. A full session would look like: (Bear with me for typo's, I didn't copy-paste) zfs set sharenfs="-maproot=root -network 10.0.0.0/24 > /path/to/mountpoint -maproot=root -network 192.168.0.0/24 > /path/to/mountpoint -maproot=root -network 172.16.0.0/24" pool0/space This translates to an /etc/zfs/exports like: ----< cut here >---- /path/to/mountpoint -maproot=root -network=10.0.0.0/24 /path/to/mountpoint -maproot=root -network=192.168.0.0/24 /path/to/mountpoint -maproot=root -network=172.16.0.0/24 ----< cut here >---- The resulting "zfs get sharenfs" looks like: ----< cut here >---- pool0/space sharenfs -maproot=root -network=10.0.0.0/24 /path/to/mountpoint -maproot=root -network=192.168.0.0/24 /path/to/mountpoint -maproot=root -network=172.16.0.0/24 local ----< cut here >---- This all makes it work so that it exports the pool to multiple subnets, possibly with their own properties. Question is however, how desirable is it that this works? ;-) Kind regards, Marco van Tol -- It's fried rice, you plick. -- Lethal Weapon 4 From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 01:25:12 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F36B6106568B for ; Tue, 29 Dec 2009 01:25:11 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 80B078FC13 for ; Tue, 29 Dec 2009 01:25:10 +0000 (UTC) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id nBT1P9lQ061646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 29 Dec 2009 02:25:09 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id nBT1P6HA070100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 29 Dec 2009 02:25:06 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id nBT1P1oV071201 for ; Tue, 29 Dec 2009 02:25:06 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id nBT1OisK071200 for freebsd-fs@freebsd.org; Tue, 29 Dec 2009 02:24:44 +0100 (CET) (envelope-from ticso) Date: Tue, 29 Dec 2009 02:24:44 +0100 From: Bernd Walter To: freebsd-fs@freebsd.org Message-ID: <20091229012443.GF43739@cicely7.cicely.de> References: <20091228225228.GA1114@donald.home.tols.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091228225228.GA1114@donald.home.tols.org> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.013, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Subject: Re: zfs sharenfs to multiple subnets - found a dirty looking hack X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Dec 2009 01:25:12 -0000 On Mon, Dec 28, 2009 at 11:52:28PM +0100, Marco van Tol wrote: > Hi there, > > I would like to refer to a thread in this list about zfs exporting to > multiple subnets using sharenfs. The thread I mean is this one: > http://lists.freebsd.org/pipermail/freebsd-fs/2008-September/005158.html > I wasn't subscribed at the time, so I'm just referencing to the thread. > > I was testing and needed to also export a filesystem to multiple subnets, > and found something out that may or may not be allowed. > > What happens is you start to type > zfs set sharenfs=" > and don't close the double quote. The result on the following lines will > literally make it to /etc/zfs/exports, and make it work as desired. > > A full session would look like: > (Bear with me for typo's, I didn't copy-paste) > > zfs set sharenfs="-maproot=root -network 10.0.0.0/24 > > /path/to/mountpoint -maproot=root -network 192.168.0.0/24 > > /path/to/mountpoint -maproot=root -network 172.16.0.0/24" pool0/space > > This translates to an /etc/zfs/exports like: > ----< cut here >---- > /path/to/mountpoint -maproot=root -network=10.0.0.0/24 > /path/to/mountpoint -maproot=root -network=192.168.0.0/24 > /path/to/mountpoint -maproot=root -network=172.16.0.0/24 > ----< cut here >---- > > The resulting "zfs get sharenfs" looks like: > ----< cut here >---- > pool0/space sharenfs -maproot=root -network=10.0.0.0/24 > /path/to/mountpoint -maproot=root -network=192.168.0.0/24 > /path/to/mountpoint -maproot=root -network=172.16.0.0/24 local > ----< cut here >---- > > This all makes it work so that it exports the pool to multiple subnets, > possibly with their own properties. > > Question is however, how desirable is it that this works? ;-) The really cool thing about using zfs property instead of manual exports line is the ability to inherit export options, but since you need to write the path into the argument... It would be nice however if the export-file creator would parse the newline and automatically prepend the path to each line. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 10:35:10 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6426D1065672 for ; Tue, 29 Dec 2009 10:35:10 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out1.tiscali.nl (smtp-out1.tiscali.nl [195.241.79.176]) by mx1.freebsd.org (Postfix) with ESMTP id 215808FC17 for ; Tue, 29 Dec 2009 10:35:09 +0000 (UTC) Received: from [212.123.145.58] (helo=sjakie.klop.ws) by smtp-out1.tiscali.nl with esmtp (Exim) (envelope-from ) id 1NPZPw-0004g0-NO; Tue, 29 Dec 2009 11:35:08 +0100 Received: from 82-170-177-25.ip.telfort.nl (localhost [127.0.0.1]) by sjakie.klop.ws (Postfix) with ESMTP id 764111511F; Tue, 29 Dec 2009 11:35:03 +0100 (CET) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Thomas Burgess" References: <568624531.20091215163420@pyro.de> <42952D86-6B4D-49A3-8E4F-7A1A53A954C2@spry.com> <957649379.20091216005253@pyro.de> <26F8D203-A923-47D3-9935-BE4BC6DA09B7@corp.spry.com> <1696529130.20091223212612@pyro.de> Date: Tue, 29 Dec 2009 11:35:03 +0100 MIME-Version: 1.0 From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/10.10 (FreeBSD) Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS RaidZ2 with 24 drives? 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, 29 Dec 2009 10:35:10 -0000 On Fri, 25 Dec 2009 01:46:30 +0100, Thomas Burgess =20 wrote: > On Thu, Dec 24, 2009 at 11:53 AM, Ronald Klop > wrote: > >> Isn't it write caching? >> My Solaris machine at work also flushes the data every 30 seconds. >> >> Ronald. >> >> I think you are right. ZFS does work in bursts...it's very different = =20 >> than > what most people expect. I know it was really weird to me when i firs= t =20 > saw > it. So increase your load and you will see a steady stream of bytes when all = =20 the bursts are clustered together. :-) BTW: it isn't that weird. UFS does the same, but you probably never build= =20 a UFS of 24 disks before. Ronald. From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 10:51:38 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 283721065670 for ; Tue, 29 Dec 2009 10:51:38 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out3.tiscali.nl (smtp-out3.tiscali.nl [195.241.79.178]) by mx1.freebsd.org (Postfix) with ESMTP id DBB9A8FC08 for ; Tue, 29 Dec 2009 10:51:37 +0000 (UTC) Received: from [212.123.145.58] (helo=sjakie.klop.ws) by smtp-out3.tiscali.nl with esmtp (Exim) (envelope-from ) id 1NPZfs-0000Sl-OY; Tue, 29 Dec 2009 11:51:36 +0100 Received: from 82-170-177-25.ip.telfort.nl (localhost [127.0.0.1]) by sjakie.klop.ws (Postfix) with ESMTP id DBDAE15121; Tue, 29 Dec 2009 11:51:30 +0100 (CET) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: patpro , "Barry Pederson" References: <32CA2B73-3412-49DD-9401-4773CC73BED0@patpro.net> <4B3283F2.7060804@barryp.org> <3ea87f5f62bb8ba30d798d4605a64c83@localhost> Date: Tue, 29 Dec 2009 11:51:30 +0100 MIME-Version: 1.0 From: "Ronald Klop" Message-ID: In-Reply-To: <3ea87f5f62bb8ba30d798d4605a64c83@localhost> User-Agent: Opera Mail/10.10 (FreeBSD) Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: snapshot implementation 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, 29 Dec 2009 10:51:38 -0000 On Fri, 25 Dec 2009 15:29:53 +0100, patpro wrote: > > On Wed, 23 Dec 2009 14:56:18 -0600, Barry Pederson wrot= e: >> "...there's virtually no overhead at all due to the copy-on-write >> architecture. In fact, sometimes it is faster to take a snapshot rathe= r >> than free the blocks containing the old data!" >> >> That's certainly not the case with UFS snapshots, which can take a lon= g >> time to complete (we're talking freezing your machine's disk activity >> for many minutes), and are limited to 20 total. > > > UFS uses copy on write. But you say many minutes to complete? Don't you > speak about dump(1), that uses snapshot as a basis to dump a live file > system? > I agree, UFS snapshot creation is not lightning-fast, but many minutes > seems a lot to me, and I never experienced such a long creation time. As far as I know UFS snapshots need to create a list of currently in use = =20 blocks. This is O(n) on the size of the FS and pauses the FS during the =20 snapshot. On large FS's this can take a long time. ZFS always maintains this list so it only needs to mark this list as =20 readonly to create a snapshot. This is O(1). Ronald. From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 11:22:21 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C1581065698 for ; Tue, 29 Dec 2009 11:22:21 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by mx1.freebsd.org (Postfix) with ESMTP id A9CD18FC08 for ; Tue, 29 Dec 2009 11:22:18 +0000 (UTC) Received: from smtp5-g21.free.fr (localhost [127.0.0.1]) by smtp5-g21.free.fr (Postfix) with ESMTP id 22F78D4802A; Tue, 29 Dec 2009 12:22:14 +0100 (CET) Received: from boleskine.patpro.net (boleskine.patpro.net [82.230.142.222]) by smtp5-g21.free.fr (Postfix) with ESMTP id B572AD480BD; Tue, 29 Dec 2009 12:22:11 +0100 (CET) Received: from [192.168.0.2] (unknown [192.168.0.2]) by boleskine.patpro.net (Postfix) with ESMTP id 18F111CCD4; Tue, 29 Dec 2009 12:22:11 +0100 (CET) Message-Id: From: Patrick Proniewski To: "Ronald Klop" In-Reply-To: Content-Type: multipart/signed; boundary=Apple-Mail-1-310690000; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 29 Dec 2009 12:22:11 +0100 References: <32CA2B73-3412-49DD-9401-4773CC73BED0@patpro.net> <4B3283F2.7060804@barryp.org> <3ea87f5f62bb8ba30d798d4605a64c83@localhost> X-Mailer: Apple Mail (2.936) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: snapshot implementation 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, 29 Dec 2009 11:22:21 -0000 --Apple-Mail-1-310690000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable On 29 d=E9c. 2009, at 11:51, Ronald Klop wrote: >>> That's certainly not the case with UFS snapshots, which can take a =20= >>> long >>> time to complete (we're talking freezing your machine's disk =20 >>> activity >>> for many minutes), and are limited to 20 total. >> >> UFS uses copy on write. But you say many minutes to complete? Don't =20= >> you >> speak about dump(1), that uses snapshot as a basis to dump a live =20 >> file >> system? >> I agree, UFS snapshot creation is not lightning-fast, but many =20 >> minutes >> seems a lot to me, and I never experienced such a long creation time. > > As far as I know UFS snapshots need to create a list of currently in =20= > use blocks. This is O(n) on the size of the FS and pauses the FS =20 > during the snapshot. On large FS's this can take a long time. > ZFS always maintains this list so it only needs to mark this list as =20= > readonly to create a snapshot. This is O(1). That's a very interesting precision. Thank you. patpro= --Apple-Mail-1-310690000-- From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 17:27:32 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B11A010657CC for ; Tue, 29 Dec 2009 17:27:32 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 147A08FC26 for ; Tue, 29 Dec 2009 17:27:31 +0000 (UTC) Received: by ewy26 with SMTP id 26so8553836ewy.3 for ; Tue, 29 Dec 2009 09:27:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=/H9OEMKz4XWRraOFcSAZcGxo4F4E/fCQMRtbyTOF0Gc=; b=fMrPGsrhMGNttrzsh7sO762aIbKdQo63b75X4alYBoAIaTJRtS+4xLmCAs8DReEOEc /K6vMDewNA8Kj4+vGLrX/uOS24uqKEaztxBwfFMYbOzDtOG2AtOZdCvgmRk5iIojNZJf d4vncN0TzvYe7xADkecRUTpkyCFm1qAunn0t0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=nPz4H0t3uqmyDK8IK9SRx7CYjhTyU5fvdJtUIRSBPz6ICI2ea5auM0K8tLXePASXyM Bdcaogm6ZgZsRzHhUNjlQstvvqQXPpNfuYjgm1uBFy6mxg44l8zUA/rMbEtpUW4/vKNd yXc777IngdkKTOMVnAupqxzICurIrvp3SIYoU= MIME-Version: 1.0 Received: by 10.216.88.14 with SMTP id z14mr6197343wee.25.1262107644948; Tue, 29 Dec 2009 09:27:24 -0800 (PST) In-Reply-To: <200912282043.nBSKhG5B019589@freefall.freebsd.org> References: <200912282043.nBSKhG5B019589@freefall.freebsd.org> Date: Tue, 29 Dec 2009 12:27:24 -0500 Message-ID: <5f67a8c40912290927x787bcaa1vda350230ab07d29b@mail.gmail.com> From: Zaphod Beeblebrox To: delphij@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: kern/141800: [zfs] [patch] zfs pool update to v14 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, 29 Dec 2009 17:27:32 -0000 On Mon, Dec 28, 2009 at 3:43 PM, wrote: > Synopsis: [zfs] [patch] zfs pool update to v14 > > Responsible-Changed-From-To: freebsd-fs->delphij > Responsible-Changed-By: delphij > Responsible-Changed-When: Mon Dec 28 20:41:40 UTC 2009 > Responsible-Changed-Why: > I'll handle this. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=141800 Compelling, and yo do provide the OpenSolaris revision, so in theory I can find the changelog, but it would be handy if you could provide a URL to it :) From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 18:17:02 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7414106568F; Tue, 29 Dec 2009 18:17:02 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [IPv6:2001:470:a803::1]) by mx1.freebsd.org (Postfix) with ESMTP id 8DC808FC21; Tue, 29 Dec 2009 18:17:02 +0000 (UTC) Received: from mail.geekcn.org (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id EA258A5DE54; Wed, 30 Dec 2009 02:17:00 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by mail.geekcn.org (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with LMTP id sxKXLsRlFH31; Wed, 30 Dec 2009 02:16:52 +0800 (CST) Received: from delta.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 1A3B1A5DE52; Wed, 30 Dec 2009 02:16:50 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=m0OI4FZbHfD3wGrWTDx/unrVBxzL/nakeSCvC8afxi/c45nedCU3bcNTwli33hub0 W3lDkPf/gzIeF/ZweESdQ== Message-ID: <4B3A478E.3020006@delphij.net> Date: Tue, 29 Dec 2009 10:16:46 -0800 From: Xin LI Organization: The Geek China Organization User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.5) Gecko/20091220 Thunderbird/3.0 ThunderBrowse/3.2.6.8 MIME-Version: 1.0 To: Zaphod Beeblebrox References: <200912282043.nBSKhG5B019589@freefall.freebsd.org> <5f67a8c40912290927x787bcaa1vda350230ab07d29b@mail.gmail.com> In-Reply-To: <5f67a8c40912290927x787bcaa1vda350230ab07d29b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.ORG, delphij@FreeBSD.ORG Subject: Re: kern/141800: [zfs] [patch] zfs pool update to v14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Dec 2009 18:17:03 -0000 On 2009/12/29 09:27, Zaphod Beeblebrox wrote: > On Mon, Dec 28, 2009 at 3:43 PM, wrote: >> Synopsis: [zfs] [patch] zfs pool update to v14 >> >> Responsible-Changed-From-To: freebsd-fs->delphij >> Responsible-Changed-By: delphij >> Responsible-Changed-When: Mon Dec 28 20:41:40 UTC 2009 >> Responsible-Changed-Why: >> I'll handle this. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=141800 > > Compelling, and yo do provide the OpenSolaris revision, so in theory I > can find the changelog, but it would be handy if you could provide a > URL to it :) Oh I agree and I hope so but unfortunately, to be frank I never knew if there is a handy public OpenSolaris hg mirror with revisions, I have a OpenSolaris mercurial repository mirror of onnv-gate on my laptop and I use that for integrating the changes... Do anyone know if there is a permenent OpenSolaris mercurial repository mirror that provided web access? Cheers, -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 18:43:39 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A75EE1065676 for ; Tue, 29 Dec 2009 18:43:39 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [64.81.247.49]) by mx1.freebsd.org (Postfix) with ESMTP id 81F7E8FC08 for ; Tue, 29 Dec 2009 18:43:39 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id nBTIhBF0026212; Tue, 29 Dec 2009 10:43:11 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <200912291843.nBTIhBF0026212@chez.mckusick.com> To: Dan Strick X-URL: http://WWW.McKusick.COM/ Date: Tue, 29 Dec 2009 10:43:11 -0800 From: Kirk McKusick Cc: freebsd-fs@freebsd.org, bug-followup@freebsd.org Subject: kern/141992: fsck cannot repair file system in which it finds an error X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kirk McKusick List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Dec 2009 18:43:39 -0000 I am investigating your bug report about your problems with fsck in going from 6.1 to 8.0. There have been only insignificant changes in the filesystem during that time, so in theory you should not have any problems going back and forth between these two versions of FreeBSD. The fsck program has been changed to look more critically at the cylinder group maps, so some errors that would not previously have been detected will now be found. That said though, it should be able to completely fix those errors which it appears that it is not able to do. To help me track down your problem, please supply me with the following information: 1) Do you have more than one 6.1 filesystem that you are running on this system. If so, is this the only filesystem having trouble in this way, or are more than one of them exhibiting similar problems? 2) Are you getting any disk errors reported for this drive in /var/log/messages? It really looks like there is a bad sector in cylinder group 48 and so even though fsck can calculate a correct one, it is not able to write it out. Even if errors are not being reported, I am inclined to write a small test program that attempts to read and write the affected sectors to see if the changes stick. 3) Please provide me with a `dumpfs /dev/ad4s4a'. I don't need the whole (huge) thing. Just the start up through cylinder group 0, then the output for cylinder groups 47, 48, and 49. I am looking for any obvious anomolies in cylinder group 48 versus its neighbors. Hopefully we can sort out what is going wrong here. Kirk McKusick From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 18:48:17 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A7B6106566B; Tue, 29 Dec 2009 18:48:17 +0000 (UTC) (envelope-from mckusick@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 607F28FC0C; Tue, 29 Dec 2009 18:48:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBTImH7I070825; Tue, 29 Dec 2009 18:48:17 GMT (envelope-from mckusick@freefall.freebsd.org) Received: (from mckusick@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBTImHS4070821; Tue, 29 Dec 2009 18:48:17 GMT (envelope-from mckusick) Date: Tue, 29 Dec 2009 18:48:17 GMT Message-Id: <200912291848.nBTImHS4070821@freefall.freebsd.org> To: mckusick@FreeBSD.org, freebsd-fs@FreeBSD.org, mckusick@FreeBSD.org From: mckusick@FreeBSD.org Cc: Subject: Re: kern/141992: [ufs] fsck cannot repair file system in which it finds an error [regression] 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, 29 Dec 2009 18:48:17 -0000 Synopsis: [ufs] fsck cannot repair file system in which it finds an error [regression] Responsible-Changed-From-To: freebsd-fs->mckusick Responsible-Changed-By: mckusick Responsible-Changed-When: Tue Dec 29 18:47:02 UTC 2009 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=141992 From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 18:51:37 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FE2A106566B for ; Tue, 29 Dec 2009 18:51:37 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-iw0-f198.google.com (mail-iw0-f198.google.com [209.85.223.198]) by mx1.freebsd.org (Postfix) with ESMTP id E76878FC16 for ; Tue, 29 Dec 2009 18:51:36 +0000 (UTC) Received: by iwn36 with SMTP id 36so7665594iwn.3 for ; Tue, 29 Dec 2009 10:51:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=gSCf9xg1zucaQe2KTWwoW9dLEOq7cQEaKp82wYtLgtE=; b=k5EZbdpcLG/sUbWdK7dacSwJLvASZbV71+koG6KYo705wMwF14i7nf4Ede4sWeZyMY eTvVt2P0KTIDbbQqcfIyEPtIH61KrvV2UA2BDo7YYQbGOhiwGMvXAbkPwH3BKKkOd5Qk Jk3M+/5Y2ZlaYdWbQwbZMRcjYB9jNr/NVQcmg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=iQRaMpshw91mUKN4tuFwFYPNlcghJb63PDuMbnjDhCpAaGTwcUl1mFDN546scMAnrf ZRM1E8s62CPShWq7O/z4NUxmZbCFOEiYCI1bMe1IsT+UmgqY69J1ZyRL1WbFwSQdTYmV ofiXH6p3QW0yfSeQl1QQ/VXikoR4Ch4zi1vEk= MIME-Version: 1.0 Sender: artemb@gmail.com Received: by 10.231.81.148 with SMTP id x20mr3330267ibk.2.1262112690148; Tue, 29 Dec 2009 10:51:30 -0800 (PST) In-Reply-To: <4B3A478E.3020006@delphij.net> References: <200912282043.nBSKhG5B019589@freefall.freebsd.org> <5f67a8c40912290927x787bcaa1vda350230ab07d29b@mail.gmail.com> <4B3A478E.3020006@delphij.net> Date: Tue, 29 Dec 2009 10:51:30 -0800 X-Google-Sender-Auth: 6fa86bdb5736de15 Message-ID: From: Artem Belevich To: d@delphij.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, delphij@freebsd.org Subject: Re: kern/141800: [zfs] [patch] zfs pool update to v14 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, 29 Dec 2009 18:51:37 -0000 > Do anyone know if there is a permenent OpenSolaris mercurial repository > mirror that provided web access? Here's one: http://hg.intevation.org/mirrors/opensolaris.org/onnv-gate/ Changeset 8053 referred to in PR is here: http://hg.intevation.org/mirrors/opensolaris.org/onnv-gate/rev/271f44d3de11 You can do it yourself, too. Just clone onnv repository, run "hg serve" and then just open http://localhost:8000 in your favorite browser... --Artem On Tue, Dec 29, 2009 at 10:16 AM, Xin LI wrote: > On 2009/12/29 09:27, Zaphod Beeblebrox wrote: >> >> On Mon, Dec 28, 2009 at 3:43 PM, =A0wrote: >>> >>> Synopsis: [zfs] [patch] zfs pool update to v14 >>> >>> Responsible-Changed-From-To: freebsd-fs->delphij >>> Responsible-Changed-By: delphij >>> Responsible-Changed-When: Mon Dec 28 20:41:40 UTC 2009 >>> Responsible-Changed-Why: >>> I'll handle this. >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D141800 >> >> Compelling, and yo do provide the OpenSolaris revision, so in theory I >> can find the changelog, but it would be handy if you could provide a >> URL to it :) > > Oh I agree and I hope so but unfortunately, to be frank I never knew if > there is a handy public OpenSolaris hg mirror with revisions, I have a > OpenSolaris mercurial repository mirror of onnv-gate on my laptop and I u= se > that for integrating the changes... > > > Cheers, > -- > Xin LI =A0 =A0http://www.delphij.net/ > FreeBSD - The Power to Serve! =A0 =A0 =A0 =A0 =A0Live free or die > _______________________________________________ > 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 Dec 29 18:51:59 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 382B0106568B for ; Tue, 29 Dec 2009 18:51:59 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 9854E8FC1A for ; Tue, 29 Dec 2009 18:51:58 +0000 (UTC) Received: by fxm27 with SMTP id 27so11014794fxm.3 for ; Tue, 29 Dec 2009 10:51:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=dqBUiwYPEZzJEMU88CvLJH1GrcSqTQJCp5GPrbCld4E=; b=YzXvCJUjeIoPmwJEQ7v5uYwgswNgjFJzpOYiaKQ1Ym3km8JRJI8PlSqsG4394YAw7P ssVFJbYmmSZq3/ANNGMXPNfOODW+nOFajVG+ZlpHbUqQNNaml3iAOWo/cyRJamF8PBWP JAOIVVazCsNwyb1mjG09MGCmFsBNliW5x0I7s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=f9hMhrHDI/YP3h4ZMmwcrJz2vrQH7x7WxieMb7Xw+qrahphr4Gek94qrlmzZYjiRqs JqrcOtGlwJhnlEQUSahA71r8O5xXfWS1ysXbDkax4L0K9mTInSiMvDOjkiHHYoI8Ai+L MGfjhXga5ixC0JKeJbX2c5/NN2WIneL4fa6mQ= MIME-Version: 1.0 Received: by 10.239.134.134 with SMTP id 6mr33244hbz.44.1262112711743; Tue, 29 Dec 2009 10:51:51 -0800 (PST) In-Reply-To: <4B3A478E.3020006@delphij.net> References: <200912282043.nBSKhG5B019589@freefall.freebsd.org> <5f67a8c40912290927x787bcaa1vda350230ab07d29b@mail.gmail.com> <4B3A478E.3020006@delphij.net> Date: Tue, 29 Dec 2009 13:51:51 -0500 Message-ID: <5da0588e0912291051j32637458tef09747c0cc31f7f@mail.gmail.com> From: Rich To: d@delphij.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, delphij@freebsd.org Subject: Re: kern/141800: [zfs] [patch] zfs pool update to v14 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, 29 Dec 2009 18:51:59 -0000 On Tue, Dec 29, 2009 at 1:16 PM, Xin LI wrote: > On 2009/12/29 09:27, Zaphod Beeblebrox wrote: >> >> On Mon, Dec 28, 2009 at 3:43 PM, =A0wrote: >>> >>> Synopsis: [zfs] [patch] zfs pool update to v14 >>> >>> Responsible-Changed-From-To: freebsd-fs->delphij >>> Responsible-Changed-By: delphij >>> Responsible-Changed-When: Mon Dec 28 20:41:40 UTC 2009 >>> Responsible-Changed-Why: >>> I'll handle this. >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D141800 >> >> Compelling, and yo do provide the OpenSolaris revision, so in theory I >> can find the changelog, but it would be handy if you could provide a >> URL to it :) > > Oh I agree and I hope so but unfortunately, to be frank I never knew if > there is a handy public OpenSolaris hg mirror with revisions, I have a > OpenSolaris mercurial repository mirror of onnv-gate on my laptop and I u= se > that for integrating the changes... > > Do anyone know if there is a permenent OpenSolaris mercurial repository > mirror that provided web access? I'd just use their opengrok instance to look up rev 8053, like this search: http://src.opensolaris.org/source/search?q=3D&defs=3D&refs=3D&path=3D&hist= =3D+8053%3A271f44d3de11+&project=3D%2Fonnv Failing that, I could certainly set up a public onnv-gate web-accessible Hg mirror to do this. - Rich From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 21:13:14 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3EFA106566B for ; Tue, 29 Dec 2009 21:13:14 +0000 (UTC) (envelope-from mickael.maillot@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 3CC7C8FC18 for ; Tue, 29 Dec 2009 21:13:13 +0000 (UTC) Received: by ewy26 with SMTP id 26so8759313ewy.3 for ; Tue, 29 Dec 2009 13:13:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Il8yT8Z7Au2CaHQV8SFf2K1JFM78Krk0iFJwRqFwQiY=; b=djOrhclrwd3jYmmc6pZVddml8sEQnU9TwTnqZR51FLw6NmlBgWahbEtii888xBDSSO WMiPHH1dg5DUYsMQmibi6WSu2urb+/hFhvm6sefry2LkifrPnW19NJAoajLJJ98EZDef V0xAWQqwTP9QuvJhsv7iY/d+r/lHxUE3yenoA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=wspifpkxWCs4ITxF94WtARnEhZQeOR98Ie9b5PymO0yCa/g0NO3cL0mnZy74wbh7Wg KTypZdsC9TEZxZdv00LwMgsmQ0OGrjHgR4UvvI6ogLqXmc4GKg7yHUtBHjTBUkicW1FL 9aKDA/+4vb9L9znEWfj+br5+tIioizL4RWTj0= MIME-Version: 1.0 Received: by 10.216.86.131 with SMTP id w3mr6030062wee.156.1262119590812; Tue, 29 Dec 2009 12:46:30 -0800 (PST) Date: Tue, 29 Dec 2009 21:46:30 +0100 Message-ID: From: =?ISO-8859-1?Q?Micka=EBl_Maillot?= To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: ZFS small fix in arc.c and zvol.c 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, 29 Dec 2009 21:13:14 -0000 Hi, /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs in arc.c, a mutex is not properly detroyed: --- arc.c.orig 2009-12-29 21:15:31.192819155 +0100 +++ arc.c 2009-12-29 21:16:58.034271766 +0100 @@ -3626,6 +3626,7 @@ mutex_destroy(&arc_mru_ghost->arcs_mtx); mutex_destroy(&arc_mfu->arcs_mtx); mutex_destroy(&arc_mfu_ghost->arcs_mtx); + mutex_destroy(&arc_l2c_only->arcs_mtx); mutex_destroy(&zfs_write_limit_lock); i dont know if it's ok but in zvol.c opensolaris call zvol_size_changed just after zil_replay in zvol_create_minor function --- zvol.c.orig 2009-12-29 21:31:42.111529028 +0100 +++ zvol.c 2009-12-29 21:32:32.347413297 +0100 @@ -837,6 +837,7 @@ zv->zv_volblocksize = doi.doi_data_block_size; zil_replay(os, zv, &zv->zv_txg_assign, zvol_replay_vector, NULL); + zvol_size_changed(zv, maj); /* XXX this should handle the possible i/o error */ VERIFY(dsl_prop_register(dmu_objset_ds(zv->zv_objset), From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 22:32:06 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F5161065698 for ; Tue, 29 Dec 2009 22:32:06 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mx1.freebsd.org (Postfix) with ESMTP id 00BE68FC16 for ; Tue, 29 Dec 2009 22:32:05 +0000 (UTC) Received: by pwi15 with SMTP id 15so7725756pwi.3 for ; Tue, 29 Dec 2009 14:31:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=o6xZoR5s7zgJxPnvtLPLOhr4mBIsse3FHjVyfrAL0AQ=; b=eY2oYMojdeStdnRfYTOEq29tZXRGxLJNWm1k5uS3jJ/QH6bvrWkFGefgIAMgX+whjf n/UBoSsnQwHRBg9vDPbMhopwug7DIcytP0yP+De674H3gvDxg7nqzYjHAnP1CbwJC9m/ NDYnWfb+3QcZmgH4vdiNi1u2ajng92rxlYvmg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MAwwHlO2fArAcBcUXCa6emMYYw4UsKWPuuTI3yZ4yHPuNtpnf6GfvrCaLRz6jFT7F/ L7PxmnzbQPGkcfdi5LCD+KKV9YDB/mHzdt6VyjKhH3Do07N9BwK2I0hZaJRZTf5HNdVz axtwmll2EFv0MVW8kIgVcsBCMPEeHBXhlyAK4= MIME-Version: 1.0 Received: by 10.114.215.6 with SMTP id n6mr754307wag.158.1262124613995; Tue, 29 Dec 2009 14:10:13 -0800 (PST) In-Reply-To: References: Date: Tue, 29 Dec 2009 14:10:13 -0800 Message-ID: From: Xin LI To: =?UTF-8?Q?Micka=C3=ABl_Maillot?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS small fix in arc.c and zvol.c 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, 29 Dec 2009 22:32:06 -0000 Hi, I think we'd better to bring our base code to be more current rather than picking up individual revisions, diverging further is probably not a good idea if we see long term cooperation with OpenSolaris as a goal... On Tue, Dec 29, 2009 at 12:46 PM, Micka=C3=ABl Maillot wrote: > Hi, > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs > in arc.c, a mutex is not properly detroyed: > > --- arc.c.orig =C2=A02009-12-29 21:15:31.192819155 +0100 > +++ arc.c =C2=A0 =C2=A0 =C2=A0 2009-12-29 21:16:58.034271766 +0100 > @@ -3626,6 +3626,7 @@ > =C2=A0 =C2=A0 =C2=A0 =C2=A0mutex_destroy(&arc_mru_ghost->arcs_mtx); > =C2=A0 =C2=A0 =C2=A0 =C2=A0mutex_destroy(&arc_mfu->arcs_mtx); > =C2=A0 =C2=A0 =C2=A0 =C2=A0mutex_destroy(&arc_mfu_ghost->arcs_mtx); > + =C2=A0 =C2=A0 =C2=A0 mutex_destroy(&arc_l2c_only->arcs_mtx); > > =C2=A0 =C2=A0 =C2=A0 =C2=A0mutex_destroy(&zfs_write_limit_lock); Looks like a part of OpenSolaris onnv revision 8214? Are you having some specific issue without this patch? > i dont know if it's ok but in zvol.c > opensolaris call zvol_size_changed > just after zil_replay in zvol_create_minor function > > --- zvol.c.orig 2009-12-29 21:31:42.111529028 +0100 > +++ zvol.c =C2=A0 =C2=A0 =C2=A02009-12-29 21:32:32.347413297 +0100 > @@ -837,6 +837,7 @@ > =C2=A0 =C2=A0 =C2=A0 =C2=A0zv->zv_volblocksize =3D doi.doi_data_block_siz= e; > > =C2=A0 =C2=A0 =C2=A0 =C2=A0zil_replay(os, zv, &zv->zv_txg_assign, zvol_re= play_vector, NULL); > + =C2=A0 =C2=A0 =C2=A0 zvol_size_changed(zv, maj); > > =C2=A0 =C2=A0 =C2=A0 =C2=A0/* XXX this should handle the possible i/o err= or */ > =C2=A0 =C2=A0 =C2=A0 =C2=A0VERIFY(dsl_prop_register(dmu_objset_ds(zv->zv_= objset), It seems that the OpenSolaris code has changed a lot and I didn't find similar change in OpenSolaris (yet). Do you have a specific revision number or a tag? Cheers, --=20 Xin LI http://www.delphij.net From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 23:55:42 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E020C106566C for ; Tue, 29 Dec 2009 23:55:41 +0000 (UTC) (envelope-from mickael.maillot@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 74E008FC0C for ; Tue, 29 Dec 2009 23:55:40 +0000 (UTC) Received: by ewy26 with SMTP id 26so8877142ewy.3 for ; Tue, 29 Dec 2009 15:55:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hJ8bkPvd438d9qM5LfexGZY2xgk2xZIZcXM2YgwL4ts=; b=vHNAojcGGjVJw34XNLWbbWgnmomvIk5IVjVEBaH5gznlC7vB2zq9Jm0NaqeyDXbZHN kO3V6z7A6TKBFELRBF4vaD7yuaP/rh910H89dKdD4I8Zcv+VP1Pa5yZrSQC9Ms/CpxCe P1SBVIqjcXMpubfNvg35GeaypEoVgvUUEGTZw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Pz+zBH2tnqzFCWMtTJD1Ir09f4wDimqmE/pAItmmRhqxythtSjQFis4eNNGyXBkokB V8W6JSoEBThUou7O9mu2hsCSROeial7/KzzOH89JM51uP65zy376RE/wG8yZrUfTRVje Y8vHd2yHBV0861E1tYCg54TdB26lWDWbb2F+Y= MIME-Version: 1.0 Received: by 10.216.93.74 with SMTP id k52mr660856wef.144.1262130933043; Tue, 29 Dec 2009 15:55:33 -0800 (PST) In-Reply-To: References: Date: Wed, 30 Dec 2009 00:55:33 +0100 Message-ID: From: =?ISO-8859-1?Q?Micka=EBl_Maillot?= To: Xin LI Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS small fix in arc.c and zvol.c 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, 29 Dec 2009 23:55:42 -0000 2009/12/29 Xin LI : > Hi, > > I think we'd better to bring our base code to be more current rather > than picking up individual revisions, diverging further is probably > not a good idea if we see long term cooperation with OpenSolaris as a > goal... > > On Tue, Dec 29, 2009 at 12:46 PM, Micka=EBl Maillot > wrote: >> Hi, >> >> /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs >> in arc.c, a mutex is not properly detroyed: >> >> --- arc.c.orig =A02009-12-29 21:15:31.192819155 +0100 >> +++ arc.c =A0 =A0 =A0 2009-12-29 21:16:58.034271766 +0100 >> @@ -3626,6 +3626,7 @@ >> =A0 =A0 =A0 =A0mutex_destroy(&arc_mru_ghost->arcs_mtx); >> =A0 =A0 =A0 =A0mutex_destroy(&arc_mfu->arcs_mtx); >> =A0 =A0 =A0 =A0mutex_destroy(&arc_mfu_ghost->arcs_mtx); >> + =A0 =A0 =A0 mutex_destroy(&arc_l2c_only->arcs_mtx); >> >> =A0 =A0 =A0 =A0mutex_destroy(&zfs_write_limit_lock); > > Looks like a part of OpenSolaris onnv revision 8214? =A0Are you having > some specific issue without this patch? > i don't have any problem, it's just look like a miss. only this line is missing. http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=3D6747934 http://hg.intevation.org/mirrors/opensolaris.org/onnv-gate/rev/d7abf7c1f1c1 >> i dont know if it's ok but in zvol.c >> opensolaris call zvol_size_changed >> just after zil_replay in zvol_create_minor function >> >> --- zvol.c.orig 2009-12-29 21:31:42.111529028 +0100 >> +++ zvol.c =A0 =A0 =A02009-12-29 21:32:32.347413297 +0100 >> @@ -837,6 +837,7 @@ >> =A0 =A0 =A0 =A0zv->zv_volblocksize =3D doi.doi_data_block_size; >> >> =A0 =A0 =A0 =A0zil_replay(os, zv, &zv->zv_txg_assign, zvol_replay_vector= , NULL); >> + =A0 =A0 =A0 zvol_size_changed(zv, maj); >> >> =A0 =A0 =A0 =A0/* XXX this should handle the possible i/o error */ >> =A0 =A0 =A0 =A0VERIFY(dsl_prop_register(dmu_objset_ds(zv->zv_objset), > > It seems that the OpenSolaris code has changed a lot and I didn't find > similar change in OpenSolaris (yet). =A0Do you have a specific revision > number or a tag? > > Cheers, > -- > Xin LI http://www.delphij.net > i just compare with zvol.c at nov 2008, this line was recently removed with: http://cvs.opensolaris.org/source/diff/onnv/onnv-gate/usr/src/uts/common/fs= /zfs/zvol.c?r2=3D%252Fonnv%252Fonnv-gate%252Fusr%252Fsrc%252Futs%252Fcommon= %252Ffs%252Fzfs%252Fzvol.c%4010588%3Adc03f981ea18&r1=3D%252Fonnv%252Fonnv-g= ate%252Fusr%252Fsrc%252Futs%252Fcommon%252Ffs%252Fzfs%252Fzvol.c%4010310%3A= ba87b3315737 but with comment on r196927 from pjd, may be it's ok to add zvol_size_changed or totally useless. From owner-freebsd-fs@FreeBSD.ORG Wed Dec 30 05:18:37 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37CF71065672 for ; Wed, 30 Dec 2009 05:18:37 +0000 (UTC) (envelope-from benschumacher@gmail.com) Received: from mail-pz0-f185.google.com (mail-pz0-f185.google.com [209.85.222.185]) by mx1.freebsd.org (Postfix) with ESMTP id 095FF8FC12 for ; Wed, 30 Dec 2009 05:18:36 +0000 (UTC) Received: by pzk15 with SMTP id 15so8044530pzk.3 for ; Tue, 29 Dec 2009 21:18:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=gQqGNCfO+30ZdiPAL4P8kov+Ef8C52nBCiQhoy/+ZLc=; b=gEX6r7GxfaEjr8zoEgdWrwJWcpUP16Ayq88w81z2SA8kylFTTUvE3ASH1r/qJWy82a EUmGA3wHR+coMqVLF5c5Jn+5DqYuvPjEIrpOq0N579WQ4tCUt9Pbg6x1H607pZojtVh6 mXz/pyy8IDHmBWj7yRxv6Ui/pj1dUSIE8nhRg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=qQ8xiyU7hRrNOcORj2kS5HzpepMAyvD36KkyBCbiFDhBYBb9Z5+ngj1VRlPqVGCQAs 8cAZT6L9C+ICZTLBM9+wGWOVl95SPEo5sKmJfJ/1caIVFGRaj8uyiwm56IgMkenSo5l7 hHEbhVZj7UpUyfZJz0fpoiXgsCRDsXjHKE+kQ= MIME-Version: 1.0 Sender: benschumacher@gmail.com Received: by 10.143.25.29 with SMTP id c29mr11967259wfj.255.1262150309670; Tue, 29 Dec 2009 21:18:29 -0800 (PST) In-Reply-To: References: <32CA2B73-3412-49DD-9401-4773CC73BED0@patpro.net> <4B3283F2.7060804@barryp.org> <3ea87f5f62bb8ba30d798d4605a64c83@localhost> Date: Tue, 29 Dec 2009 22:18:29 -0700 X-Google-Sender-Auth: a94100bdc8d34bfc Message-ID: <9859143f0912292118h44a33961mc8207d9b943a5f1f@mail.gmail.com> From: Ben Schumacher To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Jeff Roberson Subject: Re: snapshot implementation 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, 30 Dec 2009 05:18:37 -0000 On Sun, Dec 27, 2009 at 6:25 PM, Jeff Roberson wr= ote: > It can take some time depending on fs activity on the machine. =C2=A0Ther= e are > ways to continue to optimize it within the existing infrastructure. =C2= =A0It only > requires someone willing to expend the time. Any idea how complex of a task this is (and how much fruit it would bear)? I've been interested in dipping my toes into some FreeBSD kernel work, but I'm not exactly sure where to start. I honestly don't have tons of free time to work on it (job commitments and all that), but am curious if this is something that an experienced C programmer would have a shot at doing having very little experience with low-level kernel internals. (I'm used to dealing with POSIX interfaces and not the code that implements them...) I've recently picked up a copy of "The Design and Implementation of the FreeBSD OS", so I'm starting there, but I would love it if anybody could toss me a hint or two on what some of the low-hanging fruit in the arena might be. I've been playing with ZFS on a few boxes now, but I've had (even with FreeBSD 8) enough unusual crashes that I'm personally not ready to commit to using it on at least one "mission critical" project I'm working on. That being said I'd love to be able to do snapshots on the box without it hanging for over an hour due to the fact that the data drive is >400GB (frankly on the small side for some of the storage applications I've read about on this mailing list). Any hints, tips, pointers would be appreciated. Cheers, Ben From owner-freebsd-fs@FreeBSD.ORG Wed Dec 30 14:59:26 2009 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 651A4106566C; Wed, 30 Dec 2009 14:59:26 +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 D31F28FC0C; Wed, 30 Dec 2009 14:59:25 +0000 (UTC) Received: from outgoing.leidinger.net (pD954FE07.dip.t-dialin.net [217.84.254.7]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 0DB6DA18E; Wed, 30 Dec 2009 15:59:16 +0100 (CET) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 96AD72C4E93; Wed, 30 Dec 2009 15:59:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1262185152; bh=xUv1vS+L4TsyNfGx8JPbtqG4dVM9MOQQSwln9pe+7hI=; h=Message-ID:Date:From:To:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding; b=oCTN9nai+8N1ToN1dYq6zKlJnnmEkI+KrcmPPWjIgwkLWFyAxXXLhCojLyFdfZMrX S7vzNnCpOIw89fqJAQyAKHHY2Yf1jzy2jzzQqqWGuQkWc+7yGJnxqeSSE5k/oKohtF VEbgNOYRAIdqBM1gEUiu8z+1WRWSEXxQDWJDN0myIG1cBasRFC+4Ajnxs/mA7zX1/Z xG7dDvFSdzV183a2kj6PUOIBgz3zREtFLLLmmLBRlcQPFaPg1CroWaZQwhlP+lzDLA oHOG6p7GqLgMjt4Ed8f8KmvP89TSbmZzlWPMu9McSvE1W/Bt8IY9Rp4+zGcrbr4DHx nCLjQ1LrG/2ZA== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id nBUExBvf088610; Wed, 30 Dec 2009 15:59:11 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from 192.168.2.46 ([192.168.2.46]) by webmail.leidinger.net (Horde Framework) with HTTP; Wed, 30 Dec 2009 15:59:10 +0100 Message-ID: <20091230155910.21474ubpm9u244qo@webmail.leidinger.net> Date: Wed, 30 Dec 2009 15:59:10 +0100 From: Alexander Leidinger To: fs@freebsd.org, stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.3) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 0DB6DA18E.2848C X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.686, required 6, autolearn=disabled, ALL_TRUSTED -1.44, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, J_CHICKENPOX_32 0.60, TW_SK 0.08, TW_ZF 0.08) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1262789960.52093@dA14L+B3GA+hEqYdWDK4zw X-EBL-Spam-Status: No Cc: Subject: Some fixes for ZFS on 7-stable (more testers wanted) 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, 30 Dec 2009 14:59:26 -0000 Hi, I backported some changes from 8-stable to 7-stable, I have this running on one 7-stable machine. I would like to get some more feedback for it (even an "it works for me" would be great). The main part of this change is that the FreeBSD taskqueue is used now instead of the opensolaris one (a more detailed list is below). It would also be nice if someone could have a look at the FIRST_THREAD_IN_PROC part. Can there be more than one thread at this place (I do not think so) and I should use FOREACH_THREAD_IN_PROC_instead? How to apply: - cd /usr/src/ - fetch http://www.Leidinger.net/FreeBSD/test/releng7_zfs_merge3.diff - fetch http://www.Leidinger.net/FreeBSD/test/opensolaris_taskq.c - fetch http://www.Leidinger.net/FreeBSD/test/taskq.h - mv taskq.h sys/cddl/contrib/opensolaris/uts/common/sys/taskq.h - mv opensolaris_taskq.c sys/cddl/compat/opensolaris/kern/opensolaris_taskq.c - patch -p0 --quiet nvl_priv' and given the type of the 'packed' pointer the compiler could assume proper alignment for the replacement of bzero() with an 8-byte wide store to be valid. The problem is with the programmer. The programmer knew that the address did not have the alignment guarantees needed for a regular assignment, but failed to inform the compiler of that fact. In fact, the programmer told the compiler the opposite: alignment is guaranteed. The fix is to avoid using a pointer of type "nvlist_t *" and instead use a "char *" pointer as the basis for calculating the address. This tells the compiler that only 1-byte alignment can be assumed and the compiler will either keep the bzero() call or instead replace it with a sequence of byte-wise stores. Both are valid. ---snip--- MERGE http://svn.freebsd.org/viewvc/base?view=revision&revision=195822 trasz - easy merge ---snip--- Fix extattr_list_file(2) on ZFS in case the attribute directory doesn't exist and user doesn't have write access to the file. Without this fix, it returns bogus value instead of 0. For some reason this didn't manifest on my kernel compiled with -O0. ---snip--- MERGE http://svn.freebsd.org/viewvc/base?view=revision&revision=195909 pjd - very easy merge ---snip--- We don't support ephemeral IDs in FreeBSD and without this fix ZFS can panic when in zfs_fuid_create_cred() when userid is negative. It is converted to unsigned value which makes IS_EPHEMERAL() macro to incorrectly report that this is ephemeral ID. The most reasonable solution for now is to always report that the given ID is not ephemeral. ---snip--- MERGE http://svn.freebsd.org/viewvc/base?view=revision&revision=196291 pjd - probably easy merge ---snip--- - Fix a race where /dev/zfs control device is created before ZFS is fully initialized. Also destroy /dev/zfs before doing other deinitializations. - Initialization through taskq is no longer needed and there is a race where one of the zpool/zfs command loads zfs.ko and tries to do some work immediately, but /dev/zfs is not there yet. ---snip--- MERGE http://svn.freebsd.org/viewvc/base?view=revision&revision=196269 marcel - easy merge ---snip--- Fix misalignment in nvpair_native_embedded() caused by the compiler replacing the bzero(). See also revision 195627, which fixed the misalignment in nvpair_native_embedded_array(). ---snip--- MERGE (this also affects dtrace) http://svn.freebsd.org/viewvc/base?view=revision&revision=196295 pjd - added stuff to be reviewed, taskqueue available & same syntax? ---snip--- Remove OpenSolaris taskq port (it performs very poorly in our kernel) and replace it with wrappers around our taskqueue(9). To make it possible implement taskqueue_member() function which returns 1 if the given thread was created by the given taskqueue. ---snip--- MERGE http://svn.freebsd.org/viewvc/base?view=revision&revision=196297 pjd - easy merge ---snip--- Fix panic in zfs recv code. The last vnode (mountpoint's vnode) can have 0 usecount. ---snip--- MERGE http://svn.freebsd.org/viewvc/base?view=revision&revision=196299 pjd - VI_UNLOCK same syntax in RELENG_7? ---snip--- - We need to recycle vnode instead of freeing znode. Submitted by: avg - Add missing vnode interlock unlock. - Remove redundant znode locking. ---snip--- MERGE http://svn.freebsd.org/viewvc/base?view=revision&revision=196301 pjd - probably easy merge ---snip--- If z_buf is NULL, we should free znode immediately. ---snip--- MERGE http://svn.freebsd.org/viewvc/base?view=revision&revision=196307 pjd - to be reviewed ---snip--- Manage asynchronous vnode release just like Solaris. ---snip--- Bye, Alexander. -- Zeus gave Leda the bird. 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 Dec 30 21:52:28 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B530A1065672 for ; Wed, 30 Dec 2009 21:52:28 +0000 (UTC) (envelope-from mahlerrd@yahoo.com) Received: from web51005.mail.re2.yahoo.com (web51005.mail.re2.yahoo.com [206.190.38.136]) by mx1.freebsd.org (Postfix) with SMTP id 5B93A8FC1F for ; Wed, 30 Dec 2009 21:52:28 +0000 (UTC) Received: (qmail 88191 invoked by uid 60001); 30 Dec 2009 21:25:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1262208345; bh=VAot/hW/9rcd8+hSizC1Utj4pKmIqPJGuoJXCbzxgSU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=SAXBmGA5vsf5zfmQY+yB6OIz61vZWdkD70G49fczrrF+n7aGOuBNcy6IeseYP/O4p2QRP/dIRxwL0hAuC2sbid3GQexTdoD9kyQEed6PCpxc9+RNWK1lv6Wct9IrL6QI113/bExI/P8HgJjf4aJkjZVi8syZy7ApEyfndLXFOCs= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=ANokX6q0e/dFRrM/C6RvEQi0mkQ7R9hOTA2Yl3ZzYr78U/UPjUihtL1anH2XXkgCc79OZQ2Sw6n1v71FErbGQpXuJEywN3cg6KyrUKzSQ5kKytZHaBqMDsuTFGFBHYcnGRDkptmmihYfdWNcwSQ4niVV25UyUCtgtGh/1/63JMc=; Message-ID: <368515.86742.qm@web51005.mail.re2.yahoo.com> X-YMail-OSG: 5J1zOhwVM1mi9Ta8W65JPW_z44iUPMMgVQN9OLbyjqP6PwYqXPCbp1IllzcnfnDiuGx4Wp8achnkhWqeAXZUrwmGxsBh1MnVIFLTFQuBzSUm4k6Z_G5n4wezoYfWIfaZCIzBx1.wo7sn0e5KngR4DlDNxb7.kbIM0Wjam0HZUTec2ujUbjP1zFzCUWtNFEGOFQWIamopSbfTmLOdd_sz2gNZz4KyD3zfg4UCyZvoOTD5XX16GW7KnUVYc4NNd0FkGEUW2AV3jY0yGsPlh5s0G4cGc4UCrc3OeqoRHWLeZxTOIgbBw62vCbTRAmD0ki4aQcnRDV54KWaj_jYopTbY5QiG8ItVk_Na9G9vTOGuQ1QKM7DWAT3rhcntaQ-- Received: from [174.101.168.4] by web51005.mail.re2.yahoo.com via HTTP; Wed, 30 Dec 2009 13:25:45 PST X-Mailer: YahooMailRC/240.3 YahooMailWebService/0.8.100.260964 Date: Wed, 30 Dec 2009 13:25:45 -0800 (PST) From: Richard Mahlerwein To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ZFS "Dataset is busy" error X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Richard Mahlerwein List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 21:52:28 -0000 I am attempting to test the interation of ZFS snapshots with the Previous Versions capability of Windows. I installed FreeBSD 8 into VMware workstation. curie# uname -a FreeBSD curie.localdomain 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I added a second drive (da1) and created a test pool on it. curie# zpool history History for 'tank': 2009-12-30.14:23:08 zpool create tank da1 I installed Samba 3.3 from ports... curie# smbd --version Version 3.3.9 Added a super simple entry to my smb.conf to allow user test to get to the shared /tank (which works fine, AFAICT), restarted all services and browsed the share from my windows host. I dropped in half a dozen text files, then tried... curie# zfs list NAME USED AVAIL REFER MOUNTPOINT tank 70.5K 2.94G 18K /tank curie# zfs snapshot tank@snap1 cannot create snapshot 'tank@snap1': dataset is busy I've tried google, but it's of not much help given the above strings to search on. (I also tried the freebsd-fs archives, but I just get this... Note:The archive search index was last rebuilt at Wednesday, 07 Feb 2007 20:23:54 UTC. Any postings after that will not be found by a search. Index rebuild is usally done once every 24 hours for this list. You can use a "View by date" link below to access more recent postings. ) This is nearly the same setup as I had 3 or 4 weeks ago on a VM while I was testing ZFS itself, and that worked flawlessly. I'm not sure what's different or changed. I shouldn't have deleted that VM. :) Can anyone help point me to where to look for what's going wrong, or for what other information you may need? From owner-freebsd-fs@FreeBSD.ORG Wed Dec 30 23:27:00 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5FE710656C0 for ; Wed, 30 Dec 2009 23:26:59 +0000 (UTC) (envelope-from mla_strick@att.net) Received: from smtp126.sbc.mail.sp1.yahoo.com (smtp126.sbc.mail.sp1.yahoo.com [69.147.65.185]) by mx1.freebsd.org (Postfix) with SMTP id 8AA358FC19 for ; Wed, 30 Dec 2009 23:26:59 +0000 (UTC) Received: (qmail 14110 invoked from network); 30 Dec 2009 23:00:17 -0000 Received: from adsl-69-228-80-86.dsl.pltn13.pacbell.net (mla_strick@69.228.80.86 with login) by smtp126.sbc.mail.sp1.yahoo.com with SMTP; 30 Dec 2009 15:00:17 -0800 PST X-Yahoo-SMTP: ppEzeiKswBBq7wHVNDEiPbPsAwzyGELyRI8IdiDYGqsxaD5uQA-- X-YMail-OSG: 63vdlwkVM1m_AFt2SVR7YAVo72YmiaGj5K0BcsANWezr8i3DmM3BagZwr3USnuBx5CWaOvyoisUNPimS3FKYDj1Ld3QHbyKpcF1QK5zj55qKYvHMzpRp9Nt4R6kw1xPGr1vyWfoS.s6nvF6sDCB_DNEou2Chq3NxLkfu5TxghXQZqnqw73Gk.eud6THl66q2jgRVGfYRJvIbvtqxHkx8zNmfiVRCJZZeJh9Gp3_ckop4nJw4HZVLh8my0iJYHL6RRmMPiMUQyYqBGnOGHNYExl4LSdlOjws- X-Yahoo-Newman-Property: ymail-3 Received: from mist.nodomain (localhost [127.0.0.1]) by mist.nodomain (8.14.3/8.14.3) with ESMTP id nBUN0Gmw004500; Wed, 30 Dec 2009 15:00:16 -0800 (PST) (envelope-from mla@mist.nodomain) Received: (from dan@localhost) by mist.nodomain (8.14.3/8.14.3/Submit) id nBUN0GEl004499; Wed, 30 Dec 2009 15:00:16 -0800 (PST) (envelope-from mla) Date: Wed, 30 Dec 2009 15:00:16 -0800 (PST) From: Dan Strick Message-Id: <200912302300.nBUN0GEl004499@mist.nodomain> To: mckusick@mckusick.com In-Reply-To: <200912301731.nBUHV720089853@chez.mckusick.com> Cc: freebsd-fs@freebsd.org, bug-followup@freebsd.org, mla@mist.nodomain Subject: Re: kern/141992: fsck cannot repair file system in which it finds an error 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, 30 Dec 2009 23:27:00 -0000 > From mckusick@mckusick.com Wed Dec 30 09:45:41 2009 > To: Dan Strick > Subject: Re: kern/141992: fsck cannot repair file system in ... > Date: Wed, 30 Dec 2009 09:31:07 -0800 > > Thanks.The thing that immediately jumps out at me is that the filesystem > is UFS1 format (which would make it 4.X vintage unless you specifically > requested UFS1 when you built it). The new code to fix cylinder groups > in fsck can only fix UFS2 filesystems. So the problem is that it is > unhappy with cylinder group 48, then tries to fix it and finds that > it cannot do anything. At a minimum it should just not do its check > for bad cylinder groups in UFS1 filesystems. The file system was probably created by FreeBSD 4.10, the first version of FreeBSD that would run on my machine. Perhaps when the new fsck finds a bad UFS1 cylinder group and cannot fix it, the new fsck should simply explain its limitation and recommend copying the UFS1 file system contents to a new UFS2 file system. > Is there a chance that I can either (1) get a copy of the mdconfig > disk image so I can work out a solution here, or (2) get a login > on your machine so I can poke at things there. > > Kirk McKusick I have prepared a new file system by deleting all files in the old file system, creating a huge file containing only zeros, and deleting the huge file. The new file system gzips nicely and still has the bad cylinder group. The new file system is about 16 MB compressed (almost 9 GB uncompressed). How should I send it to you? Dan Strick From owner-freebsd-fs@FreeBSD.ORG Wed Dec 30 23:52:55 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7659B106566B for ; Wed, 30 Dec 2009 23:52:55 +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 3DFA68FC16 for ; Wed, 30 Dec 2009 23:52:55 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.13.8+Sun/8.13.8) with ESMTP id nBUNqsoY029362; Wed, 30 Dec 2009 17:52:54 -0600 (CST) Date: Wed, 30 Dec 2009 17:52:54 -0600 (CST) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Richard Mahlerwein In-Reply-To: <368515.86742.qm@web51005.mail.re2.yahoo.com> Message-ID: References: <368515.86742.qm@web51005.mail.re2.yahoo.com> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Wed, 30 Dec 2009 17:52:54 -0600 (CST) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS "Dataset is busy" error 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, 30 Dec 2009 23:52:55 -0000 > > Added a super simple entry to my smb.conf to allow user test to get to the shared /tank (which works fine, AFAICT), restarted all services and browsed the share from my windows host. I dropped in half a dozen text files, then tried... > > curie# zfs list > NAME USED AVAIL REFER MOUNTPOINT > tank 70.5K 2.94G 18K /tank > > curie# zfs snapshot tank@snap1 > cannot create snapshot 'tank@snap1': dataset is busy This seems to have something to do with how the filesystem is mounted. See http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg00812.html Also see http://defect.opensolaris.org/bz/show_bug.cgi?id=5000 So try zfs unmount tank zfs mount tank and maybe it will start working as expected. I am finding more Google hits for FreeBSD and OS-X than I am for Solaris so it may be that this issue is somewhat OS specific. 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 Thu Dec 31 00:12:03 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E296C1065676; Thu, 31 Dec 2009 00:12:03 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [64.81.247.49]) by mx1.freebsd.org (Postfix) with ESMTP id A32B88FC12; Thu, 31 Dec 2009 00:12:03 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id nBV0BfPm024346; Wed, 30 Dec 2009 16:11:41 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <200912310011.nBV0BfPm024346@chez.mckusick.com> To: Dan Strick In-reply-to: <200912302300.nBUN0GEl004499@mist.nodomain> Date: Wed, 30 Dec 2009 16:11:41 -0800 From: Kirk McKusick Cc: freebsd-fs@freebsd.org, bug-followup@freebsd.org, mla@mist.nodomain Subject: Re: kern/141992: fsck cannot repair file system in which it finds an error 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, 31 Dec 2009 00:12:04 -0000 > Date: Wed, 30 Dec 2009 15:00:16 -0800 (PST) > From: Dan Strick > To: mckusick@mckusick.com > In-Reply-To: <200912301731.nBUHV720089853@chez.mckusick.com> > Cc: freebsd-fs@freebsd.org, bug-followup@freebsd.org, mla@mist.nodomain > Subject: Re: kern/141992: fsck cannot repair file system in which it finds > an error > X-BeenThere: freebsd-fs@freebsd.org > > > From mckusick@mckusick.com Wed Dec 30 09:45:41 2009 > > To: Dan Strick > > Subject: Re: kern/141992: fsck cannot repair file system in ... > > Date: Wed, 30 Dec 2009 09:31:07 -0800 > > > > Thanks.The thing that immediately jumps out at me is that the filesystem > > is UFS1 format (which would make it 4.X vintage unless you specifically > > requested UFS1 when you built it). The new code to fix cylinder groups > > in fsck can only fix UFS2 filesystems. So the problem is that it is > > unhappy with cylinder group 48, then tries to fix it and finds that > > it cannot do anything. At a minimum it should just not do its check > > for bad cylinder groups in UFS1 filesystems. > > The file system was probably created by FreeBSD 4.10, the first version > of FreeBSD that would run on my machine. Yes, quite believeable. > Perhaps when the new fsck finds a bad UFS1 cylinder group and cannot > fix it, the new fsck should simply explain its limitation and recommend > copying the UFS1 file system contents to a new UFS2 file system. That is what I will probably do unless an easy fix for UFS1 presents itself. > > Is there a chance that I can either (1) get a copy of the mdconfig > > disk image so I can work out a solution here, or (2) get a login > > on your machine so I can poke at things there. > > > > Kirk McKusick > > I have prepared a new file system by deleting all files in the old file > system, creating a huge file containing only zeros, and deleting the > huge file. The new file system gzips nicely and still has the bad > cylinder group. The new file system is about 16 MB compressed (almost > 9 GB uncompressed). How should I send it to you? > > Dan Strick > _______________________________________________ > 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" Excellent. I wish all folks that reported bugs could provide such help as you have :-) Do you have a web server on which you could put it from which I could do a download? Or an ftp server? If not, I'll create a guest account for you on my machine and let you download to that. ~Kirk From owner-freebsd-fs@FreeBSD.ORG Thu Dec 31 01:34:21 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACEFA1065670 for ; Thu, 31 Dec 2009 01:34:21 +0000 (UTC) (envelope-from mla_strick@att.net) Received: from smtp127.sbc.mail.sp1.yahoo.com (smtp127.sbc.mail.sp1.yahoo.com [69.147.65.186]) by mx1.freebsd.org (Postfix) with SMTP id 7B3A18FC18 for ; Thu, 31 Dec 2009 01:34:21 +0000 (UTC) Received: (qmail 42319 invoked from network); 31 Dec 2009 01:34:16 -0000 Received: from adsl-69-228-80-86.dsl.pltn13.pacbell.net (mla_strick@69.228.80.86 with login) by smtp127.sbc.mail.sp1.yahoo.com with SMTP; 30 Dec 2009 17:34:15 -0800 PST X-Yahoo-SMTP: ppEzeiKswBBq7wHVNDEiPbPsAwzyGELyRI8IdiDYGqsxaD5uQA-- X-YMail-OSG: 35HgGeAVM1kxlnrtMVOlSoud5sPsgsT9OG95OudAiRYiw4QndoZrmmnigN2v1A0BXPNA3_Eb6h98iOzWt45T44VTxw8YovZb8AHYKlBFM7lpFfdZbNhlEecr0cGEZ3Wix2xqx1qbPkSxsrEnkKbn282TDq5WCTxfPb.Fs_CzVR1Yy_3mae1aIeBsAcPBv69OGws5QqyBWpjX8sNfYqXwmcW7m_183d29QUDTnRab8MfK2IieO9mt2ZcC3hIs2jyH X-Yahoo-Newman-Property: ymail-3 Received: from mist.nodomain (localhost [127.0.0.1]) by mist.nodomain (8.14.3/8.14.3) with ESMTP id nBV1YFgE005500; Wed, 30 Dec 2009 17:34:15 -0800 (PST) (envelope-from mla@mist.nodomain) Received: (from dan@localhost) by mist.nodomain (8.14.3/8.14.3/Submit) id nBV1YFap005499; Wed, 30 Dec 2009 17:34:15 -0800 (PST) (envelope-from mla) Date: Wed, 30 Dec 2009 17:34:15 -0800 (PST) From: Dan Strick Message-Id: <200912310134.nBV1YFap005499@mist.nodomain> To: mckusick@mckusick.com In-Reply-To: <200912310011.nBV0BfPm024346@chez.mckusick.com> Cc: freebsd-fs@freebsd.org, bug-followup@freebsd.org, mla@mist.nodomain Subject: Re: kern/141992: fsck cannot repair file system in which it finds an error 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, 31 Dec 2009 01:34:21 -0000 > Do you have a web server on which you could put it from which I could > do a download? Or an ftp server? If not, I'll create a guest account > for you on my machine and let you download to that. I don't have a web or ftp server. I am pretty sure my ISP does not provide me with a place to store a web page. I should be able to anonymous ftp or do scp to a guest account. Send instructions. Thanks, Dan Strick From owner-freebsd-fs@FreeBSD.ORG Thu Dec 31 02:59:21 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F110106566C for ; Thu, 31 Dec 2009 02:59:21 +0000 (UTC) (envelope-from mahlerrd@yahoo.com) Received: from web51006.mail.re2.yahoo.com (web51006.mail.re2.yahoo.com [206.190.38.137]) by mx1.freebsd.org (Postfix) with SMTP id C1A048FC0C for ; Thu, 31 Dec 2009 02:59:20 +0000 (UTC) Received: (qmail 50690 invoked by uid 60001); 31 Dec 2009 02:59:17 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1262228357; bh=bjbIpLHtavY+84qxJlGhY3Uu1k3b4fHdzPREJIqmUCE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=4uroc8tB/7XVrgVBG65LJvbMlzq3O0fIDUC0TNFDp4kmMaR4VLqACiwm9aO2JGApFq35Fe6RxF3Bf7+Woxv95NUjwiYYR9/KLqNinmLaWawLbXsOUvIY47/IlfxNRDkPPBijvDekvhokDL0wClRSDEkfolNnoa3pRLehNcbScIA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=5oJFYLrEcw2HemElJQjznKpyPe9/vDrkJbsCky93MzWHKu0xHzrq9UVMkaXaX5vZS7EX6zpJ7Zs+VQqegLkrFrRPdAkrzvp9cYuXsU6blykRqrtGkMyPrAwzt/BDxN9bVz36xVR3KzgTamLLTSFmwlC3rDT51jSjnGfiLmlj7WM=; Message-ID: <489290.49450.qm@web51006.mail.re2.yahoo.com> X-YMail-OSG: y_Ik_D8VM1l2Xx7TTHYJ105XTJtEUtQB6m9H3V3ghqVXS4S.uMY28FHnK.I8mP8UqsQBZqLvJYv6d4UK2lGE9k51yfOYtLM3nO6DkzOgrJumx3nHLXSqcqENDCqZFDOlZqTG7hg_iuaVlQCd6Kn0CJhUXEWbFPoO1y77eR_bQMJ04SHw_eO8RWgMoDZznNCJSs5X9.1Uh3xG7oZrDwuA_MvB_FSK8Jj6IwkEYpzL5qmM5rhCJxfThrzB4.1czBqEzuWgZNFca2Zq4vPOnwD8BdEKqp9rqbN_XO5FeuMYxBNn27_v6kdb0UH5SFadWC9mC3J7WQmPN8ecJG5GYBK6M9adSzbOdPXpSr_nuxBKRRtcAGi4_wDIPK_T9fwi.UitS2t4UWn9FqLqiR5l1_hpbOusXpqggqQk6lYiRrrhJYGbh.jQ1a60xZySQWT3sUAYPa.W4LX79bkGJa4.HtCTBoezSeUfmNrSYS6.FKFTqcC21.xfUx.tj0hq.wB2Z_UVWWH_r.5lF8kJdmdQrDsoGNfhPecJWiOJGkb67J_4hTNHz30SszXyxUFIjYqvMWKbcczKaaC0yFuyEbEmsAL3O91g7C_mGw-- Received: from [208.95.208.226] by web51006.mail.re2.yahoo.com via HTTP; Wed, 30 Dec 2009 18:59:17 PST X-Mailer: YahooMailRC/240.3 YahooMailWebService/0.8.100.260964 References: <368515.86742.qm@web51005.mail.re2.yahoo.com> Date: Wed, 30 Dec 2009 18:59:17 -0800 (PST) From: Richard Mahlerwein To: Bob Friesenhahn In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS "Dataset is busy" error X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Richard Mahlerwein List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2009 02:59:21 -0000 >From: Bob Friesenhahn >To: Richard Mahlerwein >Cc: freebsd-fs@freebsd.org >Sent: Wed, December 30, 2009 6:52:54 PM >Subject: Re: ZFS "Dataset is busy" error > >> >> Added a super simple entry to my smb.conf to allow user test to get to the shared /tank (which works fine, AFAICT), restarted all services and browsed the share from my windows host. I dropped in half a dozen text files, then tried... >> >> curie# zfs list >> NAME USED AVAIL REFER MOUNTPOINT >> tank 70.5K 2.94G 18K /tank >> >> curie# zfs snapshot tank@snap1 >> cannot create snapshot 'tank@snap1': dataset is busy > >This seems to have something to do with how the filesystem is mounted. >See >http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg00812.html >Also see >http://defect.opensolaris.org/bz/show_bug.cgi?id=5000 >So try > zfs unmount tank > zfs mount tank >and maybe it will start working as expected. > >I am finding more Google hits for FreeBSD and OS-X than I am for >Solaris so it may be that this issue is somewhat OS specific. So, a completely unrelated bug with Windows and ACPI took down my machine while the VM was running. After some tomfoolery to get filesystems cleaned back up again, I tried what you suggested... curie# zfs unmount tank curie# zfs mount tank curie# zfs snapshot tank@snap1 curie# Poof! Success! At least at making snapshots. Of course, I don't yet see a "Previous Versions" tab in the properties of anything yet (which I do see on some other shares from other servers). But at least now I can fool with those a bit. Thanks Bob! From owner-freebsd-fs@FreeBSD.ORG Thu Dec 31 09:55:44 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20F181065696 for ; Thu, 31 Dec 2009 09:55:44 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id CF8B28FC18 for ; Thu, 31 Dec 2009 09:55:42 +0000 (UTC) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7BA7719E045; Thu, 31 Dec 2009 10:55:41 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 10BF619E044; Thu, 31 Dec 2009 10:55:39 +0100 (CET) Message-ID: <4B3C751A.9040909@quip.cz> Date: Thu, 31 Dec 2009 10:55:38 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1 MIME-Version: 1.0 To: Richard Mahlerwein References: <368515.86742.qm@web51005.mail.re2.yahoo.com> <489290.49450.qm@web51006.mail.re2.yahoo.com> In-Reply-To: <489290.49450.qm@web51006.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS "Dataset is busy" error / Samba + Previous Versions 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, 31 Dec 2009 09:55:44 -0000 Richard Mahlerwein wrote: >> From: Bob Friesenhahn [...] >> This seems to have something to do with how the filesystem is mounted. >> See >> http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg00812.html >> Also see >> http://defect.opensolaris.org/bz/show_bug.cgi?id=5000 >> So try >> zfs unmount tank >> zfs mount tank >> and maybe it will start working as expected. >> >> I am finding more Google hits for FreeBSD and OS-X than I am for >> Solaris so it may be that this issue is somewhat OS specific. > > So, a completely unrelated bug with Windows and ACPI took down my machine while the VM was running. After some tomfoolery to get filesystems cleaned back up again, I tried what you suggested... > > curie# zfs unmount tank > curie# zfs mount tank > curie# zfs snapshot tank@snap1 > curie# > > Poof! Success! At least at making snapshots. Of course, I don't yet see a "Previous Versions" tab in the properties of anything yet (which I do see on some other shares from other servers). But at least now I can fool with those a bit. Do you see Previous Versions on Samaba shares from FreeBSD? I think you need some tweaks in smb.conf: http://www.edplese.com/samba-with-zfs.html http://www.edplese.com/blog/2009/12/02/samba-shadow_copy2-enhancements/ http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/VFS.html#id2651813 Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Thu Dec 31 13:52:24 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D66211065672 for ; Thu, 31 Dec 2009 13:52:24 +0000 (UTC) (envelope-from mahlerrd@yahoo.com) Received: from web51002.mail.re2.yahoo.com (web51002.mail.re2.yahoo.com [206.190.38.133]) by mx1.freebsd.org (Postfix) with SMTP id 899E78FC17 for ; Thu, 31 Dec 2009 13:52:24 +0000 (UTC) Received: (qmail 17251 invoked by uid 60001); 31 Dec 2009 13:52:21 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1262267541; bh=kFuGSpBPJil7A9kJrlBbGT+A6LWqawMRkiAb5S8JGMY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=30u+8uVq9cdx2gN5Fd9CSeyuFnEfHYKef5Ipu1/62zJ/btd4pFAG8idQ+nTgVg65ydNYx+fX3S0W3ZSXiusJfyMULd3MC87vnQAiDFpJnIR4izlhk8nLwRstnbtHpc/R6p8hwLH8nOuP69WgWyAPH87tzKrNEYbOOsWtAsNHQdA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=rKx4NF3Ft73uVgnr6PBxrZ9Wlfwp2LiMRw0KLui0Na3T4tu+pI8nI7yWsQFUqJaA7x9R2ZcO+JSfM+PVJkU3FOr73l1rUUbsRAUHSIKtpFFdxdKXk6fi3CnF1JGjL7pKLSS6jBVfz/Yx6bWjFRqQrTeZX54EgEhNVzpSEEK60g4=; Message-ID: <463202.16609.qm@web51002.mail.re2.yahoo.com> X-YMail-OSG: qeXYTQEVM1mmGiyr3THVggx2sFRRR3mRlFuQ9tv_0nBOcu1DZiTKDOByMbs1N.PkNlBLxvUzcv15L5dIZj5j2Ha_aaiV63rMR1YzFEgSg8pvm9g2QbJ7tFtiPprmraypI1l2n87fRK3l7V_eb.9fOACADVDqa9jCDPYX.Ktol5DAm.f.FDCL.ln4uUep8Rnz03NM6mIvDbLzrayenpj6DhWfuNU91v1VBiU6LLsPM.BSO.gHZn6M67OqWH.yK8Xb3El9NHJGZNxvhDeRONnsX1KmIkfvrLEHDxunfdbdQ6aS5nhMZnO9cWHZSsk37cDckFgxXKeRSm3q6IDieMR.B.UDHrSxmlD9Hvdk5E3xpqvHtyBZ5gRd14O6T_SE2kw3VVXhM_BGJymD23nJp9GII0SSlyzxuvyoYJRIp9hhLzgRARY0XfYQKGqvEHH8eT0_X0HU4tG02kKPKqvE8qHSMXTkM04VNq0o4fDceN7KRXD6C4M2qhA2UUOqiMdEwjPnb85NuZ2809cIDVIg5.UwNOxW2rx2ETK0fH7aX.VvuLnVHEqKLIESl1vTjljtAknRFWy0vrtwKF3y8rOl.7r7KqepUWiPZ2sr.epB9Vb2siYm7Vl1xntcAM4nohW89AtUe06mhrJeAcJeWLahf43Zjbm.tLTE3U1U_cYQCzNMmV499I._gJzHsnN.we182GGB.KH_js7ZD6wBTHkoKrd0N0f7664.et7pJsqRkQ-- Received: from [174.101.168.4] by web51002.mail.re2.yahoo.com via HTTP; Thu, 31 Dec 2009 05:52:21 PST X-Mailer: YahooMailRC/240.3 YahooMailWebService/0.8.100.260964 References: <368515.86742.qm@web51005.mail.re2.yahoo.com> <489290.49450.qm@web51006.mail.re2.yahoo.com> <4B3C751A.9040909@quip.cz> Date: Thu, 31 Dec 2009 05:52:21 -0800 (PST) From: Richard Mahlerwein To: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: <4B3C751A.9040909@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org Subject: Re: ZFS "Dataset is busy" error / Samba + Previous Versions X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Richard Mahlerwein List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2009 13:52:25 -0000 >From: Miroslav Lachman <000.fbsd@quip.cz> >Subject: Re: ZFS "Dataset is busy" error / Samba + Previous Versions > >Richard Mahlerwein wrote: >>> From: Bob Friesenhahn > >[...] > >>> This seems to have something to do with how the filesystem is mounted. >>> See >>> http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg00812.html >>> Also see >>> http://defect.opensolaris.org/bz/show_bug.cgi?id=5000 >>> So try >>> zfs unmount tank >>> zfs mount tank >>> and maybe it will start working as expected. >>> >>> I am finding more Google hits for FreeBSD and OS-X than I am for >>> Solaris so it may be that this issue is somewhat OS specific. >> >> So, a completely unrelated bug with Windows and ACPI took >> down my machine while the VM was running. After some >> tomfoolery to get filesystems cleaned back up again, I tried >> what you suggested... >> >> curie# zfs unmount tank >> curie# zfs mount tank >> curie# zfs snapshot tank@snap1 >> curie# >> >> Poof! Success! At least at making snapshots. Of course, >> I don't yet see a "Previous Versions" tab in the properties of >> anything yet (which I do see on some other shares from other >> servers). But at least now I can fool with those a bit. > >Do you see Previous Versions on Samba shares from FreeBSD? I >think you need some tweaks in smb.conf: > >http://www.edplese.com/samba-with-zfs.html > >http://www.edplese.com/blog/2009/12/02/samba-shadow_copy2-enhancements/ > >http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/VFS.html#id2651813 > >Miroslav Lachman Thanks!. I had found the last link, but it was a bit hard to follow since it was so LVM specific. Hopefully, the patches in the second link will be reasonably easily modified to apply to the 3.3.9 source, because that's my easiest avenue to get it running. And, the first link looks fabulous. When I get something working, I'll have to try some of those. Neat stuff. Hopefully I'll get some time to fool with it this week yet and if I get anywhere, I'll update everyone. -Rich From owner-freebsd-fs@FreeBSD.ORG Thu Dec 31 16:13:24 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAF021065679 for ; Thu, 31 Dec 2009 16:13:24 +0000 (UTC) (envelope-from mickael.maillot@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 839D68FC1A for ; Thu, 31 Dec 2009 16:13:24 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so3342894eyf.9 for ; Thu, 31 Dec 2009 08:13:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=4gGeHh1Jkl1EqLkFVKWd2p46lsuWibmQ4iZiDWJtp44=; b=NXGAhpLg0/5pjXXMkh8kECxsKofSRSo+Izddi+dZP4ZPDVzASKdZID8aZv9YEgyvZf nMbo59QHjfWC/ICwtbxYyLn8lKGnJhLd4QVRkenGiM4YPVcp8oo5mNWJO1aP6unU3A6W zo1g0oNsUMaTPbwXHdkl1YPg9EJag77J6yZ8w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=B/JFf410mAaGL3yQIH6ydAOpNeEeXEClfsj0IXxZXC3CU70QYzCDDA2ZIFHAwWvCOv BcW8JfhRsz1y25fSiO6d75lspB8rAvH8njPSyKbLz9sdGTc4IgDYjxHRat/MAsfRVjGP 3KttWaNNsS+iG3nAQjQupzg57nlJKEOXv73WA= MIME-Version: 1.0 Received: by 10.216.85.209 with SMTP id u59mr7297526wee.109.1262275995097; Thu, 31 Dec 2009 08:13:15 -0800 (PST) Date: Thu, 31 Dec 2009 17:13:15 +0100 Message-ID: From: =?ISO-8859-1?Q?Micka=EBl_Maillot?= To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: ZFS prefetch 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, 31 Dec 2009 16:13:25 -0000 this bug is referenced: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6859997 and a good description can be found here: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6861397 and a long thread on zfs-discuss http://mail.opensolaris.org/pipermail/zfs-discuss/2009-July/029710.html i use bob friesenhahn's script to test (with little mod) http://www.simplesystems.org/users/bfriesen/zfs-discuss/zfs-cache-test.ksh so i test on my hardware for reading 3000 8M files without prefetch: no problem initial real 7m49.039s user 0m2.931s sys 0m22.574s second real 7m48.080s user 0m2.858s sys 0m32.559s with prefetch enable: initial real 2m55.163s user 0m2.244s sys 0m10.072s second real 7m37.522s user 0m2.367s sys 0m10.565s ok i hit the same bug. it was fix by this commit: http://hg.intevation.org/mirrors/opensolaris.org/onnv-gate/rev/0e96dd3b905a which add kstats for prefetch and a bug in rollback (not for us) the only modif for the prefetch + arc problem is resolv by: --- dmu_zfetch.c.orig 2009-12-31 15:46:15.211700719 +0100 +++ dmu_zfetch.c 2009-12-31 15:46:42.915461251 +0100 @@ -323,7 +323,8 @@ * we will read "len" blocks before "striding". */ if (zh->zst_offset >= zs->zst_offset && - zh->zst_offset < zs->zst_offset + zs->zst_len) { + zh->zst_offset < zs->zst_offset + zs->zst_len && + prefetched) { /* already fetched */ rc = 1; goto out; with this patch i have: initial real 2m57.614s user 0m2.228s sys 0m10.054s second real 2m45.403s user 0m2.445s sys 0m9.726s third real 2m16.381s user 0m2.152s sys 0m9.136s looks good. tested on 8-STABLE amd64, with/without log/cache ssd. (but not with zil_disable) From owner-freebsd-fs@FreeBSD.ORG Thu Dec 31 22:22:54 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6F1A1065694 for ; Thu, 31 Dec 2009 22:22:54 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gx0-f218.google.com (mail-gx0-f218.google.com [209.85.217.218]) by mx1.freebsd.org (Postfix) with ESMTP id 757688FC17 for ; Thu, 31 Dec 2009 22:22:54 +0000 (UTC) Received: by gxk10 with SMTP id 10so12538747gxk.3 for ; Thu, 31 Dec 2009 14:22:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:date:from:to:cc :subject:in-reply-to:message-id:references:user-agent :x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version :content-type; bh=b6T3YaoN+Oy0xvID81VRude2NMfcSYr594jHJ9NiLgg=; b=h2nwgIZYzGt5HbyyZ7+KkIUGcdCCOBcIglk+C+WScPzgeiVOOZdXCaxkfbSXBLuoNc cZII/VdHfyvse2P+NHZ8Kx5/+ZubIEO9SHp3Hsqxpvpm3FzFxmeHlmFl98ClNJjEN7gF lRiwlnQ+JmmaWOSzX7qJIE4JuF5Q/DqKY+qVU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version :content-type; b=hTjROb0gbm2f32luef2acXx59/u1k8PahVw+RZ4HA7tNvHfpM4YUa+2MNFMBkzjpjj l2WWPAluH9mmtUk3EnyBUMRpLWu6VEDVzxyrK9M6pPqNtRj1zRt5iZ70KAq57vdtOr3L 1fjhLxJeXW+ElgbrOhX/1EV1/8DC9MJ+hGNjg= Received: by 10.150.172.6 with SMTP id u6mr12368520ybe.41.1262298166307; Thu, 31 Dec 2009 14:22:46 -0800 (PST) Received: from dimension.5p.local (ppp-22.194.dialinfree.com [209.172.22.194]) by mx.google.com with ESMTPS id 20sm14048998iwn.5.2009.12.31.14.22.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 31 Dec 2009 14:22:45 -0800 (PST) Sender: "J. Hellenthal" Date: Thu, 31 Dec 2009 17:22:26 -0500 From: jhell To: =?ISO-8859-15?Q?Micka=EBl_Maillot?= In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1091451658-817458301-1262298180=:72873" Cc: freebsd-fs@freebsd.org Subject: Re: ZFS prefetch 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, 31 Dec 2009 22:22:54 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1091451658-817458301-1262298180=:72873 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 31 Dec 2009 11:13, mickael.maillot@ wrote: > this bug is referenced: > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6859997 > and a good description can be found here: > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6861397 > and a long thread on zfs-discuss > http://mail.opensolaris.org/pipermail/zfs-discuss/2009-July/029710.html > > i use bob friesenhahn's script to test (with little mod) > http://www.simplesystems.org/users/bfriesen/zfs-discuss/zfs-cache-test.ksh > > so i test on my hardware for reading 3000 8M files > > without prefetch: no problem > initial > real 7m49.039s > user 0m2.931s > sys 0m22.574s > second > real 7m48.080s > user 0m2.858s > sys 0m32.559s > > with prefetch enable: > initial > real 2m55.163s > user 0m2.244s > sys 0m10.072s > second > real 7m37.522s > user 0m2.367s > sys 0m10.565s > > ok i hit the same bug. > it was fix by this commit: > http://hg.intevation.org/mirrors/opensolaris.org/onnv-gate/rev/0e96dd3b905a > which add kstats for prefetch and a bug in rollback (not for us) > > the only modif for the prefetch + arc problem is resolv by: > --- dmu_zfetch.c.orig 2009-12-31 15:46:15.211700719 +0100 > +++ dmu_zfetch.c 2009-12-31 15:46:42.915461251 +0100 > @@ -323,7 +323,8 @@ > * we will read "len" blocks before "striding". > */ > if (zh->zst_offset >= zs->zst_offset && > - zh->zst_offset < zs->zst_offset + zs->zst_len) { > + zh->zst_offset < zs->zst_offset + zs->zst_len && > + prefetched) { > /* already fetched */ > rc = 1; > goto out; > > with this patch i have: > initial > real 2m57.614s > user 0m2.228s > sys 0m10.054s > second > real 2m45.403s > user 0m2.445s > sys 0m9.726s > third > real 2m16.381s > user 0m2.152s > sys 0m9.136s > > looks good. > tested on 8-STABLE amd64, with/without log/cache ssd. (but not with zil_disable) > Thanks for the heads up on this. I have applied the following to a stable/7 system @r201336 "The obrien new year copyright ;)" and will write back with further results. Attached is a patch to r201336. Happy New Years! - -- Thu Dec 31 17:08:44 2009 jhell -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJLPSQtAAoJEJBXh4mJ2FR+SdcH/jb7j6Fb7OfvRwY2yNpoJ3iG li5NZ3Ukj7CC4XNIYS3nal3xg55oIvzTfjX6+c7MCCpbx2p3RuAvMh2wOcU+B2vn Pdvd0sDFRG96caUrdJ0O1ZIs2SmdVSKz/vxQEVtWW6EUq/4NOd+D243zDJxqOYED CkgobJmymWQ9swxR0uvH0vlsj8mK481GkMJPWVKDthGvjLU72dp+A1sCEj1e7B3J b9n48m66jUSYJwxO0Kyf8oHNVYdUvOURcwrSnS0yUdZlsUIn0ALHEGkO26N3Jl0V Te9CFuNaQfpsswTMiZQvpMVfhPk+292tGXsERaxx4m46SyWFnZYpXu8qUIwqhpM= =0pfh -----END PGP SIGNATURE----- --1091451658-817458301-1262298180=:72873 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=r201336+dmu_zfetch.c.patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=r201336+dmu_zfetch.c.patch LS0tIGRtdV96ZmV0Y2guYy5vcmlnCTIwMDktMTItMzEgMTY6NTQ6MTcuOTIx NDk2MjgzIC0wNTAwDQorKysgZG11X3pmZXRjaC5jCTIwMDktMTItMzEgMTY6 NTg6MTYuMjc4MTEzMzk1IC0wNTAwDQpAQCAtMzI0LDcgKzMyNCw4IEBADQog CQkgKiB3ZSB3aWxsIHJlYWQgImxlbiIgYmxvY2tzIGJlZm9yZSAic3RyaWRp bmciLg0KIAkJICovDQogCQlpZiAoemgtPnpzdF9vZmZzZXQgPj0genMtPnpz dF9vZmZzZXQgJiYNCi0JCSAgICB6aC0+enN0X29mZnNldCA8IHpzLT56c3Rf b2Zmc2V0ICsgenMtPnpzdF9sZW4pIHsNCisJCSAgICB6aC0+enN0X29mZnNl dCA8IHpzLT56c3Rfb2Zmc2V0ICsgenMtPnpzdF9sZW4gJiYNCisJCQlwcmVm ZXRjaGVkKSB7DQogCQkJLyogYWxyZWFkeSBmZXRjaGVkICovDQogCQkJcmMg PSAxOw0KIAkJCWdvdG8gb3V0Ow0K --1091451658-817458301-1262298180=:72873-- From owner-freebsd-fs@FreeBSD.ORG Thu Dec 31 22:37:06 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5D91106566C for ; Thu, 31 Dec 2009 22:37:06 +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 69AC88FC08 for ; Thu, 31 Dec 2009 22:37:06 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.13.8+Sun/8.13.8) with ESMTP id nBVMarbm011123; Thu, 31 Dec 2009 16:36:53 -0600 (CST) Date: Thu, 31 Dec 2009 16:36:53 -0600 (CST) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: jhell In-Reply-To: Message-ID: References: User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-76287759-1262299013=:1586" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Thu, 31 Dec 2009 16:36:53 -0600 (CST) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS prefetch 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, 31 Dec 2009 22:37:06 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-76287759-1262299013=:1586 Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 31 Dec 2009, jhell wrote: >> >> looks good. >> tested on 8-STABLE amd64, with/without log/cache ssd. (but not with >> zil_disable) >> > > Thanks for the heads up on this. I have applied the following to a stable/7 > system @r201336 "The obrien new year copyright ;)" and will write back with > further results. Now if someone can figure out how to crank up (double) the prefetch rate for my little test, I would be happy. 145MB/second is not nearly enough, especially if zfs can sometimes deliver 5X (or more) that rate. The read performance I see here (under Solaris 10) is very similar to the numbers posted by Mickaël Maillot. In fact initial read performance values posted by many others was almost the same, regardless of how many drives are available (e.g. 2 or 48 SAS drives). This suggests that zfs is not accellerating prefetch fast enough to make much difference for 8GB files. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ ---559023410-76287759-1262299013=:1586--