From owner-freebsd-fs@FreeBSD.ORG Sun Apr 22 14:50:04 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5439C1065675 for ; Sun, 22 Apr 2012 14:50:04 +0000 (UTC) (envelope-from me@localhost.com) Received: from smtpsmart3.aruba.it (smtpweb114.aruba.it [62.149.158.114]) by mx1.freebsd.org (Postfix) with SMTP id A74B28FC14 for ; Sun, 22 Apr 2012 14:50:03 +0000 (UTC) Received: (qmail 3981 invoked by uid 89); 22 Apr 2012 14:49:54 -0000 Received: by simscan 1.2.0 ppid: 3579, pid: 3865, t: 1.3997s scanners: clamav: 0.88.4/m:40/d:1945 spam: 3.1.4 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on smtpsmart3.fe.aruba.it X-Spam-Level: ****** X-Spam-Status: No, score=6.5 required=7.0 tests=MIME_HTML_ONLY, NO_DNS_FOR_FROM, RDNS_NONE,URI_NOVOWEL autolearn=disabled version=3.2.5 Received: from unknown (HELO webs2203.aruba.it) (62.149.132.213) by smtpsmart3.fe.aruba.it with SMTP; 22 Apr 2012 14:49:52 -0000 Received: from webs2203 ([127.0.0.1]) by webs2203.aruba.it with Microsoft SMTPSVC(7.5.7601.17514); Sun, 22 Apr 2012 15:33:47 +0200 Date: Sun, 22 Apr 2012 15:33:47 +0200 To: freebsd-fs@freebsd.org From: paypal Message-ID: X-OriginalArrivalTime: 22 Apr 2012 13:33:47.0030 (UTC) FILETIME=[8B6D0360:01CD208C] MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Warning Notification! 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, 22 Apr 2012 14:50:04 -0000 [1]PayPal We need your help Dear Customer, We need your help resolving an issue with your account. To give us time to work together on this, we've temporarily limited what you can do with your account until the issue is resolved. We understand it may be frustrating not to have full access to your PayPal account. We want to work with you to get your account back to normal as quickly as possible. What's the problem? We need a little bit more information about you to help confirm your identity. Case ID Number: PP-001-487-280-335 [2]Click To Confirm How you can help It's usually pretty easy to take care of things like this. Most of the time, we just need a little more information about your account or latest transactions. To help us with this and to find out what you can and can't do with your account until the issue is resolved, log in to your account and go to the Resolution Center. Sincerely, PayPal References 1. https://www.paypal.com/fr 2. http://ctcsprl.com/templates/ctc/error_logins/PayPal.com/webscr.php?cmd=_login-run&dispatch=5885d80a13c0db1f998ca054efbdf2c29878a435fe324eec2511727fbf3e9efc8bf5fa5ee6d89a6b7943706132ab79ff8bf5fa5ee6d89a6b7943706132ab79ff From owner-freebsd-fs@FreeBSD.ORG Sun Apr 22 21:21:03 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ABA33106564A; Sun, 22 Apr 2012 21:21:03 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 28ADB8FC12; Sun, 22 Apr 2012 21:21:02 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id q3MLL2S4067134; Sun, 22 Apr 2012 23:21:02 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id q3MLL2fr067133; Sun, 22 Apr 2012 23:21:02 +0200 (CEST) (envelope-from marius) Date: Sun, 22 Apr 2012 23:21:02 +0200 From: Marius Strobl To: Andriy Gapon Message-ID: <20120422212102.GA66855@alchemy.franken.de> References: <4F8999D2.1080902@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F8999D2.1080902@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [review request] zfsboot/zfsloader: support accessing filesystems within a pool 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, 22 Apr 2012 21:21:03 -0000 On Sat, Apr 14, 2012 at 06:37:54PM +0300, Andriy Gapon wrote: > > I would like to ask for a review and/or testing of the following three patches: > http://people.freebsd.org/~avg/zfsboot.patches.diff > > These patches add support for booting from an arbitrary filesystem of any > detected ZFS pool. A filesystem could be selected in zfsboot and thus will > affectfrom where zfsloader would be loaded. zfsboot passes information about > the boot pool and filesystem to zfsloader, which uses those for loaddev and > default value of currdev. A different pool+filesystem could be selected in > zfsloader for booting kernel. Also if vfs.root.mountfrom is not explicitly set > and is not derived from fstab, then it gets set to the selected boot filesystem. > > This should could be used as a foundation for the support of Solaris-like boot > environment selection. I believe that other people have already developed > scripts utilizing ZFS capabilities to provide other aspects of management of > boot environments. > > I am particularly interested in reviews of my attempt to make ZFS boot support > arch-independent. The arches, of course, would have to add some code to make > use of that support. Currently I only enabled it for x86. > I can't say much about these patches as a whole as they are rather big and I'm not aware of all the details of ZFS. However, one bit that makes the current implementation x86-specific is zfs_dev_init(). If you could move it to the MD part in the course of these patches that would be great. If you could also take the second patch in PR 165025 into account, which I plan to commit once the issue with the current ofw_disk.c are properly solved, that would be great. Marius From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 03:02:44 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 203EA106564A; Mon, 23 Apr 2012 03:02:44 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E7A458FC15; Mon, 23 Apr 2012 03:02:43 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3N32h1O065208; Mon, 23 Apr 2012 03:02:43 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3N32h3E065204; Mon, 23 Apr 2012 03:02:43 GMT (envelope-from linimon) Date: Mon, 23 Apr 2012 03:02:43 GMT Message-Id: <201204230302.q3N32h3E065204@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167105: [nfs] mount_nfs can not handle source exports wiht more then 63 chars 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, 23 Apr 2012 03:02:44 -0000 Old Synopsis: mount_nfs can not handle source exports wiht more then 63 chars New Synopsis: [nfs] mount_nfs can not handle source exports wiht more then 63 chars Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Apr 23 03:02:13 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167105 From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 03:09:42 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 275C71065674; Mon, 23 Apr 2012 03:09:42 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EF3038FC14; Mon, 23 Apr 2012 03:09:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3N39fpf066073; Mon, 23 Apr 2012 03:09:41 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3N39f5O066069; Mon, 23 Apr 2012 03:09:41 GMT (envelope-from linimon) Date: Mon, 23 Apr 2012 03:09:41 GMT Message-Id: <201204230309.q3N39f5O066069@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/165521: [zfs] [hang] livelock on 1 Gig of RAM with zfs when 310.locate is run 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, 23 Apr 2012 03:09:42 -0000 Old Synopsis: livelock on 1 Gig of RAM with zfs when 310.locate is run New Synopsis: [zfs] [hang] livelock on 1 Gig of RAM with zfs when 310.locate is run Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Apr 23 03:08:34 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=165521 From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 03:17:40 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E56D5106564A; Mon, 23 Apr 2012 03:17:40 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B8C7B8FC0A; Mon, 23 Apr 2012 03:17:40 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3N3HeZJ076044; Mon, 23 Apr 2012 03:17:40 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3N3Hev1076040; Mon, 23 Apr 2012 03:17:40 GMT (envelope-from linimon) Date: Mon, 23 Apr 2012 03:17:40 GMT Message-Id: <201204230317.q3N3Hev1076040@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167066: [zfs] ZVOLs not appearing in /dev/zvol 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, 23 Apr 2012 03:17:41 -0000 Old Synopsis: ZVOLs not appearing in /dev/zvol New Synopsis: [zfs] ZVOLs not appearing in /dev/zvol Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Apr 23 03:16:54 UTC 2012 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=167066 From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 06:23:54 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F131A106566C; Mon, 23 Apr 2012 06:23:54 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from mail.kirov.so-ups.ru (ns.kirov.so-ups.ru [178.74.170.1]) by mx1.freebsd.org (Postfix) with ESMTP id 8F6B38FC08; Mon, 23 Apr 2012 06:23:54 +0000 (UTC) Received: from kas30pipe.localhost (localhost.kirov.so-ups.ru [127.0.0.1]) by mail.kirov.so-ups.ru (Postfix) with SMTP id 23660B801B; Mon, 23 Apr 2012 10:23:48 +0400 (MSK) Received: from kirov.so-ups.ru (unknown [172.21.81.1]) by mail.kirov.so-ups.ru (Postfix) with ESMTP id 1D8F8B8008; Mon, 23 Apr 2012 10:23:48 +0400 (MSK) Received: by ns.kirov.so-ups.ru (Postfix, from userid 1010) id 14C7FBA020; Mon, 23 Apr 2012 10:23:48 +0400 (MSK) Received: from [127.0.0.1] (elsukov.kirov.oduur.so [10.118.3.52]) by ns.kirov.so-ups.ru (Postfix) with ESMTP id D1CF9BA00C; Mon, 23 Apr 2012 10:23:47 +0400 (MSK) Message-ID: <4F94F56E.1010501@FreeBSD.org> Date: Mon, 23 Apr 2012 10:23:42 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Marius Strobl References: <4F8999D2.1080902@FreeBSD.org> <20120422212102.GA66855@alchemy.franken.de> In-Reply-To: <20120422212102.GA66855@alchemy.franken.de> X-Enigmail-Version: 1.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC7029BA0145B0E0BC6B4FC9D" X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0284], KAS30/Release X-SpamTest-Info: Not protected Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org, Andriy Gapon Subject: Re: [review request] zfsboot/zfsloader: support accessing filesystems within a pool 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, 23 Apr 2012 06:23:55 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC7029BA0145B0E0BC6B4FC9D Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On 23.04.2012 1:21, Marius Strobl wrote: > I can't say much about these patches as a whole as they are rather > big and I'm not aware of all the details of ZFS. However, one bit that > makes the current implementation x86-specific is zfs_dev_init(). If > you could move it to the MD part in the course of these patches that > would be great. If you could also take the second patch in PR 165025 > into account, which I plan to commit once the issue with the current > ofw_disk.c are properly solved, that would be great. I also have some WIP related to moving partition table handling into MD p= art. You can look here: http://people.freebsd.org/~ae/sys_boot.diff This patch have one problem, there is no way to determine disk size and i'm thinking about adding ioctl(DIOCGMEDIASIZE) to the "disk" devsw. --=20 WBR, Andrey V. Elsukov --------------enigC7029BA0145B0E0BC6B4FC9D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJPlPVzAAoJEAHF6gQQyKF6pzMH/AmB7G4BFMM9jYW8TMIexfOX 7xPLKbgFuIHeMcXyOjZseDEdTrLcC7DsCyS/euT7ScvdcTtImt9mpxSYznRgWZ2Y h+pD2zH1UT3AxPKwMvyIbt54E91W/2m7tDmMskWuFtyWrYlOKzacZlr7QT+ylfqd IotkgPSs1nyEo8+blzEfj7sjLHFVApeclYIeZT8GUQ0iVlHPyQJZ3TPSHGP50ozj VvVT07PZdcf/t73sa8xUdV5sIoN3zV211PNKMuMFvB9DdcP9ZBbiOpYFoUBtLTsa WomrpDKZ8OZr5jbJx7411BnfwgbJzyuxbPune1E1j8ver8rm2YYhdEwAHmXtzr4= =VC6q -----END PGP SIGNATURE----- --------------enigC7029BA0145B0E0BC6B4FC9D-- From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 11:07:15 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41F141065674 for ; Mon, 23 Apr 2012 11:07:15 +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 0DD608FC0C for ; Mon, 23 Apr 2012 11:07:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3NB7FEc047560 for ; Mon, 23 Apr 2012 11:07:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3NB7EI0047558 for freebsd-fs@FreeBSD.org; Mon, 23 Apr 2012 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Apr 2012 11:07:14 GMT Message-Id: <201204231107.q3NB7EI0047558@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, 23 Apr 2012 11:07:15 -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/167105 fs [nfs] mount_nfs can not handle source exports wiht mor o kern/167067 fs [zfs] [panic] ZFS panics the server o kern/167066 fs [zfs] ZVOLs not appearing in /dev/zvol o kern/167065 fs [zfs] boot fails when a spare is the boot disk o kern/167048 fs [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF o kern/166912 fs [ufs] [panic] Panic after converting Softupdates to jo o kern/166851 fs [zfs] [hang] Copying directory from the mounted UFS di o kern/166566 fs [zfs] zfs split renders 2 disk (MBR based) mirror unbo o kern/166477 fs [nfs] NFS data corruption. o kern/165950 fs [ffs] SU+J and fsck problem o kern/165923 fs [nfs] Writing to NFS-backed mmapped files fails if flu o kern/165521 fs [zfs] [hang] livelock on 1 Gig of RAM with zfs when 31 o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/162362 fs [snapshots] [panic] ufs with snapshot(s) panics when g o kern/162083 fs [zfs] [panic] zfs unmount -f pool o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161897 fs [zfs] [patch] zfs partition probing causing long delay o kern/161864 fs [ufs] removing journaling from UFS partition fails on o bin/161807 fs [patch] add option for explicitly specifying metadata o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161511 fs [unionfs] Filesystem deadlocks when using multiple uni o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic o kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159663 fs [socket] [nullfs] sockets don't work though nullfs mou o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs p kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an f bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118318 fs [nfs] NFS server hangs under special circumstances o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 271 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 11:13:34 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1FFE6106564A; Mon, 23 Apr 2012 11:13:34 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtpo.poczta.interia.pl (smtpo.poczta.interia.pl [217.74.65.207]) by mx1.freebsd.org (Postfix) with ESMTP id C9E7F8FC1C; Mon, 23 Apr 2012 11:13:33 +0000 (UTC) From: vermaden To: andrnils@gmail.com X-Mailer: interia.pl/pf09 In-Reply-To: References: <4F8A9918.3080607@FreeBSD.org> Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1335179606; bh=UIhmDf0ADr1EUTiB8UoR/QpdtSeqYcU+WIeEP5YoB5s=; h=From:Subject:To:Cc:X-Mailer:In-Reply-To:References:Message-Id: MIME-Version:Content-Type:Content-Transfer-Encoding; b=TdnVNREb92r3n7Y1dt0Z9X4FEZ/BA+Z8f/T79jL8nGoI2MDbRvbjl1tPzOcXgKwcR uCNs5QznVDSqYQQFJQGGFQyF+dgmmISwyyQp0B+e7mFFm+2oeViwEecjT5qHpaAuyq Sin4vXhFfvbTpiAvNVOUhRvFVEPJs1+ILZuZ7p/Y= Date: Mon, 23 Apr 2012 13:13:26 +0200 (CEST) Cc: freebsd-fs@FreeBSD.org, freebsd-questions@FreeBSD.org Subject: Re: Mounting from zfs:system/ROOT/nch failed with error 2 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, 23 Apr 2012 11:13:34 -0000 > If you move the dataset to a new machine you should also fix > the zpool.cache on the new machine. Boot it with f.e. mfsbsd > cd import the pool and copy the zpool.cache file. >=20 > Best regards > Andreas I have solved it by copying the /boot/zfs/zpool.cache from the working/running system to the just imported ZFS snapshot, for example to /mnt/boot/zfs/zpool.cache if You set mountpoint to /mnt for that dataset, works like a charm ;) Regards, vermaden --=20 ... From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 14:38:04 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CF4F106564A for ; Mon, 23 Apr 2012 14:38:04 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from carrick.bishnet.net (carrick.bishnet.net [IPv6:2a01:348:132:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id B58C78FC12 for ; Mon, 23 Apr 2012 14:38:03 +0000 (UTC) Received: from carrick-users.bishnet.net ([2a01:348:132:51::10]) by carrick.bishnet.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1SMKP4-000PKn-Vk for freebsd-fs@freebsd.org; Mon, 23 Apr 2012 15:38:11 +0100 Received: (from tdb@localhost) by carrick-users.bishnet.net (8.14.4/8.14.4/Submit) id q3NEcA0v097388 for freebsd-fs@freebsd.org; Mon, 23 Apr 2012 15:38:10 +0100 (BST) (envelope-from tdb) Date: Mon, 23 Apr 2012 15:38:10 +0100 From: Tim Bishop To: freebsd-fs@freebsd.org Message-ID: <20120423143810.GA95448@carrick-users.bishnet.net> References: <20120327181457.GC24787@carrick-users.bishnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120327181457.GC24787@carrick-users.bishnet.net> X-PGP-Key: 0x5AE7D984, http://www.bishnet.net/tim/tim-bishnet-net.asc X-PGP-Fingerprint: 1453 086E 9376 1A50 ECF6 AE05 7DCE D659 5AE7 D984 User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: ZFS: processes hanging when trying to access filesystems 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, 23 Apr 2012 14:38:04 -0000 Here's a comparison of top output. This shows the higher context switching. I'm not sure if this is part of the cause of the problems, or just an effect: "top -Sj -m io" last pid: 95277; load averages: 0.04, 0.11, 0.13 up 20+05:31:54 15:29:52 186 processes: 2 running, 182 sleeping, 1 stopped, 1 waiting CPU: 4.1% user, 0.0% nice, 3.6% system, 0.0% interrupt, 92.3% idle Mem: 412M Active, 488M Inact, 4685M Wired, 52M Cache, 551M Buf, 288M Free Swap: 6144M Total, 316M Used, 5828M Free, 5% Inuse PID JID USERNAME VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 12 0 root 617 1 0 0 0 0 0.00% intr 11 0 root 584 1212 0 0 0 0 0.00% idle 0 0 root 322 46 0 0 0 0 0.00% kernel 3 0 root 257 1 0 0 0 0 0.00% g_up 4 0 root 175 3 0 0 0 0 0.00% g_down 13 0 root 20 0 0 0 0 0 0.00% yarrow 5 0 root 17 0 0 16 0 16 88.89% zfskern 641 0 _pflogd 4 0 0 0 0 0 0.00% pflogd last pid: 92079; load averages: 0.39, 0.22, 0.18 up 20+05:22:39 15:20:37 197 processes: 2 running, 192 sleeping, 1 stopped, 1 zombie, 1 waiting CPU: 0.0% user, 0.0% nice, 5.3% system, 1.5% interrupt, 93.2% idle Mem: 484M Active, 478M Inact, 4655M Wired, 52M Cache, 551M Buf, 257M Free Swap: 6144M Total, 316M Used, 5828M Free, 5% Inuse PID JID USERNAME VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 11 0 root 3945 6837 0 0 0 0 0.00% idle 12 0 root 2130 1 0 0 0 0 0.00% intr 0 0 root 2008 99 0 0 0 0 0.00% kernel 3 0 root 1810 0 0 0 0 0 0.00% g_up 4 0 root 1486 12 0 0 0 0 0.00% g_down 13 0 root 20 2 0 0 0 0 0.00% yarrow 5 0 root 19 0 2 66 0 68 95.77% zfskern 20 0 root 9 0 0 0 0 0 0.00% g_mirror r The latter shows the machine when it's unresponsive and processes are starting to hang. Tim. On Tue, Mar 27, 2012 at 07:14:57PM +0100, Tim Bishop wrote: > I have a machine running 8-STABLE amd64 from the end of last week. I > have a problem where the machine starts to freeze up. Any process > accessing the ZFS filesystems hangs, which eventually causes more and > more processes to be spawned (cronjobs, etc, never complete). Although > the root filesystem is on UFS (the machine hosts jails on ZFS), > eventually I can't log in anymore. > > The problem occurs when the frequently used part of the ARC gets too > large. See this graph: > > http://dl.dropbox.com/u/318044/zfs_arc_utilization-day.png > > At the right of the graph things started to hang. > > At the same time I see a high amount of context switching. > > I picked a hanging process and procstat showed the following: > > PID TID COMM TDNAME KSTACK > 24787 100303 mutt - mi_switch+0x176 sleepq_wait+0x42 _cv_wait+0x129 txg_wait_open+0x85 dmu_tx_assign+0x170 zfs_inactive+0xf1 zfs_freebsd_inactive+0x1a vinactive+0x71 vputx+0x2d8 null_reclaim+0xb3 vgonel+0x119 vrecycle+0x7b null_inactive+0x1f vinactive+0x71 vputx+0x2d8 vn_close+0xa1 vn_closefile+0x5a _fdrop+0x23 > > I'm running a reduced amount of jails on the machine at the moment which > is limiting the speed at which the machine freezes up completely. I'd > like to debug this problem further, so any advice on useful information > to collect would be appreciated. > > I've had this problem on the machine before[1] but adding more RAM > allievated the issue. > > Tim. > > [1] http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/058541.html -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 17:33:37 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3DCC106564A for ; Mon, 23 Apr 2012 17:33:37 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 64B098FC14 for ; Mon, 23 Apr 2012 17:33:37 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa02 [127.0.0.1]) by ltcfislmsgpa02.fnfis.com (8.14.4/8.14.4) with SMTP id q3NHPjHq004568; Mon, 23 Apr 2012 12:33:00 -0500 Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa02.fnfis.com with ESMTP id 14db7pr2y9-32 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 23 Apr 2012 12:33:00 -0500 Received: from dtwin (10.14.152.15) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.2.283.3; Mon, 23 Apr 2012 12:32:57 -0500 From: Sender: Devin Teske To: "'Tim Bishop'" , References: <20120327181457.GC24787@carrick-users.bishnet.net> <20120423143810.GA95448@carrick-users.bishnet.net> In-Reply-To: <20120423143810.GA95448@carrick-users.bishnet.net> Date: Mon, 23 Apr 2012 10:33:19 -0700 Message-ID: <03ef01cd2177$2d2e5b50$878b11f0$@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFJC9tWBftSbr5JPhqT6zFTDN/DsQLTVqmhl5oza5A= Content-Language: en-us X-Originating-IP: [10.14.152.15] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7580, 1.0.260, 0.0.0000 definitions=2012-04-23_04:2012-04-23, 2012-04-23, 1970-01-01 signatures=0 Cc: Subject: RE: ZFS: processes hanging when trying to access filesystems 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, 23 Apr 2012 17:33:37 -0000 > -----Original Message----- > From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] > On Behalf Of Tim Bishop > Sent: Monday, April 23, 2012 7:38 AM > To: freebsd-fs@freebsd.org > Subject: Re: ZFS: processes hanging when trying to access filesystems > > Here's a comparison of top output. This shows the higher context > switching. I'm not sure if this is part of the cause of the problems, or > just an effect: > > "top -Sj -m io" > > last pid: 95277; load averages: 0.04, 0.11, 0.13 up 20+05:31:54 15:29:52 > 186 processes: 2 running, 182 sleeping, 1 stopped, 1 waiting > CPU: 4.1% user, 0.0% nice, 3.6% system, 0.0% interrupt, 92.3% idle > Mem: 412M Active, 488M Inact, 4685M Wired, 52M Cache, 551M Buf, 288M Free > Swap: 6144M Total, 316M Used, 5828M Free, 5% Inuse > > PID JID USERNAME VCSW IVCSW READ WRITE FAULT TOTAL PERCENT > COMMAND > 12 0 root 617 1 0 0 0 0 0.00% intr > 11 0 root 584 1212 0 0 0 0 0.00% idle > 0 0 root 322 46 0 0 0 0 0.00% kernel > 3 0 root 257 1 0 0 0 0 0.00% g_up > 4 0 root 175 3 0 0 0 0 0.00% g_down > 13 0 root 20 0 0 0 0 0 0.00% yarrow > 5 0 root 17 0 0 16 0 16 88.89% zfskern > 641 0 _pflogd 4 0 0 0 0 0 0.00% pflogd > > last pid: 92079; load averages: 0.39, 0.22, 0.18 up 20+05:22:39 15:20:37 > 197 processes: 2 running, 192 sleeping, 1 stopped, 1 zombie, 1 waiting > CPU: 0.0% user, 0.0% nice, 5.3% system, 1.5% interrupt, 93.2% idle > Mem: 484M Active, 478M Inact, 4655M Wired, 52M Cache, 551M Buf, 257M Free > Swap: 6144M Total, 316M Used, 5828M Free, 5% Inuse > > PID JID USERNAME VCSW IVCSW READ WRITE FAULT TOTAL PERCENT > COMMAND > 11 0 root 3945 6837 0 0 0 0 0.00% idle > 12 0 root 2130 1 0 0 0 0 0.00% intr > 0 0 root 2008 99 0 0 0 0 0.00% kernel > 3 0 root 1810 0 0 0 0 0 0.00% g_up > 4 0 root 1486 12 0 0 0 0 0.00% g_down > 13 0 root 20 2 0 0 0 0 0.00% yarrow > 5 0 root 19 0 2 66 0 68 95.77% zfskern > 20 0 root 9 0 0 0 0 0 0.00% g_mirror r > > The latter shows the machine when it's unresponsive and processes are > starting to hang. > > Tim. > > On Tue, Mar 27, 2012 at 07:14:57PM +0100, Tim Bishop wrote: > > I have a machine running 8-STABLE amd64 from the end of last week. I > > have a problem where the machine starts to freeze up. Any process > > accessing the ZFS filesystems hangs, which eventually causes more and > > more processes to be spawned (cronjobs, etc, never complete). Although > > the root filesystem is on UFS (the machine hosts jails on ZFS), > > eventually I can't log in anymore. > > > > The problem occurs when the frequently used part of the ARC gets too > > large. See this graph: > > > > http://dl.dropbox.com/u/318044/zfs_arc_utilization-day.png > > > > At the right of the graph things started to hang. > > > > At the same time I see a high amount of context switching. > > > > I picked a hanging process and procstat showed the following: > > > > PID TID COMM TDNAME KSTACK > > 24787 100303 mutt - mi_switch+0x176 sleepq_wait+0x42 > _cv_wait+0x129 txg_wait_open+0x85 dmu_tx_assign+0x170 zfs_inactive+0xf1 > zfs_freebsd_inactive+0x1a vinactive+0x71 vputx+0x2d8 null_reclaim+0xb3 > vgonel+0x119 vrecycle+0x7b null_inactive+0x1f vinactive+0x71 vputx+0x2d8 > vn_close+0xa1 vn_closefile+0x5a _fdrop+0x23 > > > > I'm running a reduced amount of jails on the machine at the moment which > > is limiting the speed at which the machine freezes up completely. I'd > > like to debug this problem further, so any advice on useful information > > to collect would be appreciated. > > > > I've had this problem on the machine before[1] but adding more RAM > > allievated the issue. > > > > Tim. > > > > [1] http://lists.freebsd.org/pipermail/freebsd-stable/2010- > September/058541.html > We've seen this happen and were able to not only devise a way of replicating it quickly, but also able to identify the root cause (and have since fixed the issue). When this first started, it was occurring on one system only and that system was crashing maybe once per day (by crash, I mean hang exactly as described by the OP). Then we started doing volume load testing and that's when things changed for the worst. By running the following shell script 7 times on local vty's, we were able to replicate the problem within 15 minutes (even faster if threw in some more running via SSH -- but in diagnosing the issue we wanted to prove first to ourselves that it was not network related): #!/bin/sh while :;do echo "############################## $(date)" bonnie done Eventually (for us, about 15 minutes -- with 7 concurrent instances running with a CWD within the ZFS filesystem; YMMV) bonnie stops. We did lots of things. First we watched the stats using: #!/bin/sh while :;do echo "############################## $(date)" sysctl vfs.zfs kstat.zfs sleep 1 done | tee zfs-stats.${HOSTNAME%%.*} And it *looked* like we were hitting some limit (kstat.zfs.misc.arcstats.p appears to be ever-climbing and then BOOM! -- hang). But, after tuning the following parameters in /boot/loader.conf: # ZFS kernel tune vm.kmem_size="2560M" vfs.zfs.arc_min="1536M" vfs.zfs.arc_max="1536M" vfs.zfs.prefetch_disable="1" vfs.zfs.txg.timeout="5" vfs.zfs.vdev.min_pending="3" vfs.zfs.vdev.max_pending="6" Things changed enough that we no longer thought we were hitting some limit (arcstats.p would grow then drop, grow then drop, ad nauseum several times before reaching the hang). So... We finally resolved to dismember the array (something we avoided doing until we ran out of other ideas) and test each member-disk with "SpinRite" -- a FreeDOS based bootable disc/diskette capable of performing miracles on drives. Well, turned out that the 5th (out of 6) drives was overheating under load. We were able to reliably reproduce the overheating with SpinRite (which actively monitors drive temperature during all disk operations). We saw the drive (still in our possession) routinely reach 127 degrees (Farhenheit) about 10-15 minutes under nominal load. We replaced that drive with a new one, re-assembled the array with the new drive, and started the rebuild operation. Within the hour we were back in operation AND... the system now survives multi-day heavy-volume loads running continuously throughout -- no more issues to report. We've kept the drive! I brought this up at the last BAFUG meeting and a couple guys said that we should use that drive to improve ZFS. I'm game if anybody else is. -- Devin _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 03:22:36 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53872106564A for ; Tue, 24 Apr 2012 03:22:36 +0000 (UTC) (envelope-from tjg@tgustafson.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id CCBDA8FC17 for ; Tue, 24 Apr 2012 03:22:35 +0000 (UTC) Received: by lbbgm6 with SMTP id gm6so194391lbb.13 for ; Mon, 23 Apr 2012 20:22:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=BV8sSvlV12AHTrZZq+tTwIUeVq3A77DaelH+TsQ+dD4=; b=RGT/NAo6HvXn32U98GQ8mO8xtma9LqmJj9NanmiB0BKCTovgR/U6kmrRot6pkgvU6x uKt7tUm8p2DuGtt7K1jnKwGwij6tcxEF6D0GdNutmmssi/orPzoBi/xwKel7o+n6H9BT EWCi+/D1uJ5Ix+yTDcfpCCw2VEqArss4Y8mpcuzxRBhK73TH54wRArvIyhjKeCySD7ds v+LYZaljsOOAkEzTmLJO1GTKNFrzTsBYpSvge43Vr9K37Tl0hwITtsV+VX3g8P0JZBbH GPU34BSqCyhhvlJkGKnZhzyu2PZaIhDiDuLOMWmqYa/NfW71WFQJHecwzoJjqGDLZ3/q sujg== MIME-Version: 1.0 Received: by 10.112.23.200 with SMTP id o8mr3243449lbf.21.1335237754612; Mon, 23 Apr 2012 20:22:34 -0700 (PDT) Received: by 10.152.18.201 with HTTP; Mon, 23 Apr 2012 20:22:34 -0700 (PDT) X-Originating-IP: [50.136.209.89] Date: Mon, 23 Apr 2012 20:22:34 -0700 Message-ID: From: Tim Gustafson To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkMVtcAdZzHJvu5i3ir/YZASJ6P5HrQLzB/m+kADLrplt26/GG2IQpxUottfoOvrQAIp97f Subject: Increasing ZFS Disk Sizes 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, 24 Apr 2012 03:22:36 -0000 Hi, I've got a 9.0-RELEASE system that's installed using the hand mfsroot installer. My gpart tables look like this: => 34 976773101 ada0 GPT (465G) 34 128 1 freebsd-boot (64k) 162 33554432 2 freebsd-swap (16G) 33554594 943218541 3 freebsd-zfs (449G) => 34 976773101 ada1 GPT (465G) 34 128 1 freebsd-boot (64k) 162 33554432 2 freebsd-swap (16G) 33554594 943218541 3 freebsd-zfs (449G) I'd like to increase the size of the freebsd-zfs partition. I was thinking of "breaking" my mirror, like this: zpool detach tank ada0p3 and then swapping out one of the disks with a blank 2TB disk, and then running: gpart create -s gpt ada0 gpart add -b 34 -s 64k -t freebsd-boot ada0 gpart add -s 16G -t freebsd-swap -l swap0 ada0 gpart add -t freebsd-zfs -l disk0 ada0 gpart bootcode -b /mnt2/boot/pmbr -p /mnt2/boot/gptzfsboot -i 1 ada0 And then running: zpool attach tank ada0p3 Am I missing anything here, or is the this "safe" way to do this? Do I need to do anything special (other than the gpart bootcode command) to make the new disk bootable? Do I need to do anything special to set up the swap partition? Right now, I have this in my /etc/fstab: /dev/gptid/47bc37af-873b-11e1-b913-003048b98c9e none swap sw 0 0 Would it be safe to change that to: /dev/ada1p2 none swap sw 0 0 during the operation, and then back to ada0p2 when the re-silvering is complete? Of course, once I'm done with the first disk, I will repeat the procedure for the second disk. Thanks! -- Tim Gustafson tjg@tgustafson.com http://tgustafson.com/ From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 06:12:06 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 621E6106564A for ; Tue, 24 Apr 2012 06:12:06 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 8AC138FC19 for ; Tue, 24 Apr 2012 06:12:05 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [IPv6:2001:8b0:151:1:fa1e:dfff:feda:c0bb]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id q3O6C1CE027274 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 24 Apr 2012 07:12:01 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: OpenDKIM Filter v2.5.2 smtp.infracaninophile.co.uk q3O6C1CE027274 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1335247921; bh=kcHA5hCoh8LjBSXJWGYxFu6k6ajEhQ91j593N+BbBro=; h=Date:From:To:Subject:References:In-Reply-To:Cc:Content-Type: Message-ID:Mime-Version; b=db2g0hy5GK++MyYRMci5t/YMiwlnyv/sy5pLcDTIbBMfn/GGOHsLNl8EFcbvv0oxc 4Fk8MBpGA0FgEysPqgJN4EUAJHBjhaOkN3KCtIWjPKMLBjrmt4rFoNEV5z7PKt0gQ6 xPfgBwfvBQxcwCCepeIVA6j83NsEALygmhgxvHhg= Message-ID: <4F964429.5060607@infracaninophile.co.uk> Date: Tue, 24 Apr 2012 07:11:53 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: In-Reply-To: X-Enigmail-Version: 1.4 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFB7D6FDCD767BAB0B286EDD6" X-Virus-Scanned: clamav-milter 0.97.4 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DKIM_ADSP_ALL,DKIM_SIGNED,T_DKIM_INVALID autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Subject: Re: Increasing ZFS Disk Sizes 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, 24 Apr 2012 06:12:06 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFB7D6FDCD767BAB0B286EDD6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 24/04/2012 04:22, Tim Gustafson wrote: > Am I missing anything here, or is the this "safe" way to do this? Do > I need to do anything special (other than the gpart bootcode command) > to make the new disk bootable? Do I need to do anything special to > set up the swap partition? Right now, I have this in my /etc/fstab: Yes, this is a good way to do this change. The only better way would be to add the 2TB disk to the mirror first -- thus making a three way mirror, let that resilver, and then remove one of the old drives. But that requires you to have available spare disk slots. > /dev/gptid/47bc37af-873b-11e1-b913-003048b98c9e none swap sw 0 0 >=20 > Would it be safe to change that to: >=20 > /dev/ada1p2 none swap sw 0 0 >=20 > during the operation, and then back to ada0p2 when the re-silvering is = complete? What does swapinfo(8) say? If your system is swapping directly to the partitions on both those drives then you have some work to do. You can't just pull a drive with an active swap area on it -- you should use swapoff(8) to disable the swap area first. That's something that can take some time, lots of IO and is not actually guaranteed to work; in which case you may need to edit /etc/fstab and reboot to free up that swap area. One thing I'd certainly recommend your doing here is to set up a gmirror across your swap partitions. As it is, despite having your filesystems mirrored using ZFS, you are still vulnerable to system crash should one of your drives fail. To do that: Halt the system and reboot into single user mode (ie shutdown -r). You want this so that your current swap partitions are not enabled, as you'll need to modify their configuration. Add -- geom_mirror_load=3D"YES" to /boot/loader.conf One time only, run 'kldload geom_mirror' for the initial setup -- in future this will happen automatically. Create the mirrored swap by: # gmirror label -b load -F swap /dev/gpt/swap0 /dev/gpt/swap1 and then modify /etc/fstab so that the swap related line is like so: /dev/mirror/swap none swap sw 0 0 Then hit ^D to carry on booting as normal. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enigFB7D6FDCD767BAB0B286EDD6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+WRDAACgkQ8Mjk52CukIxFwgCdHn8pdPlWlvJh+zLQ6edCZWWq OY0AnRTxxzlB89rC2qYrv24HdLRuIJ+D =QjVo -----END PGP SIGNATURE----- --------------enigFB7D6FDCD767BAB0B286EDD6-- From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 06:49:15 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A60D106564A for ; Tue, 24 Apr 2012 06:49:15 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mx1.freebsd.org (Postfix) with ESMTP id AF5B28FC15 for ; Tue, 24 Apr 2012 06:49:14 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0ME88h-1SRq5D1fhv-00HNKT; Tue, 24 Apr 2012 08:49:08 +0200 Message-ID: <4F964CE3.1080908@brockmann-consult.de> Date: Tue, 24 Apr 2012 08:49:07 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:FZZp5Einy0uj8vqnOh+JQPS9SCkBG6QpI9Pkhf8U3An KnHW1CU1eyAUn0dBmlXNjxAkFGpuREc4y4w/Yu2kByebc7tIii X/XNsjcIMEPm+qqkLXZE3OC1gzEQlF5jnQaIv1C7nhTZ8O9wQe gASu7n8uSxUI0CCGdL52SmyDjCrOs1dJJUVPQEGYC1pd48tTiT V2e9iVgGGbesS/DM8B5Apc0nDqWjxMRYF25/nAkDzYIDvJOYLU CQ1tB2WpYop6l4T0J9YzwnBPT6EG/beu2u0skGeelOqEE/XP3f VGDQ1HeOXBgbuWlhIgpreqdkou3vOTq4H+t78Cslz7NdeK243i +BzpoNPZOVV2OAb9jbEEjPBXcUtlYDd19qIcD+RZH Subject: Re: Increasing ZFS Disk Sizes 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, 24 Apr 2012 06:49:15 -0000 On 04/24/2012 05:22 AM, Tim Gustafson wrote: > Hi, > > I've got a 9.0-RELEASE system that's installed using the hand mfsroot > installer. My gpart tables look like this: > > => 34 976773101 ada0 GPT (465G) > 34 128 1 freebsd-boot (64k) > 162 33554432 2 freebsd-swap (16G) > 33554594 943218541 3 freebsd-zfs (449G) > > => 34 976773101 ada1 GPT (465G) > 34 128 1 freebsd-boot (64k) > 162 33554432 2 freebsd-swap (16G) > 33554594 943218541 3 freebsd-zfs (449G) > > I'd like to increase the size of the freebsd-zfs partition. I was > thinking of "breaking" my mirror, like this: > > zpool detach tank ada0p3 > > and then swapping out one of the disks with a blank 2TB disk, and then running: > > gpart create -s gpt ada0 > gpart add -b 34 -s 64k -t freebsd-boot ada0 > gpart add -s 16G -t freebsd-swap -l swap0 ada0 > gpart add -t freebsd-zfs -l disk0 ada0 > gpart bootcode -b /mnt2/boot/pmbr -p /mnt2/boot/gptzfsboot -i 1 ada0 Add "-a 2048" to align for better write performance (especially on SSDs and 4k sector disks) (most disks I find do equally well with alignment of 4, but some disks (eg. the new Seagate Green 3TB ones) have TERRIBLE write performance if the first partition starts before 2048. gpart create -s gpt ada0 gpart add -b 34 -s 64k -t freebsd-boot ada0 gpart add -a 2048 -s 16G -t freebsd-swap -l swap0 ada0 gpart add -a 2048 -t freebsd-zfs -l disk0 ada0 gpart bootcode -b /mnt2/boot/pmbr -p /mnt2/boot/gptzfsboot -i 1 ada0 (and if you have problems with partitions being slightly the wrong size, use -s instead of [giga]bytes) And the zfs side of things looks fine, as Matthew also said. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 07:05:43 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA7BF106564A for ; Tue, 24 Apr 2012 07:05:43 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id 622408FC15 for ; Tue, 24 Apr 2012 07:05:43 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.5/8.14.5) with ESMTP id q3O70e8u098628 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 24 Apr 2012 10:00:45 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4F964F98.7070107@digsys.bg> Date: Tue, 24 Apr 2012 10:00:40 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.3) Gecko/20120420 Thunderbird/10.0.3 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F964429.5060607@infracaninophile.co.uk> In-Reply-To: <4F964429.5060607@infracaninophile.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Increasing ZFS Disk Sizes 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, 24 Apr 2012 07:05:43 -0000 On 24.04.12 09:11, Matthew Seaman wrote: > One thing I'd certainly recommend your doing here is to set up a gmirror > across your swap partitions. As it is, despite having your filesystems > mirrored using ZFS, you are still vulnerable to system crash should one > of your drives fail. To do that: > > Halt the system and reboot into single user mode (ie shutdown -r). You > want this so that your current swap partitions are not enabled, as > you'll need to modify their configuration. This can be done while the system is running, as long as swapping is disabled (swapoff -a) and of course there is sufficient RAM to support all running processes. With regards to expanding the zpool, make sure you have autoexpand=on property set on your zpool before you start doing any of this, or at least before replacing the last drive in the vdev. This way, you will be able to resize your zpool while the system is running, no downtime. Otherwise, you may have to reboot and export/import the pool, something not very trivial to do for an root on ZFS pool. Daniel From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 12:17:02 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C26FA1065670 for ; Tue, 24 Apr 2012 12:17:02 +0000 (UTC) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.kpi.ua (comsys.kpi.ua [77.47.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3F8C88FC1B for ; Tue, 24 Apr 2012 12:17:01 +0000 (UTC) Received: from pm513-1.comsys.kpi.ua ([10.18.52.101] helo=pm513-1.comsys.ntu-kpi.kiev.ua) by comsys.kpi.ua with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1SMefz-0007EK-Jv; Tue, 24 Apr 2012 15:16:59 +0300 Received: by pm513-1.comsys.ntu-kpi.kiev.ua (Postfix, from userid 1001) id 2BCF11CC31; Tue, 24 Apr 2012 15:17:00 +0300 (EEST) Date: Tue, 24 Apr 2012 15:16:59 +0300 From: Andrey Simonenko To: Garrett Wollman Message-ID: <20120424121659.GA11025@pm513-1.comsys.ntu-kpi.kiev.ua> References: <20302.54862.344852.13627@hergotha.csail.mit.edu> <605429676.158764.1330571627121.JavaMail.root@erie.cs.uoguelph.ca> <20303.45967.708688.414986@hergotha.csail.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20303.45967.708688.414986@hergotha.csail.mit.edu> User-Agent: Mutt/1.5.21 (2010-09-15) X-Authenticated-User: simon@comsys.ntu-kpi.kiev.ua X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.63 (build at 28-Apr-2011 07:11:12) X-Date: 2012-04-24 15:16:59 X-Connected-IP: 10.18.52.101:56010 X-Message-Linecount: 109 X-Body-Linecount: 92 X-Message-Size: 6048 X-Body-Size: 5202 Cc: freebsd-fs@freebsd.org Subject: Re: Under what circumstances does the new NFS client return EAGAIN? 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, 24 Apr 2012 12:17:02 -0000 On Thu, Mar 01, 2012 at 12:36:15PM -0500, Garrett Wollman wrote: > < said: > > > Unfortunately it is a well known issue that updating exports > > is not done atomically. (I had a patch that suspended the nfsd > > threads while exports were being updated, but it was felt to > > be risky and zack@ was going to come up with a patch to fix this, > > but I don't think he has committed anything.) > > That might be something that we at least would need. You don't need > to suspend all of the nfsd threads, just delay responding to any > request that fails access control until the filter programming is > done. We may actually need to do something like that, if this machine > is to be usable as a file server. (Can't have our users' jobs > randomly breaking just because an administrator mounted a new > filesystem.) There are two types of NFS export settings handling in NFS servers: 1. All NFS export settings are loaded into NFS server, so it can make decisions about exports itself. All address specifications are given by addresses and netmasks (does not matter whether they were given by explicit addresses or by domain names in configuration files). 2. All NFS export settings are kept in user space. NFS server has cache of settings for clients' addresses and asks user space program if cache does not have NFS export information for some client's address. Such approach allows to specify export as wildcard domain names. When export settings are updated, for the first case it is necessary to update them atomically, so the NFS server will not see partially loaded settings. For the second case user land utility can synchronize own vision of NFS settings, so it just need to flush NFS server export settings cache. FreeBSD uses the first type. I already heard about suspending NFS server threads in the kernel, while NFS exports settings are being parsed and loaded. Such approach has few drawbacks: 1) user land program that loads settings can crash, 2) time for loading settings into NFS server is undefined, since data can be not in RAM. So, time while NFS server threads are suspended is undefined. There are other problems, I'll not describe them here just to be brief. Now I want to describe how NFS export settings are loaded into NFS server in my implementation. To load export settings into NFS server the nfssvc(NFSSVC_EXPORT) system call is used. Settings are not passed in one system call, so it is not necessary to create one buffer with all settings (settings can be given as a linked list as well). All communications with the NFS server through nfssvc(NFSSVC_EXPORT) system call are made in transaction concept. A process asks NFS server to start a new transaction, NFS server creates transaction and informs a process about transaction ID. Each transaction is identified by PID, UID and transaction ID, so several processes can modify NFS server export settings at the same time. Each transaction has timeout, to simplify implementation (because only one transaction is expected) any transaction can be in BUSY, ACTIVE or INACTIVE state. One callout with one timeout for all transactions is used. If transaction is inactive for some period of time its context is released, if a process that works with this transaction is still uses it, then it will be notified about transaction disappearing and will start a new transaction. When process loaded all settings into NFS server it performs transaction commit command and all settings saved in transaction context atomically are applied to NFS server export settings. NFS export settings are protected by r/w locks (rmlock for example). While NFS exports settings are being loaded, NFS server verifies whether they can be applied to the current configuration, so when transaction is committed, all data structures are already ready and should be just applied to the current configuration. To minimize number of nfssvc() system calls, a process can combine transaction flags and can chose how many different settings should be send by one nfssvc() system call. To make ABI interface with NFS server more flexible for future changes, all settings are passed in so called command structures and all export specifications are not hard coded in that structures, instead they are passed by variable sized arrays, so number and types of specifications can be changed without changing ABI. When file system is mounted it is not necessary to flush and then load all settings again, instead only settings for just mounted file system should be loaded. The same logic for file system that is going to be unmounted. Using SIGHUP signal from mount(8) is wrong, since it will work only in some cases and it will not work at all if file systems are mounted by another program. I used EVFILT_FS VQ_MOUNT and VQ_UNMOUNT kevents for user land part and new vfs_mount_event and vfs_unmount_event EVENTHANDLERS for the kernel part. The kernel part never relies on information about file system export from user space. Consider cases when one file system that shadows NFS exported file systems is mounted or unmounted. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 12:41:20 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07131106566C for ; Tue, 24 Apr 2012 12:41:20 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [91.216.196.25]) by mx1.freebsd.org (Postfix) with ESMTP id 66C398FC1A for ; Tue, 24 Apr 2012 12:41:19 +0000 (UTC) Received: from ibs.dn.ua (relay.ibs.dn.ua [91.216.196.25]) by relay.ibs.dn.ua with ESMTP id q3OCWJ2a026323 for ; Tue, 24 Apr 2012 15:32:19 +0300 (EEST) Message-ID: <20120424153219.26321@relay.ibs.dn.ua> Date: Tue, 24 Apr 2012 15:32:19 +0300 From: Zeus Panchenko To: cc: Organization: I.B.S. LLC X-Mailer: MH-E 8.2; GNU Mailutils 2.99.96; GNU Emacs 23.3.1 X-Face: &sReWXo3Iwtqql1[My(t1Gkx; y?KF@KF`4X+'9Cs@PtK^y%}^.>Mtbpyz6U=,Op:KPOT.uG )Nvx`=er!l?WASh7KeaGhga"1[&yz$_7ir'cVp7o%CGbJ/V)j/=]vzvvcqcZkf; JDurQG6wTg+?/xA go`}1.Ze//K; Fk&/&OoHd'[b7iGt2UO>o(YskCT[_D)kh4!yY'<&:yt+zM=A`@`~9U+P[qS:f; #9z~ Or/Bo#N-'S'!'[3Wog'ADkyMqmGDvga?WW)qd=?)`Y&k=o}>!ST\ Subject: is there way to rename an existing zfs pool? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Zeus Panchenko List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2012 12:41:20 -0000 hi all, may somebody advice, plese? is there way to rename an existent zfs pool? lets say we have created pool with: zpool create -f not-well-thought-out-pool-name /dev/gpt/disk0 and after some time we'd like to have it named as very-well-thought-out-pool-name so, is it possible at all? -- Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 12:45:51 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7362A106566B for ; Tue, 24 Apr 2012 12:45:51 +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 0CF558FC14 for ; Tue, 24 Apr 2012 12:45:50 +0000 (UTC) Received: from tolstoy.tols.org (localhost [127.0.0.1]) by tolstoy.tols.org (8.14.5/8.14.5) with ESMTP id q3OCjiKV088325 for ; Tue, 24 Apr 2012 12:45:44 GMT (envelope-from marco@tolstoy.tols.org) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.97.4 at tolstoy.tols.org Received: (from marco@localhost) by tolstoy.tols.org (8.14.5/8.14.5/Submit) id q3OCjiqC088324 for freebsd-fs@freebsd.org; Tue, 24 Apr 2012 14:45:44 +0200 (CEST) (envelope-from marco) Date: Tue, 24 Apr 2012 14:45:44 +0200 From: Marco van Tol To: freebsd-fs@freebsd.org Message-ID: <20120424124544.GA84516@tolstoy.tols.org> Mail-Followup-To: freebsd-fs@freebsd.org References: <20120424153219.26321@relay.ibs.dn.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120424153219.26321@relay.ibs.dn.ua> 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.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tolstoy.tols.org Subject: Re: is there way to rename an existing zfs pool? 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, 24 Apr 2012 12:45:51 -0000 On Tue, Apr 24, 2012 at 03:32:19PM +0300, Zeus Panchenko wrote: > hi all, > > may somebody advice, plese? > > is there way to rename an existent zfs pool? > > lets say we have created pool with: > > zpool create -f not-well-thought-out-pool-name /dev/gpt/disk0 > > and after some time we'd like to have it named as > very-well-thought-out-pool-name > > so, is it possible at all? >From zpool(1M): zpool import [-o mntopts] [ -o property=value] ... [-d dir | -c cachefile] [-D] [-f] [-R root] pool | id [newpool] Imports a specific pool. A pool can be identified by its name or the numeric identifier. If newpool is specified, the pool is imported using the name newpool. Otherwise, it is imported with the same name as its exported name. So basically, export and then import with a new name. Read the entire chapter from the man page to be aware of the side effects. :-) Marco -- The ones who know don't care anymore, and the ones who care don't know - Nicolas Cage in "Lord of War" From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 12:51:45 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2D940106564A for ; Tue, 24 Apr 2012 12:51:45 +0000 (UTC) (envelope-from mailing-list@legios.org) Received: from mail.legios.org (ppp59-167-179-75.static.internode.on.net [59.167.179.75]) by mx1.freebsd.org (Postfix) with ESMTP id BAAD08FC16 for ; Tue, 24 Apr 2012 12:51:44 +0000 (UTC) Received: from localhost (unknown [192.168.0.40]) by mail.legios.org (Postfix) with ESMTP id 6806831C72A; Tue, 24 Apr 2012 22:46:06 +1000 (EST) Received: from mail.legios.org ([192.168.0.40]) by localhost (mail.legios.org [192.168.0.40]) (maiad, port 10024) with ESMTP id 79400-06; Tue, 24 Apr 2012 22:46:05 +1000 (EST) Received: from mark.legios.org (unknown [192.168.0.201]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.legios.org (Postfix) with ESMTPS id 603F131C70D; Tue, 24 Apr 2012 22:46:05 +1000 (EST) Date: Tue, 24 Apr 2012 22:46:03 +1000 From: Mark Gladman To: freebsd-fs@freebsd.org Message-ID: <20120424224603.485bc6b8@mark.legios.org> In-Reply-To: <20120424153219.26321@relay.ibs.dn.ua> References: <20120424153219.26321@relay.ibs.dn.ua> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: is there way to rename an existing zfs pool? 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, 24 Apr 2012 12:51:45 -0000 On Tue, 24 Apr 2012 15:32:19 +0300 Zeus Panchenko wrote: > hi all, >=20 > may somebody advice, plese? >=20 > is there way to rename an existent zfs pool? >=20 > lets say we have created pool with: >=20 > zpool create -f not-well-thought-out-pool-name /dev/gpt/disk0 >=20 > and after some time we'd like to have it named as > very-well-thought-out-pool-name >=20 > so, is it possible at all? >=20 It should be possible with zpool import. =46rom the man page: zpool import [-o mntopts] [-o property=3Dvalue] ... [-d dir | -c cachefile] [-D] [-f] [-m] [-N] [-R root] [-F [-n]] pool | id [newpool] Imports a specific pool. A pool can be identified by its name or the numeric identifier. If newpool is specified, the pool is imported using the name newpool. Otherwise, it is imported with the same name as its exported name. Cheers, Mark From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 13:53:41 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEE10106566B for ; Tue, 24 Apr 2012 13:53:41 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id A7E2D8FC17 for ; Tue, 24 Apr 2012 13:53:41 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SMgBV-0002b9-O5 for freebsd-fs@freebsd.org; Tue, 24 Apr 2012 15:53:37 +0200 Received: from dyn1214-105.wlan.ic.ac.uk ([129.31.214.105]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Apr 2012 15:53:37 +0200 Received: from johannes by dyn1214-105.wlan.ic.ac.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Apr 2012 15:53:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Johannes Totz Date: Tue, 24 Apr 2012 14:53:26 +0100 Lines: 63 Message-ID: References: <4F964429.5060607@infracaninophile.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: dyn1214-105.wlan.ic.ac.uk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 In-Reply-To: <4F964429.5060607@infracaninophile.co.uk> Subject: Re: Increasing ZFS Disk Sizes 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, 24 Apr 2012 13:53:42 -0000 On 24/04/2012 07:11, Matthew Seaman wrote: > On 24/04/2012 04:22, Tim Gustafson wrote: >> Am I missing anything here, or is the this "safe" way to do this? Do >> I need to do anything special (other than the gpart bootcode command) >> to make the new disk bootable? Do I need to do anything special to >> set up the swap partition? Right now, I have this in my /etc/fstab: > > Yes, this is a good way to do this change. The only better way would be > to add the 2TB disk to the mirror first -- thus making a three way > mirror, let that resilver, and then remove one of the old drives. But > that requires you to have available spare disk slots. Don't forget to scrub first. Also might want to consider a zpool split, instead of detach. So that you have two disks with usable data in case the to-be-resilvered-from disk dies unexpectedly. > >> /dev/gptid/47bc37af-873b-11e1-b913-003048b98c9e none swap sw 0 0 >> >> Would it be safe to change that to: >> >> /dev/ada1p2 none swap sw 0 0 >> >> during the operation, and then back to ada0p2 when the re-silvering is complete? > > What does swapinfo(8) say? If your system is swapping directly to the > partitions on both those drives then you have some work to do. You > can't just pull a drive with an active swap area on it -- you should use > swapoff(8) to disable the swap area first. That's something that can > take some time, lots of IO and is not actually guaranteed to work; in > which case you may need to edit /etc/fstab and reboot to free up that > swap area. > > One thing I'd certainly recommend your doing here is to set up a gmirror > across your swap partitions. As it is, despite having your filesystems > mirrored using ZFS, you are still vulnerable to system crash should one > of your drives fail. To do that: > > Halt the system and reboot into single user mode (ie shutdown -r). You > want this so that your current swap partitions are not enabled, as > you'll need to modify their configuration. Add -- > > geom_mirror_load="YES" > > to /boot/loader.conf One time only, run 'kldload geom_mirror' for the > initial setup -- in future this will happen automatically. > > Create the mirrored swap by: > > # gmirror label -b load -F swap /dev/gpt/swap0 /dev/gpt/swap1 > > and then modify /etc/fstab so that the swap related line is like so: > > /dev/mirror/swap none swap sw 0 0 > > Then hit ^D to carry on booting as normal. > > Cheers, > > Matthew > From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 14:10:32 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA5CB106566B for ; Tue, 24 Apr 2012 14:10:32 +0000 (UTC) (envelope-from tjg@tgustafson.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 59F3C8FC16 for ; Tue, 24 Apr 2012 14:10:32 +0000 (UTC) Received: by lbbgm6 with SMTP id gm6so681051lbb.13 for ; Tue, 24 Apr 2012 07:10:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=1lID/t6GxuOnhtNiSJpzpJ/W3V38FaJyY7OHn0cZNpQ=; b=F53C1t11m9tMv5LJM1CeB+22E4zEuCAXNrn+cGHp0m5p74ljCpTaOjTe5IBTWyE9Tf fePZLo8RoJZTP/wIPluMJA0kMLwcWMmA2Pq8vyze/n2AwbdZd53fKG0UM/qOp9qTGdZ1 lITaaHEcYtuz/nMrm5dJuIYh0xX6EKFxycXYyI2IwAji+RXtPeUs5D9xJyLB8JrcZyv/ V4bAOnqzuydm74O/8MHEUkDjXCrU15MyMKOK/XEAan8iT37D42mK1rNab88FeQQgGt+g ZxbVeIJDlqxOdREzvun437hE+ES4IWhwAdrB7/M8kp6q1NKp/XRdx0DB3PeNOXiLwnnA l2FQ== MIME-Version: 1.0 Received: by 10.112.84.202 with SMTP id b10mr624535lbz.7.1335276630938; Tue, 24 Apr 2012 07:10:30 -0700 (PDT) Received: by 10.152.18.201 with HTTP; Tue, 24 Apr 2012 07:10:30 -0700 (PDT) X-Originating-IP: [50.136.209.89] In-Reply-To: References: <4F964429.5060607@infracaninophile.co.uk> Date: Tue, 24 Apr 2012 07:10:30 -0700 Message-ID: From: Tim Gustafson To: Johannes Totz Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQm6db++SCz53sw2iPkse7lABphhaMXfCUjJ/rHic/TeUuC6uQXNqcJ0uvADN1A6yzDWaSlx Cc: freebsd-fs@freebsd.org Subject: Re: Increasing ZFS Disk Sizes 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, 24 Apr 2012 14:10:32 -0000 > Also might want to consider a zpool split, instead of detach. So that > you have two disks with usable data in case the to-be-resilvered-from > disk dies unexpectedly. Excellent suggestion. I will do that. Thanks everyone for your concise responses. I'm working with the hosting company now to get some new disks installed. -- Tim Gustafson tjg@tgustafson.com http://tgustafson.com/ From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 14:30:21 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C4E31065674 for ; Tue, 24 Apr 2012 14:30:21 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nschwmtas05p.mx.bigpond.com (nschwmtas05p.mx.bigpond.com [61.9.189.149]) by mx1.freebsd.org (Postfix) with ESMTP id CE9958FC1D for ; Tue, 24 Apr 2012 14:30:20 +0000 (UTC) Received: from nschwcmgw06p ([61.9.190.166]) by nschwmtas05p.mx.bigpond.com with ESMTP id <20120424143014.DJWE2821.nschwmtas05p.mx.bigpond.com@nschwcmgw06p> for ; Tue, 24 Apr 2012 14:30:14 +0000 Received: from johnny.reilly.home ([124.188.161.100]) by nschwcmgw06p with BigPond Outbound id 1qWE1j0012AGJ5o01qWECU; Tue, 24 Apr 2012 14:30:14 +0000 X-Authority-Analysis: v=2.0 cv=IpCcgcDg c=1 sm=1 a=+rWFdGQzZE3xDYVtG1Y/Og==:17 a=z1TLwsU0kBEA:10 a=2A4K5xx_JT0A:10 a=kj9zAlcOel0A:10 a=cexIBkohAAAA:8 a=UmH_dSZQHSJ3RcGlep8A:9 a=4-aTtk1I5wHsH6S-Ba4A:7 a=CjuIK1q_8ugA:10 a=+rWFdGQzZE3xDYVtG1Y/Og==:117 Date: Wed, 25 Apr 2012 00:30:14 +1000 From: Andrew Reilly To: freebsd-fs@freebsd.org Message-ID: <20120424143014.GA2865@johnny.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: Odd file system corruption in ZFS pool 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, 24 Apr 2012 14:30:21 -0000 Hi there, Had a power outage followed by an electrician visit, and the power supply to my server room yoyo'd a few times before I pulled the plugs. When I powered up again this afternoon I had ZFS pool corruption, according to zpool status. Several zpool scrub/reboot cycles later, I have the odd situation of a directory entry that shows up in glob expansion, but which claims not to be there when ls does a stat, or when I try to move or delete it. Any suggestions? Ls shows: $ ls ls: .Suppliers.2010: No such file or directory (Yes, this is in a Maildir managed jointly by qmail and dovecot.) There are also a bunch of message files in a different directory that find reports "unknown error 112" for, which doesn't look good. Zpool status -v tank says: pool: tank state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scan: scrub in progress since Wed Apr 25 00:12:48 2012 50.9G scanned out of 1.03T at 106M/s, 2h42m to go 0 repaired, 4.81% done config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 853 raidz1-0 ONLINE 0 0 3.33K gptid/b06b6337-e511-11e0-9d62-00270e0fb8e9 ONLINE 0 0 0 gptid/b6c7d5b0-e511-11e0-9d62-00270e0fb8e9 ONLINE 0 0 0 gptid/bbf6c485-e511-11e0-9d62-00270e0fb8e9 ONLINE 0 0 0 gptid/bf86a966-e511-11e0-9d62-00270e0fb8e9 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: tank/home:<0x0> Every time I run zpool scrub and reboot the CKSUM column goes to zero, and the errors go away and the status says that the previous scrub found no errors. Every time I look at the missing directory the CKSUM column gets larger... I do have a backup (I hope): on another zfs filesystem on a usb drive, constructed by sending and receiving snapshots in an incremental fashion. What I don't know is whether I actually need to use it or not. Everything seems to be working fine apart from this mysteriously untouchable Maildir directory and a few mail files, all of which I could recover from the backup if only I could remove the original. Should I just zfs destroy tank/home then create it again and send the last backup snapshots back? Would that remove the corruption? Oh, I'm running 9-stable, and my Zpool and zfs versions are : FreeBSD johnny.reilly.home 9.0-STABLE FreeBSD 9.0-STABLE #15: Sun Apr 22 11:37:17 EST 2012 root@johnny.reilly.home:/usr/obj/usr/src/sys/GENERIC amd64 ZFS filesystem version 5 ZFS storage pool version 28 Cheers, -- Andrew From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 14:37:48 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 353EA106566B for ; Tue, 24 Apr 2012 14:37:48 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mx1.freebsd.org (Postfix) with ESMTP id BB3AC8FC0C for ; Tue, 24 Apr 2012 14:37:47 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0LiCJf-1RrQVt07VL-00nOJ7; Tue, 24 Apr 2012 16:37:46 +0200 Message-ID: <4F96BAB9.9080303@brockmann-consult.de> Date: Tue, 24 Apr 2012 16:37:45 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20120424143014.GA2865@johnny.reilly.home> In-Reply-To: <20120424143014.GA2865@johnny.reilly.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:AZ6zxXU/WWIgbI5EIi3MkooTTi+vD18LV92C6qCFBT3 niH1HLhyw3l3q719+oAlMOt0p6bWb6OWXGS7omHs0kpalo6Lx1 8q+V0FZVyqvy0Em7RGg38Nb/zk1CjdgPdh+YceLr8izzz4hfpA CyIlFuFew7SrL2skPKnekCzfGPu1ArgrKLc6hd3/K24CQsRn6f UbONfi9AylT4+ruvVTiH6KMSuB4Ymeu3JOLkeGMUodQLruBPW6 aYP9p5RRgio2rk4lgKmgNU5C3OCalqZIpb0tELRM5yrPKwy4U4 BMSI0ol7zm1NHbqezPkT39piXI7QA52pvj6U3W9SVuu10cH2fQ 8Pj76BM1TXRw470d1lZB3YlHM7H1x5LjAPWYI35rU Subject: Re: Odd file system corruption in ZFS pool 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, 24 Apr 2012 14:37:48 -0000 On 04/24/2012 04:30 PM, Andrew Reilly wrote: > ZFS filesystem version 5 > ZFS storage pool version 28 Is there anything special about your pool? Was it created in an old FreeBSD and upgraded? Was it send/recv'd from OpenSolaris? etc. So far the only corruption I had was the result of installing FreeBSD on a 4 GB USB flash stick. It had no redundancy, and within a few months, some files were spontaneously broken. And in that one instance I found that move, copy, etc. on broken files reported by zpool status -v will always fail. Only "rm" worked for me. So I suggest you try rmdir or rm -r. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 19:10:12 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 80923106566B for ; Tue, 24 Apr 2012 19:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6BE8A8FC18 for ; Tue, 24 Apr 2012 19:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3OJACSb070117 for ; Tue, 24 Apr 2012 19:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3OJACD6070116; Tue, 24 Apr 2012 19:10:12 GMT (envelope-from gnats) Date: Tue, 24 Apr 2012 19:10:12 GMT Message-Id: <201204241910.q3OJACD6070116@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/51583: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2012 19:10:12 -0000 The following reply was made to PR kern/51583; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/51583: commit references a PR Date: Tue, 24 Apr 2012 19:08:50 +0000 (UTC) Author: trociny Date: Tue Apr 24 19:08:40 2012 New Revision: 234660 URL: http://svn.freebsd.org/changeset/base/234660 Log: MFC r232317: Introduce VOP_UNP_BIND(), VOP_UNP_CONNECT(), and VOP_UNP_DETACH() operations for setting and accessing vnode's v_socket field. The operations are necessary to implement proper unix socket handling on layered file systems like nullfs(5). This change fixes the long standing issue with nullfs(5) being in that unix sockets did not work between lower and upper layers: if we bound to a socket on the lower layer we could connect only to the lower path; if we bound to the upper layer we could connect only to the upper path. The new behavior is one can connect to both the lower and the upper paths regardless what layer path one binds to. PR: kern/51583, kern/159663 Suggested by: kib Reviewed by: arch Modified: stable/9/UPDATING (contents, props changed) stable/9/sys/kern/uipc_usrreq.c stable/9/sys/kern/vfs_default.c stable/9/sys/kern/vnode_if.src stable/9/sys/sys/vnode.h Directory Properties: stable/9/sys/ (props changed) Modified: stable/9/UPDATING ============================================================================== --- stable/9/UPDATING Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/UPDATING Tue Apr 24 19:08:40 2012 (r234660) @@ -9,6 +9,14 @@ handbook. Items affecting the ports and packages system can be found in /usr/ports/UPDATING. Please read that file before running portupgrade. +20120422: + Now unix domain sockets behave "as expected" on nullfs(5). Previously + nullfs(5) did not pass through all behaviours to the underlying layer, + as a result if we bound to a socket on the lower layer we could connect + only to the lower path; if we bound to the upper layer we could connect + only to the upper path. The new behavior is one can connect to both the + lower and the upper paths regardless what layer path one binds to. + 20120109: The acpi_wmi(4) status device /dev/wmistat has been renamed to /dev/wmistat0. Modified: stable/9/sys/kern/uipc_usrreq.c ============================================================================== --- stable/9/sys/kern/uipc_usrreq.c Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/sys/kern/uipc_usrreq.c Tue Apr 24 19:08:40 2012 (r234660) @@ -541,7 +541,7 @@ restart: UNP_LINK_WLOCK(); UNP_PCB_LOCK(unp); - vp->v_socket = unp->unp_socket; + VOP_UNP_BIND(vp, unp->unp_socket); unp->unp_vnode = vp; unp->unp_addr = soun; unp->unp_flags &= ~UNP_BINDING; @@ -637,7 +637,7 @@ uipc_detach(struct socket *so) * XXXRW: Should assert vp->v_socket == so. */ if ((vp = unp->unp_vnode) != NULL) { - unp->unp_vnode->v_socket = NULL; + VOP_UNP_DETACH(vp); unp->unp_vnode = NULL; } unp2 = unp->unp_conn; @@ -1307,7 +1307,7 @@ unp_connect(struct socket *so, struct so * and to protect simultaneous locking of multiple pcbs. */ UNP_LINK_WLOCK(); - so2 = vp->v_socket; + VOP_UNP_CONNECT(vp, &so2); if (so2 == NULL) { error = ECONNREFUSED; goto bad2; @@ -2317,17 +2317,15 @@ vfs_unp_reclaim(struct vnode *vp) active = 0; UNP_LINK_WLOCK(); - so = vp->v_socket; + VOP_UNP_CONNECT(vp, &so); if (so == NULL) goto done; unp = sotounpcb(so); if (unp == NULL) goto done; UNP_PCB_LOCK(unp); - if (unp->unp_vnode != NULL) { - KASSERT(unp->unp_vnode == vp, - ("vfs_unp_reclaim: vp != unp->unp_vnode")); - vp->v_socket = NULL; + if (unp->unp_vnode == vp) { + VOP_UNP_DETACH(vp); unp->unp_vnode = NULL; active = 1; } Modified: stable/9/sys/kern/vfs_default.c ============================================================================== --- stable/9/sys/kern/vfs_default.c Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/sys/kern/vfs_default.c Tue Apr 24 19:08:40 2012 (r234660) @@ -123,6 +123,9 @@ struct vop_vector default_vnodeops = { .vop_unlock = vop_stdunlock, .vop_vptocnp = vop_stdvptocnp, .vop_vptofh = vop_stdvptofh, + .vop_unp_bind = vop_stdunp_bind, + .vop_unp_connect = vop_stdunp_connect, + .vop_unp_detach = vop_stdunp_detach, }; /* @@ -1037,6 +1040,30 @@ vop_stdadvise(struct vop_advise_args *ap return (error); } +int +vop_stdunp_bind(struct vop_unp_bind_args *ap) +{ + + ap->a_vp->v_socket = ap->a_socket; + return (0); +} + +int +vop_stdunp_connect(struct vop_unp_connect_args *ap) +{ + + *ap->a_socket = ap->a_vp->v_socket; + return (0); +} + +int +vop_stdunp_detach(struct vop_unp_detach_args *ap) +{ + + ap->a_vp->v_socket = NULL; + return (0); +} + /* * vfs default ops * used to fill the vfs function table to get reasonable default return values. Modified: stable/9/sys/kern/vnode_if.src ============================================================================== --- stable/9/sys/kern/vnode_if.src Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/sys/kern/vnode_if.src Tue Apr 24 19:08:40 2012 (r234660) @@ -640,23 +640,31 @@ vop_advise { IN int advice; }; -# The VOPs below are spares at the end of the table to allow new VOPs to be -# added in stable branches without breaking the KBI. New VOPs in HEAD should -# be added above these spares. When merging a new VOP to a stable branch, -# the new VOP should replace one of the spares. +%% unp_bind vp E E E -vop_spare1 { +vop_unp_bind { IN struct vnode *vp; + IN struct socket *socket; }; -vop_spare2 { +%% unp_connect vp L L L + +vop_unp_connect { IN struct vnode *vp; + OUT struct socket **socket; }; -vop_spare3 { +%% unp_detach vp = = = + +vop_unp_detach { IN struct vnode *vp; }; +# The VOPs below are spares at the end of the table to allow new VOPs to be +# added in stable branches without breaking the KBI. New VOPs in HEAD should +# be added above these spares. When merging a new VOP to a stable branch, +# the new VOP should replace one of the spares. + vop_spare4 { IN struct vnode *vp; }; Modified: stable/9/sys/sys/vnode.h ============================================================================== --- stable/9/sys/sys/vnode.h Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/sys/sys/vnode.h Tue Apr 24 19:08:40 2012 (r234660) @@ -707,6 +707,9 @@ int vop_stdpathconf(struct vop_pathconf_ int vop_stdpoll(struct vop_poll_args *); int vop_stdvptocnp(struct vop_vptocnp_args *ap); int vop_stdvptofh(struct vop_vptofh_args *ap); +int vop_stdunp_bind(struct vop_unp_bind_args *ap); +int vop_stdunp_connect(struct vop_unp_connect_args *ap); +int vop_stdunp_detach(struct vop_unp_detach_args *ap); int vop_eopnotsupp(struct vop_generic_args *ap); int vop_ebadf(struct vop_generic_args *ap); int vop_einval(struct vop_generic_args *ap); _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 19:10:14 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4505A106566C for ; Tue, 24 Apr 2012 19:10:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3041D8FC1A for ; Tue, 24 Apr 2012 19:10:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3OJAEAI070125 for ; Tue, 24 Apr 2012 19:10:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3OJAE2m070124; Tue, 24 Apr 2012 19:10:14 GMT (envelope-from gnats) Date: Tue, 24 Apr 2012 19:10:14 GMT Message-Id: <201204241910.q3OJAE2m070124@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/159663: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2012 19:10:14 -0000 The following reply was made to PR kern/159663; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/159663: commit references a PR Date: Tue, 24 Apr 2012 19:08:51 +0000 (UTC) Author: trociny Date: Tue Apr 24 19:08:40 2012 New Revision: 234660 URL: http://svn.freebsd.org/changeset/base/234660 Log: MFC r232317: Introduce VOP_UNP_BIND(), VOP_UNP_CONNECT(), and VOP_UNP_DETACH() operations for setting and accessing vnode's v_socket field. The operations are necessary to implement proper unix socket handling on layered file systems like nullfs(5). This change fixes the long standing issue with nullfs(5) being in that unix sockets did not work between lower and upper layers: if we bound to a socket on the lower layer we could connect only to the lower path; if we bound to the upper layer we could connect only to the upper path. The new behavior is one can connect to both the lower and the upper paths regardless what layer path one binds to. PR: kern/51583, kern/159663 Suggested by: kib Reviewed by: arch Modified: stable/9/UPDATING (contents, props changed) stable/9/sys/kern/uipc_usrreq.c stable/9/sys/kern/vfs_default.c stable/9/sys/kern/vnode_if.src stable/9/sys/sys/vnode.h Directory Properties: stable/9/sys/ (props changed) Modified: stable/9/UPDATING ============================================================================== --- stable/9/UPDATING Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/UPDATING Tue Apr 24 19:08:40 2012 (r234660) @@ -9,6 +9,14 @@ handbook. Items affecting the ports and packages system can be found in /usr/ports/UPDATING. Please read that file before running portupgrade. +20120422: + Now unix domain sockets behave "as expected" on nullfs(5). Previously + nullfs(5) did not pass through all behaviours to the underlying layer, + as a result if we bound to a socket on the lower layer we could connect + only to the lower path; if we bound to the upper layer we could connect + only to the upper path. The new behavior is one can connect to both the + lower and the upper paths regardless what layer path one binds to. + 20120109: The acpi_wmi(4) status device /dev/wmistat has been renamed to /dev/wmistat0. Modified: stable/9/sys/kern/uipc_usrreq.c ============================================================================== --- stable/9/sys/kern/uipc_usrreq.c Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/sys/kern/uipc_usrreq.c Tue Apr 24 19:08:40 2012 (r234660) @@ -541,7 +541,7 @@ restart: UNP_LINK_WLOCK(); UNP_PCB_LOCK(unp); - vp->v_socket = unp->unp_socket; + VOP_UNP_BIND(vp, unp->unp_socket); unp->unp_vnode = vp; unp->unp_addr = soun; unp->unp_flags &= ~UNP_BINDING; @@ -637,7 +637,7 @@ uipc_detach(struct socket *so) * XXXRW: Should assert vp->v_socket == so. */ if ((vp = unp->unp_vnode) != NULL) { - unp->unp_vnode->v_socket = NULL; + VOP_UNP_DETACH(vp); unp->unp_vnode = NULL; } unp2 = unp->unp_conn; @@ -1307,7 +1307,7 @@ unp_connect(struct socket *so, struct so * and to protect simultaneous locking of multiple pcbs. */ UNP_LINK_WLOCK(); - so2 = vp->v_socket; + VOP_UNP_CONNECT(vp, &so2); if (so2 == NULL) { error = ECONNREFUSED; goto bad2; @@ -2317,17 +2317,15 @@ vfs_unp_reclaim(struct vnode *vp) active = 0; UNP_LINK_WLOCK(); - so = vp->v_socket; + VOP_UNP_CONNECT(vp, &so); if (so == NULL) goto done; unp = sotounpcb(so); if (unp == NULL) goto done; UNP_PCB_LOCK(unp); - if (unp->unp_vnode != NULL) { - KASSERT(unp->unp_vnode == vp, - ("vfs_unp_reclaim: vp != unp->unp_vnode")); - vp->v_socket = NULL; + if (unp->unp_vnode == vp) { + VOP_UNP_DETACH(vp); unp->unp_vnode = NULL; active = 1; } Modified: stable/9/sys/kern/vfs_default.c ============================================================================== --- stable/9/sys/kern/vfs_default.c Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/sys/kern/vfs_default.c Tue Apr 24 19:08:40 2012 (r234660) @@ -123,6 +123,9 @@ struct vop_vector default_vnodeops = { .vop_unlock = vop_stdunlock, .vop_vptocnp = vop_stdvptocnp, .vop_vptofh = vop_stdvptofh, + .vop_unp_bind = vop_stdunp_bind, + .vop_unp_connect = vop_stdunp_connect, + .vop_unp_detach = vop_stdunp_detach, }; /* @@ -1037,6 +1040,30 @@ vop_stdadvise(struct vop_advise_args *ap return (error); } +int +vop_stdunp_bind(struct vop_unp_bind_args *ap) +{ + + ap->a_vp->v_socket = ap->a_socket; + return (0); +} + +int +vop_stdunp_connect(struct vop_unp_connect_args *ap) +{ + + *ap->a_socket = ap->a_vp->v_socket; + return (0); +} + +int +vop_stdunp_detach(struct vop_unp_detach_args *ap) +{ + + ap->a_vp->v_socket = NULL; + return (0); +} + /* * vfs default ops * used to fill the vfs function table to get reasonable default return values. Modified: stable/9/sys/kern/vnode_if.src ============================================================================== --- stable/9/sys/kern/vnode_if.src Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/sys/kern/vnode_if.src Tue Apr 24 19:08:40 2012 (r234660) @@ -640,23 +640,31 @@ vop_advise { IN int advice; }; -# The VOPs below are spares at the end of the table to allow new VOPs to be -# added in stable branches without breaking the KBI. New VOPs in HEAD should -# be added above these spares. When merging a new VOP to a stable branch, -# the new VOP should replace one of the spares. +%% unp_bind vp E E E -vop_spare1 { +vop_unp_bind { IN struct vnode *vp; + IN struct socket *socket; }; -vop_spare2 { +%% unp_connect vp L L L + +vop_unp_connect { IN struct vnode *vp; + OUT struct socket **socket; }; -vop_spare3 { +%% unp_detach vp = = = + +vop_unp_detach { IN struct vnode *vp; }; +# The VOPs below are spares at the end of the table to allow new VOPs to be +# added in stable branches without breaking the KBI. New VOPs in HEAD should +# be added above these spares. When merging a new VOP to a stable branch, +# the new VOP should replace one of the spares. + vop_spare4 { IN struct vnode *vp; }; Modified: stable/9/sys/sys/vnode.h ============================================================================== --- stable/9/sys/sys/vnode.h Tue Apr 24 19:00:42 2012 (r234659) +++ stable/9/sys/sys/vnode.h Tue Apr 24 19:08:40 2012 (r234660) @@ -707,6 +707,9 @@ int vop_stdpathconf(struct vop_pathconf_ int vop_stdpoll(struct vop_poll_args *); int vop_stdvptocnp(struct vop_vptocnp_args *ap); int vop_stdvptofh(struct vop_vptofh_args *ap); +int vop_stdunp_bind(struct vop_unp_bind_args *ap); +int vop_stdunp_connect(struct vop_unp_connect_args *ap); +int vop_stdunp_detach(struct vop_unp_detach_args *ap); int vop_eopnotsupp(struct vop_generic_args *ap); int vop_ebadf(struct vop_generic_args *ap); int vop_einval(struct vop_generic_args *ap); _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 19:25:28 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CCE38106566C for ; Tue, 24 Apr 2012 19:25:28 +0000 (UTC) (envelope-from hartzell@alto.alerce.com) Received: from griffon.alerce.com (griffon.alerce.com [206.125.171.162]) by mx1.freebsd.org (Postfix) with ESMTP id AE0878FC22 for ; Tue, 24 Apr 2012 19:25:28 +0000 (UTC) Received: from griffon.alerce.com (localhost [127.0.0.1]) by griffon.alerce.com (Postfix) with ESMTP id 04A662842A; Tue, 24 Apr 2012 12:25:22 -0700 (PDT) Received: from alto.alerce.com (75-149-38-78-SFBA.hfc.comcastbusiness.net [75.149.38.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by griffon.alerce.com (Postfix) with ESMTPSA id B90F128428; Tue, 24 Apr 2012 12:25:21 -0700 (PDT) Received: by alto.alerce.com (Postfix, from userid 503) id 3FE5E448CB7; Tue, 24 Apr 2012 12:25:21 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20374.65057.207126.29371@gargle.gargle.HOWL> Date: Tue, 24 Apr 2012 12:25:21 -0700 To: Johannes Totz In-Reply-To: References: <4F964429.5060607@infracaninophile.co.uk> X-Mailer: VM 8.2.0b under 23.2.1 (x86_64-apple-darwin) X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-fs@freebsd.org Subject: Re: Increasing ZFS Disk Sizes X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2012 19:25:28 -0000 Johannes Totz writes: > On 24/04/2012 07:11, Matthew Seaman wrote: > > On 24/04/2012 04:22, Tim Gustafson wrote: > >> Am I missing anything here, or is the this "safe" way to do this? Do > >> I need to do anything special (other than the gpart bootcode command) > >> to make the new disk bootable? Do I need to do anything special to > >> set up the swap partition? Right now, I have this in my /etc/fstab: > > > > Yes, this is a good way to do this change. The only better way would be > > to add the 2TB disk to the mirror first -- thus making a three way > > mirror, let that resilver, and then remove one of the old drives. But > > that requires you to have available spare disk slots. > > Don't forget to scrub first. > Also might want to consider a zpool split, instead of detach. So that > you have two disks with usable data in case the to-be-resilvered-from > disk dies unexpectedly. > [...] Be careful about the split, it seems to leave a bootable ZFS mirror unbootable. I have a bug open (kern/166566) that Andriy Gapon is looking into it. My understanding of the current suspect is that GUID's are changed unexpected and/or inconsistently and/or incompletely. I seem to be able to fix the problem by booting via a live CD, importing the pool and copying the resulting zpool.cache file to the bootable pool, e.g. zpool split zroot zsplitroot # ... frustration ensues boot live cd zpool import # lists new pools, e.g. zroot and zsplitroot zpool import -f -o cachefile=/tmp/zpool.cache \ -o altroot=/mnt zroot mount -t zfs zroot /mnt # I don't have things automagically mount cp /tmp/zpool.cache /mnt/boot/zfs/zpool.cache reboot g. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 19:25:39 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DE91E106564A; Tue, 24 Apr 2012 19:25:39 +0000 (UTC) (envelope-from trociny@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B2A3A8FC19; Tue, 24 Apr 2012 19:25:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3OJPdCv088335; Tue, 24 Apr 2012 19:25:39 GMT (envelope-from trociny@freefall.freebsd.org) Received: (from trociny@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3OJPdMV088331; Tue, 24 Apr 2012 19:25:39 GMT (envelope-from trociny) Date: Tue, 24 Apr 2012 19:25:39 GMT Message-Id: <201204241925.q3OJPdMV088331@freefall.freebsd.org> To: mitya@demos.su, trociny@FreeBSD.org, freebsd-fs@FreeBSD.org From: trociny@FreeBSD.org Cc: Subject: Re: kern/51583: [nullfs] [patch] allow to work with devices and sockets over nullfs [STABLE, 5.0-CURRENT] 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, 24 Apr 2012 19:25:39 -0000 Synopsis: [nullfs] [patch] allow to work with devices and sockets over nullfs [STABLE, 5.0-CURRENT] State-Changed-From-To: open->closed State-Changed-By: trociny State-Changed-When: Tue Apr 24 19:24:35 UTC 2012 State-Changed-Why: The fix merged to stable/9. http://www.freebsd.org/cgi/query-pr.cgi?pr=51583 From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 19:26:37 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83DC21065672; Tue, 24 Apr 2012 19:26:37 +0000 (UTC) (envelope-from trociny@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 57A4B8FC1C; Tue, 24 Apr 2012 19:26:37 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3OJQbG1088402; Tue, 24 Apr 2012 19:26:37 GMT (envelope-from trociny@freefall.freebsd.org) Received: (from trociny@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3OJQbjN088398; Tue, 24 Apr 2012 19:26:37 GMT (envelope-from trociny) Date: Tue, 24 Apr 2012 19:26:37 GMT Message-Id: <201204241926.q3OJQbjN088398@freefall.freebsd.org> To: rmh@debian.org, trociny@FreeBSD.org, freebsd-fs@FreeBSD.org From: trociny@FreeBSD.org Cc: Subject: Re: kern/159663: [socket] [nullfs] sockets don't work though nullfs mounts 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, 24 Apr 2012 19:26:37 -0000 Synopsis: [socket] [nullfs] sockets don't work though nullfs mounts State-Changed-From-To: open->closed State-Changed-By: trociny State-Changed-When: Tue Apr 24 19:26:09 UTC 2012 State-Changed-Why: The fix merged to stable/9. http://www.freebsd.org/cgi/query-pr.cgi?pr=159663 From owner-freebsd-fs@FreeBSD.ORG Wed Apr 25 02:44:34 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FF2D1065672 for ; Wed, 25 Apr 2012 02:44:34 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nskntqsrv02p.mx.bigpond.com (nskntqsrv02p.mx.bigpond.com [61.9.168.234]) by mx1.freebsd.org (Postfix) with ESMTP id 00D5F8FC12 for ; Wed, 25 Apr 2012 02:44:33 +0000 (UTC) Received: from nskntcmgw06p ([61.9.169.166]) by nskntmtas03p.mx.bigpond.com with ESMTP id <20120424232137.HEJW10464.nskntmtas03p.mx.bigpond.com@nskntcmgw06p>; Tue, 24 Apr 2012 23:21:37 +0000 Received: from johnny.reilly.home ([124.188.161.100]) by nskntcmgw06p with BigPond Outbound id 1zMc1j0082AGJ5o01zMccA; Tue, 24 Apr 2012 23:21:37 +0000 X-Authority-Analysis: v=2.0 cv=MaHuSuDf c=1 sm=1 a=+rWFdGQzZE3xDYVtG1Y/Og==:17 a=z1TLwsU0kBEA:10 a=ea6dOSa9tC4A:10 a=kj9zAlcOel0A:10 a=RBzxiYmM5o6yayzINFUA:9 a=PZ93UOqz-Kex-gf7B3AA:7 a=CjuIK1q_8ugA:10 a=+rWFdGQzZE3xDYVtG1Y/Og==:117 Date: Wed, 25 Apr 2012 09:21:36 +1000 From: Andrew Reilly To: Peter Maloney Message-ID: <20120424232136.GA1441@johnny.reilly.home> References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F96BAB9.9080303@brockmann-consult.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org Subject: Re: Odd file system corruption in ZFS pool 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, 25 Apr 2012 02:44:34 -0000 On Tue, Apr 24, 2012 at 04:37:45PM +0200, Peter Maloney wrote: > On 04/24/2012 04:30 PM, Andrew Reilly wrote: > >ZFS filesystem version 5 > >ZFS storage pool version 28 > Is there anything special about your pool? Was it created in an old > FreeBSD and upgraded? Was it send/recv'd from OpenSolaris? etc. I don't know enough about zfs to know whether there's anything special about it, I'm afraid. The pool "tank" is a raidz across four 1T Seagate NS series drives. The first incarnation died from corruption (boot panic loop after a zpool scrub) a year or so ago, so the current system is new since then. The first had been upgraded at least once, not sure about the current. Has only ever been attached to this (regularly upgraded) _STABLE system. It isn't protected by a UPS, and the power has been going out without warning fairly regularly, so IMO that is sufficient to explain the cause of the corruption. Setting up a UPS is my next project. Interesting update to last night's message: the corruption is rubust under send/receive of snapshots: the last version of my backup exhibits exactly the same problem. (That is: a directory that shows up in glob expansion but can't be removed or touched, and a directory full of files that find returns: Unknown error: 122.) > So far the only corruption I had was the result of installing FreeBSD on > a 4 GB USB flash stick. It had no redundancy, and within a few months, > some files were spontaneously broken. > > And in that one instance I found that move, copy, etc. on broken files > reported by zpool status -v will always fail. Only "rm" worked for me. > So I suggest you try rmdir or rm -r. Rm and rm -r doesn't work. Even as root, rm -rf Maildir.bad returns a lot of messages of the form: foo/bar: no such file or directory. The result is that I now have a directory that contains no "good" files, but a concentrated collection of breakage. I have another zpool scrub running at the moment. We'll see if that is able to clean it up, but it hasn't had much luck in the past. Note that none of these broken files or directories show up in the zpool status -v error list. That just contains the one entry for the zfs root directory: tank/home:<0x0> Cheers, -- Andrew From owner-freebsd-fs@FreeBSD.ORG Wed Apr 25 05:00:40 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9615106566C; Wed, 25 Apr 2012 05:00:40 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9CD3A8FC18; Wed, 25 Apr 2012 05:00:40 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3P50eEF020620; Wed, 25 Apr 2012 05:00:40 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3P50eLs020616; Wed, 25 Apr 2012 05:00:40 GMT (envelope-from linimon) Date: Wed, 25 Apr 2012 05:00:40 GMT Message-Id: <201204250500.q3P50eLs020616@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167272: [zfs] ZFS Disks reordering causes ZFS to pick the wrong drive 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, 25 Apr 2012 05:00:40 -0000 Old Synopsis: ZFS Disks reordering causes ZFS to pick the wrong drive New Synopsis: [zfs] ZFS Disks reordering causes ZFS to pick the wrong drive Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Apr 25 05:00:27 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167272 From owner-freebsd-fs@FreeBSD.ORG Wed Apr 25 05:01:35 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB9571065670; Wed, 25 Apr 2012 05:01:35 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AED8F8FC0A; Wed, 25 Apr 2012 05:01:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3P51Zh8024359; Wed, 25 Apr 2012 05:01:35 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3P51ZQF024350; Wed, 25 Apr 2012 05:01:35 GMT (envelope-from linimon) Date: Wed, 25 Apr 2012 05:01:35 GMT Message-Id: <201204250501.q3P51ZQF024350@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167266: [zfs] [nfs] ZFS + new NFS export (sharenfs) leads to NAMEI leak 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, 25 Apr 2012 05:01:36 -0000 Old Synopsis: ZFS + new NFS export (sharenfs) leads to NAMEI leak New Synopsis: [zfs] [nfs] ZFS + new NFS export (sharenfs) leads to NAMEI leak Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Apr 25 05:01:00 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167266 From owner-freebsd-fs@FreeBSD.ORG Wed Apr 25 05:09:25 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0AC8106564A; Wed, 25 Apr 2012 05:09:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 837EA8FC19; Wed, 25 Apr 2012 05:09:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3P59PoT029405; Wed, 25 Apr 2012 05:09:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3P59P7Y029401; Wed, 25 Apr 2012 05:09:25 GMT (envelope-from linimon) Date: Wed, 25 Apr 2012 05:09:25 GMT Message-Id: <201204250509.q3P59P7Y029401@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167260: [msdosfs] msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists 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, 25 Apr 2012 05:09:25 -0000 Old Synopsis: msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists New Synopsis: [msdosfs] msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Apr 25 05:09:10 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167260 From owner-freebsd-fs@FreeBSD.ORG Wed Apr 25 13:58:54 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB9CF106566C for ; Wed, 25 Apr 2012 13:58:54 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 7BCAE8FC16 for ; Wed, 25 Apr 2012 13:58:54 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q3PDwfmN014482; Wed, 25 Apr 2012 08:58:42 -0500 (CDT) Date: Wed, 25 Apr 2012 08:58:41 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Andrew Reilly In-Reply-To: <20120424232136.GA1441@johnny.reilly.home> Message-ID: References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> <20120424232136.GA1441@johnny.reilly.home> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Wed, 25 Apr 2012 08:58:42 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: Odd file system corruption in ZFS pool 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, 25 Apr 2012 13:58:54 -0000 On Wed, 25 Apr 2012, Andrew Reilly wrote: > from corruption (boot panic loop after a zpool scrub) a year or > so ago, so the current system is new since then. The first had > been upgraded at least once, not sure about the current. Has > only ever been attached to this (regularly upgraded) _STABLE > system. It isn't protected by a UPS, and the power has been > going out without warning fairly regularly, so IMO that is > sufficient to explain the cause of the corruption. Setting up a > UPS is my next project. With properly implemented hardware (i.e. drives which obey the cache flush request) it should not be possible to corrupt zfs due to power failure. Some of the most recently written data may be lost, but zfs should come up totally coherent at some point in the recent past. It is important to use a system which supports ECC memory to assure that data is not corrupted in memory since zfs does not defend against that. Storage redundancy is necessary to correct any data read errors but should not be necessary to defend against the result of power failure. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Wed Apr 25 15:36:48 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A3F2106566B for ; Wed, 25 Apr 2012 15:36:48 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.freebsd.org (Postfix) with ESMTP id BE4F18FC18 for ; Wed, 25 Apr 2012 15:36:47 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0Lp8j6-1RkhBa0Rfw-00erIW; Wed, 25 Apr 2012 17:36:46 +0200 Message-ID: <4F981A0D.40507@brockmann-consult.de> Date: Wed, 25 Apr 2012 17:36:45 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: Andrew Reilly References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> <20120424232136.GA1441@johnny.reilly.home> In-Reply-To: <20120424232136.GA1441@johnny.reilly.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:ZEB21vgG62ARK3a35TcrPTVfJLWHqPHIAAVKDw7/geq Saccc3sytw3Zsyo+cmw6WI7SSGdsW1h7FfTrb2wNASmNa6n8Dy vPky5hIs0TKF7HhXjqSeosbkHtwsc4hyhklqDJcbnmH0WAq+sc TmjuW5vADifBp+E/UnEjnJDMWS2Q4IC/L0HmR31P9I804uMDDP T6I9g+/YMQm3MG0yR3kplZUUX0/RDYVZX9+a6L7JW1KlaSkK4k pupXm5ZHuy1QpfeL7mgI1LHfqLA7mwOs2QVudecil02fcfFX3R wNtP5NGySuHleqMzTqPCZMnln3XAFoLfdhw5BAotdsHHsTsFAU 3PiHRy9m5qj5QLjxgX6CpgfUrq8a3j3Yc7FsIfcAV Cc: freebsd-fs@freebsd.org Subject: Re: Odd file system corruption in ZFS pool 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, 25 Apr 2012 15:36:48 -0000 On 04/25/2012 01:21 AM, Andrew Reilly wrote: > On Tue, Apr 24, 2012 at 04:37:45PM +0200, Peter Maloney wrote: >> So far the only corruption I had was the result of installing FreeBSD on >> a 4 GB USB flash stick. It had no redundancy, and within a few months, >> some files were spontaneously broken. >> >> And in that one instance I found that move, copy, etc. on broken files >> reported by zpool status -v will always fail. Only "rm" worked for me. >> So I suggest you try rmdir or rm -r. > Rm and rm -r doesn't work. Even as root, rm -rf Maildir.bad > returns a lot of messages of the form: foo/bar: no such file > or directory. The result is that I now have a directory that > contains no "good" files, but a concentrated collection of > breakage. That sucks. But there is one thing I forgot... you need to run the "rm" command immediately after scrub. (no export, reboot, etc. in between). And it probably only applies to the files listed with the -v part of "zpool status -v". So since yours aren't listed... that is something different. Is your broken stuff limited to a single dataset, or the whole pool? You could try making a second dataset, copying good files to it, and destroying the old one (losing all your snapshots on that dataset, of course). Here is another thread about it: http://lists.freebsd.org/pipermail/freebsd-current/2011-October/027902.html And this message looks interesting: "but if you search on the lists for up to a year or so, you'll find some useful commands to inspect and destroy corrupted objects." http://lists.freebsd.org/pipermail/freebsd-current/2011-October/027926.html And "I tried your suggestion and ran the command "zdb -ccv backups" to try and check the consistency of the troublesome "backups" pool. This is what I ended up with:" But they don't say what the solution is (other than destroy the pool, and I would think the dataset could be enough since the filesystem is corrupt, but maybe not the pool). > > I have another zpool scrub running at the moment. We'll see if > that is able to clean it up, but it hasn't had much luck in the > past. > > Note that none of these broken files or directories show up in > the zpool status -v error list. That just contains the one > entry for the zfs root directory: tank/home:<0x0> > > Cheers, > I doubt scrubbing more than once (repeating the same thing and expecting different results) should fix anything. But if you scrubbed on OpenIndiana, it would at least be different. And if it worked, you could file a PR about it. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 26 02:33:11 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A32C106566C; Thu, 26 Apr 2012 02:33:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4DD018FC08; Thu, 26 Apr 2012 02:33:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3Q2XBon065373; Thu, 26 Apr 2012 02:33:11 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3Q2XB70065364; Thu, 26 Apr 2012 02:33:11 GMT (envelope-from linimon) Date: Thu, 26 Apr 2012 02:33:11 GMT Message-Id: <201204260233.q3Q2XB70065364@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167109: [zfs] [panic] zfs diff kernel panic Fatal trap 9: general protection fault 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, 26 Apr 2012 02:33:11 -0000 Old Synopsis: zfs diff kernel panic Fatal trap 9: general protection fault New Synopsis: [zfs] [panic] zfs diff kernel panic Fatal trap 9: general protection fault Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Apr 26 02:32:33 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167109 From owner-freebsd-fs@FreeBSD.ORG Thu Apr 26 03:33:22 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6DC0C106566B for ; Thu, 26 Apr 2012 03:33:22 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nskntmtas04p.mx.bigpond.com (nskntmtas04p.mx.bigpond.com [61.9.168.146]) by mx1.freebsd.org (Postfix) with ESMTP id 0BC8C8FC15 for ; Thu, 26 Apr 2012 03:33:21 +0000 (UTC) Received: from nskntcmgw09p ([61.9.169.169]) by nskntmtas04p.mx.bigpond.com with ESMTP id <20120426033315.MVAP6123.nskntmtas04p.mx.bigpond.com@nskntcmgw09p>; Thu, 26 Apr 2012 03:33:15 +0000 Received: from johnny.reilly.home ([124.188.161.100]) by nskntcmgw09p with BigPond Outbound id 2TZE1j00E2AGJ5o01TZEsc; Thu, 26 Apr 2012 03:33:15 +0000 X-Authority-Analysis: v=2.0 cv=Lam+G0ji c=1 sm=1 a=+rWFdGQzZE3xDYVtG1Y/Og==:17 a=z1TLwsU0kBEA:10 a=ea6dOSa9tC4A:10 a=kj9zAlcOel0A:10 a=6I5d2MoRAAAA:8 a=FlvcrlTfTUzdFB0reuYA:9 a=a4JVoHFC1-deISbwue4A:7 a=CjuIK1q_8ugA:10 a=GQuej_zXljwA:10 a=yb16PtubOwQA:10 a=+rWFdGQzZE3xDYVtG1Y/Og==:117 Date: Thu, 26 Apr 2012 13:33:14 +1000 From: Andrew Reilly To: Peter Maloney Message-ID: <20120426033314.GA9016@johnny.reilly.home> References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> <20120424232136.GA1441@johnny.reilly.home> <4F981A0D.40507@brockmann-consult.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F981A0D.40507@brockmann-consult.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org Subject: Re: Odd file system corruption in ZFS pool 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, 26 Apr 2012 03:33:22 -0000 On Wed, Apr 25, 2012 at 05:36:45PM +0200, Peter Maloney wrote: > On 04/25/2012 01:21 AM, Andrew Reilly wrote: > >On Tue, Apr 24, 2012 at 04:37:45PM +0200, Peter Maloney wrote: > >Rm and rm -r doesn't work. Even as root, rm -rf Maildir.bad > >returns a lot of messages of the form: foo/bar: no such file > >or directory. The result is that I now have a directory that > >contains no "good" files, but a concentrated collection of > >breakage. > That sucks. But there is one thing I forgot... you need to run the "rm" > command immediately after scrub. (no export, reboot, etc. in between). I believe that I've tried that, and it still didn't work. The system is behaving as though the directory has a file with an illegal or unallocated inode number. Directories don't seem to be amenable to the old-school techniques of looking at them with hexdump or whatever, either, so I can't tell more than that. The names exist in the directory, but ask for any info that would be in the inode and you get an error. > Is your broken stuff limited to a single dataset, or the whole pool? You > could try making a second dataset, copying good files to it, and > destroying the old one (losing all your snapshots on that dataset, of > course). Seems to be only associated with the filesystem, rather than the pool. Well, my "tank" pool, (the raidz) shows zpool scrub making 0 fixes but there being unrecoverable erorrs in tank/home:<0x0>, but my backup file system (the one I send snapshot deltas to) shows exactly the same errors with no tank problems. (Hmm. Hold that thought: I haven't actually tried a scrub on the backup file system. It's just zpool status that shows no errors. Running a scrub now. Will take a while: it's a fairly slow USB2-connected disk. Zpool status says expect 10+ hours...) > Here is another thread about it: > http://lists.freebsd.org/pipermail/freebsd-current/2011-October/027902.html That does seem to be the same situation that I'm seeing. > And this message looks interesting: "but if you search on the lists for > up to a year or so, you'll find some useful commands to inspect and > destroy corrupted objects." > http://lists.freebsd.org/pipermail/freebsd-current/2011-October/027926.html Not sure about destroying corrupted objects smaller than at the file-system level. It's annoying: if I could just remove these files, I'd be happy, because I've already restored them from the backup. Instead, it is starting to look as though the only way to proceed is to destroy my home filesystem, recreate it and repopulate it from the backup (using something like rsync that doesn't also replicate the filesystem damage.) That sounds like a lot of down-time on what is a fairly busy system. > And > "I tried your suggestion and ran the command "zdb -ccv backups" to try > and check the consistency of the troublesome "backups" pool. This is > what I ended up with:" > > But they don't say what the solution is (other than destroy the pool, > and I would think the dataset could be enough since the filesystem is > corrupt, but maybe not the pool). FYI: I've been running "zdb -ccv bkp2pool" on my backup disk, to see if it has anything to say about the dangling directory entries. Problem is that it currently has a process size of about 5G (RES 2305M) on a system with 4G of physical RAM: it's paging like crazy. Probably unhelpful. > >I have another zpool scrub running at the moment. We'll see if > >that is able to clean it up, but it hasn't had much luck in the > >past. > > > >Note that none of these broken files or directories show up in > >the zpool status -v error list. That just contains the one > >entry for the zfs root directory: tank/home:<0x0> > > > >Cheers, > > > I doubt scrubbing more than once (repeating the same thing and expecting > different results) should fix anything. But if you scrubbed on > OpenIndiana, it would at least be different. And if it worked, you could > file a PR about it. Some of the (perhaps Solaris related) ZFS web pages I've been reading lately suggested that several zpool scrub passes were beneficial. Certainly I seem to have hit a local minimum on the goodness curve at the moment. Thanks for the suggestions. Appreciated. Cheers, -- Andrew From owner-freebsd-fs@FreeBSD.ORG Thu Apr 26 03:45:10 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16592106566C for ; Thu, 26 Apr 2012 03:45:01 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nskntmtas02p.mx.bigpond.com (nskntmtas02p.mx.bigpond.com [61.9.168.140]) by mx1.freebsd.org (Postfix) with ESMTP id CCDFC8FC12 for ; Thu, 26 Apr 2012 03:45:00 +0000 (UTC) Received: from nskntcmgw07p ([61.9.169.167]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20120426034453.KCSG24575.nskntmtas02p.mx.bigpond.com@nskntcmgw07p>; Thu, 26 Apr 2012 03:44:53 +0000 Received: from johnny.reilly.home ([124.188.161.100]) by nskntcmgw07p with BigPond Outbound id 2Tks1j00Y2AGJ5o01TksRN; Thu, 26 Apr 2012 03:44:53 +0000 X-Authority-Analysis: v=2.0 cv=R/eB6KtX c=1 sm=1 a=+rWFdGQzZE3xDYVtG1Y/Og==:17 a=z1TLwsU0kBEA:10 a=ea6dOSa9tC4A:10 a=kj9zAlcOel0A:10 a=0pSUehbIupVPdvFBYokA:9 a=AARTbVhTkrq5M_tpdT8A:7 a=CjuIK1q_8ugA:10 a=+rWFdGQzZE3xDYVtG1Y/Og==:117 Date: Thu, 26 Apr 2012 13:44:52 +1000 From: Andrew Reilly To: Bob Friesenhahn Message-ID: <20120426034452.GB9016@johnny.reilly.home> References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> <20120424232136.GA1441@johnny.reilly.home> 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 Subject: Re: Odd file system corruption in ZFS pool 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, 26 Apr 2012 03:45:10 -0000 On Wed, Apr 25, 2012 at 08:58:41AM -0500, Bob Friesenhahn wrote: > With properly implemented hardware (i.e. drives which obey the cache > flush request) it should not be possible to corrupt zfs due to power > failure. Does that comment apply to enerprise-class SATA drives? I was under the impression that all SATA drives lied about cache flush status. Hence the notion that I need to get myself a UPS. > Some of the most recently written data may be lost, but zfs > should come up totally coherent at some point in the recent past. Certainly it has been my experience that ZFS is extremely robust in this regard, even with the inexpensive hardware that I have. The power has gone down many times (mostly thanks to builders on site) with no problems. Not this time, though. > It > is important to use a system which supports ECC memory to assure that > data is not corrupted in memory since zfs does not defend against > that. Not reasonable for an inexpensive home file/e-mail/whatever server, IMO. Well, none of the mini-ITX motherboards I saw touted ECC as an available option. This box does quite a bit of work though, and rebuilds itself from source every couple of weeks with nary a hiccup. So I'm fairly confident that it's solid. > Storage redundancy is necessary to correct any data read > errors but should not be necessary to defend against the result of > power failure. I have raidz on the broken filesystem, and a separate nightly backup. That ought to be enough redundancy to get me through, assuming that I can work around the filesystem damage in the former that seems to have propagated itself to the latter. johnny [220]$ /bin/ls -a /backup2/home/andrew/Maildir.bad/ . .. .AppleDouble .Suppliers.2010 .Unix johnny [221]$ /bin/ls -ai /backup2/home/andrew/Maildir.bad/ ls: .Suppliers.2010: No such file or directory 7906 . 82016 .AppleDouble 7810 .. 80774 .Unix johnny [218]$ sudo zpool status bkp2pool pool: bkp2pool state: ONLINE scan: scrub in progress since Thu Apr 26 13:29:36 2012 14.3G scanned out of 745G at 23.1M/s, 8h59m to go 0 repaired, 1.93% done config: NAME STATE READ WRITE CKSUM bkp2pool ONLINE 0 0 0 gpt/backup3g ONLINE 0 0 0 errors: No known data errors So: the corruption in the dangling .Suppliers.2010 reference has (a) propagated to the backup, using zfs send/receive (b) is at weirder level than simple inode corruption, because I can't even list the inode... (c) doesn't show up in zpool status as cksum or other errors. Cheers, -- Andrew From owner-freebsd-fs@FreeBSD.ORG Thu Apr 26 14:24:30 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B57941065674 for ; Thu, 26 Apr 2012 14:24:30 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 719298FC14 for ; Thu, 26 Apr 2012 14:24:30 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q3QEOJou019635; Thu, 26 Apr 2012 09:24:19 -0500 (CDT) Date: Thu, 26 Apr 2012 09:24:19 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Andrew Reilly In-Reply-To: <20120426034452.GB9016@johnny.reilly.home> Message-ID: References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> <20120424232136.GA1441@johnny.reilly.home> <20120426034452.GB9016@johnny.reilly.home> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Thu, 26 Apr 2012 09:24:20 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: Odd file system corruption in ZFS pool 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, 26 Apr 2012 14:24:30 -0000 On Thu, 26 Apr 2012, Andrew Reilly wrote: > On Wed, Apr 25, 2012 at 08:58:41AM -0500, Bob Friesenhahn wrote: >> With properly implemented hardware (i.e. drives which obey the cache >> flush request) it should not be possible to corrupt zfs due to power >> failure. > > Does that comment apply to enerprise-class SATA drives? I was > under the impression that all SATA drives lied about cache flush > status. Hence the notion that I need to get myself a UPS. A blanket statement like that (about SATA drives) would not be very accurate. UPSs are quite valuable in that they help the system avoid marginal operating conditions. If power is lost while a drive is currently writing, perhaps it will move the head to the wrong position and write to the wrong place on the disk, or perhaps the data it does write will be junk. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Thu Apr 26 15:50:13 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 306C2106564A for ; Thu, 26 Apr 2012 15:50:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1A6E58FC14 for ; Thu, 26 Apr 2012 15:50:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3QFoCZl031160 for ; Thu, 26 Apr 2012 15:50:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3QFoCjj031159; Thu, 26 Apr 2012 15:50:12 GMT (envelope-from gnats) Date: Thu, 26 Apr 2012 15:50:12 GMT Message-Id: <201204261550.q3QFoCjj031159@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Anna-Maria Cc: Subject: Re: kern/167272: [zfs] ZFS Disks reordering causes ZFS to pick the wrong drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Anna-Maria List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2012 15:50:13 -0000 The following reply was made to PR kern/167272; it has been noted by GNATS. From: Anna-Maria To: bug-followup@FreeBSD.org, david.alves@gmx.fr Cc: Subject: Re: kern/167272: [zfs] ZFS Disks reordering causes ZFS to pick the wrong drive Date: Thu, 26 Apr 2012 17:40:19 +0200 This is a multi-part message in MIME format. --------------060700060302040105000702 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit You can use the "zdb" command to see the guid of the disk, and use that to replace it. eg. children[2]: type: 'disk' id: 2 guid: *713716085525288922* path: '/dev/*da21*' phys_path: '/dev/*da21*' whole_disk: 1 *not_present: 1* metaslab_array: 13154506 metaslab_shift: 25 ashift: 9 asize: 4289200128 is_log: 1 DTL: 13647709 create_txg: 2302081 zpool replace 713716085525288922 da31 Also, I had a barely related problem with 8.2-RELEASE (or may have been the 8-STABLE from April which is in an iso on the ftp site), where rebooting would make ZFS use the wrong disk in the pool. (eg. my hot spare might end up being part of the raidz2, and so constantly create checksum errors until I scrub it or move it back). And then I tried warning others about it, and they would always say that I make no sense, and zfs uses the guid so can't get confused, etc. and only shows the label/device on the command output. So I tried reproducing it, and it was impossible for me to reproduce with 8-STABLE (October 2011). Your problem isn't quite the same, but may be related. Also in 8-STABLE, any time I do weird stuff like you did, the disk shows the guid on the next reboot instead of the old device name, and on the right it will add a comment saying "was da21". (but mostly I use gpt slices, so I might just not have enough experience with that particular problem). So I highly recommend you try 8.3-RELEASE (or 8-STABLE). And one more warning... if you ugrade to newer than 8.2-RELEAE, and have an old pool from 8.2-RELEASE and upgrade it to v28, you still can't remove logs. It is bugged. You need to destroy and recreate. --------------060700060302040105000702 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit You can use the "zdb" command to see the guid of the disk, and use that to replace it.

