From owner-freebsd-fs@FreeBSD.ORG Sun Nov 4 03:23:46 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 0977B7C0 for ; Sun, 4 Nov 2012 03:23:46 +0000 (UTC) (envelope-from fjwcash@gmail.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 6E6448FC08 for ; Sun, 4 Nov 2012 03:23:45 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id b5so4325700lbd.13 for ; Sat, 03 Nov 2012 20:23:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Hwr1/YFr7+qCpS/5sOUte1HKdVVxw8Z7+CGZWRhPaq8=; b=RqqtApbs4gdJg2jNoQR3v2TeMRiK9Qt3Xf+BNhY0dw9xx8CZ5xSLECSXBfBBnd4pwo VesxLhwQ9fBfADOgOu/34nqNsJ0mVIdXVQAhm9F8VPEhnaUKfBpDUBG2lC4QGVkEzVyq DkYS/MmBnF/eHl/cSiska6/OxL/m65l8YtPpS2QJJPXRvPSQ1kUIelwaW2LTeadzitqB Bkmmle7FAzrx0LqnWVq1PcJs07Ov9PV1DXjwLC7EIhRoHJFilyl33oFEJ5ugHTdtspYO J9byxmWczNF3caHuzmxKqRUmp+f20sLnBlPpy+PfMeClekUVETH2ZEnsL3gIrfOx7zej KP9w== MIME-Version: 1.0 Received: by 10.152.124.83 with SMTP id mg19mr5678284lab.6.1351999424060; Sat, 03 Nov 2012 20:23:44 -0700 (PDT) Received: by 10.114.24.66 with HTTP; Sat, 3 Nov 2012 20:23:43 -0700 (PDT) Received: by 10.114.24.66 with HTTP; Sat, 3 Nov 2012 20:23:43 -0700 (PDT) In-Reply-To: <50955FB1.2070800@cyberfoxfire.com> References: <50955FB1.2070800@cyberfoxfire.com> Date: Sat, 3 Nov 2012 20:23:43 -0700 Message-ID: Subject: Re: Convert standalone zpool to RAID1 with data in place From: Freddie Cash To: Fox F Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Nov 2012 03:23:46 -0000 You don't. At least, not in that order. Or, at least not with the ZFS-native tools. You can create a pool with 2 separate single-disk vdevs, and data will be striped across them. Similar to RAID0, there will be no redundancy to the pool. zpool create poolname disk1 disk2 Later, you can convert the single-disk vdevs to mirrors, thus turning the pool into a RAID10: zpool attach poolname disk1 disk3 zpool attach poolname disk2 disk4 Or, you can create a pool with a single mirror vdev: zpool create poolname mirror disk1 disk2 Later, you can add another mirror vdev to the pool, and data will be striped across the two vdevs, similar to a RAID10: zpool add poolname mirror disk3 disk4 If you are truly hell bent on doing things in the other order (mirror on top of two stripesets), then you have to use gstripe(8) to create the stripesets, and then add those to the pool. The following is from memory, so it may not be perfectly correct: gstripe label stripe1 disk1 disk2 gstripe label stripe2 disk3 disk4 zpool create poolname mirror stripe/stripe1 stripe/stripe2 On Nov 3, 2012 11:17 AM, "Fox F" wrote: > > Hello, > > My intention is to have a zpool with two drives (1TB and 2TB) striped. I suppose I'd create it as such: > > zpool create zp_test disk1 disk2 > > I would then create a zfs filesystem on that zpool and add data to it. > > Then, I would want to mirror this data on another identical striped vdev. > > The question is, what is the order of operations for creating the second striped vdev and adding it as a mirror to the first one, and how do I do that in such a way that the data on disk1/2 gets mirrored to the new addition? > > I hope I am making sense. > > -F > _______________________________________________ > 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 Sun Nov 4 19:50:56 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 E8A2F3A8 for ; Sun, 4 Nov 2012 19:50:56 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 5D16C8FC17 for ; Sun, 4 Nov 2012 19:50:55 +0000 (UTC) Received: from server.rulingia.com (c220-239-241-202.belrs5.nsw.optusnet.com.au [220.239.241.202]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id qA4Joljj091588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Nov 2012 06:50:47 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id qA4JoffJ030606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Nov 2012 06:50:41 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id qA4Jofnw030605; Mon, 5 Nov 2012 06:50:41 +1100 (EST) (envelope-from peter) Date: Mon, 5 Nov 2012 06:50:41 +1100 From: Peter Jeremy To: Garrett Cooper Subject: Re: Inconsistent/potentially incorrect behavior with relative lookups via chdir(2) on UFS/ZFS Message-ID: <20121104195041.GE12996@server.rulingia.com> References: <20121103103849.GD12996@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lCAWRPmW1mITcIfM" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Nov 2012 19:50:57 -0000 --lCAWRPmW1mITcIfM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Nov-03 13:56:04 -0700, Garrett Cooper wrote: >On Sat, Nov 3, 2012 at 3:38 AM, Peter Jeremy wrote: >> Whilst playing with the above, I've found some wierd timing issues >> with UFS+SU: >> >> $ mkdir -p ~/p/q/r;sync >> $ cd p/q/r >> $ rm -r ~/p; while date; do sleep 3 ; ls -al;done >> Sat 3 Nov 2012 21:29:19 EST >> total 2 >> drwxr-xr-x 0 peter jeremy 512 3 Nov 21:28 . >> drwxr-xr-x 0 peter jeremy 0 3 Nov 21:29 .. >> Sat 3 Nov 2012 21:29:22 EST =2E.. >> Sat 3 Nov 2012 21:29:46 EST >> total 0 >> Sat 3 Nov 2012 21:29:49 EST >> > > Interesting; with SU-J or SUJ (my testing was with the default: SUJ)? This was on 8.3 with no journalling. I haven't tried on later variants. I couldn't reproduce it with ZFS and couldn't always reproduce it with UFS. --=20 Peter Jeremy --lCAWRPmW1mITcIfM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCWxxEACgkQ/opHv/APuIen9QCfaDzZY3s1L/bCfgmidxyYMNAF HuwAmwei84eQ5OGLj6SkFxB3Lq/Q4T38 =b5Z1 -----END PGP SIGNATURE----- --lCAWRPmW1mITcIfM-- From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 02:36:54 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 4314DBF3; Mon, 5 Nov 2012 02:36:54 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 115118FC12; Mon, 5 Nov 2012 02:36:54 +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 qA52arbg056653; Mon, 5 Nov 2012 02:36:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA52ar0r056649; Mon, 5 Nov 2012 02:36:53 GMT (envelope-from linimon) Date: Mon, 5 Nov 2012 02:36:53 GMT Message-Id: <201211050236.qA52ar0r056649@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/173363: [zfs] [panic] Panic on 'zpool replace' on readonly pool X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 02:36:54 -0000 Old Synopsis: Panic on 'zpool replace' on readonly pool New Synopsis: [zfs] [panic] Panic on 'zpool replace' on readonly pool Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Nov 5 02:36:30 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=173363 From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 02:37:27 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 8EFEECE0; Mon, 5 Nov 2012 02:37:27 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 5D6F38FC0C; Mon, 5 Nov 2012 02:37:27 +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 qA52bRsN056707; Mon, 5 Nov 2012 02:37:27 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA52bRwT056703; Mon, 5 Nov 2012 02:37:27 GMT (envelope-from linimon) Date: Mon, 5 Nov 2012 02:37:27 GMT Message-Id: <201211050237.qA52bRwT056703@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/173234: [zfs] [patch] Allow filtering of properties on zfs receive (patch included) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 02:37:27 -0000 Old Synopsis: Allow filtering of properties on zfs receive (patch included) New Synopsis: [zfs] [patch] Allow filtering of properties on zfs receive (patch included) Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Nov 5 02:37:03 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=173234 From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 11:06:33 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 55FBCCE2 for ; Mon, 5 Nov 2012 11:06:33 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 393FD8FC19 for ; Mon, 5 Nov 2012 11:06:33 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qA5B6Xcx001140 for ; Mon, 5 Nov 2012 11:06:33 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA5B6Whj001138 for freebsd-fs@FreeBSD.org; Mon, 5 Nov 2012 11:06:32 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Nov 2012 11:06:32 GMT Message-Id: <201211051106.qA5B6Whj001138@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 Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 11:06:33 -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/173363 fs [zfs] [panic] Panic on 'zpool replace' on readonly poo o kern/173254 fs [zfs] [patch] Upgrade requests used in ZFS trim map ba o kern/173234 fs [zfs] [patch] Allow filtering of properties on zfs rec o kern/173136 fs [unionfs] mounting above the NFS read-only share panic o kern/172348 fs [unionfs] umount -f of filesystem in use with readonly o kern/172334 fs [unionfs] unionfs permits recursive union mounts; caus o kern/172259 fs [zfs] [patch] ZFS fails to receive valid snapshots (pa o kern/171626 fs [tmpfs] tmpfs should be noisier when the requested siz o kern/171415 fs [zfs] zfs recv fails with "cannot receive incremental o kern/170945 fs [gpt] disk layout not portable between direct connect o kern/170914 fs [zfs] [patch] Import patchs related with issues 3090 a o kern/170912 fs [zfs] [patch] unnecessarily setting DS_FLAG_INCONSISTE o bin/170778 fs [zfs] [panic] FreeBSD panics randomly o kern/170680 fs [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEA o kern/170497 fs [xfs][panic] kernel will panic whenever I ls a mounted o kern/170238 fs [zfs] [panic] Panic when deleting data o kern/169945 fs [zfs] [panic] Kernel panic while importing zpool (afte o kern/169480 fs [zfs] ZFS stalls on heavy I/O o kern/169398 fs [zfs] Can't remove file with permanent error o kern/169339 fs panic while " : > /etc/123" o kern/169319 fs [zfs] zfs resilver can't complete o kern/168947 fs [nfs] [zfs] .zfs/snapshot directory is messed up when o kern/168942 fs [nfs] [hang] nfsd hangs after being restarted (not -HU o kern/168158 fs [zfs] incorrect parsing of sharenfs options in zfs (fs o kern/167979 fs [ufs] DIOCGDINFO ioctl does not work on 8.2 file syste o kern/167977 fs [smbfs] mount_smbfs results are differ when utf-8 or U o kern/167688 fs [fusefs] Incorrect signal handling with direct_io o kern/167685 fs [zfs] ZFS on USB drive prevents shutdown / reboot o kern/167612 fs [portalfs] The portal file system gets stuck inside po o kern/167272 fs [zfs] ZFS Disks reordering causes ZFS to pick the wron o kern/167260 fs [msdosfs] msdosfs disk was mounted the second time whe o kern/167109 fs [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene 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/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/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo p 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/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/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 bin/153142 fs [zfs] ls -l outputs `ls: ./.zfs: Operation not support 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 " p 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 conf/144213 fs [rc.d] [patch] Disappearing zvols on reboot 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/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/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 298 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 13:40:53 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 10BF79C1 for ; Mon, 5 Nov 2012 13:40:53 +0000 (UTC) (envelope-from fluca1978@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id B1A6C8FC0A for ; Mon, 5 Nov 2012 13:40:52 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so7655880vba.13 for ; Mon, 05 Nov 2012 05:40:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Wznlw0koCOciiGRyRZy4en2cBWuP8Timy/end6kQUpo=; b=CsqUaAWek47xi1sgZQO47fSTzYEw7e78Wv2NdPgTXcLvjtB6j4wFSvmoMPXadseLj2 Ib9a9faEkPwY4x17OyNVm+XewhetxYgFyAxhv87OuiHhoryt9NbZteOfyenmeefsB248 XW1H3U5FpXBcQ8NRRVBb7CXXN7FOo2T74gE8eGgAy0CQ8ZiCZIHPb0O5vc718pHTq7zP LRuP90JKZXq9/v1BVlE34Mlj+l69qF5t31RP/3dqgN26sx3kHVfUCYPdmQGBI5P1XZW/ x+DdMc5AAyjMt1SuVH+7CNUGi0x45RxN1l3mfv89trOThVBcLCvk+e3SQerMQghxMKkm CYPQ== MIME-Version: 1.0 Received: by 10.52.77.101 with SMTP id r5mr8220358vdw.25.1352122851862; Mon, 05 Nov 2012 05:40:51 -0800 (PST) Sender: fluca1978@gmail.com Received: by 10.220.2.135 with HTTP; Mon, 5 Nov 2012 05:40:51 -0800 (PST) In-Reply-To: References: Date: Mon, 5 Nov 2012 14:40:51 +0100 X-Google-Sender-Auth: 2c7MxSJNU19XtVmubNvu9f-5Mw4 Message-ID: Subject: Fwd: vop setattr and secure levels From: Luca Ferrari To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 13:40:53 -0000 Ops...I just realized I have not pushed the message to the list. Sorry. ---------- Forwarded message ---------- From: Luca Ferrari Date: Tue, Oct 30, 2012 at 7:58 AM Subject: Re: vop setattr and secure levels To: Ryan Stone Thanks Ryan, therefore is it correct that pretty mich any file system operation generates a VOP_SETATTR call and that such call will check against the secure levels? Luca > The kernel build process generates some .c and .h files which define > VOP_SETATTR, VOP_SETATTR_AP and VOP_SETATTR_APV, which are called from > various places in the kernel. These functions are what end up calling > vop_setattr. From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 16:58:56 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 99CDAC5F for ; Mon, 5 Nov 2012 16:58:56 +0000 (UTC) (envelope-from fox@cyberfoxfire.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3DA9C8FC0A for ; Mon, 5 Nov 2012 16:58:55 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id wc20so7407356obb.13 for ; Mon, 05 Nov 2012 08:58:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=RJ8bD77oPEjsssbyxpA1Rj9tH4dKpq/dUpcTTPAzHgg=; b=pSXWO3IWXTDn2OwSyapwofpf+jkRQpclInRSkxJur24V1lo9DIaP/uU0UEbNhe2+zQ XfhdedEX3IgHV/Q9ERJTLf+qC3bts9E1gZBKWetnCwa4zPA21KaTiC01napMYmmh5lN8 BNYUIYHwXI+DJ54rFfKajQEu+KaloZfZB+QSBn9PAqpk1wnzebmiMTWq2QzDk968tkUz oenJ5wdh333mC8VuNGrt/80EmifsPDaGcbVY1O/RjGJBSKIZ7NcPWFGbgxgeLofCQyb1 blSMjWNcd9TpdWZG/kiDLHoXHhEo3nmZX3UqyAjbheqi1paZg6rxnea0WDCj+GQgqSs4 ekew== Received: by 10.60.32.241 with SMTP id m17mr8455640oei.50.1352134735157; Mon, 05 Nov 2012 08:58:55 -0800 (PST) Received: from [10.99.99.9] ([67.11.63.242]) by mx.google.com with ESMTPS id j19sm14181689oei.2.2012.11.05.08.58.53 (version=SSLv3 cipher=OTHER); Mon, 05 Nov 2012 08:58:54 -0800 (PST) Message-ID: <5097F04A.5060701@cyberfoxfire.com> Date: Mon, 05 Nov 2012 10:58:50 -0600 From: Fox F User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Freddie Cash Subject: Re: Convert standalone zpool to RAID1 with data in place References: <50955FB1.2070800@cyberfoxfire.com> In-Reply-To: X-Gm-Message-State: ALoCoQkj68eT3WSvvgZmzThSdZbiy/UOPIyFQyxFCF09eZi8RZncnjQ7b8QF5x6A0t0AOKlthHof Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 16:58:56 -0000 On 11/3/2012 10:23 PM, Freddie Cash wrote: > > You don't. At least, not in that order. Or, at least not with the > ZFS-native tools. > > You can create a pool with 2 separate single-disk vdevs, and data will > be striped across them. Similar to RAID0, there will be no redundancy > to the pool. > zpool create poolname disk1 disk2 > > Later, you can convert the single-disk vdevs to mirrors, thus turning > the pool into a RAID10: > zpool attach poolname disk1 disk3 > zpool attach poolname disk2 disk4 > > Or, you can create a pool with a single mirror vdev: > zpool create poolname mirror disk1 disk2 > > Later, you can add another mirror vdev to the pool, and data will be > striped across the two vdevs, similar to a RAID10: > zpool add poolname mirror disk3 disk4 > > If you are truly hell bent on doing things in the other order (mirror > on top of two stripesets), then you have to use gstripe(8) to create > the stripesets, and then add those to the pool. The following is from > memory, so it may not be perfectly correct: > gstripe label stripe1 disk1 disk2 > gstripe label stripe2 disk3 disk4 > zpool create poolname mirror stripe/stripe1 stripe/stripe2 > > On Nov 3, 2012 11:17 AM, "Fox F" > wrote: > > > > Hello, > > > > My intention is to have a zpool with two drives (1TB and 2TB) > striped. I suppose I'd create it as such: > > > > zpool create zp_test disk1 disk2 > > > > I would then create a zfs filesystem on that zpool and add data to it. > > > > Then, I would want to mirror this data on another identical striped > vdev. > > > > The question is, what is the order of operations for creating the > second striped vdev and adding it as a mirror to the first one, and > how do I do that in such a way that the data on disk1/2 gets mirrored > to the new addition? > > > > I hope I am making sense. > > > > -F > > _______________________________________________ > > 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 > " > Thank you. It sounds like I need to use gstripe then. My need is to have two 3TB mirrors, for which I need a striped device of 1TB + 2TB given my current hardware. Thanks for the help. BTW, your memory seems to have served you well. I recommend anyone needing this advice check the man page for gstripe, though... it's pretty readable. From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 17:38: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 B51D9467 for ; Mon, 5 Nov 2012 17:38:13 +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 38D418FC0C for ; Mon, 5 Nov 2012 17:38:12 +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 qA5HBbxl039298 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 5 Nov 2012 19:11:38 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <5097F349.3080407@digsys.bg> Date: Mon, 05 Nov 2012 19:11:37 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.10) Gecko/20121029 Thunderbird/10.0.10 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Re: Convert standalone zpool to RAID1 with data in place References: <50955FB1.2070800@cyberfoxfire.com> <5097F04A.5060701@cyberfoxfire.com> In-Reply-To: <5097F04A.5060701@cyberfoxfire.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 17:38:13 -0000 On 05.11.12 18:58, Fox F wrote: > > Thank you. It sounds like I need to use gstripe then. My need is to > have two 3TB mirrors, for which I need a striped device of 1TB + 2TB > given my current hardware. Thanks for the help. > It seems this is only sensible if you have now one 1TB and one 2TB drive and look at mirroring them to another 3TB drive. My worry with using gstripe would be the order in which metadata is tasted and whether you might not end up in the unfortunately situation where for some reason ZFS tastes the drives first... Of course, with the classing conversion of single disk vdevs to mirrors, you need same size drives, or you could mirror your existing 1TB and 2TB drives with two 2TB or two 3TB drives. You will not use all the capacity initially, but then later if you replace, say the 1TB drive with a larger one, the zpool will expand. Daniel From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 17:46:52 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 1490E796 for ; Mon, 5 Nov 2012 17:46:52 +0000 (UTC) (envelope-from fox@cyberfoxfire.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id BBAF58FC12 for ; Mon, 5 Nov 2012 17:46:51 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so7580204oag.13 for ; Mon, 05 Nov 2012 09:46:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=0n7LcaHvZUeQL5+UbnP1sly6tRoMXPVLn04dArK9VnY=; b=Qiomo6j2UCZrywSitCwOSaDM9/O0JDtaJoCjDewfVkz8LUDUVNVuG03GAlcvik9oGb vw26g8OuVdQohbb6/jZ73YkwnrbSHoIcNsB+xA0jYNxMd2IA945voDIj0f80gRQZFhN6 FxiplONaNeGCV5szLPlM7v+q4vax3t94Tn7i8s5V7pyO2nXeRSaxhQzdErTJfry91d2g b1arJFQAXRkFbL4fKehMEgbB0sAtO2/NQaZld/hy1VDXL82JzAHx2oKYzEnEMmp/QFHc 6zdlfW3t0rSyQeSI+J/FScsvVQnefYL37Q33izByerLkbHvtnuCwFprIQ+zcKIRWBNRP EF3Q== Received: by 10.182.145.35 with SMTP id sr3mr8309238obb.98.1352137611084; Mon, 05 Nov 2012 09:46:51 -0800 (PST) Received: from [10.99.99.9] ([67.11.63.242]) by mx.google.com with ESMTPS id a7sm18274759obw.6.2012.11.05.09.46.49 (version=SSLv3 cipher=OTHER); Mon, 05 Nov 2012 09:46:50 -0800 (PST) Message-ID: <5097FB86.9050008@cyberfoxfire.com> Date: Mon, 05 Nov 2012 11:46:46 -0600 From: Fox F User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Freddie Cash Subject: Re: Convert standalone zpool to RAID1 with data in place References: <50955FB1.2070800@cyberfoxfire.com> In-Reply-To: X-Gm-Message-State: ALoCoQkzkO5dLA4OoI8YpnotKAw+mn7gTrWeXUllFqnioqs16PlZgNACQMvDRB8i0Q3KdPNzAUw4 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 17:46:52 -0000 On 11/3/2012 10:23 PM, Freddie Cash wrote: > > You don't. At least, not in that order. Or, at least not with the > ZFS-native tools. > > You can create a pool with 2 separate single-disk vdevs, and data will > be striped across them. Similar to RAID0, there will be no redundancy > to the pool. > zpool create poolname disk1 disk2 > > Later, you can convert the single-disk vdevs to mirrors, thus turning > the pool into a RAID10: > zpool attach poolname disk1 disk3 > zpool attach poolname disk2 disk4 > > Or, you can create a pool with a single mirror vdev: > zpool create poolname mirror disk1 disk2 > > Later, you can add another mirror vdev to the pool, and data will be > striped across the two vdevs, similar to a RAID10: > zpool add poolname mirror disk3 disk4 > > If you are truly hell bent on doing things in the other order (mirror > on top of two stripesets), then you have to use gstripe(8) to create > the stripesets, and then add those to the pool. The following is from > memory, so it may not be perfectly correct: > gstripe label stripe1 disk1 disk2 > gstripe label stripe2 disk3 disk4 > zpool create poolname mirror stripe/stripe1 stripe/stripe2 > > On Nov 3, 2012 11:17 AM, "Fox F" > wrote: > > > > Hello, > > > > My intention is to have a zpool with two drives (1TB and 2TB) > striped. I suppose I'd create it as such: > > > > zpool create zp_test disk1 disk2 > > > > I would then create a zfs filesystem on that zpool and add data to it. > > > > Then, I would want to mirror this data on another identical striped > vdev. > > > > The question is, what is the order of operations for creating the > second striped vdev and adding it as a mirror to the first one, and > how do I do that in such a way that the data on disk1/2 gets mirrored > to the new addition? > > > > I hope I am making sense. > > > > -F > > _______________________________________________ > > 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 did forget one point to have clarified. Forget the striping. Let's just assume two disks, 1 and 2. I only have disk1 on hand. So I create a zpool/zfs with it. # zpool create mypool disk1 # zfs create mypool/repository Then some data is put on the zfs. Now, I want to convert mypool to a mirror with disk2, while keeping the data on disk1 intact. Is there a way to do that? From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 17:53: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 32582BAD for ; Mon, 5 Nov 2012 17:53:13 +0000 (UTC) (envelope-from prvs=1656497edf=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id B50578FC17 for ; Mon, 5 Nov 2012 17:53:12 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50000961333.msg for ; Mon, 05 Nov 2012 17:53:11 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Mon, 05 Nov 2012 17:53:11 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1656497edf=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Fox F" , "Freddie Cash" References: <50955FB1.2070800@cyberfoxfire.com> <5097FB86.9050008@cyberfoxfire.com> Subject: Re: Convert standalone zpool to RAID1 with data in place Date: Mon, 5 Nov 2012 17:53:07 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 17:53:13 -0000 ----- Original Message ----- From: "Fox F" > I did forget one point to have clarified. > > Forget the striping. Let's just assume two disks, 1 and 2. > > I only have disk1 on hand. So I create a zpool/zfs with it. > > # zpool create mypool disk1 > # zfs create mypool/repository > > Then some data is put on the zfs. Now, I want to convert mypool to a > mirror with disk2, while keeping the data on disk1 intact. Is there a > way to do that? Yes off hand you want "zpool attach mypool disk1 disk2" more details in "man zpool" Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Mon Nov 5 18:28:47 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 9723BAFA for ; Mon, 5 Nov 2012 18:28:47 +0000 (UTC) (envelope-from fox@cyberfoxfire.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4EAA88FC12 for ; Mon, 5 Nov 2012 18:28:46 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so7641533oag.13 for ; Mon, 05 Nov 2012 10:28:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=WsffhnYqPAXnChH4MCDzGR4qp0PCsbMsD8j7RPYGhcE=; b=XAszzl6pHp83w52ZdZia0uYuY+sGRNg316Jguks3GztSTO/MKGprStkZPWdJnF0ltN Y0Fltlq7I1J4seaNy3wjnGE127aK6iAqQEstdBlXIwMGRWLCM4acyaJ0tmTSVXJ4LMcn 0PussTSq7S0p/nniEp7Cma+ghp5RCeGu3ly7JmzHNkrX5cCLdxPYoFYBxItxOpLNOquU GJlIJjByI9UnATj5lNSYvw0UIe4BCK7hq1+A8Va/hLNvrwkxRjAG7PpbG7JTELT2zE7t yA1oduME4PASAMYJiG1WfKFIvAVVBpM+Fo1SE8Q3s+GJY2RkNc0Xy4hyI7CH1ULzgUM8 XjZg== Received: by 10.182.131.37 with SMTP id oj5mr8414871obb.54.1352140126216; Mon, 05 Nov 2012 10:28:46 -0800 (PST) Received: from [10.99.99.9] ([67.11.63.242]) by mx.google.com with ESMTPS id zn9sm18351099obb.23.2012.11.05.10.28.44 (version=SSLv3 cipher=OTHER); Mon, 05 Nov 2012 10:28:45 -0800 (PST) Message-ID: <50980559.3050306@cyberfoxfire.com> Date: Mon, 05 Nov 2012 12:28:41 -0600 From: Fox F User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Steven Hartland Subject: Re: Convert standalone zpool to RAID1 with data in place References: <50955FB1.2070800@cyberfoxfire.com> <5097FB86.9050008@cyberfoxfire.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlq62FWLQR1DZb/DD6R7xKXj2h2O5ctz0u0BaUpmhHpKH5dgnhUtrPxZS4fFicozQ8o24b1 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 18:28:47 -0000 On 11/5/2012 11:53 AM, Steven Hartland wrote: > ----- Original Message ----- From: "Fox F" > >> I did forget one point to have clarified. >> >> Forget the striping. Let's just assume two disks, 1 and 2. >> >> I only have disk1 on hand. So I create a zpool/zfs with it. >> >> # zpool create mypool disk1 >> # zfs create mypool/repository >> >> Then some data is put on the zfs. Now, I want to convert mypool to a >> mirror with disk2, while keeping the data on disk1 intact. Is there a >> way to do that? > > Yes off hand you want "zpool attach mypool disk1 disk2" more details in > "man zpool" > > Regards > Steve > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. > and the person or entity to whom it is addressed. In the event of > misdirection, the recipient is prohibited from using, copying, > printing or otherwise disseminating it or any information contained in > it. > In the event of misdirection, illegible or incomplete transmission > please telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > Alright, I think I got it! "zpool attach" adds a new device to an existing one as a mirror, whereas "zpool add" adds it as a stripe. For example, # zpool create mypool disk1 I now have a single vdev pool. # zpool add mypool disk2 I now have a striped two-disk pool. # zpool attach mypool disk1 disk3 Now, I have the following: mypool mirror-0 disk1 disk3 disk2 FINALLY, if I want to add disk4, I would say, # zpool attach mypool disk2 disk4 which would give mypool mirror-0 disk1 disk3 mirror-1 disk2 disk4 Which would give me what I need. So to Freddie, this is exactly what you recommended, and fortunately will work for my circumstances. I guess what confused me was how attach vs. add work, and the resulting disk layout. Now, after some testing on my server, I see how it all works. Thanks for the education. From owner-freebsd-fs@FreeBSD.ORG Tue Nov 6 10:10:50 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8336DFD for ; Tue, 6 Nov 2012 10:10:50 +0000 (UTC) (envelope-from rija@stratoserver.net) Received: from h2075222.stratoserver.net (h2075222.stratoserver.net [81.169.154.59]) by mx1.freebsd.org (Postfix) with ESMTP id CF23E8FC08 for ; Tue, 6 Nov 2012 10:10:49 +0000 (UTC) Received: from h2075222.stratoserver.net (IOM-22-28 [81.169.154.59]) by h2075222.stratoserver.net (mailer) with SMTP id EWmUYBUiabA for ; Tue, 06 Nov 2012 11:10:49 +0100 Date: Tue, 06 Nov 2012 11:10:49 +0100 From: "Rachele" To: Subject: Re: Re: Proposta di legge. Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2012 10:10:50 -0000 Gentile utente, Ti e stata inviata un pagamento anticipato del 20% domanda di numero di fattura 25902872. http://muzicanouablue.net/Proposta_di_legge.zip?freebsd-fs@freebsd.org Si prega di confermare la ricezione del pagamento. Aspetto la tua risposta Cordiali saluti From owner-freebsd-fs@FreeBSD.ORG Wed Nov 7 09:16: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 8CFF1EAD for ; Wed, 7 Nov 2012 09:16:15 +0000 (UTC) (envelope-from petri@helenius.fi) Received: from mail.secroom.net (r083.secroom.net [193.19.137.83]) by mx1.freebsd.org (Postfix) with ESMTP id 3D2548FC0A for ; Wed, 7 Nov 2012 09:16:14 +0000 (UTC) Received: from mail.secroom.net (localhost [127.0.0.1]) by mail.secroom.net (Postfix) with ESMTP id 92C675C95 for ; Wed, 7 Nov 2012 09:16:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at example.com Received: from mail.secroom.net ([127.0.0.1]) by mail.secroom.net (mail.secroom.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ygg-sUYbpEw for ; Wed, 7 Nov 2012 09:16:10 +0000 (UTC) Received: from d149.dyn.helenius.fi (d149.dyn.helenius.fi [83.150.121.149]) (Authenticated sender: pete) by mail.secroom.net (Postfix) with ESMTPA id 04C495C23 for ; Wed, 7 Nov 2012 09:16:10 +0000 (UTC) From: Petri Helenius Subject: zvol node bug Message-Id: Date: Wed, 7 Nov 2012 11:16:10 +0200 To: "freebsd-fs@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 09:16:15 -0000 Hi, Any chance https://www.illumos.org/issues/3170 would be fixed in RELENG_9? Pete From owner-freebsd-fs@FreeBSD.ORG Wed Nov 7 10:52:02 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 67DBE5FB for ; Wed, 7 Nov 2012 10:52:02 +0000 (UTC) (envelope-from mickael.canevet@gmail.com) Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2B5308FC08 for ; Wed, 7 Nov 2012 10:52:01 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id k10so1315410iag.13 for ; Wed, 07 Nov 2012 02:52:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lBx9urRET6zB0750iW1BMciZex5LxqhC7+ESzFe2CW4=; b=KWRPBk38dwT1QZBYt7Wo5yx1LbsshmNQ+6mO3nI2t+7qPBdbfCYly7MSw7WyG0Z8HL Ziw/k6rqF79idr9MtpluXrS1jgMWzX9g48+88YVvtutZN9J0n1aIHR586IBioTOEPJrO +vyMwHHaQeIRwmEYoZQltaZmHMJSkfUxiqAiTvr/VcsCUYqDi81P8VOzVQWoSZqViMfH 7oK23T4Cn2CB4KYuxA83YHUqv9Deqvpz3wI/5QYlptFvvC6OrN2zZ4XFgNr+LrpAOs1s l/QhbqmnMKj282EPOux1hCkJL5LAsoRvLAWn4pAarwd6Oru5D3pYBrKxpnm26HgAD438 gv/A== MIME-Version: 1.0 Received: by 10.50.237.6 with SMTP id uy6mr1566588igc.31.1352285521480; Wed, 07 Nov 2012 02:52:01 -0800 (PST) Received: by 10.64.28.172 with HTTP; Wed, 7 Nov 2012 02:52:01 -0800 (PST) Date: Wed, 7 Nov 2012 11:52:01 +0100 Message-ID: Subject: NFS export with space in directory name From: =?UTF-8?B?TWlja2HDq2wgQ2Fuw6l2ZXQ=?= To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 10:52:02 -0000 Hello, I'm trying to export a ZFS volume that contains a space (which is allowed according to /usr/src/sys/cddl/contrib/opensolaris/common/zfs/zfs_namecheck.c, function valid_char() ), but I noticed that it was not exported (showmount -e). /etc/zfs/export creates an entry like this: /data/my directory with space -network 192.168.0.0/24 I tried to do it manually by escaping space character in /etc/exports: /data/my\ directory\ with\ space -network 192.168.0.0/24 or "/data/my directory with space" -network 192.168.0.0/24 (works on Debian) or '/data/my directory with space' -network 192.168.0.0/24 But it does not work ; /var/log/messages always reports "mountd: bad exports list line..." So I'd like to know if there is a way to export a directory with a space in its name on FreeBSD 9.0-RELEASE ? Thank you, Micka=C3=ABl From owner-freebsd-fs@FreeBSD.ORG Wed Nov 7 13:27:46 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 D4C9A1E0 for ; Wed, 7 Nov 2012 13:27:46 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id B43248FC08 for ; Wed, 7 Nov 2012 13:27:46 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TW5fW-0001bx-3D for freebsd-fs@freebsd.org; Wed, 07 Nov 2012 05:27:46 -0800 Date: Wed, 7 Nov 2012 05:27:46 -0800 (PST) From: Beeblebrox To: freebsd-fs@freebsd.org Message-ID: <1352294866076-5758864.post@n5.nabble.com> Subject: [ZFS] How to fix corrupt ZDB MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 13:27:46 -0000 I removed the HDD before deleting one of the zpools, then I added a ZIL device using gnop. Now I get multiple ashift values even though I have only 1 zpool (vdev): zdb mypool | grep ashift ashift: 9 ashift: 12 ashift: 9 ashift: 12 Looking through various ZDB functions has shown me that the previously removed pool is still in ZDB. But unfortunately the ZDB manual talks more about "status reporting" and not much about "error correction". Any ideas on how to correct/remove/delete faulty ZDB entries (other than re-install)? -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-How-to-fix-corrupt-ZDB-tp5758864.html Sent from the freebsd-fs mailing list archive at Nabble.com. From owner-freebsd-fs@FreeBSD.ORG Wed Nov 7 13:34: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 E7ED34C2 for ; Wed, 7 Nov 2012 13:34:22 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id C6EE98FC08 for ; Wed, 7 Nov 2012 13:34:22 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TW5lu-0001zY-7r for freebsd-fs@freebsd.org; Wed, 07 Nov 2012 05:34:22 -0800 Date: Wed, 7 Nov 2012 05:34:22 -0800 (PST) From: Beeblebrox To: freebsd-fs@freebsd.org Message-ID: <1352295262237-5758865.post@n5.nabble.com> In-Reply-To: References: Subject: Re: unionfs and NFS? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 13:34:23 -0000 I tried it with several jail setup scenarios. - it did not work, so I gave up on it. It's a nice concept, but as it states, it can be (and in my experience was) unrelaible. -- View this message in context: http://freebsd.1045724.n5.nabble.com/unionfs-and-NFS-tp5753281p5758865.html Sent from the freebsd-fs mailing list archive at Nabble.com. From owner-freebsd-fs@FreeBSD.ORG Wed Nov 7 13:49:10 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 3F888E3E for ; Wed, 7 Nov 2012 13:49:10 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B7AFE8FC1A for ; Wed, 7 Nov 2012 13:49:09 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jf20so829524bkc.13 for ; Wed, 07 Nov 2012 05:49:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=pXh9VLDXljlmp5EWuhJC7hnDvjU9HnXXR0gSNminA1U=; b=v4JAuwxcgk6LxDN1BD7tcNjE9+b7H4uEtla71A1wUOtdJf0sfiOehMAtTrKWNzNHem eEyQKJQVtAqPv0OanHh5Or7+UtSrzrj1YkGWl57vllzh/tNKGGWS8lf2jBMsv0MA3fKf pwXLgjKHjcNdw6W1RWbnm9/9Jb5IAIYf9SViX4+NuYnzxhWQ+rmHMLhLzITpinwqgh0R gm1HVO2WDUYA8KUek94zEWPfcBslIn36A9sD5GIU2rI1NE5ng/NIJE2Xslql+5GKoAPw N43OZZ2+dQT9R+YKMHzPCLzMySi3tnatH9kj2etOrxtqeLkwAvnzIzmqcMk5Ht9j6Azv TICw== Received: by 10.204.147.5 with SMTP id j5mr1180193bkv.21.1352296148803; Wed, 07 Nov 2012 05:49:08 -0800 (PST) Received: from [192.168.50.105] (double-l.xs4all.nl. [80.126.205.144]) by mx.google.com with ESMTPS id k21sm14513043bkv.1.2012.11.07.05.49.07 (version=SSLv3 cipher=OTHER); Wed, 07 Nov 2012 05:49:07 -0800 (PST) Message-ID: <509A66D2.5060706@gmail.com> Date: Wed, 07 Nov 2012 14:49:06 +0100 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Beeblebrox Subject: Re: [ZFS] How to fix corrupt ZDB References: <1352294866076-5758864.post@n5.nabble.com> In-Reply-To: <1352294866076-5758864.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 13:49:10 -0000 Beeblebrox schreef: > I removed the HDD before deleting one of the zpools, then I added a ZIL > device using gnop. Now I get multiple ashift values even though I have only > 1 zpool (vdev): > zdb mypool | grep ashift > ashift: 9 > ashift: 12 > ashift: 9 > ashift: 12 > > Looking through various ZDB functions has shown me that the previously > removed pool is still in ZDB. But unfortunately the ZDB manual talks more > about "status reporting" and not much about "error correction". > > Any ideas on how to correct/remove/delete faulty ZDB entries (other than > re-install)? > Can you show the output of zpool status. gr johan From owner-freebsd-fs@FreeBSD.ORG Wed Nov 7 14:31:12 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 69514A28 for ; Wed, 7 Nov 2012 14:31:12 +0000 (UTC) (envelope-from prvs=16580431d0=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id EC1CC8FC14 for ; Wed, 7 Nov 2012 14:31:11 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50000979458.msg for ; Wed, 07 Nov 2012 14:31:10 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 07 Nov 2012 14:31:10 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=16580431d0=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> From: "Steven Hartland" To: "Johan Hendriks" , "Beeblebrox" References: <1352294866076-5758864.post@n5.nabble.com> <509A66D2.5060706@gmail.com> Subject: Re: [ZFS] How to fix corrupt ZDB Date: Wed, 7 Nov 2012 14:31:12 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 14:31:12 -0000 The way that zdb finds things can be dodgy, so while everything else is working zdb can often fail. If your tank is working ok and all devices are online then try:- zpool reguid This will rewrite all labels to the vdevs using current settings. Regards Steve ----- Original Message ----- From: "Johan Hendriks" To: "Beeblebrox" Cc: Sent: Wednesday, November 07, 2012 1:49 PM Subject: Re: [ZFS] How to fix corrupt ZDB > Beeblebrox schreef: >> I removed the HDD before deleting one of the zpools, then I added a ZIL >> device using gnop. Now I get multiple ashift values even though I have only >> 1 zpool (vdev): >> zdb mypool | grep ashift >> ashift: 9 >> ashift: 12 >> ashift: 9 >> ashift: 12 >> >> Looking through various ZDB functions has shown me that the previously >> removed pool is still in ZDB. But unfortunately the ZDB manual talks more >> about "status reporting" and not much about "error correction". >> >> Any ideas on how to correct/remove/delete faulty ZDB entries (other than >> re-install)? >> > Can you show the output of zpool status. > > gr > johan > _______________________________________________ > 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" > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Wed Nov 7 15:06: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 7B358390 for ; Wed, 7 Nov 2012 15:06:32 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by mx1.freebsd.org (Postfix) with ESMTP id 286258FC0A for ; Wed, 7 Nov 2012 15:06:31 +0000 (UTC) X-AuditID: 12074425-b7fcc6d00000091f-8f-509a77c494c9 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 02.3D.02335.4C77A905; Wed, 7 Nov 2012 10:01:25 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id qA7F1O0d010392 for ; Wed, 7 Nov 2012 10:01:24 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qA7F1M42021103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 7 Nov 2012 10:01:24 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id qA7F1L3m023105; Wed, 7 Nov 2012 10:01:21 -0500 (EST) Date: Wed, 7 Nov 2012 10:01:21 -0500 (EST) From: Benjamin Kaduk To: freebsd-fs@freebsd.org Subject: will non-MPSAFE-deorbit remove MNTK_MPSAFE? Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHIsWRmVeSWpSXmKPExsUixG6nrnu0fFaAwar7zBbHHv9kc2D0mPFp PksAYxSXTUpqTmZZapG+XQJXxonlu9gKWpkqpv/fwtjAeJ6xi5GTQ0LAROLusxfsELaYxIV7 69lAbCGBfYwSrQ11XYxcQPYZRoknj2+wQThPmCR2XJrOCFFVLzHzRR+YzSKgJdH/4SFYN5uA isTMNxvBbBEBKYmZJ1+DbRAG2ta0ZB9YPa+Ag8TBqw/B4qICOhKr909hgYgLSpyc+QTMZhaw lPi39hfrBEa+WUhSs5CkFjAyrWKUTcmt0s1NzMwpTk3WLU5OzMtLLdK10MvNLNFLTSndxAgO JhfVHYwTDikdYhTgYFTi4W2InBkgxJpYVlyZe4hRkoNJSZR3b86sACG+pPyUyozE4oz4otKc 1OJDjBIczEoivCyFQDnelMTKqtSifJiUNAeLkjjvjZSb/kIC6YklqdmpqQWpRTBZGQ4OJQne ZWVAjYJFqempFWmZOSUIaSYOTpDhPEDDd4HU8BYXJOYWZ6ZD5E8xKkqJ8+4ASQiAJDJK8+B6 YdH+ilEc6BVh3pUgVTzARAHX/QpoMBPQ4OJrM0AGlyQipKQaGGdvqZhcs+v+44v+W/Vv2u7h 8vF51lfy6O3UL2mL7M9y80gHTVTg6J1W++iDd/U2o+/bIp93FoW+/rzEqCX/7hvpqB2T/jEW dqx5q+W60LlMfJnsRA31ltru1HDhBYc0GAXL30+et3ly4iu+81udEkRniUp0y+llrp90e8XU dxfTnVorVuxdslKJpTgj0VCLuag4EQB5In5S0QIAAA== X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 15:06:32 -0000 Per the thread on svn-src-head, I was wondering if there are plans to remove the MNTK_MPSAFE flag at some point. A quick grep through the sources seems to indicate that it is not really used, as the check in VFS_NEEDSGIANT was removed in r241896. -Ben From owner-freebsd-fs@FreeBSD.ORG Wed Nov 7 15:15:42 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 8699A626 for ; Wed, 7 Nov 2012 15:15:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id E28468FC0A for ; Wed, 7 Nov 2012 15:15:41 +0000 (UTC) Received: from tom.home (localhost [127.0.0.1]) by kib.kiev.ua (8.14.5/8.14.5) with ESMTP id qA7FFZHw065378; Wed, 7 Nov 2012 17:15:35 +0200 (EET) (envelope-from kostikbel@gmail.com) X-DKIM: OpenDKIM Filter v2.5.2 kib.kiev.ua qA7FFZHw065378 Received: (from kostik@localhost) by tom.home (8.14.5/8.14.5/Submit) id qA7FFY2R065377; Wed, 7 Nov 2012 17:15:34 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 7 Nov 2012 17:15:34 +0200 From: Konstantin Belousov To: Benjamin Kaduk Subject: Re: will non-MPSAFE-deorbit remove MNTK_MPSAFE? Message-ID: <20121107151534.GR73505@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i9pGKxSHTiGLjQSm" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=0.2 required=5.0 tests=ALL_TRUSTED, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 15:15:42 -0000 --i9pGKxSHTiGLjQSm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 07, 2012 at 10:01:21AM -0500, Benjamin Kaduk wrote: > Per the thread on svn-src-head, I was wondering if there are plans to=20 > remove the MNTK_MPSAFE flag at some point. > A quick grep through the sources seems to indicate that it is not really= =20 > used, as the check in VFS_NEEDSGIANT was removed in r241896. Yes, it will be removed some time before 10.0. Right now I opted to not change mpsafe filesystem modules. An option was to keep the code which refused to mount filesystem without MNTK_MPSAFE set, but I decided to cut the whole tail once. But I did not wanted to touch working mpsafe filesystems, thus MNTK_MPSAFE survived yet. --i9pGKxSHTiGLjQSm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCaexYACgkQC3+MBN1Mb4iXbQCgl/foIv1y4q6ilOt8TY632aOV lCEAnjU/Sah4fvQfGWxdgwFUp7HXtOpH =eSlz -----END PGP SIGNATURE----- --i9pGKxSHTiGLjQSm-- From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 00:10:11 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 7305CB0A for ; Thu, 8 Nov 2012 00:10:11 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 22E9C8FC12 for ; Thu, 8 Nov 2012 00:10:10 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EABT4mlCDaFvO/2dsb2JhbABEhhi+W4IeAQEBAwEBAQEgBCcgCwUWGAICDRkCKQEJJgYIBwQBHASHYwYLqXGTEYEgiweFGoETA4hainSCLYEcjyiDDYFGNQ X-IronPort-AV: E=Sophos;i="4.80,735,1344225600"; d="scan'208";a="187092344" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 07 Nov 2012 19:10:02 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 412D8B3F14; Wed, 7 Nov 2012 19:10:02 -0500 (EST) Date: Wed, 7 Nov 2012 19:10:02 -0500 (EST) From: Rick Macklem To: =?utf-8?Q?Micka=C3=ABl_Can=C3=A9vet?= Message-ID: <416641890.106495.1352333402239.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: NFS export with space in directory name MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 00:10:11 -0000 Mickael Canevet wrote: > Hello, >=20 > I'm trying to export a ZFS volume that contains a space (which is > allowed > according to > /usr/src/sys/cddl/contrib/opensolaris/common/zfs/zfs_namecheck.c, > function > valid_char() ), but I noticed that it was not exported (showmount -e). >=20 > /etc/zfs/export creates an entry like this: >=20 > /data/my directory with space -network 192.168.0.0/24 >=20 > I tried to do it manually by escaping space character in /etc/exports: >=20 > /data/my\ directory\ with\ space -network 192.168.0.0/24 >=20 > or >=20 > "/data/my directory with space" -network 192.168.0.0/24 (works on > Debian) >=20 > or >=20 > '/data/my directory with space' -network 192.168.0.0/24 >=20 > But it does not work ; /var/log/messages always reports "mountd: bad > exports list line..." >=20 > So I'd like to know if there is a way to export a directory with a > space in > its name on FreeBSD 9.0-RELEASE ? >=20 Running mountd-> Nope. I am not sure if nfse can support this? (It can be found on sourceforge.net and I've cc'd Andrey, since he'll know the answer.) rick > Thank you, > Micka=C3=ABl > _______________________________________________ > 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 Thu Nov 8 06:34:58 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 04A8DED4 for ; Thu, 8 Nov 2012 06:34:58 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id D35C08FC08 for ; Thu, 8 Nov 2012 06:34:57 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TWLhY-0004EO-QC for freebsd-fs@freebsd.org; Wed, 07 Nov 2012 22:34:56 -0800 Date: Wed, 7 Nov 2012 22:34:56 -0800 (PST) From: Beeblebrox To: freebsd-fs@freebsd.org Message-ID: <1352356496801-5759081.post@n5.nabble.com> In-Reply-To: <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> References: <1352294866076-5758864.post@n5.nabble.com> <509A66D2.5060706@gmail.com> <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> Subject: Re: [ZFS] How to fix corrupt ZDB MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 06:34:58 -0000 Hi everyone, thanks for the help / suggestions. Starting with Steve's suggestion: *# zpool reguid bsdr* Did not change the original ashift output for ZDB but resulted in all labels being erased: *# zdb -l ** -------------------------------------------- LABEL 0 -------------------------------------------- failed to read label 0 -------------------------------------------- LABEL 1 -------------------------------------------- failed to read label 1 -------------------------------------------- LABEL 2 -------------------------------------------- failed to read label 2 -------------------------------------------- LABEL 3 -------------------------------------------- failed to read label 3 (I suppose ZDB has multiple labels because I had re-created the root pool bsdr several times in the past year on the same HDD). This command also did not change the corrupt entry for an old pool: *# zdb -c ** zdb: can't open 'asp': No such file or directory Finally, *# zpool status* pool: bsdr state: ONLINE scan: scrub repaired 0 in 0h25m with 0 errors config: NAME STATE READ WRITE CKSUM bsdr ONLINE 0 0 0 ada0 ONLINE 0 0 0 logs ada1p9 ONLINE 0 0 0 errors: No known data errors -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-How-to-fix-corrupt-ZDB-tp5758864p5759081.html Sent from the freebsd-fs mailing list archive at Nabble.com. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 10:03:00 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 B8579432 for ; Thu, 8 Nov 2012 10:03:00 +0000 (UTC) (envelope-from kiwi@oav.net) Received: from mail02.oav.net (mail02.oav.net [IPv6:2001:67c:ec:100::25:2]) by mx1.freebsd.org (Postfix) with ESMTP id 3D43A8FC16 for ; Thu, 8 Nov 2012 10:03:00 +0000 (UTC) Received: from amavis1.local.oav.net (amavis1.local.oav.net [IPv6:2001:67c:ec:100::25:41]) by mail02.oav.net (Postfix) with ESMTP id 440FD61C3F for ; Thu, 8 Nov 2012 11:02:52 +0100 (CET) (envelope-from kiwi@oav.net) X-Virus-Scanned: Amavisd-new at amavis1.local.oav.net.local.oav.net Received: from mail02.oav.net ([172.31.1.2]) by amavis1.local.oav.net (amavis1.local.oav.net [172.31.1.41]) (amavisd-new, port 10026) with LMTP id U1wteWdl0aJT for ; Thu, 8 Nov 2012 11:02:45 +0100 (CET) Received: from nat-out.openvisp.net (nat-out.openvisp.net [193.218.105.29]) (Authenticated sender: kiwi@oav.net) by mail02.oav.net (Postfix) with ESMTPA id A77CC61C3E for ; Thu, 8 Nov 2012 11:02:45 +0100 (CET) (envelope-from kiwi@oav.net) Received: from [2001:67c:2219:7::86:62] by webmail.openvisp.net with HTTP (HTTP/1.1 POST); Thu, 08 Nov 2012 11:02:45 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 08 Nov 2012 11:02:45 +0100 From: Xavier Beaudouin To: Subject: 9.0-RELEASE-p4 + NFS + ZFS =?UTF-8?Q?=3D=20issues=2E=2E=2E=20=3A/?= =?UTF-8?Q?=20=28probably=20a=20memory=20leak=29?= Organization: Association Kazar - http://kazar.net/ Message-ID: <7791bd21138de89e5c47cca5513d0757@oav.net> X-Sender: kiwi@oav.net User-Agent: RoundCube Webmail/0.8.2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 10:03:00 -0000 Hello there, I try to make a FreeBSD ZFS NFS server with the following configuration : - Supermicro X7DB8 - 2 L5420 - 12G RAM - 8 x 300G SCSI drives using the 2 U320 scsi channel. - lagg (LACP) of 2 e1000 - zpool : # zpool status pool: vol state: ONLINE scan: scrub repaired 0 in 2h11m with 0 errors on Thu Nov 1 07:42:05 2012 config: NAME STATE READ WRITE CKSUM vol ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da0 ONLINE 0 0 0 da4 ONLINE 0 0 0 raidz1-1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da5 ONLINE 0 0 0 raidz1-2 ONLINE 0 0 0 da2 ONLINE 0 0 0 da6 ONLINE 0 0 0 raidz1-3 ONLINE 0 0 0 da3 ONLINE 0 0 0 da7 ONLINE 0 0 0 I have tried this patch : http://people.freebsd.org/~namei-leak.patch And issue still here. Also tried to move from newnfs to oldnfs server and client, same issue. Issue is comming when copying from a netapp to this machine a 70G data with bunch of big files (eg 600M ~ 8G) and web files. All NFS clients use NFSv3 and UDP. Tried : nfs client netapp and freebsd on the same machine : 1srt rsync from netapp to freebsd ok : no issue, second rsync : memory leak, swap is used (about less than 100Mb, but this trigger the bug. nfs client of the netapp is the "filer" machine, and the destination is local zfs spool. The rsync to make up to date data trigger as well the issue. /boot/loader.conf zfs_load="YES" if_lagg_load="YES" autoboot_delay="10" # Delay in seconds before autobooting, start # http://icesquare.com/wordpress/how-to-improve-zfs-performance/ #I have 8G of Ram #vfs.zfs.prefetch_disable=0 #If Ram = 4GB, set the value to 512M #If Ram = 8GB, set the value to 1024M #vfs.zfs.arc_min="1024M" #Ram x 0.5 - 512 MB #vfs.zfs.arc_max="3584M" #Ram x 2 vm.kmem_size_max="24G" #Ram x 1.5 #vm.kmem_size="12G" /etc/sysctl.conf # $FreeBSD: release/9.0.0/etc/sysctl.conf 112200 2003-03-13 18:43:50Z mux $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # # Uncomment this to prevent users from seeing information about processes that # are being run under another UID. #security.bsd.see_other_uids=0 kern.maxfiles=64000 vfs.nfsd.maxthreads=16 vfs.zfs.prefetch_disable=1 The latter (vfs.zfs.prefetch_disable=1) make the bug a bit strange. Inactive memory keeps growing, but active and free is still very low during the copy. Then machine use all of his memory, and NFS server not responsive. /etc/rc.conf hostname="filernew" keymap="fr.iso.acc.kbd" cloned_interfaces="lagg0" ifconfig_em0="up" ifconfig_em1="up" ifconfig_lagg0="inet 172.31.x.x netmask 255.255.0.0 laggproto lacp laggport em0 laggport em1" defaultrouter="172.31.x.x" sshd_enable="YES" ntpd_enable="YES" powerd_enable="YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="NO" zfs_enable="YES" puppet_enable="YES" # NFS rpcbind_enable="YES" nfs_server_enable="YES" nfs_server_flags="-u -t -n 4" mountd_flags="-r" mountd_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" # Added by Puppet bsnmpd_enable="YES" Kind regards... Xavier -- Xavier Beaudouin From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 10:26:57 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 560EC1FF for ; Thu, 8 Nov 2012 10:26:57 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 31B108FC0C for ; Thu, 8 Nov 2012 10:26:56 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TWPK3-0004Dp-OS for freebsd-fs@freebsd.org; Thu, 08 Nov 2012 02:26:55 -0800 Date: Thu, 8 Nov 2012 02:26:55 -0800 (PST) From: Beeblebrox To: freebsd-fs@freebsd.org Message-ID: <1352370415751-5759123.post@n5.nabble.com> In-Reply-To: <1352356496801-5759081.post@n5.nabble.com> References: <1352294866076-5758864.post@n5.nabble.com> <509A66D2.5060706@gmail.com> <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> <1352356496801-5759081.post@n5.nabble.com> Subject: Re: [ZFS] How to fix corrupt ZDB MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 10:26:57 -0000 *** correction on previous post *** Beeblebrox wrote > This command also did not change the corrupt entry for an old pool: * > # zdb -c * * > zdb: can't open 'asp': No such file or directory It turns out, ZDB just looks in the first folder / file name it runs into when running this command. So change to a different folder, run the command and the error message changes to complain about a different folder. I was running that command at the top-level and I have a folder named "asp" there as well. So disregard that bit... -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-How-to-fix-corrupt-ZDB-tp5758864p5759123.html Sent from the freebsd-fs mailing list archive at Nabble.com. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 12:54:11 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 EC575BA4 for ; Thu, 8 Nov 2012 12:54:11 +0000 (UTC) (envelope-from prvs=1659aa6059=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 7CFCB8FC0C for ; Thu, 8 Nov 2012 12:54:10 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50000989437.msg for ; Thu, 08 Nov 2012 12:54:08 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 08 Nov 2012 12:54:08 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1659aa6059=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Beeblebrox" , References: <1352294866076-5758864.post@n5.nabble.com> <509A66D2.5060706@gmail.com> <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> <1352356496801-5759081.post@n5.nabble.com> Subject: Re: [ZFS] How to fix corrupt ZDB Date: Thu, 8 Nov 2012 12:54:10 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 12:54:12 -0000 ----- Original Message ----- From: "Beeblebrox" To: Sent: Thursday, November 08, 2012 6:34 AM Subject: Re: [ZFS] How to fix corrupt ZDB > Hi everyone, thanks for the help / suggestions. Starting with Steve's > suggestion: > > *# zpool reguid bsdr* > Did not change the original ashift output for ZDB but resulted in all labels > being erased: Hmmm if the labels we're really not there pool wouldn't be working, so how / where its looking sounds like it may be wrong. What do you get from the following commands zdb zdb -C zdb -l /dev/ada0 zdb -l /dev/ada1p9 Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 13:56:40 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 DCB382A2 for ; Thu, 8 Nov 2012 13:56:40 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 8C7878FC16 for ; Thu, 8 Nov 2012 13:56:40 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAG+5m1CDaFvO/2dsb2JhbABEFoYCvlqCHgEBAQMBAQEBICsgCwUWDgoCAg0ZAikBCSYGCAcEARwEh2MGC6kYkw6BIIpyGgaFFIETA4hainSCLYEcjyeDDYE+CBce X-IronPort-AV: E=Sophos;i="4.80,738,1344225600"; d="scan'208";a="187155294" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 08 Nov 2012 08:56:38 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id A8131B3EEF; Thu, 8 Nov 2012 08:56:38 -0500 (EST) Date: Thu, 8 Nov 2012 08:56:38 -0500 (EST) From: Rick Macklem To: Xavier Beaudouin Message-ID: <1066915051.120042.1352382998672.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <7791bd21138de89e5c47cca5513d0757@oav.net> Subject: Re: 9.0-RELEASE-p4 + NFS + ZFS = issues... :/ (probably a memory leak) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 13:56:40 -0000 Xavier Beaudouin wrote: > Hello there, > > I try to make a FreeBSD ZFS NFS server with the following > configuration > : > > - Supermicro X7DB8 > - 2 L5420 > - 12G RAM > - 8 x 300G SCSI drives using the 2 U320 scsi channel. > - lagg (LACP) of 2 e1000 > - zpool : > > # zpool status > pool: vol > state: ONLINE > scan: scrub repaired 0 in 2h11m with 0 errors on Thu Nov 1 07:42:05 > 2012 > config: > > NAME STATE READ WRITE CKSUM > vol ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > da0 ONLINE 0 0 0 > da4 ONLINE 0 0 0 > raidz1-1 ONLINE 0 0 0 > da1 ONLINE 0 0 0 > da5 ONLINE 0 0 0 > raidz1-2 ONLINE 0 0 0 > da2 ONLINE 0 0 0 > da6 ONLINE 0 0 0 > raidz1-3 ONLINE 0 0 0 > da3 ONLINE 0 0 0 > da7 ONLINE 0 0 0 > > > I have tried this patch : http://people.freebsd.org/~namei-leak.patch > > And issue still here. > > Also tried to move from newnfs to oldnfs server and client, same > issue. > > Issue is comming when copying from a netapp to this machine a 70G data > with bunch of big files (eg 600M ~ 8G) and web files. > > All NFS clients use NFSv3 and UDP. > There is this patch for NFSv3 over UDP: http://people.freebsd.org/~rmacklem/udp-timer.patch (It applies to both NFS clients, since it is krpc related.) I can't remember what the implications of not having this patch is, but if the client retries NFS RPCs too agressively, it could use a lot of DRC storage (mbuf clusters mainly) in the NFS server (if the NFS server is a FreeBSD box). OR Try the mounts using TCP and see if the problem goes away. If it is slow leak, doing "vmstat -z" and "vmstat -m" while the system is getting constipated might show what is leaking. > Tried : > > nfs client netapp and freebsd on the same machine : 1srt rsync from > netapp to freebsd ok : no issue, second rsync : memory leak, swap is > used (about less than 100Mb, but this trigger the bug. > > nfs client of the netapp is the "filer" machine, and the destination > is > local zfs spool. The rsync to make up to date data trigger as well the > issue. > I'll admit you lost me w.r.t. what is the NFS client and what is the NFS server. (Does "netapp" refer to a Netapp Filer or a FreeBSD box?) I'm not sure that matters, except that it isn't obvious to me if the leak you are referring to is in the NFS client or NFS server? > /boot/loader.conf > zfs_load="YES" > if_lagg_load="YES" > autoboot_delay="10" # Delay in seconds before autobooting, > start > # http://icesquare.com/wordpress/how-to-improve-zfs-performance/ > #I have 8G of Ram > #vfs.zfs.prefetch_disable=0 > > #If Ram = 4GB, set the value to 512M > #If Ram = 8GB, set the value to 1024M > #vfs.zfs.arc_min="1024M" > > #Ram x 0.5 - 512 MB > #vfs.zfs.arc_max="3584M" > > #Ram x 2 > vm.kmem_size_max="24G" > > #Ram x 1.5 > #vm.kmem_size="12G" > > > /etc/sysctl.conf > # $FreeBSD: release/9.0.0/etc/sysctl.conf 112200 2003-03-13 18:43:50Z > mux $ > # > # This file is read when going to multi-user and its contents piped > thru > # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for > details. > # > > # Uncomment this to prevent users from seeing information about > processes that > # are being run under another UID. > #security.bsd.see_other_uids=0 > kern.maxfiles=64000 > vfs.nfsd.maxthreads=16 > vfs.zfs.prefetch_disable=1 > > > The latter (vfs.zfs.prefetch_disable=1) make the bug a bit strange. > Inactive memory keeps growing, but active and free is still very low > during the copy. Then machine use all of his memory, and NFS server > not > responsive. > > /etc/rc.conf > hostname="filernew" > keymap="fr.iso.acc.kbd" > cloned_interfaces="lagg0" > ifconfig_em0="up" > ifconfig_em1="up" > ifconfig_lagg0="inet 172.31.x.x netmask 255.255.0.0 laggproto lacp > laggport em0 laggport em1" If you can take lagg out of the mix, I'd try that. > defaultrouter="172.31.x.x" > sshd_enable="YES" > ntpd_enable="YES" > powerd_enable="YES" > # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable > dumpdev="NO" > zfs_enable="YES" > puppet_enable="YES" > # NFS > rpcbind_enable="YES" > nfs_server_enable="YES" > nfs_server_flags="-u -t -n 4" > mountd_flags="-r" > mountd_enable="YES" > rpc_lockd_enable="YES" > rpc_statd_enable="YES" > > # Added by Puppet > bsnmpd_enable="YES" > > Kind regards... > > Xavier > Good luck with it, rick > -- > Xavier Beaudouin > _______________________________________________ > 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 Thu Nov 8 14:28:24 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 24E2323C for ; Thu, 8 Nov 2012 14:28:24 +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 C11FA8FC12 for ; Thu, 8 Nov 2012 14:28:23 +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 1TWT5g-000300-Ou; Thu, 08 Nov 2012 16:28:20 +0200 Received: by pm513-1.comsys.ntu-kpi.kiev.ua (Postfix, from userid 1001) id BCF5B1E08A; Thu, 8 Nov 2012 16:28:21 +0200 (EET) Date: Thu, 8 Nov 2012 16:28:21 +0200 From: Andrey Simonenko To: Rick Macklem Subject: Re: NFS export with space in directory name Message-ID: <20121108142821.GA55875@pm513-1.comsys.ntu-kpi.kiev.ua> References: <416641890.106495.1352333402239.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <416641890.106495.1352333402239.JavaMail.root@erie.cs.uoguelph.ca> 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-11-08 16:28:20 X-Connected-IP: 10.18.52.101:43107 X-Message-Linecount: 32 X-Body-Linecount: 16 X-Message-Size: 1447 X-Body-Size: 641 Cc: freebsd-fs@freebsd.org, Mickael Canevet X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 14:28:24 -0000 On Wed, Nov 07, 2012 at 07:10:02PM -0500, Rick Macklem wrote: > Mickael Canevet wrote: > > > > So I'd like to know if there is a way to export a directory with a > > space in > > its name on FreeBSD 9.0-RELEASE ? > > > Running mountd-> Nope. > > I am not sure if nfse can support this? (It can be found on sourceforge.net > and I've cc'd Andrey, since he'll know the answer.) Such support exists in nfs.exports(5) (nfse native mode), a pathname can be enclosed in double quotes or any character can be represented by three octal digits of its ASCII code. Such support will not work in "nfse -C", since exports(5) does not support this. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 14:37: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 A92C65C6 for ; Thu, 8 Nov 2012 14:37:30 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 6CC168FC12 for ; Thu, 8 Nov 2012 14:37:30 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1TWTEV-000DGz-1R; Thu, 08 Nov 2012 09:37:27 -0500 Date: Thu, 8 Nov 2012 09:37:26 -0500 From: Gary Palmer To: Beeblebrox Subject: Re: [ZFS] How to fix corrupt ZDB Message-ID: <20121108143726.GB24320@in-addr.com> References: <1352294866076-5758864.post@n5.nabble.com> <509A66D2.5060706@gmail.com> <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> <1352356496801-5759081.post@n5.nabble.com> <1352370415751-5759123.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1352370415751-5759123.post@n5.nabble.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 14:37:30 -0000 On Thu, Nov 08, 2012 at 02:26:55AM -0800, Beeblebrox wrote: > *** correction on previous post *** > > > Beeblebrox wrote > > This command also did not change the corrupt entry for an old pool: > * > > # zdb -c * > * > > zdb: can't open 'asp': No such file or directory > > It turns out, ZDB just looks in the first folder / file name it runs into > when running this command. So change to a different folder, run the command > and the error message changes to complain about a different folder. I was > running that command at the top-level and I have a folder named "asp" there > as well. > > So disregard that bit... More correctly, the * was expanded by the shell as a list of files/directories in the pwd for you and then passed to zdb as arguments. Regards, Gary From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 14:53:17 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 9499AAC1 for ; Thu, 8 Nov 2012 14:53:17 +0000 (UTC) (envelope-from kiwi@oav.net) Received: from mail03.oav.net (mail03.oav.net [IPv6:2001:67c:ec:100::25:3]) by mx1.freebsd.org (Postfix) with ESMTP id 19A1F8FC14 for ; Thu, 8 Nov 2012 14:53:17 +0000 (UTC) Received: from amavis2.local.oav.net (unknown [IPv6:2001:67c:ec:100::25:42]) by mail03.oav.net (Postfix) with ESMTP id 1FD9661C4D; Thu, 8 Nov 2012 15:53:16 +0100 (CET) (envelope-from kiwi@oav.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=oav.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=a; t=1352386389; x= 1354200790; bh=8rZzh5CYxUZZCz56QGO1q6p/qtrltf+eSHjDZvyA6QY=; b=D rUNBYvqQQa3icwEd8CO6Ez6Wx8WDDrlQt+U1npT1GJDzvcIJJsJ5RfocWQ2GRgZ4 nqjnv4RQodqReVrWVwyKY+UqTS1insgbIUvkbJIpQQWMIOMwIQtorCzzOhSV3VWo FM4s800vh7msvL/PSg/cudOnmh+4gYL1YQS3Z+4LqE= X-Virus-Scanned: Amavisd-new at amavis2.local.oav.net.local.oav.net Received: from mail01.oav.net ([172.31.1.1]) by amavis2.local.oav.net (amavis2.local.oav.net [172.31.1.42]) (amavisd-new, port 10026) with LMTP id LxfuBJ1jI78V; Thu, 8 Nov 2012 15:53:09 +0100 (CET) Received: from calchas.nic.fr (calchas.tech.ipv6.nic.fr [IPv6:2001:67c:2219:7::86:40]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: kiwi@oav.net) by mail01.oav.net (Postfix) with ESMTPSA id D872161C5D; Thu, 8 Nov 2012 15:53:09 +0100 (CET) (envelope-from kiwi@oav.net) Message-ID: <509BC6A1.9040102@oav.net> Date: Thu, 08 Nov 2012 15:50:09 +0100 From: Xavier Beaudouin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121031 Thunderbird/16.0.2 MIME-Version: 1.0 To: Rick Macklem Subject: Re: 9.0-RELEASE-p4 + NFS + ZFS = issues... :/ (probably a memory leak) References: <1066915051.120042.1352382998672.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1066915051.120042.1352382998672.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 14:53:17 -0000 Hi Rick, (...) >> Issue is comming when copying from a netapp to this machine a 70G data >> with bunch of big files (eg 600M ~ 8G) and web files. >> >> All NFS clients use NFSv3 and UDP. >> > There is this patch for NFSv3 over UDP: > http://people.freebsd.org/~rmacklem/udp-timer.patch > (It applies to both NFS clients, since it is krpc related.) > I can't remember what the implications of not having this patch is, but > if the client retries NFS RPCs too agressively, it could use a lot of > DRC storage (mbuf clusters mainly) in the NFS server (if the NFS server > is a FreeBSD box). > OR > Try the mounts using TCP and see if the problem goes away. I will try this patch. :) TCP mount... gave me usualy lots of pain (but this is my own experience...) Is there really improovments with tcp ? :) > If it is slow leak, doing "vmstat -z" and "vmstat -m" while the system > is getting constipated might show what is leaking. Will try this patch. Maybe this will fix it... I keep you in touch. >> Tried : >> >> nfs client netapp and freebsd on the same machine : 1srt rsync from >> netapp to freebsd ok : no issue, second rsync : memory leak, swap is >> used (about less than 100Mb, but this trigger the bug. >> >> nfs client of the netapp is the "filer" machine, and the destination >> is >> local zfs spool. The rsync to make up to date data trigger as well the >> issue. >> > I'll admit you lost me w.r.t. what is the NFS client and what is the > NFS server. (Does "netapp" refer to a Netapp Filer or a FreeBSD box?) > I'm not sure that matters, except that it isn't obvious to me if the > leak you are referring to is in the NFS client or NFS server? I was a bit unclear. Sorry :) So let me rephrase :) Scenario A : Netapp server -> FreeBSD 8.x NFS Client -> FreeBSD 9.0-p4 server w/ ZFS Scenario B : Netapp server -> FreeBSD 9.0-p4 server w/ ZFS as NFS client I wanted on my own to remoce the part : the nfs server on freeBSD 9.0-p4 is leaking memory. Will try the udp patch and report. Kind regards, Xavier From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 15:11: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 1E09013B for ; Thu, 8 Nov 2012 15:11:54 +0000 (UTC) (envelope-from mickael.canevet@gmail.com) Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id CB8E58FC08 for ; Thu, 8 Nov 2012 15:11:53 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id k10so2604001iag.13 for ; Thu, 08 Nov 2012 07:11:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oVCGQNEfQC9hX1sVucMjKSUnH18Y+XtvdSGaTfR70Nc=; b=B0z7PQNEb7QTEpjSzja4McCyeXojTSyllidhNNEDVorpMzTL3jsBxTjm6QrnIm2SO8 6fMs58gmq1UKNC36Gxh4V8v/C8OqiTKaCJRXtG+CPiApTS3BMt5/+1nmsnrkvADISt3r hVw8nF7A083IoGw1sZQ9KNSmaLqF6QRY7/BW4wog5B1D1zIGP1Q6EtWdDaV39n2ZTQgm f5/2YkHowrL62DuspXbYXTFHjXP50pphlLNlUWimIngg4YEF43R/7BZ70/W2CePBzeWH iROiqZbSAVAXGwcPh57+lqJtp/vwwCeMDocVTRyWMc8qAiJQ76rFhbboEK10wQ297BG5 SEgA== MIME-Version: 1.0 Received: by 10.50.153.137 with SMTP id vg9mr20510976igb.40.1352387512846; Thu, 08 Nov 2012 07:11:52 -0800 (PST) Received: by 10.64.28.172 with HTTP; Thu, 8 Nov 2012 07:11:52 -0800 (PST) In-Reply-To: <20121108142821.GA55875@pm513-1.comsys.ntu-kpi.kiev.ua> References: <416641890.106495.1352333402239.JavaMail.root@erie.cs.uoguelph.ca> <20121108142821.GA55875@pm513-1.comsys.ntu-kpi.kiev.ua> Date: Thu, 8 Nov 2012 16:11:52 +0100 Message-ID: Subject: Re: NFS export with space in directory name From: =?UTF-8?B?TWlja2HDq2wgQ2Fuw6l2ZXQ=?= To: Andrey Simonenko Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 15:11:54 -0000 On Thu, Nov 8, 2012 at 3:28 PM, Andrey Simonenko < simon@comsys.ntu-kpi.kiev.ua> wrote: > On Wed, Nov 07, 2012 at 07:10:02PM -0500, Rick Macklem wrote: > > Mickael Canevet wrote: > > > > > > So I'd like to know if there is a way to export a directory with a > > > space in > > > its name on FreeBSD 9.0-RELEASE ? > > > > > Running mountd-> Nope. > > > > I am not sure if nfse can support this? (It can be found on > sourceforge.net > > and I've cc'd Andrey, since he'll know the answer.) > > Such support exists in nfs.exports(5) (nfse native mode), a pathname can be > enclosed in double quotes or any character can be represented by three > octal > digits of its ASCII code. Such support will not work in "nfse -C", since > exports(5) does not support this. > OK, thanks for the explanation. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 16:07:41 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 1960D430 for ; Thu, 8 Nov 2012 16:07:41 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id E877E8FC0A for ; Thu, 8 Nov 2012 16:07:40 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TWUdo-0000y4-57 for freebsd-fs@freebsd.org; Thu, 08 Nov 2012 08:07:40 -0800 Date: Thu, 8 Nov 2012 08:07:40 -0800 (PST) From: Beeblebrox To: freebsd-fs@freebsd.org Message-ID: <1352390860142-5759205.post@n5.nabble.com> In-Reply-To: <20121108143726.GB24320@in-addr.com> References: <1352294866076-5758864.post@n5.nabble.com> <509A66D2.5060706@gmail.com> <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> <1352356496801-5759081.post@n5.nabble.com> <1352370415751-5759123.post@n5.nabble.com> <20121108143726.GB24320@in-addr.com> Subject: Re: [ZFS] How to fix corrupt ZDB MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 16:07:41 -0000 output for *# zdb* is the same as *# zdb -C* bsdr: version: 28 name: 'bsdr' state: 0 txg: 43281 pool_guid: 18171682415991203571 hostid: 2739729201 hostname: 'rbsd.me' vdev_children: 2 vdev_tree: type: 'root' id: 0 guid: 18171682415991203571 children[0]: type: 'disk' id: 0 guid: 3768638969829014374 path: '/dev/ada0' phys_path: '/dev/ada0' whole_disk: 1 metaslab_array: 30 metaslab_shift: 31 ashift: 9 asize: 320068124672 is_log: 0 DTL: 42 create_txg: 4 children[1]: type: 'disk' id: 1 guid: 1129540067409051140 path: '/dev/ada1p9' phys_path: '/dev/ada1p9' whole_disk: 1 metaslab_array: 166 metaslab_shift: 24 ashift: 12 asize: 2035548160 is_log: 1 create_txg: 23549 Interestingly, the log on SSD /dev/ada1p9 correctly shows ashift 12 - So that is correct. Root pool is on a regular samsung (no 4k). *# zdb -l /dev/ada0* LABEL 0 -------------------------------------------- version: 28 name: 'bsdr' state: 0 txg: 43281 pool_guid: 18171682415991203571 hostid: 2739729201 hostname: 'rbsd.me' top_guid: 3768638969829014374 guid: 3768638969829014374 vdev_children: 2 vdev_tree: type: 'disk' id: 0 guid: 3768638969829014374 path: '/dev/ada0' phys_path: '/dev/ada0' whole_disk: 1 metaslab_array: 30 metaslab_shift: 31 ashift: 9 asize: 320068124672 is_log: 0 DTL: 42 create_txg: 4 The exact same information is repeated 4 times from LABEL 0 -> LABEL 3 *# zdb -l /dev/ada1p9 * LABEL 0 -------------------------------------------- version: 28 name: 'bsdr' state: 0 txg: 43281 pool_guid: 18171682415991203571 hostid: 2739729201 hostname: 'rbsd.me' top_guid: 1129540067409051140 guid: 1129540067409051140 is_log: 1 vdev_children: 2 vdev_tree: type: 'disk' id: 1 guid: 1129540067409051140 path: '/dev/ada1p9' phys_path: '/dev/ada1p9' whole_disk: 1 metaslab_array: 166 metaslab_shift: 24 ashift: 12 asize: 2035548160 is_log: 1 create_txg: 23549 The exact same information is repeated 4 times from LABEL 0 -> LABEL 3 It looks like I made a big deal out of nothing? -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-How-to-fix-corrupt-ZDB-tp5758864p5759205.html Sent from the freebsd-fs mailing list archive at Nabble.com. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 16:47: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 6FF036A6 for ; Thu, 8 Nov 2012 16:47:44 +0000 (UTC) (envelope-from prvs=1659aa6059=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id E47308FC15 for ; Thu, 8 Nov 2012 16:47:43 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50000991184.msg for ; Thu, 08 Nov 2012 16:47:41 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 08 Nov 2012 16:47:41 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1659aa6059=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <29E4BB2D5E9840E799915414365B6CB1@multiplay.co.uk> From: "Steven Hartland" To: "Beeblebrox" , References: <1352294866076-5758864.post@n5.nabble.com> <509A66D2.5060706@gmail.com> <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> <1352356496801-5759081.post@n5.nabble.com> <1352370415751-5759123.post@n5.nabble.com> <20121108143726.GB24320@in-addr.com> <1352390860142-5759205.post@n5.nabble.com> Subject: Re: [ZFS] How to fix corrupt ZDB Date: Thu, 8 Nov 2012 16:47:43 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 16:47:44 -0000 ----- Original Message ----- From: "Beeblebrox" To: Sent: Thursday, November 08, 2012 4:07 PM Subject: Re: [ZFS] How to fix corrupt ZDB > output for *# zdb* is the same as *# zdb -C* > bsdr: > version: 28 > name: 'bsdr' > state: 0 > txg: 43281 > pool_guid: 18171682415991203571 > hostid: 2739729201 > hostname: 'rbsd.me' > vdev_children: 2 > vdev_tree: > type: 'root' > id: 0 > guid: 18171682415991203571 > children[0]: > type: 'disk' > id: 0 > guid: 3768638969829014374 > path: '/dev/ada0' > phys_path: '/dev/ada0' > whole_disk: 1 > metaslab_array: 30 > metaslab_shift: 31 > ashift: 9 > asize: 320068124672 > is_log: 0 > DTL: 42 > create_txg: 4 > children[1]: > type: 'disk' > id: 1 > guid: 1129540067409051140 > path: '/dev/ada1p9' > phys_path: '/dev/ada1p9' > whole_disk: 1 > metaslab_array: 166 > metaslab_shift: 24 > ashift: 12 > asize: 2035548160 > is_log: 1 > create_txg: 23549 > Interestingly, the log on SSD /dev/ada1p9 correctly shows ashift 12 - So > that is correct. Root pool is on a regular samsung (no 4k). > > *# zdb -l /dev/ada0* > LABEL 0 > -------------------------------------------- > version: 28 > name: 'bsdr' > state: 0 > txg: 43281 > pool_guid: 18171682415991203571 > hostid: 2739729201 > hostname: 'rbsd.me' > top_guid: 3768638969829014374 > guid: 3768638969829014374 > vdev_children: 2 > vdev_tree: > type: 'disk' > id: 0 > guid: 3768638969829014374 > path: '/dev/ada0' > phys_path: '/dev/ada0' > whole_disk: 1 > metaslab_array: 30 > metaslab_shift: 31 > ashift: 9 > asize: 320068124672 > is_log: 0 > DTL: 42 > create_txg: 4 > The exact same information is repeated 4 times from LABEL 0 -> LABEL 3 > > *# zdb -l /dev/ada1p9 * > LABEL 0 > -------------------------------------------- > version: 28 > name: 'bsdr' > state: 0 > txg: 43281 > pool_guid: 18171682415991203571 > hostid: 2739729201 > hostname: 'rbsd.me' > top_guid: 1129540067409051140 > guid: 1129540067409051140 > is_log: 1 > vdev_children: 2 > vdev_tree: > type: 'disk' > id: 1 > guid: 1129540067409051140 > path: '/dev/ada1p9' > phys_path: '/dev/ada1p9' > whole_disk: 1 > metaslab_array: 166 > metaslab_shift: 24 > ashift: 12 > asize: 2035548160 > is_log: 1 > create_txg: 23549 > The exact same information is repeated 4 times from LABEL 0 -> LABEL 3 > > It looks like I made a big deal out of nothing? Yep that all looks good to me. Your pool is using 512 byte blocks and your log is using 4k so all fine :) Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 17:49:37 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 4FEDB21F for ; Thu, 8 Nov 2012 17:49:37 +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 B21FE8FC0C for ; Thu, 8 Nov 2012 17:49:35 +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 qA8HnM49063224 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 8 Nov 2012 19:49:23 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <509BF0A2.2050600@digsys.bg> Date: Thu, 08 Nov 2012 19:49:22 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.10) Gecko/20121029 Thunderbird/10.0.10 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: zfs remove vdev functionality Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 17:49:37 -0000 I was thinking on how to implement vdev removal on ZFS and came to this idea: If we can have an per-vdev flag that prohibits new allocations on the vdev, but permits reads and frees - then we could mark so the vdev we intend to remove form the zpool and issue an scrub-like command that will rewrite all blocks allocated form that particular vdev. Since ZFS is COW, this will effectively move all blocks off that "no write" vdev and we can now detach it. All this could be implemented with the new ZFS feature flags, so no version bumps etc are necessary. Is there something I didn't think of? Daniel From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 19:39:14 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C694DD3 for ; Thu, 8 Nov 2012 19:39:14 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8CEE88FC1A for ; Thu, 8 Nov 2012 19:39:13 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id c10so1550330eaa.13 for ; Thu, 08 Nov 2012 11:39:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=IY3YJ0EuCZ1COFeWAn7hkhpP6vi5MFH08ihryHC1ItQ=; b=QPQcScL0lPOlMwmmUUXxPxrCtT8IWotat10YVk9MGBk1mwfmcVNGA0YR8Q6n6WBpjF o5BmtT5edB99sXIyUQVvGMp5GLNPc2aDSTWpWJCWX0WJMZRUIZNExzUdRB3/7kp8eBeX d1UaLllyAN3Q2xFMsokmkIwr00iCyzKf/rHkx1B0YWAA2LQCUB4mp2tLxYYthtecntbQ eoa51/42+FiceceV/jbKoJw4wALyCbI3pCd6FYWwWxSodPgu8pUL/K5RRgxSL1E3Oh5o FxFYfGlAmdUJxuqgrj7cxBMqu/VTcsnhRSIccc4Q+diaLY1LA1DaOZZo0DK/aJ3lCyWU +zDg== Received: by 10.14.223.4 with SMTP id u4mr30272181eep.19.1352403552742; Thu, 08 Nov 2012 11:39:12 -0800 (PST) Received: from [10.0.0.86] ([93.152.184.10]) by mx.google.com with ESMTPS id g5sm72066772eem.4.2012.11.08.11.39.10 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 08 Nov 2012 11:39:11 -0800 (PST) Subject: Re: zfs remove vdev functionality Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Content-Type: text/plain; charset=us-ascii From: Nikolay Denev In-Reply-To: <509BF0A2.2050600@digsys.bg> Date: Thu, 8 Nov 2012 21:39:09 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <393C72B3-7231-47C6-ABD2-1C6BA166ED11@gmail.com> References: <509BF0A2.2050600@digsys.bg> To: Daniel Kalchev X-Mailer: Apple Mail (2.1499) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 19:39:14 -0000 On Nov 8, 2012, at 7:49 PM, Daniel Kalchev wrote: > I was thinking on how to implement vdev removal on ZFS and came to = this idea: >=20 > If we can have an per-vdev flag that prohibits new allocations on the = vdev, but permits reads and frees - then we could mark so the vdev we = intend to remove form the zpool and issue an scrub-like command that = will rewrite all blocks allocated form that particular vdev. Since ZFS = is COW, this will effectively move all blocks off that "no write" vdev = and we can now detach it. >=20 > All this could be implemented with the new ZFS feature flags, so no = version bumps etc are necessary. >=20 > Is there something I didn't think of? >=20 > Daniel > _______________________________________________ > 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 don't think this will be that easy, because of snapshots, clones etc. There was a project that you are probably aware of called BP Rewrite = (block pointer rewrite), that was interrupted by Sun-Oracle merger. It very well may be still = being worked on in Sun, who knows :) The closest thing to your idea that I seem to find is this : = https://www.illumos.org/issues/1051 Cheers, Nikolay= From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 21:07: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 BCA0D45D for ; Thu, 8 Nov 2012 21:07:26 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 677F28FC0A for ; Thu, 8 Nov 2012 21:07:25 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so4161013vba.13 for ; Thu, 08 Nov 2012 13:07:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=kMheIp0MAIt6u8EsYbp203ums3uwoLEkHzp2UXzZO4U=; b=kO9ik4PCYrkCDF68Bp0WP94rglte/WFB/vfiDN7IoAfdoJklQM8vZDr2orjJzHsS9x rJ1j/KDv5z0P/9pXSPP6xJNICRaC0RP49630jRIKx2N0PQEfQkvHhONaT9Tho0uFcwAB PEOsKx7gjC0mjwcgJvRjWYEgP6czDzTFO/UdZpWrLPXGQUCSo4xQ7/LRrBi+qVpaD2Kh qJyN2GRpG6xOV5oaBvW2Op0Kgi2Qf/haLX8+X3P3qj5h4pe9gCU8tWvLO3wo+JjjC1GV JTKknlhzyu+GtdEAK63zMClOcos2Ag9otOOY6btOJKMF7yFx9xfTbXI99dTgWaTg6WiV YHlg== MIME-Version: 1.0 Received: by 10.52.98.105 with SMTP id eh9mr7433554vdb.11.1352408844775; Thu, 08 Nov 2012 13:07:24 -0800 (PST) Received: by 10.58.233.39 with HTTP; Thu, 8 Nov 2012 13:07:24 -0800 (PST) Date: Thu, 8 Nov 2012 21:07:24 +0000 Message-ID: Subject: SSD recommendations for ZFS cache/log From: Tom Evans To: FreeBSD FS Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 21:07:26 -0000 Hi all I'm upgrading my home ZFS setup, and want to speed things up a bit by adding some SSDs for cache/log. I was hoping some more experienced heads could offer some advice on what I've gleaned so far. I've read that the Sandforce based devices get their astonishing write speeds from compressible data, and that on random data, it is significantly worse, so comparing headline write speeds is not that useful. I've also read that MLC flash is significantly slower writing to the 2nd bit, and so the drive firmware will constantly be moving bits in the background from 1st bit to 2nd bit, in order to keep high write speeds, and so the firmware is specially important, which to my mind rules out devices using stock Sandforce firmware (everyone but Intel), and OCZ, who I've read too many horror stories about. This is a home setup, so SLC is out unfortunately. Is it still recommended to have a mirror for log device, now that pools can survive losing a log device unexpectedly? I was planning to get two 128GB drives, and slice them up 4/8/20/96 for UFS root, swap, log, cache respectively, but I could instead get a single larger and faster drive. The drives I am thinking of getting are either Intel 330, Intel 520, Crucial M4 RealSSD or Samsung 830, all in their 120/128GB variants. Any advice gratefully accepted. Cheers Tom From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 23:50:25 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 3574BB1F; Thu, 8 Nov 2012 23:50:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 047DC8FC08; Thu, 8 Nov 2012 23:50: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 qA8NoOiU081904; Thu, 8 Nov 2012 23:50:24 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA8NoOcZ081900; Thu, 8 Nov 2012 23:50:24 GMT (envelope-from linimon) Date: Thu, 8 Nov 2012 23:50:24 GMT Message-Id: <201211082350.qA8NoOcZ081900@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/173442: [zfs] ZFS ZVOL snapshot device nodes are not removed X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 23:50:25 -0000 Old Synopsis: ZFS ZVOL snapshot device nodes are not removed New Synopsis: [zfs] ZFS ZVOL snapshot device nodes are not removed Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Nov 8 23:50:02 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=173442 From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 00:22: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 2C4AC52D for ; Fri, 9 Nov 2012 00:22:44 +0000 (UTC) (envelope-from prvs=1660defc6c=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id AEC2F8FC12 for ; Fri, 9 Nov 2012 00:22:43 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50000995205.msg for ; Fri, 09 Nov 2012 00:22:42 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Fri, 09 Nov 2012 00:22:42 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1660defc6c=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Tom Evans" , "FreeBSD FS" References: Subject: Re: SSD recommendations for ZFS cache/log Date: Fri, 9 Nov 2012 00:22:46 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 00:22:44 -0000 ----- Original Message ----- From: "Tom Evans" To: "FreeBSD FS" Sent: Thursday, November 08, 2012 9:07 PM Subject: SSD recommendations for ZFS cache/log > Hi all > > I'm upgrading my home ZFS setup, and want to speed things up a bit by > adding some SSDs for cache/log. I was hoping some more experienced > heads could offer some advice on what I've gleaned so far. > > I've read that the Sandforce based devices get their astonishing write > speeds from compressible data, and that on random data, it is > significantly worse, so comparing headline write speeds is not that > useful. I've also read that MLC flash is significantly slower writing > to the 2nd bit, and so the drive firmware will constantly be moving > bits in the background from 1st bit to 2nd bit, in order to keep high > write speeds, and so the firmware is specially important, which to my > mind rules out devices using stock Sandforce firmware (everyone but > Intel), and OCZ, who I've read too many horror stories about. This is > a home setup, so SLC is out unfortunately. > > Is it still recommended to have a mirror for log device, now that > pools can survive losing a log device unexpectedly? I was planning to > get two 128GB drives, and slice them up 4/8/20/96 for UFS root, swap, > log, cache respectively, but I could instead get a single larger and > faster drive. > > The drives I am thinking of getting are either Intel 330, Intel 520, > Crucial M4 RealSSD or Samsung 830, all in their 120/128GB variants. > Any advice gratefully accepted. New Intel drive announced the other day sounds nice, very much focused on constant timings instead of streaming / random benchmarks. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 01:57: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 246736DD for ; Fri, 9 Nov 2012 01:57:19 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) by mx1.freebsd.org (Postfix) with ESMTP id E7FE28FC12 for ; Fri, 9 Nov 2012 01:57:18 +0000 (UTC) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id 2C01A37B6E8; Thu, 8 Nov 2012 19:57:12 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3XyPcl33GLzYrY; Thu, 8 Nov 2012 19:57:11 -0600 (CST) Date: Thu, 8 Nov 2012 19:57:11 -0600 From: "Matthew D. Fuller" To: Tom Evans Subject: Re: SSD recommendations for ZFS cache/log Message-ID: <20121109015711.GB66994@over-yonder.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.21-fullermd.4 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.6 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 01:57:19 -0000 On Thu, Nov 08, 2012 at 09:07:24PM +0000 I heard the voice of Tom Evans, and lo! it spake thus: > > I've read that the Sandforce based devices get their astonishing > write speeds from compressible data, and that on random data, it is > significantly worse, so comparing headline write speeds is not that > useful. Yes, but don't read too much into that. It doesn't mean the drive falls over and acts like a 4200RPM PIO ATA drive, it just means the "easy" benchmarking shows compressible numbers, which are higher than what it's likely to get on real data. So with simplistic checking, they often beat other SSD's quite hard on benchmark numbers, but don't really pull off the same crushing in real life. Nowadays a lot of the benchmarks you'll find test them with incompressible data too, and they generally wind up in the same territory as other major SSD's with that. > I've also read that MLC flash is significantly slower writing to the > 2nd bit, and so the drive firmware will constantly be moving bits in > the background from 1st bit to 2nd bit, That... isn't even meaningful. So somebody wrote some stuff on an acid trip ;p > Is it still recommended to have a mirror for log device, now that > pools can survive losing a log device unexpectedly? Remember how the log works; it only ever gets read in the case of an unclean shutdown, so your only chance to lose data is that stuff gets committed into the log, THEN you get a crash/powerpull/etc, THEN the drive dies/throws errors when you come back up. If it dies any other time, no problem, it just disables. The previous state was that once you added a log device, it was inextricably part of the pool, could never be removed, and it dying meant you lost the pool. Now [theoretically] that shouldn't be the case; the worst that can happen is you lost those couple-seconds of data. > The drives I am thinking of getting are either Intel 330, Intel 520, > Crucial M4 RealSSD or Samsung 830, all in their 120/128GB variants. I've got a m4 in the system I'm typing on, and an 830 in the system the typing is happening on. And there's another system (currently in testing, not yet in production) with a 520 in it. I like the m4 and 830; we mostly wound up with the 520 because happenstance made it the cheaper choice in that case. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 09:12:23 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 1F913A48 for ; Fri, 9 Nov 2012 09:12:23 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id E836E8FC13 for ; Fri, 9 Nov 2012 09:12:22 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TWkdM-0005L3-4F for freebsd-fs@freebsd.org; Fri, 09 Nov 2012 01:12:16 -0800 Date: Fri, 9 Nov 2012 01:12:16 -0800 (PST) From: Beeblebrox To: freebsd-fs@freebsd.org Message-ID: <1352452336122-5759482.post@n5.nabble.com> In-Reply-To: <29E4BB2D5E9840E799915414365B6CB1@multiplay.co.uk> References: <1352294866076-5758864.post@n5.nabble.com> <509A66D2.5060706@gmail.com> <8F907219A6904829A66E1E9A01696CF4@multiplay.co.uk> <1352356496801-5759081.post@n5.nabble.com> <1352370415751-5759123.post@n5.nabble.com> <20121108143726.GB24320@in-addr.com> <1352390860142-5759205.post@n5.nabble.com> <29E4BB2D5E9840E799915414365B6CB1@multiplay.co.uk> Subject: Re: [ZFS] How to fix corrupt ZDB MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 09:12:23 -0000 Thanks for your help [CLOSED] -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-How-to-fix-corrupt-ZDB-tp5758864p5759482.html Sent from the freebsd-fs mailing list archive at Nabble.com. From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 11:44:46 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 BC79070B for ; Fri, 9 Nov 2012 11:44:46 +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 34BA18FC12 for ; Fri, 9 Nov 2012 11:44:45 +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 qA9BicZA067717 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 9 Nov 2012 13:44:38 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <509CECA6.70308@digsys.bg> Date: Fri, 09 Nov 2012 13:44:38 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.10) Gecko/20121029 Thunderbird/10.0.10 MIME-Version: 1.0 To: Nikolay Denev Subject: Re: zfs remove vdev functionality References: <509BF0A2.2050600@digsys.bg> <393C72B3-7231-47C6-ABD2-1C6BA166ED11@gmail.com> In-Reply-To: <393C72B3-7231-47C6-ABD2-1C6BA166ED11@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 11:44:47 -0000 On 08.11.12 21:39, Nikolay Denev wrote: > On Nov 8, 2012, at 7:49 PM, Daniel Kalchev wrote: > >> I was thinking on how to implement vdev removal on ZFS and came to this idea: >> >> If we can have an per-vdev flag that prohibits new allocations on the vdev, but permits reads and frees - then we could mark so the vdev we intend to remove form the zpool and issue an scrub-like command that will rewrite all blocks allocated form that particular vdev. Since ZFS is COW, this will effectively move all blocks off that "no write" vdev and we can now detach it. >> >> All this could be implemented with the new ZFS feature flags, so no version bumps etc are necessary. >> >> Is there something I didn't think of? > I don't think this will be that easy, because of snapshots, clones etc. The snapshots etc are above the block allocator level, at which this should be implemented. I believe the BP rewrite is the same concept, except it was probably intended to increment the zpool version etc. My idea is to make this feature independent of the on-disk format. The only more involving change would be the "detach vdev" part. A side effect of this might be the ability to re-balance the data over all vdevs, which is an issue currently, especially if you add new vdevs to an reasonably full zpool. Daniel From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 12:40:02 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 6338A4E2 for ; Fri, 9 Nov 2012 12:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 492F28FC13 for ; Fri, 9 Nov 2012 12:40:02 +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 qA9Ce158052273 for ; Fri, 9 Nov 2012 12:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA9Ce13u052272; Fri, 9 Nov 2012 12:40:01 GMT (envelope-from gnats) Date: Fri, 9 Nov 2012 12:40:01 GMT Message-Id: <201211091240.qA9Ce13u052272@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org Cc: From: Guido Falsi Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Guido Falsi List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 12:40:02 -0000 The following reply was made to PR kern/150503; it has been noted by GNATS. From: Guido Falsi To: bug-followup@FreeBSD.org, william.franck@oceasys.net, Martin Matuska Cc: Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot Date: Fri, 09 Nov 2012 13:32:29 +0100 hi, I'm seeing something similar on a CURRENT Machine: I start from this system: FreeBSD ted 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r242126: Fri Oct 26 13:03:09 CEST 2012 root@ted:/usr/obj/usr/src/sys/TED amd64 Please note that this machine was already built with clang, and has been since I reinstalled OS on it at the start of October update sources: gfalsi@ted:/usr/src [0]> svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 242822 Node Kind: directory Schedule: normal Last Changed Author: gjb Last Changed Rev: 242816 Last Changed Date: 2012-11-09 05:52:15 +0100 (Fri, 09 Nov 2012) make buildworld, buildkernel and installkernel, reboot and I get this (copied by hand) after kernel booting(so loader seems to be ok): Trying to mount root from zfs:tank []... Mounting from zfs:tank failed with error 22 I then reboot the machine using a snapshot from https://pub.allbsd.org/FreeBSD-snapshots/amd64-amd64/10.0-HEAD-20121006-JPSNAP/ load zfs.ko and perform a zpool status and I get this output: pool: tank state: UNAVAIL status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and online it using 'zpool online'. see: http://illumos.org/msg/ZFS-8000-3C scan: none requested config: NAME STATE READ WRITE CKSUM tank UNAVAIL 0 0 0 mirror-0 UNAVAIL 0 0 0 13149740312808713750 UNAVAIL 0 0 0 was /dev/gpt/disk0 6984386892400701167 UNAVAIL 0 0 0 was /dev/gpt/disk1 mirror-1 UNAVAIL 0 0 0 10066834453677312324 UNAVAIL 0 0 0 was /dev/gpt/disk2 571766486195567663 UNAVAIL 0 0 0 was /dev/gpt/disk3 I fought a little with this then tried: zpool export tank ; zpool import -f -R /mnt/tank tank and can read the pool once more: pool: tank state: ONLINE scan: scrub repaired 0 in 0h13m with 0 errors on Thu Nov 8 16:43:19 2012 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 ada2p2 ONLINE 0 0 0 gpt/disk3 ONLINE 0 0 0 errors: No known data errors If I reboot now I get back to the same error and pool status as before, If I replace the old kernel machine reboots correctly. I'm going now to test checking out some old revision of the source to single out the faulty commit. Is this information useful to you? This is a test machine, so I can test patches and fixes there. I'd rather not loose the pool, but if that happens it's not that bad either. So I'm available for any further test or experiment. Thanks in advance! -- Guido Falsi From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 13:17: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 71A3515A for ; Fri, 9 Nov 2012 13:17:21 +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 1EBA08FC08 for ; Fri, 9 Nov 2012 13:17:20 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TWoSd-0004S6-Pr for freebsd-fs@freebsd.org; Fri, 09 Nov 2012 14:17:27 +0100 Received: from dyn1219-66.wlan.ic.ac.uk ([129.31.219.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Nov 2012 14:17:27 +0100 Received: from johannes by dyn1219-66.wlan.ic.ac.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Nov 2012 14:17:27 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Johannes Totz Subject: Re: zfs remove vdev functionality Date: Fri, 09 Nov 2012 13:17:08 +0000 Lines: 45 Message-ID: References: <509BF0A2.2050600@digsys.bg> <393C72B3-7231-47C6-ABD2-1C6BA166ED11@gmail.com> <509CECA6.70308@digsys.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: dyn1219-66.wlan.ic.ac.uk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 In-Reply-To: <509CECA6.70308@digsys.bg> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 13:17:21 -0000 On 09/11/2012 11:44, Daniel Kalchev wrote: > > > On 08.11.12 21:39, Nikolay Denev wrote: >> On Nov 8, 2012, at 7:49 PM, Daniel Kalchev wrote: >> >>> I was thinking on how to implement vdev removal on ZFS and came to >>> this idea: >>> >>> If we can have an per-vdev flag that prohibits new allocations on the >>> vdev, but permits reads and frees - then we could mark so the vdev >>> we intend to remove form the zpool and issue an scrub-like command >>> that will rewrite all blocks allocated form that particular vdev. >>> Since ZFS is COW, this will effectively move all blocks off that "no >>> write" vdev and we can now detach it. >>> >>> All this could be implemented with the new ZFS feature flags, so no >>> version bumps etc are necessary. >>> >>> Is there something I didn't think of? >> I don't think this will be that easy, because of snapshots, clones etc. > > The snapshots etc are above the block allocator level, at which this > should be implemented. Are you sure about this? Because exactly the reason that snapshots are built on the actual block pointer addresses makes the whole BP-rewrite so difficult. > I believe the BP rewrite is the same concept, except it was probably > intended to increment the zpool version etc. My idea is to make this > feature independent of the on-disk format. The only more involving > change would be the "detach vdev" part. > > A side effect of this might be the ability to re-balance the data over > all vdevs, which is an issue currently, especially if you add new vdevs > to an reasonably full zpool. > > Daniel > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 15:20:01 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 A4E6D244 for ; Fri, 9 Nov 2012 15:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 7177C8FC14 for ; Fri, 9 Nov 2012 15:20:01 +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 qA9FK1Pn063066 for ; Fri, 9 Nov 2012 15:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA9FK1qZ063065; Fri, 9 Nov 2012 15:20:01 GMT (envelope-from gnats) Date: Fri, 9 Nov 2012 15:20:01 GMT Message-Id: <201211091520.qA9FK1qZ063065@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org Cc: From: Andriy Gapon Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 15:20:01 -0000 The following reply was made to PR kern/150503; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@FreeBSD.org, Guido Falsi Cc: william.franck@oceasys.net, Martin Matuska Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot Date: Fri, 09 Nov 2012 17:14:52 +0200 > pool: tank > state: UNAVAIL > status: One or more devices could not be opened. There are insufficient > replicas for the pool to continue functioning. > action: Attach the missing device and online it using 'zpool online'. > see: http://illumos.org/msg/ZFS-8000-3C > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > tank UNAVAIL 0 0 0 > mirror-0 UNAVAIL 0 0 0 > 13149740312808713750 UNAVAIL 0 0 0 was > /dev/gpt/disk0 > 6984386892400701167 UNAVAIL 0 0 0 was > /dev/gpt/disk1 > mirror-1 UNAVAIL 0 0 0 > 10066834453677312324 UNAVAIL 0 0 0 was > /dev/gpt/disk2 > 571766486195567663 UNAVAIL 0 0 0 was > /dev/gpt/disk3 Commenting only on this piece. After some ZFS changes from about a month ago you can get this kind of output if your ZFS userland is older than your kernel ZFS. If this is the case, the then above message is just symptom of that discrepancy. > Trying to mount root from zfs:tank []... > Mounting from zfs:tank failed with error 22 22 is EINVAL, not sure how to interpret this failure. Could be a result of zpool.cache being produced by the older code, but not sure... -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 15:40:01 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 E5F0C6DA for ; Fri, 9 Nov 2012 15:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B348A8FC0C for ; Fri, 9 Nov 2012 15:40:01 +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 qA9Fe1QC063614 for ; Fri, 9 Nov 2012 15:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA9Fe1Dc063613; Fri, 9 Nov 2012 15:40:01 GMT (envelope-from gnats) Date: Fri, 9 Nov 2012 15:40:01 GMT Message-Id: <201211091540.qA9Fe1Dc063613@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org Cc: From: Guido Falsi Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Guido Falsi List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 15:40:02 -0000 The following reply was made to PR kern/150503; it has been noted by GNATS. From: Guido Falsi To: Andriy Gapon Cc: bug-followup@FreeBSD.org, william.franck@oceasys.net, Martin Matuska Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot Date: Fri, 09 Nov 2012 16:34:54 +0100 On 11/09/12 16:14, Andriy Gapon wrote: >> pool: tank >> state: UNAVAIL >> status: One or more devices could not be opened. There are insufficient >> replicas for the pool to continue functioning. >> action: Attach the missing device and online it using 'zpool online'. >> see: http://illumos.org/msg/ZFS-8000-3C >> scan: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> tank UNAVAIL 0 0 0 >> mirror-0 UNAVAIL 0 0 0 >> 13149740312808713750 UNAVAIL 0 0 0 was >> /dev/gpt/disk0 >> 6984386892400701167 UNAVAIL 0 0 0 was >> /dev/gpt/disk1 >> mirror-1 UNAVAIL 0 0 0 >> 10066834453677312324 UNAVAIL 0 0 0 was >> /dev/gpt/disk2 >> 571766486195567663 UNAVAIL 0 0 0 was >> /dev/gpt/disk3 > > > Commenting only on this piece. After some ZFS changes from about a month ago you > can get this kind of output if your ZFS userland is older than your kernel ZFS. > If this is the case, the then above message is just symptom of that discrepancy. > I also tried making make installkernel ; make installworld ; reboot, but had the same symptoms. luckily I was also able to rollback to a previous zfs snapshot from the USB key after the export/import trick. >> Trying to mount root from zfs:tank []... >> Mounting from zfs:tank failed with error 22 > > 22 is EINVAL, not sure how to interpret this failure. > Could be a result of zpool.cache being produced by the older code, but not sure... > Uhm I don't know how to generate a new zpool.cache from a newly update system, since I can't export/import the root and don't have a newer system on a USB key. I'll have to produce one perhaps. -- Guido Falsi From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 18:55:38 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E77A35EB for ; Fri, 9 Nov 2012 18:55:38 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9660C8FC16 for ; Fri, 9 Nov 2012 18:55:38 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so5460095vba.13 for ; Fri, 09 Nov 2012 10:55:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mNcGKd/7LC+7Aae2YlQQiGq4AyL93pyVDksq/qHx3Ic=; b=Ozrga7OqDu+W6OUCnWxe7Cmdeg5RBBKoj7IYTd8iz0pBgv+hM8n5Ahmp7Jnmga3jYS qmLj9LHcmqEsy471EgjdPIuh2G6WIglyGwPqChNzyOjmD2KSw7pf90g8C9FUh2eS7yMd RUJ9/KkzEZxVsBmdtMZXs+hFBI5JfVLJ7B6IX/V3DLPVvK5dg29lgdI/Ws5pjrS6uEKg ++oxHEEzty7/U73azuDqy3tznRDBnMztXy4bFAmFE9QLjYnEPT9Ho1eob4tKb+4385Q+ fF/6C7VSltaT2J7iCys1gG1yb3lfBTaeaWw9VCCiQ3f7DENvT1KamPSIFbCMyUVZTbTu 9KUw== MIME-Version: 1.0 Received: by 10.52.77.101 with SMTP id r5mr9779049vdw.25.1352487337732; Fri, 09 Nov 2012 10:55:37 -0800 (PST) Received: by 10.58.19.74 with HTTP; Fri, 9 Nov 2012 10:55:37 -0800 (PST) In-Reply-To: References: <509BF0A2.2050600@digsys.bg> <393C72B3-7231-47C6-ABD2-1C6BA166ED11@gmail.com> <509CECA6.70308@digsys.bg> Date: Fri, 9 Nov 2012 13:55:37 -0500 Message-ID: Subject: Re: zfs remove vdev functionality From: Rich To: Johannes Totz Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 18:55:39 -0000 I have not looked at the code to confirm this, but wouldn't the snapshots be built on the logical block addresses (e.g. the layer above the RAID/pool abstraction that maps to physical blocks) rather than physical block addresses? So as long as the logical block mapping is correct, the snapshot layer shouldn't care - it's if you were reshaping how the logical block layer being presented worked that would make this painful for that. Modulo the abstraction of translation that the DDT does, of course - I have no clue how that voodoo is implemented under the covers. - Rich On Fri, Nov 9, 2012 at 8:17 AM, Johannes Totz wrote: > On 09/11/2012 11:44, Daniel Kalchev wrote: > > > > > > On 08.11.12 21:39, Nikolay Denev wrote: > >> On Nov 8, 2012, at 7:49 PM, Daniel Kalchev wrote: > >> > >>> I was thinking on how to implement vdev removal on ZFS and came to > >>> this idea: > >>> > >>> If we can have an per-vdev flag that prohibits new allocations on the > >>> vdev, but permits reads and frees - then we could mark so the vdev > >>> we intend to remove form the zpool and issue an scrub-like command > >>> that will rewrite all blocks allocated form that particular vdev. > >>> Since ZFS is COW, this will effectively move all blocks off that "no > >>> write" vdev and we can now detach it. > >>> > >>> All this could be implemented with the new ZFS feature flags, so no > >>> version bumps etc are necessary. > >>> > >>> Is there something I didn't think of? > >> I don't think this will be that easy, because of snapshots, clones etc. > > > > The snapshots etc are above the block allocator level, at which this > > should be implemented. > > Are you sure about this? Because exactly the reason that snapshots are > built on the actual block pointer addresses makes the whole BP-rewrite > so difficult. > > > I believe the BP rewrite is the same concept, except it was probably > > intended to increment the zpool version etc. My idea is to make this > > feature independent of the on-disk format. The only more involving > > change would be the "detach vdev" part. > > > > A side effect of this might be the ability to re-balance the data over > > all vdevs, which is an issue currently, especially if you add new vdevs > > to an reasonably full zpool. > > > > Daniel > > _______________________________________________ > > 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" > > > > > _______________________________________________ > 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 Nov 10 12:34:30 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 B5F798BB; Sat, 10 Nov 2012 12:34:30 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 80B578FC0C; Sat, 10 Nov 2012 12:34:30 +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 qAACYUII012763; Sat, 10 Nov 2012 12:34:30 GMT (envelope-from avg@freefall.freebsd.org) Received: (from avg@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAACYUsx012759; Sat, 10 Nov 2012 12:34:30 GMT (envelope-from avg) Date: Sat, 10 Nov 2012 12:34:30 GMT Message-Id: <201211101234.qAACYUsx012759@freefall.freebsd.org> To: avg@FreeBSD.org, freebsd-fs@FreeBSD.org, avg@FreeBSD.org From: avg@FreeBSD.org Subject: Re: kern/173442: [zfs] ZFS ZVOL snapshot device nodes are not removed X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 12:34:30 -0000 Synopsis: [zfs] ZFS ZVOL snapshot device nodes are not removed Responsible-Changed-From-To: freebsd-fs->avg Responsible-Changed-By: avg Responsible-Changed-When: Sat Nov 10 12:34:30 UTC 2012 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=173442 From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 12:35:33 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 E53E4B51 for ; Sat, 10 Nov 2012 12:35:32 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id 6B3608FC12 for ; Sat, 10 Nov 2012 12:35:32 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1TXAHa-00023h-LW for freebsd-fs@freebsd.org; Sat, 10 Nov 2012 13:35:31 +0100 Received: from h253044.upc-h.chello.nl ([62.194.253.44] helo=pinky) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1TXAHa-0002qa-3f for freebsd-fs@freebsd.org; Sat, 10 Nov 2012 13:35:30 +0100 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-fs@freebsd.org Subject: Re: zfs remove vdev functionality References: <509BF0A2.2050600@digsys.bg> <393C72B3-7231-47C6-ABD2-1C6BA166ED11@gmail.com> <509CECA6.70308@digsys.bg> Date: Sat, 10 Nov 2012 13:35:29 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.10 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.0 X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_50 autolearn=disabled version=3.2.5 X-Scan-Signature: 22b714be0c51703cd3047a81d17f7b3c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 12:35:33 -0000 On Fri, 09 Nov 2012 19:55:37 +0100, Rich wrote: > I have not looked at the code to confirm this, but wouldn't the snapshots What keeps you from looking at the code? The answers are in there. Ronald. > be built on the logical block addresses (e.g. the layer above the > RAID/pool > abstraction that maps to physical blocks) rather than physical block > addresses? > > So as long as the logical block mapping is correct, the snapshot layer > shouldn't care - it's if you were reshaping how the logical block layer > being presented worked that would make this painful for that. > > Modulo the abstraction of translation that the DDT does, of course - I > have > no clue how that voodoo is implemented under the covers. > > - Rich > > > On Fri, Nov 9, 2012 at 8:17 AM, Johannes Totz wrote: > >> On 09/11/2012 11:44, Daniel Kalchev wrote: >> > >> > >> > On 08.11.12 21:39, Nikolay Denev wrote: >> >> On Nov 8, 2012, at 7:49 PM, Daniel Kalchev wrote: >> >> >> >>> I was thinking on how to implement vdev removal on ZFS and came to >> >>> this idea: >> >>> >> >>> If we can have an per-vdev flag that prohibits new allocations on >> the >> >>> vdev, but permits reads and frees - then we could mark so the vdev >> >>> we intend to remove form the zpool and issue an scrub-like command >> >>> that will rewrite all blocks allocated form that particular vdev. >> >>> Since ZFS is COW, this will effectively move all blocks off that "no >> >>> write" vdev and we can now detach it. >> >>> >> >>> All this could be implemented with the new ZFS feature flags, so no >> >>> version bumps etc are necessary. >> >>> >> >>> Is there something I didn't think of? >> >> I don't think this will be that easy, because of snapshots, clones >> etc. >> > >> > The snapshots etc are above the block allocator level, at which this >> > should be implemented. >> >> Are you sure about this? Because exactly the reason that snapshots are >> built on the actual block pointer addresses makes the whole BP-rewrite >> so difficult. >> >> > I believe the BP rewrite is the same concept, except it was probably >> > intended to increment the zpool version etc. My idea is to make this >> > feature independent of the on-disk format. The only more involving >> > change would be the "detach vdev" part. >> > >> > A side effect of this might be the ability to re-balance the data over >> > all vdevs, which is an issue currently, especially if you add new >> vdevs >> > to an reasonably full zpool. >> > >> > Daniel >> > _______________________________________________ >> > 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" >> > >> >> >> _______________________________________________ >> 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" >> > _______________________________________________ > 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 Nov 10 15:59:23 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 AB875EA8 for ; Sat, 10 Nov 2012 15:59:23 +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 558028FC17 for ; Sat, 10 Nov 2012 15:59:22 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; q=dns; s=sweb; b=2dvYtPG60Os7ZYmND1w M+l3NWVVEsoL+YWWosB5pvL746h5Va7q+ZRRWgrljnqmApCRpxatj+kK5DLNp5hd 1aX7pqisTtjnf21MQg0M/ZwUDONlJdB+48nU7pSjpshBT0CUXlkurSVnjhI8+9Ll f5D3nihN53Rc/LyUmTd6G2lE= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; s=sweb; bh=0oYPspgHnxI6nfSIxWI7FdQFH oDgj9HHnM1Yc8lIQSQ=; b=cbwNXziY0Y2NOhHJFylFvPOhm/VMxTaHOJNbXf224 WH/oUeulFHv2qdrByIMrDbJTFox8Gb6JifrfYkHeqRjd8C5XO6uo5Fp195AQI2cR HAdCcIcU3fw+MmgsiV5R6uewfU7/JiuhqR0swa9+YpOdx25q/YpnVYz7qi8tXdpZ 4E= Received: (qmail 67650 invoked from network); 10 Nov 2012 09:59:15 -0600 Received: from unknown (HELO ?10.10.0.115?) (bryan@shatow.net@10.10.0.115) by sweb.xzibition.com with ESMTPA; 10 Nov 2012 09:59:15 -0600 Message-ID: <509E79C7.10300@shatow.net> Date: Sat, 10 Nov 2012 09:59:03 -0600 From: Bryan Drewery User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Subject: ZFS can't delete files when over quota X-Enigmail-Version: 1.4.5 OpenPGP: id=3C9B0CF9; url=http://www.shatow.net/bryan/bryan.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 15:59:23 -0000 Is this known? # pwd /tank/distfiles/freebsd # rm -f ./KDE/qt-everywhere-opensource-src-4.7.4.tar.gz rm: ./KDE/qt-everywhere-opensource-src-4.7.4.tar.gz: Disc quota exceeded # zfs list -r tank/distfiles NAME USED AVAIL REFER MOUNTPOINT tank/distfiles 10.0G 0 25K /tank/distfiles tank/distfiles/freebsd 10.0G 0 10.0G /tank/distfiles/freebsd tank/distfiles/gentoo 80K 0 80K /tank/distfiles/gentoo # zfs list -rt snapshot tank/distfiles no datasets available # zfs get -s local all tank/distfiles NAME PROPERTY VALUE SOURCE tank/distfiles quota 10G local tank/distfiles sharenfs -maproot=root -network 10.10.0.0/16 local tank/distfiles compression off local tank/distfiles primarycache metadata local tank/distfiles secondarycache metadata local tank/distfiles com.sun:auto-snapshot false local Bryan From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 16:11:09 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 09634505 for ; Sat, 10 Nov 2012 16:11:09 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8BB078FC16 for ; Sat, 10 Nov 2012 16:11:08 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jm19so946991bkc.13 for ; Sat, 10 Nov 2012 08:11:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=4oxVVA9i5pahhiX4FSl92+1f85T1RJJE138b5ngj9z8=; b=byR8slOEUVsRbZx+iYbjNnga+/1z6c5DXUHcGG1/EnMDblEsHs1Z3rEhtbWO7PLVfI CMUhC9u9izGh811iXRW41LWjaz0Rm1saVxrkIwDOoZw0UC3wM8h7D+S/k3Eys2VnUm6A X8Cffc0gprYUCz2mSjycP69aGM4w3xG94w5QCSYJuYZLOwUSJBBN3aQAyf6wu+FRJgh9 DheZ0k+kNFVv/UcR6eakqgtZVLcgeaJFuaED2f/7SKqs13gf7lOEoHGQljFjBp7YGpym NQBn0eF3flMTqeyV5G0Rtx0/uctE1GNGXYJ90uyQ0lNYkEvnNP3T1o3vI8yAaxVs78pf z+lg== Received: by 10.204.147.212 with SMTP id m20mr141713bkv.103.1352563867641; Sat, 10 Nov 2012 08:11:07 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.50.197 with HTTP; Sat, 10 Nov 2012 08:10:37 -0800 (PST) In-Reply-To: <509E79C7.10300@shatow.net> References: <509E79C7.10300@shatow.net> From: Chris Rees Date: Sat, 10 Nov 2012 16:10:37 +0000 X-Google-Sender-Auth: hIKesCKwI7z3iqrLXLU4UBmzAcU Message-ID: Subject: Re: ZFS can't delete files when over quota To: Bryan Drewery Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 16:11:09 -0000 On 10 November 2012 15:59, Bryan Drewery wrote: > Is this known? > > # pwd > /tank/distfiles/freebsd > # rm -f ./KDE/qt-everywhere-opensource-src-4.7.4.tar.gz > rm: ./KDE/qt-everywhere-opensource-src-4.7.4.tar.gz: Disc quota exceeded > > # zfs list -r tank/distfiles > NAME USED AVAIL REFER MOUNTPOINT > tank/distfiles 10.0G 0 25K /tank/distfiles > tank/distfiles/freebsd 10.0G 0 10.0G /tank/distfiles/freebsd > tank/distfiles/gentoo 80K 0 80K /tank/distfiles/gentoo > > # zfs list -rt snapshot tank/distfiles > no datasets available > > # zfs get -s local all tank/distfiles > NAME PROPERTY VALUE > SOURCE > tank/distfiles quota 10G > local > tank/distfiles sharenfs -maproot=root -network > 10.10.0.0/16 local > tank/distfiles compression off > local > tank/distfiles primarycache metadata > local > tank/distfiles secondarycache metadata > local > tank/distfiles com.sun:auto-snapshot false > local Yes. You can truncate a big file if you find it using dd count=1 then delete it as a workaround. Chris From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 16:19: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 596C4732; Sat, 10 Nov 2012 16:19:21 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id E89318FC19; Sat, 10 Nov 2012 16:19:20 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so6383245vba.13 for ; Sat, 10 Nov 2012 08:19:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GZgCvmalDq5uNAuGMPED5JqoE+OOnzCSsszR0DtDTww=; b=QRHr+6br8UT/txHgVWsvrPkv0pJRiCMIScpCpfxQTuCVz5R1zBSHm5C4+Z2I1UVITv ckW6JkgOtxzzoHhMV103mBAtaUZpcH6gZlwXY+5IukUgk3sFVEuvwUZaDASAyxWNT8Gs JjgJnSSF0GtDSBDPK6DShlJVdcWWAk0IB9M5f1TgDVAvbm/8aR4b81ootHrQu/oqnnC2 xdnarUqBqCS/Tt8vVUbe4ycDDhMrHH7ZIc72xtpIpLMLvDBUFkPEkLEH4E4foCCCBp6U 5rXDJgpclZzpfo+REHWXjjyH63gaObT4NFjDjOYtKsBiiOaaGTOjDxnuRZwxOCWhTLCo SmNA== MIME-Version: 1.0 Received: by 10.52.33.197 with SMTP id t5mr6045759vdi.91.1352564359806; Sat, 10 Nov 2012 08:19:19 -0800 (PST) Received: by 10.58.207.114 with HTTP; Sat, 10 Nov 2012 08:19:19 -0800 (PST) In-Reply-To: References: <509E79C7.10300@shatow.net> Date: Sat, 10 Nov 2012 11:19:19 -0500 Message-ID: Subject: Re: ZFS can't delete files when over quota From: Ryan Stone To: Chris Rees Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-fs@freebsd.org" , Bryan Drewery X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 16:19:21 -0000 Perhaps rm should truncate the file itself before calling unlink? Or do that if unlink returns EDQUOT? On Sat, Nov 10, 2012 at 11:10 AM, Chris Rees wrote: > On 10 November 2012 15:59, Bryan Drewery wrote: > > Is this known? > > > > # pwd > > /tank/distfiles/freebsd > > # rm -f ./KDE/qt-everywhere-opensource-src-4.7.4.tar.gz > > rm: ./KDE/qt-everywhere-opensource-src-4.7.4.tar.gz: Disc quota exceeded > > > > # zfs list -r tank/distfiles > > NAME USED AVAIL REFER MOUNTPOINT > > tank/distfiles 10.0G 0 25K /tank/distfiles > > tank/distfiles/freebsd 10.0G 0 10.0G /tank/distfiles/freebsd > > tank/distfiles/gentoo 80K 0 80K /tank/distfiles/gentoo > > > > # zfs list -rt snapshot tank/distfiles > > no datasets available > > > > # zfs get -s local all tank/distfiles > > NAME PROPERTY VALUE > > SOURCE > > tank/distfiles quota 10G > > local > > tank/distfiles sharenfs -maproot=root -network > > 10.10.0.0/16 local > > tank/distfiles compression off > > local > > tank/distfiles primarycache metadata > > local > > tank/distfiles secondarycache metadata > > local > > tank/distfiles com.sun:auto-snapshot false > > local > > > Yes. You can truncate a big file if you find it using dd count=1 then > delete it as a workaround. > > Chris > _______________________________________________ > 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 Nov 10 16:50: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 82252530 for ; Sat, 10 Nov 2012 16:50:59 +0000 (UTC) (envelope-from kiwi@oav.net) Received: from mail03.oav.net (mail03.local.oav.net [IPv6:2001:67c:ec:100::25:3]) by mx1.freebsd.org (Postfix) with ESMTP id 0C4C48FC0C for ; Sat, 10 Nov 2012 16:50:58 +0000 (UTC) Received: from amavis2.local.oav.net (unknown [IPv6:2001:67c:ec:100::25:42]) by mail03.oav.net (Postfix) with ESMTP id 8BB2B61C42; Sat, 10 Nov 2012 17:50:57 +0100 (CET) (envelope-from kiwi@oav.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=oav.net; h= x-mailer:references:message-id:content-transfer-encoding:date :date:in-reply-to:from:from:subject:subject:mime-version :content-type:content-type:received:received; s=a; t=1352566257; x=1354380658; bh=qCPhKl8PvxkTmfTJyO+WH8y+fEVmG2yomWqBoz4ZwCc=; b= pZNzKFtijgyJ4B5jbUyh2WIB+IA4FZK6uZkc7N+BF2ZLClB9ER+WXqrU6Ncz/+gH uVPGvBLI8FtdmfFbf4pO6GajtrPiUr6SkwVeLzVkX7QGYrfanze7gFq4iLP448Ck dZDmcUxKu6V9rxGBDxxQVli3ijTK5y5M3uqcnDzGHF0= X-Virus-Scanned: Amavisd-new at amavis2.local.oav.net.local.oav.net Received: from mail03.oav.net ([172.31.1.3]) by amavis2.local.oav.net (amavis2.local.oav.net [172.31.1.42]) (amavisd-new, port 10026) with LMTP id 2MpZZnw-36Be; Sat, 10 Nov 2012 17:50:57 +0100 (CET) Received: from [192.168.0.172] (mts78-3-82-245-101-206.fbx.proxad.net [82.245.101.206]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: kiwi@oav.net) by mail03.oav.net (Postfix) with ESMTPSA id 394A561C3F; Sat, 10 Nov 2012 17:50:57 +0100 (CET) (envelope-from kiwi@oav.net) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\)) Subject: Re: 9.0-RELEASE-p4 + NFS + ZFS = issues... :/ (probably a memory leak) From: Xavier Beaudouin In-Reply-To: <509BC6A1.9040102@oav.net> Date: Sat, 10 Nov 2012 17:50:56 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1066915051.120042.1352382998672.JavaMail.root@erie.cs.uoguelph.ca> <509BC6A1.9040102@oav.net> To: Rick Macklem X-Mailer: Apple Mail (2.1486) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 16:50:59 -0000 Hi Rick, I did several nfs mount using the udp patch you gave me and also TCP = mount instead. Seem with vmstat -m that : NFS fh 1 1K - 342087 64 Is going to growing and growing. Umounting the nfs mount free some memory and I getting free memory = again. Seems that : rsync -r -v -p -o -g --times --specials --delete --exclude=3D.snapshot = /mnt/ /vol/hosting/ is raising this issue on my own (on case B, see previous mails). Any another hints? /Xavier From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 18:55: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 7C2C882D for ; Sat, 10 Nov 2012 18:55:32 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 04B228FC0C for ; Sat, 10 Nov 2012 18:55:31 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jm19so973305bkc.13 for ; Sat, 10 Nov 2012 10:55:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=t/GlKsbGTwKqGIOymnFsFsDF8YdbIqPlxZo5EiMSGfA=; b=KOYBUtCf3hDYcRX6hG3H0oQjBNCH05FkPDwfbRufvZ/2B9ZIaZX4FeGlxabKYm6HTg TnWajF5OvNBN8J35J/k11HaD33UE+Fm+fD+nrZNsZBvh5cFXW+XmK0TcI8CfF+jS2TZq p27K4sKirAlXXP1zyxL6f2bpZCDY5EKZMUfQQsuYRpGyT8X84cthdAMrUxjMjrHIgvaa 5Zi+0DbtqOkGrK8EHjad63eQH3je+CbaiSh3xz5sP6agXO7zfTAfffCBJYeXRASTq7T7 +pBPGZKaV7pyasIaokx/HM4Qqj3gczuNIltJmA2S7IGIWkXZ3oLxpk0kEVcR2ftIqIMs hVfw== Received: by 10.205.137.7 with SMTP id im7mr5092292bkc.25.1352573730764; Sat, 10 Nov 2012 10:55:30 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.50.197 with HTTP; Sat, 10 Nov 2012 10:55:00 -0800 (PST) In-Reply-To: References: <509E79C7.10300@shatow.net> From: Chris Rees Date: Sat, 10 Nov 2012 18:55:00 +0000 X-Google-Sender-Auth: iBpyRQCaKMp2dA2qm1QeZUtyuVk Message-ID: Subject: Re: ZFS can't delete files when over quota To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-fs@freebsd.org" , Bryan Drewery X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 18:55:32 -0000 Bryan, Please try the patch at [1]; if it works I'll document it. Chris [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff On 10 November 2012 16:19, Ryan Stone wrote: > Perhaps rm should truncate the file itself before calling unlink? Or do > that if unlink returns EDQUOT? > > > On Sat, Nov 10, 2012 at 11:10 AM, Chris Rees wrote: >> >> On 10 November 2012 15:59, Bryan Drewery wrote: >> > Is this known? >> > >> > # pwd >> > /tank/distfiles/freebsd >> > # rm -f ./KDE/qt-everywhere-opensource-src-4.7.4.tar.gz >> > rm: ./KDE/qt-everywhere-opensource-src-4.7.4.tar.gz: Disc quota exceeded >> > >> > # zfs list -r tank/distfiles >> > NAME USED AVAIL REFER MOUNTPOINT >> > tank/distfiles 10.0G 0 25K /tank/distfiles >> > tank/distfiles/freebsd 10.0G 0 10.0G /tank/distfiles/freebsd >> > tank/distfiles/gentoo 80K 0 80K /tank/distfiles/gentoo >> > >> > # zfs list -rt snapshot tank/distfiles >> > no datasets available >> > >> > # zfs get -s local all tank/distfiles >> > NAME PROPERTY VALUE >> > SOURCE >> > tank/distfiles quota 10G >> > local >> > tank/distfiles sharenfs -maproot=root -network >> > 10.10.0.0/16 local >> > tank/distfiles compression off >> > local >> > tank/distfiles primarycache metadata >> > local >> > tank/distfiles secondarycache metadata >> > local >> > tank/distfiles com.sun:auto-snapshot false >> > local >> >> >> Yes. You can truncate a big file if you find it using dd count=1 then >> delete it as a workaround. >> >> Chris >> _______________________________________________ >> 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 Nov 10 19:21:55 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 4BFFAE7C for ; Sat, 10 Nov 2012 19:21:55 +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 D6B9D8FC12 for ; Sat, 10 Nov 2012 19:21:54 +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:content-transfer-encoding; q=dns; s=sweb; b=wbvEaT rDzkKn8zbucVUBRZpeYAdwDiyZ5HOVGz1nsbVHsOUr6U+QpMGIuewNu9877cZClZ Be+EW8gHIY7EmxPuFnQnoI5EH8BPbi4Bjfc2H9aWk3yUb+/foCXyOMMoVCEvy+BC I/Bat/qYGT3TyRa6rLIOPUCx2nPzUCk2lfF7o= 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:content-transfer-encoding; s=sweb; bh=QUNQu/wwgjfk 406uwmOOV2TR5mNU744wm0HCQ1F/a3E=; b=Poom4OgMkCrRzPSMU/maf926wJPf ic/uYTKq/gM/of3za/2WqQ7KY3aT7rv84Cks/Mvw0cEeZWm6xWi2i3viTb1UdP3m 3B/Qdmc5MjAiw5WnxZTqvy8isTipiAS91ueEyzrqtEyx8cF2L/lg8LybrYBLu7vQ 2u/jheTijrIz378= Received: (qmail 52761 invoked from network); 10 Nov 2012 13:21:52 -0600 Received: from unknown (HELO ?10.10.0.115?) (bryan@shatow.net@10.10.0.115) by sweb.xzibition.com with ESMTPA; 10 Nov 2012 13:21:52 -0600 Message-ID: <509EA942.9060801@shatow.net> Date: Sat, 10 Nov 2012 13:21:38 -0600 From: Bryan Drewery User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Chris Rees Subject: Re: ZFS can't delete files when over quota References: <509E79C7.10300@shatow.net> In-Reply-To: X-Enigmail-Version: 1.4.5 OpenPGP: id=3C9B0CF9; url=http://www.shatow.net/bryan/bryan.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 19:21:55 -0000 On 11/10/2012 12:55 PM, Chris Rees wrote: > Bryan, > > Please try the patch at [1]; if it works I'll document it. > > Chris > > [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff > Hmm, I'm not a fan of -T. I think it should just work out-of-the-box here. Something like: http://people.freebsd.org/~bdrewery/rm-quota.txt Bryan From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 19:41:00 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 DE9B343C; Sat, 10 Nov 2012 19:41:00 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8ACBD8FC12; Sat, 10 Nov 2012 19:41:00 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so6386816oag.13 for ; Sat, 10 Nov 2012 11:41:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WGwtkNNkjMV0HJw9YdjJ3gZRO8iQ91DDdNh6+NGb2pQ=; b=tlkKOJCRKHjXeq6LzYVsvXHOx0VHdwcxBy2ggtzAZd68AjRS8frX7Ry1kvMXM2H//C UzQMvXOHHVqlY7EcBwMtqqBSTQ/LYYF154oU+tUGiV+DZzubmrGnFyVdZwrh8d+IpuRo 2E0Dy39UyOupc9EihYT9R9tS0ZsckrTtISihEI5Atq+8KWcWFaKOaZfTe5dedDoDTRqG 0KyMA8iGBaVQrGtOCL6Usqmwds5/SK5fi9D5mdVweKw+hSgJ5tlUjIpsmPju8mAaGjNE fJfqeDeS+4jx+zT1JYQZwmUqxySYcCQZvB3+BnA17Qi/59WrISYP7xYkLsJDg5JJhR7b k5UA== MIME-Version: 1.0 Received: by 10.60.170.114 with SMTP id al18mr11210361oec.56.1352576459961; Sat, 10 Nov 2012 11:40:59 -0800 (PST) Received: by 10.76.143.33 with HTTP; Sat, 10 Nov 2012 11:40:59 -0800 (PST) In-Reply-To: <509EA942.9060801@shatow.net> References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> Date: Sat, 10 Nov 2012 11:40:59 -0800 Message-ID: Subject: Re: ZFS can't delete files when over quota From: Garrett Cooper To: Bryan Drewery Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 19:41:00 -0000 On Sat, Nov 10, 2012 at 11:21 AM, Bryan Drewery wrote: > On 11/10/2012 12:55 PM, Chris Rees wrote: > > Bryan, > > > > Please try the patch at [1]; if it works I'll document it. > > > > Chris > > > > [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff > > > > Hmm, I'm not a fan of -T. I think it should just work out-of-the-box here. > > Something like: > > http://people.freebsd.org/~bdrewery/rm-quota.txt > +1. FWIW, I find it interesting that EDQUOT isn't listed in the unlink(2) documentation under ERRORS. Should this be another error? Thanks! -Garrett From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 19:48:11 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 2D8B250A; Sat, 10 Nov 2012 19:48:11 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 54FBE8FC08; Sat, 10 Nov 2012 19:48:10 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id 16so3339075wgi.31 for ; Sat, 10 Nov 2012 11:48:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=coIQdeRaDMsnJWm/8CZYRGvD4hszI8lAtMNPoAy1rAM=; b=pXhEIY/Efv4KpR+SPczloy9Vx/26x7gmbBwMgWdSuJTpRRZ8qyvRlg134Le+Irg1tw 6+37r5oav74D+/BC2K8Xqh1OzA1HHztHiI9nqx4YBWja+h1vBurKVcK0zSTkiOcH9FlG FJKg4tMVKlnQfNexW59UGiYVeFbGJRkG347I+8S7M1KYv5TOeD9zu9QJZr8vNhgyI3zJ ETZyA7DhpNTUxxaQsT9Y946Z1Vw9eZJzvdWkDsoXMoMufFzhrBxap6UYBcSSgYoi9TBU fAEejqKQXKNQ2Upzr6JvTwpkUwH4YjdqKS9M+WGtNXwYTFqOdRenGZB5hc7tcXs44eic hlBQ== Received: by 10.180.106.2 with SMTP id gq2mr8297120wib.18.1352576889334; Sat, 10 Nov 2012 11:48:09 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id gk9sm7664886wib.4.2012.11.10.11.48.08 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 10 Nov 2012 11:48:08 -0800 (PST) Date: Sat, 10 Nov 2012 20:48:00 +0100 From: Mateusz Guzik To: Bryan Drewery Subject: Re: ZFS can't delete files when over quota Message-ID: <20121110194759.GA19081@dft-labs.eu> References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <509EA942.9060801@shatow.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 19:48:11 -0000 On Sat, Nov 10, 2012 at 01:21:38PM -0600, Bryan Drewery wrote: > On 11/10/2012 12:55 PM, Chris Rees wrote: > > Bryan, > > > > Please try the patch at [1]; if it works I'll document it. > > > > Chris > > > > [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff > > > > Hmm, I'm not a fan of -T. I think it should just work out-of-the-box here. > > Something like: > > http://people.freebsd.org/~bdrewery/rm-quota.txt > I think this approach is incorrect. If you cannot rm $file due to EDQUOT, but truncate $file && rm $file works (and both patches try to do this), then I think this is a filesystem bug. -- Mateusz Guzik From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 20:03: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 B4FBD632 for ; Sat, 10 Nov 2012 20:03:03 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 325198FC08 for ; Sat, 10 Nov 2012 20:03:02 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jm19so982458bkc.13 for ; Sat, 10 Nov 2012 12:03:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ad6QPb/Olj+gdhD/GCLKNlXGe6zl8FWn4/0BAw2ttJ0=; b=Jwt5AiOWIZH1rQZcOha+3H2cWJoVoXmHdf4gY1ey8Dvn0mQ/oEYkRm7nHLD/8j7FwM 5M5NngERaQG1ximf5fL/j5JoIS2oYSbv2lpVdmp5BXmydmkfrECMl8r84K9PFItCzPdA UBBS1qDMPoPd+wXySCNrB34bz8Opr0GfTXEzCV2Face38+SFaZyNLAOLguZ4vdqJe9qn td4eYEITfYjq4YVq3RBBlTlB8ZHJXeZpn3RUV7CG+el6bJBxbrLS4WNvYy1QY15IEZN0 QXs4iomP6a/1WKj2nIucCWymOM8peeNgJY3PlwqJrvMmicp0zf0FiagikF10yrkGFfE3 Kekg== MIME-Version: 1.0 Received: by 10.204.11.208 with SMTP id u16mr1069561bku.81.1352577781635; Sat, 10 Nov 2012 12:03:01 -0800 (PST) Received: by 10.204.50.197 with HTTP; Sat, 10 Nov 2012 12:03:01 -0800 (PST) Received: by 10.204.50.197 with HTTP; Sat, 10 Nov 2012 12:03:01 -0800 (PST) In-Reply-To: <20121110194759.GA19081@dft-labs.eu> References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> <20121110194759.GA19081@dft-labs.eu> Date: Sat, 10 Nov 2012 20:03:01 +0000 Message-ID: Subject: Re: ZFS can't delete files when over quota From: Chris Rees To: Mateusz Guzik Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org, Bryan Drewery X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 20:03:03 -0000 On 10 Nov 2012 19:48, "Mateusz Guzik" wrote: > > On Sat, Nov 10, 2012 at 01:21:38PM -0600, Bryan Drewery wrote: > > On 11/10/2012 12:55 PM, Chris Rees wrote: > > > Bryan, > > > > > > Please try the patch at [1]; if it works I'll document it. > > > > > > Chris > > > > > > [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff > > > > > > > Hmm, I'm not a fan of -T. I think it should just work out-of-the-box here. > > > > Something like: > > > > http://people.freebsd.org/~bdrewery/rm-quota.txt > > > > I think this approach is incorrect. > > If you cannot rm $file due to EDQUOT, but truncate $file && rm $file > works (and both patches try to do this), then I think this is a filesystem bug. Quite right, but this has been a known issue in ZFS for a while, without a forthcoming fix. I'll do some grovelling in the zfs code tomorrow, wish me luck-- I don't expect to be productive. Chris From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 20:29: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 B0467A3F for ; Sat, 10 Nov 2012 20:29:51 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 60FA38FC0A for ; Sat, 10 Nov 2012 20:29:50 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so9650580iea.13 for ; Sat, 10 Nov 2012 12:29:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dragondata.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=bUt6aJMQ7IlxpYz6BgstXMubAZkBz0xA4MQKDvkFI9k=; b=Fd9fZJlx4drKxSJpnoDIp5ZfwgSvTl06Vm/sVHH20yPYdol9rGZ807lIWdnEUQtK+G y8thhWTsohtk13ZsNwjfxo5RdK/jdXIw04XzFsWG9i8has/xzV+jW8p006hqpu7lfxW4 BUptRFoqeo8yWOZuEKd31jd9PejSHh/XFku2w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=bUt6aJMQ7IlxpYz6BgstXMubAZkBz0xA4MQKDvkFI9k=; b=gMX/cH0yhgbYx1FRp8hnvb/I1ofdBiapMpLynQfS/wZYIyv6GV6Y45GUXOCZUz0ovl 1WSD8oZxhBI8pymtMF7F81ZhTInKdxOzUt/jymQ8+VlvowvN1gKXAaNPINU4HjkmIrhR 7FzogAOIswCw47z1r3rljnEHik7VJE2bJa7NPn3TzCLFnxsH5zY0qni8Tx4+oruDCVHM +gRAKlq0EgN51Qjjpqnk2VdWDbAVWGyT4WQ5ZVjpyoIXh9YLTB1Ij8Cmfe4dLtQbNrMD lYUGY66HnaBFmezEOtkGJ1GlzuWUOr1HVoFFfoikn5z5Q7bxovxQEc/Yp6M7K4ZxwBYC JUmA== Received: by 10.50.213.99 with SMTP id nr3mr4121202igc.16.1352579390419; Sat, 10 Nov 2012 12:29:50 -0800 (PST) Received: from unassigned.v6.your.org ([2001:4978:1:45:15a1:f03b:726b:c856]) by mx.google.com with ESMTPS id kp4sm2075142igc.1.2012.11.10.12.29.48 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 10 Nov 2012 12:29:49 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: ZFS can't delete files when over quota From: Kevin Day In-Reply-To: <509EA942.9060801@shatow.net> Date: Sat, 10 Nov 2012 14:29:46 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <67C1C89F-4A91-4595-8EA7-19AF3EC4656F@dragondata.com> References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> To: Bryan Drewery X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQnBnJQCOkGHYrz+nVyxHT8OQdvfr+reVLAtEcsB9DF7pbwTadkLkr2Yb3mYjMxl6tONnCS/ Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 20:29:52 -0000 On Nov 10, 2012, at 1:21 PM, Bryan Drewery wrote: > On 11/10/2012 12:55 PM, Chris Rees wrote: >> Bryan, >>=20 >> Please try the patch at [1]; if it works I'll document it. >>=20 >> Chris >>=20 >> [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff >>=20 >=20 > Hmm, I'm not a fan of -T. I think it should just work out-of-the-box = here. >=20 > Something like: >=20 > http://people.freebsd.org/~bdrewery/rm-quota.txt >=20 > Bryan This also may cause unintended or weird behavior with regard to = open/running binaries or processes that want to keep a file open. If you're trying to rm a binary that's currently in use, this is = normally a supported feature. Old copies of the binary keep running and = the disk space isn't actually freed until after everything holding the = old version exits. With the patch, truncate will fail with ETXTBSY. = Having rm fail with ETXTBSY is probably wrong. Programs are also allowed to keep reading/writing to a file that another = process has unlinked. Unlinking a file is not supposed to destroy the = contents of it until after everyone is done with it. Throwing a truncate = in there changes that behavior. I realize this is only happening under already broken circumstances, but = changing unlink to occasionally doing unlink-truncate-unlink is going to = make some hard to debug situations occur. Also, you need to be testing errno =3D=3D EDQUOT, not rval. -- Kevin From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 20:36: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 8DB72C96 for ; Sat, 10 Nov 2012 20:36:19 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 46A4C8FC08 for ; Sat, 10 Nov 2012 20:36:18 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so6413528oag.13 for ; Sat, 10 Nov 2012 12:36:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hqN78dtA5NWeT7rMohuGw/9qDXkWpWexxMnkU7m7xcs=; b=RCWHoy/kwEk/nBigkaIZOWj44MAmbbZHn2Qyg4vKhQ5AqI5UeQFvipyhm857rsUcyI EeZkbYeLRBs9v2oI087hJimyIi6yFBO8kXlbzOQOq/05BpNZBFwEds8nPpwUvY23r5Qv y9aJ6skoLNlOvYmie22oqY/03FQSh1QCbUzBGnSR4c90PvsIEd3WtipmqQdNXyWWBccm 6jsxZYsFcrMK3Ldo/DY/doHYmO0Owhr1G2XpZmAx1Qr0APRDt6VI5mF9XcplEgw6PK/T /zbT2z2tU0h/SslL29MNnSd7xyFJsNqkK3C7nE9AJRAQCaHkCLDqh6tMDE6BlQE3V1B7 s5og== MIME-Version: 1.0 Received: by 10.60.32.137 with SMTP id j9mr11373835oei.133.1352579778397; Sat, 10 Nov 2012 12:36:18 -0800 (PST) Received: by 10.76.143.33 with HTTP; Sat, 10 Nov 2012 12:36:18 -0800 (PST) In-Reply-To: <67C1C89F-4A91-4595-8EA7-19AF3EC4656F@dragondata.com> References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> <67C1C89F-4A91-4595-8EA7-19AF3EC4656F@dragondata.com> Date: Sat, 10 Nov 2012 12:36:18 -0800 Message-ID: Subject: Re: ZFS can't delete files when over quota From: Garrett Cooper To: Kevin Day Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-fs@freebsd.org" , Bryan Drewery X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 20:36:19 -0000 On Sat, Nov 10, 2012 at 12:29 PM, Kevin Day wrote: > > On Nov 10, 2012, at 1:21 PM, Bryan Drewery wrote: > > > On 11/10/2012 12:55 PM, Chris Rees wrote: > >> Bryan, > >> > >> Please try the patch at [1]; if it works I'll document it. > >> > >> Chris > >> > >> [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff > >> > > > > Hmm, I'm not a fan of -T. I think it should just work out-of-the-box > here. > > > > Something like: > > > > http://people.freebsd.org/~bdrewery/rm-quota.txt > > > > Bryan > > > This also may cause unintended or weird behavior with regard to > open/running binaries or processes that want to keep a file open. > > If you're trying to rm a binary that's currently in use, this is normally > a supported feature. Old copies of the binary keep running and the disk > space isn't actually freed until after everything holding the old version > exits. With the patch, truncate will fail with ETXTBSY. Having rm fail with > ETXTBSY is probably wrong. > > Programs are also allowed to keep reading/writing to a file that another > process has unlinked. Unlinking a file is not supposed to destroy the > contents of it until after everyone is done with it. Throwing a truncate in > there changes that behavior. > > I realize this is only happening under already broken circumstances, but > changing unlink to occasionally doing unlink-truncate-unlink is going to > make some hard to debug situations occur. > > Also, you need to be testing errno == EDQUOT, not rval. > Yes. unlink(...) == -1 && errno == EDQUOT From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 20:37: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 10DB2E22 for ; Sat, 10 Nov 2012 20:37:06 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 875B48FC12 for ; Sat, 10 Nov 2012 20:37:05 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jm19so986864bkc.13 for ; Sat, 10 Nov 2012 12:37:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=s3DhBzZhY78lxgky5EVXIsLS45CQ9MruaiiiuMQJlNM=; b=WeQTON0AR8qYFDQ8bcwjG59KZNEY6YGqU91p+b3hXiIeb5Z/dRthRYJmSkWhLfa6mX lr8MprfrIxRjJlLE8l7RbtFQ3RDk5HFlxDGagSiXbGC9B6lcrjmX3OHOo03mQ+SI0oCo rVd0qVKZkzB5hyP/fUX2a/QuE5LTMJsRhZZYZGYB31TCtAuhDBfYPmlZXmr5dGbClzu/ yn8yoF+Tm6aO8ehTzVJuIrIu4+untTy9fHl3GWho4tAS5ecKsedGXVBgc27w/GaYQbwF wrp9fFqaWPCgWIju4OnRLkXrzjkkXAYM0qj3yBX9IRmhsceQ75pOx5UKaMKho1ArrMrF w+Vg== Received: by 10.204.11.208 with SMTP id u16mr1093130bku.81.1352579824452; Sat, 10 Nov 2012 12:37:04 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.50.197 with HTTP; Sat, 10 Nov 2012 12:36:34 -0800 (PST) In-Reply-To: <67C1C89F-4A91-4595-8EA7-19AF3EC4656F@dragondata.com> References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> <67C1C89F-4A91-4595-8EA7-19AF3EC4656F@dragondata.com> From: Chris Rees Date: Sat, 10 Nov 2012 20:36:34 +0000 X-Google-Sender-Auth: xrO0xUvyDOu77ewt79guDT7YCy0 Message-ID: Subject: Re: ZFS can't delete files when over quota To: Kevin Day Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-fs@freebsd.org" , Bryan Drewery X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 20:37:06 -0000 On 10 November 2012 20:29, Kevin Day wrote: > > On Nov 10, 2012, at 1:21 PM, Bryan Drewery wrote: > >> On 11/10/2012 12:55 PM, Chris Rees wrote: >>> Bryan, >>> >>> Please try the patch at [1]; if it works I'll document it. >>> >>> Chris >>> >>> [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff >>> >> >> Hmm, I'm not a fan of -T. I think it should just work out-of-the-box her= e. >> >> Something like: >> >> http://people.freebsd.org/~bdrewery/rm-quota.txt >> >> Bryan > > > This also may cause unintended or weird behavior with regard to open/runn= ing binaries or processes that want to keep a file open. > > If you're trying to rm a binary that's currently in use, this is normally= a supported feature. Old copies of the binary keep running and the disk sp= ace isn't actually freed until after everything holding the old version exi= ts. With the patch, truncate will fail with ETXTBSY. Having rm fail with ET= XTBSY is probably wrong. > > Programs are also allowed to keep reading/writing to a file that another = process has unlinked. Unlinking a file is not supposed to destroy the conte= nts of it until after everyone is done with it. Throwing a truncate in ther= e changes that behavior. > > I realize this is only happening under already broken circumstances, but = changing unlink to occasionally doing unlink-truncate-unlink is going to ma= ke some hard to debug situations occur. > > Also, you need to be testing errno =3D=3D EDQUOT, not rval. These are the reasons I added the -T option, which I realise would have been more correct as -t; it's undesirable to have as default behaviour. In my patch, errno is tested. Chris From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 21:00:11 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 8E252119 for ; Sat, 10 Nov 2012 21:00:11 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 176E98FC0C for ; Sat, 10 Nov 2012 21:00:10 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id x43so2839209wey.13 for ; Sat, 10 Nov 2012 13:00:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=b0SpiCs3jQYRIYjHmURzAfeJiJbH2Ul/xwleAer+Ils=; b=QWwScYE0UVWFL+WGB/dLSGPBF077V9ElfBdI9qV1g5rjkhAkJ2dsQ2m+49mg++fuPo SNvkd6xFUlyWSVjGmdlJzNUc9Qa+Aw1ZmGa6rLX2boKTXljHNmdKmcqqjNzVzw6jajTg xcT6FdXAsEFx3Gd0cdkKT9KvyMZn/yLRqbtNy71MsPM1Stts3NNfTeIBg1NK3JqMhVfj CDoWpJWvxFhigm9oq/Bw/nDiB5T/fj8m9Oq6TDiOnJiHQLRDfZAaLb0imnCDIqXtI4tj X/QCV1yf0MSfbmF4MpKCWbDI2kTDP2Fqqc00AQUjyKcCONt0E3WQOOl6Af65szAZqaet o2Gw== Received: by 10.216.212.225 with SMTP id y75mr6255153weo.39.1352581209812; Sat, 10 Nov 2012 13:00:09 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id r10sm4113610wiz.0.2012.11.10.13.00.08 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 10 Nov 2012 13:00:09 -0800 (PST) Date: Sat, 10 Nov 2012 22:00:00 +0100 From: Mateusz Guzik To: Chris Rees Subject: Re: ZFS can't delete files when over quota Message-ID: <20121110210000.GB19081@dft-labs.eu> References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> <20121110194759.GA19081@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org, Bryan Drewery X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 21:00:11 -0000 On Sat, Nov 10, 2012 at 08:03:01PM +0000, Chris Rees wrote: > On 10 Nov 2012 19:48, "Mateusz Guzik" wrote: > > > > On Sat, Nov 10, 2012 at 01:21:38PM -0600, Bryan Drewery wrote: > > > On 11/10/2012 12:55 PM, Chris Rees wrote: > > > > Bryan, > > > > > > > > Please try the patch at [1]; if it works I'll document it. > > > > > > > > Chris > > > > > > > > [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff > > > > > > > > > > Hmm, I'm not a fan of -T. I think it should just work out-of-the-box > here. > > > > > > Something like: > > > > > > http://people.freebsd.org/~bdrewery/rm-quota.txt > > > > > > > I think this approach is incorrect. > > > > If you cannot rm $file due to EDQUOT, but truncate $file && rm $file > > works (and both patches try to do this), then I think this is a > filesystem bug. > > Quite right, but this has been a known issue in ZFS for a while, without a > forthcoming fix. > > I'll do some grovelling in the zfs code tomorrow, wish me luck-- I don't > expect to be productive. > In this case the right fix (whatever it is) may be really non-trivial. I'm in mood for ugly hacks, so: You can think of a workardound in the kernel. If removal fails with EDQUOT and you can guarantee that no thread has this file opened and truncation will allow removal to succeed, you truncate and remove. Determining whether truncation will be able to help (and making sure that these conditions hold until removal is finised) may be non-trivial as well. But I doubt something like this could be accepted. :) My point is that even if this problem persists, changing tools in the basesystem to cope is a bad idea. If you are happy with only rm being able to cope, you can wrap/alias it on your machines. -- Mateusz Guzik From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 21:24:09 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 6DB70717 for ; Sat, 10 Nov 2012 21:24:09 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 25EE78FC08 for ; Sat, 10 Nov 2012 21:24:08 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id wc20so6455429obb.13 for ; Sat, 10 Nov 2012 13:24:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5DxWrY517cqz658dsjUXzCQAmj1SDSXEanWyfkMCgyU=; b=eIQwJjVqL+LHwLKh9RvwordmMtllmmRI4yxOUtTC88kA6GtMZTsV477GwmQq0/xMof 3FmdOBk+5xtumFtC50iTQRH+1OuDyumDt4ACRMM1Hq6YW+rgwJq2pR6ziRGh9g5DnY3J VeB3rsm+wup17Lar0WJOj9a/xzoHFkRezpZYaRnaPDL5vmpeTILoQ920LK+6QZtvIgxl aY4jeiXLCRdUhHS1Wc+m3keyQvQ3mWhlLf9ih3cTcR47CxEvi5nF+BlWTpffzgUlSdt1 zsIC7njLZf9hZFAJEMQpijFhD6LYC3VX0KuIbMuZuJMfkiCpZOfFstrkkUjkLixVmyYN TotQ== MIME-Version: 1.0 Received: by 10.182.197.8 with SMTP id iq8mr3756727obc.66.1352582648356; Sat, 10 Nov 2012 13:24:08 -0800 (PST) Received: by 10.76.143.33 with HTTP; Sat, 10 Nov 2012 13:24:08 -0800 (PST) In-Reply-To: <20121110210317.GC19081@dft-labs.eu> References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> <20121110194759.GA19081@dft-labs.eu> <20121110210317.GC19081@dft-labs.eu> Date: Sat, 10 Nov 2012 13:24:08 -0800 Message-ID: Subject: Re: ZFS can't delete files when over quota From: Garrett Cooper To: Mateusz Guzik Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 21:24:09 -0000 On Sat, Nov 10, 2012 at 1:03 PM, Mateusz Guzik wrote: > On Sat, Nov 10, 2012 at 11:55:14AM -0800, Garrett Cooper wrote: > > On Sat, Nov 10, 2012 at 11:48 AM, Mateusz Guzik > wrote: > > > > > On Sat, Nov 10, 2012 at 01:21:38PM -0600, Bryan Drewery wrote: > > > > On 11/10/2012 12:55 PM, Chris Rees wrote: > > > > > Bryan, > > > > > > > > > > Please try the patch at [1]; if it works I'll document it. > > > > > > > > > > Chris > > > > > > > > > > [1] http://www.bayofrum.net/~crees/patches/bdrewery.diff > > > > > > > > > > > > > Hmm, I'm not a fan of -T. I think it should just work out-of-the-box > > > here. > > > > > > > > Something like: > > > > > > > > http://people.freebsd.org/~bdrewery/rm-quota.txt > > > > > > > > > > I think this approach is incorrect. > > > > > > If you cannot rm $file due to EDQUOT, but truncate $file && rm $file > > > works (and both patches try to do this), then I think this is a > filesystem > > > bug. > > > > > > > Perhaps. This is kind of an implementation/compatibility issue because of > > how ZFS (and other COW-based FSes) work. > > Except this is not about being unable to rm because of EDQUOT (whether > ZFS can do something about that or not I have no idea). This is about being > able to remove just after truncation, which clearly shows that zfs can in > principle remove this file on its own. > You're probably right. My guess is that the fix would be to ignore EDQUOT in the unlink VOP handler. Thanks, -Garrett From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 22:32: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 74C8D56A for ; Sat, 10 Nov 2012 22:32:59 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 0373A8FC08 for ; Sat, 10 Nov 2012 22:32:58 +0000 (UTC) Received: from server.rulingia.com (c220-239-241-202.belrs5.nsw.optusnet.com.au [220.239.241.202]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id qAAMWupG059984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 11 Nov 2012 09:32:56 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id qAAMWotV096126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 11 Nov 2012 09:32:50 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id qAAMWnrF096121 for freebsd-fs@freebsd.org; Sun, 11 Nov 2012 09:32:49 +1100 (EST) (envelope-from peter) Date: Sun, 11 Nov 2012 09:32:49 +1100 From: Peter Jeremy To: freebsd-fs@freebsd.org Subject: zfs diff deadlock Message-ID: <20121110223249.GB506@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0ntfKIWw70PvrIHh" Content-Disposition: inline X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 22:32:59 -0000 --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I recently decided to do a "zfs diff" between two snapshots to try and identify why there was so much "USED" space in the snapshot. The diff ran for a while (though with very little IO) but has now wedged unkillably. There's nothing on the console or in any logs, the pool reports no problems and there are no other visible FS issues. Any ideas on tracking this down? root@server:/root # ps -lp 53146 UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 53146 53092 0 76 0 18096 948 ffffff0149cc6100 D+ 33 4:18.= 76 zfs diff -F tank/beckett/home@20121108 tank/beckett/home@20121109 root@server:/root # procstat -kk 53146 PID TID COMM TDNAME KSTACK = =20 53146 100490 zfs - mi_switch+0x18e sleepq_wait+= 0x44 _sx_slock_hard+0x22c _sx_slock+0x7a zap_get_leaf_byblk+0xbd zap_deref_= leaf+0x68 fzap_cursor_retrieve+0xe7 zap_cursor_retrieve+0x155 zap_value_sea= rch+0x7f zfs_obj_to_path_impl+0x292 zfs_obj_to_stats+0x175 zfs_ioc_obj_to_s= tats+0x7e zfsdev_ioctl+0xe6 devfs_ioctl_f+0x7a kern_ioctl+0xb6 ioctl+0xf0 a= md64_syscall+0x109 Xfast_syscall+0xfc=20 53146 100643 zfs initial thread mi_switch+0x18e sleepq_catch= _signals+0x247 sleepq_wait_sig+0x16 _sleep+0x2be pipe_write+0x6c8 write_rec= ord+0x79 diff_cb+0x166 traverse_visitbp+0x21c traverse_visitbp+0x316 traver= se_visitbp+0x316 traverse_visitbp+0x316 traverse_visitbp+0x316 traverse_vis= itbp+0x316 traverse_visitbp+0x316 traverse_dnode+0x7c traverse_visitbp+0x48= c traverse_impl+0x188 traverse_dataset+0x32=20 root@server:/root # zpool status tank pool: tank state: ONLINE scan: resilvered 1.58G in 0h10m with 0 errors on Tue Oct 30 06:55:29 2012 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 ada2p5 ONLINE 0 0 0 ada3p5 ONLINE 0 0 0 ada1p5 ONLINE 0 0 0 ada5p5 ONLINE 0 0 0 ada0p5 ONLINE 0 0 0 ada4p5 ONLINE 0 0 0 logs ada6p3 ONLINE 0 0 0 cache ada6p4 ONLINE 0 0 0 errors: No known data errors The systems is running a 4-month old 8-stable (r237444) --=20 Peter Jeremy --0ntfKIWw70PvrIHh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCe1hEACgkQ/opHv/APuIc8cgCeM46iryYjF5fu86dHSlptsm9p 47UAoMC43Ujh6w51gsXNk5mKF367zFUN =dEyt -----END PGP SIGNATURE----- --0ntfKIWw70PvrIHh-- From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 23:06:25 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 830DCA76 for ; Sat, 10 Nov 2012 23:06:25 +0000 (UTC) (envelope-from prvs=1661e47a27=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 0DAFD8FC13 for ; Sat, 10 Nov 2012 23:06:24 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50001015282.msg for ; Sat, 10 Nov 2012 23:06:15 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 10 Nov 2012 23:06:15 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1661e47a27=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Garrett Cooper" , "Mateusz Guzik" References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> <20121110194759.GA19081@dft-labs.eu> <20121110210317.GC19081@dft-labs.eu> Subject: Re: ZFS can't delete files when over quota Date: Sat, 10 Nov 2012 23:06:21 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 23:06:25 -0000 ----- Original Message ----- From: "Garrett Cooper" >> Except this is not about being unable to rm because of EDQUOT (whether >> ZFS can do something about that or not I have no idea). This is about being >> able to remove just after truncation, which clearly shows that zfs can in >> principle remove this file on its own. >> > > You're probably right. My guess is that the fix would be to ignore > EDQUOT in the unlink VOP handler. The CoW nature of ZFS causes this issue, which is why UFS doesn't have this problem. Unfortunately given ZFS's snapshots there's no guarantee that truncating the file will result in enough free space to perform the unlink. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 23:59:14 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7923ED6 for ; Sat, 10 Nov 2012 23:59:14 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8B0848FC08 for ; Sat, 10 Nov 2012 23:59:14 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id wc20so6519338obb.13 for ; Sat, 10 Nov 2012 15:59:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Fjans/yCU0S4Or0oBMY1Qlqlulzz4JY6sxax5tbGUWY=; b=WBOm14jyNNpgz/y9VTZbksbhlUpREMpgSmgAm2usThXwLVCO7yDjYIcCyEve/lvXnB tXni9rFSrJXJAHNXtQLHeSrlCybji4p0LQR8r0DyKmsSLeExVKij1mN6xg7ZNOCZTz+N m6NQama20vkqLo0EqVh2qDrm0G15oRGjAUKCuP+f0W3f/bkAmnnoe6lyZnI9Lg7EAfvX 59COTH0VgHkxY5RkIwriApZli3AtaKs9P47bs0GhMB2X6aC1ErkHrXpm8rkHusZKlLAp GyFJck8dMNjPPPiyU3TBoJW5NhuKMxg4DycTHV6oCMgnz1q/XZIEYZ/Ll7p/aF59S+jC akDA== MIME-Version: 1.0 Received: by 10.60.11.68 with SMTP id o4mr8772043oeb.89.1352591948319; Sat, 10 Nov 2012 15:59:08 -0800 (PST) Received: by 10.76.68.39 with HTTP; Sat, 10 Nov 2012 15:59:08 -0800 (PST) Date: Sat, 10 Nov 2012 18:59:08 -0500 Message-ID: Subject: ZFS can't delete files when over quota From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 23:59:14 -0000 NAME USED AVAIL REFER MOUNTPOINT tank/distfiles 10.0G 0 25K /tank/distfiles NAME PROPERTY VALUE tank/distfiles quota 10G What is your free in 'zpool list tank'? Because of CoW for metadata, I think it makes sense that your tank/distfiles won't rm within your used up 10G limit there. What if you raise the distfiles limit to use more of tank? What if you rollback distfiles? And consider using per user/group quotas so root can still rm in tank/distfiles [1]. [1] Sure, ZFS arguably should make internal reserved space to allow rm (the effective metadata). Question is, how much, what dynamic metrics for that? Maybe ZFS feel admin still has some responsibility. But you really don't want to take a user ticket because they can't manage their own rm as under other file systems. What is the state of this in current Solaris?