From owner-freebsd-fs@FreeBSD.ORG Sun Aug 7 07:32:37 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 140FA106564A for ; Sun, 7 Aug 2011 07:32:37 +0000 (UTC) (envelope-from ttsestt@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9C5CC8FC0C for ; Sun, 7 Aug 2011 07:32:36 +0000 (UTC) Received: by fxe4 with SMTP id 4so1325695fxe.13 for ; Sun, 07 Aug 2011 00:32:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:subject:references:date:message-id:user-agent:mime-version :content-type:content-transfer-encoding; bh=vqKk9BP8Yl5uAkFCQUQ9h3YEai0pAlE/5zovvN5PUuo=; b=rZeknNiXxpk1zzSkJF9JBzDCT1aae5CRPul2cBWBTERvOJ4V+H5j/vG7k/h1w0Ss0T xYfIkLofVFHwdXVWpPQhQSTXd1bW4pWdzjKwj0aXyD4fg330hEYgRUNcgB1stHjq2Xdc DnfJLb1oPwrm86VTZRi6FhLtDH8klH2k+h/P4= Received: by 10.204.18.13 with SMTP id u13mr274094bka.83.1312700467479; Sun, 07 Aug 2011 00:01:07 -0700 (PDT) Received: from localhost (raskin.torservers.net [74.120.15.150]) by mx.google.com with ESMTPS id m25sm1123084bks.15.2011.08.07.00.01.05 (version=SSLv3 cipher=OTHER); Sun, 07 Aug 2011 00:01:06 -0700 (PDT) From: Test Rat To: freebsd-fs@freebsd.org References: Date: Sun, 07 Aug 2011 11:00:59 +0400 Message-ID: <867h6pemdw.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: kern.geom.debugflags=16 does NOT allow me to write to device X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2011 07:32:37 -0000 Peter Schuller writes: [...] > In addition, geom(4) still has: > > 0x10 (allow foot shooting) > Allow writing to Rank 1 providers. This would, for example, > allow the super=E2=80=90user to overwrite the MBR on the roo= t disk or > write random sectors elsewhere to a mounted disk. The impli= ca=E2=80=90 > tions are obvious. > > In addition, geom/geom_subr.c has: > > /* If foot-shooting is enabled, any open on rank#1 is OK */ > if ((g_debugflags & 16) && pp->geom->rank =3D=3D 1) > ; > > I wonder if the problem is that it's not of rank 1 because I'm writing > to the slice's first second rather than the MBR... That's now feeling > pretty likely and can perhaps explain lots of confusion that seems to > exist based on Googling. [...] The issue still seems unanswered. For example, this guide http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition silently avoids explaining why zroot on MBR & BSD should be exported. If gpart is ever fixed I still think shooting the foot on rank > 1 is useful for things like testing FS for corruption without accidentally destroying partition table if operating on rank =3D=3D 1. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 7 22:47:47 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6061B106566C for ; Sun, 7 Aug 2011 22:47:47 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 20EE88FC08 for ; Sun, 7 Aug 2011 22:47:46 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap0EAIQVP06DaFvO/2dsb2JhbABChEejZYFqBFI1Ag0ZAl+xHJALgSuEC4EQBJMCkQQ X-IronPort-AV: E=Sophos;i="4.67,334,1309752000"; d="scan'208";a="130299992" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 07 Aug 2011 18:47:46 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 5922EB3F0A; Sun, 7 Aug 2011 18:47:46 -0400 (EDT) Date: Sun, 7 Aug 2011 18:47:46 -0400 (EDT) From: Rick Macklem To: FreeBSD FS Message-ID: <1687823014.1491995.1312757266327.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Linux)/6.0.10_GA_2692) Cc: onwahe@gmail.com Subject: NFS calculation of max commit size X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2011 22:47:47 -0000 A recent PR (kern/159351) noted that the following calculation results in a divide-by-zero when desiredvnodes < 1000. nmp->nm_wcommitsize = hibufspace / (desiredvnodes / 1000); Just fixing the divide-by-zero is easy enough, but I'm not sure what this calculation is trying to do. Making it a fraction of "hibufspace" makes sense (nm_wcommitsize is the maximum # of bytes of uncommitted data in the NFS client's buffer cache blocks, if I understand it correctly), but why divide it by (desiredvnodes / 1000) ?? Maybe thinking that fewer vnodes means sharing it with fewer other file systems or ??? Anyhow, it seems to me that the formulae is bogus for small values of desiredvnodes (for example desiredvnodes == 1500 implies nm_wcommitsize == hibufspace, which sounds too large to me). I'm thinking that putting an upper limit of 10% of hibufspace might make sense. ie. Change the above to: if (desiredvnodes >= 11000) nmp->nm_wcommitsize = hibufspace / (desiredvnodes / 1000); else nmp->nm_wcommitsize = hibufspace / 10; Anyone have comments or insight into this calculation? rick ps: jhb, I hope you don't mind. I emailed you first and then thought others might have some ideas, too. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 8 11:07:03 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93639106564A for ; Mon, 8 Aug 2011 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 810D78FC1C for ; Mon, 8 Aug 2011 11:07:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p78B73Vi078531 for ; Mon, 8 Aug 2011 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p78B72Ke078529 for freebsd-fs@FreeBSD.org; Mon, 8 Aug 2011 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Aug 2011 11:07:02 GMT Message-Id: <201108081107.p78B72Ke078529@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2011 11:07:03 -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/159418 fs [tmpfs] [panic] tmpfs kernel panic: recursing on non r 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/159233 fs [ext2fs] [patch] fs/ext2fs: finish reallocblk implemen o kern/159232 fs [ext2fs] [patch] fs/ext2fs: merge ext2_readwrite into 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] amd(8) ICMP storm and unkillable process. o kern/158711 fs [ffs] [panic] panic in ffs_blkfree and ffs_valloc o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157728 fs [zfs] zfs (v28) incremental receive may leave behind t o kern/157722 fs [geli] unable to newfs a geli encrypted partition 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/156933 fs [zfs] ZFS receive after read on readonly=on filesystem 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/156168 fs [nfs] [panic] Kernel panic under concurrent access ove 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 o 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 o kern/154447 fs [zfs] [panic] Occasional panics - solaris assert somew 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/153847 fs [nfs] [panic] Kernel panic from incorrect m_free in nf o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small p kern/152488 fs [tmpfs] [patch] mtime of file updated when only inode 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 kern/151845 fs [smbfs] [patch] smbfs should be upgraded to support Un 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/150207 fs zpool(1): zpool import -d /dev tries to open weird dev 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 bin/148296 fs [zfs] [loader] [patch] Very slow probe in /usr/src/sys o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/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 o bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133174 fs [msdosfs] [patch] msdosfs must support multibyte inter 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 f kern/130133 fs [panic] [zfs] 'kmem_map too small' caused by make clea 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 f kern/127375 fs [zfs] If vm.kmem_size_max>"1073741823" then write spee 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 f kern/126703 fs [panic] [zfs] _mtx_lock_sleep: recursed on non-recursi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files f sparc/123566 fs [zfs] zpool import issue: EOVERFLOW o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 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 f kern/120210 fs [zfs] [panic] reboot after panic: solaris assert: arc_ o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash 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 244 problems total. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 9 01:51:40 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97B951065673 for ; Tue, 9 Aug 2011 01:51:40 +0000 (UTC) (envelope-from mailreturn@smtp.ymlp15.net) Received: from smtp.ymlp15.net (smtp.ymlp15.net [87.237.8.246]) by mx1.freebsd.org (Postfix) with SMTP id 8F9B08FC15 for ; Tue, 9 Aug 2011 01:51:39 +0000 (UTC) Received: (qmail 24450 invoked by uid 0); 9 Aug 2011 01:49:18 -0000 Date: Tue, 9 Aug 2011 03:49:18 +0200 To: fs@freebsd.org From: PROJECT MANAGEMENT COMPETENCE Message-ID: <1150bf4fbdb20c68b56e96e37466934d@smtp.ymlp15.net> X-YMLPcode: p82a+2399+322236 MIME-Version: 1.0 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Training on "PROJECT MANAGEMENT" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: invitation@thewodia.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 01:51:40 -0000 --------------------------------------------------------------------------= ------ This email newsletter was sent to you in graphical HTML format. If you're seeing this version, your email program prefers plain text = emails. You can read the original version online: http://ymlp125.com/zSsUTp --------------------------------------------------------------------------= ------ WODIA Training Institute (WOTI) Management Training andSkills Development The Boat House, 21, Ogunnusi Road, Ogba, Ikeja, Lagos.www.thewodia.org/woti.html ( http://www.thewodia.org/woti.html ), Email : support@thewodia.org,invitation@thewodia.org Telephone : +234 802 307 9485, +234 813 375 4358 INVITATION TOTRAINING PROGRAM ON PROJECT MANAGEMENT Investment in People- TOPIC: PROJECT MANAGEMENT Date : AUGUST 23-26, 2011 (4 days). Venue : WODIA Training Institute (WOTI) The Boat House, 21, Ogunnusi Road, (AVIS Petrol Station Bus-Stop), Ogba, Ikeja, Lagos. Nigeria. Fee : N60,000:00 (Sixty thousand Naira only)per Head. Fees include Tuition, Resource Materials, Writing Materials, Conference Bags, Certificateof Participation, Tea/Coffee Break , ContinentalBreakfast, Buffet Lunch, and Group Photograph. Time : 9.00a.m daily Participation:Kindly Confirm Space Availabilitybefore payment by calling +234 802 307 9485 OR +234 813 375 4358. You could also send an Email to:support@thewodia.org, invitation@thewodia.org ------------------------- Payment Instructions : After confirmation of space availability, payment should be made into any Branch of Zenith Bank PLC. account number 6011822855 in favour of WODIA Training Institute (WOTI) before program date. TRAINING DETAILS: Objectives: After the four-day Intensive Management Training Program on PROJECT MANAGEMENT, Participants will be able to : ----conduct feasibility studies, cost and initiate viable projects; ----develop the skills and knowledge needed to manage the project life cycle from Initiation to Planning through Implementation to Closing Stage; ----learn how to organize and control projects effectively, with particular emphasis on delivery of results within time, resource management, budget and quality perspective; ----create, mobilize and organise an effective and enthusiastic project team; ----understand how to use the Program Evaluation and Review Technique ( PERT) to schedule, organize , coordinate and analyze tasks involved in completing a given project; ----utilize scientific methodologies for risk assessment, project control and hazard prevention; ----acquire Effective Leadership, Team Building, Time Management and Emotional Intelligence skills required for successful Project Management; and ----enhance Human Capital Output through Effective Communication, Enthusiasm, Empathy and Positive Attitude toWork . COURSE OUTLINES : ---- Introduction to Project Management and Development- Background, Objectives, Scope, Constraints, Assumptions, Risks and Deliverables (BOSCARD) Terms of Reference. ----Project Proposal, Definitions and Reporting. ----Project Planning -Specific, Measurable, Agreed upon, Realistic and Time-based (SMART) goals. ----Implementing the Project Plan , Scope and Time Estimates- Program Evaluation and Review Technique (PERT). ----Project Costing Estimation. ----Risk Analysis and Management, Hazard Prevention, Resource and Change Control. ----Qualities of a Project Manager- Responsible, Accountable, Consulted and Informed (RACI) Matrix; Great Initiatives, Can Do Ability, Integrity, Effective Power Delegation and Competence. ----Emotional Intelligence in Project Management. ----Project Communication ( report writing, meetings, listening, brain storming and feedback). ----Project Management Leadership and Team Building Skills. ----Project Review and Benefits Realization. WHO SHOULD ATTEND: Attendanceopen to both Male and Female who are project managers, senior executives, leaders, project team members, business analysts and managers in Public, Private, Corporate, Educational and Voluntary Establishments. Accreditation : WOTI is Certified by the Centre for Management Development (CMD), Nigeria as an Accredited Management Training Institution. Resource Persons will be WOTI Training Consultants and others to be invited from the Industrial Training Fund (ITF), Centre for Management Development (CMD) and other National and International Consulting Agencies. Training Aids will include but not limited to projectors and screen, flip charts, magic boards, computers and other multi-media and audio-visual aids. Methodology will involve lecture, role play, demonstration, discussion and other methods suitable for the target audience. Program will be highly inclusive, interactive and participatory. Thanks for Reading, ------------------------- Gladys Osagie, Program Coordinator, WODIA Training Institute (WOTI), www.thewodia.org/woti.html, EMAIL : support@thewodia.org +234 802 307 9485 Forward this email to a friend ( = http://ymlp125.com/forward.php?id=3DSsUTp&e=3Dfs@freebsd.org ) _____________________________ Unsubscribe / Change Profile: = http://ymlp125.com/u.php?id=3Dgewmweugsgmeeemhgemyy Powered by YourMailingListProvider From owner-freebsd-fs@FreeBSD.ORG Tue Aug 9 13:11:07 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A98E1065670 for ; Tue, 9 Aug 2011 13:11:07 +0000 (UTC) (envelope-from jeremie@le-hen.org) Received: from smtp5-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::14]) by mx1.freebsd.org (Postfix) with ESMTP id B18A18FC0C for ; Tue, 9 Aug 2011 13:11:05 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id 294F6D480B7; Tue, 9 Aug 2011 15:10:58 +0200 (CEST) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id 13DF63723C; Tue, 9 Aug 2011 13:10:58 +0000 (UTC) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id 0ABA8A128A; Tue, 9 Aug 2011 13:10:58 +0000 (UTC) Date: Tue, 9 Aug 2011 15:10:57 +0200 From: Jeremie Le Hen To: freebsd-fs@FreeBSD.org Message-ID: <20110809131057.GA53580@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: jeremie@le-hen.org Subject: zfs mirror reads only on one disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 13:11:07 -0000 Hi, Please Cc: me when replying, as I've not subscribed. Thanks. I'm using FreeBSD 8.2-STABLE, with a mirrored ZFS pool v15: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 mirror ONLINE 0 0 0 ad10s1 ONLINE 0 0 0 ad6s1 ONLINE 0 0 0 ad6: 1907729MB at ata3-master UDMA100 SATA 3Gb/s ad10: 1907729MB at ata5-master UDMA100 SATA 3Gb/s (For those who wonder why I use a sliced disk, this is because the disks are not the same and this allows me to get the same size on each side. Besides, ZFS v15 doesn't have the autoexpand property, this is a workaround.) The mirror is correctly synchronized and when I write on it, I get the following iostat(8) output (3 seconds interval): extended device statistics device r/s w/s kr/s kw/s wait svc_t %b ad6 0.0 682.8 0.0 41593.3 16 18.7 77 ad10 0.3 686.8 21.3 41465.4 19 19.4 80 extended device statistics device r/s w/s kr/s kw/s wait svc_t %b ad6 0.0 680.9 0.0 41910.7 16 17.3 78 ad10 0.0 671.2 0.0 41228.1 16 19.6 80 However, when I read on the mirror, only ad10 is being used: extended device statistics device r/s w/s kr/s kw/s wait svc_t %b ad6 0.0 0.0 0.0 0.0 0 0.0 0 ad10 762.7 0.0 48796.7 0.0 2 1.8 82 extended device statistics device r/s w/s kr/s kw/s wait svc_t %b ad6 0.0 0.0 0.0 0.0 0 0.0 0 ad10 740.2 0.0 47373.1 0.0 1 1.9 81 extended device statistics device r/s w/s kr/s kw/s wait svc_t %b ad6 0.0 0.3 0.0 1.3 0 0.2 0 ad10 716.2 0.3 45836.0 1.3 2 1.9 82 One of my colleagues told me this was maybe an optimization of ZFS for sequentials reads, so I tried to run two reading processes in parallel, with the same unfortunate outcome. I also tried to run "cat *" in a highly populated Maildir, so I'm sure the reads are not sequential, same outcome. Do you have any idea why this happens? Thanks, -- Jeremie Le Hen Humans are born free and equal. But some are more equal than others. Coluche From owner-freebsd-fs@FreeBSD.ORG Tue Aug 9 13:52:14 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAC2A106566B for ; Tue, 9 Aug 2011 13:52:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by mx1.freebsd.org (Postfix) with ESMTP id A2F2B8FC14 for ; Tue, 9 Aug 2011 13:52:14 +0000 (UTC) Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta13.emeryville.ca.mail.comcast.net with comcast id JDq91h0031ZMdJ4ADDsAB0; Tue, 09 Aug 2011 13:52:10 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta16.emeryville.ca.mail.comcast.net with comcast id JDs91h01D1t3BNj8cDs9Ui; Tue, 09 Aug 2011 13:52:10 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E7D15102C19; Tue, 9 Aug 2011 06:52:12 -0700 (PDT) Date: Tue, 9 Aug 2011 06:52:12 -0700 From: Jeremy Chadwick To: Jeremie Le Hen Message-ID: <20110809135212.GA13334@icarus.home.lan> References: <20110809131057.GA53580@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110809131057.GA53580@felucia.tataz.chchile.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.org Subject: Re: zfs mirror reads only on one disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 13:52:14 -0000 On Tue, Aug 09, 2011 at 03:10:57PM +0200, Jeremie Le Hen wrote: > Please Cc: me when replying, as I've not subscribed. Thanks. > > I'm using FreeBSD 8.2-STABLE, with a mirrored ZFS pool v15: > > NAME STATE READ WRITE CKSUM > data ONLINE 0 0 0 > mirror ONLINE 0 0 0 > ad10s1 ONLINE 0 0 0 > ad6s1 ONLINE 0 0 0 > > ad6: 1907729MB at ata3-master UDMA100 SATA 3Gb/s > ad10: 1907729MB at ata5-master UDMA100 SATA 3Gb/s > > (For those who wonder why I use a sliced disk, this is because the disks > are not the same and this allows me to get the same size on each side. > Besides, ZFS v15 doesn't have the autoexpand property, this is a > workaround.) > > The mirror is correctly synchronized and when I write on it, I get the > following iostat(8) output (3 seconds interval): > > extended device statistics > device r/s w/s kr/s kw/s wait svc_t %b > ad6 0.0 682.8 0.0 41593.3 16 18.7 77 > ad10 0.3 686.8 21.3 41465.4 19 19.4 80 > extended device statistics > device r/s w/s kr/s kw/s wait svc_t %b > ad6 0.0 680.9 0.0 41910.7 16 17.3 78 > ad10 0.0 671.2 0.0 41228.1 16 19.6 80 > > > However, when I read on the mirror, only ad10 is being used: > > extended device statistics > device r/s w/s kr/s kw/s wait svc_t %b > ad6 0.0 0.0 0.0 0.0 0 0.0 0 > ad10 762.7 0.0 48796.7 0.0 2 1.8 82 > extended device statistics > device r/s w/s kr/s kw/s wait svc_t %b > ad6 0.0 0.0 0.0 0.0 0 0.0 0 > ad10 740.2 0.0 47373.1 0.0 1 1.9 81 > extended device statistics > device r/s w/s kr/s kw/s wait svc_t %b > ad6 0.0 0.3 0.0 1.3 0 0.2 0 > ad10 716.2 0.3 45836.0 1.3 2 1.9 82 > > > One of my colleagues told me this was maybe an optimization of ZFS for > sequentials reads, so I tried to run two reading processes in parallel, > with the same unfortunate outcome. > > I also tried to run "cat *" in a highly populated Maildir, so I'm sure > the reads are not sequential, same outcome. > > Do you have any idea why this happens? Since I have a ZFS mirror setup I can test this. Let's take a look: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ATA-8 SATA 3.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 ada3: ATA-8 SATA 2.x device ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada3: Command Queueing enabled ada3: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) Each of these disks can push about 140MByte/sec (sequential) but I don't expect to see that kind of I/O. I do expect to see around 100MByte/sec per disk (just have to trust me; I'm used to my disks! :-) ). zpool-wise, absolutely nothing special (note I am using ZFSv28 on RELENG_8 however), and *VERY* little tuning is done in loader.conf: icarus# zpool status data pool: data state: ONLINE scan: scrub repaired 0 in 0h54m with 0 errors on Tue Jun 14 10:24:49 2011 config: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 ada3 ONLINE 0 0 0 errors: No known data errors icarus# egrep ^vfs.zfs /boot/loader.conf vfs.zfs.arc_max="5120M" So let's test. I have some pretty big files on the data/storage filesystem, so let's try dd'ing one of those while simultaneously using "gstat -I500ms -f 'ada1|ada3'" to watch disk I/O. It's *extremely* important that I dd a file which isn't already in ARC (ARC right now for me takes up about 6GB of RAM, so I'll pick a CD image I haven't accessed since the machine has rebooted). icarus# cd /storage/CD_Images/FreeBSD/7.4-STABLE/ icarus# ls -l *disc1* -rwxr--r-- 1 storage storage 663519232 Mar 4 06:54 FreeBSD-7.4-RELEASE-amd64-disc1.iso icarus# dd if=FreeBSD-7.4-RELEASE-amd64-disc1.iso of=/dev/null bs=64k 10124+1 records in 10124+1 records out 663519232 bytes transferred in 3.965980 secs (167302715 bytes/sec) And in another window: dT: 0.504s w: 0.500s filter: ada1|ada3 L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 10 750 750 94557 13.4 0 0 0.0 100.4| ada1 10 631 631 80771 15.9 0 0 0.0 100.2| ada3 Looks to me like both disks were getting utilised. Let's double check with "zpool iostat -v data 1" and use another file which isn't in the ARC: icarus# cd ../8.2-STABLE/ icarus# ls -l *memstick* -rwxr--r-- 1 storage storage 1087774720 Mar 4 06:17 FreeBSD-8.2-RELEASE-amd64-memstick.img icarus# dd if=FreeBSD-8.2-RELEASE-amd64-memstick.img of=/dev/null bs=64k 16598+1 records in 16598+1 records out 1087774720 bytes transferred in 6.802677 secs (159903917 bytes/sec) capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 0 0 0 0 mirror 278G 650G 0 0 0 0 ada1 - - 0 0 0 0 ada3 - - 0 0 0 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 1.09K 0 138M 0 mirror 278G 650G 1.09K 0 138M 0 ada1 - - 595 0 74.2M 0 ada3 - - 519 0 63.7M 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 1.10K 0 140M 0 mirror 278G 650G 1.10K 0 140M 0 ada1 - - 542 0 66.8M 0 ada3 - - 584 0 73.1M 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 1.32K 0 168M 0 mirror 278G 650G 1.32K 0 168M 0 ada1 - - 724 0 89.3M 0 ada3 - - 626 0 78.3M 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 1.26K 0 161M 0 mirror 278G 650G 1.26K 0 161M 0 ada1 - - 655 0 80.7M 0 ada3 - - 637 0 79.7M 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 1.23K 0 156M 0 mirror 278G 650G 1.23K 0 156M 0 ada1 - - 635 0 78.2M 0 ada3 - - 625 0 78.2M 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 1.17K 0 148M 0 mirror 278G 650G 1.17K 0 148M 0 ada1 - - 600 0 73.8M 0 ada3 - - 595 0 74.4M 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 955 0 119M 0 mirror 278G 650G 955 0 119M 0 ada1 - - 411 0 50.8M 0 ada3 - - 544 0 68.1M 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 278G 650G 0 0 0 0 mirror 278G 650G 0 0 0 0 ada1 - - 0 0 0 0 ada3 - - 0 0 0 0 ---------- ----- ----- ----- ----- ----- ----- Performance was a little less than I estimated (I really don't care to be honest), but this double-confirms that yes, reads do get split across mirror members. Therefore I cannot explain what you're seeing. Maybe consider upgrading to a newer RELENG_8 and ZFSv28 and see if things improve? I wish I had a way to confirm this would fix your problem but I do not. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue Aug 9 14:00:57 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EA851065673 for ; Tue, 9 Aug 2011 14:00:57 +0000 (UTC) (envelope-from strigeus@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id C0AAB8FC13 for ; Tue, 9 Aug 2011 14:00:56 +0000 (UTC) Received: by qyk9 with SMTP id 9so2787qyk.13 for ; Tue, 09 Aug 2011 07:00:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=FSTMNnb/wRtGUJdDAYktA/tC1PovUYB9tQ45ANsKqwk=; b=J1KNjj6usWV/bS8qlG0SH9FO+lCaJzzzo/coacHBK0lduKlXiOEQMoSKbeLknmlzi4 OWwkR/5ZjP6AtQG6lzDuFH/AouhwVkN4j/n/Nyk5n83es54pi62F+Ib/+pm0/pLCpmWL 965i6/+6IKRRjTW/G7YC1oa7JSVy2IK2flNnc= Received: by 10.229.17.9 with SMTP id q9mr3623334qca.198.1312896871157; Tue, 09 Aug 2011 06:34:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.85.12 with HTTP; Tue, 9 Aug 2011 06:34:00 -0700 (PDT) From: Ludvig Strigeus Date: Tue, 9 Aug 2011 15:34:00 +0200 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Free space of 'zfs list' vs 'zpool list' X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 14:00:57 -0000 I use zfs as root file system in a raidz1 configuration with 4x1.5TB disks. zpool list says 150G available while zfs list says 47.1GB available. I do not use any reservations but compression is enabled. Due to the raidz with 4 disks, I would expect zfs list to say 150GB * 75% = 112.50GB free, not 47.1GB. Can someone explain where the 65GB have gone? uname -a: FreeBSD ludde.dyndns.org 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 zpool list: NAME SIZE USED AVAIL CAP HEALTH ALTROOT tank 5.44T 5.29T 150G 97% ONLINE - zfs list: NAME USED AVAIL REFER MOUNTPOINT tank 3.96T 47.1G 28.4K legacy tank/data 3.95T 47.1G 3.95T /data ... other file systems omitted ... zfs list -t snapshot: NAME USED AVAIL REFER MOUNTPOINT tank/data@2011-08-05 385M - 3.60T - zpool status: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gptid/da8c85e1-f9fa-11de-a19c-001731eee65f ONLINE 0 0 0 gptid/db86c6a9-f9fa-11de-a19c-001731eee65f ONLINE 0 0 0 gptid/dc4efa95-f9fa-11de-a19c-001731eee65f ONLINE 0 0 0 gptid/dcd40f4a-f9fa-11de-a19c-001731eee65f ONLINE 0 0 0 Thanks, Ludde From owner-freebsd-fs@FreeBSD.ORG Tue Aug 9 14:05:54 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 100ED106564A for ; Tue, 9 Aug 2011 14:05:54 +0000 (UTC) (envelope-from universite@ukr.net) Received: from otrada.od.ua (universite-1-pt.tunnel.tserv24.sto1.ipv6.he.net [IPv6:2001:470:27:140::2]) by mx1.freebsd.org (Postfix) with ESMTP id 718F38FC14 for ; Tue, 9 Aug 2011 14:05:53 +0000 (UTC) Received: from [IPv6:2001:470:28:140:834:8668:764c:37a8] ([IPv6:2001:470:28:140:834:8668:764c:37a8]) (authenticated bits=0) by otrada.od.ua (8.14.4/8.14.4) with ESMTP id p79E5lqf022319 for ; Tue, 9 Aug 2011 17:05:48 +0300 (EEST) (envelope-from universite@ukr.net) Message-ID: <4E413EB0.5040108@ukr.net> Date: Tue, 09 Aug 2011 17:05:36 +0300 From: "Vladislav V. Prodan" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20110809131057.GA53580@felucia.tataz.chchile.org> <20110809135212.GA13334@icarus.home.lan> In-Reply-To: <20110809135212.GA13334@icarus.home.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-95.5 required=5.0 tests=FREEMAIL_FROM,FSL_RU_URL, RDNS_NONE, SPF_SOFTFAIL, T_TO_NO_BRKTS_FREEMAIL, USER_IN_WHITELIST autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mary-teresa.otrada.od.ua X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (otrada.od.ua [IPv6:2001:470:28:140::5]); Tue, 09 Aug 2011 17:05:50 +0300 (EEST) Subject: Re: zfs mirror reads only on one disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 14:05:54 -0000 09.08.2011 16:52, Jeremy Chadwick wrote: > Since I have a ZFS mirror setup I can test this. Let's take a look: > > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 Maybe it lies in the differences between the drivers ad and ada? -- Vladislav V. Prodan VVP24-UANIC +380[67]4584408 +380[99]4060508 vlad11@jabber.ru From owner-freebsd-fs@FreeBSD.ORG Tue Aug 9 14:12:22 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3EB8106564A for ; Tue, 9 Aug 2011 14:12:22 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id 9C5D68FC1E for ; Tue, 9 Aug 2011 14:12:22 +0000 (UTC) Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta08.emeryville.ca.mail.comcast.net with comcast id JEBC1h0020EPchoA8ECJMq; Tue, 09 Aug 2011 14:12:18 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta01.emeryville.ca.mail.comcast.net with comcast id JECK1h00H1t3BNj8MECKPj; Tue, 09 Aug 2011 14:12:20 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C8803102C19; Tue, 9 Aug 2011 07:12:20 -0700 (PDT) Date: Tue, 9 Aug 2011 07:12:20 -0700 From: Jeremy Chadwick To: "Vladislav V. Prodan" Message-ID: <20110809141220.GA14141@icarus.home.lan> References: <20110809131057.GA53580@felucia.tataz.chchile.org> <20110809135212.GA13334@icarus.home.lan> <4E413EB0.5040108@ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E413EB0.5040108@ukr.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: zfs mirror reads only on one disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 14:12:22 -0000 On Tue, Aug 09, 2011 at 05:05:36PM +0300, Vladislav V. Prodan wrote: > 09.08.2011 16:52, Jeremy Chadwick wrote: > >Since I have a ZFS mirror setup I can test this. Let's take a look: > > > >ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > > Maybe it lies in the differences between the drivers ad and ada? ZFS would have to have code in it that differentiated between the two. A vdev is a vdev, so I don't see how this is a plausible explanation. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue Aug 9 15:19:10 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC2591065676 for ; Tue, 9 Aug 2011 15:19:10 +0000 (UTC) (envelope-from jeremie@le-hen.org) Received: from smtp5-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::14]) by mx1.freebsd.org (Postfix) with ESMTP id 4CAAD8FC17 for ; Tue, 9 Aug 2011 15:19:08 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id 2A257D480F9; Tue, 9 Aug 2011 17:19:02 +0200 (CEST) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id 1483B3723C; Tue, 9 Aug 2011 15:19:02 +0000 (UTC) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id 09A93A128A; Tue, 9 Aug 2011 15:19:02 +0000 (UTC) Date: Tue, 9 Aug 2011 17:19:02 +0200 From: Jeremie Le Hen To: Jeremy Chadwick Message-ID: <20110809151901.GA7877@felucia.tataz.chchile.org> References: <20110809131057.GA53580@felucia.tataz.chchile.org> <20110809135212.GA13334@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110809135212.GA13334@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.org, Jeremie Le Hen Subject: Re: zfs mirror reads only on one disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 15:19:10 -0000 On Tue, Aug 09, 2011 at 06:52:12AM -0700, Jeremy Chadwick wrote: > > Performance was a little less than I estimated (I really don't care to > be honest), but this double-confirms that yes, reads do get split across > mirror members. By the way, I tried with the same disk (WD Caviar Black) (not the same size though) on Solaris 11: extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 1104.5 0.0 141371.6 0.0 0.0 0.9 0.0 0.9 1 95 c5t5d0 extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 1101.7 0.0 141014.0 0.0 0.0 0.9 0.0 0.9 1 95 c5t5d0 It can reach 140 MB/s! > Therefore I cannot explain what you're seeing. Maybe consider upgrading > to a newer RELENG_8 and ZFSv28 and see if things improve? I wish I had > a way to confirm this would fix your problem but I do not. Ok, I didn't know ZFS v28 was MFC'd to RELENG_8. By the way, I see you switched to the new ata(4) driver according to your device names. Is it painless to upgrade? I'll give it a try this evening hopefully. Thanks. Regards, -- Jeremie Le Hen Humans are born free and equal. But some are more equal than others. Coluche From owner-freebsd-fs@FreeBSD.ORG Tue Aug 9 15:42:09 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4A8C106564A for ; Tue, 9 Aug 2011 15:42:09 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id BBF568FC0A for ; Tue, 9 Aug 2011 15:42:09 +0000 (UTC) Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta06.emeryville.ca.mail.comcast.net with comcast id JFR71h0031wfjNsA6Fi5vx; Tue, 09 Aug 2011 15:42:05 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta23.emeryville.ca.mail.comcast.net with comcast id JFi61h00f1t3BNj8jFi6QS; Tue, 09 Aug 2011 15:42:07 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 185C5102C19; Tue, 9 Aug 2011 08:42:08 -0700 (PDT) Date: Tue, 9 Aug 2011 08:42:08 -0700 From: Jeremy Chadwick To: Jeremie Le Hen Message-ID: <20110809154208.GA15410@icarus.home.lan> References: <20110809131057.GA53580@felucia.tataz.chchile.org> <20110809135212.GA13334@icarus.home.lan> <20110809151901.GA7877@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110809151901.GA7877@felucia.tataz.chchile.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.org Subject: Re: zfs mirror reads only on one disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 15:42:10 -0000 On Tue, Aug 09, 2011 at 05:19:02PM +0200, Jeremie Le Hen wrote: > On Tue, Aug 09, 2011 at 06:52:12AM -0700, Jeremy Chadwick wrote: > > > > Performance was a little less than I estimated (I really don't care to > > be honest), but this double-confirms that yes, reads do get split across > > mirror members. > > By the way, I tried with the same disk (WD Caviar Black) (not the same > size though) on Solaris 11: > > extended device statistics > r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device > 1104.5 0.0 141371.6 0.0 0.0 0.9 0.0 0.9 1 95 c5t5d0 > extended device statistics > r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device > 1101.7 0.0 141014.0 0.0 0.0 0.9 0.0 0.9 1 95 c5t5d0 > > It can reach 140 MB/s! I'm aware of this, but the drive won't perform like that under random seeks, nor as the actuator arm starts to work its way towards the centre of the disk. This is normal for mechanical drives. Given that my disks are about ~30% used, the performance I saw is about right. I should also point out, even though it's unrelated to this thread, that the WD1002FAEX drives use 1 less platter than the WD1001FALS (both are 1TB drives), and the WD1002FAEX has 64MBytes cache. As such, the overall speed improvement is about 20MBytes/sec.. Also, less platters = better airflow; the idle temperature difference between the two models is about 6C on my desktop system, and about 4-5C on my (low-noise) servers. I have a small side project to replace all our WD1001FALS drives with WD1002FAEX due to all the positives. It's worth it, IMO. > > Therefore I cannot explain what you're seeing. Maybe consider upgrading > > to a newer RELENG_8 and ZFSv28 and see if things improve? I wish I had > > a way to confirm this would fix your problem but I do not. > > Ok, I didn't know ZFS v28 was MFC'd to RELENG_8. By the way, I see you > switched to the new ata(4) driver according to your device names. Is it > painless to upgrade? I'll give it a try this evening hopefully. That depends on how complex your system is as well as what you define "painless" as. For me, it's as simple as adding ahci_load="yes" into /boot/loader.conf and changing /etc/fstab. That's literally all I have to do on my systems to get them to work. I'm excluding things like adjusting configuration files for monitoring suites (e.g. changing rrdbot's configuration to monitor ada0 instead of ad4, etc...). Overall the ATA-to-CAM emulation stuff works beautifully, it's one of the things that makes me a very happy camper with FreeBSD. I wish I could send mav@ a whole ton of beer. :-) FreeBSD 9.0-BETA1 defaults to using ada(4), even on IDE/PATA disks, by the way. Just thought I'd throw that out there. (I verified it in VMware Workstation using IDE disk emulation (not LSI Logic SAS) last night). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Aug 10 10:04:53 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5C83106564A for ; Wed, 10 Aug 2011 10:04:53 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out0.tiscali.nl (smtp-out0.tiscali.nl [195.241.79.175]) by mx1.freebsd.org (Postfix) with ESMTP id 435CB8FC14 for ; Wed, 10 Aug 2011 10:04:52 +0000 (UTC) Received: from [212.182.167.131] (helo=sjakie.klop.ws) by smtp-out0.tiscali.nl with esmtp (Exim) (envelope-from ) id 1Qr5GB-00045K-OM for freebsd-fs@freebsd.org; Wed, 10 Aug 2011 11:39:35 +0200 Received: from 212-182-167-131.ip.telfort.nl (localhost [127.0.0.1]) by sjakie.klop.ws (Postfix) with ESMTP id C0F88203 for ; Wed, 10 Aug 2011 11:39:32 +0200 (CEST) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-fs@freebsd.org References: Date: Wed, 10 Aug 2011 11:39:32 +0200 MIME-Version: 1.0 From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/11.50 (FreeBSD) Content-Transfer-Encoding: quoted-printable Subject: Re: Free space of 'zfs list' vs 'zpool list' X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2011 10:04:53 -0000 On Tue, 09 Aug 2011 15:34:00 +0200, Ludvig Strigeus = =20 wrote: > I use zfs as root file system in a raidz1 configuration with 4x1.5TB =20 > disks. > zpool list says 150G available while zfs list says 47.1GB available. I = do > not use any reservations but compression is enabled. > > Due to the raidz with 4 disks, I would expect zfs list to say 150GB * =20 > 75% =3D > 112.50GB free, not 47.1GB. Can someone explain where the 65GB have gone= ? > > uname -a: > FreeBSD ludde.dyndns.org 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 > 02:41:51 UTC 2011 =20 > root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > amd64 > > zpool list: > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > tank 5.44T 5.29T 150G 97% ONLINE - > > zfs list: > NAME USED AVAIL REFER MOUNTPOINT > tank 3.96T 47.1G 28.4K legacy > tank/data 3.95T 47.1G 3.95T /data > ... other file systems omitted ... > > zfs list -t snapshot: > NAME USED AVAIL REFER MOUNTPOINT > tank/data@2011-08-05 385M - 3.60T - > > zpool status: > NAME STATE READ = =20 > WRITE > CKSUM > tank ONLINE =20 > 0 0 > 0 > raidz1 ONLINE =20 > 0 0 > 0 > gptid/da8c85e1-f9fa-11de-a19c-001731eee65f ONLINE =20 > 0 0 > 0 > gptid/db86c6a9-f9fa-11de-a19c-001731eee65f ONLINE =20 > 0 0 > 0 > gptid/dc4efa95-f9fa-11de-a19c-001731eee65f ONLINE =20 > 0 0 > 0 > gptid/dcd40f4a-f9fa-11de-a19c-001731eee65f ONLINE =20 > 0 0 > 0 > > Thanks, > Ludde > _______________________________________________ > 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" There is more overhead than one disk for raidz1. There is also metadata =20 for the filesystem. 65GB of 3.5TB isn't that much. It is like 0.5%. It is time to delete some files or add another disk. Ronald. From owner-freebsd-fs@FreeBSD.ORG Wed Aug 10 17:27:16 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21856106564A for ; Wed, 10 Aug 2011 17:27:16 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id D581A8FC12 for ; Wed, 10 Aug 2011 17:27:15 +0000 (UTC) Received: by gyd10 with SMTP id 10so971191gyd.13 for ; Wed, 10 Aug 2011 10:27:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=b5pdjC8JCzdEoLLENVUUyJcVNY9qflqSFF3ehsKZU2M=; b=M6lISeV2Z50GjdQBvJWfbRKW5rRm+In6LbEQHBSpJr5ozwI3lxSmHxn/GXEBGXjRLN R4ZmhmWW4W83OdZoF2jbNshHi4YzlkR7MMsNHH74maHR5AI+BON/a/N/LLVbxLwaoXLT Gt/WE97v48POgyJyYFj62CZ58HE4L5E84pQf0= MIME-Version: 1.0 Received: by 10.236.155.40 with SMTP id i28mr8685926yhk.156.1312997235234; Wed, 10 Aug 2011 10:27:15 -0700 (PDT) Received: by 10.236.103.19 with HTTP; Wed, 10 Aug 2011 10:27:15 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Aug 2011 18:27:15 +0100 Message-ID: From: krad To: Ludvig Strigeus Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Free space of 'zfs list' vs 'zpool list' X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2011 17:27:16 -0000 On 9 August 2011 14:34, Ludvig Strigeus wrote: > I use zfs as root file system in a raidz1 configuration with 4x1.5TB disks. > zpool list says 150G available while zfs list says 47.1GB available. I do > not use any reservations but compression is enabled. > > Due to the raidz with 4 disks, I would expect zfs list to say 150GB * 75% = > 112.50GB free, not 47.1GB. Can someone explain where the 65GB have gone? > > uname -a: > FreeBSD ludde.dyndns.org 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 > 02:41:51 UTC 2011 root@mason.cse.buffalo.edu: > /usr/obj/usr/src/sys/GENERIC > amd64 > > zpool list: > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > tank 5.44T 5.29T 150G 97% ONLINE - > > zfs list: > NAME USED AVAIL REFER MOUNTPOINT > tank 3.96T 47.1G 28.4K legacy > tank/data 3.95T 47.1G 3.95T /data > ... other file systems omitted ... > > zfs list -t snapshot: > NAME USED AVAIL REFER MOUNTPOINT > tank/data@2011-08-05 385M - 3.60T - > > zpool status: > NAME STATE READ WRITE > CKSUM > tank ONLINE 0 0 > 0 > raidz1 ONLINE 0 0 > 0 > gptid/da8c85e1-f9fa-11de-a19c-001731eee65f ONLINE 0 0 > 0 > gptid/db86c6a9-f9fa-11de-a19c-001731eee65f ONLINE 0 0 > 0 > gptid/dc4efa95-f9fa-11de-a19c-001731eee65f ONLINE 0 0 > 0 > gptid/dcd40f4a-f9fa-11de-a19c-001731eee65f ONLINE 0 0 > 0 > > Thanks, > Ludde > _______________________________________________ > 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" > how about quotas? From owner-freebsd-fs@FreeBSD.ORG Wed Aug 10 19:10:13 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE176106564A for ; Wed, 10 Aug 2011 19:10:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BF05C8FC17 for ; Wed, 10 Aug 2011 19:10:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7AJADA2070368 for ; Wed, 10 Aug 2011 19:10:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7AJADsn070367; Wed, 10 Aug 2011 19:10:13 GMT (envelope-from gnats) Date: Wed, 10 Aug 2011 19:10:13 GMT Message-Id: <201108101910.p7AJADsn070367@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Matuska Cc: Subject: Re: kern/157728: [zfs] zfs (v28) incremental receive may leave behind temporary clones X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Matuska List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2011 19:10:13 -0000 The following reply was made to PR kern/157728; it has been noted by GNATS. From: Martin Matuska To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/157728: [zfs] zfs (v28) incremental receive may leave behind temporary clones Date: Wed, 10 Aug 2011 21:08:36 +0200 This is a multi-part message in MIME format. --------------020705050701020904030304 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I have now an alternative patch (does almost the same, but at different place). -- Martin Matuska FreeBSD committer http://blog.vx.sk --------------020705050701020904030304 Content-Type: text/plain; name="dmu_objset.c.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmu_objset.c.patch" Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_objset.c =================================================================== --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_objset.c (revision 224760) +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_objset.c (working copy) @@ -1760,10 +1760,29 @@ dmu_objset_prefetch(const char *name, void *arg) { dsl_dataset_t *ds; + char *cp; + /* + * If the objset starts with a '%', then ignore it. + * These hidden datasets are always inconsistent and by not opening + * them here, we can avoid a race with dsl_dir_destroy_check(). + */ + cp = strrchr(name, '/'); + if (cp && cp[1] == '%') + return (0); + if (dsl_dataset_hold(name, FTAG, &ds)) return (0); + /* + * If the objset is in an inconsistent state (eg, in the process + * of being destroyed), don't prefetch it. + */ + if (ds->ds_phys->ds_flags & DS_FLAG_INCONSISTENT) { + dsl_dataset_rele(ds, FTAG); + return (0); + } + if (!BP_IS_HOLE(&ds->ds_phys->ds_bp)) { mutex_enter(&ds->ds_opening_lock); if (ds->ds_objset == NULL) { --------------020705050701020904030304-- From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 07:30:18 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A937106566C for ; Thu, 11 Aug 2011 07:30:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 594528FC14 for ; Thu, 11 Aug 2011 07:30:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7B7UHjt079076 for ; Thu, 11 Aug 2011 07:30:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7B7UHsJ079071; Thu, 11 Aug 2011 07:30:17 GMT (envelope-from gnats) Date: Thu, 11 Aug 2011 07:30:17 GMT Message-Id: <201108110730.p7B7UHsJ079071@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: bas Cc: Subject: Re: kern/156193: [ufs] [hang] UFS snapshot hangs & & deadlocks processes X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bas List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 07:30:18 -0000 The following reply was made to PR kern/156193; it has been noted by GNATS. From: bas To: bug-followup@freebsd.org, sec@42.org Cc: Subject: Re: kern/156193: [ufs] [hang] UFS snapshot hangs && deadlocks processes Date: Thu, 11 Aug 2011 13:01:22 +0600 --00235400f436315abe04aa355e1b Content-Type: text/plain; charset=UTF-8 I have same problem. FreeBSD domain.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 --00235400f436315abe04aa355e1b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have same problem.
FreeBSD domain.com 8.2-RELEASE FreeB= SD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011 =C2=A0 =C2=A0 root@almeida.= cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC =C2=A0i386
--00235400f436315abe04aa355e1b-- From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:03:16 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CB20106564A for ; Thu, 11 Aug 2011 16:03:16 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id 04A2A8FC14 for ; Thu, 11 Aug 2011 16:03:15 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.5/8.14.4) with ESMTP id p7BG3EPA026304 for ; Thu, 11 Aug 2011 18:03:14 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.5/8.14.4/Submit) id p7BG3EUM026303 for freebsd-fs@freebsd.org; Thu, 11 Aug 2011 12:03:14 -0400 (EDT) (envelope-from cracauer) Date: Thu, 11 Aug 2011 12:03:14 -0400 From: Martin Cracauer To: freebsd-fs@freebsd.org Message-ID: <20110811160314.GA25076@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:03:16 -0000 My computer keeps doing what I say, not what I want :-) This zpool with a 2-drive mirror had a dead drive (ad10) which I removed. After I tried to put ad2 as a replacement drive I ended up with the drive not in the mirror, it seems to have extended the zpool (it's size?). NAME STATE READ WRITE CKSUM cbackup3 DEGRADED 0 0 0 mirror DEGRADED 0 0 0 ad6 ONLINE 0 0 0 ad10 REMOVED 0 0 0 ad2 ONLINE 0 0 11 Unfortunately I didn't keep note of the specific command that I used. Two questions: - Does somebody know offhand what I did and what I should have done instead to get ad2 into the mirror? - Would there have been a way to remove ad2 from this set? It didn't let me, saying it can only remove drives from mirror or raid sets. I think it should have been possible before I mounted the filesystem in there read-write for the first time after the drive add. This seems like an easy mistake to make. The array doesn't contain important data, just trying to sort out things for the future. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:24:22 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C42A0106564A for ; Thu, 11 Aug 2011 16:24:22 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 82D968FC0C for ; Thu, 11 Aug 2011 16:24:22 +0000 (UTC) Received: by vws18 with SMTP id 18so2430699vws.13 for ; Thu, 11 Aug 2011 09:24:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WRdMBqB7JTOBQ6v8IS2F8W2PNkJYefQP13LyO9RpJs0=; b=NoY/Pkm88hOBAlH3ALHh3LzCDWVPz1t6x6uglWBqUxcx0dybIgSwyv/RWWEduAkP6x jOyY+jfw8p6LhektQv87RHjNjPu7FlxmTFPH3jzxoEQ6Bddm0ZCMDlME9meKz9mTOh3Q Ek3kvxH0rKDdQ/1o/StWUcZqOSA4e6gwUJOA0= MIME-Version: 1.0 Received: by 10.220.117.136 with SMTP id r8mr1596379vcq.109.1313079861686; Thu, 11 Aug 2011 09:24:21 -0700 (PDT) Received: by 10.220.186.134 with HTTP; Thu, 11 Aug 2011 09:24:21 -0700 (PDT) In-Reply-To: <20110811160314.GA25076@cons.org> References: <20110811160314.GA25076@cons.org> Date: Thu, 11 Aug 2011 09:24:21 -0700 Message-ID: From: Freddie Cash To: Martin Cracauer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:24:22 -0000 On Thu, Aug 11, 2011 at 9:03 AM, Martin Cracauer wrote: > My computer keeps doing what I say, not what I want :-) > > This zpool with a 2-drive mirror had a dead drive (ad10) which I > removed. After I tried to put ad2 as a replacement drive I ended up > with the drive not in the mirror, it seems to have extended the zpool > (it's size?). > > NAME STATE READ WRITE CKSUM > cbackup3 DEGRADED 0 0 0 > mirror DEGRADED 0 0 0 > ad6 ONLINE 0 0 0 > ad10 REMOVED 0 0 0 > ad2 ONLINE 0 0 11 > > Unfortunately I didn't keep note of the specific command that I used. > > Mirror vdevs are slightly special in they way they are handled. You don't have to "zpool replace" drives in vdevs. Instead, you "zpool detach" the old/dead drive from the pool (this "breaks" the mirror vdev, leaving you with a single-disk vdev), and then you "zpool attach" the new drive *to the existing drive*. For example, the series of commands you should have used would be: zpool detach cbackup3 ad10 zpool attach cbackup3 ad2 ad6 Or, you don't want to lose any redundancy in your pool, you attach the new drive first, creating a 3-way mirror vdev, and then detach the old drive after the resilver is complete. zpool attach cbackup3 ad2 ad6 zpool detach cbackup3 ad10 Right now, your pool has 2 vdevs in it: 1 mirror (ad6 + ad10) and one single-disk (ad2). You are currently running with a "degraded" pool, as there is no redundancy in it: if you lose disk ad2, you lose the entire pool. Thankfully, if you have the drive bays, this is easy to fix. Just attach another drive to ad2 to create a second mirror vdev. :) Then you will have a pool with 2 mirror vdevs (similar to a RAID10 setup). Of course, you'll need to replace the ad10 disk to make it fully redundant. Something like: zpool attach cbackup3 adXX ad2 zpool detach cbackup3 ad10 zpool attach cbackup3 adYY ad6 > Two questions: > > - Does somebody know offhand what I did and what I should have done > instead to get ad2 into the mirror? > > You used "zpool add" (which adds new vdevs to the pool) instead of "zpool attach" (which attaches drives to an existing mirror vdev). Or, you used "zpool add" instead of "zpool replace". > - Would there have been a way to remove ad2 from this set? Nope. You cannot remove storage vdevs from a pool. You can only remove log and cache vdevs from a pool. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:28:39 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDD79106564A for ; Thu, 11 Aug 2011 16:28:39 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id 6FCE08FC0C for ; Thu, 11 Aug 2011 16:28:39 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.5/8.14.4) with ESMTP id p7BGSc9K030971; Thu, 11 Aug 2011 18:28:38 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.5/8.14.4/Submit) id p7BGScRe030970; Thu, 11 Aug 2011 12:28:38 -0400 (EDT) (envelope-from cracauer) Date: Thu, 11 Aug 2011 12:28:38 -0400 From: Martin Cracauer To: Adam Vande More Message-ID: <20110811162838.GA29108@cons.org> References: <20110811160314.GA25076@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, Martin Cracauer Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:28:40 -0000 Adam Vande More wrote on Thu, Aug 11, 2011 at 11:10:34AM -0500: > On Thu, Aug 11, 2011 at 11:03 AM, Martin Cracauer wrote: > > > NAME STATE READ WRITE CKSUM > > cbackup3 DEGRADED 0 0 0 > > mirror DEGRADED 0 0 0 > > ad6 ONLINE 0 0 0 > > ad10 REMOVED 0 0 0 > > ad2 ONLINE 0 0 11 > > > > Unfortunately I didn't keep note of the specific command that I used. > > > > Two questions: > > > > - Does somebody know offhand what I did and what I should have done > > instead to get ad2 into the mirror? > > > > What you did is add a disk to the zpool, not the mirror. `zpool history` shows: "zpool add -f cbackup3 ad2" What would have been correct? `zpool attach cbackup3 ad6 ad2` ? `zpool replace cbackup ad10 ad2` ? I guess they are equivalent except the first one would create a degraded three-way mirror. > > - Would there have been a way to remove ad2 from this set? > > > > I'm not sure of a way to remove the vdev other than to recreate from scratch > but perhaps the new features of zpool v28 allow for some forgiveness here. That reminds me to ask: Is there a way to clone a ZFS filesystem (not pool) including all snapshots inside? Let's say I have a 3-disk raidz filesystem with a bunch of snapshots and I want to go to new disks in a mirror setup. Is there a better way than doing an rsync snapshot by snapshot going forward? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:30:12 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9ECBA106566B for ; Thu, 11 Aug 2011 16:30:12 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id EC6138FC1B for ; Thu, 11 Aug 2011 16:30:11 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA17995; Thu, 11 Aug 2011 19:30:08 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E44038F.7000001@FreeBSD.org> Date: Thu, 11 Aug 2011 19:30:07 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Martin Cracauer References: <20110811160314.GA25076@cons.org> In-Reply-To: <20110811160314.GA25076@cons.org> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:30:12 -0000 on 11/08/2011 19:03 Martin Cracauer said the following: > My computer keeps doing what I say, not what I want :-) > > This zpool with a 2-drive mirror had a dead drive (ad10) which I > removed. After I tried to put ad2 as a replacement drive I ended up > with the drive not in the mirror, it seems to have extended the zpool > (it's size?). > > NAME STATE READ WRITE CKSUM > cbackup3 DEGRADED 0 0 0 > mirror DEGRADED 0 0 0 > ad6 ONLINE 0 0 0 > ad10 REMOVED 0 0 0 > ad2 ONLINE 0 0 11 > > Unfortunately I didn't keep note of the specific command that I used. > > Two questions: > > - Does somebody know offhand what I did and what I should have done > instead to get ad2 into the mirror? You confused 'add' and 'attach' commands or something like that. > - Would there have been a way to remove ad2 from this set? No. > It didn't > let me, saying it can only remove drives from mirror or raid sets. > I think it should have been possible before I mounted the filesystem > in there read-write for the first time after the drive add. This > seems like an easy mistake to make. This has been reported to the ZFS people (upstream) many times, still they didn't add any safety nets. > The array doesn't contain important data, just trying to sort out > things for the future. Read the docs, twice, be careful, take backups before any modifying actions. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:36:09 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 267F9106566B for ; Thu, 11 Aug 2011 16:36:09 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id BF70C8FC0C for ; Thu, 11 Aug 2011 16:36:08 +0000 (UTC) Received: by vxh11 with SMTP id 11so2406250vxh.13 for ; Thu, 11 Aug 2011 09:36:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vJu2FTEovBDMYTegJQRPdSRNSS1+sOrPGy35M1XLuyo=; b=e8WQqJO10jzyk+djFjQrzKZ/+RzmbK+YYz/MkBPZlNYBIIjmXHWjcbtWNLCi0DB/AL xXySrj6lxC1xfqGXLcdEl4I1dHmYt6+cG0FFMG+6UeyIg3+Mhu7TZGKUNdfh8rBvgCBD vAiFVvauDP9R6nIlo7+o14ANLpY/gykUcKDl8= MIME-Version: 1.0 Received: by 10.220.57.11 with SMTP id a11mr3026766vch.4.1313080567852; Thu, 11 Aug 2011 09:36:07 -0700 (PDT) Received: by 10.220.186.134 with HTTP; Thu, 11 Aug 2011 09:36:07 -0700 (PDT) In-Reply-To: <4E44038F.7000001@FreeBSD.org> References: <20110811160314.GA25076@cons.org> <4E44038F.7000001@FreeBSD.org> Date: Thu, 11 Aug 2011 09:36:07 -0700 Message-ID: From: Freddie Cash To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Martin Cracauer Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:36:09 -0000 On Thu, Aug 11, 2011 at 9:30 AM, Andriy Gapon wrote: > on 11/08/2011 19:03 Martin Cracauer said the following: > It didn't > > let me, saying it can only remove drives from mirror or raid sets. > > I think it should have been possible before I mounted the filesystem > > in there read-write for the first time after the drive add. This > > seems like an easy mistake to make. > > This has been reported to the ZFS people (upstream) many times, still they > didn't > add any safety nets. > > There's a very big safety net included already: zpool will error out complaining about mis-matched vdevs if you try to "zpool add" a single disk to a pool with a mirror vdev. In fact, the user has to add "-f" (force) to the "zpool add" command in order for this to even happen. IOW, this is user error, not "lack of safety nets". :) > > The array doesn't contain important data, just trying to sort out > > things for the future. > > Read the docs, twice, be careful, take backups before any modifying > actions. > > And read the error messages, as well. :) -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:37:24 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4BFF106571C for ; Thu, 11 Aug 2011 16:37:24 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8F2908FC1A for ; Thu, 11 Aug 2011 16:37:24 +0000 (UTC) Received: by vxh11 with SMTP id 11so2407604vxh.13 for ; Thu, 11 Aug 2011 09:37:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jQQnHPQf0jQgPOM9sRD1MRJXIkqI3AMRMKzuNkGRTV0=; b=HmY1Bg8qqHtYgJ83eg2qWg0DgWzpW6kuFRIhtWGXu3fTNVxNv3d8m04qYgRhy6bo+S rGMP37E2ReJiW+cal/AzHT7HIldby7o0Q/MsvxMtbVNds8kAbnm0ev+2rWrgkdjw8VYY ZU/F5NnMsbDaDiBSJY0yW1L/CXfbrk0MPcO2s= MIME-Version: 1.0 Received: by 10.220.57.11 with SMTP id a11mr3027178vch.4.1313080644005; Thu, 11 Aug 2011 09:37:24 -0700 (PDT) Received: by 10.220.186.134 with HTTP; Thu, 11 Aug 2011 09:37:23 -0700 (PDT) In-Reply-To: <20110811162838.GA29108@cons.org> References: <20110811160314.GA25076@cons.org> <20110811162838.GA29108@cons.org> Date: Thu, 11 Aug 2011 09:37:23 -0700 Message-ID: From: Freddie Cash To: Martin Cracauer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:37:24 -0000 On Thu, Aug 11, 2011 at 9:28 AM, Martin Cracauer wrote: > That reminds me to ask: > > Which reminds me to ask, have you read any part of the zpool and zfs man pages? ;) > Is there a way to clone a ZFS filesystem (not pool) including all > snapshots inside? > > Read the zfs man page, especially the parts about "zfs send" and "zfs recv". -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:38:38 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24DDC106566B for ; Thu, 11 Aug 2011 16:38:38 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id ACFE18FC17 for ; Thu, 11 Aug 2011 16:38:37 +0000 (UTC) Received: by fxe4 with SMTP id 4so2390346fxe.13 for ; Thu, 11 Aug 2011 09:38:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9ImXTMNuR8G39wqfKxrBS8eByrBw6xiaWwNvzjHVTl8=; b=YNx4/51jmQh0ZiNEwbqV3ujN9f5HszKxSyVGgQFbFKSQqvNHQ7Q9LrDXR8ZkI99K3n fc6UgDFWaeo8sa7vXXX4Yt71iHLKYr7YBZ1O24qWBRxQoeahl9Ea0v5XLJWawrSpg8fe JJbfmU2po6WwoRt2BT4G1qBFK2xaDlyVIEtxM= MIME-Version: 1.0 Received: by 10.223.10.143 with SMTP id p15mr12972531fap.12.1313079035002; Thu, 11 Aug 2011 09:10:35 -0700 (PDT) Received: by 10.223.120.72 with HTTP; Thu, 11 Aug 2011 09:10:34 -0700 (PDT) In-Reply-To: <20110811160314.GA25076@cons.org> References: <20110811160314.GA25076@cons.org> Date: Thu, 11 Aug 2011 11:10:34 -0500 Message-ID: From: Adam Vande More To: Martin Cracauer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:38:38 -0000 On Thu, Aug 11, 2011 at 11:03 AM, Martin Cracauer wrote: > NAME STATE READ WRITE CKSUM > cbackup3 DEGRADED 0 0 0 > mirror DEGRADED 0 0 0 > ad6 ONLINE 0 0 0 > ad10 REMOVED 0 0 0 > ad2 ONLINE 0 0 11 > > Unfortunately I didn't keep note of the specific command that I used. > > Two questions: > > - Does somebody know offhand what I did and what I should have done > instead to get ad2 into the mirror? > What you did is add a disk to the zpool, not the mirror. > - Would there have been a way to remove ad2 from this set? > I'm not sure of a way to remove the vdev other than to recreate from scratch but perhaps the new features of zpool v28 allow for some forgiveness here. -- Adam Vande More From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:39:30 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F4A3106564A for ; Thu, 11 Aug 2011 16:39:30 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4870F8FC14 for ; Thu, 11 Aug 2011 16:39:30 +0000 (UTC) Received: by qyk9 with SMTP id 9so1557845qyk.13 for ; Thu, 11 Aug 2011 09:39:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.95.84 with SMTP id c20mr4623063qcn.278.1313079423248; Thu, 11 Aug 2011 09:17:03 -0700 (PDT) Received: by 10.229.87.10 with HTTP; Thu, 11 Aug 2011 09:17:03 -0700 (PDT) In-Reply-To: <20110811160314.GA25076@cons.org> References: <20110811160314.GA25076@cons.org> Date: Thu, 11 Aug 2011 18:17:03 +0200 Message-ID: From: Olivier Smedts To: Martin Cracauer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:39:30 -0000 2011/8/11 Martin Cracauer : > My computer keeps doing what I say, not what I want :-) > > This zpool with a 2-drive mirror had a dead drive (ad10) which I > removed. =A0After I tried to put ad2 as a replacement drive I ended up > with the drive not in the mirror, it seems to have extended the zpool > (it's size?). > > =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > =A0 =A0 =A0 =A0cbackup3 =A0 =A0DEGRADED =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0mirror =A0 =A0DEGRADED =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0ad6 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > =A0 =A0 =A0 =A0 =A0 =A0ad10 =A0 =A0REMOVED =A0 =A0 =A00 =A0 =A0 0 =A0 =A0= 0 > =A0 =A0 =A0 =A0 =A0ad2 =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 11 > > Unfortunately I didn't keep note of the specific command that I used. > > Two questions: > > - Does somebody know offhand what I did and what I should have done > =A0instead to get ad2 into the mirror? Maybe try : zpool history > - Would there have been a way to remove ad2 from this set? It didn't > =A0let me, saying it can only remove drives from mirror or raid sets. > =A0I think it should have been possible before I mounted the filesystem > =A0in there read-write for the first time after the drive add. =A0This > =A0seems like an easy mistake to make. Unfortunately, There is no way to shrink a pool, or remove vdevs. > The array doesn't contain important data, just trying to sort out > things for the future. > > Martin > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Martin Cracauer =A0 http://www.cons.org/cracauer/ > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 Olivier Smedts=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 _ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 ASCII ribbon campaign ( ) e-mail: olivier@gid0.org=A0 =A0 =A0 =A0 - against HTML email & vCards=A0 X www: http://www.gid0.org=A0 =A0 - against proprietary attachments / \ =A0 "Il y a seulement 10 sortes de gens dans le monde : =A0 ceux qui comprennent le binaire, =A0 et ceux qui ne le comprennent pas." From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 16:51:44 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A7351065670 for ; Thu, 11 Aug 2011 16:51:44 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id DD1838FC19 for ; Thu, 11 Aug 2011 16:51:43 +0000 (UTC) Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta09.westchester.pa.mail.comcast.net with comcast id K4ja1h0021ei1Bg594rkbz; Thu, 11 Aug 2011 16:51:44 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta24.westchester.pa.mail.comcast.net with comcast id K4rh1h01x1t3BNj3k4riLZ; Thu, 11 Aug 2011 16:51:43 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 3E1B4102C1A; Thu, 11 Aug 2011 09:51:40 -0700 (PDT) Date: Thu, 11 Aug 2011 09:51:40 -0700 From: Jeremy Chadwick To: Martin Cracauer Message-ID: <20110811165140.GA1421@icarus.home.lan> References: <20110811160314.GA25076@cons.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110811160314.GA25076@cons.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 16:51:44 -0000 On Thu, Aug 11, 2011 at 12:03:14PM -0400, Martin Cracauer wrote: > My computer keeps doing what I say, not what I want :-) First point: OP is using ZFSv15 or earlier. I can tell from the mirror vdev (not pool) being called "mirror", not "mirror-0". Readers should take note of that fact. To the OP: it's very important you disclose exactly what FreeBSD version you're using when submitting help requests. "I use FreeBSD 8" is insufficient; providing uname -a is always best. > This zpool with a 2-drive mirror had a dead drive (ad10) which I > removed. After I tried to put ad2 as a replacement drive I ended up > with the drive not in the mirror, it seems to have extended the zpool > (it's size?). > > NAME STATE READ WRITE CKSUM > cbackup3 DEGRADED 0 0 0 > mirror DEGRADED 0 0 0 > ad6 ONLINE 0 0 0 > ad10 REMOVED 0 0 0 > ad2 ONLINE 0 0 11 The pool "grew" because your pool is now, effectively, a stripe (RAID-0) of two disks (ad6 and ad2). Keep reading. > Unfortunately I didn't keep note of the specific command that I used. > > Two questions: > > - Does somebody know offhand what I did and what I should have done > instead to get ad2 into the mirror? I'm pretty sure I know what happened, but the problem is that I'm having severe difficulty phrasing the explanation. Adding to the annoyance is the fact that you did not bother to keep track of the commands you issued. The problem is something I have run into myself many times. It's a syntax-specific "quirk" with the zpool command, and ONLY applies when working with mirrors. Furthermore, the "gotcha" may be gone with ZFSv28 (which you aren't running); I'm not sure. The "quirk" is that you have to specify the name of an existing (working) mirror device *before* the new device you're attempting to integrate. E.g. "zpool {command} pool {existingdev} {newdev}", rather than "zpool {command} pool {newdev}". Failure to provide the name of the device of the existing mirror member results in the pool becoming a stripe, which you have no way to recover from without recreating the entire pool. I would show you an example but all my systems run ZFSv28 and I can't seem to find any online documentation which helps back up my statement. I hope someone else here can phrase what I'm trying to say in a more eloquent manner and provide documentation/references confirming it. > - Would there have been a way to remove ad2 from this set? It didn't > let me, saying it can only remove drives from mirror or raid sets. > I think it should have been possible before I mounted the filesystem > in there read-write for the first time after the drive add. This > seems like an easy mistake to make. What you have right now is a pool that consists of both a mirror (ad6+ad10), as well as a stripe (the mirror + ad2). As you know, stripe means the equivalent of RAID-0; lose the disk and you lose your pool. You will need to do this, given that you said "the array doesn't contain important data": # zpool destroy cbackup3 # zpool create cbackup3 mirror ad2 ad10 In the future please be sure to take note of all the commands you do, as well as any physical actions you take (yanking disks, etc.) between commands. ZFS is amazing and awesome, and the power of the zpool command is unmatched. However, I will agree that the likelihood of a mistake being made is quite high given that its commands use words which could mean the same thing as one another; "add" vs. "attach", "remove" vs. "detach", etc.. Yet they differ severely, and issuing the wrong one can be fatal in some situations. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 17:24:40 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C51A1065673 for ; Thu, 11 Aug 2011 17:24:40 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 10FBA8FC14 for ; Thu, 11 Aug 2011 17:24:39 +0000 (UTC) Received: by fxe4 with SMTP id 4so2425865fxe.13 for ; Thu, 11 Aug 2011 10:24:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=y+0u9YYAs7ZsOpQgOFY2yTKDIe6JPkWcrCUZtq0iHSg=; b=c0s64JCo1tGowwLJZmird+ewRh0kbEJULJ58JMn1RIbZ3O1JD2lrWQXH5qb6/x+N+b AlO8X3t1GGwVOeqYahrvTzQ4v+U3rKpGniu1WtvFzvycDqLLr4ucYhrUf+xX10fHWAAd dIIkSWmJFWWxoGtRoQcayuYqa1LYDBsCOs2Ks= MIME-Version: 1.0 Received: by 10.223.10.143 with SMTP id p15mr13067815fap.12.1313083478909; Thu, 11 Aug 2011 10:24:38 -0700 (PDT) Received: by 10.223.120.72 with HTTP; Thu, 11 Aug 2011 10:24:38 -0700 (PDT) In-Reply-To: <20110811165140.GA1421@icarus.home.lan> References: <20110811160314.GA25076@cons.org> <20110811165140.GA1421@icarus.home.lan> Date: Thu, 11 Aug 2011 12:24:38 -0500 Message-ID: From: Adam Vande More To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Martin Cracauer Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 17:24:40 -0000 On Thu, Aug 11, 2011 at 11:51 AM, Jeremy Chadwick wrote: > The problem is something I have run into myself many times. It's a > syntax-specific "quirk" with the zpool command, and ONLY applies when > working with mirrors. Furthermore, the "gotcha" may be gone with ZFSv28 > (which you aren't running); I'm not sure. > > The "quirk" is that you have to specify the name of an existing > (working) mirror device *before* the new device you're attempting to > integrate. E.g. "zpool {command} pool {existingdev} {newdev}", rather > than "zpool {command} pool {newdev}". Failure to provide the name of > the device of the existing mirror member results in the pool becoming > a stripe, which you have no way to recover from without recreating the > entire pool. > > I would show you an example but all my systems run ZFSv28 and I can't > seem to find any online documentation which helps back up my statement. > I hope someone else here can phrase what I'm trying to say in a more > eloquent manner and provide documentation/references confirming it. > I think you mean this but I'm not sure I'd agree it's a quirk. If there is an understanding of zpools, mirrors, and vdev's it seems like a logical syntax. However, the unforgiving nature of vdev's does put some fear in me whenever I make an change. http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Disk_Replacement_Example -- Adam Vande More From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 17:34:26 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 062FC106564A for ; Thu, 11 Aug 2011 17:34:26 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 533288FC0A for ; Thu, 11 Aug 2011 17:34:24 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA18921; Thu, 11 Aug 2011 20:34:21 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QrZ9A-000KYj-RA; Thu, 11 Aug 2011 20:34:20 +0300 Message-ID: <4E441299.9010505@FreeBSD.org> Date: Thu, 11 Aug 2011 20:34:17 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: Freddie Cash References: <20110811160314.GA25076@cons.org> <4E44038F.7000001@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, Martin Cracauer Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 17:34:26 -0000 on 11/08/2011 19:36 Freddie Cash said the following: > There's a very big safety net included already: zpool will error out > complaining about mis-matched vdevs if you try to "zpool add" a single disk to a > pool with a mirror vdev. In fact, the user has to add "-f" (force) to the > "zpool add" command in order for this to even happen. IOW, this is user error, > not "lack of safety nets". :) > Good! Didn't know about this, thanks. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 17:45:14 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D8671065670; Thu, 11 Aug 2011 17:45:14 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id 50AA98FC08; Thu, 11 Aug 2011 17:45:13 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.5/8.14.4) with ESMTP id p7BHjChX046213; Thu, 11 Aug 2011 19:45:12 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.5/8.14.4/Submit) id p7BHjCNl046207; Thu, 11 Aug 2011 13:45:12 -0400 (EDT) (envelope-from cracauer) Date: Thu, 11 Aug 2011 13:45:12 -0400 From: Martin Cracauer To: Freddie Cash Message-ID: <20110811174512.GA35650@cons.org> References: <20110811160314.GA25076@cons.org> <4E44038F.7000001@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, Martin Cracauer , Andriy Gapon Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 17:45:14 -0000 Freddie Cash wrote on Thu, Aug 11, 2011 at 09:36:07AM -0700: > On Thu, Aug 11, 2011 at 9:30 AM, Andriy Gapon wrote: > > > on 11/08/2011 19:03 Martin Cracauer said the following: > > > It didn't > > > > let me, saying it can only remove drives from mirror or raid sets. > > > I think it should have been possible before I mounted the filesystem > > > in there read-write for the first time after the drive add. This > > > seems like an easy mistake to make. > > > > This has been reported to the ZFS people (upstream) many times, still they > > didn't > > add any safety nets. > > > > There's a very big safety net included already: zpool will error out > complaining about mis-matched vdevs if you try to "zpool add" a single disk > to a pool with a mirror vdev. In fact, the user has to add "-f" (force) to > the "zpool add" command in order for this to even happen. IOW, this is user > error, not "lack of safety nets". :) I only issued the -f since the filesystem in there isn't important but anyway. The problem here isn't so much safety net in code. But I don't think the manpage is doing a good job explaining specifically how to replace failed drives in raidz and mirrors, respectively. Ending up doing a drive add to the zpool instead like I did is pretty easy, in particular if you are coming from traditional block device level raid systems. I also don't think that the behavior observed (add device to the pool and make it unremovable even before the filesystem is even mounted) is very intuitive. Sending snapshots, I was hoping for something that would send all snapshots at once (a clone of the complete filesystem). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 17:55:37 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19D7B106564A for ; Thu, 11 Aug 2011 17:55:37 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id B98928FC08 for ; Thu, 11 Aug 2011 17:55:36 +0000 (UTC) Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta08.westchester.pa.mail.comcast.net with comcast id K4ER1h0021wpRvQ585vcRQ; Thu, 11 Aug 2011 17:55:36 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta18.westchester.pa.mail.comcast.net with comcast id K5va1h01M1t3BNj3e5vbSQ; Thu, 11 Aug 2011 17:55:36 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 839ED102C1A; Thu, 11 Aug 2011 10:55:33 -0700 (PDT) Date: Thu, 11 Aug 2011 10:55:33 -0700 From: Jeremy Chadwick To: Adam Vande More Message-ID: <20110811175533.GA3196@icarus.home.lan> References: <20110811160314.GA25076@cons.org> <20110811165140.GA1421@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, Martin Cracauer Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 17:55:37 -0000 On Thu, Aug 11, 2011 at 12:24:38PM -0500, Adam Vande More wrote: > On Thu, Aug 11, 2011 at 11:51 AM, Jeremy Chadwick > wrote: > > > The problem is something I have run into myself many times. It's a > > syntax-specific "quirk" with the zpool command, and ONLY applies when > > working with mirrors. Furthermore, the "gotcha" may be gone with ZFSv28 > > (which you aren't running); I'm not sure. > > > > The "quirk" is that you have to specify the name of an existing > > (working) mirror device *before* the new device you're attempting to > > integrate. E.g. "zpool {command} pool {existingdev} {newdev}", rather > > than "zpool {command} pool {newdev}". Failure to provide the name of > > the device of the existing mirror member results in the pool becoming > > a stripe, which you have no way to recover from without recreating the > > entire pool. > > > > I would show you an example but all my systems run ZFSv28 and I can't > > seem to find any online documentation which helps back up my statement. > > I hope someone else here can phrase what I'm trying to say in a more > > eloquent manner and provide documentation/references confirming it. > > > > I think you mean this but I'm not sure I'd agree it's a quirk. If there is > an understanding of zpools, mirrors, and vdev's it seems like a logical > syntax. However, the unforgiving nature of vdev's does put some fear in me > whenever I make an change. > > http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Disk_Replacement_Example Yes, thank you -- that's one example of what I'm referring to. It applies to more than just "zpool replace" though; I'm pretty sure "zpool attach" is the one I'm thinking of: http://dbaspot.com/solaris/375684-zfs-convert-non-mirrored-mirrored.html Quoting the page: "zpool attach tank c1t2d0 c1t4d0" Had the individual done "zpool attach tank c1t4d0" they would have ended up with a stripe, which may or may not have been what they wanted. My personal preference is to refer to this as syntax/design flaw (someone wasn't thinking ahead), but I tend to piss people off when I get on my soapbox so I use the word "quirk" instead. The reason I classify it as such is that the chance of someone mucking up their pool as a result is extremely high. There are a *ton* of ways to address this in the parser. My choice would be to require a pool type designator in front of whatever you were doing (e.g. "zpool attach tank mirror c1t4d0", "zpool attach tank stripe c1t4d0", etc.). You get the idea. Sure, it's more characters to type, but it removes the ambiguity and greatly decreases the chance of someone screwing up. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Thu Aug 11 18:38:44 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E44C9106566C; Thu, 11 Aug 2011 18:38:44 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8872B8FC15; Thu, 11 Aug 2011 18:38:44 +0000 (UTC) Received: by vxh11 with SMTP id 11so2527314vxh.13 for ; Thu, 11 Aug 2011 11:38:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=s0bx/kCFI6e1nzV75Jj5lCEHTwmQHEVdiwvOgwHFahc=; b=H1RPGQU0z7qzyprWniSV40RPjXZzwd/OiwboHKsAi2wkgUSGjsvV+8up+rAqN3lzZs 1rFwpIcijndJeSHSWrN8w/Rhc5MuFPSI37HmYLd5K0AOSPzzg2Jeaxq6w5bX7d0nx5w/ 53J5A6HrZ5Au5Z+lf+TMMH8qhX+p4MDO8LDMQ= MIME-Version: 1.0 Received: by 10.220.117.136 with SMTP id r8mr1638667vcq.109.1313087923898; Thu, 11 Aug 2011 11:38:43 -0700 (PDT) Received: by 10.220.186.134 with HTTP; Thu, 11 Aug 2011 11:38:43 -0700 (PDT) In-Reply-To: <20110811174512.GA35650@cons.org> References: <20110811160314.GA25076@cons.org> <4E44038F.7000001@FreeBSD.org> <20110811174512.GA35650@cons.org> Date: Thu, 11 Aug 2011 11:38:43 -0700 Message-ID: From: Freddie Cash To: Martin Cracauer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Andriy Gapon Subject: Re: ZFS zpool mirror drive replacement confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 18:38:45 -0000 On Thu, Aug 11, 2011 at 10:45 AM, Martin Cracauer wrote: > Sending snapshots, I was hoping for something that would send all > snapshots at once (a clone of the complete filesystem). > There are options for incremental send (send first snapshot, then send an incremental that includes everything between then and the last snapshot) and for a recursive send that clones the entire filesystem, including all the properties. -i and -R are what you want to look into. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Sat Aug 13 10:53:52 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B79231065670 for ; Sat, 13 Aug 2011 10:53:52 +0000 (UTC) (envelope-from Martin.Birgmeier@aon.at) Received: from email.aon.at (smtpout02.highway.telekom.at [195.3.96.113]) by mx1.freebsd.org (Postfix) with ESMTP id 03E9D8FC18 for ; Sat, 13 Aug 2011 10:53:51 +0000 (UTC) Received: (qmail 10263 invoked from network); 13 Aug 2011 10:53:49 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on WARSBL505.highway.telekom.at X-Spam-Level: Received: from 188-23-213-15.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([188.23.213.15]) (envelope-sender ) by smarthub78.res.a1.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 13 Aug 2011 10:53:49 -0000 Received: from atpcdvvc.xyzzy (atpcdvvc.xyzzy [IPv6:fec0:0:0:4d42::84]) by gandalf.xyzzy (8.14.4/8.14.4) with ESMTP id p7DArnEV013603 for ; Sat, 13 Aug 2011 12:53:49 +0200 (CEST) (envelope-from Martin.Birgmeier@aon.at) Message-ID: <4E4657BD.2090803@aon.at> Date: Sat, 13 Aug 2011 12:53:49 +0200 From: Martin Birgmeier User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:5.0) Gecko/20110708 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Does nfse support specifying multiple exports for one mount point? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Aug 2011 10:53:52 -0000 See http://www.freebsd.org/cgi/query-pr.cgi?pr=147881 - can I specify multiple exports with nfse? I am using the patch proposed in PR 147881, even though I believe it is incomplete (I read that somewhere). For me, it is working fine; for example, I have [0]# zfs list -o name,sharenfs hal.1/backup/dumps NAME SHARENFS hal.1/backup/dumps -network 192.168.0.0 -mask 255.255.0.0;-network fec0:0:0:4d42::/56 [0]# which in /etc/zfs/exports translates to /z/backup/dumps -network 192.168.0.0 -mask 255.255.0.0 /z/backup/dumps -network fec0:0:0:4d42::/56 How can I specify this using nfse? Regards, Martin From owner-freebsd-fs@FreeBSD.ORG Sat Aug 13 11:00:29 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 853E110656A3 for ; Sat, 13 Aug 2011 11:00:29 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8F8A88FC13 for ; Sat, 13 Aug 2011 11:00:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7DB0NUt065068 for ; Sat, 13 Aug 2011 11:00:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7DB0NeT065067; Sat, 13 Aug 2011 11:00:23 GMT (envelope-from gnats) Date: Sat, 13 Aug 2011 11:00:23 GMT Message-Id: <201108131100.p7DB0NeT065067@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/157728: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Aug 2011 11:00:29 -0000 The following reply was made to PR kern/157728; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/157728: commit references a PR Date: Sat, 13 Aug 2011 10:59:07 +0000 (UTC) Author: mm Date: Sat Aug 13 10:58:53 2011 New Revision: 224814 URL: http://svn.freebsd.org/changeset/base/224814 Log: Fix race between dmu_objset_prefetch() invoked from zfs_ioc_dataset_list_next() and dsl_dir_destroy_check() indirectly invoked from dmu_recv_existing_end() via dsl_dataset_destroy() by not prefetching temporary clones, as these count as always inconsistent. In addition, do not prefetch hidden datasets at all as we are not going to process these later. Filed as Illumos Bug #1346 PR: kern/157728 Tested by: Borja Marcos , mm Reviewed by: pjd Approved by: re (kib) MFC after: 1 week Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c ============================================================================== --- head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c Sat Aug 13 10:43:56 2011 (r224813) +++ head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c Sat Aug 13 10:58:53 2011 (r224814) @@ -1964,7 +1964,8 @@ top: int len = sizeof (zc->zc_name) - (p - zc->zc_name); while (dmu_dir_list_next(os, len, p, NULL, &cookie) == 0) - (void) dmu_objset_prefetch(zc->zc_name, NULL); + if (dataset_name_hidden(zc->zc_name) == B_FALSE) + (void) dmu_objset_prefetch(zc->zc_name, NULL); } do { _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org"