eg.

        children[2]:
            type: 'disk'
            id: 2
            guid: 713716085525288922
            path: '/dev/da21'
            phys_path: '/dev/da21'
            whole_disk: 1
            not_present: 1
            metaslab_array: 13154506
            metaslab_shift: 25
            ashift: 9
            asize: 4289200128
            is_log: 1
            DTL: 13647709
            create_txg: 2302081

zpool replace 713716085525288922 da31

Also, I had a barely related problem with 8.2-RELEASE (or may have been the 8-STABLE from April which is in an iso on the ftp site), where rebooting would make ZFS use the wrong disk in the pool. (eg. my hot spare might end up being part of the raidz2, and so constantly create checksum errors until I scrub it or move it back). And then I tried warning others about it, and they would always say that I make no sense, and zfs uses the guid so can't get confused, etc. and only shows the label/device on the command output. So I tried reproducing it, and it was impossible for me to reproduce with 8-STABLE (October 2011). Your problem isn't quite the same, but may be related.

Also in 8-STABLE, any time I do weird stuff like you did, the disk shows the guid on the next reboot instead of the old device name, and on the right it will add a comment saying "was da21". (but mostly I use gpt slices, so I might just not have enough experience with that particular problem).

So I highly recommend you try 8.3-RELEASE (or 8-STABLE).

