From owner-freebsd-fs@FreeBSD.ORG Sun Aug 29 08:21:23 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 347D310656B5 for ; Sun, 29 Aug 2010 08:21:23 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 8F6508FC0A for ; Sun, 29 Aug 2010 08:21:11 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 2F7F445E9C; Sun, 29 Aug 2010 10:21:10 +0200 (CEST) Received: from localhost (chello089077043238.chello.pl [89.77.43.238]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 4974545683; Sun, 29 Aug 2010 10:21:05 +0200 (CEST) Date: Sun, 29 Aug 2010 10:20:55 +0200 From: Pawel Jakub Dawidek To: Zhu Han Message-ID: <20100829082055.GA43904@garage.freebsd.pl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS Porting Roadmap 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, 29 Aug 2010 08:21:23 -0000 --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 27, 2010 at 10:44:54AM +0800, Zhu Han wrote: > Hi, >=20 > Does anybody know is there a road map document on porting different zpool > versions to FreeBSD? I want to know when will ZFS pool version 19 be port= ed > to FreeBSD? Removal of slog device is important for our environment. I'm getting very close to be able to publish ZFS v28 patch for wider testing. It might happen even today, but the patch will be very experimental. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkx6GGcACgkQForvXbEpPzQwrACeJzheKYgZwpIBgRFMOdbN2J5W Od8AmgJz5MLM7NP6v9LWGeU+v29P/2JK =C52l -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY-- From owner-freebsd-fs@FreeBSD.ORG Sun Aug 29 08:49:39 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72BA71065694; Sun, 29 Aug 2010 08:49:39 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7469E8FC16; Sun, 29 Aug 2010 08:49:38 +0000 (UTC) Received: by fxm4 with SMTP id 4so3192602fxm.13 for ; Sun, 29 Aug 2010 01:49:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=MGM58uv0UovCfym5HFAl8XGd6WoYqoQ14gQj9OPtKb0=; b=Y5LoBphq6USUwHSVLTljbPfC6UxAT09qcz5CvVLR7s2E/BxEvEGopkaZ38kTazq8T+ H2R0qLXADvix6g/I62Aw/fUCvdBFRPnTRRcE8jrbKLOjLjf3FrUc6qzg4oIQ1KX51KKm /RGP4QwEK5CvleR2mTh+WeaBkt8JDZgqb+NX4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=pNpjfDphYZXVLw7rE80xhofI8/2rz/Ts6ZSflwny8boD+FCewp06QK6XYEkLLJboRM 5DVvqJzffOTeeODGL0YjUbd06XAuiB9DiBkVTDdp84pPxgaoA6a58dOmjI7/wQofVseY 8WyqcuXBSgLymwcS2SNCdFLmXds4o0RDyJc/g= Received: by 10.223.113.65 with SMTP id z1mr2412925fap.38.1283071777570; Sun, 29 Aug 2010 01:49:37 -0700 (PDT) Received: from limbo.lan ([193.33.173.33]) by mx.google.com with ESMTPS id c20sm2777380fak.33.2010.08.29.01.49.35 (version=SSLv3 cipher=RC4-MD5); Sun, 29 Aug 2010 01:49:36 -0700 (PDT) Message-ID: <4C7A1F1D.7070109@gmail.com> Date: Sun, 29 Aug 2010 11:49:33 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; uk-UA; rv:1.9.2.8) Gecko/20100807 Thunderbird/3.1.2 MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20100829082055.GA43904@garage.freebsd.pl> In-Reply-To: <20100829082055.GA43904@garage.freebsd.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS Porting Roadmap 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, 29 Aug 2010 08:49:39 -0000 29.08.2010 11:20, Pawel Jakub Dawidek wrote: >> Does anybody know is there a road map document on porting different zpool >> versions to FreeBSD? I want to know when will ZFS pool version 19 be ported >> to FreeBSD? Removal of slog device is important for our environment. > > I'm getting very close to be able to publish ZFS v28 patch for wider > testing. It might happen even today, but the patch will be very > experimental. Would that one include PSARC 2010/306? If no how far is this from OpenSolaris source HEAD? I have tried to patch v15 with this one, but I have no luck because code was slightly different in some files... -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 29 10:29:46 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87ED010656A7 for ; Sun, 29 Aug 2010 10:29:46 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id DFBB48FC24 for ; Sun, 29 Aug 2010 10:29:34 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 0D6F645EA4; Sun, 29 Aug 2010 12:29:33 +0200 (CEST) Received: from localhost (chello089077043238.chello.pl [89.77.43.238]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id DB51F45E9C; Sun, 29 Aug 2010 12:29:27 +0200 (CEST) Date: Sun, 29 Aug 2010 12:29:19 +0200 From: Pawel Jakub Dawidek To: Volodymyr Kostyrko Message-ID: <20100829102919.GA1848@garage.freebsd.pl> References: <20100829082055.GA43904@garage.freebsd.pl> <4C7A1F1D.7070109@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <4C7A1F1D.7070109@gmail.com> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS Porting Roadmap 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, 29 Aug 2010 10:29:46 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 29, 2010 at 11:49:33AM +0300, Volodymyr Kostyrko wrote: > 29.08.2010 11:20, Pawel Jakub Dawidek wrote: > >>Does anybody know is there a road map document on porting different zpo= ol > >>versions to FreeBSD? I want to know when will ZFS pool version 19 be=20 > >>ported > >>to FreeBSD? Removal of slog device is important for our environment. > > > >I'm getting very close to be able to publish ZFS v28 patch for wider > >testing. It might happen even today, but the patch will be very > >experimental. >=20 > Would that one include PSARC 2010/306? >=20 > If no how far is this from OpenSolaris source HEAD? I have tried to=20 > patch v15 with this one, but I have no luck because code was slightly=20 > different in some files... The patch I want to publish contains everything what Sun and Oracle published so far. It is the most recent version you can get. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkx6Nn8ACgkQForvXbEpPzQePACgppNwQ+e1m7VVw240gsFQEc1Q mwkAoKGmUxVQRjitM0cFdyIze/l9PXU/ =XrQW -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-freebsd-fs@FreeBSD.ORG Sun Aug 29 22:28:07 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D7CA10657F6 for ; Sun, 29 Aug 2010 22:28:04 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by mx1.freebsd.org (Postfix) with ESMTP id 7F0B68FC08 for ; Sun, 29 Aug 2010 22:28:04 +0000 (UTC) X-AuditID: 12074425-b7cccae000005f17-29-4c7adeeba1ef Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-8.mit.edu (Symantec Brightmail Gateway) with SMTP id DA.B1.24343.BEEDA7C4; Sun, 29 Aug 2010 18:27:55 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id o7TMS3E5026754; Sun, 29 Aug 2010 18:28:03 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o7TMS1D6005695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 29 Aug 2010 18:28:03 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id o7TMS0M2026313; Sun, 29 Aug 2010 18:28:00 -0400 (EDT) Date: Sun, 29 Aug 2010 18:28:00 -0400 (EDT) From: Benjamin Kaduk To: Kostik Belousov In-Reply-To: <20100828082453.GG2396@deviant.kiev.zoral.com.ua> Message-ID: References: <20100828082453.GG2396@deviant.kiev.zoral.com.ua> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: AAAAAgB+j9UVxJa6 Cc: freebsd-fs@freebsd.org Subject: Re: memory inconsistencies with OpenAFS on FreeBSD X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2010 22:28:07 -0000 On Sat, 28 Aug 2010, Kostik Belousov wrote: > On Sat, Aug 28, 2010 at 12:28:51AM -0400, Benjamin Kaduk wrote: >> >> I also don't seem to be able to run executables from AFS: >> freebuild# ./my_mmap test4 >> elf_load_section: truncated ELF file >> Abort > This sounds very much as missed vnode_pager_setsize() calls. > VM tracks the file size as vnode vmobject size separately. > I think this was done for historical reasons, but also it > allows to not traverse the vop stack calling VOP_GETATTR each > time when size is needed. Yes, that looks to have done the trick -- thanks to Matt Benjamin for doing the legwork to find all the places it was needed. With that fix and a small locking patch, my buildworld now finishes. Thanks! -Ben From owner-freebsd-fs@FreeBSD.ORG Sun Aug 29 23:34:58 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC1EF106566C for ; Sun, 29 Aug 2010 23:34:58 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 87DFA8FC19 for ; Sun, 29 Aug 2010 23:34:58 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAPuLekyDaFvO/2dsb2JhbACDF54iqHiQfIEigyJzBIoJ X-IronPort-AV: E=Sophos;i="4.56,289,1280721600"; d="scan'208";a="90092542" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 29 Aug 2010 19:34:50 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id D41F1B3E95; Sun, 29 Aug 2010 19:34:50 -0400 (EDT) Date: Sun, 29 Aug 2010 19:34:50 -0400 (EDT) From: Rick Macklem To: Gleb Kurtsou Message-ID: <825702521.248882.1283124890775.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20100719074050.GA2640@tops> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: fix for remove for NFS through nullfs 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, 29 Aug 2010 23:34:58 -0000 > On (18/07/2010 22:40), Rick Macklem wrote: > > Mikolaj Golub submitted the attached patch that fixes a problem > > w.r.t. > > a nullfs mounted NFS mount point for remove. The problem is that, > > without this patch, NFS does not see that a file is still open > > (v_usecount > 1) when removed and removes it instead of silly > > renaming > > it. This patch increments the v_usecount of the lower level vnode > > during the remove call, so that silly rename works. kib@ has noted > > that this may be "racy" and result in silly rename happening when it > > isn't required but, imho, that is less of a problem than it never > > working. (I have tested it a bit for NFS and UFS and it seems to > > work for those file systems under a nullfs mount.) > > > > Why I am posting is that I am wondering if anyone knows of a file > > system type where this extra v_usecount on the vnode at the time of > > remove > > will/might cause problems? > It seems to be easily reproducible only with stacked filesystems. But > the problem is that v_usecount can be different from number of open > descriptors for the vnode, and it generally is. > > IMHO using v_usecount is racy for all filesystems. Grep for vref and > VREF, it's used all over the place. > > The issue was discussed some time ago already: > http://marc.info/?l=freebsd-hackers&m=125675165319186&w=4 > > I think the better solution would be to add a means of getting number > of > opened file descriptors, but not misuse v_usecount, e.g. the patch > looks > a pure hack for me. > > Thanks, > Gleb. > I tried keeping a count of "opens" in the NFS part of the vnode, but it doesn't work well. For example, mmap'd files do I/O after the VOP_CLOSE() { nfs_close() } call, so you can't decrement the count in nfs_close(). You can set bthe count back to 0 in nfs_inactive(), but VOP_INACTIVE() isn't always called, so it only happens sometimes. I grep'd the file systems and the only file systems other than the NFS clients that look at vrefcnt() in their VOP_REMOVE() calls are smbfs and nwfs and these 2 file systems only use vrefcnt() when the vnode is a directory. As such, if the increment of v_usecount is only done by nullfs in its VOP_REMOVE() for v_type == VREG, it seems that it will be ok. Discussions off-list seem to agree that the patch should go in, so I plan on committing it, although I agree that it is a hack. rick From owner-freebsd-fs@FreeBSD.ORG Mon Aug 30 11:06:56 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8436710656B5 for ; Mon, 30 Aug 2010 11:06:56 +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 592EE8FC2B for ; Mon, 30 Aug 2010 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o7UB6uCQ087422 for ; Mon, 30 Aug 2010 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o7UB6txF087420 for freebsd-fs@FreeBSD.org; Mon, 30 Aug 2010 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Aug 2010 11:06:55 GMT Message-Id: <201008301106.o7UB6txF087420@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, 30 Aug 2010 11:06:56 -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/149855 fs [gvinum] growfs causes fsck to report errors in Filesy o kern/149495 fs [zfs] chflags sappend on zfs not working right o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149022 fs [hang] File system operations hangs with suspfs state o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o bin/148296 fs [zfs] [loader] [patch] Very slow probe in /usr/src/sys o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/147292 fs [nfs] [patch] readahead missing in nfs client options o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server o kern/146375 fs [nfs] [patch] Typos in macro variables names in sys/fs s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o kern/145309 fs [disklabel] Editing disk label invalidates the whole d o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c o kern/144458 fs [nfs] [patch] nfsd fails as a kld p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o kern/143345 fs [ext2fs] [patch] extfs minor header cleanups to better o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142924 fs [ext2fs] [patch] Small cleanup for the inode struct in o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142401 fs [ntfs] [patch] Minor updates to NTFS from NetBSD o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs o bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/139363 fs [nfs] diskless root nfs mount from non FreeBSD server o kern/138790 fs [zfs] ZFS ceases caching when mem demand is high o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb f kern/137037 fs [zfs] [hang] zfs rollback on root causes FreeBSD to fr o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic o kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [panic] panic: ffs_truncate: read-only filesystem o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129059 fs [zfs] [patch] ZFS bootloader whitelistable via WITHOUT f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS p kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F f kern/119735 fs [zfs] geli + ZFS + samba starting on boot panics 7.0-B o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with 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] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/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 a docs/61716 fs [patch] newfs(8) code and manpage are out of sync o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 188 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 30 20:55:38 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B14A610656BA for ; Mon, 30 Aug 2010 20:55:38 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 43DA28FC0C for ; Mon, 30 Aug 2010 20:55:37 +0000 (UTC) Received: by eyx24 with SMTP id 24so3913809eyx.13 for ; Mon, 30 Aug 2010 13:55:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:user-agent:mime-version:content-type; bh=1ZNsjc1rliYZ4x4HrIFcRyvUhr8ZXqbdUYVtNUfAif4=; b=dM6DYofsTlmZenWL6GksLLyzUEmC5f7dbhJlyQ0QTBkoPfzXnQJ097kpMl12ctdgXW ROmMsPQleIf5ITLKZxBC7PJyCUCTuk6UAIIDqSyaUH5ocopikl93AchpvIgmPJrH9Ktw pXJ+wt2k9rTaDjykBimg4hbOyDSSZd890mcF4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:user-agent:mime-version :content-type; b=eIFfTgEV5wFxjsdQuAP1FzIAlptbzF8Y++nfSaGAJQqXjaBps1z3MPh6cFMWXBsBpv suC2i1pBGJyIT3qCtHmdAwD+AKA2HWbWPqTtVB29XIMNTUVrjwgaq9C+TR0os8MxSNWv WK241JLH0zD7wTpUNLQJQGOp1eD55O+ghKMrI= Received: by 10.213.98.84 with SMTP id p20mr118099ebn.59.1283200066208; Mon, 30 Aug 2010 13:27:46 -0700 (PDT) Received: from localhost ([95.69.170.24]) by mx.google.com with ESMTPS id z55sm12679177eeh.3.2010.08.30.13.27.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 30 Aug 2010 13:27:45 -0700 (PDT) From: Mikolaj Golub To: freebsd-fs@freebsd.org Date: Mon, 30 Aug 2010 23:27:42 +0300 Message-ID: <8639tv6e2p.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Subject: hastd: log the process id X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2010 20:55:38 -0000 --=-=-= Hi, Currently hastd does not log the process id with each message, although it might be useful in some cases. And it looks like most of our daemons do this. The patch below adds pid logging. Also it fixes wrong log message in secondary. -- Mikolaj Golub --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=hastd.patch Index: secondary.c =================================================================== --- secondary.c (revision 212008) +++ secondary.c (working copy) @@ -556,7 +556,7 @@ recv_thread(void *arg) if (hast_proto_recv_data(res, res->hr_remotein, hio->hio_nv, hio->hio_data, MAXPHYS) < 0) { secondary_exit(EX_TEMPFAIL, - "Unable to receive reply data"); + "Unable to receive request data"); } } pjdlog_debug(2, "recv: (%p) Moving request to the disk queue.", Index: pjdlog.c =================================================================== --- pjdlog.c (revision 212008) +++ pjdlog.c (working copy) @@ -57,6 +57,9 @@ pjdlog_mode_set(int mode) assert(mode == PJDLOG_MODE_STD || mode == PJDLOG_MODE_SYSLOG); pjdlog_mode = mode; + + if (mode == PJDLOG_MODE_SYSLOG) + openlog (NULL, LOG_PID, LOG_DAEMON); } /* --=-=-=-- From owner-freebsd-fs@FreeBSD.ORG Mon Aug 30 22:58:43 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B230510656B2 for ; Mon, 30 Aug 2010 22:58:43 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id 7774C8FC2E for ; Mon, 30 Aug 2010 22:58:43 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.4/8.14.4) with ESMTP id o7UMwgXh019526 for ; Tue, 31 Aug 2010 00:58:42 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.4/8.14.4/Submit) id o7UMwg4n019525 for freebsd-fs@freebsd.org; Mon, 30 Aug 2010 18:58:42 -0400 (EDT) (envelope-from cracauer) Date: Mon, 30 Aug 2010 18:58:42 -0400 From: Martin Cracauer To: freebsd-fs@freebsd.org Message-ID: <20100830225841.GA9363@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: fsync(2) and on-disk write-back cache 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, 30 Aug 2010 22:58:43 -0000 I always assumed the answer to this question is "of course": When doing an fsync (waiting for the commit), do we actually tell the disk to flush the on-disk write-back cache (if that is in use) to the platters? I just went down some code paths in both FreeBSD and Linux and in both cases the paths for fsync quickly disappear in the generic block-by-block flushing code that is also used for regular (non-fsync) flushing. I didn't see anything aware of the on-disk cache. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 10:08:30 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8546A10656A4 for ; Tue, 31 Aug 2010 10:08:30 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 15B098FC0A for ; Tue, 31 Aug 2010 10:08:29 +0000 (UTC) Received: by fxm4 with SMTP id 4so4422949fxm.13 for ; Tue, 31 Aug 2010 03:08:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:reply-to:x-mailer:mime-version :content-type:content-transfer-encoding; bh=TJUXauNGbOByVh7o0kpLzcqsg+MLEAKbCPOjRkwSFHA=; b=qMwxOT8HCWL0BYtWJBNnkzrBV4yIQJmI3NIk29dC7e4NCbCr3IdZD0rJDjypD6t9q3 lCfpg1TBtnKAqRpNGS5n+grWuQNx0pf4sBcUaes7wWU5Z90D9yfQVuJcAhDhhs63Jyyg 8O2/nIFXdY2vo9VvLKHwJlHWsn0LAOefIgF78= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=gwj8bNcb9BvcuPPvC0q18snzcWeuAR6LVj06/ST8/OGcvNux+I7v7rj00rwCrLAZTd q+YEGHqOMLjurU4TqN4G4sIv2nIYe+6UYWwcfOOFuKXslIRct8dR1ZkOp6rdSvVrdEbA MnJyDgARDBbNo1zbxjRv/X17KiQRIOX5tIsug= Received: by 10.223.108.81 with SMTP id e17mr5118185fap.28.1283247533629; Tue, 31 Aug 2010 02:38:53 -0700 (PDT) Received: from ernst.jennejohn.org (p578E3809.dip.t-dialin.net [87.142.56.9]) by mx.google.com with ESMTPS id 14sm3855139fav.2.2010.08.31.02.38.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 31 Aug 2010 02:38:52 -0700 (PDT) Date: Tue, 31 Aug 2010 11:38:51 +0200 From: Gary Jennejohn To: Martin Cracauer Message-ID: <20100831113851.6d449628@ernst.jennejohn.org> In-Reply-To: <20100830225841.GA9363@cons.org> References: <20100830225841.GA9363@cons.org> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: fsync(2) and on-disk write-back cache X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2010 10:08:30 -0000 On Mon, 30 Aug 2010 18:58:42 -0400 Martin Cracauer wrote: > I always assumed the answer to this question is "of course": > > When doing an fsync (waiting for the commit), do we actually tell the > disk to flush the on-disk write-back cache (if that is in use) to the > platters? > > I just went down some code paths in both FreeBSD and Linux and in both > cases the paths for fsync quickly disappear in the generic > block-by-block flushing code that is also used for regular (non-fsync) > flushing. I didn't see anything aware of the on-disk cache. > I may be wrong, but it seems to me that the actual cache flush on the disk is handled at a very low level - in the drivers. At least I'm pretty certain that e.g. the ahci code sends flush commands to the disks. -- Gary Jennejohn From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 12:05:41 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FD9310656AE for ; Tue, 31 Aug 2010 12:05:41 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id E281E8FC15 for ; Tue, 31 Aug 2010 12:05:40 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 51A2045E5C; Tue, 31 Aug 2010 14:05:39 +0200 (CEST) Received: from localhost (pdawidek.whl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 6BDCC45B36; Tue, 31 Aug 2010 14:05:34 +0200 (CEST) Date: Tue, 31 Aug 2010 14:05:26 +0200 From: Pawel Jakub Dawidek To: Mikolaj Golub Message-ID: <20100831120526.GF1795@garage.freebsd.pl> References: <8639tv6e2p.fsf@kopusha.home.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Cgrdyab2wu3Akvjd" Content-Disposition: inline In-Reply-To: <8639tv6e2p.fsf@kopusha.home.net> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=4.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: hastd: log the process id X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2010 12:05:41 -0000 --Cgrdyab2wu3Akvjd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 30, 2010 at 11:27:42PM +0300, Mikolaj Golub wrote: > Hi, >=20 > Currently hastd does not log the process id with each message, although it > might be useful in some cases. And it looks like most of our daemons do t= his. >=20 > The patch below adds pid logging. Also it fixes wrong log message in > secondary. I like the patch. It is committed now. Thanks! --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Cgrdyab2wu3Akvjd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkx88AUACgkQForvXbEpPzTThQCgn2rqcVmcP5wzn7bgklmUsEz0 atcAnArkFlnQK19s/MgzBHSazm1Qo/ZQ =JXth -----END PGP SIGNATURE----- --Cgrdyab2wu3Akvjd-- From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 12:00:00 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4A0C1065698 for ; Tue, 31 Aug 2010 12:00:00 +0000 (UTC) (envelope-from k0802647@telus.net) Received: from defout.telus.net (outbound04.telus.net [199.185.220.223]) by mx1.freebsd.org (Postfix) with ESMTP id 9193F8FC13 for ; Tue, 31 Aug 2010 12:00:00 +0000 (UTC) Received: from edtnaa02.telusplanet.net ([66.183.53.162]) by priv-edtnes24.telusplanet.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20100831110906.ZHEE6754.priv-edtnes24.telusplanet.net@edtnaa02.telusplanet.net> for ; Tue, 31 Aug 2010 05:09:06 -0600 Received: from oliver.bc.lan (d66-183-53-162.bchsia.telus.net [66.183.53.162]) by edtnaa02.telusplanet.net (BorderWare Security Platform) with ESMTP id 61E791E2A3BCDCF2 for ; Tue, 31 Aug 2010 05:09:05 -0600 (MDT) Received: from [10.111.111.112] (unknown [10.111.111.112]) by oliver.bc.lan (Postfix) with ESMTP id 493666455; Tue, 31 Aug 2010 04:09:05 -0700 (PDT) Message-ID: <4C7CE2D0.40400@telus.net> Date: Tue, 31 Aug 2010 04:09:04 -0700 From: Carl User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.7) Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Cloudmark-Analysis: v=1.1 cv=SJIhyCEJBCHyullCFvS0mIdE5QsJS0d45teFqlr0wtg= c=1 sm=0 a=SHg4dW30_F4A:10 a=8nJEP1OIZ-IA:10 a=HNgjH8kF64GtJ7EcXKEMsQ==:17 a=_N190bLxhghOylsEThsA:9 a=JMHaxkYw0aMDhDWIOe2RIzOVwJEA:4 a=wPNLvfGTeEIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 X-Mailman-Approved-At: Tue, 31 Aug 2010 12:11:16 +0000 Subject: gjournal alignment on 4K sector advanced format 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, 31 Aug 2010 12:00:00 -0000 My understanding is that I can avoid misalignment-induced performance problems with Western Digital WDxxEARS drives (4KiB physical sector size) by ensuring two things: 1. GPT partitions are aligned to 4KiB boundaries, and 2. Use "newfs -b 32768 -f 4096 ..." so that UFS2 fragments are not smaller than the physical sector size. True? Now I want to add gjournal to some of my partitions. It seems to me that I must also ensure the journal is aligned just as I've done with the data. So far, though, I have found no information as to how the journal's own filesystem layout works. Does it use fixed size blocks/fragments like the UFS2 data does? If so, what is its minimum addressable unit size? If it is smaller than 4KiB, we get journal misalignment and a performance loss, right? What must I do to ensure the journal is fully aligned? In the past I've put the data and journal on the same provider, but I am unsure whether a specified size for the journal is accurately observed. If I specify a 1GiB journal, will I get exactly that? My concern is whether an added/subtracted sector might be used for some kind of journal header, thereby throwing off the alignment of the journal again. Is it better to put the journal on its own provider (ie. separate partition) to aid alignment in some way? What are the pros and cons for shared vs. separate providers in general? Carl / K0802647 From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 12:19:51 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE04610656BC for ; Tue, 31 Aug 2010 12:19:51 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 945368FC31 for ; Tue, 31 Aug 2010 12:19:51 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OqPob-00058v-QQ for freebsd-fs@freebsd.org; Tue, 31 Aug 2010 14:19:49 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 Aug 2010 14:19:49 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 Aug 2010 14:19:49 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Tue, 31 Aug 2010 14:19:41 +0200 Lines: 18 Message-ID: References: <4C7CE2D0.40400@telus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100518 Thunderbird/3.0.4 In-Reply-To: <4C7CE2D0.40400@telus.net> X-Enigmail-Version: 1.0.1 Subject: Re: gjournal alignment on 4K sector advanced format 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, 31 Aug 2010 12:19:52 -0000 On 08/31/10 13:09, Carl wrote: > > Now I want to add gjournal to some of my partitions. It seems to me that > I must also ensure the journal is aligned just as I've done with the > data. So far, though, I have found no information as to how the > journal's own filesystem layout works. Does it use fixed size > blocks/fragments like the UFS2 data does? If so, what is its minimum > addressable unit size? If it is smaller than 4KiB, we get journal > misalignment and a performance loss, right? What must I do to ensure the > journal is fully aligned? gjournal writes its metadata throughout the journal in sector sizes (512 bytes) so it cannot be aligned in this way. For this you need a solution which will actually change the sector size, like gnop or my glabel patch. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 14:09:11 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D13C210656B0 for ; Tue, 31 Aug 2010 14:09:11 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 9E38F8FC29 for ; Tue, 31 Aug 2010 14:09:11 +0000 (UTC) Received: from [192.168.1.2] (m206-63.dsl.tsoft.com [198.144.206.63]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o7VE9AFP022983 for ; Tue, 31 Aug 2010 07:09:10 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4C7D0D01.7000009@feral.com> Date: Tue, 31 Aug 2010 07:09:05 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20100830225841.GA9363@cons.org> <20100831113851.6d449628@ernst.jennejohn.org> In-Reply-To: <20100831113851.6d449628@ernst.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.67.166.1]); Tue, 31 Aug 2010 07:09:10 -0700 (PDT) Subject: Re: fsync(2) and on-disk write-back cache 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, 31 Aug 2010 14:09:11 -0000 On FreeBSD, BIO_FLUSH is used to communicate between the filesystem./buffer cache's desire to flush out and the low level cache. > I may be wrong, but it seems to me that the actual cache flush on the > disk is handled at a very low level - in the drivers. > > At least I'm pretty certain that e.g. the ahci code sends flush commands > to the disks. > > -- > Gary Jennejohn > _______________________________________________ > 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 Aug 31 14:21:46 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C65B01065679 for ; Tue, 31 Aug 2010 14:21:46 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id 890E48FC0A for ; Tue, 31 Aug 2010 14:21:46 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.4/8.14.4) with ESMTP id o7VELjNY030391; Tue, 31 Aug 2010 16:21:45 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.4/8.14.4/Submit) id o7VELjVt030390; Tue, 31 Aug 2010 10:21:45 -0400 (EDT) (envelope-from cracauer) Date: Tue, 31 Aug 2010 10:21:45 -0400 From: Martin Cracauer To: Gary Jennejohn Message-ID: <20100831142144.GA26989@cons.org> References: <20100830225841.GA9363@cons.org> <20100831113851.6d449628@ernst.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100831113851.6d449628@ernst.jennejohn.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, Martin Cracauer Subject: Re: fsync(2) and on-disk write-back cache 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, 31 Aug 2010 14:21:46 -0000 Gary Jennejohn wrote on Tue, Aug 31, 2010 at 11:38:51AM +0200: > On Mon, 30 Aug 2010 18:58:42 -0400 > Martin Cracauer wrote: > > > I always assumed the answer to this question is "of course": > > > > When doing an fsync (waiting for the commit), do we actually tell the > > disk to flush the on-disk write-back cache (if that is in use) to the > > platters? > > > > I just went down some code paths in both FreeBSD and Linux and in both > > cases the paths for fsync quickly disappear in the generic > > block-by-block flushing code that is also used for regular (non-fsync) > > flushing. I didn't see anything aware of the on-disk cache. > > > > I may be wrong, but it seems to me that the actual cache flush on the > disk is handled at a very low level - in the drivers. > > At least I'm pretty certain that e.g. the ahci code sends flush commands > to the disks. But does it wait for confirmation of completion? >From what I have seen in the code, the path for fsync(2) quickly merges with the code paths for regular flush (e.g. buffer full enough). fsync does wait for the underlying flush of the blocks in question, but that doesn't tell me whether that waits for the disk to confirm "on platter". So either all code paths wait for the data to be on platter or none. I can't think that all code waits for completion, because then the disk write performance would be the same with cache on write-through (reads only) and write-back. Unless the code flushes larger chunks between AHCI flush commands. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 16:08:43 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53AEB10656AB for ; Tue, 31 Aug 2010 16:08:43 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by mx1.freebsd.org (Postfix) with ESMTP id 020788FC27 for ; Tue, 31 Aug 2010 16:08:42 +0000 (UTC) Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta14.westchester.pa.mail.comcast.net with comcast id 10r61f0071vXlb85E48jJi; Tue, 31 Aug 2010 16:08:43 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta17.westchester.pa.mail.comcast.net with comcast id 148h1f00M3LrwQ23d48i80; Tue, 31 Aug 2010 16:08:43 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 992219B425; Tue, 31 Aug 2010 09:08:40 -0700 (PDT) Date: Tue, 31 Aug 2010 09:08:40 -0700 From: Jeremy Chadwick To: Martin Cracauer Message-ID: <20100831160840.GA74125@icarus.home.lan> References: <20100830225841.GA9363@cons.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100830225841.GA9363@cons.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: fsync(2) and on-disk write-back cache 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, 31 Aug 2010 16:08:43 -0000 On Mon, Aug 30, 2010 at 06:58:42PM -0400, Martin Cracauer wrote: > I always assumed the answer to this question is "of course": > > When doing an fsync (waiting for the commit), do we actually tell the > disk to flush the on-disk write-back cache (if that is in use) to the > platters? > > I just went down some code paths in both FreeBSD and Linux and in both > cases the paths for fsync quickly disappear in the generic > block-by-block flushing code that is also used for regular (non-fsync) > flushing. I didn't see anything aware of the on-disk cache. I don't have an authoritative answer to your question, but this thread seems to imply there's a relation between fsync() and an intentional disk flush (BIO_FLUSH). I'm sure when BIO_FLUSH is called depends on the filesystem as well. Funny timing this topic, given a post over in -stable: http://lists.freebsd.org/pipermail/freebsd-stable/2010-August/058525.html -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 16:12:09 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF1F310656A4 for ; Tue, 31 Aug 2010 16:12:09 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-1.mit.edu (DMZ-MAILSEC-SCANNER-1.MIT.EDU [18.9.25.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9A8B58FC16 for ; Tue, 31 Aug 2010 16:12:09 +0000 (UTC) X-AuditID: 1209190c-b7c9cae00000753f-5c-4c7d29d89ff0 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-1.mit.edu (Symantec Brightmail Gateway) with SMTP id 9B.62.30015.8D92D7C4; Tue, 31 Aug 2010 12:12:08 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id o7VGC7MG016926; Tue, 31 Aug 2010 12:12:08 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o7VGC53g001583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 31 Aug 2010 12:12:06 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id o7VGC435001834; Tue, 31 Aug 2010 12:12:04 -0400 (EDT) Date: Tue, 31 Aug 2010 12:12:04 -0400 (EDT) From: Benjamin Kaduk To: Martin Cracauer In-Reply-To: <20100831160840.GA74125@icarus.home.lan> Message-ID: References: <20100830225841.GA9363@cons.org> <20100831160840.GA74125@icarus.home.lan> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: AAAAARXFYDA= Cc: freebsd-fs@freebsd.org Subject: Re: fsync(2) and on-disk write-back cache 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, 31 Aug 2010 16:12:10 -0000 On Tue, 31 Aug 2010, Jeremy Chadwick wrote: > On Mon, Aug 30, 2010 at 06:58:42PM -0400, Martin Cracauer wrote: >> I always assumed the answer to this question is "of course": >> >> When doing an fsync (waiting for the commit), do we actually tell the >> disk to flush the on-disk write-back cache (if that is in use) to the >> platters? >> >> I just went down some code paths in both FreeBSD and Linux and in both >> cases the paths for fsync quickly disappear in the generic >> block-by-block flushing code that is also used for regular (non-fsync) >> flushing. I didn't see anything aware of the on-disk cache. > > I don't have an authoritative answer to your question, but this thread > seems to imply there's a relation between fsync() and an intentional > disk flush (BIO_FLUSH). I'm sure when BIO_FLUSH is called depends on > the filesystem as well. It is probably also worth noting that disks have been known to lie about having actually flushed bits from their internal cache to the platter. -Ben Kaduk From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 21:59:43 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF7FB10656B2; Tue, 31 Aug 2010 21:59:43 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id F2CD58FC14; Tue, 31 Aug 2010 21:59:31 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4006745DD8; Tue, 31 Aug 2010 23:59:30 +0200 (CEST) Received: from localhost (chello089077043238.chello.pl [89.77.43.238]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 61EF845B36; Tue, 31 Aug 2010 23:59:24 +0200 (CEST) Date: Tue, 31 Aug 2010 23:59:15 +0200 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20100831215915.GE1932@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RpqchZ26BWispMcB" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-current@FreeBSD.org Subject: ZFS v28 is ready for wider testing. 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, 31 Aug 2010 21:59:44 -0000 --RpqchZ26BWispMcB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b none swap sw 0 0 Add the following line to /etc/rc.conf: ddb_enable=3D"YES" Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb> run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Good luck! >:> --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --RpqchZ26BWispMcB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkx9ezMACgkQForvXbEpPzQ+ZwCg6EtfJjx6X1nJaj5uTkEM2fwx HkoAoJ5/L97SHbIHcyLrOqmH/t4oBmFi =ePEI -----END PGP SIGNATURE----- --RpqchZ26BWispMcB-- From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 22:40:29 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E04B1065673; Tue, 31 Aug 2010 22:40:29 +0000 (UTC) (envelope-from mattjreimer@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0ED1A8FC0C; Tue, 31 Aug 2010 22:40:28 +0000 (UTC) Received: by vws7 with SMTP id 7so6907781vws.13 for ; Tue, 31 Aug 2010 15:40:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ki0tc+dAY8p1oWfXMsIqOcddraNldGDHrUljVznLpFk=; b=ckRuQlVoY7Wd/FH7ss+FSjX9Ywam3QRCzotfExuwB32IbW1ExP5hVCLkGg4vuRKQBD i1myiYfMzPR4VCwuYWMcRgqzxbypmBcOTr1WBPxkIgZ1gIrYvU+ZC20CtDdJRRL58Y51 3MmSVmZVe3CyIjiOWu4U9oETiWaZrlJ+m5Mqg= 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=P5z7WxWEi/XK+AuRB/sMl9MdW0gpWsjHd7ZQ2U42Mt6mpB6x1/XVujHcVg9+IvdM4F ssu2YMoQ8FA/M53dKsNJTPSbgEzf+pvK0iEjfFCiOYqETNAlsh5govwo5VBw1OwHtgMb F87Wc03p67S57JVKIxbj0BuI3lCHaMAtnjI+Q= MIME-Version: 1.0 Received: by 10.220.158.11 with SMTP id d11mr3381071vcx.231.1283292694935; Tue, 31 Aug 2010 15:11:34 -0700 (PDT) Received: by 10.220.177.1 with HTTP; Tue, 31 Aug 2010 15:11:34 -0700 (PDT) In-Reply-To: <20100831215915.GE1932@garage.freebsd.pl> References: <20100831215915.GE1932@garage.freebsd.pl> Date: Tue, 31 Aug 2010 15:11:34 -0700 Message-ID: From: Matt Reimer To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. 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, 31 Aug 2010 22:40:29 -0000 On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek wrote: > Hello. > > I'd like to give you ZFS v28 for testing. If you are neither brave nor > mad, you can stop here. Woohoo! Thanks for all your hard work on this! Matt From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 23:07:31 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16FE110656A3 for ; Tue, 31 Aug 2010 23:07:31 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id CC23A8FC15 for ; Tue, 31 Aug 2010 23:07:30 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.4/8.14.4) with ESMTP id o7VN7Tkg040888; Wed, 1 Sep 2010 01:07:29 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.4/8.14.4/Submit) id o7VN7S0W040565; Tue, 31 Aug 2010 19:07:28 -0400 (EDT) (envelope-from cracauer) Date: Tue, 31 Aug 2010 19:07:28 -0400 From: Martin Cracauer To: Benjamin Kaduk Message-ID: <20100831230728.GA36384@cons.org> References: <20100830225841.GA9363@cons.org> <20100831160840.GA74125@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, Martin Cracauer Subject: Re: fsync(2) and on-disk write-back cache 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, 31 Aug 2010 23:07:31 -0000 Benjamin Kaduk wrote on Tue, Aug 31, 2010 at 12:12:04PM -0400: > On Tue, 31 Aug 2010, Jeremy Chadwick wrote: > > >On Mon, Aug 30, 2010 at 06:58:42PM -0400, Martin Cracauer wrote: > >>I always assumed the answer to this question is "of course": > >> > >>When doing an fsync (waiting for the commit), do we actually tell the > >>disk to flush the on-disk write-back cache (if that is in use) to the > >>platters? > >> > >>I just went down some code paths in both FreeBSD and Linux and in both > >>cases the paths for fsync quickly disappear in the generic > >>block-by-block flushing code that is also used for regular (non-fsync) > >>flushing. I didn't see anything aware of the on-disk cache. > > > >I don't have an authoritative answer to your question, but this thread > >seems to imply there's a relation between fsync() and an intentional > >disk flush (BIO_FLUSH). I'm sure when BIO_FLUSH is called depends on > >the filesystem as well. I just went the for-dummies way and annotated all relevant BIO_FLUSH places with debug print statements. They don't seem to be called when doing an fsync on a file in a local filesystem. ufs (no softupdates) -> old-style SCSI disk. I'll snoop around some more, try it on ZFS/SATA and do some timing tests. > It is probably also worth noting that disks have been known to lie about > having actually flushed bits from their internal cache to the platter. I know, that's why the whole question is a little academic. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-fs@FreeBSD.ORG Tue Aug 31 23:10:47 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 800161065670; Tue, 31 Aug 2010 23:10:47 +0000 (UTC) (envelope-from jasonjwwilliams@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id E36328FC14; Tue, 31 Aug 2010 23:10:46 +0000 (UTC) Received: by wyb33 with SMTP id 33so9897313wyb.13 for ; Tue, 31 Aug 2010 16:10:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=g4T5tDjkzj9MxqK0+q8JD1j48l7mrZJ+L8HhNJKQS3c=; b=rOIb3qkB7bzGGDrSF7oezmUOi0bx2HUHqkBOifZ/n3/Oukch+cLcGxjpg0SX+oOdZ+ i4VjPCw09XguqDI3JP0cTWYcmZHDTNfaOwXzJRLBrmdW1j5U4oUasZ0IJDWZXDWWqVok 11WY1r8s7LudQi7Y9jHIvwgYR0CipUBe1AF2c= 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=ioiHjKHqH6IoXxFKzBfJT777EHPBQNOH1deHOQPmGICfq+VBJH4LaprKzNHTe7sthf PZZ0izOqY9UKe0nFFzXC1DzarbcM3uQEU/91YA0ZPLIHh0M+J+Ol+NbEJFnLlct8Q6MN xeritLmsv7Nt0i4+w8J86oheQIIyirsCUjhYQ= MIME-Version: 1.0 Received: by 10.216.50.73 with SMTP id y51mr6985026web.85.1283294611016; Tue, 31 Aug 2010 15:43:31 -0700 (PDT) Received: by 10.216.135.39 with HTTP; Tue, 31 Aug 2010 15:43:30 -0700 (PDT) In-Reply-To: <20100831215915.GE1932@garage.freebsd.pl> References: <20100831215915.GE1932@garage.freebsd.pl> Date: Tue, 31 Aug 2010 16:43:30 -0600 Message-ID: From: "Jason J. W. Williams" To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. 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, 31 Aug 2010 23:10:47 -0000 This is awesome. Thank you! -J On Tue, Aug 31, 2010 at 3:59 PM, Pawel Jakub Dawidek wrot= e: > Hello. > > I'd like to give you ZFS v28 for testing. If you are neither brave nor > mad, you can stop here. > > The patchset is very experimental. It can eat your cookie and hurt your > teddy bear, so be warned. Don't try it for anything except testing. > > This patchset is also a message we, as the FreeBSD project, would like > to send to our users: Eventhough OpenSolaris is dead, the ZFS file > system is going to stay in FreeBSD. At this point we have quite a few > developers involved in ZFS on FreeBSD as well as serveral companies. > We are also looking forward to work with IllumOS. > > So, what this new ZFS brings? > > - Data deduplication. Read more here: > > =A0 =A0 =A0 =A0http://blogs.sun.com/bonwick/entry/zfs_dedup > > - Triple parity RAIDZ (RAIDZ3). Read more here: > > =A0 =A0 =A0 =A0http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-= z/ > > - zfs diff. Read more here: > > =A0 =A0 =A0 =A0http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328= _tim.haley > > - zpool split. Read more here: > > =A0 =A0 =A0 =A0http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924= _mark.musante > > - Snapshot holds. Read more here: > > =A0 =A0 =A0 =A0http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511= _chris.kirby > > - zpool import -F. Allows to rewind corrupted pool to earlier > =A0transaction group. > > - Possibility to import pool in read-only mode. > > And much, much more, including plenty of preformance improvements and bug > fixes. > > So test whatever you can and report back. Look for regressions, strange > behaviour, missing features, deadlocks, livelocks, preformance > degradation, etc. > > The boot code is not updated at all, so booting off of ZFS doesn't > currently work. > > The patch is against today's FreeBSD HEAD. > > The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, > please don't turn it off. Also, compile your kernel with the following > options: > > =A0 =A0 =A0 =A0options =A0 =A0 =A0 =A0 KDB > =A0 =A0 =A0 =A0options =A0 =A0 =A0 =A0 DDB > =A0 =A0 =A0 =A0options =A0 =A0 =A0 =A0 INVARIANTS > =A0 =A0 =A0 =A0options =A0 =A0 =A0 =A0 INVARIANT_SUPPORT > =A0 =A0 =A0 =A0options =A0 =A0 =A0 =A0 WITNESS > =A0 =A0 =A0 =A0options =A0 =A0 =A0 =A0 WITNESS_SKIPSPIN > =A0 =A0 =A0 =A0options =A0 =A0 =A0 =A0 DEBUG_LOCKS > =A0 =A0 =A0 =A0options =A0 =A0 =A0 =A0 DEBUG_VFS_LOCKS > > Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will > be plenty of those, and you'll desperately want to report them, but pleas= e > don't. > > The best way to report a problem is to answer to this e-mail with as shor= t > as possible procedure of how to reproduce it and debugging info. I'd > prefer textdump if possible. Below you can find quick procedure how to > setup textdumps: > > =A0 =A0 =A0 =A0Choose spare/swap disk/partition in your system, let's say= it is > =A0 =A0 =A0 =A0/dev/ad0s1b. > > =A0 =A0 =A0 =A0Add the following line to /etc/fstab: > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/dev/ad0s1b =A0 =A0 none =A0 =A0swap =A0 = =A0sw =A0 =A0 =A00 =A0 =A0 =A0 0 > > =A0 =A0 =A0 =A0Add the following line to /etc/rc.conf: > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0ddb_enable=3D"YES" > > =A0 =A0 =A0 =A0Run the following commands: > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# /etc/rc.d/swap1 start > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# /etc/rc.d/dumpon start > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# /etc/rc.d/ddb start > > =A0 =A0 =A0 =A0This will setup swap, mark it as dump device and setup som= e DDB > =A0 =A0 =A0 =A0scripts. Or you can just reboot. > > =A0 =A0 =A0 =A0Now when your system panic or deadlock, enter DDB and call= the > =A0 =A0 =A0 =A0following command: > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0ddb> run kdb.enter.panic > > =A0 =A0 =A0 =A0It will execute all the commands I need, dump them in text= format to > =A0 =A0 =A0 =A0your swap device and reboot machine. > > =A0 =A0 =A0 =A0After the reboot, you should find textdump.tar.0 file in /= var/crash/ > =A0 =A0 =A0 =A0directory. This is the debug info I need. > > End of textdumps procedure. > > Ok, now that I know you read everything carefully, here is the patch: > > =A0 =A0 =A0 =A0http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.= bz2 > > Good luck! >:> > > -- > Pawel Jakub Dawidek =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://ww= w.wheelsystems.com > pjd@FreeBSD.org =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http:= //www.FreeBSD.org > FreeBSD committer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Am I Ev= il? Yes, I Am! > From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 00:19:03 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B71810656A5 for ; Wed, 1 Sep 2010 00:19:03 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mailgw.dannysplace.net (mailgw.dannysplace.net [204.109.56.184]) by mx1.freebsd.org (Postfix) with ESMTP id 0A8A38FC0A for ; Wed, 1 Sep 2010 00:19:02 +0000 (UTC) Received: from [203.206.171.212] (helo=[192.168.10.10]) by mailgw.dannysplace.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1Oqb2j-000KT1-Uh for freebsd-fs@freebsd.org; Wed, 01 Sep 2010 10:19:11 +1000 Message-ID: <4C7D9BF1.9010102@dannysplace.net> Date: Wed, 01 Sep 2010 10:18:57 +1000 From: Danny Carroll User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-fs Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Exim-Version: 4.72 (build at 12-Jul-2010 18:31:29) X-Date: 2010-09-01 10:19:10 X-Connected-IP: 203.206.171.212:58434 X-Message-Linecount: 88 X-Body-Linecount: 77 X-Message-Size: 3253 X-Body-Size: 2778 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on damka.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailgw.dannysplace.net) Subject: How is data written to a pool with multiple VDevs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2010 00:19:03 -0000 Hello All, I'm in the process of upgrading my home file server and at the same time I'm going to reorganise the pool. Currently it looks like this: nas# zpool status pool: areca state: ONLINE scrub: scrub completed after 12h59m with 0 errors on Sun Aug 29 16:09:09 2010 config: NAME STATE READ WRITE CKSUM areca ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 da6 ONLINE 0 0 0 da7 ONLINE 0 0 0 da8 ONLINE 0 0 0 da9 ONLINE 0 0 0 da10 ONLINE 0 0 0 da11 ONLINE 0 0 0 When I am done I will be using larger drives and I want it to look like this (I did not know about the 6 drive per vdev recommendation when I created the array originally): nas# zpool status pool: areca state: ONLINE scrub: scrub completed after 12h59m with 0 errors on Sun Aug 29 16:09:09 2010 config: NAME STATE READ WRITE CKSUM areca ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da6 ONLINE 0 0 0 da7 ONLINE 0 0 0 da8 ONLINE 0 0 0 da9 ONLINE 0 0 0 da10 ONLINE 0 0 0 da11 ONLINE 0 0 0 I plan to do the migration in 2 steps. 1. Put 6 of the new drives into a spare machine I have and create a 6 disk raidz array. 2. Copy the data accross. 3. Import those 6 drives into the old server and add the remaining 6 to the pool in a second raidz vdev. I believe that data is striped accross the 2 vdevs much like a raid0 array stripes across 2 drives. My question is: Since the data will initially be on only one of the raidz vdevs, when I add the second one, will ZFS re-organise the data on the whole pool to be efficient or will I end up with only new data being striped. If that is the case then I will try and find a way to build the new array fully on a temporary machine first before copying the data. -D From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 01:20:10 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A030A10656C2 for ; Wed, 1 Sep 2010 01:20:10 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4FD478FC15 for ; Wed, 1 Sep 2010 01:20:09 +0000 (UTC) Received: by vws7 with SMTP id 7so7052772vws.13 for ; Tue, 31 Aug 2010 18:20:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=C75rNDr+pyZ1zaK/HLsEkKEA4A+FviQd7T/lk9QGdL4=; b=VwJcI2YoaQ0KHqg5ywycgCCSQJsSHT5GSeMKh7yvPDppEXSXUs3Xv246w1qxOXYZTT C6ObbjWa26yqVqbw0iRQ8FuOgaVkstWg3ww2tqXKbQhiZ4I+QN4dWktt2W9AYqSVkNKr cl6ZfBMl7/buu9QiayJRXVmtUmOYbFQOWUjws= 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=d0VsnC3q1JfiDPSLVcy5F9yGleeZ6BTXr/0IX2p6JChMdCeHMqw6Q11Dk2iPlYr5Ev 7e9YJpA4OCTANdoOfK/oPHgaeOttmUcA5GTaHkLvcy8Lfx+DQch6OSoV4tW7X4x+roiW Wfgc1TXE/fAqeReZ8LPv0qcaQPW7bp3RPM/Xo= MIME-Version: 1.0 Received: by 10.220.162.148 with SMTP id v20mr4745353vcx.36.1283304009372; Tue, 31 Aug 2010 18:20:09 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.220.66.227 with HTTP; Tue, 31 Aug 2010 18:20:09 -0700 (PDT) In-Reply-To: <4C7D9BF1.9010102@dannysplace.net> References: <4C7D9BF1.9010102@dannysplace.net> Date: Tue, 31 Aug 2010 18:20:09 -0700 X-Google-Sender-Auth: JxvwZc-Xr424VlCTt_0gWfoXHjY Message-ID: From: Artem Belevich To: fbsd@dannysplace.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs Subject: Re: How is data written to a pool with multiple VDevs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2010 01:20:10 -0000 On Tue, Aug 31, 2010 at 5:18 PM, Danny Carroll wrote= : ... > My question is: =A0Since the data will initially be on only one of the > raidz vdevs, when I add the second one, will ZFS re-organise the data on > the whole pool to be efficient or will I end up with only new data being > striped. No, I believe ZFS will not reorganize the data that's already written. However, ZFS will make an attempt to spread the data across both vdev once both are available. > If that is the case then I will try and find a way to build the new > array fully on a temporary machine first before copying the data. I guess once you've added second vdev and provided that you have enough space left, you can try copying your dataset once again. New copy will be spread across both vdevs. --Artem From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 04:09:36 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54D0C10656A6; Wed, 1 Sep 2010 04:09:36 +0000 (UTC) (envelope-from schumi.han@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0A89B8FC0C; Wed, 1 Sep 2010 04:09:35 +0000 (UTC) Received: by iwn34 with SMTP id 34so555713iwn.13 for ; Tue, 31 Aug 2010 21:09:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=mWGF3sHJfj6WvMwxl2erp3boWiUdxTX2I9Ib7C0Hcys=; b=nxyk+kCNiGsJeGQXEw/VFmRS57ugPKR10zPTvVRPsqcQTp90rtojJPJZM/iP188847 DJX3lG79ZvYraz7mVGO4gsT7qg/Zz8axzw7uhPCsG5XeP1yVGXNglblid7mMVbDWRajU zdHaRXcSdnVreAW23bZs38a8ahc47DA55dOSQ= 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=drlgkXLkNOTvymAkegCAG3IOkm4i0XgLWQzQWPv4y9c6VMSt+iDPPMyc7UqK103b8t /8RWxsvvJ8nIDzQ+CFCHcMjR6SH9QbWWJQLktpjZMtmP8a+NEpgB0sPgjtjDUpStlmmG MIrP+ZyJj4t1CzpaYwYy3eODyz74fWKy2uHhY= MIME-Version: 1.0 Received: by 10.231.12.136 with SMTP id x8mr233778ibx.55.1283314175216; Tue, 31 Aug 2010 21:09:35 -0700 (PDT) Received: by 10.231.191.73 with HTTP; Tue, 31 Aug 2010 21:09:35 -0700 (PDT) In-Reply-To: <20100831215915.GE1932@garage.freebsd.pl> References: <20100831215915.GE1932@garage.freebsd.pl> Date: Wed, 1 Sep 2010 12:09:35 +0800 Message-ID: From: Zhu Han To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. 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, 01 Sep 2010 04:09:36 -0000 That's cool. Thank you for your work on it. best regards, hanzhu On Wed, Sep 1, 2010 at 5:59 AM, Pawel Jakub Dawidek wrote: > Hello. > > I'd like to give you ZFS v28 for testing. If you are neither brave nor > mad, you can stop here. > > The patchset is very experimental. It can eat your cookie and hurt your > teddy bear, so be warned. Don't try it for anything except testing. > > This patchset is also a message we, as the FreeBSD project, would like > to send to our users: Eventhough OpenSolaris is dead, the ZFS file > system is going to stay in FreeBSD. At this point we have quite a few > developers involved in ZFS on FreeBSD as well as serveral companies. > We are also looking forward to work with IllumOS. > > So, what this new ZFS brings? > > - Data deduplication. Read more here: > > http://blogs.sun.com/bonwick/entry/zfs_dedup > > - Triple parity RAIDZ (RAIDZ3). Read more here: > > http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ > > - zfs diff. Read more here: > > > http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley > > - zpool split. Read more here: > > > http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante > > - Snapshot holds. Read more here: > > > http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby > > - zpool import -F. Allows to rewind corrupted pool to earlier > transaction group. > > - Possibility to import pool in read-only mode. > > And much, much more, including plenty of preformance improvements and bug > fixes. > > So test whatever you can and report back. Look for regressions, strange > behaviour, missing features, deadlocks, livelocks, preformance > degradation, etc. > > The boot code is not updated at all, so booting off of ZFS doesn't > currently work. > > The patch is against today's FreeBSD HEAD. > > The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, > please don't turn it off. Also, compile your kernel with the following > options: > > options KDB > options DDB > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options WITNESS_SKIPSPIN > options DEBUG_LOCKS > options DEBUG_VFS_LOCKS > > Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will > be plenty of those, and you'll desperately want to report them, but please > don't. > > The best way to report a problem is to answer to this e-mail with as short > as possible procedure of how to reproduce it and debugging info. I'd > prefer textdump if possible. Below you can find quick procedure how to > setup textdumps: > > Choose spare/swap disk/partition in your system, let's say it is > /dev/ad0s1b. > > Add the following line to /etc/fstab: > > /dev/ad0s1b none swap sw 0 0 > > Add the following line to /etc/rc.conf: > > ddb_enable="YES" > > Run the following commands: > > # /etc/rc.d/swap1 start > # /etc/rc.d/dumpon start > # /etc/rc.d/ddb start > > This will setup swap, mark it as dump device and setup some DDB > scripts. Or you can just reboot. > > Now when your system panic or deadlock, enter DDB and call the > following command: > > ddb> run kdb.enter.panic > > It will execute all the commands I need, dump them in text format to > your swap device and reboot machine. > > After the reboot, you should find textdump.tar.0 file in /var/crash/ > directory. This is the debug info I need. > > End of textdumps procedure. > > Ok, now that I know you read everything carefully, here is the patch: > > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 > > Good luck! >:> > > -- > Pawel Jakub Dawidek http://www.wheelsystems.com > pjd@FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil? Yes, I Am! > From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 06:48:20 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D0C610656AE for ; Wed, 1 Sep 2010 06:48:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 930618FC1E for ; Wed, 1 Sep 2010 06:48:19 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o816m5iw082303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Sep 2010 09:48:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id o816m5Xf032224; Wed, 1 Sep 2010 09:48:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o816m5uB032223; Wed, 1 Sep 2010 09:48:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 1 Sep 2010 09:48:05 +0300 From: Kostik Belousov To: Martin Cracauer Message-ID: <20100901064805.GF2396@deviant.kiev.zoral.com.ua> References: <20100830225841.GA9363@cons.org> <20100831160840.GA74125@icarus.home.lan> <20100831230728.GA36384@cons.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Zv6RaYeLzrVfNTUZ" Content-Disposition: inline In-Reply-To: <20100831230728.GA36384@cons.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Re: fsync(2) and on-disk write-back cache 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, 01 Sep 2010 06:48:20 -0000 --Zv6RaYeLzrVfNTUZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 31, 2010 at 07:07:28PM -0400, Martin Cracauer wrote: > Benjamin Kaduk wrote on Tue, Aug 31, 2010 at 12:12:04PM -0400:=20 > > On Tue, 31 Aug 2010, Jeremy Chadwick wrote: > >=20 > > >On Mon, Aug 30, 2010 at 06:58:42PM -0400, Martin Cracauer wrote: > > >>I always assumed the answer to this question is "of course": > > >> > > >>When doing an fsync (waiting for the commit), do we actually tell the > > >>disk to flush the on-disk write-back cache (if that is in use) to the > > >>platters? > > >> > > >>I just went down some code paths in both FreeBSD and Linux and in both > > >>cases the paths for fsync quickly disappear in the generic > > >>block-by-block flushing code that is also used for regular (non-fsync) > > >>flushing. I didn't see anything aware of the on-disk cache. > > > > > >I don't have an authoritative answer to your question, but this thread > > >seems to imply there's a relation between fsync() and an intentional > > >disk flush (BIO_FLUSH). I'm sure when BIO_FLUSH is called depends on > > >the filesystem as well. >=20 > I just went the for-dummies way and annotated all relevant BIO_FLUSH > places with debug print statements. They don't seem to be called when > doing an fsync on a file in a local filesystem. ufs (no softupdates) > -> old-style SCSI disk. >=20 > I'll snoop around some more, try it on ZFS/SATA and do some timing > tests. Be assured that all variants of UFS (sync, async, SU, SU+J) do not call BIO_FLUSH. --Zv6RaYeLzrVfNTUZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkx99yQACgkQC3+MBN1Mb4jcqQCgyqLtkAiTxZoEw9bmpPfUteaC UiIAoO4PRdQ7q/P3EAjErhh7h2G/m7IZ =lyKn -----END PGP SIGNATURE----- --Zv6RaYeLzrVfNTUZ-- From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 08:38:37 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9B9A10656A9 for ; Wed, 1 Sep 2010 08:38:37 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (unknown [IPv6:2001:470:1f08:679::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5F6078FC1E for ; Wed, 1 Sep 2010 08:38:37 +0000 (UTC) Received: from unknown (client-86-31-85-106.midd.adsl.virginmedia.com [86.31.85.106]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 5073E5F15; Wed, 1 Sep 2010 08:38:28 +0000 (UTC) Date: Wed, 1 Sep 2010 09:38:29 +0100 From: Bruce Cran To: Kostik Belousov Message-ID: <20100901093829.00005841@unknown> In-Reply-To: <20100901064805.GF2396@deviant.kiev.zoral.com.ua> References: <20100830225841.GA9363@cons.org> <20100831160840.GA74125@icarus.home.lan> <20100831230728.GA36384@cons.org> <20100901064805.GF2396@deviant.kiev.zoral.com.ua> X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Martin Cracauer Subject: Re: fsync(2) and on-disk write-back cache 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, 01 Sep 2010 08:38:37 -0000 On Wed, 1 Sep 2010 09:48:05 +0300 Kostik Belousov wrote: > Be assured that all variants of UFS (sync, async, SU, SU+J) do not > call BIO_FLUSH. Isn't that something that should be fixed ASAP? -- Bruce Cran From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 09:11:42 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DF0410656BC for ; Wed, 1 Sep 2010 09:11:42 +0000 (UTC) (envelope-from k0802647@telus.net) Received: from defout.telus.net (defout.telus.net [204.209.205.13]) by mx1.freebsd.org (Postfix) with ESMTP id DE2BF8FC15 for ; Wed, 1 Sep 2010 09:11:41 +0000 (UTC) Received: from edmwaa03.telusplanet.net ([66.183.53.162]) by priv-edmwes24.telusplanet.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20100901091140.XQLJ16905.priv-edmwes24.telusplanet.net@edmwaa03.telusplanet.net> for ; Wed, 1 Sep 2010 03:11:40 -0600 Received: from oliver.bc.lan (d66-183-53-162.bchsia.telus.net [66.183.53.162]) by edmwaa03.telusplanet.net (BorderWare Security Platform) with ESMTP id 93B92256E7C3E3E8 for ; Wed, 1 Sep 2010 03:11:40 -0600 (MDT) Received: from [10.111.111.112] (unknown [10.111.111.112]) by oliver.bc.lan (Postfix) with ESMTP id 2654D6455; Wed, 1 Sep 2010 02:11:40 -0700 (PDT) Message-ID: <4C7E18CB.7020400@telus.net> Date: Wed, 01 Sep 2010 02:11:39 -0700 From: Carl User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.7) Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4C7CE2D0.40400@telus.net> In-Reply-To: <4C7CE2D0.40400@telus.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Cloudmark-Analysis: v=1.1 cv=SJIhyCEJBCHyullCFvS0mIdE5QsJS0d45teFqlr0wtg= c=1 sm=0 a=-TCISbd4vvQA:10 a=8nJEP1OIZ-IA:10 a=HNgjH8kF64GtJ7EcXKEMsQ==:17 a=TSbVqHtbAAAA:8 a=ovWl91bCEESMzyah8xIA:9 a=fiiRb9nCYlAv-_QnrpUA:7 a=1JQRu8pM5reU-8oiI3I0w186ZlQA:4 a=wPNLvfGTeEIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Subject: Re: gjournal alignment on 4K sector advanced format 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: Wed, 01 Sep 2010 09:11:42 -0000 On Tue Aug 31 12:19:52 UTC 2010, Ivan Voras wrote: > On 08/31/10 13:09, Carl wrote: >> Now I want to add gjournal to some of my partitions. It seems to me that >> I must also ensure the journal is aligned just as I've done with the >> data. So far, though, I have found no information as to how the >> journal's own filesystem layout works. Does it use fixed size >> blocks/fragments like the UFS2 data does? If so, what is its minimum >> addressable unit size? If it is smaller than 4KiB, we get journal >> misalignment and a performance loss, right? What must I do to ensure the >> journal is fully aligned? > > gjournal writes its metadata throughout the journal in sector sizes (512 > bytes) so it cannot be aligned in this way. > > For this you need a solution which will actually change the sector size, > like gnop or my glabel patch. From the following discussion, the glabel patch isn't likely to get committed, in which case I can't use it: http://comments.gmane.org/gmane.os.freebsd.devel.hackers/40664 Correct me if I'm wrong, but the gnop solution is still non-persistent and therefore unavailable for partitions whose mounting cannot be delayed till after startup scripts have executed. I'm not knowledgeable enough about this, so I'd welcome a clear description of how to reliably and automatically use gnop to override sector size at boot time. It sounds like neither ZFS nor gjournal are suitable for a production server with WDxxEARS drives. Soft updates and horribly long fsck times is the only option? A pox on Western Digital for delivering drives that lie about sector size >:-< Carl / K0802647 From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 09:19:21 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D9C910656A3 for ; Wed, 1 Sep 2010 09:19:21 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by mx1.freebsd.org (Postfix) with ESMTP id 238628FC15 for ; Wed, 1 Sep 2010 09:19:20 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta02.emeryville.ca.mail.comcast.net with comcast id 1MKL1f0031smiN4A2MKLnT; Wed, 01 Sep 2010 09:19:20 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta20.emeryville.ca.mail.comcast.net with comcast id 1MKK1f0033LrwQ28gMKKUl; Wed, 01 Sep 2010 09:19:20 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 5BD349B425; Wed, 1 Sep 2010 02:19:19 -0700 (PDT) Date: Wed, 1 Sep 2010 02:19:19 -0700 From: Jeremy Chadwick To: Carl Message-ID: <20100901091919.GA98434@icarus.home.lan> References: <4C7CE2D0.40400@telus.net> <4C7E18CB.7020400@telus.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C7E18CB.7020400@telus.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: gjournal alignment on 4K sector advanced format 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: Wed, 01 Sep 2010 09:19:21 -0000 On Wed, Sep 01, 2010 at 02:11:39AM -0700, Carl wrote: > On Tue Aug 31 12:19:52 UTC 2010, Ivan Voras wrote: > >On 08/31/10 13:09, Carl wrote: > >>Now I want to add gjournal to some of my partitions. It seems to me that > >>I must also ensure the journal is aligned just as I've done with the > >>data. So far, though, I have found no information as to how the > >>journal's own filesystem layout works. Does it use fixed size > >>blocks/fragments like the UFS2 data does? If so, what is its minimum > >>addressable unit size? If it is smaller than 4KiB, we get journal > >>misalignment and a performance loss, right? What must I do to ensure the > >>journal is fully aligned? > > > >gjournal writes its metadata throughout the journal in sector sizes (512 > >bytes) so it cannot be aligned in this way. > > > >For this you need a solution which will actually change the sector size, > >like gnop or my glabel patch. > > From the following discussion, the glabel patch isn't likely to get > committed, in which case I can't use it: > > http://comments.gmane.org/gmane.os.freebsd.devel.hackers/40664 > > Correct me if I'm wrong, but the gnop solution is still > non-persistent and therefore unavailable for partitions whose > mounting cannot be delayed till after startup scripts have executed. > I'm not knowledgeable enough about this, so I'd welcome a clear > description of how to reliably and automatically use gnop to > override sector size at boot time. > > It sounds like neither ZFS nor gjournal are suitable for a > production server with WDxxEARS drives. Soft updates and horribly > long fsck times is the only option? > > A pox on Western Digital for delivering drives that lie about sector > size >:-< Can't you just set the jumper on the drive to us 512-byte sectors? I mean, that's what it's there for... -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 10:34:47 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5133B10656BF for ; Wed, 1 Sep 2010 10:34:47 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id 0FF9A8FC08 for ; Wed, 1 Sep 2010 10:34:46 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.4/8.14.4) with ESMTP id o81AYjDw024121; Wed, 1 Sep 2010 12:34:45 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.4/8.14.4/Submit) id o81AYilx024120; Wed, 1 Sep 2010 06:34:44 -0400 (EDT) (envelope-from cracauer) Date: Wed, 1 Sep 2010 06:34:44 -0400 From: Martin Cracauer To: Kostik Belousov Message-ID: <20100901103444.GA22129@cons.org> References: <20100830225841.GA9363@cons.org> <20100831160840.GA74125@icarus.home.lan> <20100831230728.GA36384@cons.org> <20100901064805.GF2396@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100901064805.GF2396@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, Martin Cracauer Subject: Re: fsync(2) and on-disk write-back cache 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, 01 Sep 2010 10:34:47 -0000 Kostik Belousov wrote on Wed, Sep 01, 2010 at 09:48:05AM +0300: > On Tue, Aug 31, 2010 at 07:07:28PM -0400, Martin Cracauer wrote: > > Benjamin Kaduk wrote on Tue, Aug 31, 2010 at 12:12:04PM -0400: > > > On Tue, 31 Aug 2010, Jeremy Chadwick wrote: > > > > > > >On Mon, Aug 30, 2010 at 06:58:42PM -0400, Martin Cracauer wrote: > > > >>I always assumed the answer to this question is "of course": > > > >> > > > >>When doing an fsync (waiting for the commit), do we actually tell the > > > >>disk to flush the on-disk write-back cache (if that is in use) to the > > > >>platters? > > > >> > > > >>I just went down some code paths in both FreeBSD and Linux and in both > > > >>cases the paths for fsync quickly disappear in the generic > > > >>block-by-block flushing code that is also used for regular (non-fsync) > > > >>flushing. I didn't see anything aware of the on-disk cache. > > > > > > > >I don't have an authoritative answer to your question, but this thread > > > >seems to imply there's a relation between fsync() and an intentional > > > >disk flush (BIO_FLUSH). I'm sure when BIO_FLUSH is called depends on > > > >the filesystem as well. > > > > I just went the for-dummies way and annotated all relevant BIO_FLUSH > > places with debug print statements. They don't seem to be called when > > doing an fsync on a file in a local filesystem. ufs (no softupdates) > > -> old-style SCSI disk. > > > > I'll snoop around some more, try it on ZFS/SATA and do some timing > > tests. > Be assured that all variants of UFS (sync, async, SU, SU+J) do not > call BIO_FLUSH. With a ZFS on SATA it looks different. ad_strategy gets called to queue BIO_FLUSH three times (for a single-block fsync). However, those calls are after fsync completes and returned to the called. And I still can't see how the disk would communicate individual block's status (on platter or not), all I see is global commands to flush all the cache (and I don't think that is synchronous). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 10:41:35 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A4E610656A8 for ; Wed, 1 Sep 2010 10:41:35 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1F44D8FC16 for ; Wed, 1 Sep 2010 10:41:34 +0000 (UTC) Received: by qyk4 with SMTP id 4so8364547qyk.13 for ; Wed, 01 Sep 2010 03:41:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=KrY70pItVAFcS4E6ERfiwXv8fzla/5hHkpUnMRTxPS4=; b=V1htt39UEojvue0MRF2Bkk4AifodCHd/kr+D6lWQINv5aRl/xycrEAqlOdVE4RWzbC TSyCeyU6lThF+zBJElslioUgvGBTV/eLMGvzYwYiGt4z4HsVH8cRSGJ+F/ladxFMWInp 7DdjrUZKfjyd1UuqL5R+QjODAzuc2PjzzdyQU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=o+kzabM76MbwvEXg45iBHIAdTUeKQQ2ijSpHaD7E1M/eRoIY0N1IYHO1J8Mq3AswQF WD2T3PrqnZX49YkNFah0x1pBImDnsWUvhkB/XB5FXxP/wgAHJAul2PDAYfmR5utat/df UD9wnU3hyB+lZU72/usSM894Zhu9vsAt3u/rc= Received: by 10.229.218.143 with SMTP id hq15mr5314102qcb.34.1283337694335; Wed, 01 Sep 2010 03:41:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.241.213 with HTTP; Wed, 1 Sep 2010 03:41:04 -0700 (PDT) In-Reply-To: <20100901091919.GA98434@icarus.home.lan> References: <4C7CE2D0.40400@telus.net> <4C7E18CB.7020400@telus.net> <20100901091919.GA98434@icarus.home.lan> From: Matthias Gamsjager Date: Wed, 1 Sep 2010 12:41:04 +0200 Message-ID: To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Cc: Carl , freebsd-fs@freebsd.org Subject: Re: gjournal alignment on 4K sector advanced format 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: Wed, 01 Sep 2010 10:41:35 -0000 > Can't you just set the jumper on the drive to us 512-byte sectors? > I mean, that's what it's there for... apparently this isn;t the case because all it does is change to offset From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 14:48:31 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C48BA1065670; Wed, 1 Sep 2010 14:48:31 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 8FB288FC22; Wed, 1 Sep 2010 14:48:31 +0000 (UTC) Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id BBF0F340; Wed, 1 Sep 2010 10:29:01 -0400 (EDT) Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 01 Sep 2010 10:29:01 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=from:to:subject:date:cc:references:in-reply-to:mime-version:content-type:message-id; s=smtpout; bh=pJk3SMQlFVY7V8eXshHQdk/x8vo=; b=lGH2QOA0EBH5FMI37ugpKSquGLIZpDzQZ64hwbhpsB/Z/xAJSamROv1jkjdBT5iiEp4o4gk2426qivevRd4Aa+liLj6b3R9bgxTPcvV1+hmI1kdzPBNJ+ZvIanwRSQrN152cSfuoA1KwLZwFH18faEMjuFjFNzHGSxMQ246N6pA= X-Sasl-enc: azRSuw/gq4EPAUCxbqlOVhjSPO1nYgnj7bowFsb5VoN9 1283351340 Received: from tcbug.ixsystems.com (74-34-16-134.dr01.rsmt.mn.frontiernet.net [74.34.16.134]) by mail.messagingengine.com (Postfix) with ESMTPSA id E581B5E5C62; Wed, 1 Sep 2010 10:29:00 -0400 (EDT) From: Josh Paetzel To: freebsd-fs@freebsd.org Date: Wed, 1 Sep 2010 09:28:59 -0500 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.4.5; amd64; ; ) References: <20100831215915.GE1932@garage.freebsd.pl> In-Reply-To: <20100831215915.GE1932@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_rMmfMpNLXbHCsBj" Message-Id: <201009010928.59725.josh@tcbug.org> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: ZFS v28 is ready for wider testing. 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, 01 Sep 2010 14:48:32 -0000 --Boundary-00=_rMmfMpNLXbHCsBj Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit On Tuesday 31 August 2010 16:59:15 Pawel Jakub Dawidek wrote: > Hello. > > I'd like to give you ZFS v28 for testing. If you are neither brave nor > mad, you can stop here. > > The patchset is very experimental. It can eat your cookie and hurt your > teddy bear, so be warned. Don't try it for anything except testing. > > This patchset is also a message we, as the FreeBSD project, would like > to send to our users: Eventhough OpenSolaris is dead, the ZFS file > system is going to stay in FreeBSD. At this point we have quite a few > developers involved in ZFS on FreeBSD as well as serveral companies. > We are also looking forward to work with IllumOS. > > So, what this new ZFS brings? > > - Data deduplication. Read more here: > > http://blogs.sun.com/bonwick/entry/zfs_dedup > > - Triple parity RAIDZ (RAIDZ3). Read more here: > > http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ > > - zfs diff. Read more here: > > http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley > > - zpool split. Read more here: > > http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante > > - Snapshot holds. Read more here: > > http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby > > - zpool import -F. Allows to rewind corrupted pool to earlier > transaction group. > > - Possibility to import pool in read-only mode. > > And much, much more, including plenty of preformance improvements and bug > fixes. > > So test whatever you can and report back. Look for regressions, strange > behaviour, missing features, deadlocks, livelocks, preformance > degradation, etc. > > The boot code is not updated at all, so booting off of ZFS doesn't > currently work. > > The patch is against today's FreeBSD HEAD. > > The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, > please don't turn it off. Also, compile your kernel with the following > options: > > options KDB > options DDB > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options WITNESS_SKIPSPIN > options DEBUG_LOCKS > options DEBUG_VFS_LOCKS > > Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will > be plenty of those, and you'll desperately want to report them, but please > don't. > > The best way to report a problem is to answer to this e-mail with as short > as possible procedure of how to reproduce it and debugging info. I'd > prefer textdump if possible. Below you can find quick procedure how to > setup textdumps: > > Choose spare/swap disk/partition in your system, let's say it is > /dev/ad0s1b. > > Add the following line to /etc/fstab: > > /dev/ad0s1b none swap sw 0 0 > > Add the following line to /etc/rc.conf: > > ddb_enable="YES" > > Run the following commands: > > # /etc/rc.d/swap1 start > # /etc/rc.d/dumpon start > # /etc/rc.d/ddb start > > This will setup swap, mark it as dump device and setup some DDB > scripts. Or you can just reboot. > > Now when your system panic or deadlock, enter DDB and call the > following command: > > ddb> run kdb.enter.panic > > It will execute all the commands I need, dump them in text format to > your swap device and reboot machine. > > After the reboot, you should find textdump.tar.0 file in /var/crash/ > directory. This is the debug info I need. > > End of textdumps procedure. > > Ok, now that I know you read everything carefully, here is the patch: > > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 > > Good luck! >:> I get the following error from make buildworld after applying the patch. I checked twice to make sure the patch applied cleanly, which it did. cc -O2 -pipe - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/compat/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/compat/opensolaris/include - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/head - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/common - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris/uts/common -DNEED_SOLARIS_BOOLEAN -g -std=gnu89 -Wno-unknown-pragmas - I/usr/obj/usr/src/tmp/legacy/usr/include -static - L/usr/obj/usr/src/tmp/legacy/usr/lib -o ctfconvert alist.o ctf.o ctfconvert.o dwarf.o fixup_tdescs.o hash.o iidesc.o input.o list.o memory.o merge.o output.o st_parse.o stabs.o stack.o strtab.o symbol.o tdata.o traverse.o util.o -lctf -ldwarf -lelf -lz -lpthread -legacy strtab.o(.text+0x109): In function `strtab_print': /usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:249: undefined reference to `MIN' strtab.o(.text+0x28d): In function `strtab_insert': /usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:119: undefined reference to `MIN' strtab.o(.text+0x3a1):/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:145: undefined reference to `MIN' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error # uname -a FreeBSD head.tcbug.org 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Aug 31 16:30:57 UTC 2010 root@head.tcbug.org:/usr/obj/usr/src/sys/HEAD amd64 -- Thanks, Josh Paetzel --Boundary-00=_rMmfMpNLXbHCsBj-- From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 15:03:56 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0834310656BF for ; Wed, 1 Sep 2010 15:03:56 +0000 (UTC) (envelope-from kungfujesus06@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id B9D5F8FC1C for ; Wed, 1 Sep 2010 15:03:55 +0000 (UTC) Received: by gxk24 with SMTP id 24so3529269gxk.13 for ; Wed, 01 Sep 2010 08:03:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=UXXYYKqcKq+hLG1p4jPF5lZQBI1iMHugBGIT0XRuAWo=; b=e2OFY/1DGLCWPDaR10UL7f2clp0EiP/79iV6fRwRyBrjLU5iz7Zpv1/Y0oWCfi8ykb o2sLK1EUiDPKd4z+YsD/2Jr6Ma9OF7RjZXdxzG4ThQHaYQZcOuBTNhoAFzZ+oRRYKIEZ pnxYGaF1DdJDEeOfPJjC+jHnM1JOcoVpwtKf8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=W83rRwCfX4mVoaw0nE5exlGabTJHsRr/71iGkhsunJG5WxZw0Fo8urMKZU9R8sYHla Ox2P0BnizeeGbyljjT4K/nrhRE8bv9KAYKqwwPcRPDy3wKDzjnbDKkBPL3Itm7mgyCh1 SNTwFdDV7lF38ukdzg6voOZovtYd65ylUT7JE= MIME-Version: 1.0 Received: by 10.150.150.2 with SMTP id x2mr3891663ybd.283.1283353434450; Wed, 01 Sep 2010 08:03:54 -0700 (PDT) Received: by 10.231.186.215 with HTTP; Wed, 1 Sep 2010 08:03:54 -0700 (PDT) Date: Wed, 1 Sep 2010 11:03:54 -0400 Message-ID: From: Adam Stylinski To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS v28 is ready for wider testing. 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, 01 Sep 2010 15:03:56 -0000 ZFS diff looks like an especially useful feature. No more worrying about what you deleted when a snapshot grows suspiciously large. V22 on OpenSolaris already seems much faster, and the ability to remove log devices will make management much less scary when migrating a pool. From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 18:43:58 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B133C10656AC for ; Wed, 1 Sep 2010 18:43:58 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7A41F8FC18 for ; Wed, 1 Sep 2010 18:43:58 +0000 (UTC) Received: by iwn34 with SMTP id 34so1182178iwn.13 for ; Wed, 01 Sep 2010 11:43:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=iq0YUec0Tid+GD20Ukctr2bAAXeCnTpGEW5fk7ctI3M=; b=BOmztG6/EfHkfVWf8AwTM9QgiHBCWZmK+VdLQyKKTuzKh+Ab1/sJav7C2trlOt6bhF EnnnNwmD6H39rMPGufLCdeLJtrQ/yoJ5nSBTKDSduYWRRRWW3xftPJ8a6CSIVnC676ax ekyCijJvejkSPZXKkWLWdsMfpAmGO77YlMLYM= 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 :content-type; b=uO9FKrkKg5Iu3TWhYCHvPh1B1/ldPmFBuEFzFUqmU831Mb2da1aJkrZNMwQiJel6Hg vAliIDRlrUa/lJ5NQFcEj3cdQR9bkIiULYWTAnUNARZWA2ELT+sm4ukO5v9PkMbREZMT LFtjWNH4NgSBPt//6bJKuoxg0wcXzHD7V7ows= MIME-Version: 1.0 Received: by 10.231.33.67 with SMTP id g3mr8940697ibd.31.1283365049771; Wed, 01 Sep 2010 11:17:29 -0700 (PDT) Received: by 10.231.189.35 with HTTP; Wed, 1 Sep 2010 11:17:29 -0700 (PDT) In-Reply-To: <20100901091919.GA98434@icarus.home.lan> References: <4C7CE2D0.40400@telus.net> <4C7E18CB.7020400@telus.net> <20100901091919.GA98434@icarus.home.lan> Date: Wed, 1 Sep 2010 11:17:29 -0700 Message-ID: From: Freddie Cash To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: gjournal alignment on 4K sector advanced format 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: Wed, 01 Sep 2010 18:43:58 -0000 On Wed, Sep 1, 2010 at 2:19 AM, Jeremy Chadwick wrote: > Can't you just set the jumper on the drive to us 512-byte sectors? > I mean, that's what it's there for... The jumper doesn't change the reported sector size. All it does is change the internal offset used by 1, so that the first partition created by Windows XP starts at physical (512 B) sector 64 instead of sector 63 (although it's still logical sector 63), which aligns it to a 4 KB boundary. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 20:30:40 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F3E710656D3; Wed, 1 Sep 2010 20:30:40 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 667E18FC1D; Wed, 1 Sep 2010 20:30:39 +0000 (UTC) Received: by qyk31 with SMTP id 31so1152589qyk.13 for ; Wed, 01 Sep 2010 13:30:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=uzcSJllXdxoIPDxmhQ3qAz4zhB30v+bumkY0A1GZ6MQ=; b=iFDYkC1zH/XcKhJYQCnkTzsp64S783bZsURts4jslPoVw47ICVHZaBK7bsVUfLqI0Y hcz+uRvMdYl8/K19puWANHeuMMlBQHsgP3zDVq1b4iZU8G1HvK00OqlAcD1PoVxDgtmV TuNAa5mSlayyiXG+A1fQgTSQuqCqwxcuYxTc0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=XhWr8Kt96LPfzXK32X5Nqs+XoeTUjAmXRY5Y7gXBmMgxUPaBpUslQEF7IBpplIY6sK tefOEy1fRZOHycg0n3nR5E9L0NkdTD5t5nLvs9hnZnp89o1zpJXZ9MgMnSmNwrFfP6kv kjZkqcRTF8LfXbOwrTzS8l1wcKBoDW3Pz5sbA= Received: by 10.229.231.4 with SMTP id jo4mr6025969qcb.22.1283373038606; Wed, 01 Sep 2010 13:30:38 -0700 (PDT) Received: from centel.dataix.local ([99.181.137.20]) by mx.google.com with ESMTPS id q8sm11534397qcs.12.2010.09.01.13.30.36 (version=SSLv3 cipher=RC4-MD5); Wed, 01 Sep 2010 13:30:37 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C7EB7EB.8070206@DataIX.net> Date: Wed, 01 Sep 2010 16:30:35 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100806 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20100831215915.GE1932@garage.freebsd.pl> In-Reply-To: <20100831215915.GE1932@garage.freebsd.pl> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. 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, 01 Sep 2010 20:30:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/31/2010 17:59, Pawel Jakub Dawidek wrote: > Hello. > > I'd like to give you ZFS v28 for testing. If you are neither brave nor > mad, you can stop here. > > The patchset is very experimental. It can eat your cookie and hurt your > teddy bear, so be warned. Don't try it for anything except testing. > > This patchset is also a message we, as the FreeBSD project, would like > to send to our users: Eventhough OpenSolaris is dead, the ZFS file > system is going to stay in FreeBSD. At this point we have quite a few > developers involved in ZFS on FreeBSD as well as serveral companies. > We are also looking forward to work with IllumOS. > > So, what this new ZFS brings? > > - Data deduplication. Read more here: > > http://blogs.sun.com/bonwick/entry/zfs_dedup > > - Triple parity RAIDZ (RAIDZ3). Read more here: > > http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ > > - zfs diff. Read more here: > > http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley > > - zpool split. Read more here: > > http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante > > - Snapshot holds. Read more here: > > http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby > > - zpool import -F. Allows to rewind corrupted pool to earlier > transaction group. > > - Possibility to import pool in read-only mode. > > And much, much more, including plenty of preformance improvements and bug > fixes. > > So test whatever you can and report back. Look for regressions, strange > behaviour, missing features, deadlocks, livelocks, preformance > degradation, etc. > > The boot code is not updated at all, so booting off of ZFS doesn't > currently work. > > The patch is against today's FreeBSD HEAD. > > The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, > please don't turn it off. Also, compile your kernel with the following > options: > > options KDB > options DDB > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options WITNESS_SKIPSPIN > options DEBUG_LOCKS > options DEBUG_VFS_LOCKS > > Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will > be plenty of those, and you'll desperately want to report them, but please > don't. > > The best way to report a problem is to answer to this e-mail with as short > as possible procedure of how to reproduce it and debugging info. I'd > prefer textdump if possible. Below you can find quick procedure how to > setup textdumps: > > Choose spare/swap disk/partition in your system, let's say it is > /dev/ad0s1b. > > Add the following line to /etc/fstab: > > /dev/ad0s1b none swap sw 0 0 > > Add the following line to /etc/rc.conf: > > ddb_enable="YES" > > Run the following commands: > > # /etc/rc.d/swap1 start > # /etc/rc.d/dumpon start > # /etc/rc.d/ddb start > > This will setup swap, mark it as dump device and setup some DDB > scripts. Or you can just reboot. > > Now when your system panic or deadlock, enter DDB and call the > following command: > > ddb> run kdb.enter.panic > > It will execute all the commands I need, dump them in text format to > your swap device and reboot machine. > > After the reboot, you should find textdump.tar.0 file in /var/crash/ > directory. This is the debug info I need. > > End of textdumps procedure. > > Ok, now that I know you read everything carefully, here is the patch: > > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 > > Good luck! >:> > 293 files changed, 54587 insertions(+), 19525 deletions(-) Yikes! I certainly commend you for this work. As for how to explain it I do not think the words exist in the English dictionary. Though it is unlikely that I will be attempting to use this ATM I logged some things for giggles. http://bit.ly/d20tML At that URL you will find a patch.log reject-files.log and a directory 'reject-files' with non-other than the reject files from the patch tar & bzip2'd for convenience. Just for being curious & found out that only 14 of the 293 files that were changed had rejects against a stable/8 that was patched to ZFSv15 + metaslab_v2 + abe_stat_rrwlock. My Hats off to the developers and everyone involved with keeping this all together, it says A LOT!. This is impressive. Not to mention this easily read and understandable email to top it off. Regards! - -- Again here is the link: http://bit.ly/d20tML jhell,v -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMfrfqAAoJEJBXh4mJ2FR+gscH/3tXKOTa2/eVt5Ev9ovpEbS3 n3EiMe6b8G8jxWaynoccNFWi6IywTzDhuKQxM/o4I1RnUJe50fSF00IQqwVo3QDm rcju0RKFw6jFgLar+1qq2prssAWQZ4DLC9VQY5CxZ/NY6MgEoWWqaV91RkOqLu5a /4VrvnvkkNhF7Q8Wni3tljAKTw4OFo3thuft5AxsBhecnF+ghCsr9Ne7xFPA6sl0 x6tx9p1p4sTBhSy1/oIBDt16mD/6O9FPVdme7lCvhUtPY7mtlANIYM1GLPMDlu6p iKyzxJOx7veBH0cb3VPkWvd8quItwMIZj/EbS9vTORUEEq0OtTZeZMNVc/nJsX4= =PIN+ -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 20:51:27 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE83D10656A9; Wed, 1 Sep 2010 20:51:27 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 7AFC78FC0C; Wed, 1 Sep 2010 20:51:27 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 8521745CBA; Wed, 1 Sep 2010 22:51:25 +0200 (CEST) Received: from localhost (chello089077043238.chello.pl [89.77.43.238]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id AA04145C98; Wed, 1 Sep 2010 22:51:20 +0200 (CEST) Date: Wed, 1 Sep 2010 22:51:11 +0200 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20100901205111.GA4003@garage.freebsd.pl> References: <20100831215915.GE1932@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <20100831215915.GE1932@garage.freebsd.pl> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-current@FreeBSD.org Subject: Re: ZFS v28 is ready for wider testing. 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, 01 Sep 2010 20:51:27 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote: > Ok, now that I know you read everything carefully, here is the patch: >=20 > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Important note. Please patch with the following command: # patch -E -p0 < zfs_20100831.patch If you don't use -E option, patch(1) won't remove empty files and you won't be able to compile it. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkx+vL8ACgkQForvXbEpPzR3+ACZAQy6uz+yOkCgsBlpwTuOJsI7 BE4AniJtblvdvgteNZSJnvbPzm+wpR/Q =WYSO -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 20:59:25 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FB311065675; Wed, 1 Sep 2010 20:59:25 +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 CF3C78FC12; Wed, 1 Sep 2010 20:59:24 +0000 (UTC) Received: from mail.geekcn.org (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id EE90AA68247; Thu, 2 Sep 2010 04:59:23 +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 yQDwnh-lnYjb; Thu, 2 Sep 2010 04:59:17 +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 98878A67CC9; Thu, 2 Sep 2010 04:59:14 +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: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=ozLKEqsiH+ZnpDr+oAgjge/RGOYClZoTbnT3dvXZTQgQa0cqSlaIypC4d1YpxVWnS 8o4VJN6TasnX4wPaqpAhQ== Message-ID: <4C7EBE9F.8000406@delphij.net> Date: Wed, 01 Sep 2010 13:59:11 -0700 From: Xin LI Organization: The Geek China Organization User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100721 Thunderbird/3.0.6 ThunderBrowse/3.3.2 MIME-Version: 1.0 To: Josh Paetzel References: <20100831215915.GE1932@garage.freebsd.pl> <201009010928.59725.josh@tcbug.org> In-Reply-To: <201009010928.59725.josh@tcbug.org> X-Enigmail-Version: 1.0.1 OpenPGP: id=3FCA37C1; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: ZFS v28 is ready for wider testing. 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: Wed, 01 Sep 2010 20:59:25 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010/09/01 07:28, Josh Paetzel wrote: > On Tuesday 31 August 2010 16:59:15 Pawel Jakub Dawidek wrote: >> Hello. >> >> I'd like to give you ZFS v28 for testing. If you are neither brave nor >> mad, you can stop here. >> >> The patchset is very experimental. It can eat your cookie and hurt your >> teddy bear, so be warned. Don't try it for anything except testing. >> >> This patchset is also a message we, as the FreeBSD project, would like >> to send to our users: Eventhough OpenSolaris is dead, the ZFS file >> system is going to stay in FreeBSD. At this point we have quite a few >> developers involved in ZFS on FreeBSD as well as serveral companies. >> We are also looking forward to work with IllumOS. >> >> So, what this new ZFS brings? >> >> - Data deduplication. Read more here: >> >> http://blogs.sun.com/bonwick/entry/zfs_dedup >> >> - Triple parity RAIDZ (RAIDZ3). Read more here: >> >> http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ >> >> - zfs diff. Read more here: >> >> http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley >> >> - zpool split. Read more here: >> >> http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante >> >> - Snapshot holds. Read more here: >> >> http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby >> >> - zpool import -F. Allows to rewind corrupted pool to earlier >> transaction group. >> >> - Possibility to import pool in read-only mode. >> >> And much, much more, including plenty of preformance improvements and bug >> fixes. >> >> So test whatever you can and report back. Look for regressions, strange >> behaviour, missing features, deadlocks, livelocks, preformance >> degradation, etc. >> >> The boot code is not updated at all, so booting off of ZFS doesn't >> currently work. >> >> The patch is against today's FreeBSD HEAD. >> >> The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, >> please don't turn it off. Also, compile your kernel with the following >> options: >> >> options KDB >> options DDB >> options INVARIANTS >> options INVARIANT_SUPPORT >> options WITNESS >> options WITNESS_SKIPSPIN >> options DEBUG_LOCKS >> options DEBUG_VFS_LOCKS >> >> Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will >> be plenty of those, and you'll desperately want to report them, but please >> don't. >> >> The best way to report a problem is to answer to this e-mail with as short >> as possible procedure of how to reproduce it and debugging info. I'd >> prefer textdump if possible. Below you can find quick procedure how to >> setup textdumps: >> >> Choose spare/swap disk/partition in your system, let's say it is >> /dev/ad0s1b. >> >> Add the following line to /etc/fstab: >> >> /dev/ad0s1b none swap sw 0 0 >> >> Add the following line to /etc/rc.conf: >> >> ddb_enable="YES" >> >> Run the following commands: >> >> # /etc/rc.d/swap1 start >> # /etc/rc.d/dumpon start >> # /etc/rc.d/ddb start >> >> This will setup swap, mark it as dump device and setup some DDB >> scripts. Or you can just reboot. >> >> Now when your system panic or deadlock, enter DDB and call the >> following command: >> >> ddb> run kdb.enter.panic >> >> It will execute all the commands I need, dump them in text format to >> your swap device and reboot machine. >> >> After the reboot, you should find textdump.tar.0 file in /var/crash/ >> directory. This is the debug info I need. >> >> End of textdumps procedure. >> >> Ok, now that I know you read everything carefully, here is the patch: >> >> http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 >> >> Good luck! >:> > > I get the following error from make buildworld after applying the patch. I > checked twice to make sure the patch applied cleanly, which it did. > > cc -O2 -pipe - > I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/compat/opensolaris - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/compat/opensolaris/include - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris - > I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/head - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/common > - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt > - > I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris/uts/common > -DNEED_SOLARIS_BOOLEAN -g -std=gnu89 -Wno-unknown-pragmas - > I/usr/obj/usr/src/tmp/legacy/usr/include -static - > L/usr/obj/usr/src/tmp/legacy/usr/lib -o ctfconvert alist.o ctf.o ctfconvert.o > dwarf.o fixup_tdescs.o hash.o iidesc.o input.o list.o memory.o merge.o > output.o st_parse.o stabs.o stack.o strtab.o symbol.o tdata.o traverse.o > util.o -lctf -ldwarf -lelf -lz -lpthread -legacy > strtab.o(.text+0x109): In function `strtab_print': > /usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:249: > undefined reference to `MIN' > strtab.o(.text+0x28d): In function `strtab_insert': > /usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:119: > undefined reference to `MIN' > strtab.o(.text+0x3a1):/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:145: > undefined reference to `MIN' > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error Try compiling without -j perhaps? Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBCAAGBQJMfr6eAAoJEATO+BI/yjfBQfgH/i2uvAqIbnkoljBs9ADJAev1 3Ea/xCU/cIeUjJaftVh5ORYHiC2eT/bYFmNevVBb5oJ+UFB52WmB6/iECqn2IFsp QGWwKdS6M6g1FKWmYON4rgrB9EpX+TLOKGiql1pOtQ+25n8rGAXGOdfl0qvbkkms trK3EyKLIIn+30DisUKDGk+RICs0jof25GZ1g/CZNUm66kP8GhRlnJncYP0J0SGN TOD+IKVya8OPG13nfQY5k1DyDL9xG+fmOoDvbU7YyGh7Sf94IYUL0VTm3CF1aGY1 I51Nqj+dP6HO0uop8XL2FMwaZ85Y2Pr6HYCpvl31jkuwhDVEcGL2roxJ9yORGrc= =VE+N -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Wed Sep 1 22:20:22 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 288AD10656C7; Wed, 1 Sep 2010 22:20:22 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9F3CB8FC21; Wed, 1 Sep 2010 22:20:21 +0000 (UTC) Received: by qwg5 with SMTP id 5so294664qwg.13 for ; Wed, 01 Sep 2010 15:20:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=+KmcYoV8D5+ByztE6oQjkbqdMWH5lF3dyANs3shH64E=; b=bO2GqwtmkV/NSjZEyrf3VdNeA4m6DEfAirhUho47V30HHSkStt2lYrwmmHjaPNCarI d/a1cRnVWGNWteGw++aAdrlJg0e46qVlZpkejKzpRqlppa09wnTOfaBmyMBg724daZ4g ksdM8/GIOmvJznhhgahR0Gog0WbIsCZ32tcKk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=GOOPz9UK7UnyX04c7YRYQhbtFsUWMzOogZs/0hNF27IjrV8l3aTol7NrCQu2hNEzIm +9NhKsQB8hU+LQQsfAtG94SGu4kLsxGSSKdaM9NRZZfdiOLg8d7B7M1FRCJd3CAQtPp4 jHrxU/yz/lUM9e3sSZ4/yhc62Ea0WhX4NU+Fw= Received: by 10.229.191.71 with SMTP id dl7mr6109941qcb.184.1283379619185; Wed, 01 Sep 2010 15:20:19 -0700 (PDT) Received: from centel.dataix.local ([99.181.137.20]) by mx.google.com with ESMTPS id f15sm11645490qcr.37.2010.09.01.15.20.16 (version=SSLv3 cipher=RC4-MD5); Wed, 01 Sep 2010 15:20:17 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C7ED19F.2080302@DataIX.net> Date: Wed, 01 Sep 2010 18:20:15 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100806 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Josh Paetzel References: <20100831215915.GE1932@garage.freebsd.pl> <201009010928.59725.josh@tcbug.org> In-Reply-To: <201009010928.59725.josh@tcbug.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: ZFS v28 is ready for wider testing. 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, 01 Sep 2010 22:20:22 -0000 On 09/01/2010 10:28, Josh Paetzel wrote: > On Tuesday 31 August 2010 16:59:15 Pawel Jakub Dawidek wrote: >> Hello. >> >> I'd like to give you ZFS v28 for testing. If you are neither brave nor >> mad, you can stop here. >> >> The patchset is very experimental. It can eat your cookie and hurt your >> teddy bear, so be warned. Don't try it for anything except testing. >> >> This patchset is also a message we, as the FreeBSD project, would like >> to send to our users: Eventhough OpenSolaris is dead, the ZFS file >> system is going to stay in FreeBSD. At this point we have quite a few >> developers involved in ZFS on FreeBSD as well as serveral companies. >> We are also looking forward to work with IllumOS. >> >> So, what this new ZFS brings? >> >> - Data deduplication. Read more here: >> >> http://blogs.sun.com/bonwick/entry/zfs_dedup >> >> - Triple parity RAIDZ (RAIDZ3). Read more here: >> >> http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ >> >> - zfs diff. Read more here: >> >> http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley >> >> - zpool split. Read more here: >> >> http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante >> >> - Snapshot holds. Read more here: >> >> http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby >> >> - zpool import -F. Allows to rewind corrupted pool to earlier >> transaction group. >> >> - Possibility to import pool in read-only mode. >> >> And much, much more, including plenty of preformance improvements and bug >> fixes. >> >> So test whatever you can and report back. Look for regressions, strange >> behaviour, missing features, deadlocks, livelocks, preformance >> degradation, etc. >> >> The boot code is not updated at all, so booting off of ZFS doesn't >> currently work. >> >> The patch is against today's FreeBSD HEAD. >> >> The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, >> please don't turn it off. Also, compile your kernel with the following >> options: >> >> options KDB >> options DDB >> options INVARIANTS >> options INVARIANT_SUPPORT >> options WITNESS >> options WITNESS_SKIPSPIN >> options DEBUG_LOCKS >> options DEBUG_VFS_LOCKS >> >> Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will >> be plenty of those, and you'll desperately want to report them, but please >> don't. >> >> The best way to report a problem is to answer to this e-mail with as short >> as possible procedure of how to reproduce it and debugging info. I'd >> prefer textdump if possible. Below you can find quick procedure how to >> setup textdumps: >> >> Choose spare/swap disk/partition in your system, let's say it is >> /dev/ad0s1b. >> >> Add the following line to /etc/fstab: >> >> /dev/ad0s1b none swap sw 0 0 >> >> Add the following line to /etc/rc.conf: >> >> ddb_enable="YES" >> >> Run the following commands: >> >> # /etc/rc.d/swap1 start >> # /etc/rc.d/dumpon start >> # /etc/rc.d/ddb start >> >> This will setup swap, mark it as dump device and setup some DDB >> scripts. Or you can just reboot. >> >> Now when your system panic or deadlock, enter DDB and call the >> following command: >> >> ddb> run kdb.enter.panic >> >> It will execute all the commands I need, dump them in text format to >> your swap device and reboot machine. >> >> After the reboot, you should find textdump.tar.0 file in /var/crash/ >> directory. This is the debug info I need. >> >> End of textdumps procedure. >> >> Ok, now that I know you read everything carefully, here is the patch: >> >> http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 >> >> Good luck! >:> > > I get the following error from make buildworld after applying the patch. I > checked twice to make sure the patch applied cleanly, which it did. > > cc -O2 -pipe - > I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/compat/opensolaris - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/compat/opensolaris/include - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris - > I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/head - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/common > - > I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt > - > I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris/uts/common > -DNEED_SOLARIS_BOOLEAN -g -std=gnu89 -Wno-unknown-pragmas - > I/usr/obj/usr/src/tmp/legacy/usr/include -static - > L/usr/obj/usr/src/tmp/legacy/usr/lib -o ctfconvert alist.o ctf.o ctfconvert.o > dwarf.o fixup_tdescs.o hash.o iidesc.o input.o list.o memory.o merge.o > output.o st_parse.o stabs.o stack.o strtab.o symbol.o tdata.o traverse.o > util.o -lctf -ldwarf -lelf -lz -lpthread -legacy > strtab.o(.text+0x109): In function `strtab_print': > /usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:249: > undefined reference to `MIN' > strtab.o(.text+0x28d): In function `strtab_insert': > /usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:119: > undefined reference to `MIN' > strtab.o(.text+0x3a1):/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:145: > undefined reference to `MIN' > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > # uname -a > FreeBSD head.tcbug.org 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Aug 31 16:30:57 > UTC 2010 root@head.tcbug.org:/usr/obj/usr/src/sys/HEAD amd64 > Did you apply with ( patch -E -p0 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 4157810656A7; Thu, 2 Sep 2010 00:51:08 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 184468FC15; Thu, 2 Sep 2010 00:51:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o820p7HZ057445; Thu, 2 Sep 2010 00:51:07 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o820p7qW057441; Thu, 2 Sep 2010 00:51:07 GMT (envelope-from arundel) Date: Thu, 2 Sep 2010 00:51:07 GMT Message-Id: <201009020051.o820p7qW057441@freefall.freebsd.org> To: arundel@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: kern/150207: zpool import -d /dev tries to open weird devices 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, 02 Sep 2010 00:51:08 -0000 Synopsis: zpool import -d /dev tries to open weird devices Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: arundel Responsible-Changed-When: Thu Sep 2 00:50:09 UTC 2010 Responsible-Changed-Why: Assign to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=150207 From owner-freebsd-fs@FreeBSD.ORG Thu Sep 2 09:05:07 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FEE510656FB; Thu, 2 Sep 2010 09:05:07 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 6F0508FC16; Thu, 2 Sep 2010 09:04:55 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id EE18345CDD; Thu, 2 Sep 2010 11:04:53 +0200 (CEST) Received: from localhost (pdawidek.whl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id A958845B36; Thu, 2 Sep 2010 11:04:48 +0200 (CEST) Date: Thu, 2 Sep 2010 11:04:39 +0200 From: Pawel Jakub Dawidek To: Rob Farmer Message-ID: <20100902090439.GB29617@garage.freebsd.pl> References: <20100831215915.GE1932@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZmUaFz6apKcXQszQ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=4.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. 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, 02 Sep 2010 09:05:07 -0000 --ZmUaFz6apKcXQszQ Content-Type: multipart/mixed; boundary="hHWLQfXTYDoKhP50" Content-Disposition: inline --hHWLQfXTYDoKhP50 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 02, 2010 at 01:55:51AM -0700, Rob Farmer wrote: > On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek wr= ote: > > > > Ok, now that I know you read everything carefully, here is the patch: > > > > =A0 =A0 =A0 =A0http://people.freebsd.org/~pjd/patches/zfs_20100831.patc= h.bz2 > > >=20 > buildworld on i386 (yes I know ZFS isn't ideal there): [...] Yes, I know about this problem, You can use attached patch or wait for full patch, which I'll be sending later today. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --hHWLQfXTYDoKhP50 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="atomic.h.patch" Content-Transfer-Encoding: quoted-printable --- sys/cddl/compat/opensolaris/sys/atomic.h +++ sys/cddl/compat/opensolaris/sys/atomic.h @@ -39,10 +39,9 @@ #ifndef __LP64__ extern void atomic_add_64(volatile uint64_t *target, int64_t delta); extern void atomic_dec_64(volatile uint64_t *target); -extern void *atomic_cas_ptr(volatile void *target, void *cmp, void *newva= l); #endif #ifndef __sparc64__ -extern uint64_t atomic_cas_32(volatile uint32_t *target, uint32_t cmp, +extern uint32_t atomic_cas_32(volatile uint32_t *target, uint32_t cmp, uint32_t newval); extern uint64_t atomic_cas_64(volatile uint64_t *target, uint64_t cmp, uint64_t newval); @@ -119,21 +118,19 @@ } =20 #ifndef COMPAT_32BIT -#if defined(__LP64__) +#ifdef __LP64__ static __inline void * atomic_cas_ptr(volatile void *target, void *cmp, void *newval) { - return ((void *)atomic_cas_64((volatile uint64_t *)target, (uint64_t)cmp, - (uint64_t)newval)); + return ((void *)atomic_cas_64(target, (uint64_t)cmp, (uint64_t)newval)); } #else static __inline void * atomic_cas_ptr(volatile void *target, void *cmp, void *newval) { - return ((void *)atomic_cas_32((volatile uint64_t *)target, (uint64_t)cmp, - (uint64_t)newval)); + return ((void *)atomic_cas_32(target, (uint32_t)cmp, (uint32_t)newval)); } #endif -#endif +#endif /* !COMPAT_32BIT */ =20 #endif /* !_OPENSOLARIS_SYS_ATOMIC_H_ */ --hHWLQfXTYDoKhP50-- --ZmUaFz6apKcXQszQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkx/aKcACgkQForvXbEpPzR1NgCfSnScNjJXmF4glzhV0HLFSajN FikAoMjsbxt5Qp1xSu32PvK+4N5gOeGY =BeVA -----END PGP SIGNATURE----- --ZmUaFz6apKcXQszQ-- From owner-freebsd-fs@FreeBSD.ORG Thu Sep 2 09:26:09 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 184D610656DE; Thu, 2 Sep 2010 09:26:09 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id A9AEE8FC08; Thu, 2 Sep 2010 09:26:08 +0000 (UTC) Received: by qyk4 with SMTP id 4so356854qyk.13 for ; Thu, 02 Sep 2010 02:26:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.46.5 with SMTP id h5mr6206885qaf.201.1283417751613; Thu, 02 Sep 2010 01:55:51 -0700 (PDT) Received: by 10.220.200.8 with HTTP; Thu, 2 Sep 2010 01:55:51 -0700 (PDT) X-Originating-IP: [71.1.133.114] In-Reply-To: <20100831215915.GE1932@garage.freebsd.pl> References: <20100831215915.GE1932@garage.freebsd.pl> Date: Thu, 2 Sep 2010 01:55:51 -0700 Message-ID: From: Rob Farmer To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. 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, 02 Sep 2010 09:26:09 -0000 On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek wrot= e: > > Ok, now that I know you read everything carefully, here is the patch: > > =A0 =A0 =A0 =A0http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.= bz2 > buildworld on i386 (yes I know ZFS isn't ideal there): =3D=3D=3D> cddl/lib/libdtrace (all) cc -O2 -fno-strict-aliasing -pipe -march=3Dprescott -I/usr/obj/usr/src/cddl/lib/libdtrace -I/usr/src/cddl/lib/libdtrace -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/dev/dtrace/i386 -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris -I/usr/src/cddl/lib/libdtrace/../../../cddl/compat/opensolaris/include -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/head -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libctf/= common -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtr= ace/common -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/contrib/opensolaris/uts/co= mmon -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/contrib/opensolaris/uts/int= el -DDIS_MEM -DNEED_SOLARIS_BOOLEAN -std=3Dgnu89 -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-unknown-pragmas -c /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace= /common/dt_aggregate.c In file included from /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/bitmap= .h:36, from /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace= /common/dt_impl.h:33, from /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace= /common/dt_aggregate.c:33: /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic= .h:132: error: static declaration of 'atomic_cas_ptr' follows non-static declaration /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic= .h:42: error: previous declaration of 'atomic_cas_ptr' was here cc1: warnings being treated as errors /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic= .h: In function 'atomic_cas_ptr': /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic= .h:133: warning: cast from pointer to integer of different size /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic= .h:134: warning: cast from pointer to integer of different size /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic= .h:134: warning: passing argument 1 of 'atomic_cas_32' from incompatible pointer type /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic= .h:134: warning: cast to pointer from integer of different size *** Error code 1 I tried applying the patch to r212087 to rule out recent changes to dtrace, but it made no difference. I used patch -E -p0 < patch. --=20 Rob Farmer From owner-freebsd-fs@FreeBSD.ORG Thu Sep 2 21:48:40 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 769D81065861; Thu, 2 Sep 2010 21:48:40 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 1BF138FC08; Thu, 2 Sep 2010 21:48:40 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id C367E45E5C; Thu, 2 Sep 2010 23:48:38 +0200 (CEST) Received: from localhost (chello089077043238.chello.pl [89.77.43.238]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 8FF2145CA0; Thu, 2 Sep 2010 23:48:32 +0200 (CEST) Date: Thu, 2 Sep 2010 23:48:23 +0200 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20100902214823.GB2542@garage.freebsd.pl> References: <20100831215915.GE1932@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NDin8bjvE/0mNLFQ" Content-Disposition: inline In-Reply-To: <20100831215915.GE1932@garage.freebsd.pl> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-current@FreeBSD.org Subject: Re: ZFS v28 is ready for wider testing. 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, 02 Sep 2010 21:48:40 -0000 --NDin8bjvE/0mNLFQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote: [...] > Ok, now that I know you read everything carefully, here is the patch: >=20 > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Now it is even easier to test new ZFS! :) Here you can find VirtualBox Appliance (113MB) with FreeBSD 9-CURRENT and ZFSv28: http://people.freebsd.org/~pjd/misc/FreeBSD9_ZFSv28_0.1.tgz Untar it, import it (zfsv28.ovf) to VirtualBox and have fun. You can log in as root with no password (via virtual console or via SSH). The system IP address is IP 192.168.56.66/24. There are 16 ada(4) disks to play with. For example: zfsv28:root:~# zpool create tank raidz3 ada{0,1,2,3,4,5,6,7} raidz3 ada{8,= 9,10,11,12,13,14,15} zfsv28:root:~# zpool status pool: tank state: ONLINE scan: none requested config: =09 NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz3-0 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 raidz3-1 ONLINE 0 0 0 ada8 ONLINE 0 0 0 ada9 ONLINE 0 0 0 ada10 ONLINE 0 0 0 ada11 ONLINE 0 0 0 ada12 ONLINE 0 0 0 ada13 ONLINE 0 0 0 ada14 ONLINE 0 0 0 ada15 ONLINE 0 0 0 =09 errors: No known data errors --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --NDin8bjvE/0mNLFQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkyAG6cACgkQForvXbEpPzTeRACghpYEuLMvkG4Fcnzsgu/e58AS q/QAoI93dqmCL4ycU9CAyvcmtKNy+jqg =owgd -----END PGP SIGNATURE----- --NDin8bjvE/0mNLFQ-- From owner-freebsd-fs@FreeBSD.ORG Thu Sep 2 22:14:11 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3311D1065805 for ; Thu, 2 Sep 2010 22:14:11 +0000 (UTC) (envelope-from phillip.nordwall@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id DE26C8FC17 for ; Thu, 2 Sep 2010 22:14:10 +0000 (UTC) Received: by qwg5 with SMTP id 5so1133029qwg.13 for ; Thu, 02 Sep 2010 15:14:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=z9cnxbJ/Q6oMlc9TDb//iYOfWBo1T/6reJ4iPXg4fgc=; b=Gl0zKolDGbpfGk7nG0lG/JqU0sDIaVhVNQDBFRfsb+ggdAIV/A2D8TXdOhQl2eBHPJ Z9r0CydP1KgOXePMBe8te9+cCy3vso4CSOEirJE4wTFJDKfzA0AO8GKESXMk+u/sSbHE v+oQ9Dc8tX5qWzNhESobsea+gX8BZQq5yo7Sk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=aVFraiqnS/YgHyKP6LfdRulOGVPFGpxh6aDCMMo+fxa6xbCIXh77lCNpsI3/5fuhle WINq6Yymh52UiOJeVuBu52jbCMFJnCA99Ssv1atBidrE8IL/EatLxPODwU9dWSzUxZOj qdCBPMrK9ucUYcj8uTFSrNWlPRvTZ5Din7L80= MIME-Version: 1.0 Received: by 10.224.29.4 with SMTP id o4mr853953qac.203.1283463927234; Thu, 02 Sep 2010 14:45:27 -0700 (PDT) Received: by 10.224.47.144 with HTTP; Thu, 2 Sep 2010 14:45:27 -0700 (PDT) Date: Thu, 2 Sep 2010 14:45:27 -0700 Message-ID: From: Phillip Nordwall To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ZFS mount_unionfs or ZFS overlay 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, 02 Sep 2010 22:14:11 -0000 I'm trying to do a mount_unionfs of a zfs file system over another filesystem and am getting an Operation not supported. If I try to do a zfs mount -O (for an overlay) I get the following error: no overlay mounts support on FreeBSD, ignoring. I'm thinking about digging into the code (guided by The Design and Implementation of the FreeBSD Operating Sytem) to find out how to make zfs union mounts work, but I figured I should ask here if there is a good reason why it is not currently implemented. My goal is to have the following mount setup. tank0/base on /zmnts/base (zfs, local) tank0/www on /zmnts/www (zfs, local) tank0/web0 on /zmnts/web0 (zfs, local) tank0/web1 on /zmnts/web1 (zfs, local) . . . tank0/webn on /zmnts/webn (zfs, local) /zmnts/base on /jails/base (nullfs, local) /jails/base on /jails/www (nullfs, local, read-only) :/zmnts/www on /jails/www (unionfs, local) /jails/www on /jails/web0 (nullfs, local, read-only) :/zmnts/web0 on /jails/web0 (unionfs, local) /jails/www on /jails/web1 (nullfs, local, read-only) :/zmnts/web1 on /jails/web1 (unionfs, local) . . . /jails/www on /jails/webn (nullfs, local, read-only) :/zmnts/webn on /jails/webn (unionfs, local) This would allow me to have a hierarchy of "inherited" jails where I could update any level and the levels below it would be updated, but also allow each level to override any or all files from a higher level. It also would allow for snapshotting any level, cloning it, performing a union mount below another level followed by the unmounting of a level it is now over. This gives much more power than just using a single nullfs layer. If you have any reason why I shouldn't do this, please let me know. Philip Nordwall Senior Systems Analyst/Programmer Computer Science Department Western Washington University On Thu, Sep 2, 2010 at 2:04 AM, Pawel Jakub Dawidek wrote: > On Thu, Sep 02, 2010 at 01:55:51AM -0700, Rob Farmer wrote: > > On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek > wrote: > > > > > > Ok, now that I know you read everything carefully, here is the patch: > > > > > > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 > > > > > > > buildworld on i386 (yes I know ZFS isn't ideal there): > [...] > > Yes, I know about this problem, You can use attached patch or wait for > full patch, which I'll be sending later today. > > -- > Pawel Jakub Dawidek http://www.wheelsystems.com > pjd@FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil? Yes, I Am! > From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 06:03:15 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7697F1065743 for ; Fri, 3 Sep 2010 06:03:15 +0000 (UTC) (envelope-from TERRY@tmk.com) Received: from server.tmk.com (server.tmk.com [204.141.35.63]) by mx1.freebsd.org (Postfix) with ESMTP id 56E878FC16 for ; Fri, 3 Sep 2010 06:03:15 +0000 (UTC) Received: from tmk.com by tmk.com (PMDF V6.4 #37010) id <01NRFO62ID6O002NBB@tmk.com> for freebsd-fs@freebsd.org; Fri, 03 Sep 2010 01:43:31 -0400 (EDT) Date: Fri, 03 Sep 2010 01:35:12 -0400 (EDT) From: Terry Kennedy To: freebsd-fs@freebsd.org Message-id: <01NRFOGNZW90002NBB@tmk.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=us-ascii Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 06:03:15 -0000 First, thanks for the immense amount of effort you've obviously put into this! I'm running 8-STABLE and would love to give this a good workout here. I currently have 3 test boxes w/ 32TB on each, currently runnihg the ZFS 14 that comes w/ RELENG_8. Dual E5520 CPU's and 48GB of RAM on each as well. The OS is on a separate set of gmirror'd UFS drives, so the lack of boot support won't be a problem. I saw that another poster said there were only a small percentage of patch files that didn't apply on his system (which was RELENG_8 with some other ZFS changes, IIRC). If someone can put together a v28 patchset against 8_STABLE, I promise to give it a good workout. Also, if that happens, would it be useful to have a list of the "ex- pected" LOR's in case testing on 8 turns up some that you haven't seen before? Terry Kennedy http://www.tmk.com terry@tmk.com New York, NY USA From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 06:36:42 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 258AB1065817 for ; Fri, 3 Sep 2010 06:36:42 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6E84B8FC0C for ; Fri, 3 Sep 2010 06:36:40 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA10898; Fri, 03 Sep 2010 09:36:38 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OrPt8-0006xz-LR; Fri, 03 Sep 2010 09:36:38 +0300 Message-ID: <4C809776.6000204@icyb.net.ua> Date: Fri, 03 Sep 2010 09:36:38 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.8) Gecko/20100822 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Phillip Nordwall References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS mount_unionfs or ZFS overlay X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 06:36:42 -0000 on 03/09/2010 00:45 Phillip Nordwall said the following: > I'm trying to do a mount_unionfs of a zfs file system over another > filesystem and am getting an Operation not supported. If I try to do a zfs > mount -O (for an overlay) I get the following error: no overlay mounts > support on FreeBSD, ignoring. > > I'm thinking about digging into the code (guided by The Design and > Implementation of the FreeBSD Operating Sytem) to find out how to make zfs > union mounts work, but I figured I should ask here if there is a good reason > why it is not currently implemented. To be able to work as upper layer in unionfs a filesystem should have support for "whiteouts". This hint should get you started. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 06:57:17 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4D8D10656BE; Fri, 3 Sep 2010 06:57:17 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4DF968FC17; Fri, 3 Sep 2010 06:57:17 +0000 (UTC) Received: by ywt2 with SMTP id 2so673085ywt.13 for ; Thu, 02 Sep 2010 23:57:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type; bh=Btf58SC1LUliEg2iiDdbIl8ZFLmi56NZ1jXy/DW4xoI=; b=IJsiD8J5jxe6AhS+W2St4dLB0ZbARIVbK9jB/xMJDaiiNa7ldC85FTPpSb8ahxdQjn rOKQFxA/LUvjoDyIMAEyhJ7hkeTUMtyVxBszMEeZhdUdJ+s3XvsCkS17OBBMuGlV+hpa vcNeEOg31xspTSGr0SZJII7SzJbUEMiyq24PA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type; b=Bfdh/5uQTf1I9YHYgI/9nws4xz4d6LrFEwmRreTOw3Za64VkM5Cy+De1tV28ngP4es o5c5tqwnRtG1+Zfy6wdf43rcR6fXvET9FTOKxtR3iQRcRQYce3ZWYG3MYdnva1ufy4X3 cWAU7yI3kXrGK27xdE8JTEOvsdxvLFt1uWYFU= Received: by 10.151.85.4 with SMTP id n4mr434890ybl.66.1283497036483; Thu, 02 Sep 2010 23:57:16 -0700 (PDT) Received: from centel.dataix.local ([99.181.137.20]) by mx.google.com with ESMTPS id v6sm3128528ybm.11.2010.09.02.23.57.13 (version=SSLv3 cipher=RC4-MD5); Thu, 02 Sep 2010 23:57:15 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C809C3F.10706@DataIX.net> Date: Fri, 03 Sep 2010 02:57:03 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100806 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Rob Farmer References: <20100831215915.GE1932@garage.freebsd.pl> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig62313E93F16F60022DDAC2FA" Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 06:57:17 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig62313E93F16F60022DDAC2FA Content-Type: multipart/mixed; boundary="------------000108090209070800040508" This is a multi-part message in MIME format. --------------000108090209070800040508 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 09/02/2010 04:55, Rob Farmer wrote: >=20 > I tried applying the patch to r212087 to rule out recent changes to > dtrace, but it made no difference. I used patch -E -p0 < patch. >=20 Hi Rob, I see that in your build error are a bunch of things to do with atomic.h and I recalled a patch from pjd@ on current@ that he sent in the same thread. I attached the downloaded patch. Maybe you can write back and site if it helped at all so people have a reference. Regards, --=20 jhell,v --------------000108090209070800040508 Content-Type: text/plain; name="atomic.h.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="atomic.h.patch" --- sys/cddl/compat/opensolaris/sys/atomic.h +++ sys/cddl/compat/opensolaris/sys/atomic.h @@ -39,10 +39,9 @@ #ifndef __LP64__ extern void atomic_add_64(volatile uint64_t *target, int64_t delta); extern void atomic_dec_64(volatile uint64_t *target); -extern void *atomic_cas_ptr(volatile void *target, void *cmp, void *new= val); #endif #ifndef __sparc64__ -extern uint64_t atomic_cas_32(volatile uint32_t *target, uint32_t cmp, +extern uint32_t atomic_cas_32(volatile uint32_t *target, uint32_t cmp, uint32_t newval); extern uint64_t atomic_cas_64(volatile uint64_t *target, uint64_t cmp, uint64_t newval); @@ -119,21 +118,19 @@ } =20 #ifndef COMPAT_32BIT -#if defined(__LP64__) +#ifdef __LP64__ static __inline void * atomic_cas_ptr(volatile void *target, void *cmp, void *newval) { - return ((void *)atomic_cas_64((volatile uint64_t *)target, (uint64_t)cm= p, - (uint64_t)newval)); + return ((void *)atomic_cas_64(target, (uint64_t)cmp, (uint64_t)newval))= ; } #else static __inline void * atomic_cas_ptr(volatile void *target, void *cmp, void *newval) { - return ((void *)atomic_cas_32((volatile uint64_t *)target, (uint64_t)cm= p, - (uint64_t)newval)); + return ((void *)atomic_cas_32(target, (uint32_t)cmp, (uint32_t)newval))= ; } #endif -#endif +#endif /* !COMPAT_32BIT */ =20 #endif /* !_OPENSOLARIS_SYS_ATOMIC_H_ */ --------------000108090209070800040508-- --------------enig62313E93F16F60022DDAC2FA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMgJxGAAoJEJBXh4mJ2FR+sEoH/0GeSafbV/bBE62OejKnryVk 3eSKAap2xC8YnOVNNQckPTAJ82ArZprJ3YF6UssjVvYZZky6oZuJpP+SQ1ipzBtE 9CGUwo3jVqt44CJt3ARRef2DyegIPyZYg8MnTBsqAJsThDbgW+Q8ndKqlc1Ja902 uUHyVtU1Nfz6P7CMZJUZ1Jk93ZJAONIdMXAJ1kcCqar4O43a0tfPVNuE1XUfgnbO 00xZCxiP2ZZOcfoMvMDD6ZxdeuwA7tc/sDp4DehC8gGGSvuL1SjFeRh3xoPuuihT YeiU5dLj3AWt8mANW6JbAmyw+3s0w9QP5wRPbb3aXVukbMPW2EdYgesWHaadcZw= =ce0L -----END PGP SIGNATURE----- --------------enig62313E93F16F60022DDAC2FA-- From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 08:16:47 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E8D810657F0; Fri, 3 Sep 2010 08:16:47 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id A77858FC19; Fri, 3 Sep 2010 08:16:46 +0000 (UTC) Received: by vws7 with SMTP id 7so1262409vws.13 for ; Fri, 03 Sep 2010 01:16:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.124.224 with SMTP id v32mr391906vcr.4.1283501805697; Fri, 03 Sep 2010 01:16:45 -0700 (PDT) Received: by 10.220.200.8 with HTTP; Fri, 3 Sep 2010 01:16:45 -0700 (PDT) X-Originating-IP: [71.1.133.114] In-Reply-To: <4C809C3F.10706@DataIX.net> References: <20100831215915.GE1932@garage.freebsd.pl> <4C809C3F.10706@DataIX.net> Date: Fri, 3 Sep 2010 01:16:45 -0700 Message-ID: From: Rob Farmer To: jhell Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 08:16:47 -0000 On Thu, Sep 2, 2010 at 23:57, jhell wrote: > On 09/02/2010 04:55, Rob Farmer wrote: >> >> I tried applying the patch to r212087 to rule out recent changes to >> dtrace, but it made no difference. I used patch -E -p0 < patch. >> > > Hi Rob, > > I see that in your build error are a bunch of things to do with atomic.h > and I recalled a patch from pjd@ on current@ that he sent in the same > thread. I attached the downloaded patch. Maybe you can write back and > site if it helped at all so people have a reference. Yes, it worked. Since this is just a testing thing and pjd alredy knew about the problem and seemed confident about the solution I didn't bother to reply. --=20 Rob Farmer > > > Regards, > > -- > > =A0jhell,v > From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 11:24:04 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AADBD10657B5 for ; Fri, 3 Sep 2010 11:24:04 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 30D058FC13 for ; Fri, 3 Sep 2010 11:24:03 +0000 (UTC) Received: by eyx24 with SMTP id 24so1095794eyx.13 for ; Fri, 03 Sep 2010 04:24:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=TSt4gZPD0Zm+mHt4XDFPXwZlYSNp9fzqeQYfXyeRSVI=; b=urigIB2kWQ5gTxr3SK05Cyx6JOkw23WDSNvaBgLe7ug62AeI7FwIMputsYeM6YGfzn nADzTo6VEQZAqoQLBOMIFJZCbdRTtVOM/+lpq0E8f3zEX1nbJMiROM49QBKyF8vv7Sdb zRYqZ6G2pLirET+oc2RUquUchopyjquAosDE0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=DdxON1BPKue3ObPugTpeM7KCWnGN7HA8VRBlMjDJjo2emNdxb+72jqDa5ciD59HESV CQ/izhdVMr3sVaP98m8OKxmkg7wf3RgfC1MTRXe6qHosO/WGYDm4y5aQwcEak3goEtAX w2UPxbU4HTESfjLpE6Joxe4XJ+x4JCvkoWOnU= Received: by 10.213.20.19 with SMTP id d19mr673198ebb.1.1283511673486; Fri, 03 Sep 2010 04:01:13 -0700 (PDT) Received: from localhost ([212.98.186.134]) by mx.google.com with ESMTPS id z55sm2520086eeh.3.2010.09.03.04.01.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 03 Sep 2010 04:01:12 -0700 (PDT) Date: Fri, 3 Sep 2010 14:01:08 +0300 From: Gleb Kurtsou To: Phillip Nordwall Message-ID: <20100903110107.GA2084@tops> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS mount_unionfs or ZFS overlay X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 11:24:04 -0000 On (02/09/2010 14:45), Phillip Nordwall wrote: > I'm trying to do a mount_unionfs of a zfs file system over another > filesystem and am getting an Operation not supported. If I try to do a zfs > mount -O (for an overlay) I get the following error: no overlay mounts > support on FreeBSD, ignoring. > > I'm thinking about digging into the code (guided by The Design and > Implementation of the FreeBSD Operating Sytem) to find out how to make zfs > union mounts work, but I figured I should ask here if there is a good reason > why it is not currently implemented. > > My goal is to have the following mount setup. > > tank0/base on /zmnts/base (zfs, local) > tank0/www on /zmnts/www (zfs, local) > tank0/web0 on /zmnts/web0 (zfs, local) > tank0/web1 on /zmnts/web1 (zfs, local) > . > . > . > tank0/webn on /zmnts/webn (zfs, local) > /zmnts/base on /jails/base (nullfs, local) > /jails/base on /jails/www (nullfs, local, read-only) > :/zmnts/www on /jails/www (unionfs, local) > > /jails/www on /jails/web0 (nullfs, local, read-only) > :/zmnts/web0 on /jails/web0 (unionfs, local) > /jails/www on /jails/web1 (nullfs, local, read-only) > :/zmnts/web1 on /jails/web1 (unionfs, local) > . > . > . > > /jails/www on /jails/webn (nullfs, local, read-only) > :/zmnts/webn on /jails/webn (unionfs, local) > > > This would allow me to have a hierarchy of "inherited" jails where I could > update any level and the levels below it would be updated, but also allow > each level to override any or all files from a higher level. It also would > allow for snapshotting any level, cloning it, performing a union mount below > another level followed by the unmounting of a level it is now over. This > gives much more power than just using a single nullfs layer. > > If you have any reason why I shouldn't do this, please let me know. If you are going to implement it I'd suggest to look at implementing per-jail private mounts. What I suggest is that each jail has /zmnts/base on it's root (mounted in root jail) and private /zmnts/www, i.e jailN has tank0/webN mounted on /zmnts/www. The jail should have deadfs mounted on /zmnts/www if nothing was mounted (to simplify implementation). It's a bit different from your setup and there would be no union mounts but it would let you avoid nullfs overhead. The only drawback is that filesystem can be mounted only once, and you would have to mount snapshots to perform administrative tasks on tank0/webN, or add support for multiple mounts to zfs, or develop a stacked pseudo filesystem to show all private mounts under /zmnts/www in root jail. I was told that "somebody" is likely to be already working on it, but wasn't able to find who is it. I'm going to implement it myself, but busy with other tasks, unless someone is willing to sponsor it. Thanks, Gleb. > > Philip Nordwall > Senior Systems Analyst/Programmer > Computer Science Department > Western Washington University From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 12:58:31 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ACD21065772 for ; Fri, 3 Sep 2010 12:58:31 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 31E538FC12 for ; Fri, 3 Sep 2010 12:58:31 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1OrVqe-000JtM-Uh for freebsd-fs@freebsd.org; Fri, 03 Sep 2010 12:58:29 +0000 Date: Fri, 03 Sep 2010 21:58:28 +0900 Message-ID: From: Randy Bush To: freebsd-fs User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: just another sad story in zfs tuning city X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 12:58:31 -0000 i have a system that should move right along. but it is as soggy as a tenugui on an august afternoon. 2*amd64 2.0GHz 4GB 750GB 8.1-STABLE Sun Aug 8 01:05:24 UTC 2010 /dev/mirror/boota 8.3G 909M 6.7G 12% / procfs 4.1k 4.1k 0B 100% /proc tank 729G 28k 729G 0% /tank tank/data 729G 31k 729G 0% /data tank/data/nfsen 877G 148G 729G 17% /data/nfsen tank/data/rpki 729G 107M 729G 0% /data/rpki tank/usr 737G 7.7G 729G 1% /usr tank/usr/home 732G 2.6G 729G 0% /usr/home tank/usr/usr 732G 2.6G 729G 0% /usr/usr tank/var 730G 759M 729G 0% /var tank/var/log 730G 415M 729G 0% /var/log tank/var/spool 729G 68M 729G 0% /var/spool work0.psg.com:/usr/home/rancid# cat /boot/loader.conf.local loader_logo=beastie zfs_load=YES vm.kmem_size=4G vfs.zfs.arc_max=64M vfs.zfs.prefetch_disable=1 geom_mirror_load=YES kern.maxvnodes=50000 i am tempted to just boot without the zfs memory hacks in loader conf. any warnings on doing so? any other clues also gladly accepted. randy From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 13:06:50 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC737106567A for ; Fri, 3 Sep 2010 13:06:50 +0000 (UTC) (envelope-from marco@tolstoy.tols.org) Received: from tolstoy.tols.org (tolstoy.tols.org [IPv6:2a02:898:0:20::57:1]) by mx1.freebsd.org (Postfix) with ESMTP id 559C88FC15 for ; Fri, 3 Sep 2010 13:06:50 +0000 (UTC) Received: from tolstoy.tols.org (localhost [127.0.0.1]) by tolstoy.tols.org (8.14.4/8.14.4) with ESMTP id o83D6kne024275 for ; Fri, 3 Sep 2010 13:06:46 GMT (envelope-from marco@tolstoy.tols.org) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.96.1 at tolstoy.tols.org Received: (from marco@localhost) by tolstoy.tols.org (8.14.4/8.14.4/Submit) id o83D6k5Y024274 for freebsd-fs@freebsd.org; Fri, 3 Sep 2010 15:06:46 +0200 (CEST) (envelope-from marco) Date: Fri, 3 Sep 2010 15:06:46 +0200 From: Marco van Tol To: freebsd-fs Message-ID: <20100903130646.GD19666@tolstoy.tols.org> Mail-Followup-To: freebsd-fs References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on tolstoy.tols.org Subject: Re: just another sad story in zfs tuning city X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 13:06:50 -0000 On Fri, Sep 03, 2010 at 09:58:28PM +0900, Randy Bush wrote: > i have a system that should move right along. but it is as soggy as a > tenugui on an august afternoon. > > 2*amd64 2.0GHz 4GB 750GB > 8.1-STABLE Sun Aug 8 01:05:24 UTC 2010 > > /dev/mirror/boota 8.3G 909M 6.7G 12% / > procfs 4.1k 4.1k 0B 100% /proc > tank 729G 28k 729G 0% /tank > tank/data 729G 31k 729G 0% /data > tank/data/nfsen 877G 148G 729G 17% /data/nfsen > tank/data/rpki 729G 107M 729G 0% /data/rpki > tank/usr 737G 7.7G 729G 1% /usr > tank/usr/home 732G 2.6G 729G 0% /usr/home > tank/usr/usr 732G 2.6G 729G 0% /usr/usr > tank/var 730G 759M 729G 0% /var > tank/var/log 730G 415M 729G 0% /var/log > tank/var/spool 729G 68M 729G 0% /var/spool > > work0.psg.com:/usr/home/rancid# cat /boot/loader.conf.local > loader_logo=beastie > zfs_load=YES > vm.kmem_size=4G > vfs.zfs.arc_max=64M > vfs.zfs.prefetch_disable=1 > geom_mirror_load=YES > kern.maxvnodes=50000 > > i am tempted to just boot without the zfs memory hacks in loader conf. > any warnings on doing so? any other clues also gladly accepted. In my view you limited the page cache (equivalent) for your zfs filesystems to 64MB out of 4GB system memory. Not sure what your I/O is like, but that could explain the sluggishness? :-) Sticking a wet finger in the air, and assuming /dev/mirror/boota holds a UFS filesystem that's just used to boot from I'd say give kmem_size 1.5x physical, arc_max 1.0x physical, and arc_min 0.5x physical memory to have it compete with the UFS page cache. After that applications that run can't use more then (0.5x physical memory plus swap space). Then again, I'm by far no zfs expert, so consider this an experiment ;) Marco -- Now watch me snatch defeat from the jaws of victory - "Rigoletto" during a game on www.dailygammon.com From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 16:21:57 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07FA610657DC; Fri, 3 Sep 2010 16:21:57 +0000 (UTC) (envelope-from peter@3mail4.co.uk) Received: from mail4.morpheushosting.sk (mail4.morpheushosting.sk [69.60.120.12]) by mx1.freebsd.org (Postfix) with ESMTP id B99628FC1E; Fri, 3 Sep 2010 16:21:56 +0000 (UTC) Received: from [192.168.1.5] (cpc14-know8-0-0-cust118.know.cable.virginmedia.com [82.46.228.119]) (authenticated bits=0) by mail4.morpheushosting.sk (8.14.4/8.14.4) with ESMTP id o83FpYp4004314; Fri, 3 Sep 2010 17:51:48 +0200 (CEST) (envelope-from peter@3mail4.co.uk) Message-ID: <4C811954.5040602@3mail4.co.uk> Date: Fri, 03 Sep 2010 16:50:44 +0100 From: "Peter Molnar, BSD" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100713 Thunderbird/3.0.6 MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20100831215915.GE1932@garage.freebsd.pl> <20100902214823.GB2542@garage.freebsd.pl> In-Reply-To: <20100902214823.GB2542@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-100.5 required=5.1 tests=BAYES_00, RCVD_IN_BRBL_LASTEXT,RCVD_IN_SORBS_DUL,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail4.morpheushosting.sk Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 16:21:57 -0000 On 02/09/10 22:48, Pawel Jakub Dawidek wrote: > On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote: > [...] > >> Ok, now that I know you read everything carefully, here is the patch: >> >> http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 >> > Now it is even easier to test new ZFS! :) > > Here you can find VirtualBox Appliance (113MB) with > FreeBSD 9-CURRENT and ZFSv28: > > http://people.freebsd.org/~pjd/misc/FreeBSD9_ZFSv28_0.1.tgz > > Untar it, import it (zfsv28.ovf) to VirtualBox and have fun. > > You can log in as root with no password (via virtual console or via SSH). > The system IP address is IP 192.168.56.66/24. > There are 16 ada(4) disks to play with. For example: > > zfsv28:root:~# zpool create tank raidz3 ada{0,1,2,3,4,5,6,7} raidz3 ada{8,9,10,11,12,13,14,15} > zfsv28:root:~# zpool status > pool: tank > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > raidz3-0 ONLINE 0 0 0 > ada0 ONLINE 0 0 0 > ada1 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 > ada4 ONLINE 0 0 0 > ada5 ONLINE 0 0 0 > ada6 ONLINE 0 0 0 > ada7 ONLINE 0 0 0 > raidz3-1 ONLINE 0 0 0 > ada8 ONLINE 0 0 0 > ada9 ONLINE 0 0 0 > ada10 ONLINE 0 0 0 > ada11 ONLINE 0 0 0 > ada12 ONLINE 0 0 0 > ada13 ONLINE 0 0 0 > ada14 ONLINE 0 0 0 > ada15 ONLINE 0 0 0 > > errors: No known data errors > > Hi, I would like to try ZFS + VirtualBox but I have got problems: 1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux I tried import that file in my VirtualBox but I have got error: Failed to import appliance. /home/peter/FreeBSD/zfsv28.ovf Too many IDE controllers in OVF; import facility only supports one. 2) I tried to install VirtualBox under 64-bit FreeBSD 9.0-CURRENT #2 [root@server /usr/ports/emulators/virtualbox-ose]# make Requires 32-bit libraries installed under /usr/lib32. Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. How can I fix that error in FreeBSD? Peter From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 16:35:19 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFDA1106566C for ; Fri, 3 Sep 2010 16:35:19 +0000 (UTC) (envelope-from gull@gull.us) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id AE10D8FC16 for ; Fri, 3 Sep 2010 16:35:19 +0000 (UTC) Received: by vws7 with SMTP id 7so1635709vws.13 for ; Fri, 03 Sep 2010 09:35:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.251.197 with SMTP id mt5mr899462qcb.131.1283530088652; Fri, 03 Sep 2010 09:08:08 -0700 (PDT) Received: by 10.229.214.199 with HTTP; Fri, 3 Sep 2010 09:08:08 -0700 (PDT) X-Originating-IP: [69.91.158.135] In-Reply-To: References: Date: Fri, 3 Sep 2010 09:08:08 -0700 Message-ID: From: David Brodbeck To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Fri, 03 Sep 2010 16:35:20 -0000 (Note: I originally posted this to freebsd-questions, and it was suggested I take it here.) While doing some interoperability testing between Linux and FreeBSD, I came up with this unusual issue. =A0I could use some help figuring out if this is a bug, and if so, where to file it. =A0Here's the scenario: - FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4. - Linux client (I've tested with RHEL 5.4 and Debian Lenny) mounting said filesystem with NFSv4. - A user on the Linux client does a Subversion checkout onto the mounted filesystem. At the end of the checkout, access to the filesystem hangs. =A0nfsd on the FreeBSD server and rpciod on the Linux client seem to be in a tight loop, and there's lots of network traffic between them. =A0I can reproduce this every time. The problem does not occur if the backing filesystem is UFS instead of ZFS, if NFSv3 is used instead of NFSv4, or if the client is FreeBSD instead of Linux. From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 16:52:11 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B34010656A5; Fri, 3 Sep 2010 16:52:11 +0000 (UTC) (envelope-from peter@3mail4.co.uk) Received: from mail4.morpheushosting.sk (mail4.morpheushosting.sk [69.60.120.12]) by mx1.freebsd.org (Postfix) with ESMTP id 1F48C8FC14; Fri, 3 Sep 2010 16:52:10 +0000 (UTC) Received: from [192.168.1.5] (cpc14-know8-0-0-cust118.know.cable.virginmedia.com [82.46.228.119]) (authenticated bits=0) by mail4.morpheushosting.sk (8.14.4/8.14.4) with ESMTP id o83GptoW005612; Fri, 3 Sep 2010 18:52:10 +0200 (CEST) (envelope-from peter@3mail4.co.uk) Message-ID: <4C81277A.60407@3mail4.co.uk> Date: Fri, 03 Sep 2010 17:51:06 +0100 From: "Peter Reo Molnar, 64-bit FreeBSD 9.0" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100713 Thunderbird/3.0.6 MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20100831215915.GE1932@garage.freebsd.pl> <20100902214823.GB2542@garage.freebsd.pl> <4C811954.5040602@3mail4.co.uk> In-Reply-To: <4C811954.5040602@3mail4.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-100.5 required=5.1 tests=BAYES_00, RCVD_IN_BRBL_LASTEXT,RCVD_IN_SORBS_DUL,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail4.morpheushosting.sk Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 16:52:11 -0000 On 03/09/10 16:50, Peter Molnar, BSD wrote: > On 02/09/10 22:48, Pawel Jakub Dawidek wrote: >> On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote: >> [...] >>> Ok, now that I know you read everything carefully, here is the patch: >>> >>> http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 >> Now it is even easier to test new ZFS! :) >> >> Here you can find VirtualBox Appliance (113MB) with >> FreeBSD 9-CURRENT and ZFSv28: >> >> http://people.freebsd.org/~pjd/misc/FreeBSD9_ZFSv28_0.1.tgz >> >> Untar it, import it (zfsv28.ovf) to VirtualBox and have fun. >> >> You can log in as root with no password (via virtual console or via >> SSH). >> The system IP address is IP 192.168.56.66/24. >> There are 16 ada(4) disks to play with. For example: >> >> zfsv28:root:~# zpool create tank raidz3 ada{0,1,2,3,4,5,6,7} >> raidz3 ada{8,9,10,11,12,13,14,15} >> zfsv28:root:~# zpool status >> pool: tank >> state: ONLINE >> scan: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> tank ONLINE 0 0 0 >> raidz3-0 ONLINE 0 0 0 >> ada0 ONLINE 0 0 0 >> ada1 ONLINE 0 0 0 >> ada2 ONLINE 0 0 0 >> ada3 ONLINE 0 0 0 >> ada4 ONLINE 0 0 0 >> ada5 ONLINE 0 0 0 >> ada6 ONLINE 0 0 0 >> ada7 ONLINE 0 0 0 >> raidz3-1 ONLINE 0 0 0 >> ada8 ONLINE 0 0 0 >> ada9 ONLINE 0 0 0 >> ada10 ONLINE 0 0 0 >> ada11 ONLINE 0 0 0 >> ada12 ONLINE 0 0 0 >> ada13 ONLINE 0 0 0 >> ada14 ONLINE 0 0 0 >> ada15 ONLINE 0 0 0 >> >> errors: No known data errors >> > Hi, > I would like to try ZFS + VirtualBox but I have got problems: > > > 1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 > x86_64 GNU/Linux > > I tried import that file in my VirtualBox but I have got error: > Failed to import appliance. > /home/peter/FreeBSD/zfsv28.ovf > Too many IDE controllers in OVF; import facility only supports one. > > > 2) I tried to install VirtualBox under 64-bit FreeBSD 9.0-CURRENT #2 > > [root@server /usr/ports/emulators/virtualbox-ose]# make > Requires 32-bit libraries installed under /usr/lib32. > Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 > *** Error code 1 > > Stop in /usr/ports/emulators/virtualbox-ose. > *** Error code 1 > > Stop in /usr/ports/emulators/virtualbox-ose. > > How can I fix that error in FreeBSD? > > > Peter > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" I forgot reading sorry for bother... cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 Peter From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 16:53:21 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AAB11065697; Fri, 3 Sep 2010 16:53:21 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5EBD58FC1E; Fri, 3 Sep 2010 16:53:20 +0000 (UTC) Received: by fxm4 with SMTP id 4so1450042fxm.13 for ; Fri, 03 Sep 2010 09:53:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=yIp+Ym5b2Hg8+Ds8upZ1wBGdyIzDIDxsZzFbrZK6r6E=; b=XAS5f9/NPWBrYaQu5zZuMFp+0WZefWuiH8SG4fiAE3g65I5VQwaKoEXnV17KZy72Bk JRQ2Kc+FXJ3Zs+Dzz+f7PraQFBzjVl3Kw81Hk7sBgB8/xennlbwy3Bw4X3754AEjuHL0 DWMnuXL5Nm/iEYmz6C6ufNLtiGA63ljzrvke4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=fjyVbbexNBSHogS3T7vNeLSJBnNctaZIqDhrTZVNDu4ShFEQE/aQvh/QUnJkI1U4ls NQR15TapPlCGeEyVFgyo5zIQB7+DliasukQKAzWWV5qg5b6ab0ISkpO2w7h2BxoTIIOY la2budeMS2fTdJVgltqMIxQx0SBnxrrAoFGAs= Received: by 10.223.119.147 with SMTP id z19mr1071674faq.4.1283532799385; Fri, 03 Sep 2010 09:53:19 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-137-20.dsl.klmzmi.sbcglobal.net [99.181.137.20]) by mx.google.com with ESMTPS id k15sm973998fai.40.2010.09.03.09.53.17 (version=SSLv3 cipher=RC4-MD5); Fri, 03 Sep 2010 09:53:18 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C8127FC.7020801@DataIX.net> Date: Fri, 03 Sep 2010 12:53:16 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100806 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: "Peter Molnar, BSD" References: <20100831215915.GE1932@garage.freebsd.pl> <20100902214823.GB2542@garage.freebsd.pl> <4C811954.5040602@3mail4.co.uk> In-Reply-To: <4C811954.5040602@3mail4.co.uk> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 16:53:21 -0000 On 09/03/2010 11:50, Peter Molnar, BSD wrote: > Requires 32-bit libraries installed under /usr/lib32. > Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 Did you happen to see the above ? -- jhell,v From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 17:02:59 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 042B510656D3; Fri, 3 Sep 2010 17:02:59 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id A36AB8FC17; Fri, 3 Sep 2010 17:02:58 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 6BF22456B1; Fri, 3 Sep 2010 19:02:56 +0200 (CEST) Received: from localhost (pdawidek.whl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 9EB3E45684; Fri, 3 Sep 2010 19:02:51 +0200 (CEST) Date: Fri, 3 Sep 2010 19:02:41 +0200 From: Pawel Jakub Dawidek To: "Peter Molnar, BSD" Message-ID: <20100903170241.GF1780@garage.freebsd.pl> References: <20100831215915.GE1932@garage.freebsd.pl> <20100902214823.GB2542@garage.freebsd.pl> <4C811954.5040602@3mail4.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BRE3mIcgqKzpedwo" Content-Disposition: inline In-Reply-To: <4C811954.5040602@3mail4.co.uk> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=4.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 17:02:59 -0000 --BRE3mIcgqKzpedwo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 03, 2010 at 04:50:44PM +0100, Peter Molnar, BSD wrote: > Hi, > I would like to try ZFS + VirtualBox but I have got problems: >=20 >=20 > 1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010=20 > x86_64 GNU/Linux >=20 > I tried import that file in my VirtualBox but I have got error: > Failed to import appliance. > /home/peter/FreeBSD/zfsv28.ovf > Too many IDE controllers in OVF; import facility only supports one. Which VirtualBox version do you use? 3.2.8? Exporting appliances is a bit broken (if you have more than one disk, it will point all disks at the last one from configuration), so I had to edit .ovf file manually to fix this. Maybe I messed something up, but I was able to successfully import it before publishing it. PS. I waited for so long for decent virtualization software for FreeBSD, and I must say VirtualBox is really great, and free, and open-source Are you reading this, VMWare? --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --BRE3mIcgqKzpedwo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkyBKjEACgkQForvXbEpPzRfNgCdH+kqRa62Hy0+V49KxZCfVkIp jg4AoM7iyd+b5QHwJ5kZ4VJ72bh6RKqZ =SKsL -----END PGP SIGNATURE----- --BRE3mIcgqKzpedwo-- From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 17:30:06 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D25910656BD for ; Fri, 3 Sep 2010 17:30:06 +0000 (UTC) (envelope-from julian@elischer.org) Received: from out-0.mx.aerioconnect.net (out-0-36.mx.aerioconnect.net [216.240.47.96]) by mx1.freebsd.org (Postfix) with ESMTP id D3D848FC16 for ; Fri, 3 Sep 2010 17:30:03 +0000 (UTC) Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160]) by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id o83HDvPe007285; Fri, 3 Sep 2010 10:13:57 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id D4E842D6014; Fri, 3 Sep 2010 10:13:56 -0700 (PDT) Message-ID: <4C812CEC.8080309@elischer.org> Date: Fri, 03 Sep 2010 10:14:20 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: David Brodbeck References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51 Cc: freebsd-fs@freebsd.org Subject: Re: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Fri, 03 Sep 2010 17:30:06 -0000 On 9/3/10 9:08 AM, David Brodbeck wrote: > (Note: I originally posted this to freebsd-questions, and it was > suggested I take it here.) > > While doing some interoperability testing between Linux and FreeBSD, I > came up with this unusual issue. I could use some help figuring out > if this is a bug, and if so, where to file it. Here's the scenario: > > - FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4. to help change and test things try using ZFS V28 with the virtualbox virtual machine that pjd announced yesterday. --Quote-- Here you can find VirtualBox Appliance (113MB) with FreeBSD 9-CURRENT and ZFSv28: http://people.freebsd.org/~pjd/misc/FreeBSD9_ZFSv28_0.1.tgz Untar it, import it (zfsv28.ovf) to VirtualBox and have fun. ---- In fact having a virtualbox 9.0 machine may help solve things anyhow as 9.0 has new nfs code too. > - Linux client (I've tested with RHEL 5.4 and Debian Lenny) mounting > said filesystem with NFSv4. > - A user on the Linux client does a Subversion checkout onto the > mounted filesystem. > > At the end of the checkout, access to the filesystem hangs. nfsd on > the FreeBSD server and rpciod on the Linux client seem to be in a > tight loop, and there's lots of network traffic between them. I can > reproduce this every time. > > The problem does not occur if the backing filesystem is UFS instead of > ZFS, if NFSv3 is used instead of NFSv4, or if the client is FreeBSD > instead of Linux. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 18:01:43 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6C4610656C1 for ; Fri, 3 Sep 2010 18:01:43 +0000 (UTC) (envelope-from gull@gull.us) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id A8FBA8FC1A for ; Fri, 3 Sep 2010 18:01:43 +0000 (UTC) Received: by qwg5 with SMTP id 5so2198965qwg.13 for ; Fri, 03 Sep 2010 11:01:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.61.12 with SMTP id r12mr183563qah.373.1283536902758; Fri, 03 Sep 2010 11:01:42 -0700 (PDT) Received: by 10.229.214.199 with HTTP; Fri, 3 Sep 2010 11:01:42 -0700 (PDT) X-Originating-IP: [69.91.158.135] In-Reply-To: <4C812CEC.8080309@elischer.org> References: <4C812CEC.8080309@elischer.org> Date: Fri, 3 Sep 2010 11:01:42 -0700 Message-ID: From: David Brodbeck To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Fri, 03 Sep 2010 18:01:44 -0000 On Fri, Sep 3, 2010 at 10:14 AM, Julian Elischer wrot= e: > On 9/3/10 9:08 AM, David Brodbeck wrote: >> >> (Note: I originally posted this to freebsd-questions, and it was >> suggested I take it here.) >> >> While doing some interoperability testing between Linux and FreeBSD, I >> came up with this unusual issue. =A0I could use some help figuring out >> if this is a bug, and if so, where to file it. =A0Here's the scenario: >> >> - FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4. > > to help change and test things > try using ZFS V28 with the virtualbox virtual machine that pjd announced > yesterday. I just grabbed it and slotted it into my VirtualBox test network. I need a little help getting nfs going, though. I'm getting the following error: KLD nfslockd.ko: depends on nfs - not available or version mismatch KLD nfsd.ko: depends on nfslockd - not available or version mismatch mountd: NFS server is not available Do I need to grab the source and build a new kernel with NFS enabled? From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 19:24:52 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D40C610656C8 for ; Fri, 3 Sep 2010 19:24:52 +0000 (UTC) (envelope-from julian@elischer.org) Received: from out-0.mx.aerioconnect.net (out-0-38.mx.aerioconnect.net [216.240.47.98]) by mx1.freebsd.org (Postfix) with ESMTP id B3EA28FC0A for ; Fri, 3 Sep 2010 19:24:52 +0000 (UTC) Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160]) by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id o83JOpi4013222; Fri, 3 Sep 2010 12:24:51 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id E6E3F2D6019; Fri, 3 Sep 2010 12:24:50 -0700 (PDT) Message-ID: <4C814B9A.5030109@elischer.org> Date: Fri, 03 Sep 2010 12:25:14 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: David Brodbeck References: <4C812CEC.8080309@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51 Cc: freebsd-fs@freebsd.org Subject: Re: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Fri, 03 Sep 2010 19:24:52 -0000 On 9/3/10 11:01 AM, David Brodbeck wrote: > On Fri, Sep 3, 2010 at 10:14 AM, Julian Elischer wrote: >> On 9/3/10 9:08 AM, David Brodbeck wrote: >>> >>> (Note: I originally posted this to freebsd-questions, and it was >>> suggested I take it here.) >>> >>> While doing some interoperability testing between Linux and FreeBSD, I >>> came up with this unusual issue. I could use some help figuring out >>> if this is a bug, and if so, where to file it. Here's the scenario: >>> >>> - FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4. >> >> to help change and test things >> try using ZFS V28 with the virtualbox virtual machine that pjd announced >> yesterday. > > I just grabbed it and slotted it into my VirtualBox test network. I > need a little help getting nfs going, though. I'm getting the > following error: > > KLD nfslockd.ko: depends on nfs - not available or version mismatch > KLD nfsd.ko: depends on nfslockd - not available or version mismatch > mountd: NFS server is not available > > Do I need to grab the source and build a new kernel with NFS enabled? you should be able to find a kernel module to do it.. maybe pjd has it lying around in his build tree, or maybe it's in /boot/kernel on the image? of course a new kernel might work too. does he have sources in his image? > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 19:54:53 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98CF51065695 for ; Fri, 3 Sep 2010 19:54:53 +0000 (UTC) (envelope-from gull@gull.us) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 5BCA68FC13 for ; Fri, 3 Sep 2010 19:54:53 +0000 (UTC) Received: by qyk31 with SMTP id 31so394723qyk.13 for ; Fri, 03 Sep 2010 12:54:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.65.228 with SMTP id k36mr378182qai.35.1283543692252; Fri, 03 Sep 2010 12:54:52 -0700 (PDT) Received: by 10.229.214.199 with HTTP; Fri, 3 Sep 2010 12:54:52 -0700 (PDT) X-Originating-IP: [69.91.158.135] In-Reply-To: <4C814B9A.5030109@elischer.org> References: <4C812CEC.8080309@elischer.org> <4C814B9A.5030109@elischer.org> Date: Fri, 3 Sep 2010 12:54:52 -0700 Message-ID: From: David Brodbeck To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Fri, 03 Sep 2010 19:54:53 -0000 On Fri, Sep 3, 2010 at 12:25 PM, Julian Elischer wrot= e: > On 9/3/10 11:01 AM, David Brodbeck wrote: >> >> On Fri, Sep 3, 2010 at 10:14 AM, Julian Elischer >> =A0wrote: >>> to help change and test things >>> try using ZFS V28 with the virtualbox virtual machine that pjd announce= d >>> yesterday. >> >> I just grabbed it and slotted it into my VirtualBox test network. =A0I >> need a little help getting nfs going, though. =A0I'm getting the >> following error: >> >> KLD nfslockd.ko: depends on nfs - not available or version mismatch >> KLD nfsd.ko: depends on nfslockd - not available or version mismatch >> mountd: NFS server is not available >> >> Do I need to grab the source and build a new kernel with NFS enabled? > > you should be able to find a kernel module to do it.. > maybe pjd has it lying around in his build tree, or maybe it's in > /boot/kernel on the image? > > of course a new kernel might work too. > does he have sources in his image? No, /usr/src/sys is a symlink to /mnt/src/zfs/sys. I suspect he left that out of the image to make it a smaller download; I know I probably would have. From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 21:30:03 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F0EF10656F1 for ; Fri, 3 Sep 2010 21:30:03 +0000 (UTC) (envelope-from julian@elischer.org) Received: from out-0.mx.aerioconnect.net (outa.internet-mail-service.net [216.240.47.224]) by mx1.freebsd.org (Postfix) with ESMTP id 3C7DB8FC1B for ; Fri, 3 Sep 2010 21:30:03 +0000 (UTC) Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160]) by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id o83LA31n018488; Fri, 3 Sep 2010 14:10:04 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id 715422D6011; Fri, 3 Sep 2010 14:10:01 -0700 (PDT) Message-ID: <4C816441.30409@elischer.org> Date: Fri, 03 Sep 2010 14:10:25 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: David Brodbeck References: <4C812CEC.8080309@elischer.org> <4C814B9A.5030109@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51 Cc: freebsd-fs@freebsd.org Subject: Re: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Fri, 03 Sep 2010 21:30:03 -0000 On 9/3/10 12:54 PM, David Brodbeck wrote: >>> >>> KLD nfslockd.ko: depends on nfs - not available or version mismatch >>> KLD nfsd.ko: depends on nfslockd - not available or version mismatch >>> mountd: NFS server is not available >>> >>> Do I need to grab the source and build a new kernel with NFS enabled? >> >> you should be able to find a kernel module to do it.. >> maybe pjd has it lying around in his build tree, or maybe it's in >> /boot/kernel on the image? >> >> of course a new kernel might work too. >> does he have sources in his image? > > No, /usr/src/sys is a symlink to /mnt/src/zfs/sys. I suspect he left > that out of the image to make it a smaller download; I know I probably > would have. given that it's a new -current, you maybe able to just grab a -current tree and make the missing modules > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 22:42:21 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D82210656C5 for ; Fri, 3 Sep 2010 22:42:21 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id CB95E8FC0A for ; Fri, 3 Sep 2010 22:42:20 +0000 (UTC) Received: by vws7 with SMTP id 7so1876173vws.13 for ; Fri, 03 Sep 2010 15:42:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=6WdaHN1Yrpjtv28dk6HWjockPr3iapLBT3sRc3idi1M=; b=TK4+y/IVdnNLnQ/TM2EVXkR7Bg9oUfWnZjXjfMly7w8HSkZdsef4avDGJV5WF/jhQY chLkNyOwCWsSwzfQZcSNrAvSe60PB1PF06/0AVmvkx42Kp9H6ZYM/oVdBBV1/qrjSWd0 v1DN5Amy8TjJN1sd1rd5KERmR86zpcvM9Ro2w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=l0RTlWSWc4f4NmrbFhOymor7sKM9Ln7YBK08/qN91Ss7lpeIoibxQxbUBlnQV4uNjs 9QX2zv8zVb88aabKBViuKCjjdi9rAS3t0FfImnKKW9kmfYmzwHu2VlwlmDhOTsYVsTPe CMadBZjZrSTN/P0vJjtM48rbvT61gzqw6C2M0= MIME-Version: 1.0 Received: by 10.220.128.138 with SMTP id k10mr713457vcs.256.1283552427592; Fri, 03 Sep 2010 15:20:27 -0700 (PDT) Received: by 10.220.192.194 with HTTP; Fri, 3 Sep 2010 15:20:27 -0700 (PDT) Date: Fri, 3 Sep 2010 18:20:27 -0400 Message-ID: From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: ZFS v28 is ready for wider testing X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 22:42:21 -0000 PJD, MM, et al... > This patchset is also a message we, as the FreeBSD project, would like > to send to our users: Eventhough OpenSolaris is dead, the ZFS file > system is going to stay in FreeBSD. At this point we have quite a few > developers involved in ZFS on FreeBSD as well as serveral companies. > We are also looking forward to work with IllumOS. ... > The patch I want to publish contains everything what Sun and Oracle > published so far. It is the most recent version you can get. I don't think the importance of this status and future work prospects can be understated :) And with the community now seemingly basing on the last ON commit from OpenSolaris before they went closed, that leaves at least three OS's soon able to interop with ZFS at the same level: [Open]Solaris, IllumOS, FreeBSD... and perhaps even Linux. Sure, a lot featurewise [big chunks such as BP rewrite and crypto] still might depend on Oracle follow through and publishing its code after binary releases. Yet even without that, a possible common community branch would be a good thing. And somehow, with luck, maybe the future Oracle stuff will still make it into open ZFS and vice versa [1]. > The boot code is not updated at all, so booting off of ZFS doesn't > currently work. As always, it will in time I'm sure. Thank you! PS: I just dropped another gig of ram in a one gig box and haven't had a ZFS lockup or kernel out of ram process kill yet, sweet! i386 RELENG_8 GENERIC 20100726 # modified vm.kmem_size=650000000 # default vm.kmem_size_max: 335544320 vm.kvm_free: 62910464 vm.kvm_size: 1073737728 vfs.zfs.arc_max: 406250000 [1] "We will have a technology partner program to permit our industry partners full access to the in-development Solaris source code through the Oracle Technology Network (OTN). This will include both early access to code and binaries, as well as contributions to us where that is appropriate." From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 23:41:07 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC61510656C1 for ; Fri, 3 Sep 2010 23:41:07 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id AB79D8FC1A for ; Fri, 3 Sep 2010 23:41:07 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAGokgUyDaFvO/2dsb2JhbACDGJ5wrWmRdIEigVaBUHMEihk X-IronPort-AV: E=Sophos;i="4.56,315,1280721600"; d="scan'208";a="92787044" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 03 Sep 2010 19:41:05 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 0006EB3F20; Fri, 3 Sep 2010 19:41:05 -0400 (EDT) Date: Fri, 3 Sep 2010 19:41:05 -0400 (EDT) From: Rick Macklem To: David Brodbeck Message-ID: <697498209.486386.1283557265921.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Fri, 03 Sep 2010 23:41:08 -0000 > (Note: I originally posted this to freebsd-questions, and it was > suggested I take it here.) > > While doing some interoperability testing between Linux and FreeBSD, I > came up with this unusual issue. I could use some help figuring out > if this is a bug, and if so, where to file it. Here's the scenario: > > - FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4. > - Linux client (I've tested with RHEL 5.4 and Debian Lenny) mounting > said filesystem with NFSv4. > - A user on the Linux client does a Subversion checkout onto the > mounted filesystem. > > At the end of the checkout, access to the filesystem hangs. nfsd on > the FreeBSD server and rpciod on the Linux client seem to be in a > tight loop, and there's lots of network traffic between them. I can > reproduce this every time. > > The problem does not occur if the backing filesystem is UFS instead of > ZFS, if NFSv3 is used instead of NFSv4, or if the client is FreeBSD > instead of Linux. > If you email me a packet capture (probably only need a few seconds when it is the tight loop), I can look at it in wireshark. Something like "tcpdump -s 0 -w xxx host " run on the server should do it. Then email me "xxx" as an attachment. However, I don't know diddly w.r.t. ZFS, so I don't know how much I'll be able to help? rick ps: You either need the correct kernel modules or a kernel built with "options NFSD" to run the exp. server (which is the one that does NFSv4). From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 00:08:50 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CD3C10656A9 for ; Sat, 4 Sep 2010 00:08:50 +0000 (UTC) (envelope-from gull@gull.us) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 45C6C8FC12 for ; Sat, 4 Sep 2010 00:08:49 +0000 (UTC) Received: by qwg5 with SMTP id 5so2554070qwg.13 for ; Fri, 03 Sep 2010 17:08:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.10.217 with SMTP id q25mr780780qcq.274.1283558928457; Fri, 03 Sep 2010 17:08:48 -0700 (PDT) Received: by 10.229.214.199 with HTTP; Fri, 3 Sep 2010 17:08:48 -0700 (PDT) X-Originating-IP: [69.91.158.135] In-Reply-To: <697498209.486386.1283557265921.JavaMail.root@erie.cs.uoguelph.ca> References: <697498209.486386.1283557265921.JavaMail.root@erie.cs.uoguelph.ca> Date: Fri, 3 Sep 2010 17:08:48 -0700 Message-ID: From: David Brodbeck To: Rick Macklem Content-Type: multipart/mixed; boundary=0016364ed9a0faa338048f63d9fa X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Sat, 04 Sep 2010 00:08:50 -0000 --0016364ed9a0faa338048f63d9fa Content-Type: text/plain; charset=ISO-8859-1 On Fri, Sep 3, 2010 at 4:41 PM, Rick Macklem wrote: >> (Note: I originally posted this to freebsd-questions, and it was >> suggested I take it here.) >> >> While doing some interoperability testing between Linux and FreeBSD, I >> came up with this unusual issue. I could use some help figuring out >> if this is a bug, and if so, where to file it. Here's the scenario: >> >> - FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4. >> - Linux client (I've tested with RHEL 5.4 and Debian Lenny) mounting >> said filesystem with NFSv4. >> - A user on the Linux client does a Subversion checkout onto the >> mounted filesystem. >> >> At the end of the checkout, access to the filesystem hangs. nfsd on >> the FreeBSD server and rpciod on the Linux client seem to be in a >> tight loop, and there's lots of network traffic between them. I can >> reproduce this every time. >> >> The problem does not occur if the backing filesystem is UFS instead of >> ZFS, if NFSv3 is used instead of NFSv4, or if the client is FreeBSD >> instead of Linux. >> > If you email me a packet capture (probably only need a few seconds > when it is the tight loop), I can look at it in wireshark. > Something like "tcpdump -s 0 -w xxx host " run on the server > should do it. Then email me "xxx" as an attachment. Here's a capture for you. This is a Linux client (192.168.30.30) working against a FreeBSD 8.1-RELEASE server (192.168.30.102). If you need a capture using FreeBSD 9, that'll require some more setup on my part and I won't be able to get to it until Monday. --0016364ed9a0faa338048f63d9fa-- From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 00:25:47 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22CBF1065694 for ; Sat, 4 Sep 2010 00:25:47 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 07ACD8FC08 for ; Sat, 4 Sep 2010 00:25:46 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1OrgZl-000LvM-PK; Sat, 04 Sep 2010 00:25:45 +0000 Date: Sat, 04 Sep 2010 09:25:44 +0900 Message-ID: From: Randy Bush To: Marco van Tol In-Reply-To: <20100903130646.GD19666@tolstoy.tols.org> References: <20100903130646.GD19666@tolstoy.tols.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-fs Subject: Re: just another sad story in zfs tuning city X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 00:25:47 -0000 >> i am tempted to just boot without the zfs memory hacks in loader >> conf. any warnings on doing so? any other clues also gladly >> accepted. > > Sticking a wet finger in the air, and assuming /dev/mirror/boota holds a > UFS filesystem that's just used to boot from I'd say give kmem_size 1.5x > physical, arc_max 1.0x physical, and arc_min 0.5x physical memory to > have it compete with the UFS page cache. After that applications that > run can't use more then (0.5x physical memory plus swap space). thanks. it ain't crashed yet. running some large builds to see how it performs. but what about just taking the defaults, no parms? one would hope that this would be successful, as that is the simple path. randy From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 00:33:35 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6925610656B5 for ; Sat, 4 Sep 2010 00:33:35 +0000 (UTC) (envelope-from prvs=18630f88c7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 0622A8FC13 for ; Sat, 4 Sep 2010 00:33:34 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 04 Sep 2010 01:22:47 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 04 Sep 2010 01:22:47 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50011181479.msg for ; Sat, 04 Sep 2010 01:22:47 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=18630f88c7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@FreeBSD.ORG Message-ID: <5DB6E7C798E44D33A05673F4B773405E@multiplay.co.uk> From: "Steven Hartland" To: Date: Sat, 4 Sep 2010 01:22:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 Cc: Subject: zfs very poor performance compared to ufs due to lack of cache? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 00:33:35 -0000 When upgrading from 8.0 on our stream server to 8.1 we decided to go for zfs to eliminate the costly fsck times should we experience any unexpected reboots on the machine as it has a sizable RAID of 1.6TB. After doing this all seemed good till after our latest event which generated a significant amount of interest and hence the stream server started to get quite a few requests. Basic install is 8.1 amd64 on a dual 2.8 Xeon with 4GB RAM and areca controller with 6 disk in RAID 6. On that the machine runs nginx with the mp4 module to sudo stream files. Previously this machine didn't have any problem dealing with significant numbers of clients as long as the clients where largely playing the same files ( which are typically quite large 1GB+ ) however after the update to zfs it seems to be really struggling with disk IO, maxing out the disk for large periods of time even when all the "active" files should be able to fit easily into ram. After digging around it seems that the default config is very conservative, not the case with ufs which seems to use all free ram as cache which is exactly what we want as nginx uses so little ram there's nothing else for it to do. So now we've added the following to loader.conf vfs.zfs.cache_flush_disable=1 # Battery Backed RAID vfs.zfs.prefetch_disable=0 # Large Streaming files seems like this would be good vm.kmem_size="6G" # Physical Memory * 1.5 as recommend in several places vfs.zfs.arc_max="3584M" # Most of the available RAM I thought this would help but apparently not, zfs still only seems to want to use a minimal amount of ram for cache as shown by arc_summary ARC Size: Current Size: 12.50% 447.97M (arcsize) Target Size: (Adaptive) 12.50% 448.00M (c) Min Size (Hard Limit): 12.50% 448.00M (c_min) Max Size (High Water): ~8:1 3584.00M (c_max) For reference top shows:- Mem: 42M Active, 3129M Inact, 565M Wired, 3188K Cache, 19M Buf, 203M Free Swap: 4096M Total, 1180K Used, 4095M Free So what are we missing and how to we get zfs to perform like ufs and use all free ram as cache? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 00:55:08 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C68B610656A6 for ; Sat, 4 Sep 2010 00:55:08 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 7E2DC8FC22 for ; Sat, 4 Sep 2010 00:55:08 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAP41gUyDaFvO/2dsb2JhbACDGJ5xrUiRbYRIcwSKGQ X-IronPort-AV: E=Sophos;i="4.56,316,1280721600"; d="scan'208";a="92791484" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 03 Sep 2010 20:55:07 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 6AC7BB3F25; Fri, 3 Sep 2010 20:55:07 -0400 (EDT) Date: Fri, 3 Sep 2010 20:55:07 -0400 (EDT) From: Rick Macklem To: David Brodbeck Message-ID: <929991361.487274.1283561707352.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_487273_1760299342.1283561707351" X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: Weird Linux - FreeBSD/ZFS NFSv4 interoperability 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: Sat, 04 Sep 2010 00:55:08 -0000 ------=_Part_487273_1760299342.1283561707351 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit > > Here's a capture for you. This is a Linux client (192.168.30.30) > working against a FreeBSD 8.1-RELEASE server (192.168.30.102). If you > need a capture using FreeBSD 9, that'll require some more setup on my > part and I won't be able to get to it until Monday. Ok, The server is returning NFS4ERR_OLD_STATEID, which means that the seqid# inside the stateid is out of date. I think the original intent of this was to be a debugging aid for client writers, but a discussion on the nfsv4 mailing list pretty much concluded that it was useless. (It is definitely the case that the server doesn't care. A separate seqd# is used to order the open/lock/close ops.) So, please try the attached little patch that just disables the server check for this case for Close. (The line #s will be different than 8.1, but all it is doing is commenting out the test for this case in nfsrv_openupdate(), if the patch won't apply directly.) I'm almost at the point where I'll just disable all the cases that generate NFS4ERR_OLDSTATEID in the server. (It is already disabled for Read/Write/Setattr of size unless you tweak a variable.) Please let me know if it helps, rick ------=_Part_487273_1760299342.1283561707351 Content-Type: text/x-patch; name=nfsdstate.patch Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=nfsdstate.patch LS0tIG5mc19uZnNkc3RhdGUuYy5zYXYJMjAxMC0wOS0wMyAxOTozNTo0NC4wMDAwMDAwMDAgLTA0 MDAKKysrIG5mc19uZnNkc3RhdGUuYwkyMDEwLTA5LTAzIDE5OjQwOjQwLjAwMDAwMDAwMCAtMDQw MApAQCAtMjg3Myw5ICsyODczLDExIEBACiAJaWYgKCFlcnJvcikKIAkJZXJyb3IgPSBuZnNydl9j aGVja3NlcWlkKG5kLCBuZXdfc3RwLT5sc19zZXEsCiAJCSAgICBzdHAtPmxzX29wZW5vd25lciwg bmV3X3N0cC0+bHNfb3ApOworI2lmZGVmIG5vdG5vdwogCWlmICghZXJyb3IgJiYgc3RwLT5sc19z dGF0ZWlkLnNlcWlkICE9IG5ld19zdHAtPmxzX3N0YXRlaWQuc2VxaWQgJiYKIAkgICAgIShuZXdf c3RwLT5sc19mbGFncyAmIE5GU0xDS19DT05GSVJNKSkKIAkJZXJyb3IgPSBORlNFUlJfT0xEU1RB VEVJRDsKKyNlbmRpZgogCWlmICghZXJyb3IgJiYgdm5vZGVfdnR5cGUodnApICE9IFZSRUcpIHsK IAkJaWYgKHZub2RlX3Z0eXBlKHZwKSA9PSBWRElSKQogCQkJZXJyb3IgPSBORlNFUlJfSVNESVI7 Cg== ------=_Part_487273_1760299342.1283561707351-- From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 01:09:44 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D9D210656D1 for ; Sat, 4 Sep 2010 01:09:44 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 22E5C8FC13 for ; Sat, 4 Sep 2010 01:09:43 +0000 (UTC) Received: by wwb18 with SMTP id 18so44996wwb.31 for ; Fri, 03 Sep 2010 18:09:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=/4uAYikoJAzJA2tUc9vqxGr5HdXmzidXtxSGchJ2Xew=; b=qXy1/59bVYurVJvSKVQ+Llzh90ZvWM9KqOcDCNQNS2zGz3xx2I0DxwCc5qqmoiNUb0 ABa9/KLhLk6Jl93McoktalGxyv/jlZF8RrVDJEbEwaqjsUe3BAtmhBJ8+SY082kXZyTV sQhF/7ik/sgpJbMgNisnA971d5yiOIR2FXhBI= 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; b=JpQe/5haQrACOmxjSUHIQyEPCbGL8+g2gYTk+tfEzsaxns6W3r0s8it6TTp7e21huT o7ItzHWNq/k7ykoAQvomviEwOEpYJrZb76x8SvGdMx/wsR0Rb6onsb/PEkrPgxlKv+AI y9XvNt0gzWD9i2sANAeSHQXiFVjSTog6xtCow= MIME-Version: 1.0 Received: by 10.216.26.194 with SMTP id c44mr698714wea.104.1283562583096; Fri, 03 Sep 2010 18:09:43 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.216.144.227 with HTTP; Fri, 3 Sep 2010 18:09:43 -0700 (PDT) In-Reply-To: <5DB6E7C798E44D33A05673F4B773405E@multiplay.co.uk> References: <5DB6E7C798E44D33A05673F4B773405E@multiplay.co.uk> Date: Fri, 3 Sep 2010 18:09:43 -0700 X-Google-Sender-Auth: L_gGwiA6gufCetvl-if7G5HRVy4 Message-ID: From: Artem Belevich To: Steven Hartland Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: zfs very poor performance compared to ufs due to lack of cache? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 01:09:44 -0000 > For reference top shows:- > Mem: 42M Active, 3129M Inact, 565M Wired, 3188K Cache, 19M Buf, 203M Free Here's your problem -- inactive list got all your memory and starved ZFS ARC. Easy workaround is to set vfs.zfs.arc_min to a value that would guarantee that ARC does not give up too much memory. Let's say - 2GB. Be warned that it would effectively make those 2GB unavailable to applications. Long term, though, there were number of patches posted on freebsd-current and freebsd-hackers recently that do improve that particular issue with ZFS. This patch in particular may help you: http://lists.freebsd.org/pipermail/freebsd-hackers/2010-August/032731.html > Swap: 4096M Total, 1180K Used, 4095M Free > > So what are we missing and how to we get zfs to perform like ufs > and use all free ram as cache? --Artem From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 11:51:38 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8A491065696; Sat, 4 Sep 2010 11:51:38 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 273B98FC19; Sat, 4 Sep 2010 11:51:38 +0000 (UTC) Received: by iwn34 with SMTP id 34so2756238iwn.13 for ; Sat, 04 Sep 2010 04:51:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=eFLx+TlBMz0Ud3UkfDf1GCrdeaPeP51pFh9vFptzriM=; b=t1+GmKf5x61alpYtjS7sp2KowJfPLecbaZPOvG/ASMjFjjAwCtxowZRDMXAhucLQHF c1Ou5rxFu0Rj4yK01/rpi/wdQI97vEhT7MVSdNMe/rSRFc5GLeFQFyBiNGvpUU3V0Os0 LV+FCzrt3AdopqAfpM+Y9UNpQNwye82+eXS0k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=a25vC4oU2ljGBxIZCOksA5Iif+o9syx/JffoX1ju3LjEkZlgGwhfMQh7+ZHfzTm/uL rOtZx2/YtuVouKRMqpka2EN84N2/nU8NjasGmyaSXBki58kFVrRBnaROF+KWaxDLKznd YcfzA13LtZyechLD7VlXtYQWVlahekQ13QWLI= Received: by 10.231.183.81 with SMTP id cf17mr2646321ibb.32.1283601097732; Sat, 04 Sep 2010 04:51:37 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-137-20.dsl.klmzmi.sbcglobal.net [99.181.137.20]) by mx.google.com with ESMTPS id r3sm3247772ibk.19.2010.09.04.04.51.35 (version=SSLv3 cipher=RC4-MD5); Sat, 04 Sep 2010 04:51:36 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C8232C6.9020108@DataIX.net> Date: Sat, 04 Sep 2010 07:51:34 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100806 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20100831215915.GE1932@garage.freebsd.pl> <20100902214823.GB2542@garage.freebsd.pl> <4C811954.5040602@3mail4.co.uk> <20100903170241.GF1780@garage.freebsd.pl> In-Reply-To: <20100903170241.GF1780@garage.freebsd.pl> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "Peter Molnar, BSD" Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 11:51:38 -0000 On 09/03/2010 13:02, Pawel Jakub Dawidek wrote: > On Fri, Sep 03, 2010 at 04:50:44PM +0100, Peter Molnar, BSD wrote: >> Hi, >> I would like to try ZFS + VirtualBox but I have got problems: >> >> >> 1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 >> x86_64 GNU/Linux >> >> I tried import that file in my VirtualBox but I have got error: >> Failed to import appliance. >> /home/peter/FreeBSD/zfsv28.ovf >> Too many IDE controllers in OVF; import facility only supports one. > > Which VirtualBox version do you use? 3.2.8? > > Exporting appliances is a bit broken (if you have more than one disk, it > will point all disks at the last one from configuration), so I had to > edit .ovf file manually to fix this. Maybe I messed something up, but I > was able to successfully import it before publishing it. > > PS. I waited for so long for decent virtualization software for FreeBSD, > and I must say VirtualBox is really great, and free, and open-source > Are you reading this, VMWare? > They will only read it if it comes with a disclaimer and they're license attached to the top along with a contract signed by you so when they disagree with it they can hand you a pink-slip with they're license attached to the top. As for VirtualBox, which is a Sun thing, gone Oratorically wrong... How long does anyone expect this technology to stick around?. -- jhell,v From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 12:09:04 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABEA210656B0 for ; Sat, 4 Sep 2010 12:09:04 +0000 (UTC) (envelope-from marco@tolstoy.tols.org) Received: from tolstoy.tols.org (tolstoy.tols.org [IPv6:2a02:898:0:20::57:1]) by mx1.freebsd.org (Postfix) with ESMTP id 445FC8FC0A for ; Sat, 4 Sep 2010 12:09:03 +0000 (UTC) Received: from tolstoy.tols.org (localhost [127.0.0.1]) by tolstoy.tols.org (8.14.4/8.14.4) with ESMTP id o84C907t040724 for ; Sat, 4 Sep 2010 12:09:00 GMT (envelope-from marco@tolstoy.tols.org) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.96.1 at tolstoy.tols.org Received: (from marco@localhost) by tolstoy.tols.org (8.14.4/8.14.4/Submit) id o84C906Q040723 for freebsd-fs@freebsd.org; Sat, 4 Sep 2010 14:09:00 +0200 (CEST) (envelope-from marco) Date: Sat, 4 Sep 2010 14:09:00 +0200 From: Marco van Tol To: freebsd-fs Message-ID: <20100904120900.GB40103@tolstoy.tols.org> Mail-Followup-To: freebsd-fs References: <20100903130646.GD19666@tolstoy.tols.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on tolstoy.tols.org Subject: Re: just another sad story in zfs tuning city X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 12:09:04 -0000 On Sat, Sep 04, 2010 at 09:25:44AM +0900, Randy Bush wrote: > >> i am tempted to just boot without the zfs memory hacks in loader > >> conf. any warnings on doing so? any other clues also gladly > >> accepted. > > > > Sticking a wet finger in the air, and assuming /dev/mirror/boota holds a > > UFS filesystem that's just used to boot from I'd say give kmem_size 1.5x > > physical, arc_max 1.0x physical, and arc_min 0.5x physical memory to > > have it compete with the UFS page cache. After that applications that > > run can't use more then (0.5x physical memory plus swap space). > > thanks. it ain't crashed yet. running some large builds to see how it > performs. > > but what about just taking the defaults, no parms? one would hope that > this would be successful, as that is the simple path. The defaults go well under what I wrote, and I'm pretty sure for good reasons. I _think_ that has to do with that the defaults have to be prepared for lots more situations then those we setup and tune the values for. And ofcourse the arc goes into wired memory as opposed to page cache in active/inactive under UFS. I'm not an expert enough to go into lots more detail, but I think what I write is accurate. :) Marco -- The first step to better times is to imagine them. - www.chinese-fortune-cookie.com From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 14:41:27 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A45E10656CB for ; Sat, 4 Sep 2010 14:41:27 +0000 (UTC) (envelope-from prvs=18630f88c7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id B953C8FC13 for ; Sat, 4 Sep 2010 14:41:26 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 04 Sep 2010 15:41:22 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 04 Sep 2010 15:41:22 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50011182480.msg for ; Sat, 04 Sep 2010 15:41:22 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=18630f88c7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Artem Belevich" References: <5DB6E7C798E44D33A05673F4B773405E@multiplay.co.uk> Date: Sat, 4 Sep 2010 15:41:26 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 Cc: freebsd-fs@freebsd.org Subject: Re: zfs very poor performance compared to ufs due to lack of cache? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 14:41:27 -0000 ----- Original Message ----- From: "Artem Belevich" >> For reference top shows:- >> Mem: 42M Active, 3129M Inact, 565M Wired, 3188K Cache, 19M Buf, 203M Free > > Here's your problem -- inactive list got all your memory and starved ZFS ARC. > Easy workaround is to set vfs.zfs.arc_min to a value that would > guarantee that ARC does not give up too much memory. Let's say - 2GB. > Be warned that it would effectively make those 2GB unavailable to > applications. > > Long term, though, there were number of patches posted on > freebsd-current and freebsd-hackers recently that do improve that > particular issue with ZFS. This patch in particular may help you: > http://lists.freebsd.org/pipermail/freebsd-hackers/2010-August/032731.html Thanks for that Artem, is there an way to tell what caused this starvation? With the machine running only nginx, which uses next to nothing, I cant think of anything which would have used the memory. Hmmm could this have been caused by nfs as the volume is shared over standard nfs as well. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 14:53:34 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D828810656A7 for ; Sat, 4 Sep 2010 14:53:34 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7F86F8FC08 for ; Sat, 4 Sep 2010 14:53:34 +0000 (UTC) Received: by gyg4 with SMTP id 4so1386686gyg.13 for ; Sat, 04 Sep 2010 07:53:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type; bh=PuYLOpaKEPRyPKZQeLSEN+72LlVdCVS3mGfWvDPnSJM=; b=qZm3ayCPJ7Y+578/d7UBwHXx4BZqvMPDLQ15LwLabtLXTqi3wToTmRWUpBaOmyEA8R FN6NepnzcOAxuAMmJeseLPdE+pbL1Ym0nIescTQaxJgR2y9R3nBiczUjDQdSpVOYqNZz X47xDLk7/LypwhiHGZSUIW0RKC5B/N7cnM3UE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type; b=rcK8yx4TYBeYHp6WuHUeXl3tDqtstQ/sUVkvqRvGhlMwS7JKnLdmW5Pq9OfeutCzoy YnmxrYSyiYUMo8TQR0FY7S279NCpDgXXrSybMVj5eH/R123gJDdxrwgkQz5iKgIJigcs y8XCppzIgm3GvzBdHmRiBaDjSOQXOEOIgaRYA= Received: by 10.151.102.21 with SMTP id e21mr389636ybm.103.1283612008315; Sat, 04 Sep 2010 07:53:28 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-137-20.dsl.klmzmi.sbcglobal.net [99.181.137.20]) by mx.google.com with ESMTPS id q25sm3719120ybk.6.2010.09.04.07.53.26 (version=SSLv3 cipher=RC4-MD5); Sat, 04 Sep 2010 07:53:27 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C825D65.3040004@DataIX.net> Date: Sat, 04 Sep 2010 10:53:25 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100806 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Artem Belevich References: <5DB6E7C798E44D33A05673F4B773405E@multiplay.co.uk> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/mixed; boundary="------------000703040900060801010300" Cc: freebsd-fs@freebsd.org Subject: Re: zfs very poor performance compared to ufs due to lack of cache? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 14:53:34 -0000 This is a multi-part message in MIME format. --------------000703040900060801010300 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/03/2010 21:09, Artem Belevich wrote: >> For reference top shows:- >> Mem: 42M Active, 3129M Inact, 565M Wired, 3188K Cache, 19M Buf, 203M Free > > Here's your problem -- inactive list got all your memory and starved ZFS ARC. > Easy workaround is to set vfs.zfs.arc_min to a value that would > guarantee that ARC does not give up too much memory. Let's say - 2GB. > Be warned that it would effectively make those 2GB unavailable to > applications. > > Long term, though, there were number of patches posted on > freebsd-current and freebsd-hackers recently that do improve that > particular issue with ZFS. This patch in particular may help you: > http://lists.freebsd.org/pipermail/freebsd-hackers/2010-August/032731.html > >> Swap: 4096M Total, 1180K Used, 4095M Free >> >> So what are we missing and how to we get zfs to perform like ufs >> and use all free ram as cache? > Attached is the needfree patch mentioned in the URL alongside a local system patch to adjust kern.maxusers to no more than 512 on systems that can support it. Modern systems would always raise to a value of 512 or more so I do not see a need to keep it limited to 384. This setting also effects the outcome of other values in the system. Not saying that these will directly help your case in anyway shape or form but if you would like to give them a shot then they are here for the taking. Apply with: cd /usr/src patch -p1 date: Fri Sep 03 12:50:37 2010 -0400 files: sys/kern/subr_param.c description: Increase maxusers to 512 by default if it equals 512 or higher. diff -r 627cf9b49e0f -r deccbf75a766 sys/kern/subr_param.c --- a/sys/kern/subr_param.c Fri Sep 03 12:42:00 2010 -0400 +++ b/sys/kern/subr_param.c Fri Sep 03 12:50:37 2010 -0400 @@ -257,8 +257,8 @@ maxusers = physpages / (2 * 1024 * 1024 / PAGE_SIZE); if (maxusers < 32) maxusers = 32; - if (maxusers > 384) - maxusers = 384; + if (maxusers > 512) + maxusers = 512; } /* --------------000703040900060801010300 Content-Type: text/plain; name="needfree.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="needfree.patch" changeset: 188:dafc39874132 user: J. Hellenthal date: Sat Sep 04 07:34:28 2010 -0400 files: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c description: PFC: r211762 arc.c needfree patch ------------------------------------------------------------------------ r211762 | avg | 2010-08-24 13:48:22 -0400 (Tue, 24 Aug 2010) | 20 lines zfs arc_reclaim_thread: no need to call arc_reclaim_needed when resetting needfree needfree is checked at the very start of arc_reclaim_needed. This change makes code easier to follow and maintain in face of potential changed in arc_reclaim_needed. Also, put the whole sub-block under _KERNEL because needfree can be set only in kernel code. To do: rename needfree to something else to aovid confusion with OpenSolaris global variable of the same name which is used in the same code, but has different meaning (page deficit). Note: I have an impression that locking around accesses to this variable as well as mutual notifications between arc_reclaim_thread and arc_lowmem are not proper. MFC after: 1 week ------------------------------------------------------------------------ diff -r 34a823aff8f6 -r dafc39874132 sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c Sat Sep 04 07:23:09 2010 -0400 +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c Sat Sep 04 07:34:28 2010 -0400 @@ -2317,12 +2317,12 @@ if (arc_eviction_list != NULL) arc_do_user_evicts(); - if (arc_reclaim_needed()) { +#ifdef _KERNEL + if (needfree) { needfree = 0; -#ifdef _KERNEL wakeup(&needfree); + } #endif - } /* block until needed, or one second, whichever is shorter */ CALLB_CPR_SAFE_BEGIN(&cpr); --------------000703040900060801010300 Content-Type: application/octet-stream; name="maxusers.patch.sig" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="maxusers.patch.sig" iQEcBAABAgAGBQJMgl1kAAoJEJBXh4mJ2FR+ztMIAJL+5MwxxHsSRmrTjt3RCtWvay7uRhnC 9HpEPJkzPNRzIwFx4ckMIuH5tMZTXHlRf6Xt0dTIYf28ExQFQyefVarMuFeK1XfESISt5PEm wDLPITr9AnEACE7IsPEpRZV0kuiPyThDybF+2eh682rPeFkHhvcNCFEkO2jpljXYdTXGbyc+ Csw2dIaMd5fFCWtXwNSCah7DoA0gsnTKRgcFJgan0/GMDLGd1N4QWTlqX0buyOGxCSDhrHZK 6vJRoMmDpJz7RzXNigiayzN8y3PgU6P2JbbHGws8edmQqWpbXHP35wmT6P5/+LhwbyplNu0U S/1U8IHFtRxTmxSL0/wGFjo= --------------000703040900060801010300 Content-Type: application/octet-stream; name="needfree.patch.sig" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="needfree.patch.sig" iQEcBAABAgAGBQJMgl1kAAoJEJBXh4mJ2FR+5ggIAJ41d2boBSnDtIXfrrWQyzvIaTV45naA Es5n94Vcx5DBkbQo915SzhOPko0l26Lkr11+oUwRpi3Cwf5ik1PaVS0CNFjZ+eCWXRBay55V AlnthIGC9K3/EbRrnuPMlKpFWbVptAOBSIRnaZVo2LU13TkkBNqFlg6AkBijcT0SCFeRVCOm xPDP/qRvOj8OEBXsbSfqC4YQajBXRy5nl7mFmK1vPfcwURG7/LUhV/jpUaCbj5QW8S58S7Zq /LxQ45DgRu5P3SK3IldeC+KJFgfxYW52zFQ9bavEuzake18OHbEFs6Qj6YiAcR0cnzA0/w9p wM6awh9TPOZ6XYaFaMgs3Ds= --------------000703040900060801010300-- From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 19:13:58 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AFD510656C1 for ; Sat, 4 Sep 2010 19:13:58 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2A57B8FC14 for ; Sat, 4 Sep 2010 19:13:57 +0000 (UTC) Received: by iwn34 with SMTP id 34so3106535iwn.13 for ; Sat, 04 Sep 2010 12:13:57 -0700 (PDT) Received: by 10.231.36.134 with SMTP id t6mr3247058ibd.128.1283626171764; Sat, 04 Sep 2010 11:49:31 -0700 (PDT) Received: from wawanesa.iciti.ca (CPE0080c8f208a5-CM001371173cf8.cpe.net.cable.rogers.com [99.246.61.82]) by mx.google.com with ESMTPS id i6sm786398iba.14.2010.09.04.11.49.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Sep 2010 11:49:30 -0700 (PDT) Message-ID: <4C8294B7.3010507@bellanet.org> Date: Sat, 04 Sep 2010 14:49:27 -0400 From: Graham Todd User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.10) Gecko/20100721 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20100831215915.GE1932@garage.freebsd.pl> <20100902214823.GB2542@garage.freebsd.pl> <4C811954.5040602@3mail4.co.uk> <20100903170241.GF1780@garage.freebsd.pl> <4C8232C6.9020108@DataIX.net> In-Reply-To: <4C8232C6.9020108@DataIX.net> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: ZFS v28 is ready for wider testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 19:13:58 -0000 On 09/04/10 07:51, jhell wrote: > On 09/03/2010 13:02, Pawel Jakub Dawidek wrote: >> >> Exporting appliances is a bit broken (if you have more than one disk, it >> will point all disks at the last one from configuration), so I had to >> edit .ovf file manually to fix this. Maybe I messed something up, but I >> was able to successfully import it before publishing it. The VM works great here. Thanks for packaging things up this way Pawel it facilitates wider testing. I am getting occasional stack backtraces on my screen when trying certain operations (e.g. zfs diff, truncate -s 200M testfile, etc.) but no crashes or serious problems. Is there any specific information or tests you'd like people to do? Thanks to you and other devs for all your careful work integrating ZFS into FreeBSD. It seems amazing that the patch for v28 *almost* even applies to 8-STABLE. cheers, >> PS. I waited for so long for decent virtualization software for FreeBSD, >> and I must say VirtualBox is really great, and free, and open-source >> Are you reading this, VMWare? The VirtualBox folks have built a pretty solid product. I am guessing good virtualization software helps with kernel development? :) > They will only read it if it comes with a disclaimer and they're license > attached to the top along with a contract signed by you so when they > disagree with it they can hand you a pink-slip with they're license > attached to the top. > > As for VirtualBox, which is a Sun thing, gone Oratorically wrong... How > long does anyone expect this technology to stick around?. It seems like a lot of people like it and the source is available under GPL so, maybe a long time ? From owner-freebsd-fs@FreeBSD.ORG Sat Sep 4 21:02:02 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E29910656B8 for ; Sat, 4 Sep 2010 21:02:02 +0000 (UTC) (envelope-from prvs=18630f88c7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 9D6178FC17 for ; Sat, 4 Sep 2010 21:02:01 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 04 Sep 2010 22:01:56 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 04 Sep 2010 22:01:56 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50011183041.msg for ; Sat, 04 Sep 2010 22:01:56 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=18630f88c7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <7EA7AD058C0143B2BF2471CC121C1687@multiplay.co.uk> From: "Steven Hartland" To: "jhell" , "Artem Belevich" References: <5DB6E7C798E44D33A05673F4B773405E@multiplay.co.uk> <4C825D65.3040004@DataIX.net> Date: Sat, 4 Sep 2010 22:01:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 Cc: freebsd-fs@freebsd.org Subject: Re: zfs very poor performance compared to ufs due to lack of cache? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 21:02:02 -0000 ----- Original Message ----- From: "jhell" > > Attached is the needfree patch mentioned in the URL alongside a local > system patch to adjust kern.maxusers to no more than 512 on systems that > can support it... Thanks, patches applied, will update once I've had chance to test. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.