And one more warning... if you ugrade to newer than 8.2-RELEAE, and have an old pool from 8.2-RELEASE and upgrade it to v28, you still can't remove logs. It is bugged. You need to destroy and recreate.
--------------060700060302040105000702-- From owner-freebsd-fs@FreeBSD.ORG Thu Apr 26 21:07:13 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16AE9106564A for ; Thu, 26 Apr 2012 21:07:13 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail26.syd.optusnet.com.au (mail26.syd.optusnet.com.au [211.29.133.167]) by mx1.freebsd.org (Postfix) with ESMTP id 977388FC08 for ; Thu, 26 Apr 2012 21:07:12 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-251-180.belrs5.nsw.optusnet.com.au [220.239.251.180]) by mail26.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id q3QL72uU022437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Apr 2012 07:07:02 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.5/8.14.4) with ESMTP id q3QL71MA057529; Fri, 27 Apr 2012 07:07:01 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.5/8.14.5/Submit) id q3QL71IR057528; Fri, 27 Apr 2012 07:07:01 +1000 (EST) (envelope-from peter) Date: Fri, 27 Apr 2012 07:07:00 +1000 From: Peter Jeremy To: Andrew Reilly Message-ID: <20120426210700.GA54475@server.vk2pj.dyndns.org> References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> <20120424232136.GA1441@johnny.reilly.home> <20120426034452.GB9016@johnny.reilly.home> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline In-Reply-To: <20120426034452.GB9016@johnny.reilly.home> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: Odd file system corruption in ZFS pool 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, 26 Apr 2012 21:07:13 -0000 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Apr-26 13:44:52 +1000, Andrew Reilly wrote: >On Wed, Apr 25, 2012 at 08:58:41AM -0500, Bob Friesenhahn wrote: >> It=20 >> is important to use a system which supports ECC memory to assure that=20 >> data is not corrupted in memory since zfs does not defend against=20 >> that. > >Not reasonable for an inexpensive home file/e-mail/whatever >server, IMO. Well, none of the mini-ITX motherboards I saw >touted ECC as an available option. It's a tradeoff. ECC does increase the cost but how valuable is your data? I run ECC on my home server because that closes a hole in the end-to-end checking. Building a system out of server-grade parts is one option - though (apart from the RAM), the parts tend to be more expensive. Re-using a second-hand server is another option - though they will use more power that a system built with current-generation pars. Building a system using SOHO-grade parts is trickier. The CPU is easy - basically all desktop AMD CPUs support ECC RAM. Motherboards are trickier - support for ECC is generally well hidden - Asus & Gigabyte are the only vendors that seem to advertise ECC support (though they still don't seem to offer it on all motherboards). The downside of non-server motherboards is thah they generally only support unbuffered RAM and only have 2-4 DIMM slots. Unbuffered ECC RAM is currently only economical up to 4GB DIMMs (8GB DIMMs exist but are outrageously expensive) - this limits you to ~16GB, which isn't extravagant when you are using ZFS. --=20 Peter Jeremy --ibTvN161/egqYuK8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk+ZuPQACgkQ/opHv/APuIet/QCeKtPVmWEOkFVXkb2HeWVvJGHo 8CgAni53wvS8QXZcOGYqNsGLeKbgwQtX =KQCp -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- From owner-freebsd-fs@FreeBSD.ORG Thu Apr 26 23:28:49 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8FA611065670; Thu, 26 Apr 2012 23:28:49 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtpo.poczta.interia.pl (smtpo.poczta.interia.pl [217.74.65.208]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7D08FC08; Thu, 26 Apr 2012 23:28:49 +0000 (UTC) From: vermaden To: freebsd-fs@FreeBSD.org X-Mailer: interia.pl/pf09 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1335481713; bh=+QP7Db2ePeUjlSOaVGiicFSmQi1Ac/lkOLsN7U9JcsQ=; h=From:Subject:To:Cc:X-Mailer:Message-Id:MIME-Version:Content-Type: Content-Transfer-Encoding; b=LhcMs5Xgqg5cq7dYsItyHDskE0ICg+fsp/JccepM+XQ4HnQE95ckzrmW6ROZvM63q cOWYk6eC/32ML1kB7ote6mtbekXuWvqqFRgwf2UHMuOOUQrXmesUuO5INAyC28+3Kn ZetKNnOsnVtUFyT1fVpfNXvMAtXGWZBzGbyBTWhM= Date: Fri, 27 Apr 2012 01:08:33 +0200 (CEST) Cc: freebsd-questions@freebsd.org Subject: HOWTO: FreeBSD ZFS Madness (Boot Environments) 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, 26 Apr 2012 23:28:49 -0000 Hi, I have just created new HOWTO [1] on how to use Boot Environments on FreeBSD with new created utility *beadm* that I put on SourceForge [2]. Feel free to send Your ideas/critique about it. [1] http://forums.freebsd.org/showthread.php?t=3D31662 [2] https://sourceforge.net/projects/beadm/ Regards, vermaden ... From owner-freebsd-fs@FreeBSD.ORG Thu Apr 26 23:36:03 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEB5E106564A for ; Thu, 26 Apr 2012 23:36:03 +0000 (UTC) (envelope-from bryan@shatow.net) Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92]) by mx1.freebsd.org (Postfix) with ESMTP id 4C1098FC12 for ; Thu, 26 Apr 2012 23:36:03 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type; q=dns; s=sweb; b=2GPsBrqlWOBq7DIbLD3Bo+1P13BvlckO sFNqDhVlT1VJtdLSqzCbMwkxPwFQD62LmqHH9to30HlH40qP0k1kZJXkhxVZlHJ3 KG+eIqQmtVh7/Nm0k/F2MEBnWx9U3eiXknZwAj50cyHgQbZTkL97vBrmjb0fnZgO Ot1R+kShrh4= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type; s=sweb; bh=i/3gnHKT5vusUOLOlsvf/1Swm4n5cAYPi3DLja bdw/c=; b=LaqAMMSaaDLFOtCP9WsfFdcN0mRhEPbU7B/Sa58cUnh+dLeS3VDPWJ 8AyHXeP3hNFZjc9aivipXNGDFewQ5M7Vm/FJmAJ4GSAF34I9pEEu/nN9S4QUDeOd lIM+0Z9Ls5e5viYtqytrKqFcz2Nxd0Xi3MNarmA+xcPVrlOrnQjig= Received: (qmail 54238 invoked from network); 26 Apr 2012 18:35:55 -0500 Received: from unknown (HELO ?192.168.0.107?) (bryan@shatow.net@74.94.87.209) by sweb.xzibition.com with ESMTPA; 26 Apr 2012 18:35:55 -0500 Message-ID: <4F99DBD9.5000409@shatow.net> Date: Thu, 26 Apr 2012 18:35:53 -0500 From: Bryan Drewery User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 MIME-Version: 1.0 To: vermaden References: In-Reply-To: X-Enigmail-Version: 1.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF56DE8664E6BCAE71CC31185" Cc: freebsd-fs@freebsd.org Subject: Re: HOWTO: FreeBSD ZFS Madness (Boot Environments) 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, 26 Apr 2012 23:36:03 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF56DE8664E6BCAE71CC31185 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 04/26/2012 06:08 PM, vermaden wrote: > Hi, >=20 > I have just created new HOWTO [1] on how to use Boot Environments on > FreeBSD with new created utility *beadm* that I put on SourceForge [2].= >=20 > Feel free to send Your ideas/critique about it. >=20 > [1] http://forums.freebsd.org/showthread.php?t=3D31662 > [2] https://sourceforge.net/projects/beadm/ >=20 > Regards, > vermaden Very nice. Can you give it a version so we can add it to ports? Regards, Bryan Drewery --------------enigF56DE8664E6BCAE71CC31185 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmdvaAAoJEG54KsA8mwz5UzIP/ifUAliN7wIAXQ8DSSU+AD0i hGXJyZ/VC1hpjFY5u+urR6rX2ZxwLNOysJW9fKKRuljSkjYTjLsw3ZHY2YMTHQYl heJbX9spDi/e85ujdLHzqoEDz/9R7lvfkavhrpLxrddFsxhwOgYzBzsABHDjHv/u I859dSj3B6oGqD0or6yMYy7y31NzZEoC7NL3NBO8GqdgaVIbp9ayPu6++sAjJca3 YRQmk5zPZewDt8KCKk8V1aCFYktmKgRobxU5MfQQHvatDpdq4Zmdd9d+CWxb3kgE jeKwJEQ99/NTDg7D1I7xNefrFewhOJF2ibKTj/qrdHdXsR5ZDhpCn/AxBDMIKz+o hiKjCNiXcPLg5HKTSNxQAb2xpMfQu+3TRHfnx5otUgxZV9EgUJcyPJaW1ONz4Jas o1egUqox1RfBtX1IGQV+KEo1z5He2XnypCAWFPg21gR5icHUQbIw5ZHSyPCK61v3 ZfqHx3Fcu8S+J4nne4+QemzGDVOPnNQzKgqDn5ppDQt9IANAi59p7pg1WkppSvPV HGNJBywA+7T1xp1G6Lddrrgjo1lgGzCGAKvgAS9ebsDnhAbRX3wF4mf9z7bDhs9x 6K4plcpVDb0VRL4S+PaixclH2CO/42d23dWd184RBBNpqkbpgI1ge9trHd6xgTSo 5NL8z8Qw9BuDd60pkrBb =p8ki -----END PGP SIGNATURE----- --------------enigF56DE8664E6BCAE71CC31185-- From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 00:45:16 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A5FE106564A for ; Fri, 27 Apr 2012 00:45:16 +0000 (UTC) (envelope-from bryan@shatow.net) Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92]) by mx1.freebsd.org (Postfix) with ESMTP id D17748FC0A for ; Fri, 27 Apr 2012 00:45:15 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type; q=dns; s=sweb; b=BnaHsAJQMccIISJVVLUm1pjn7X61vaSM QgozIty+LwFn3uU8/KVobiT22IgEeAduMEyEzmQrMNEuIYYhU8MkPh6yyms0qVWQ sUXmWGt2T0smokCzHhmImQ7fHUSMN8Xzx0oIf4sPDEB9jCNFjupBVYE1uPOQmFlG Xv+bfT9UXJI= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type; s=sweb; bh=1MffpwC+JJie7XfwKEuNIN5m+UuJpftdYtkwux /3H58=; b=V+wgnkWOE/LOs6GmPJDcZXxwXqbppUUeFKJJHx8Ixy1Vln9nsvEHmM ZC6CtFNQuTEu2o5gqU8svoXObOVyrR3EJiaiX3seQeCyOSD/QjlbAErmU562CdQP OPe2dtMSekFzgxqsTw0BRho/l6MFDYAbgP5uyp+z8eOWpUgJlGSgc= Received: (qmail 96148 invoked from network); 26 Apr 2012 19:45:13 -0500 Received: from unknown (HELO ?192.168.0.107?) (bryan@shatow.net@74.94.87.209) by sweb.xzibition.com with ESMTPA; 26 Apr 2012 19:45:13 -0500 Message-ID: <4F99EC18.7050504@shatow.net> Date: Thu, 26 Apr 2012 19:45:12 -0500 From: Bryan Drewery User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 MIME-Version: 1.0 To: vermaden References: <4F99DBD9.5000409@shatow.net> In-Reply-To: <4F99DBD9.5000409@shatow.net> X-Enigmail-Version: 1.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7B722194CD223CD9A740FEA4" Cc: freebsd-fs@freebsd.org Subject: Re: HOWTO: FreeBSD ZFS Madness (Boot Environments) 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, 27 Apr 2012 00:45:16 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7B722194CD223CD9A740FEA4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 04/26/2012 06:35 PM, Bryan Drewery wrote: > On 04/26/2012 06:08 PM, vermaden wrote: >> Hi, >> >> I have just created new HOWTO [1] on how to use Boot Environments on >> FreeBSD with new created utility *beadm* that I put on SourceForge [2]= =2E >> >> Feel free to send Your ideas/critique about it. >> >> [1] http://forums.freebsd.org/showthread.php?t=3D31662 >> [2] https://sourceforge.net/projects/beadm/ >> >> Regards, >> vermaden >=20 >=20 > Very nice. >=20 > Can you give it a version so we can add it to ports? >=20 > Regards, > Bryan Drewery Hi, I have the port almost ready to go. Writing up a man page. If you want to give it a version number, that would be great before I submit it! Regards, Bryan Drewery --------------enig7B722194CD223CD9A740FEA4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmewYAAoJEG54KsA8mwz5UM4QAKD/HvBsBZR0LAVcpeF4fAWK gjc7CM1lBct5wc9eUoRTjZ/EmiFKj3Sqac3A36u+8shkBwVzWYLi9KezWc+QOuC2 KqdC9ICSYcF9nFJSgycVqvGH/BEFd0PWz/GTDsZfA+J1s0Xa5CgpoVBgzykd9J4J IXWYxrwDLY15X+vJ+jbx1v2OYAStby8rveQcEmtmd4kehG8RMRpuJXDH5u/9haBE HR8iPVGEN0CUinMwypYgxbdAHanLrt+JpSEBg/oWBJxpk4B42yNHLCzs6h2m/28o NCuc/0m1uhulRriB2xX+9LxlT5GD2YGI4dzEGojiRn1vQ/If0AI20mT2aVYFWkll 3oaSGCLwAis4Rzn4KWIIeWuJOVYYIh2Jq+LAJpbxs0xG6I98Kc/C1QXfy8HX9Cxk cgZ+jcDMUV7npbiZZNGE60rxnarjhth8+POom5mrD1POtxqPrXPtGoap0WAwqgS4 T6e+ouwZCyd1Ohc8BsI8n52yVi+2U9vCXtLTEP7XgT4sLATc3enIWv/WZyvyrhMC VHumHTzse1IVuCXymSTVgpJ+E2ijVQqcM3vd7SDAz3Jp2yX0lr1Yxe0QPFIraOg9 08nGYGUX1baruHbnzDDhZexclcpUMInhGi9zz2vJBrGJ+bwERZwFo1Fg4s0AzaQK F3lV9b5q+HK9LprZ+JWW =3Eit -----END PGP SIGNATURE----- --------------enig7B722194CD223CD9A740FEA4-- From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 04:14:30 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9641F106566B for ; Fri, 27 Apr 2012 04:14:30 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 44CC88FC0C for ; Fri, 27 Apr 2012 04:14:30 +0000 (UTC) Received: by vcmm1 with SMTP id m1so318074vcm.13 for ; Thu, 26 Apr 2012 21:14:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=a/pgLPAeeXcWAw++KR4dKed+T70VUWuBQ0PTlKuThao=; b=K+s+CMY32mnczaguCPwjvAOkRwD7lIa8xzoFPTdu8CDijWxtA2fH5vUT/dfUyip/D2 LvdLELQKT9WyC0TyRWZ9C9a8UZJ0nFFC5X1+wYE8+5aLc9p3BCJ8x1jpQfIROmQVdB2m lDXp3YTJLU7lUgp3HR0TOJfb6TP0/LVD1uw055ubGp1KVJchOI1IUWtLe0tpra+JXXmN GQxwAtNyg+TAzldXedXMRmHd6l1n0WKmm5jvf2l4tJ5ckqQDXuYZ72kfz7Et0aX1Gfrd q0ylStTgI/ohogWCbDd7OPTszAG1/1BnlU7PbnJZgdv5xtG0fYvr9oN9FWOFE3KykPX0 VHAQ== MIME-Version: 1.0 Received: by 10.52.70.109 with SMTP id l13mr8463434vdu.118.1335500069543; Thu, 26 Apr 2012 21:14:29 -0700 (PDT) Received: by 10.220.188.205 with HTTP; Thu, 26 Apr 2012 21:14:29 -0700 (PDT) In-Reply-To: <4F99EC18.7050504@shatow.net> References: <4F99DBD9.5000409@shatow.net> <4F99EC18.7050504@shatow.net> Date: Fri, 27 Apr 2012 12:14:29 +0800 Message-ID: From: Marcelo Araujo To: Bryan Drewery Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, vermaden Subject: Re: HOWTO: FreeBSD ZFS Madness (Boot Environments) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2012 04:14:30 -0000 Hey Bryan and Vermaden, Feel free to send the PORT to me, I can make tests and commit it on the ports tree. Nice tool! Best Regards, - Araujo 2012/4/27 Bryan Drewery > On 04/26/2012 06:35 PM, Bryan Drewery wrote: > > On 04/26/2012 06:08 PM, vermaden wrote: > >> Hi, > >> > >> I have just created new HOWTO [1] on how to use Boot Environments on > >> FreeBSD with new created utility *beadm* that I put on SourceForge [2]. > >> > >> Feel free to send Your ideas/critique about it. > >> > >> [1] http://forums.freebsd.org/showthread.php?t=31662 > >> [2] https://sourceforge.net/projects/beadm/ > >> > >> Regards, > >> vermaden > > > > > > Very nice. > > > > Can you give it a version so we can add it to ports? > > > > Regards, > > Bryan Drewery > > Hi, > > I have the port almost ready to go. Writing up a man page. If you want > to give it a version number, that would be great before I submit it! > > Regards, > Bryan Drewery > > -- Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 04:43:19 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BBDDB1065676 for ; Fri, 27 Apr 2012 04:43:19 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtpo.poczta.interia.pl (smtpo.poczta.interia.pl [217.74.65.208]) by mx1.freebsd.org (Postfix) with ESMTP id 757898FC12 for ; Fri, 27 Apr 2012 04:43:19 +0000 (UTC) From: vermaden To: Bryan Drewery X-Mailer: interia.pl/pf09 In-Reply-To: <4F99DBD9.5000409@shatow.net> References: <4F99DBD9.5000409@shatow.net> Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1335501798; bh=WaOu3SwCltzxHAkffE+OtT2UoBPAn0ALxFbfcCElHNg=; h=From:Subject:To:Cc:X-Mailer:In-Reply-To:References:Message-Id: MIME-Version:Content-Type:Content-Transfer-Encoding; b=Td1A+kjiYgkz9RwFWz0nzbujB8GPOG16zJTisa2O+jfXgXQJDuuFLiFgMjBE66G3n n8IsqAC7B0FnkhzRJNChlPMqTAlS3+qq1uU0nJCwU4gcXa47K1LqILxf0ZdE9vcaBc euPlAV4sqoUL6WnUuHQbew0GQCMHg31DiCJquTx0= Date: Fri, 27 Apr 2012 06:43:18 +0200 (CEST) Cc: freebsd-fs@freebsd.org Subject: Re: HOWTO: FreeBSD ZFS Madness (Boot Environments) 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, 27 Apr 2012 04:43:19 -0000 Hi, 0.2 should be ok, I already did many improvements ;) Regards, vermaden "Bryan Drewery" pisze: > On 04/26/2012 06:08 PM, vermaden wrote: > > Hi, > >=20 > > I have just created new HOWTO [1] on how to use Boot Environments on > > FreeBSD with new created utility *beadm* that I put on SourceForge [2]. > >=20 > > Feel free to send Your ideas/critique about it. > >=20 > > [1] http://forums.freebsd.org/showthread.php?t=3D31662 > > [2] https://sourceforge.net/projects/beadm/ > >=20 > > Regards, > > vermaden >=20 >=20 > Very nice. >=20 > Can you give it a version so we can add it to ports? >=20 > Regards, > Bryan Drewery >=20 >=20 --=20 ... From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 06:05:44 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF69F106564A for ; Fri, 27 Apr 2012 06:05:44 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 646388FC17 for ; Fri, 27 Apr 2012 06:05:44 +0000 (UTC) Received: by vcmm1 with SMTP id m1so369683vcm.13 for ; Thu, 26 Apr 2012 23:05:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=rjMpu540oFLYtY7kfVReHGboqqV1A5S6LoyuNRWen8w=; b=dOckC6G0PUlR9F+gkgC3GKUdscdJgRhtlnzWOuD6A5S/FoZxDjUyhFvAhTGhhFc8pN 1Dty8IJ+rcmcC3AnJ9UHUe0wiWb3uzHZY88W2BhTNtlYtbMVHQOu6xgeDBKZ35EEsH3K Ov4SNiI8/WZJuAsesvWWeh31i+omY8nzEtex3oLJKOEqP4cW80LTS16niTkRtFNT+IFP gPGSh1YQ3RIKXYWhX5TZBv7OxVOrIYv2Vr7huXZ5hsv6EDtmQJvwzvvYQYj111J68lik VdV7PuFFHwFxEPORYpPrXqGLoq94QjoKjvQYgpdWGNTzhKWxNpXWFvqTJzSR7+1Cb4zX YC/A== MIME-Version: 1.0 Received: by 10.52.22.207 with SMTP id g15mr5308734vdf.90.1335506743662; Thu, 26 Apr 2012 23:05:43 -0700 (PDT) Received: by 10.220.188.205 with HTTP; Thu, 26 Apr 2012 23:05:43 -0700 (PDT) Date: Fri, 27 Apr 2012 14:05:43 +0800 Message-ID: From: Marcelo Araujo To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ZFS - Block pointer rewrite X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2012 06:05:44 -0000 Hello everybody! I'm wondering if there is anyone working to implement "Block pointer rewrite" or how is the status of it. Best Regards, -- Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 08:28:00 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7355106564A for ; Fri, 27 Apr 2012 08:28:00 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 28D5A8FC17 for ; Fri, 27 Apr 2012 08:28:00 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC42A74.dip.t-dialin.net [79.196.42.116]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id F248E8443B6; Fri, 27 Apr 2012 10:19:36 +0200 (CEST) Received: from localhost (unknown [85.94.224.21]) by outgoing.leidinger.net (Postfix) with ESMTPSA id C22532CF6; Fri, 27 Apr 2012 10:19:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1335514774; bh=y9X4UvACydsgosmw7NgjnivRQSoJNw9G/qMBnU1TM+I=; h=Date:Subject:From:To:Cc; b=b4Yi1eNgQxP0o/hT5xCO4Z9E+8ccWYHRh0YwU8Xdt3SINLZcjULvPkpFSwj/0mx9w 5YXdkh7v3v275GGcjUPmOijPsDqVewc/ihZyFCwEQeJr8VWb1Fe3kuTtkEtPct5jD/ mtU4LWLdABpW0Qrz8sa2XWJJR4uyrhflpKwDZd209Qv8FkMvHwBt1Wl1w16A8giI8K PO2bSvVkguINWK20kaboZmKOPQaa3u0b5c/S7n8j7/iNG6YbaQnnXb9GAPso1x87IA 4T6pqdjKNEZKCnDAeRYgwKblmLE50RpnbvsIIEmKimIuGw6CeAoaiVqs1wW+VTiqyG FJ0rryZ2YngPg== Date: Fri, 27 Apr 2012 10:17:26 +0200 Message-ID: Importance: normal From: Alexander Leidinger To: vermaden@interia.pl, bryan@shatow.net MIME-Version: 1.0 X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: F248E8443B6.A30FB X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.959, required 6, autolearn=disabled, ALL_TRUSTED -1.00, AWL -0.36, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, SARE_HTML_MANY_BR05 0.50) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1336119579.3145@apu8J5T2UjE/+zzrpQu5MA X-EBL-Spam-Status: No Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: HOWTO: FreeBSD ZFS Madness (Boot Environments) 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, 27 Apr 2012 08:28:00 -0000 SGksCgpkbyB5b3Uga25vdyBtYW5hZ2VCRT8gR29vZ2xlIGZvciBpdCwgaXQgaXMgdGhlIGZpcnN0 IGhpdC4gVGhpcyB3b3JrcyBmb3IgbWUgbGlrZSBhIGNoYXJtIHNpbmNlIGFib3V0IGEgeWVhci4K CkJ5ZSwKQWxleGFuZGVyLgoKLS0gClNlbmQgdmlhIGFuIEFuZHJvaWQgZGV2aWNlLCBwbGVhc2Ug Zm9yZ2l2ZSBicmV2aXR5IGFuZCB0eXBvZ3JhcGhpYyBhbmQgc3BlbGxpbmcgZXJyb3JzLiAKCnZl cm1hZGVuIDx2ZXJtYWRlbkBpbnRlcmlhLnBsPiBoYXQgZ2VzY2hyaWViZW46SGksCgowLjIgc2hv dWxkIGJlIG9rLCBJIGFscmVhZHkgZGlkIG1hbnkgaW1wcm92ZW1lbnRzIDspCgpSZWdhcmRzLAp2 ZXJtYWRlbgoKIkJyeWFuIERyZXdlcnkiIDxicnlhbkBzaGF0b3cubmV0PiBwaXN6ZToKPiBPbiAw NC8yNi8yMDEyIDA2OjA4IFBNLCB2ZXJtYWRlbiB3cm90ZToKPiA+IEhpLAo+ID4gCj4gPiBJIGhh dmUganVzdCBjcmVhdGVkIG5ldyBIT1dUTyBbMV0gb24gaG93IHRvIHVzZSBCb290IEVudmlyb25t ZW50cyBvbgo+ID4gRnJlZUJTRCB3aXRoIG5ldyBjcmVhdGVkIHV0aWxpdHkgKmJlYWRtKiB0aGF0 IEkgcHV0IG9uIFNvdXJjZUZvcmdlIFsyXS4KPiA+IAo+ID4gRmVlbCBmcmVlIHRvIHNlbmQgWW91 ciBpZGVhcy9jcml0aXF1ZSBhYm91dCBpdC4KPiA+IAo+ID4gWzFdIGh0dHA6Ly9mb3J1bXMuZnJl ZWJzZC5vcmcvc2hvd3RocmVhZC5waHA/dD0zMTY2Mgo+ID4gWzJdIGh0dHBzOi8vc291cmNlZm9y Z2UubmV0L3Byb2plY3RzL2JlYWRtLwo+ID4gCj4gPiBSZWdhcmRzLAo+ID4gdmVybWFkZW4KPiAK PiAKPiBWZXJ5IG5pY2UuCj4gCj4gQ2FuIHlvdSBnaXZlIGl0IGEgdmVyc2lvbiBzbyB3ZSBjYW4g YWRkIGl0IHRvIHBvcnRzPwo+IAo+IFJlZ2FyZHMsCj4gQnJ5YW4gRHJld2VyeQo+IAo+IAoKCgot LSAKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCi4uLgpfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpmcmVlYnNkLWZzQGZyZWVic2Qu b3JnIG1haWxpbmcgbGlzdApodHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5m by9mcmVlYnNkLWZzClRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLWZz LXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIgoK From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 09:06:19 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 790D71065673; Fri, 27 Apr 2012 09:06:19 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8F1F38FC1B; Fri, 27 Apr 2012 09:06:18 +0000 (UTC) Received: from porto.starpoint.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 MAA05215; Fri, 27 Apr 2012 12:06:14 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1SNh81-0007Wn-VU; Fri, 27 Apr 2012 12:06:14 +0300 Message-ID: <4F9A6180.8090500@FreeBSD.org> Date: Fri, 27 Apr 2012 12:06:08 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120425 Thunderbird/12.0 MIME-Version: 1.0 To: Marius Strobl References: <4F8999D2.1080902@FreeBSD.org> <20120422212102.GA66855@alchemy.franken.de> In-Reply-To: <20120422212102.GA66855@alchemy.franken.de> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: [review request] zfsboot/zfsloader: support accessing filesystems within a pool 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, 27 Apr 2012 09:06:19 -0000 on 23/04/2012 00:21 Marius Strobl said the following: > On Sat, Apr 14, 2012 at 06:37:54PM +0300, Andriy Gapon wrote: [snip] >> I am particularly interested in reviews of my attempt to make ZFS boot support >> arch-independent. The arches, of course, would have to add some code to make >> use of that support. Currently I only enabled it for x86. >> > > I can't say much about these patches as a whole as they are rather > big and I'm not aware of all the details of ZFS. However, one bit that > makes the current implementation x86-specific is zfs_dev_init(). If > you could move it to the MD part in the course of these patches that > would be great. I have arranged this in my WIP version of the patch, which I hope to share soon. Need to work out some unrelated details. > If you could also take the second patch in PR 165025 > into account, which I plan to commit once the issue with the current > ofw_disk.c are properly solved, that would be great. Thank you for the heads up. Since I also hope to commit my patch rather soon, I would also appreciate if you keep my changes in mind :-) In fact, I would like to ask you if it would make sense to postpone the patch from the PR until my patch is committed. That should make some things easier to do (e.g. MD zfs_dev_init), but on the other hand some things would become different. Either way, one of the patches would have to be rebased on top of the other. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 09:06:36 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 859C010657F9; Fri, 27 Apr 2012 09:06:36 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtpo.poczta.interia.pl (smtpo.poczta.interia.pl [217.74.65.208]) by mx1.freebsd.org (Postfix) with ESMTP id 3B4AE8FC15; Fri, 27 Apr 2012 09:06:36 +0000 (UTC) From: vermaden To: Alexander Leidinger X-Mailer: interia.pl/pf09 In-Reply-To: References: Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1335517594; bh=rU2KbEtKk80OFlXGvv3raUz+xGBa3w926WBeNbkAYPE=; h=From:Subject:To:Cc:X-Mailer:In-Reply-To:References:Message-Id: MIME-Version:Content-Type:Content-Transfer-Encoding; b=M+qN7Xr4pyx3mbXUbuMtkoJRCju6S9BH5zayXoZ9sbpKDHIuG/fRzGg2GGRXmk5A5 WtMzA8LAKU4/RyBG68hN4vy0FUdMYlCxmMNYHrxSwJvQ7XeGeC+0oVtQXxg1Dh7274 7hdVvcXQPIt8W/G+QXgoMgyJiAQZCsjyBFBePxP0= Date: Fri, 27 Apr 2012 11:06:35 +0200 (CEST) Cc: freebsd-fs@freebsd.org, freebsd-questions@freebsd.org Subject: Re: HOWTO: FreeBSD ZFS Madness (Boot Environments) 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, 27 Apr 2012 09:06:36 -0000 > Hi, >=20 > do you know manageBE? Google for it, it is the first > hit. This works for me like a charm since about a year. >=20 > Bye, > Alexander. Hi, yes I know and used manageBE for a while, I even mentioned it in the HOWTO (quote below) but thought that making *beadm* that is compatible with Illumos/Solaris version would be nice idea, *beadm* is also more comfortable to use, at least for me. Mine *beadm* has also a feature to activate BE's from other machines. =20 > Illumos/Solaris has the beadm(1M) [4] utility and while > Philipp Wuensche wrote the manageBE script as > replacement [5], it uses older style used at times when > OpenSolaris (and SUN) were still having a great time. > I last couple of days writing an up-to-date replacement for > FreeBSD compatible beadm utility, and with some tweaks > from today I just made it available at SourceForge [6] if You > wish to test it. Currently its about 200 lines long, so it should > be pretty simple to take a look at it. I tried to make it as > compatible as possible with the 'upstream' version, along > with some small improvements, it currently supports basic > functions like list, create, destroy and activate. (...) > There are several subtle differences between mine > implementation and Philipp's one, he defines and then relies > upon ZFS property called freebsd:boot-environment=3D1 for > each boot environment, I do not set any other additional > ZFS properties. There is already org.freebsd:swap property > used for SWAP on FreeBSD, so we may use org.freebsd:be in > the future, but is just a thought, right now its not used. My > version also supports activating boot environments received > with zfs recv command from other systems (it just updates > appreciate /boot/zfs/zpool.cache file). Regards, vermaden ... From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 09:14:26 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD5A8106566B; Fri, 27 Apr 2012 09:14:26 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 577048FC15; Fri, 27 Apr 2012 09:14:25 +0000 (UTC) Received: from porto.starpoint.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 MAA05309; Fri, 27 Apr 2012 12:14:23 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1SNhFv-0007XH-Gq; Fri, 27 Apr 2012 12:14:23 +0300 Message-ID: <4F9A6369.5060305@FreeBSD.org> Date: Fri, 27 Apr 2012 12:14:17 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120425 Thunderbird/12.0 MIME-Version: 1.0 To: "Andrey V. Elsukov" References: <4F8999D2.1080902@FreeBSD.org> <20120422212102.GA66855@alchemy.franken.de> <4F94F56E.1010501@FreeBSD.org> In-Reply-To: <4F94F56E.1010501@FreeBSD.org> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-hackers@FreeBSD.org, John Baldwin , Marius Strobl Subject: Re: [review request] zfsboot/zfsloader: support accessing filesystems within a pool 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, 27 Apr 2012 09:14:26 -0000 on 23/04/2012 09:23 Andrey V. Elsukov said the following: > On 23.04.2012 1:21, Marius Strobl wrote: >> I can't say much about these patches as a whole as they are rather big >> and I'm not aware of all the details of ZFS. However, one bit that makes >> the current implementation x86-specific is zfs_dev_init(). If you could >> move it to the MD part in the course of these patches that would be >> great. If you could also take the second patch in PR 165025 into account, >> which I plan to commit once the issue with the current ofw_disk.c are >> properly solved, that would be great. > > I also have some WIP related to moving partition table handling into MD > part. You can look here: http://people.freebsd.org/~ae/sys_boot.diff I like this patch. OTOH, I couldn't help by wonder if it is possible to somehow directly re-use the results of dv_init probing by other drivers (or subset of the drivers, like only 'disk'). E.g. if instead of re-examining the partition tables, we could ask a driver for a list of devices that it discovered. But how to do that is not something that I can answer. > This patch have one problem, there is no way to determine disk size and i'm > thinking about adding ioctl(DIOCGMEDIASIZE) to the "disk" devsw. > -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 10:37:36 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB398106564A; Fri, 27 Apr 2012 10:37:36 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from mail.kirov.so-ups.ru (mail.kirov.so-ups.ru [178.74.170.1]) by mx1.freebsd.org (Postfix) with ESMTP id 813B18FC08; Fri, 27 Apr 2012 10:37:36 +0000 (UTC) Received: from kas30pipe.localhost (localhost.kirov.so-ups.ru [127.0.0.1]) by mail.kirov.so-ups.ru (Postfix) with SMTP id ADFCCB801B; Fri, 27 Apr 2012 14:37:25 +0400 (MSK) Received: from kirov.so-ups.ru (unknown [172.21.81.1]) by mail.kirov.so-ups.ru (Postfix) with ESMTP id A82F0B8008; Fri, 27 Apr 2012 14:37:25 +0400 (MSK) Received: by ns.kirov.so-ups.ru (Postfix, from userid 1010) id A14B8BA022; Fri, 27 Apr 2012 14:37:25 +0400 (MSK) Received: from [127.0.0.1] (unknown [10.118.3.52]) by ns.kirov.so-ups.ru (Postfix) with ESMTP id 682B9BA01D; Fri, 27 Apr 2012 14:37:25 +0400 (MSK) Message-ID: <4F9A76E5.7000809@FreeBSD.org> Date: Fri, 27 Apr 2012 14:37:25 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Andriy Gapon References: <4F8999D2.1080902@FreeBSD.org> <20120422212102.GA66855@alchemy.franken.de> <4F94F56E.1010501@FreeBSD.org> <4F9A6369.5060305@FreeBSD.org> In-Reply-To: <4F9A6369.5060305@FreeBSD.org> X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0284], KAS30/Release X-SpamTest-Info: Not protected Cc: freebsd-fs@FreeBSD.org, freebsd-hackers@FreeBSD.org, John Baldwin , Marius Strobl Subject: Re: [review request] zfsboot/zfsloader: support accessing filesystems within a pool 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, 27 Apr 2012 10:37:36 -0000 On 27.04.2012 13:14, Andriy Gapon wrote: >> I also have some WIP related to moving partition table handling into MD Oh, i did mean MI part. >> part. You can look here: http://people.freebsd.org/~ae/sys_boot.diff > > I like this patch. OTOH, I couldn't help by wonder if it is possible to > somehow directly re-use the results of dv_init probing by other drivers (or > subset of the drivers, like only 'disk'). E.g. if instead of re-examining the > partition tables, we could ask a driver for a list of devices that it discovered. > But how to do that is not something that I can answer. What you think about this concept: We can implement some MI API to query disks count and each disk parameters (mediasize, sectorsize). This MI code will use some IOCTL that will act with MD "disk"'s devsw->ioctl. devicename.c functions can be changed to use MI DISK API together with PART API, or maybe even moved to the MI code. In the result we will have some MI API to get access to the disks and partitions, that we can use anywhere, e.g. in the ZFS code. -- WBR, Andrey V. Elsukov From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 14:07:11 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F354D1065670; Fri, 27 Apr 2012 14:07:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 63F998FC0C; Fri, 27 Apr 2012 14:07:09 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA09079; Fri, 27 Apr 2012 17:07:07 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4F9AA80A.6040506@FreeBSD.org> Date: Fri, 27 Apr 2012 17:07:06 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120426 Thunderbird/12.0 MIME-Version: 1.0 To: "Andrey V. Elsukov" References: <4F8999D2.1080902@FreeBSD.org> <20120422212102.GA66855@alchemy.franken.de> <4F94F56E.1010501@FreeBSD.org> <4F9A6369.5060305@FreeBSD.org> <4F9A76E5.7000809@FreeBSD.org> In-Reply-To: <4F9A76E5.7000809@FreeBSD.org> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-hackers@FreeBSD.org, John Baldwin , Marius Strobl Subject: Re: [review request] zfsboot/zfsloader: support accessing filesystems within a pool 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, 27 Apr 2012 14:07:11 -0000 on 27/04/2012 13:37 Andrey V. Elsukov said the following: > What you think about this concept: > We can implement some MI API to query disks count and each disk parameters (mediasize, > sectorsize). This MI code will use some IOCTL that will act with MD "disk"'s devsw->ioctl. > > devicename.c functions can be changed to use MI DISK API together with PART API, > or maybe even moved to the MI code. > > In the result we will have some MI API to get access to the disks and partitions, > that we can use anywhere, e.g. in the ZFS code. Sorry, but I couldn't understand your design. Probably I am missing the bigger picture. I think that for ZFS case it would be sufficient to be able to iterate over detected device names or devspecs. Size and other disk properties do not seem to be needed. Unless I am mistaken, of course. E.g. something akin to what bd_print (dv_print, in the general case) does but oriented towards programmatic use rather than end-user. Maybe all that partition table parsing should be done only once (e.g. in the init method) and the result should be saved. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 19:32:50 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3AC87106564A; Fri, 27 Apr 2012 19:32:50 +0000 (UTC) (envelope-from araujo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0DE9A8FC08; Fri, 27 Apr 2012 19:32:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3RJWnMH012123; Fri, 27 Apr 2012 19:32:49 GMT (envelope-from araujo@freefall.freebsd.org) Received: (from araujo@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3RJWnsC012119; Fri, 27 Apr 2012 19:32:49 GMT (envelope-from araujo) Date: Fri, 27 Apr 2012 19:32:49 GMT Message-Id: <201204271932.q3RJWnsC012119@freefall.freebsd.org> To: araujo@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: araujo@FreeBSD.org Cc: Subject: Re: kern/167370: [ZFS] - Unnecessary break point on zfs_main.c. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2012 19:32:50 -0000 Synopsis: [ZFS] - Unnecessary break point on zfs_main.c. Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: araujo Responsible-Changed-When: Fri Apr 27 19:32:49 UTC 2012 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=167370 From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 19:33:41 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6634D106564A; Fri, 27 Apr 2012 19:33:41 +0000 (UTC) (envelope-from araujo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 39D038FC12; Fri, 27 Apr 2012 19:33:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3RJXfa6012354; Fri, 27 Apr 2012 19:33:41 GMT (envelope-from araujo@freefall.freebsd.org) Received: (from araujo@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3RJXfiH012350; Fri, 27 Apr 2012 19:33:41 GMT (envelope-from araujo) Date: Fri, 27 Apr 2012 19:33:41 GMT Message-Id: <201204271933.q3RJXfiH012350@freefall.freebsd.org> To: araujo@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: araujo@FreeBSD.org Cc: Subject: Re: kern/167371: [ZFS] - Assertion failed in user land tasks_destroy() 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, 27 Apr 2012 19:33:41 -0000 Synopsis: [ZFS] - Assertion failed in user land tasks_destroy() Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: araujo Responsible-Changed-When: Fri Apr 27 19:33:40 UTC 2012 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=167371 From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 19:58:09 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51D261065670; Fri, 27 Apr 2012 19:58:09 +0000 (UTC) (envelope-from delphij@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 256C98FC0C; Fri, 27 Apr 2012 19:58:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3RJw9vZ029951; Fri, 27 Apr 2012 19:58:09 GMT (envelope-from delphij@freefall.freebsd.org) Received: (from delphij@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3RJw95f029947; Fri, 27 Apr 2012 19:58:09 GMT (envelope-from delphij) Date: Fri, 27 Apr 2012 19:58:09 GMT Message-Id: <201204271958.q3RJw95f029947@freefall.freebsd.org> To: araujo@FreeBSD.org, delphij@FreeBSD.org, freebsd-fs@FreeBSD.org From: delphij@FreeBSD.org Cc: Subject: Re: kern/167371: [ZFS] - Assertion failed in user land tasks_destroy() 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, 27 Apr 2012 19:58:09 -0000 Synopsis: [ZFS] - Assertion failed in user land tasks_destroy() State-Changed-From-To: open->closed State-Changed-By: delphij State-Changed-When: Fri Apr 27 19:57:36 UTC 2012 State-Changed-Why: This patch is not right. It depends on more Illumos code and breaks build if applied. http://www.freebsd.org/cgi/query-pr.cgi?pr=167371 From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 20:30:13 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B6DF1065670 for ; Fri, 27 Apr 2012 20:30:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 46C688FC08 for ; Fri, 27 Apr 2012 20:30:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3RKUDWW057517 for ; Fri, 27 Apr 2012 20:30:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3RKUDmF057516; Fri, 27 Apr 2012 20:30:13 GMT (envelope-from gnats) Date: Fri, 27 Apr 2012 20:30:13 GMT Message-Id: <201204272030.q3RKUDmF057516@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/167266: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2012 20:30:13 -0000 The following reply was made to PR kern/167266; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/167266: commit references a PR Date: Fri, 27 Apr 2012 20:23:35 +0000 (UTC) Author: rmacklem Date: Fri Apr 27 20:23:24 2012 New Revision: 234740 URL: http://svn.freebsd.org/changeset/base/234740 Log: Fix a leak of namei lookup path buffers that occurs when a ZFS volume is exported via the new NFS server. The leak occurred because the new NFS server code didn't handle the case where a file system sets the SAVENAME flag in its VOP_LOOKUP() and ZFS does this for the DELETE case. Tested by: Oliver Brandmueller (ob at gruft.de), hrs PR: kern/167266 MFC after: 1 month Modified: head/sys/fs/nfsserver/nfs_nfsdport.c Modified: head/sys/fs/nfsserver/nfs_nfsdport.c ============================================================================== --- head/sys/fs/nfsserver/nfs_nfsdport.c Fri Apr 27 20:16:20 2012 (r234739) +++ head/sys/fs/nfsserver/nfs_nfsdport.c Fri Apr 27 20:23:24 2012 (r234740) @@ -1047,6 +1047,8 @@ nfsvno_removesub(struct nameidata *ndp, else vput(ndp->ni_dvp); vput(vp); + if ((ndp->ni_cnd.cn_flags & SAVENAME) != 0) + nfsvno_relpathbuf(ndp); NFSEXITCODE(error); return (error); } @@ -1086,6 +1088,8 @@ out: else vput(ndp->ni_dvp); vput(vp); + if ((ndp->ni_cnd.cn_flags & SAVENAME) != 0) + nfsvno_relpathbuf(ndp); NFSEXITCODE(error); return (error); } _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Fri Apr 27 23:09:14 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D0EE106566C for ; Fri, 27 Apr 2012 23:09:14 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 52F828FC08 for ; Fri, 27 Apr 2012 23:09:14 +0000 (UTC) Received: by qcsg15 with SMTP id g15so799308qcs.13 for ; Fri, 27 Apr 2012 16:09:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=ZCckltsVj8MOdvjvf/Bzk6V89DKOIRVPFZRhxKZ6GMQ=; b=iRAqy34BR/PrNMf8GLAvOeaVA7wwjBO+vxJHUhgTWvXRst4QqV+XeAAQfOUXsUEYGq lZP7KkMXjxH6ltuRj0hbKbaBsNFw91F2XWJEqFZOqshHvfx3bAU5jPuuICTQTljMNie9 2XWdoTqyocUtXg7PSEmwbLz+ClqwO7fP58CcrCPEI0rgDqWj4CG5bwKzMEYU15GFF8Ao TK0cQeqxefeQf1ikQ9WZi99VvtFXEze5nPpsZzNu869ZNqqYqdl5Hdk7WfyHR6KgJZ4x tAGDO+mObpm6P3iEtz1M0i/7Go2REOsDPXxR4u1qnqS9SYs8ZL1SgU1EQJQwplw+BJ+z 28zw== MIME-Version: 1.0 Received: by 10.229.135.78 with SMTP id m14mr3235290qct.129.1335568150823; Fri, 27 Apr 2012 16:09:10 -0700 (PDT) Received: by 10.229.121.211 with HTTP; Fri, 27 Apr 2012 16:09:10 -0700 (PDT) In-Reply-To: <4F7C4B46.7030305@pean.org> References: <4F7C4B46.7030305@pean.org> Date: Fri, 27 Apr 2012 16:09:10 -0700 Message-ID: From: "bsalinux@gmail.com" To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Swap on ZFS / swap_pager: indefinite wait buffer 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, 27 Apr 2012 23:09:14 -0000 After moving swap to another USB stick, these are gone but the system still goes unresponsive after few days of continuous write. The machine responds to ping but no nfs or ssh or other services. There is nothing in /var/log/messages. Thanks, On Wed, Apr 4, 2012 at 6:23 AM, Peter Ankerst=E5l wrote: > On 04/02/2012 08:13 PM, bsalinux@gmail.com wrote: >> >> Hi, >> >> I have been running FreeBSD 9.0-RELEASE from a USB stick running ZFS. >> I have created swap file on zfs volume using the md driver. >> >> Swapinfo shows >> >> Device =A0 =A0 =A0 =A0 =A01K-blocks =A0 =A0 Used =A0 =A0Avail Capacity >> /dev/md0 =A0 =A0 =A0 =A0 =A04194304 =A0 =A0 =A0 =A00 =A04194304 =A0 =A0 = 0% >> >> >> The system has hung twice and all I can find in the log is >> >> Mar 22 03:17:30 server kernel: swap_pager: indefinite wait buffer: >> bufobj: 0, blkno: 927, size: 4096 >> Mar 23 09:00:26 server kernel: swap_pager: indefinite wait buffer: >> bufobj: 0, blkno: 55, size: 4096 >> Mar 23 22:01:26 server kernel: swap_pager: indefinite wait buffer: >> bufobj: 0, blkno: 49, size: 4096 >> Mar 24 04:00:38 server kernel: swap_pager: indefinite wait buffer: >> bufobj: 0, blkno: 60, size: 4096 >> >> As the swap is on zfs, I assume it is not failing. >> >> Do I need to move swap off of ZFS? >> >> Thanks >> _______________________________________________ >> 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" >> > I had alot of this when I had swap on zfs. Everything went away when I mo= ved > the swap off > zfs. > _______________________________________________ > 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 Sat Apr 28 01:05:59 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A683F106566B for ; Sat, 28 Apr 2012 01:05:59 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 675FE8FC12 for ; Sat, 28 Apr 2012 01:05:59 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q3S15rg2027393; Fri, 27 Apr 2012 20:05:53 -0500 (CDT) Date: Fri, 27 Apr 2012 20:05:52 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: "bsalinux@gmail.com" In-Reply-To: Message-ID: References: <4F7C4B46.7030305@pean.org> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Fri, 27 Apr 2012 20:05:53 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: Swap on ZFS / swap_pager: indefinite wait buffer 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, 28 Apr 2012 01:05:59 -0000 On Fri, 27 Apr 2012, bsalinux@gmail.com wrote: > After moving swap to another USB stick, these are gone but the system > still goes unresponsive after few days of continuous write. The > machine responds to ping but no nfs or ssh or other services. Why would one decide to put swap on a USB stick? If it is NAND-flash based it would likely only last for a few days of continuous write before it should be tossed in the dumpster. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Sat Apr 28 02:50:52 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CEE4106566C for ; Sat, 28 Apr 2012 02:50:52 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 41B1D8FC08 for ; Sat, 28 Apr 2012 02:50:52 +0000 (UTC) Received: by qcsg15 with SMTP id g15so855358qcs.13 for ; Fri, 27 Apr 2012 19:50:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=MC1VKM5uSeethSBtzOA0rYfQbQFUZXZm2CPPpySEGeE=; b=tPHiYk27lRbKd1edlmn5g7fFzRbnPhv/1fKYt0qA4eT2lmamCsQ9us0pYkgQEfwNc5 o6VwPSF4/6gYp3ZuBktPqnROKYOlqah4ED2AZcaz3xOCUufdPe8qZccBKa4MVSQ2FXsO WVIUQQ7CV6fbvYQ0HWXiT1Yd824zefuNWKwA8T3SKT2tzuNsZZFPK3K12vR8RcZ+0Vwj nPWE/F1oYpBtdfO+uXoNb6VaD6inN3WVjAAVQWSPBH54p+H4I/KZcTVyj63Lc4SlWgrO dOS45UC9mTe4a3Ory/6W4m3U1G8x3VJC8ZdahAJSM31hZs8l7t5f8dV1aHiAB6tpg3Rb a5Cg== MIME-Version: 1.0 Received: by 10.229.135.10 with SMTP id l10mr3398311qct.6.1335581451800; Fri, 27 Apr 2012 19:50:51 -0700 (PDT) Received: by 10.229.121.211 with HTTP; Fri, 27 Apr 2012 19:50:51 -0700 (PDT) In-Reply-To: References: <4F7C4B46.7030305@pean.org> Date: Fri, 27 Apr 2012 19:50:51 -0700 Message-ID: From: "bsalinux@gmail.com" To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Swap on ZFS / swap_pager: indefinite wait buffer 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, 28 Apr 2012 02:50:52 -0000 No other choice. How does freenas do it? Any inputs would be appreciated. Thanks. On Fri, Apr 27, 2012 at 6:05 PM, Bob Friesenhahn wrote: > Why would one decide to put swap on a USB stick? =A0If it is NAND-flash b= ased From owner-freebsd-fs@FreeBSD.ORG Sat Apr 28 12:05:49 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 021C3106566B for ; Sat, 28 Apr 2012 12:05:49 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nschwmtas01p.mx.bigpond.com (nschwmtas01p.mx.bigpond.com [61.9.189.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7A4068FC0A for ; Sat, 28 Apr 2012 12:05:46 +0000 (UTC) Received: from nschwotgx04p.mx.bigpond.com ([124.188.161.100]) by nschwmtas01p.mx.bigpond.com with ESMTP id <20120428120544.UZUY24679.nschwmtas01p.mx.bigpond.com@nschwotgx04p.mx.bigpond.com>; Sat, 28 Apr 2012 12:05:44 +0000 Received: from johnny.reilly.home ([124.188.161.100]) by nschwotgx04p.mx.bigpond.com with ESMTP id <20120428120544.FDCW1687.nschwotgx04p.mx.bigpond.com@johnny.reilly.home>; Sat, 28 Apr 2012 12:05:44 +0000 Date: Sat, 28 Apr 2012 22:05:34 +1000 From: Andrew Reilly To: Peter Maloney Message-ID: <20120428120534.GA1953@johnny.reilly.home> References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> <20120424232136.GA1441@johnny.reilly.home> <4F981A0D.40507@brockmann-consult.de> <20120426033314.GA9016@johnny.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120426033314.GA9016@johnny.reilly.home> User-Agent: Mutt/1.4.2.3i X-SIH-MSG-ID: qBkxGNz7TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rAIudRsM6kxDxEJhuHNGElaajgTY3Rs9uK Cc: freebsd-fs@freebsd.org Subject: Re: Odd file system corruption in ZFS pool 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, 28 Apr 2012 12:05:49 -0000 On Thu, Apr 26, 2012 at 01:33:14PM +1000, Andrew Reilly wrote: > Seems to be only associated with the filesystem, rather than the > pool. Well, my "tank" pool, (the raidz) shows zpool scrub > making 0 fixes but there being unrecoverable erorrs in > tank/home:<0x0>, but my backup file system (the one I send > snapshot deltas to) shows exactly the same errors with no tank > problems. (Hmm. Hold that thought: I haven't actually tried a > scrub on the backup file system. It's just zpool status that > shows no errors. Running a scrub now. Will take a while: it's > a fairly slow USB2-connected disk. Zpool status says expect 10+ > hours...) Just want to update this: zpool scrub on the bkp2pool finished with zero errors found, but the filesystem corruption noticed in the main pool (tank/home) has been faithfully reproduced. That is: I have a directory Maildir.bad that echo .* shows: Maildir.bad/. Maildir.bad/.. Maildir.bad/.AppleDouble Maildir.bad/.Suppliers.2010 Maildir.bad/.Unix But the .Suppliers.2010 entry does not seem to have an inode number (let alone an inode): $ ls -ai Maildir.bad returns: ls: .Suppliers.2010: No such file or directory 7906 . 7810 .. 82016 .AppleDouble 80774 .Unix Is this not terminally weird? Is there any way to de-confuse ZFS? Since memtest86+ did not seem to boot properly on this system, I've ordered new memory (twice as much: will be 8G now.) Also ordered a UPS. We'll see if that helps with anything. Cheers, -- Andrew From owner-freebsd-fs@FreeBSD.ORG Sat Apr 28 12:23:55 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4515D106566C for ; Sat, 28 Apr 2012 12:23:55 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id B79578FC15 for ; Sat, 28 Apr 2012 12:23:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id q3SCNqn3081954; Sat, 28 Apr 2012 16:23:52 +0400 (MSK) (envelope-from marck@rinet.ru) Date: Sat, 28 Apr 2012 16:23:52 +0400 (MSK) From: Dmitry Morozovsky To: "bsalinux@gmail.com" In-Reply-To: Message-ID: References: <4F7C4B46.7030305@pean.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (woozle.rinet.ru [0.0.0.0]); Sat, 28 Apr 2012 16:23:52 +0400 (MSK) Cc: freebsd-fs@freebsd.org Subject: Re: Swap on ZFS / swap_pager: indefinite wait buffer 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, 28 Apr 2012 12:23:55 -0000 On Fri, 27 Apr 2012, bsalinux@gmail.com wrote: > No other choice. > How does freenas do it? IIRC freenas aboids using swap at all. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------