From owner-freebsd-fs@FreeBSD.ORG Sun Nov 10 10:15:40 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CD05F82F; Sun, 10 Nov 2013 10:15:40 +0000 (UTC) (envelope-from benjamin.lutz@biolab.ch) Received: from gw01-1.biotronik.org (gw01-1.biotronik.org [91.204.10.44]) by mx1.freebsd.org (Postfix) with ESMTP id 33AF02186; Sun, 10 Nov 2013 10:15:39 +0000 (UTC) X-Disclaimed: 1 MIME-Version: 1.0 In-Reply-To: References: , Subject: Re: Ghost ZFS pool prevents mounting root fs From: Benjamin Lutz To: Artem Belevich X-Mailer: Lotus Domino Web Server Release 8.5.3FP3 November 15, 2012 X-MIMETrack: Serialize by HTTP Server on BIO-DE-MAIL01/SRV/BIOTRONIK(Release 8.5.3FP3|November 15, 2012) at 10.11.2013 11:15:31, Serialize complete at 10.11.2013 11:15:31, Itemize by HTTP Server on BIO-DE-MAIL01/SRV/BIOTRONIK(Release 8.5.3FP3|November 15, 2012) at 10.11.2013 11:15:31, Serialize by Router on GW01-1/SRV/MSC(Release 9.0 HF441|July 23, 2013) at 10.11.2013 11:15:39, Serialize complete at 10.11.2013 11:15:39 Message-ID: X-Priority: 3 (Normal) Importance: Normal Date: Sun, 10 Nov 2013 11:15:31 +0100 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs , Andre Seidelt , Dirk Hoefle X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2013 10:15:41 -0000 Hello Artem, Thanks for the detailed explanation, I think I understand what I need to do= . Since I left the disks with a couple GB of empty space at the end (in cas= e I need to replace them with another model which happens to be a few MB sm= aller), I'll try allocating that space in a partition then zeroing that, wh= ich should prevent any mistakes or calculation errors. If GPT makes the par= tition reach close enough to the end of the disk, that is. And if it doesn'= t, we'll see how dd(1) works as a scalpel. Annoyingly, I can't rely on ZFS here to repair any damage. Since the data s= et is large, scrubs now take about 36 hours. Even if I modfied the 8 affect= ed disks in pairs, it'd take too long. Unless renaming the active tank work= s and resolves the ambiguity, then I can maybe do it while it's working nor= mally. Anyway, thanks again. And sorry about the email formatting, I can't figure = out how to make Lotus Notes do mailing-list-appropriate replies :/ Cheers, Benjamin -- Benjamin Lutz | Software Engineer | BIOLAB=A0Technology AG Dufourstr. 80 | CH-8008 Zurich | www.biolab.ch | benjamin.lutz@biolab.ch PHONE +41 44 295 97 13 | MOBILE +41 79 558 57 13 | FAX +41 44 295 97 19 -----artemb@gmail.com wrote: ----- To: Benjamin Lutz From: Artem Belevich=20 Sent by: artemb@gmail.com Date: 2013-11-08 20:07 Cc: freebsd-fs , Andre Seidelt , Dirk Hoefle Subject: Re: Ghost ZFS pool prevents mounting root fs On Fri, Nov 8, 2013 at 2:53 AM, Benjamin Lutz wro= te: > Hello, > > I have a server here that after trying to reboot during the 9.2 update > process refuses to mount the root file system, which is a ZFS (tank). > > The error message given is: > =A0 Trying to mount root from zfs:tank []... > =A0 Mounting from zfs:tank failed with error 5. > > Adding a mit more verbosity by setting vfs.zfs.debug=3D1 gives one > additional crucial bit of information that probably explains why, it tries > to find the disk /dev/label/disk7, but no such disk exists. I ran into the same issue recently. http://lists.freebsd.org/pipermail/freebsd-fs/2013-November/018496.html > Can you tell me how to resolve the situation, i.e. how to make the ghost > pool go away? I'd rather not recreate the pool or move the data to another > system, since it's around 16TB and would take forever. It should be doable, but usual "YMMV", "proceed at your own risk", "here, there be dragons" warnings apply. [snip] > root@:~ # zdb -l /dev/da1 > -------------------------------------------- > LABEL 0 > -------------------------------------------- > failed to unpack label 0 > -------------------------------------------- > LABEL 1 > -------------------------------------------- > failed to unpack label 1 > -------------------------------------------- > LABEL 2 > -------------------------------------------- > =A0 =A0 version: 28 > =A0 =A0 name: 'tank' > =A0 =A0 state: 2 > =A0 =A0 txg: 61 > =A0 =A0 pool=5Fguid: 4570073208211798611 > =A0 =A0 hostid: 1638041647 > =A0 =A0 hostname: 'blackhole' > =A0 =A0 top=5Fguid: 5554077360160676751 > =A0 =A0 guid: 11488943812765429059 > =A0 =A0 vdev=5Fchildren: 1 > =A0 =A0 vdev=5Ftree: > =A0 =A0 =A0 =A0 type: 'raidz' > =A0 =A0 =A0 =A0 id: 0 > =A0 =A0 =A0 =A0 guid: 5554077360160676751 > =A0 =A0 =A0 =A0 nparity: 3 > =A0 =A0 =A0 =A0 metaslab=5Farray: 30 > =A0 =A0 =A0 =A0 metaslab=5Fshift: 37 > =A0 =A0 =A0 =A0 ashift: 12 > =A0 =A0 =A0 =A0 asize: 16003153002496 > =A0 =A0 =A0 =A0 is=5Flog: 0 > =A0 =A0 =A0 =A0 create=5Ftxg: 4 > =A0 =A0 =A0 =A0 children[0]: > =A0 =A0 =A0 =A0 =A0 =A0 type: 'disk' > =A0 =A0 =A0 =A0 =A0 =A0 id: 0 > =A0 =A0 =A0 =A0 =A0 =A0 guid: 7103686668495146668 > =A0 =A0 =A0 =A0 =A0 =A0 path: '/dev/label/disk0' > =A0 =A0 =A0 =A0 =A0 =A0 phys=5Fpath: '/dev/label/disk0' > =A0 =A0 =A0 =A0 =A0 =A0 whole=5Fdisk: 1 > =A0 =A0 =A0 =A0 =A0 =A0 create=5Ftxg: 4 The ghost labels are at the end of /dev/da1 (and, probably all other drives that used to be part of that pool). In my case I ended up manually zeroing out first sector of offending labels. ZFS places two copies of the labels at 512K and 256K from the end of the pool slice. See ZFS on-disk specification here: http://maczfs.googlecode.com/files/ZFSOnDiskFormat.pdf It's fairly easy to find with: #dd if=3D/dev/da1 bs=3D1m iseek=3D{disk size in mb -1} count=3D1 | hexdump = -C | grep version Once you know where exactly it is, deleting it is simple. Watch out for dd typos or, perhaps use some sort of disk editor to make sure you're not overwriting wrong data. It's a fairly risky operation as you have to make sure you don't nuke anything else by accident. If the disk portion with the labels is currently unallocated, then things are relatively safe. If it's currently used, then you'll need to figure out whether it's safe to overwrite those labels directly or find another way to do it. I.e. if the area with the labels is currently used for some other filesystem, you may be able to get rid of the label by filling up that filesystem with data which would hopefully overwrite labels with something else. If the labels are within the area that is part of the current pool, you are probably safe as it's either in unused area or it's not been used by ZFS yet. In my case the ghost labels were in the neighbourhood of the labels of the current pool and nuking them produced zero errors on scrub. Once you've established that manual label nuking is what you want, here's the recipe: * Make sure risking your data is *really* worth it. Consider erasing drives one-by-one and let raidz repair the pool if you have any doubts. Now that that's out of the way, let's nuke them. * offline one of the drives with the ghost labels or do the operation on an unmounted pool (I've booted from MFSBSD CD). Make sure that it is the right sector you're writing to (i.e. it's the label with wrong disks): * dd if=3D/dev/daN bs=3D512 iseek=3D count=3D10 | hexdump -C Nuke the ghost! Note: you only want to write *one* sector. Make sure you don't forget to edit count if you use shell history and reuse the commend above. * dd if=3D/dev/zero of=3D/dev/daN bs=3D512 oseek=3D{sector that has 'versio= n' word in the label} count=3D1 * make sure "zdb -l /dev/daN" no longer shows ghost label. * online the disk * scrub the pool. In case you made a mistake and wrote to the wrong place that may save your pool. =FFI did the scrub only after I've erased label on the first drive to make sure it didn't damage anything vital. * repeat for all other disks with ghost labels. * run the scrub after all ghost labels have been erased. Just in case. Good luck. --Artem This e-mail and the information it contains including attachments are confi= dential and meant only for use by the intended recipient(s); disclosure or copying is strictl= y prohibited. If you are not addressed, but in the possession of this e-mail, please notify the = sender immediately. From owner-freebsd-fs@FreeBSD.ORG Mon Nov 11 11:06:48 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8E0B091B for ; Mon, 11 Nov 2013 11:06:48 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B3662CAE for ; Mon, 11 Nov 2013 11:06:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rABB6m9u082012 for ; Mon, 11 Nov 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rABB6mx4082010 for freebsd-fs@FreeBSD.org; Mon, 11 Nov 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Nov 2013 11:06:48 GMT Message-Id: <201311111106.rABB6mx4082010@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2013 11:06:48 -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/182570 fs [zfs] [patch] ZFS panic in receive o kern/182536 fs [zfs] zfs deadlock o kern/181966 fs [zfs] Kernel panic in ZFS I/O: solaris assert: BP_EQUA o kern/181834 fs [nfs] amd mounting NFS directories can drive a dead-lo o kern/181565 fs [swap] Problem with vnode-backed swap space. o kern/181377 fs [zfs] zfs recv causes an inconsistant pool o kern/181281 fs [msdosfs] stack trace after successfull 'umount /mnt' o kern/181082 fs [fuse] [ntfs] Write to mounted NTFS filesystem using F o kern/180979 fs [netsmb][patch]: Fix large files handling o kern/180876 fs [zfs] [hast] ZFS with trim,bio_flush or bio_delete loc o kern/180678 fs [NFS] succesfully exported filesystems being reported o kern/180438 fs [smbfs] [patch] mount_smbfs fails on arm because of wr p kern/180236 fs [zfs] [nullfs] Leakage free space using ZFS with nullf o kern/178854 fs [ufs] FreeBSD kernel crash in UFS s kern/178467 fs [zfs] [request] Optimized Checksum Code for ZFS o kern/178412 fs [smbfs] Coredump when smbfs mounted o kern/178388 fs [zfs] [patch] allow up to 8MB recordsize o kern/178387 fs [zfs] [patch] sparse files performance improvements o kern/178349 fs [zfs] zfs scrub on deduped data could be much less see o kern/178329 fs [zfs] extended attributes leak o kern/178238 fs [nullfs] nullfs don't release i-nodes on unlink. f kern/178231 fs [nfs] 8.3 nfsv4 client reports "nfsv4 client/server pr o kern/177985 fs [zfs] disk usage problem when copying from one zfs dat o kern/177971 fs [nfs] FreeBSD 9.1 nfs client dirlist problem w/ nfsv3, o kern/177966 fs [zfs] resilver completes but subsequent scrub reports o kern/177658 fs [ufs] FreeBSD panics after get full filesystem with uf o kern/177536 fs [zfs] zfs livelock (deadlock) with high write-to-disk o kern/177445 fs [hast] HAST panic o kern/177240 fs [zfs] zpool import failed with state UNAVAIL but all d o kern/176978 fs [zfs] [panic] zfs send -D causes "panic: System call i o kern/176857 fs [softupdates] [panic] 9.1-RELEASE/amd64/GENERIC panic o bin/176253 fs zpool(8): zfs pool indentation is misleading/wrong o kern/176141 fs [zfs] sharesmb=on makes errors for sharenfs, and still o kern/175950 fs [zfs] Possible deadlock in zfs after long uptime o kern/175897 fs [zfs] operations on readonly zpool hang o kern/175449 fs [unionfs] unionfs and devfs misbehaviour o kern/175179 fs [zfs] ZFS may attach wrong device on move o kern/175071 fs [ufs] [panic] softdep_deallocate_dependencies: unrecov o kern/174372 fs [zfs] Pagefault appears to be related to ZFS o kern/174315 fs [zfs] chflags uchg not supported o kern/174310 fs [zfs] root point mounting broken on CURRENT with multi o kern/174279 fs [ufs] UFS2-SU+J journal and filesystem corruption o kern/173830 fs [zfs] Brain-dead simple change to ZFS error descriptio o kern/173718 fs [zfs] phantom directory in zraid2 pool f kern/173657 fs [nfs] strange UID map with nfsuserd o kern/173363 fs [zfs] [panic] Panic on 'zpool replace' on readonly poo o kern/173136 fs [unionfs] mounting above the NFS read-only share panic o kern/172942 fs [smbfs] Unmounting a smb mount when the server became o kern/172348 fs [unionfs] umount -f of filesystem in use with readonly o kern/172334 fs [unionfs] unionfs permits recursive union mounts; caus o kern/171626 fs [tmpfs] tmpfs should be noisier when the requested siz o kern/171415 fs [zfs] zfs recv fails with "cannot receive incremental o kern/170945 fs [gpt] disk layout not portable between direct connect o bin/170778 fs [zfs] [panic] FreeBSD panics randomly o kern/170680 fs [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEA o kern/170497 fs [xfs][panic] kernel will panic whenever I ls a mounted o kern/169945 fs [zfs] [panic] Kernel panic while importing zpool (afte o kern/169480 fs [zfs] ZFS stalls on heavy I/O o kern/169398 fs [zfs] Can't remove file with permanent error o kern/169339 fs panic while " : > /etc/123" o kern/169319 fs [zfs] zfs resilver can't complete o kern/168947 fs [nfs] [zfs] .zfs/snapshot directory is messed up when o kern/168942 fs [nfs] [hang] nfsd hangs after being restarted (not -HU o kern/168158 fs [zfs] incorrect parsing of sharenfs options in zfs (fs o kern/167979 fs [ufs] DIOCGDINFO ioctl does not work on 8.2 file syste o kern/167977 fs [smbfs] mount_smbfs results are differ when utf-8 or U o kern/167688 fs [fusefs] Incorrect signal handling with direct_io o kern/167685 fs [zfs] ZFS on USB drive prevents shutdown / reboot o kern/167612 fs [portalfs] The portal file system gets stuck inside po o kern/167272 fs [zfs] ZFS Disks reordering causes ZFS to pick the wron o kern/167260 fs [msdosfs] msdosfs disk was mounted the second time whe o kern/167109 fs [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene o kern/167105 fs [nfs] mount_nfs can not handle source exports wiht mor o kern/167067 fs [zfs] [panic] ZFS panics the server o kern/167065 fs [zfs] boot fails when a spare is the boot disk o kern/167048 fs [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF o kern/166912 fs [ufs] [panic] Panic after converting Softupdates to jo o kern/166851 fs [zfs] [hang] Copying directory from the mounted UFS di o kern/166477 fs [nfs] NFS data corruption. o kern/165950 fs [ffs] SU+J and fsck problem o kern/165521 fs [zfs] [hang] livelock on 1 Gig of RAM with zfs when 31 o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161864 fs [ufs] removing journaling from UFS partition fails on o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic f kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs p kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o bin/153142 fs [zfs] ls -l outputs `ls: ./.zfs: Operation not support o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/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 o kern/145750 fs [unionfs] [hang] unionfs locks the machine s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an f bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141950 fs [unionfs] [lor] ufs/unionfs/ufs Lock order reversal 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/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/137588 fs [unionfs] [lor] LOR nfs/ufs/nfs 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 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 p 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 o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126973 fs [unionfs] [hang] System hang with unionfs and init chr o kern/126553 fs [unionfs] unionfs move directory problem 2 (files appe o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o bin/123574 fs [unionfs] df(1) -t option destroys info for unionfs (a 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 kern/121385 fs [unionfs] unionfs cross mount -> kernel panic o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118318 fs [nfs] NFS server hangs under special circumstances o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o 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/67326 fs [msdosfs] crash after attempt to mount write protected o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t o kern/9619 fs [nfs] Restarting mountd kills existing mounts 336 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Nov 11 16:51:21 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4A146EBC for ; Mon, 11 Nov 2013 16:51:21 +0000 (UTC) (envelope-from Kamil.Choudhury@anserinae.net) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 1133225CA for ; Mon, 11 Nov 2013 16:51:20 +0000 (UTC) Received: from [74.73.121.187] ([74.73.121.187:55945] helo=janus.anserinae.net) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 21/99-27821-20B01825; Mon, 11 Nov 2013 16:51:14 +0000 Received: from JANUS.anserinae.net ([fe80::192c:4b89:9fe9:dc6d]) by janus.anserinae.net ([fe80::192c:4b89:9fe9:dc6d%11]) with mapi id 14.03.0123.003; Mon, 11 Nov 2013 11:51:14 -0500 From: Kamil Choudhury To: "freebsd-fs@freebsd.org" Subject: ZFS iscsi support Thread-Topic: ZFS iscsi support Thread-Index: Ac7e/fYw1DFBFVEFTAuTCU68Vo3tiw== Date: Mon, 11 Nov 2013 16:51:13 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [204.4.182.16] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2013 16:51:21 -0000 Does FreeBSD's ZFS implementation support the shareisci property?=0A= =0A= (FWIW, I'm running 8.3, and am open to upgrading if it is available in a la= tter version.)=0A= =0A= If not, should I just run with istgt from ports? =0A= =0A= Thanks, =0A= Kamil=0A= =0A= From owner-freebsd-fs@FreeBSD.ORG Mon Nov 11 16:56:54 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 427D5182 for ; Mon, 11 Nov 2013 16:56:54 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 15D47261A for ; Mon, 11 Nov 2013 16:56:53 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D526E221D9 for ; Mon, 11 Nov 2013 11:56:46 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Mon, 11 Nov 2013 11:56:47 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=LBIeOvHbJbO+DKbgi/ADtbtC8Rg=; b=sNM jQtiiIyWHz2+C0RIAKuwRgK+RB4prvlffM1vAR3ajbfAVoc4W/DJWQiljoI6GYoK TPn89Tx5/6U0LhniqudJa4ODZpkL4tGHOMbGtReowl1YpvhhBVWnlWXP0F3RDKEk YSIA0xtghiwfsKCkWltsUnnwxrjXEvAYYskL4Sqo= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id A17AB10E880; Mon, 11 Nov 2013 11:56:46 -0500 (EST) Message-Id: <1384189006.28605.45962569.2C86D825@webmail.messagingengine.com> X-Sasl-Enc: zi2D7N8EkuRureti7M8O60nJ87su80a/ZfXGlkLGibr7 1384189006 From: Mark Felder To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-d4893488 In-Reply-To: References: Subject: Re: ZFS iscsi support Date: Mon, 11 Nov 2013 10:56:46 -0600 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2013 16:56:54 -0000 On Mon, Nov 11, 2013, at 10:51, Kamil Choudhury wrote: > Does FreeBSD's ZFS implementation support the shareisci property? > > (FWIW, I'm running 8.3, and am open to upgrading if it is available in a > latter version.) > > If not, should I just run with istgt from ports? > No, it's not supported at this time. You should either run istgt or use the built-in iSCSI daemon (ctld) in FreeBSD 10. From owner-freebsd-fs@FreeBSD.ORG Mon Nov 11 17:26:19 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A9578EB3 for ; Mon, 11 Nov 2013 17:26:19 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ee0-x231.google.com (mail-ee0-x231.google.com [IPv6:2a00:1450:4013:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3FA782890 for ; Mon, 11 Nov 2013 17:26:19 +0000 (UTC) Received: by mail-ee0-f49.google.com with SMTP id b15so1244085eek.8 for ; Mon, 11 Nov 2013 09:26:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=m540ZdmPfoGU+2lMYZ9oRFx4FylhPkkWtFEkMh1wAPo=; b=q/qBbYm0jTrHhzFYxz7eBmNCYvtGML1kmmambCM01306OPZhO8+i7vvnIJQdXxlnQN nOPjGr5ls4vh/IMfWYNl1HO9eHxeaMf9Q+oFDsDXfUwa2lhhCnAi9qelpStJf3ur2atr BpVHvxNYby40JCRfUTc9/zR/XLDqkUs5YM0lT5gsAr9wxo/iA0+xBkF4QnA4ssBWUIw9 tyGBJI6m9Ur/Nyz0HZrZdw8ghNjYigrRxsUKhNB3SgH6rSPXVXmLptHBYF3tEkXeu4M/ GXDP3v7RxlTYizyeo8fMipSvicEgIVs9qOfkk1v+wjHPK9yl0eG0TMAbqEVc8mXplGXK LbPQ== X-Received: by 10.14.113.137 with SMTP id a9mr35869862eeh.3.1384190777545; Mon, 11 Nov 2013 09:26:17 -0800 (PST) Received: from [192.168.1.102] (45.81.datacomsa.pl. [195.34.81.45]) by mx.google.com with ESMTPSA id k7sm57115292eeg.13.2013.11.11.09.26.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Nov 2013 09:26:17 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: ZFS iscsi support Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: Date: Mon, 11 Nov 2013 18:26:13 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8384835A-FB83-4122-9C36-0D4715C5DCF8@FreeBSD.org> References: To: Kamil Choudhury X-Mailer: Apple Mail (2.1283) Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2013 17:26:19 -0000 Wiadomo=B6=E6 napisana przez Kamil Choudhury w dniu 11 lis 2013, o godz. = 17:51: > Does FreeBSD's ZFS implementation support the shareisci property? No, and since it got obsoleted by upstream it's unlikely to get = implemented. Just create ZVOLs and configure your iSCSI target of choice to share = them. --=20 If you cut off my head, what would I say? Me and my head, or me and my = body? From owner-freebsd-fs@FreeBSD.ORG Mon Nov 11 21:00:43 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 66AD9729 for ; Mon, 11 Nov 2013 21:00:43 +0000 (UTC) (envelope-from sean_bruno@yahoo.com) Received: from nm6.bullet.mail.bf1.yahoo.com (nm6.bullet.mail.bf1.yahoo.com [98.139.212.165]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 034402749 for ; Mon, 11 Nov 2013 21:00:42 +0000 (UTC) Received: from [98.139.215.143] by nm6.bullet.mail.bf1.yahoo.com with NNFMP; 11 Nov 2013 21:00:36 -0000 Received: from [98.139.213.11] by tm14.bullet.mail.bf1.yahoo.com with NNFMP; 11 Nov 2013 21:00:36 -0000 Received: from [127.0.0.1] by smtp111.mail.bf1.yahoo.com with NNFMP; 11 Nov 2013 21:00:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1384203636; bh=hvQW99sslxUaKZBzNKmpU+TZxOQo43/pwQUdveMhyQ0=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=0FuKae4+FH93nPzysm0NPy7dBMhlJmiC++Q56UWrDKtZ1kOtxvypYBF2SGLBt2TUwDqrmMon1VyLzgtHsuQsrFkYjBN1Z9O7M8QmmTG/sNpOAmd9/EPPiSNfhdZP2DhZJxTWfRGrb0u8+S2pGbSeWZY3jTMCBYMqQzjCTh+SapI= X-Yahoo-Newman-Id: 471490.34240.bm@smtp111.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: RutiqocVM1k.62XzeOpJdTMXChwuMSyBRSOHyBwMV.aKKbb TZrRKKqwSc9PzZWbwQ8rRdszCB4YfDkx_v7kanBI6uWTA6O6q_Xr6DOec4TR AyL5aqoEjQ1CtwnshBMt5dvck5MG9OBcx.Cj_ENrAGyXSkGBkq0VM9df032c jQ7thDr72FaE_IzhrrPiYVvRMys_eUqJ6xOlYQDDxrLZypio5IowXFnJk.cc 39QjIPscoPuDA7cua1CsWY79YEhb7YdhqVyXWPorkSqJADDGrfP2c14eIHxd 1Cv51s_20z7JXgT8I3C00_MbR1pTdGxz2auhGwmLb2g6kymk8SvSidlDc0rV 1Oyq6Rot_AtcbRTqYLSSWySJxiX1cXZA1S52WDkhiCXo.sNuUd6B_a75etmB jZDECGMQC3OWZMsy4vuzgGJSt28btbCEestiC2_iLfcSjITKDETObdqytfTj 0tr11DG2KjUSzLviPuJjqVIT6i6FYfAG_PRmE1xgxGWDDIXb5QTy4eH8EgUL xL.GS5VJ0.SPV.LrQFKl6wAbrX7CnVA3EdAgi2kSJ3fpP3Q9yHg_1UQbyzBI HQJczmeX0_UNCds0ZnDl1XOeaNTR0Hj1qB8Pq.btlqVF1FV0o8cCGrBXTTTB cd99HaI417WXgK_9ZgxuOi2gNJZb37EWzeKreZZRXVUThjCwX2as- X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [10.73.160.242] (sean_bruno@209.131.62.116 with ) by smtp111.mail.bf1.yahoo.com with SMTP; 11 Nov 2013 13:00:36 -0800 PST Subject: Re: [CFR] printf format changes From: Sean Bruno To: Bruce Evans In-Reply-To: <20131109183432.R907@besplex.bde.org> References: <1383961188.1526.10.camel@powernoodle.corp.yahoo.com> <20131109183432.R907@besplex.bde.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-c6B1ZI+Ea46ONCCQllKK" Date: Mon, 11 Nov 2013 13:00:35 -0800 Message-ID: <1384203635.1748.49.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2013 21:00:43 -0000 --=-c6B1ZI+Ea46ONCCQllKK Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Sat, 2013-11-09 at 19:36 +1100, Bruce Evans wrote: > On Fri, 8 Nov 2013, Sean Bruno wrote: >=20 > > http://people.freebsd.org/~sbruno/freebsd_libzfs_printf_changes.txt > > > > Some minor nits from compiles. Tested on i386/amd64 with clang. > > > > Not sure how to test with gcc though. >=20 > Every part of the patch that I can see in the mail (that is, none) is > correct. svn mail sends much larger diffs than this. >=20 > After fetching the patch: >=20 > % Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c > % =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > % --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c (revisi= on 257859) > % +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c (workin= g copy) > % @@ -2134,7 +2134,7 @@ > % localtime_r(&time, &t) =3D=3D NULL || > % strftime(propbuf, proplen, "%a %b %e %k:%M %Y", > % &t) =3D=3D 0) > % - (void) snprintf(propbuf, proplen, "%llu", val); > % + (void) snprintf(propbuf, proplen, "%ju", (intmax_t)val); > % } > % break; > % >=20 > Style bug: line expanded beyond 80 columns. The vendor code is fairly > careful about this, but has plenty of other things that I don't like, > starting with obfuscating format strings to avoid long lines. >=20 > Style bug: non-use of the long long abomination. The vendor won't > like your fix. They prefer to use the abomination. They keep using > the abomination in the format (%llu) and spell the cast '(ulonglong_t)' > in many places in this file, but this patch shows that they missed many. >=20 > Type mismatches: `val' starts as an unsigned type (uint64_t) but is cast > to a signed type (intmax_t). This gives another type mismatch with the > the format, which requires a signed type. You may be able to prove that > the behaviour is defined and correct on all arches after studying the > C standard for less than a week. It is much easier to see that it is > correct, and possibly even defined, in the usual case where intmax_t and > uintmax_t are 64 bits. >=20 > The vendor code has these type mismatches in 2 places (Sep 10 version). > The vendor casts to longlong_t where they should cast to ulonglong_t. > They consistently use the unsigned format (%llu; never %lld). >=20 > % @@ -2648,7 +2648,7 @@ > % return (err); > %=20 > % if (literal) { > % - (void) snprintf(propbuf, proplen, "%llu", propvalue); > % + (void) snprintf(propbuf, proplen, "%ju", (intmax_t)propvalue); > % } else if (propvalue =3D=3D 0 && > % (type =3D=3D ZFS_PROP_USERQUOTA || type =3D=3D ZFS_PROP_GROUPQUOT= A)) { > % (void) strlcpy(propbuf, "none", proplen); >=20 > As above, except for the long line. >=20 > Unfortunately, using the vendor spelling of the cast will make the line t= oo > long. >=20 > All the changes have much the same bugs. No further comment on ones that > have a subset of the above. >=20 > % ... > % Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_diff.c > % =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > % --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_diff.c (revision = 257859) > % +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_diff.c (working c= opy) > % @@ -116,7 +116,7 @@ > % (void) snprintf(di->errbuf, sizeof (di->errbuf), > % dgettext(TEXT_DOMAIN, > % "Unable to determine path or stats for " > % - "object %lld in %s"), obj, dsname); > % + "object %jd in %s"), (intmax_t)obj, dsname); > % return (-1); > % } > % } >=20 > 'obj' starts as an unsigned type (uint64_t), but is converted to a signed > type for printing in a signed format. Perhaps that is intended. No > further comment on this. >=20 > % Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c > % =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > % --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c (revision = 257859) > % +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c (working c= opy) > % @@ -1472,15 +1472,15 @@ > % } > % if (loss > 120) { > % (void) printf(dgettext(TEXT_DOMAIN, > % - "%s approximately %lld "), > % + "%s approximately %jd "), > % dryrun ? "Would discard" : "Discarded", > % - (loss + 30) / 60); > % + (intmax_t)(loss + 30) / 60); > % (void) printf(dgettext(TEXT_DOMAIN, > % "minutes of transactions.\n")); >=20 > 'loss' is signed (int64_t), so the signed format is clearly correct. >=20 > % Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c > % =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > % --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c (revis= ion 257859) > % +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c (worki= ng copy) > % @@ -2083,7 +2083,7 @@ > % needagain =3D B_TRUE; > % else > % progress =3D B_TRUE; > % - sprintf(guidname, "%lu", thisguid); > % + sprintf(guidname, "%ju", (uintmax_t)thisguid); > % nvlist_add_boolean(deleted, guidname); > % continue; > % } >=20 > The vendor used a very wrong format here. No furthe comment on this. >=20 > % @@ -3081,8 +3081,8 @@ > % zfs_nicenum(bytes, buf1, sizeof (buf1)); > % zfs_nicenum(bytes/delta, buf2, sizeof (buf1)); > %=20 > % - (void) printf("received %sB stream in %lu seconds (%sB/sec)\n", > % - buf1, delta, buf2); > % + (void) printf("received %sB stream in %ld seconds (%sB/sec)\n", > % + buf1, (unsigned long)delta, buf2); > % } > %=20 > % return (0); >=20 > Various type mismatches: delta is time_t which was supposed to be fully > opaque (C) but is an integer type with a specified representation of time= s > (POSIX). It can be signed or unsigned, but it is usually signed. It onl= y > needs to be signed to represent times before the Epoch and negative time > differences. Printing it using a signed format is the easiest way to > allow for it having negative differences without having to decide if they > can happen, although this is not strictly correct. Here you change the > format to signed for no apparent reason and then get a type mismatch by > casting the arg to unsigned. Both should be to signed. But let the > vendor decide this and keep the unsigned format. >=20 > Overflow errors: some systems have 64-bit time_t to avoid overflow errors= . > Casting to long or unsigned long breaks this on 32-bit systems for times > later than 2038. Times later than 2038 are probably not needed here, so > let the vendor decide this too, by keeping the %lu format and casting the > arg to match it. >=20 > Bruce Updated patch for libzfs. I've continued the (longlong_t) nonsense as it matches the vendor code, wrapped any lines that go past 80 and reset the cast and printf() for the time_t argument. This patch is being sent to illumos for review as issue 4309. http://people.freebsd.org/~sbruno/libzfs_update_casting.txt Patch txt as follows: Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c (revision 2= 57998) +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c (working co= py) @@ -2134,7 +2134,8 @@ localtime_r(&time, &t) =3D=3D NULL || strftime(propbuf, proplen, "%a %b %e %k:%M %Y", &t) =3D=3D 0) - (void) snprintf(propbuf, proplen, "%llu", val); + (void) snprintf(propbuf, proplen, "%llu", + (u_longlong_t)val); } break; =20 @@ -2648,7 +2649,8 @@ return (err); =20 if (literal) { - (void) snprintf(propbuf, proplen, "%llu", propvalue); + (void) snprintf(propbuf, proplen, "%llu", + (u_longlong_t)propvalue); } else if (propvalue =3D=3D 0 && (type =3D=3D ZFS_PROP_USERQUOTA || type =3D=3D ZFS_PROP_GROUPQUOTA)) = { (void) strlcpy(propbuf, "none", proplen); @@ -2705,7 +2707,8 @@ return (err); =20 if (literal) { - (void) snprintf(propbuf, proplen, "%llu", propvalue); + (void) snprintf(propbuf, proplen, "%llu", + (u_longlong_t)propvalue); } else { zfs_nicenum(propvalue, propbuf, proplen); } Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_diff.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_diff.c (revision 2579= 98) +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_diff.c (working copy) @@ -116,7 +116,7 @@ (void) snprintf(di->errbuf, sizeof (di->errbuf), dgettext(TEXT_DOMAIN, "Unable to determine path or stats for " - "object %lld in %s"), obj, dsname); + "object %lld in %s"), (longlong_t)obj, dsname); return (-1); } } @@ -410,7 +410,7 @@ (void) snprintf(di->errbuf, sizeof (di->errbuf), dgettext(TEXT_DOMAIN, "next allocated object (> %lld) find failure"), - zc.zc_obj); + (longlong_t)(zc.zc_obj)); di->zerr =3D errno; break; } Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c (revision 2579= 98) +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c (working copy) @@ -261,7 +261,8 @@ =20 case ZPOOL_PROP_GUID: intval =3D zpool_get_prop_int(zhp, prop, &src); - (void) snprintf(buf, len, "%llu", intval); + (void) snprintf(buf, len, "%llu", + (u_longlong_t)intval); break; =20 case ZPOOL_PROP_ALTROOT: @@ -337,7 +338,8 @@ } /* FALLTHROUGH */ default: - (void) snprintf(buf, len, "%llu", intval); + (void) snprintf(buf, len, "%llu", + (u_longlong_t)intval); } break; =20 @@ -1474,13 +1476,14 @@ (void) printf(dgettext(TEXT_DOMAIN, "%s approximately %lld "), dryrun ? "Would discard" : "Discarded", - (loss + 30) / 60); + (longlong_t)(loss + 30) / 60); (void) printf(dgettext(TEXT_DOMAIN, "minutes of transactions.\n")); } else if (loss > 0) { (void) printf(dgettext(TEXT_DOMAIN, "%s approximately %lld "), - dryrun ? "Would discard" : "Discarded", loss); + dryrun ? "Would discard" : "Discarded", + (longlong_t)loss); (void) printf(dgettext(TEXT_DOMAIN, "seconds of transactions.\n")); } @@ -1534,11 +1537,13 @@ if (loss > 120) { (void) printf(dgettext(TEXT_DOMAIN, "Approximately %lld minutes of data\n" - "\tmust be discarded, irreversibly. "), (loss + 30) / 60); + "\tmust be discarded, irreversibly. "), + (longlong_t)(loss + 30) / 60); } else if (loss > 0) { (void) printf(dgettext(TEXT_DOMAIN, "Approximately %lld seconds of data\n" - "\tmust be discarded, irreversibly. "), loss); + "\tmust be discarded, irreversibly. "), + (longlong_t)loss); } if (edata !=3D 0 && edata !=3D UINT64_MAX) { if (edata =3D=3D 1) { @@ -2524,7 +2529,7 @@ libzfs_handle_t *hdl =3D zhp->zpool_hdl; =20 (void) snprintf(msg, sizeof (msg), - dgettext(TEXT_DOMAIN, "cannot fault %llu"), guid); + dgettext(TEXT_DOMAIN, "cannot fault %llu"), (u_longlong_t)guid); =20 (void) strlcpy(zc.zc_name, zhp->zpool_name, sizeof (zc.zc_name)); zc.zc_guid =3D guid; @@ -2559,7 +2564,7 @@ libzfs_handle_t *hdl =3D zhp->zpool_hdl; =20 (void) snprintf(msg, sizeof (msg), - dgettext(TEXT_DOMAIN, "cannot degrade %llu"), guid); + dgettext(TEXT_DOMAIN, "cannot degrade %llu"), (u_longlong_t)guid); =20 (void) strlcpy(zc.zc_name, zhp->zpool_name, sizeof (zc.zc_name)); zc.zc_guid =3D guid; @@ -3228,7 +3233,7 @@ =20 (void) snprintf(msg, sizeof (msg), dgettext(TEXT_DOMAIN, "cannot clear errors for %llx"), - guid); + (longlong_t)guid); =20 (void) strlcpy(zc.zc_name, zhp->zpool_name, sizeof (zc.zc_name)); zc.zc_guid =3D guid; @@ -3793,7 +3798,8 @@ =20 if (dsobj =3D=3D 0) { /* special case for the MOS */ - (void) snprintf(pathname, len, ":<0x%llx>", obj); + (void) snprintf(pathname, len, ":<0x%llx>", + (longlong_t)obj); return; } =20 @@ -3804,7 +3810,7 @@ ZFS_IOC_DSOBJ_TO_DSNAME, &zc) !=3D 0) { /* just write out a path of two object numbers */ (void) snprintf(pathname, len, "<0x%llx>:<0x%llx>", - dsobj, obj); + (longlong_t)dsobj, (longlong_t)obj); return; } (void) strlcpy(dsname, zc.zc_value, sizeof (dsname)); @@ -3825,7 +3831,8 @@ dsname, zc.zc_value); } } else { - (void) snprintf(pathname, len, "%s:<0x%llx>", dsname, obj); + (void) snprintf(pathname, len, "%s:<0x%llx>", dsname, + (longlong_t)obj); } free(mntpnt); } Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c (revision = 257998) +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c (working c= opy) @@ -2083,7 +2083,8 @@ needagain =3D B_TRUE; else progress =3D B_TRUE; - sprintf(guidname, "%lu", thisguid); + sprintf(guidname, "%llu", + (u_longlong_t)thisguid); nvlist_add_boolean(deleted, guidname); continue; } @@ -2140,7 +2141,7 @@ needagain =3D B_TRUE; else progress =3D B_TRUE; - sprintf(guidname, "%lu", parent_fromsnap_guid); + sprintf(guidname, "%llu", (u_longlong_t)parent_fromsnap_guid); nvlist_add_boolean(deleted, guidname); continue; } @@ -2173,7 +2174,7 @@ if (stream_parent_fromsnap_guid !=3D 0 && parent_fromsnap_guid !=3D 0 && stream_parent_fromsnap_guid !=3D parent_fromsnap_guid)= { - sprintf(guidname, "%lu", parent_fromsnap_guid); + sprintf(guidname, "%ju", (uintmax_t)parent_fromsnap_guid); if (nvlist_exists(deleted, guidname)) { progress =3D B_TRUE; needagain =3D B_TRUE; Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_util.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_util.c (revision 2579= 98) +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_util.c (working copy) @@ -586,13 +586,13 @@ u =3D " KMGTPE"[index]; =20 if (index =3D=3D 0) { - (void) snprintf(buf, buflen, "%llu", n); + (void) snprintf(buf, buflen, "%llu", (u_longlong_t)n); } else if ((num & ((1ULL << 10 * index) - 1)) =3D=3D 0) { /* * If this is an even multiple of the base, always display * without any decimal precision. */ - (void) snprintf(buf, buflen, "%llu%c", n, u); + (void) snprintf(buf, buflen, "%llu%c", (u_longlong_t)n, u); } else { /* * We want to choose a precision that reflects the best choice --=-c6B1ZI+Ea46ONCCQllKK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (FreeBSD) iQEcBAABAgAGBQJSgUVyAAoJEBkJRdwI6BaHBagH/iQq25mba7DjXpnyQrizweak zC0ZNjXO1FXFLsgDqj01tFP9GA3Zbja6a8v1AnLMgqSX+Wqdxdbx9GpSX8kKZp05 tfctN773aYc1rZnOXWyBgZhyDGvv6vbeqsrZIy7ZHOw+62CoaU4ztWPHKgPXVgMk 9kq5kte+R/7NuQRheOVL7eOp3btm0uHreVXTi46DblaiH/JKrEQmTTDicptBkpHC CRRSqZnfrk78O+kb2/sk/fwouE1fVUSmOY9/L+N4qb1CNk52FRrNgLFZhgFLU4tY eQdVJY1UY+3XRkP7liz9V0zpjH9G8OZuiLzI0kMMa8WvHKZxWZHCVH6aQ0v+O3k= =rBtX -----END PGP SIGNATURE----- --=-c6B1ZI+Ea46ONCCQllKK-- From owner-freebsd-fs@FreeBSD.ORG Tue Nov 12 07:54:45 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBDA4D1C; Tue, 12 Nov 2013 07:54:45 +0000 (UTC) Received: from mail110.syd.optusnet.com.au (mail110.syd.optusnet.com.au [211.29.132.97]) by mx1.freebsd.org (Postfix) with ESMTP id 6A403271C; Tue, 12 Nov 2013 07:54:44 +0000 (UTC) Received: from c122-106-156-23.carlnfd1.nsw.optusnet.com.au (c122-106-156-23.carlnfd1.nsw.optusnet.com.au [122.106.156.23]) by mail110.syd.optusnet.com.au (Postfix) with ESMTPS id E7592780F69; Tue, 12 Nov 2013 18:54:34 +1100 (EST) Date: Tue, 12 Nov 2013 18:54:32 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: sbruno@freebsd.org Subject: Re: [CFR] printf format changes In-Reply-To: <1384203635.1748.49.camel@powernoodle.corp.yahoo.com> Message-ID: <20131112183651.Q1059@besplex.bde.org> References: <1383961188.1526.10.camel@powernoodle.corp.yahoo.com> <20131109183432.R907@besplex.bde.org> <1384203635.1748.49.camel@powernoodle.corp.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=DstvpgP+ c=1 sm=1 tr=0 a=ebeQFi2P/qHVC0Yw9JDJ4g==:117 a=PO7r1zJSAAAA:8 a=kj9zAlcOel0A:10 a=JzwRw_2MAAAA:8 a=rXxADq7T2ngA:10 a=6I5d2MoRAAAA:8 a=3oChjJZv1zds7kc0A60A:9 a=CjuIK1q_8ugA:10 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2013 07:54:46 -0000 On Mon, 11 Nov 2013, Sean Bruno wrote: > Updated patch for libzfs. I've continued the (longlong_t) nonsense as > it matches the vendor code, wrapped any lines that go past 80 and reset > the cast and printf() for the time_t argument. This patch is being sent > to illumos for review as issue 4309. > > http://people.freebsd.org/~sbruno/libzfs_update_casting.txt > > Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c > =================================================================== > --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c (revision 257998) > +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c (working copy) > @@ -2134,7 +2134,8 @@ > localtime_r(&time, &t) == NULL || > strftime(propbuf, proplen, "%a %b %e %k:%M %Y", > &t) == 0) > - (void) snprintf(propbuf, proplen, "%llu", val); > + (void) snprintf(propbuf, proplen, "%llu", > + (u_longlong_t)val); > } > break; > Next note that the vendor mostly uses KNF. This uses gnu style for the change, despite a 3-line example of KNF continuation indentation being visible in the same part of the patch. > @@ -2648,7 +2649,8 @@ > return (err); > > if (literal) { > - (void) snprintf(propbuf, proplen, "%llu", propvalue); > + (void) snprintf(propbuf, proplen, "%llu", > + (u_longlong_t)propvalue); > } else if (propvalue == 0 && > (type == ZFS_PROP_USERQUOTA || type == ZFS_PROP_GROUPQUOTA)) { > (void) strlcpy(propbuf, "none", proplen); gnu style. > @@ -2705,7 +2707,8 @@ > return (err); > > if (literal) { > - (void) snprintf(propbuf, proplen, "%llu", propvalue); > + (void) snprintf(propbuf, proplen, "%llu", > + (u_longlong_t)propvalue); > } else { > zfs_nicenum(propvalue, propbuf, proplen); > } gnu style. > Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c > =================================================================== > --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c (revision 257998) > +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c (working copy) > @@ -261,7 +261,8 @@ > > case ZPOOL_PROP_GUID: > intval = zpool_get_prop_int(zhp, prop, &src); > - (void) snprintf(buf, len, "%llu", intval); > + (void) snprintf(buf, len, "%llu", > + (u_longlong_t)intval); > break; > > case ZPOOL_PROP_ALTROOT: gnu style. > @@ -337,7 +338,8 @@ > } > /* FALLTHROUGH */ > default: > - (void) snprintf(buf, len, "%llu", intval); > + (void) snprintf(buf, len, "%llu", > + (u_longlong_t)intval); > } > break; > gnu style. > @@ -3228,7 +3233,7 @@ > > (void) snprintf(msg, sizeof (msg), > dgettext(TEXT_DOMAIN, "cannot clear errors for %llx"), > - guid); > + (longlong_t)guid); > > (void) strlcpy(zc.zc_name, zhp->zpool_name, sizeof (zc.zc_name)); > zc.zc_guid = guid; Sign mismatch in type in the cast. It matches neither the variable nor the format. > @@ -3793,7 +3798,8 @@ > > if (dsobj == 0) { > /* special case for the MOS */ > - (void) snprintf(pathname, len, ":<0x%llx>", obj); > + (void) snprintf(pathname, len, ":<0x%llx>", > + (longlong_t)obj); > return; > } > Sign mismatch. > @@ -3804,7 +3810,7 @@ > ZFS_IOC_DSOBJ_TO_DSNAME, &zc) != 0) { > /* just write out a path of two object numbers */ > (void) snprintf(pathname, len, "<0x%llx>:<0x%llx>", > - dsobj, obj); > + (longlong_t)dsobj, (longlong_t)obj); > return; > } > (void) strlcpy(dsname, zc.zc_value, sizeof (dsname)); Sign mismatch. > @@ -3825,7 +3831,8 @@ > dsname, zc.zc_value); > } > } else { > - (void) snprintf(pathname, len, "%s:<0x%llx>", dsname, obj); > + (void) snprintf(pathname, len, "%s:<0x%llx>", dsname, > + (longlong_t)obj); > } > free(mntpnt); > } Sign mismatch. > Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c > =================================================================== > --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c (revision 257998) > +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c (working copy) > @@ -2083,7 +2083,8 @@ > needagain = B_TRUE; > else > progress = B_TRUE; > - sprintf(guidname, "%lu", thisguid); > + sprintf(guidname, "%llu", > + (u_longlong_t)thisguid); > nvlist_add_boolean(deleted, guidname); > continue; > } gnu style. > @@ -2140,7 +2141,7 @@ > needagain = B_TRUE; > else > progress = B_TRUE; > - sprintf(guidname, "%lu", parent_fromsnap_guid); > + sprintf(guidname, "%llu", (u_longlong_t)parent_fromsnap_guid); > nvlist_add_boolean(deleted, guidname); > continue; > } Line too long. > @@ -2173,7 +2174,7 @@ > if (stream_parent_fromsnap_guid != 0 && > parent_fromsnap_guid != 0 && > stream_parent_fromsnap_guid != parent_fromsnap_guid) { > - sprintf(guidname, "%lu", parent_fromsnap_guid); > + sprintf(guidname, "%ju", (uintmax_t)parent_fromsnap_guid); > if (nvlist_exists(deleted, guidname)) { > progress = B_TRUE; > needagain = B_TRUE; Doesn't use ulonglong_t. Line too long. I think I found all the errors. Bruce From owner-freebsd-fs@FreeBSD.ORG Tue Nov 12 12:28:32 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 70120C73 for ; Tue, 12 Nov 2013 12:28:32 +0000 (UTC) Received: from mail-bk0-x234.google.com (mail-bk0-x234.google.com [IPv6:2a00:1450:4008:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EC0FA2800 for ; Tue, 12 Nov 2013 12:28:31 +0000 (UTC) Received: by mail-bk0-f52.google.com with SMTP id v10so2145319bkz.25 for ; Tue, 12 Nov 2013 04:28:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=aO9P7/rPEVgbtwOJC/9rtl5+LQGLbIjqQPBl5GrCRTI=; b=GrOqbCX0n/fzIPpX1XZgEsY+WI9lAB2NOlwQ9toHquj88uOUoP6XqWw47gjRGUm59t T+IkyzCLknpPVxai1hKLgA+dtyEiFtGQRMnuj67mIUUf8k+IODxoiqx7sOi9b8jJh0UG EKAIAgUDPPsKeiWPHiBMWaqzhcdSn2wFwOC3KZ80EtBUg//FQutd+OwPVwEk12ocLIt8 t/IGfMrngxZHnx8Hi0cmZFb+33lRoupSOT90Z9H+78j0WHGF+SQKvdNn/FTscM/YKxGF Hh3Ktv/MFCGOGYQp5HtY7W0XBDGfTT/WF872MVzCytjvKGxweyMKOuqRuwBHPvT0nQwk 4CUw== X-Received: by 10.204.226.75 with SMTP id iv11mr6943bkb.161.1384259310261; Tue, 12 Nov 2013 04:28:30 -0800 (PST) Received: from endymion.local ([88.203.210.106]) by mx.google.com with ESMTPSA id b7sm17957620bkg.1.2013.11.12.04.28.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Nov 2013 04:28:29 -0800 (PST) Message-ID: <52821EEE.5040502@gmail.com> Date: Tue, 12 Nov 2013 14:28:30 +0200 From: Ivan Dimitrov User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Strange lock/crash - 100% cpu with basic command line utils Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2013 12:28:32 -0000 Hello list This is my first time reporting a problem, so please excuse me if this is not the right place or format. Also apology for my poor English. Last month we started experiencing strange locks on some of our servers. On semi-random occasions, when typing `cd`, `ls`, `pwd` the server would crash and start behave strangely. Sometimes the problem is reproducible, sometimes all commands work as expected. All servers are Intel or AMD CPUs with FreeBSD 9.2 that netboot the latest kernel and load the OS in RAM. All our servers are using zfs with ssd for cache. Here is an example server: Also we tested out with preempted and non preempted kernel. ========================================== [root@ph3storage5 ~]# zpool status -v pool: zstorage5p1 state: ONLINE scan: scrub repaired 0 in 39h36m with 0 errors on Mon Nov 4 05:11:48 2013 config: NAME STATE READ WRITE CKSUM zstorage5p1 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 cache ada4p1 ONLINE 0 0 0 errors: No known data errors pool: zstorage5p2 state: ONLINE scan: scrub repaired 0 in 14h59m with 0 errors on Sun Nov 3 04:41:50 2013 config: NAME STATE READ WRITE CKSUM zstorage5p2 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 cache ada4p2 ONLINE 0 0 0 errors: No known data errors ========================================== The typical lock would look like the following: cd ~userdir/ ; ls At this point, the ls command "freezes" and cannot be "ctrl+c". We open up another console and see that the `ls` command is using 100% CPU. Also, some disk operations randomly start taking 1 to 2 minutes to complete. For example, we used `camcontrol` a few times, and it freezed at one point. Also (while crashed) we used zpool to remove the ssd cache from the pool, than we re-added the cache back to the pool, but when we issued zpool status, the command freezed for a minute. We managed to collect some data from two different incidents Incident 1: http://pastebin.com/EkCeSwY9 Incident 2: http://pastebin.com/5rj9BV68 Since the problem is reproducible, we accept proposals how to do further tests. Thanks in advance Best Regards Ivan Dimitrov From owner-freebsd-fs@FreeBSD.ORG Tue Nov 12 13:28:06 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A75F2DDF for ; Tue, 12 Nov 2013 13:28:06 +0000 (UTC) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 493A82BED for ; Tue, 12 Nov 2013 13:28:06 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50006695317.msg for ; Tue, 12 Nov 2013 13:27:56 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Tue, 12 Nov 2013 13:27:56 +0000 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1028112938=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Ivan Dimitrov" , References: <52821EEE.5040502@gmail.com> Subject: Re: Strange lock/crash - 100% cpu with basic command line utils Date: Tue, 12 Nov 2013 13:27:49 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2013 13:28:06 -0000 ----- Original Message ----- From: "Ivan Dimitrov" To: Sent: Tuesday, November 12, 2013 12:28 PM Subject: Strange lock/crash - 100% cpu with basic command line utils > Hello list > > This is my first time reporting a problem, so please excuse me if this > is not the right place or format. Also apology for my poor English. > > Last month we started experiencing strange locks on some of our servers. > On semi-random occasions, when typing `cd`, `ls`, `pwd` the server would > crash and start behave strangely. Sometimes the problem is reproducible, > sometimes all commands work as expected. > All servers are Intel or AMD CPUs with FreeBSD 9.2 that netboot the > latest kernel and load the OS in RAM. > All our servers are using zfs with ssd for cache. Here is an example > server: > Also we tested out with preempted and non preempted kernel. > > ========================================== > > [root@ph3storage5 ~]# zpool status -v > pool: zstorage5p1 > state: ONLINE > scan: scrub repaired 0 in 39h36m with 0 errors on Mon Nov 4 05:11:48 > 2013 > config: > > NAME STATE READ WRITE CKSUM > zstorage5p1 ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada0 ONLINE 0 0 0 > ada1 ONLINE 0 0 0 > cache > ada4p1 ONLINE 0 0 0 > > errors: No known data errors > > pool: zstorage5p2 > state: ONLINE > scan: scrub repaired 0 in 14h59m with 0 errors on Sun Nov 3 04:41:50 > 2013 > config: > > NAME STATE READ WRITE CKSUM > zstorage5p2 ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 > cache > ada4p2 ONLINE 0 0 0 > > errors: No known data errors > > ========================================== > The typical lock would look like the following: > cd ~userdir/ ; ls > At this point, the ls command "freezes" and cannot be "ctrl+c". > We open up another console and see that the `ls` command is using 100% > CPU. Also, some disk operations randomly start taking 1 to 2 minutes to > complete. For example, we used `camcontrol` a few times, and it freezed > at one point. > Also (while crashed) we used zpool to remove the ssd cache from the > pool, than we re-added the cache back to the pool, but when we issued > zpool status, the command freezed for a minute. > > We managed to collect some data from two different incidents > > Incident 1: http://pastebin.com/EkCeSwY9 > Incident 2: http://pastebin.com/5rj9BV68 > > Since the problem is reproducible, we accept proposals how to do further > tests. This may be off the mark, as I've not seen 100% CPU, but we have seen random unexplained hangs when connecting to some new machines here and it turned out to be a simple lack of mbufs caused by the fact the machines have 6 Intel igb nic's. So the command wasn't hanging at all it was the output over ssh which was hanging due to lack of mbufs to send the output to the client. If you run "netstat -m" you'll be able to check and confirm / eliminate this as your problem. My next check would be for a failing disk, so throw smartctl at them. Finally memory, so memtest++ or something similar Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Wed Nov 13 16:48:08 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D71CE579 for ; Wed, 13 Nov 2013 16:48:08 +0000 (UTC) Received: from filter2.win.net (filter2.win.net [216.24.27.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E5D72E73 for ; Wed, 13 Nov 2013 16:48:07 +0000 (UTC) Received: from nb-208.win.net (nb-208.win.net [216.24.27.208]) by filter2.win.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id rADGm6Ps022322 for ; Wed, 13 Nov 2013 11:48:07 -0500 Received: from Gantry (pool245.office.win.net [216.24.33.245]) by nb-208.win.net (Postfix) with SMTP id 9C99B73140 for ; Wed, 13 Nov 2013 11:48:06 -0500 (EST) Message-ID: <84DE8753E8F843A897C3B8E31B54DA29@Gantry> From: "Joseph Mays" To: Subject: Expanding a partition in gpart after increasing the size of an array. Date: Wed, 13 Nov 2013 11:48:08 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 X-Spam-Score: undef - mays@win.net is whitelisted. X-CanIt-Geo: ip=216.24.27.208; country=US; region=KY; city=Louisville; postalcode=40204; latitude=38.2390; longitude=-85.7174; metrocode=529; areacode=502; http://maps.google.com/maps?q=38.2390,-85.7174&z=6 X-CanItPRO-Stream: Outbound:default (inherits from base:default) X-Canit-Stats-ID: 01KN4M6ql - 705dc0cb8d59 - 20131113 X-Antispam-Training-Forget: http://filter.win.net/canit/b.php?i=01KN4M6ql&m=705dc0cb8d59&t=20131113&c=f X-Antispam-Training-Nonspam: http://filter.win.net/canit/b.php?i=01KN4M6ql&m=705dc0cb8d59&t=20131113&c=n X-Antispam-Training-Spam: http://filter.win.net/canit/b.php?i=01KN4M6ql&m=705dc0cb8d59&t=20131113&c=s X-Scanned-By: CanIt (www . roaringpenguin . com) on 216.24.27.102 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 16:48:08 -0000 I have a freebsd box with an LSI Raid controller in it. It had 4 = 3-terabyte drives configured in an 8TB array. I added a 5th drive and = built that into the array. Of course, the amount of drive space that = shows in operation in FreeBSD did not change, presumably because I need = to resize the partition. I was trying to follow the partition resizing instructions shown here = --- http://www.unibia.com/unibianet/freebsd/resize-your-existing-freebsd-root= -partitionslice-safely-without-re-installing but when I do the =E2=80=9Cgpart show =E2=80=9D I don=E2=80=99t see the = free space. What I do see is a change in the apparent overall size of = the disk and a set of parititions that don=E2=80=99t add up to the new = size of the disk. Is there a way to tell gpart that the size of the drive has changed? From owner-freebsd-fs@FreeBSD.ORG Wed Nov 13 16:49:50 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A0CB3709 for ; Wed, 13 Nov 2013 16:49:50 +0000 (UTC) Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7DB1A2EA3 for ; Wed, 13 Nov 2013 16:49:50 +0000 (UTC) Received: by mail-pb0-f53.google.com with SMTP id ma3so680578pbc.12 for ; Wed, 13 Nov 2013 08:49:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nVfBV81d3dXbRwmTgTuOoKQf3EVA6ugs0CEtLdAOw18=; b=JFwzKWhO2un8slMngwQo3b31yqsgqHEGXCT+X53tD3NZNrL/e062V8FnGx9k2eU4Ch 55U9ZZcreOJOIg4no3ijK4x7jN36yOBRXt6LQSljuc0Pwi1nlZN4vJX/6cXlAi7rO2ZD 5TFDXH0pTbrH00VEk0BWx2vGpXC9fx+NGTiDa7qkRFwwcu5oZn+qR78H7SG+TvWXVr1i 6z73L7aKxtyPd9itEugiWwtUVeW8jMR4NREMet1LqvULyi//kDOiOyh1uVigG3lg5BAr Lq73x/4rvatrzpuQxnXF7Je/WMvBJunRgqlXR6jVVKO8AJQ5YYFGyYCjGtb+Q8WT1AyK PH7A== MIME-Version: 1.0 X-Received: by 10.66.51.34 with SMTP id h2mr3019074pao.181.1384361389666; Wed, 13 Nov 2013 08:49:49 -0800 (PST) Received: by 10.70.92.79 with HTTP; Wed, 13 Nov 2013 08:49:49 -0800 (PST) In-Reply-To: <84DE8753E8F843A897C3B8E31B54DA29@Gantry> References: <84DE8753E8F843A897C3B8E31B54DA29@Gantry> Date: Wed, 13 Nov 2013 10:49:49 -0600 Message-ID: Subject: Re: Expanding a partition in gpart after increasing the size of an array. From: Adam Vande More To: Joseph Mays Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.16 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 16:49:50 -0000 On Wed, Nov 13, 2013 at 10:48 AM, Joseph Mays wrote: > I have a freebsd box with an LSI Raid controller in it. It had 4 > 3-terabyte drives configured in an 8TB array. I added a 5th drive and bui= lt > that into the array. Of course, the amount of drive space that shows in > operation in FreeBSD did not change, presumably because I need to resize > the partition. > > I was trying to follow the partition resizing instructions shown here --- > > > http://www.unibia.com/unibianet/freebsd/resize-your-existing-freebsd-root= -partitionslice-safely-without-re-installing > > but when I do the =93gpart show =94 I don=92t see the free space. What I = do see > is a change in the apparent overall size of the disk and a set of > parititions that don=92t add up to the new size of the disk. > > Is there a way to tell gpart that the size of the drive has changed? > At what point in this quest will you decide to share the output of gpart show? --=20 Adam From owner-freebsd-fs@FreeBSD.ORG Wed Nov 13 17:06:50 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 011D6EFF for ; Wed, 13 Nov 2013 17:06:50 +0000 (UTC) Received: from filter1.win.net (filter1.win.net [216.24.27.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C7B922FDB for ; Wed, 13 Nov 2013 17:06:49 +0000 (UTC) Received: from nb-202.win.net (nb-202.win.net [216.24.27.202]) by filter1.win.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id rADH6h4j002468 for ; Wed, 13 Nov 2013 12:06:43 -0500 Received: from Gantry (pool245.office.win.net [216.24.33.245]) by nb-202.win.net (Postfix) with SMTP id 53D31228EC for ; Wed, 13 Nov 2013 12:06:43 -0500 (EST) Message-ID: From: "Joseph Mays" To: References: <84DE8753E8F843A897C3B8E31B54DA29@Gantry> In-Reply-To: <84DE8753E8F843A897C3B8E31B54DA29@Gantry> Subject: Re: Expanding a partition in gpart after increasing the size of an array. Date: Wed, 13 Nov 2013 12:06:45 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 X-Spam-Score: undef - mays@win.net is whitelisted. X-CanIt-Geo: ip=216.24.27.202; country=US; region=KY; city=Louisville; postalcode=40204; latitude=38.2390; longitude=-85.7174; metrocode=529; areacode=502; http://maps.google.com/maps?q=38.2390,-85.7174&z=6 X-CanItPRO-Stream: Outbound:default (inherits from base:default) X-Canit-Stats-ID: 02KN56HbB - 40bec5417b17 - 20131113 X-Antispam-Training-Forget: http://filter.win.net/canit/b.php?i=02KN56HbB&m=40bec5417b17&t=20131113&c=f X-Antispam-Training-Nonspam: http://filter.win.net/canit/b.php?i=02KN56HbB&m=40bec5417b17&t=20131113&c=n X-Antispam-Training-Spam: http://filter.win.net/canit/b.php?i=02KN56HbB&m=40bec5417b17&t=20131113&c=s X-Scanned-By: CanIt (www . roaringpenguin . com) on 216.24.27.101 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 17:06:50 -0000 I was originally attaching the results of "gpart show" as a screenshot = because I was working through an internet kvm module on a system several = states away that was booted in standalone mode. But the mailing list = seems to strip off attachments, so I ssh'd into the system in normal = operation to get output of "gpart show" that I can cut and paste here. root@warehouse:/root # gpart show mfid0 =3D> 34 17578327997 mfid0 GPT (10T) [CORRUPT] 34 128 1 freebsd-boot (64k) 162 1048576000 2 freebsd-ufs (500G) 1048576162 16521363328 4 freebsd-ufs (7.7T) 17569939490 8388540 3 freebsd-swap (4G) 17578328030 1 - free - (512B) -----Original Message-----=20 From: Joseph Mays=20 Sent: Wednesday, November 13, 2013 11:48 AM=20 To: freebsd-fs@freebsd.org=20 Subject: Expanding a partition in gpart after increasing the size of an = array.=20 I have a freebsd box with an LSI Raid controller in it. It had 4 = 3-terabyte drives configured in an 8TB array. I added a 5th drive and = built that into the array. Of course, the amount of drive space that = shows in operation in FreeBSD did not change, presumably because I need = to resize the partition. I was trying to follow the partition resizing instructions shown here = --- http://www.unibia.com/unibianet/freebsd/resize-your-existing-freebsd-root= -partitionslice-safely-without-re-installing but when I do the =E2=80=9Cgpart show =E2=80=9D I don=E2=80=99t see the = free space. What I do see is a change in the apparent overall size of = the disk and a set of parititions that don=E2=80=99t add up to the new = size of the disk. Is there a way to tell gpart that the size of the drive has changed? _______________________________________________ freebsd-fs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Wed Nov 13 17:49:06 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC452DD7 for ; Wed, 13 Nov 2013 17:49:06 +0000 (UTC) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 988C822E6 for ; Wed, 13 Nov 2013 17:49:06 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id kp14so770445pab.32 for ; Wed, 13 Nov 2013 09:49:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GyhQTJd/A/QdgzksQZ2N6FpHqGjhJmCkxH4KZfHxh+o=; b=cOppAT+mgSI55o1K85XBgtYHtLuFYJs10bvMBHbiMICfCUay7uZZAMEy4cUKiVSouy NZpcUn1IpJX5gbM2vRm8GQyJGqpeHSHsIPJSZSwFocGRq3FrfuAh45rI1u0/7Gzg8J0v l+RG4R3EzYn34sr7FYkAmpyuAyVL5XKiHCDFIUlYciMW/GG3pVl/Ho5ugi+1pliVl9SC 8Cc0DMcMIw8CYxA4EWThEyeBtT5MDHDJxut229amGB6i3L/xQ4+FFBSWDOEGprOaxGJd 8rqHhMsz7l0e52DedVt54rKIZ4PyrY6Xpaa1te/6u8T2AQQeFFVSHJ4EhA9GgAWYwu5t T2XQ== MIME-Version: 1.0 X-Received: by 10.68.225.232 with SMTP id rn8mr41974722pbc.32.1384364946343; Wed, 13 Nov 2013 09:49:06 -0800 (PST) Received: by 10.70.92.79 with HTTP; Wed, 13 Nov 2013 09:49:06 -0800 (PST) In-Reply-To: References: <84DE8753E8F843A897C3B8E31B54DA29@Gantry> Date: Wed, 13 Nov 2013 11:49:06 -0600 Message-ID: Subject: Re: Expanding a partition in gpart after increasing the size of an array. From: Adam Vande More To: Joseph Mays Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.16 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 17:49:06 -0000 On Wed, Nov 13, 2013 at 11:06 AM, Joseph Mays wrote: > so I ssh'd into the system in normal operation to get output of "gpart > show" that I can cut and paste here. > Many people don't use html capable email. The burden is on you to construct good questions to the widest possible audience. > root@warehouse:/root # gpart show mfid0 > => 34 17578327997 mfid0 GPT (10T) [CORRUPT] > 34 128 1 freebsd-boot (64k) > 162 1048576000 2 freebsd-ufs (500G) > 1048576162 16521363328 4 freebsd-ufs (7.7T) > 17569939490 8388540 3 freebsd-swap (4G) > 17578328030 1 - free - (512B) > Use gpart recover -- man gpart -- Adam From owner-freebsd-fs@FreeBSD.ORG Wed Nov 13 18:42:05 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 143D92A3 for ; Wed, 13 Nov 2013 18:42:05 +0000 (UTC) Received: from barracuda.imaginaryforces.com (199.193.209.132.static.oneiricsys.com [199.193.209.132]) by mx1.freebsd.org (Postfix) with ESMTP id E8B2726D7 for ; Wed, 13 Nov 2013 18:42:03 +0000 (UTC) X-ASG-Debug-ID: 1384368116-0413ad070f0cf10001-dE2xID Received: from newman.IMAGINARYFORCES.LOCAL (newman.imaginaryforces.local [192.168.23.34]) by barracuda.imaginaryforces.com with ESMTP id sPuPa4lMAlwrN7VA for ; Wed, 13 Nov 2013 10:41:56 -0800 (PST) X-Barracuda-Envelope-From: shawn.wallbridge@imaginaryforces.com Received: from NEWMAN.IMAGINARYFORCES.LOCAL ([192.168.23.34]) by newman.IMAGINARYFORCES.LOCAL ([192.168.23.34]) with mapi id 14.01.0438.000; Wed, 13 Nov 2013 10:41:55 -0800 From: Shawn Wallbridge To: "freebsd-fs@FreeBSD.org" Subject: Controller for ZFS Thread-Topic: Controller for ZFS X-ASG-Orig-Subj: Controller for ZFS Thread-Index: AQHO4KAGQyooEFhCi0SGL6HvFgG6/Q== Date: Wed, 13 Nov 2013 18:41:55 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.23.68] Content-Type: text/plain; charset="us-ascii" Content-ID: <39AEDD98AF9CE44888C65D3CC8F58518@IMAGINARYFORCES.COM> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: newman.imaginaryforces.local[192.168.23.34] X-Barracuda-Start-Time: 1384368116 X-Barracuda-URL: http://barracuda.imaginaryforces.com:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at imaginaryforces.com X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.142286 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 18:42:05 -0000 I was wondering what the preferred/best supported 24port SAS/SATA controller is for FreeBSD? I have a box with a LSI/3Ware 9750-24i4e in it, which I can use in JBOD mode, but it seems like a waste to me. I have a few PCI-E slots, so I could run multiple cards, if necessary. Any suggestions? shawn ________________________________ This e-mail is intended only for the named person or entity to which it is = addressed and contains valuable business information that is proprietary, p= rivileged, confidential and/or otherwise protected from disclosure. If you = received this e-mail in error, any review, use, dissemination, distribution= or copying of this e-mail is strictly prohibited. Please notify us immedia= tely of the error via e-mail to postmaster@imaginaryforces.c= om and please delete the e-mail from your system, retaining no copies in an= y media. We appreciate your cooperation. ...imaginaryforces.com...=0D From owner-freebsd-fs@FreeBSD.ORG Wed Nov 13 18:57:00 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53BFE7B0 for ; Wed, 13 Nov 2013 18:57:00 +0000 (UTC) Received: from kukuro.siemiradzcy.pl (host-89-231-96-32.warszawa.mm.pl [89.231.96.32]) by mx1.freebsd.org (Postfix) with ESMTP id CC17627B7 for ; Wed, 13 Nov 2013 18:56:59 +0000 (UTC) Received: from [10.84.12.122] (volkove-THINK.siemiradzcy.pl [10.84.12.122]) by kukuro.siemiradzcy.pl (Postfix) with ESMTPSA id 746FFC0079 for ; Wed, 13 Nov 2013 19:56:58 +0100 (CET) Message-ID: <5283CB77.2040202@siemiradzcy.pl> Date: Wed, 13 Nov 2013 19:56:55 +0100 From: =?UTF-8?B?xYF1a2FzeiBKYWt1YiBTaWVtaXJhZHpraQ==?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: [ffs] ffs_valloc: dup alloc problem possible duplication of kern/133980 ? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 18:57:00 -0000 Hello! I'm having a problem with ffs: root@pathogen:~ # gpart delete -i 1 ada0 ada0s1 deleted root@pathogen:~ # gpart destroy ada0 ada0 destroyed root@pathogen:~ # gpart create -s GPT ada0 ada0 created root@pathogen:~ # gpart add -s 32M -t freebsd ada0 ada0s1 added root@pathogen:~ # newfs /dev/ada0s1 /dev/ada0s1: 32.0MB (65536 sectors) block size 32768, fragment size 4096 using 4 cylinder groups of 8.03MB, 257 blks, 1152 inodes. super-block backups (for fsck -b #) at: 192, 16640, 33088, 49536 root@pathogen:~ # mount/dev/ada0s1 /media/ root@pathogen:~ # ls/media/ .snap root@pathogen:~ # touch /media/a mode = 040755, inum = 2, fs = /media panic: ffs_valloc: dup alloc KDB: enter: panic [ thread pid 1089 tid 100062 ] Stopped at kdb_enter+0x4c: ldrb r15, [r15, r15, ror r15]! db> bt Tracing pid 1089 tid 100062 td 0xc4146640 db_trace_self() at db_trace_self pc = 0xc0bfdf98 lr = 0xc0933044 (db_hex2dec+0x494) sp = 0xde01c680 fp = 0xde01c698 r10 = 0xc0ce7ae0 db_hex2dec() at db_hex2dec+0x494 pc = 0xc0933044 lr = 0xc09329f8 (db_command_loop+0x2f4) sp = 0xde01c6a0 fp = 0xde01c740 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc0c77132 db_command_loop() at db_command_loop+0x2f4 pc = 0xc09329f8 lr = 0xc0932754 (db_command_loop+0x50) sp = 0xde01c748 fp = 0xde01c758 r4 = 0xc0c477d0 r5 = 0xc0c5e1d3 r6 = 0xc0d30d2c r7 = 0xde01c928 r8 = 0xc4146640 r9 = 0xc0d25ac4 r10 = 0xc0ce7d50 db_command_loop() at db_command_loop+0x50 pc = 0xc0932754 lr = 0xc09350a4 (X_db_symbol_values+0x254) sp = 0xde01c760 fp = 0xde01c880 r4 = 0x00000000 r5 = 0xde01c768 r6 = 0xc0d25af0 X_db_symbol_values() at X_db_symbol_values+0x254 pc = 0xc09350a4 lr = 0xc0a774f0 (kdb_trap+0xd4) sp = 0xde01c888 fp = 0xde01c8a8 r4 = 0x00000000 r5 = 0x00000001 r6 = 0xc0d25af0 r7 = 0xde01c928 kdb_trap() at kdb_trap+0xd4 pc = 0xc0a774f0 lr = 0xc0c0e918 (undefinedinstruction+0x20c) sp = 0xde01c8b0 fp = 0xde01c920 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc0c0e65c r7 = 0xe7ffffff r8 = 0xc4146640 r9 = 0xc0a76d98 r10 = 0xde01c928 undefinedinstruction() at undefinedinstruction+0x20c pc = 0xc0c0e918 lr = 0xc0bff84c (exception_exit) sp = 0xde01c928 fp = 0xde01c980 r4 = 0xffffffff r5 = 0xffff1004 r6 = 0xc0d33864 r7 = 0xc0d180b8 r8 = 0xc4146640 r9 = 0xc0d18040 r10 = 0xde01c9b4 exception_exit() at exception_exit pc = 0xc0bff84c lr = 0xc0a76d8c (kdb_enter+0x40) sp = 0xde01c97c fp = 0xde01c980 r0 = 0xc0d25ad4 r1 = 0x00000000 r2 = 0x00000000 r3 = 0x00000000 r4 = 0xc0c5e22d r5 = 0xc0c7274d r6 = 0xc0d33864 r7 = 0xc0d180b8 r8 = 0xc4146640 r9 = 0xc0d18040 r10 = 0xde01c9b4 r12 = 0x00000000 kdb_enter() at kdb_enter+0x50 pc = 0xc0a76d9c lr = 0xc0a46c64 (panic+0xcc) sp = 0xde01c988 fp = 0xde01c9a8 r4 = 0x00000100 panic() at panic+0xcc pc = 0xc0a46c64 lr = 0xc0bb3b68 (ffs_valloc+0x8b4) sp = 0xde01c9c0 fp = 0xde01ca40 r4 = 0x00000002 r5 = 0xc40e5780 r6 = 0xde01ca54 r7 = 0x00000000 r8 = 0x00000000 r9 = 0x000081a4 r10 = 0xde01cd48 ffs_valloc() at ffs_valloc+0x8b4 pc = 0xc0bb3b68 lr = 0xc0bd03f8 (ufs_vinit+0x31ec) sp = 0xde01ca48 fp = 0xde01cb80 r4 = 0xde01cc60 r5 = 0x000081a4 r6 = 0xc0bb32b4 r7 = 0xc40e5780 r8 = 0xde01cd30 r9 = 0xc4196900 r10 = 0xde01cd48 ufs_vinit() at ufs_vinit+0x31ec pc = 0xc0bd03f8 lr = 0xc0bcd280 (ufs_vinit+0x74) sp = 0xde01cb88 fp = 0xde01cb88 r4 = 0xde01cc60 r5 = 0x00000000 r6 = 0xc0d0b1c0 r7 = 0xc4196900 r8 = 0x00000000 r9 = 0xde01cce0 r10 = 0x00000202 ufs_vinit() at ufs_vinit+0x74 pc = 0xc0bcd280 lr = 0xc0c26250 (VOP_CREATE_APV+0x9c) sp = 0xde01cb90 fp = 0xde01cba0 VOP_CREATE_APV() at VOP_CREATE_APV+0x9c pc = 0xc0c26250 lr = 0xc0add1a0 (vn_open_cred+0x2f8) sp = 0xde01cba8 fp = 0xde01cc90 r4 = 0xde01cd30 r5 = 0xc4083820 r6 = 0xde01cce0 vn_open_cred() at vn_open_cred+0x2f8 pc = 0xc0add1a0 lr = 0xc0adcea0 (vn_open+0x24) sp = 0xde01cc98 fp = 0xde01cca0 r4 = 0xc4146640 r5 = 0xc418b800 r6 = 0xde01cce0 r7 = 0x00000012 r8 = 0x00000000 r9 = 0x000500cf r10 = 0xde01ccd0 vn_open() at vn_open+0x24 pc = 0xc0adcea0 lr = 0xc0ad6cc0 (kern_openat+0x24c) sp = 0xde01cca8 fp = 0xde01cda8 kern_openat() at kern_openat+0x24c pc = 0xc0ad6cc0 lr = 0xc0ad6a08 (sys_open+0x28) sp = 0xde01cdb0 fp = 0xde01cdb8 r4 = 0xc4146640 r5 = 0xc405e640 r6 = 0x00000000 r7 = 0x00000000 r8 = 0xde01ce10 r9 = 0xbfffec10 r10 = 0xbfffebe8 sys_open() at sys_open+0x28 pc = 0xc0ad6a08 lr = 0xc0c0e010 (swi_handler+0x224) sp = 0xde01cdc0 fp = 0xde01ce58 swi_handler() at swi_handler+0x224 pc = 0xc0c0e010 lr = 0xc0bff618 (swi_entry+0x40) sp = 0xde01ce60 fp = 0xbfffed08 r4 = 0xbfffed44 r5 = 0x00000000 r6 = 0xbfffed44 r7 = 0x00000005 r8 = 0xbfffec20 swi_entry() at swi_entry+0x40 pc = 0xc0bff618 lr = 0xc0bff618 (swi_entry+0x40) sp = 0xde01ce60 fp = 0xbfffed08 Unable to unwind further db> Some more details about system: # uname -a FreeBSD pathogen 10.0-BETA3 FreeBSD 10.0-BETA3 #9 r258097M: Wed Nov 13 19:06:32 CET 2013 root@fb:/usr/obj/arm.arm/usr/src/sys/SHEEVAPLUG arm # grep -Ei '(geom|FFS|MSDOS)' /usr/src/sys/arm/conf/SHEEVAPLUG options FFS #Berkeley Fast Filesystem options NO_FFS_SNAPSHOT options MSDOSFS options GEOM_PART_GPT options GEOM_PART_MBR options GEOM_ELI # camcontrol identify 1:0:0 pass0: ATA-8 SATA 3.x device pass0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) protocol ATA/ATAPI-8 SATA 3.x device model WDC WD20EARX-00PASB0 firmware revision 51.0AB51 serial number WD-WCAZAJ212143 WWN 50014ee25ccb1ff4 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 4096, offset 0 LBA supported 268435455 sectors LBA48 supported 3907029168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no automatic acoustic management no no media status notification no no power-up in Standby yes no write-read-verify no no unload no no free-fall no no Data Set Management (DSM/TRIM) no Host Protected Area (HPA) yes no 3907029168/3907029168 HPA - Security no I see that similar problem was already reported back in 2009: kern/133980 Should I fill the PR? Best regards / Pozdrawiam Łukasz Siemiradzki From owner-freebsd-fs@FreeBSD.ORG Wed Nov 13 19:02:16 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7335F9F0 for ; Wed, 13 Nov 2013 19:02:16 +0000 (UTC) Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4CBC72852 for ; Wed, 13 Nov 2013 19:02:16 +0000 (UTC) Received: by mail-pd0-f182.google.com with SMTP id y13so824972pdi.27 for ; Wed, 13 Nov 2013 11:02:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7Ijboj2Fg53LcBvTbuovlIxlSWVzCfU1ZBVJechQS5U=; b=dA/7lVbDh4auYl97oWPdkyw73rCI3rRg7ar+MHxqHJXLqhhcjpiMaxnUYEt6wh0tFb q3n5gegHJgJh3XmBDQFN4QmMXImuP3TYcZ26drY5mP0RjlQU5sekRyVl9bhvNQ/+rKmM gyxzySNrFQmCF6f/7na79IX561r6Obtd3LdBldfSDh+HuO96IT1ej0/hTIucKUGN3hoG rDIre41QeSVem6zMG8BECvDTYUmK1VR9ihiL8WhVVUOiIrrm2s7kSATtcsYDU3/vwueE O4Cji8Oor9KFrWsPZnRlPwkb0o4jz2Xtsk9ezqV3mT/tY/3yRusppdsBIhBE2IMK2HL4 k2ow== X-Received: by 10.68.163.33 with SMTP id yf1mr18555098pbb.143.1384369335933; Wed, 13 Nov 2013 11:02:15 -0800 (PST) Received: from briankrusicw.logan.tv ([64.17.255.138]) by mx.google.com with ESMTPSA id ka3sm46102269pbc.32.2013.11.13.11.02.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Nov 2013 11:02:15 -0800 (PST) Subject: Re: Controller for ZFS Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: aurfalien In-Reply-To: Date: Wed, 13 Nov 2013 11:02:13 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <31CBC0E1-5D63-43E9-981A-72F4B66BF43A@gmail.com> References: To: Shawn Wallbridge X-Mailer: Apple Mail (2.1085) Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 19:02:16 -0000 Real quick, I would break it down into 2 HBAs if possible. And if you go 2 SSD for ZIL and 2 SSD for L2ARC, I would also split them = amongst both HBAs. Just some food for thought. In terms of HBAs, I would go LSI. - aurf On Nov 13, 2013, at 10:41 AM, Shawn Wallbridge wrote: > I was wondering what the preferred/best supported 24port SAS/SATA > controller is for FreeBSD? I have a box with a LSI/3Ware 9750-24i4e in = it, > which I can use in JBOD mode, but it seems like a waste to me. >=20 > I have a few PCI-E slots, so I could run multiple cards, if necessary. >=20 > Any suggestions? >=20 > shawn >=20 >=20 > ________________________________ >=20 > This e-mail is intended only for the named person or entity to which = it is addressed and contains valuable business information that is = proprietary, privileged, confidential and/or otherwise protected from = disclosure. If you received this e-mail in error, any review, use, = dissemination, distribution or copying of this e-mail is strictly = prohibited. Please notify us immediately of the error via e-mail to = postmaster@imaginaryforces.com and please delete the = e-mail from your system, retaining no copies in any media. We appreciate = your cooperation. >=20 > ...imaginaryforces.com... >=20 > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Wed Nov 13 21:56:52 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6B61496; Wed, 13 Nov 2013 21:56:52 +0000 (UTC) Received: from frv152.fwdcdn.com (frv152.fwdcdn.com [212.42.77.152]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7616D2312; Wed, 13 Nov 2013 21:56:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:Mime-Version:Message-ID:Subject:To:From:Date; bh=VKR//ZI42D7K21EFXIjPKFeLqWuNYfnZmbUFaK23Y70=; b=ENRY2E46uyyvzxuwZ8HmYl8tBUTaZrw3JaSsbCSuB/mNYQTFnbFGhp08FGNY+F32PCK+rsndlA3b0PjAfixsAna2DW3N3CNLYDSJNMAEA0zGwlerSMXAnNKJJxbPrkYAP2WgWPjxCVPQ3KT6LO6R7zhLO8/qszcw3VpFhxcLhzA=; Received: from [37.115.116.138] (helo=nonamehost.local) by frv152.fwdcdn.com with esmtpsa ID 1VgiQS-000LsQ-0M ; Wed, 13 Nov 2013 23:56:40 +0200 Date: Wed, 13 Nov 2013 23:56:39 +0200 From: Ivan Klymenko To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: 10.0-BETA3 Fatal trap 12 with firefox Message-ID: <20131113235639.4499aecf@nonamehost.local> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=37.115.116.138; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 21:56:52 -0000 I have FreeBSD 10.0-BETA3 #0 r257891 amd64 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x298 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80b21b9b stack pointer = 0x28:0xfffffe01f46d63c0 frame pointer = 0x28:0xfffffe01f46d6450 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2831 (firefox) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff808f99f0 at kdb_backtrace+0x60 #1 0xffffffff808c0fb5 at panic+0x155 #2 0xffffffff80ce1052 at trap_fatal+0x3a2 #3 0xffffffff80ce1329 at trap_pfault+0x2c9 #4 0xffffffff80ce0ab6 at trap+0x5e6 #5 0xffffffff80cc7d52 at calltrap+0x8 #6 0xffffffff80b2c5b4 at softdep_update_inodeblock+0x154 #7 0xffffffff80b1982c at ffs_update+0x1bc #8 0xffffffff80b19d81 at ffs_truncate+0x431 #9 0xffffffff80b46123 at ufs_inactive+0x1b3 #10 0xffffffff80de9658 at VOP_INACTIVE_APV+0x98 #11 0xffffffff8095c701 at vinactive+0x101 #12 0xffffffff8095cb12 at vputx+0x272 #13 0xffffffff809653c6 at kern_unlinkat+0x246 #14 0xffffffff80ce1947 at amd64_syscall+0x357 #15 0xffffffff80cc803b at Xfast_syscall+0xfb Uptime: 8h10m43s Dumping 668 out of 6055 MB:..3%..12%..22%..32%..41%..51%..63%..72%..82%..91% ... #0 doadump (textdump=) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:219 #1 0xffffffff808c0c30 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:447 #2 0xffffffff808c0ff4 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:754 #3 0xffffffff80ce1052 in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:882 #4 0xffffffff80ce1329 in trap_pfault (frame=0xfffffe01f46d6310, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:699 #5 0xffffffff80ce0ab6 in trap (frame=0xfffffe01f46d6310) at /usr/src/sys/amd64/amd64/trap.c:463 #6 0xffffffff80cc7d52 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 #7 0xffffffff80b21b9b in softdep_process_journal (mp=, needwk=, flags=1) at /usr/src/sys/ufs/ffs/ffs_softdep.c:2768 #8 0xffffffff80b2c5b4 in softdep_update_inodeblock (ip=0xfffff8002b513930, bp=0xfffffe01718f3cf0, waitfor=1) at /usr/src/sys/ufs/ffs/ffs_softdep.c:11838 #9 0xffffffff80b1982c in ffs_update (vp=0xfffff80147e43760, waitfor=1) at /usr/src/sys/ufs/ffs/ffs_inode.c:143 #10 0xffffffff80b19d81 in ffs_truncate (vp=, length=, flags=, cred=0x0) at pcpu.h:219 #11 0xffffffff80b46123 in ufs_inactive (ap=) at /usr/src/sys/ufs/ufs/ufs_inode.c:131 #12 0xffffffff80de9658 in VOP_INACTIVE_APV (vop=, a=) at vnode_if.c:1953 #13 0xffffffff8095c701 in vinactive (vp=0xfffff80147e43760, td=0xfffff8005423c920) at vnode_if.h:807 #14 0xffffffff8095cb12 in vputx (vp=0xfffff80147e43760, func=2) at /usr/src/sys/kern/vfs_subr.c:2233 #15 0xffffffff809653c6 in kern_unlinkat (td=, fd=-100, path=0x811d2ed00
, pathseg=UIO_USERSPACE, oldinum=) at /usr/src/sys/kern/vfs_syscalls.c:1868 #16 0xffffffff80ce1947 in amd64_syscall (td=0xfffff8005423c920, traced=0) at subr_syscall.c:134 #17 0xffffffff80cc803b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:391 #18 0x0000000801271e3a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 03:06:15 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88BF9EBA for ; Thu, 14 Nov 2013 03:06:15 +0000 (UTC) Received: from mail.crittercasa.com (mail.turbofuzz.com [208.87.221.144]) by mx1.freebsd.org (Postfix) with ESMTP id 73B4C26EF for ; Thu, 14 Nov 2013 03:06:14 +0000 (UTC) Received: from kruse-49.3.ixsystems.com (unknown [69.198.165.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.crittercasa.com (Postfix) with ESMTPS id 912A216482D; Wed, 13 Nov 2013 19:06:07 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: Controller for ZFS From: Jordan Hubbard In-Reply-To: <31CBC0E1-5D63-43E9-981A-72F4B66BF43A@gmail.com> Date: Wed, 13 Nov 2013 19:06:07 -0800 Message-Id: References: <31CBC0E1-5D63-43E9-981A-72F4B66BF43A@gmail.com> To: aurfalien X-Mailer: Apple Mail (2.1822) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.16 Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 03:06:15 -0000 On Nov 13, 2013, at 11:02 AM, aurfalien wrote: > In terms of HBAs, I would go LSI. There=92s some other choice? :-) - Jordan From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 03:09:17 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3EEC4191 for ; Thu, 14 Nov 2013 03:09:17 +0000 (UTC) Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 179D22728 for ; Thu, 14 Nov 2013 03:09:17 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id um1so1350758pbc.8 for ; Wed, 13 Nov 2013 19:09:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=ZduJirlvURCZfVwMbQ0+IEZTXLzlBG6laE5ZdnlXeVU=; b=w4/sxo9WGFfmPByVPS7cbuVJJxBkk8vQMnYH4gPoX5ySuNNCpTOx+8XeTfJzG9JV/w L/jI9AD3GvAQVGwwUtn39w/SIgLUOlwXFIh7QD3mUawXp+HYUmPE4Eg72G5bXqDVc421 +jJx5fOhsGRPlQAREGAcW66tXzS5Sf5VyVS253QSI/0d0p5YuB7QbXWttWP7ggf1PIo+ P5imlxN0Bbuk8EWSQ8nN2P3BYFqBHDFxSenCP4bg2RS/i7q1btiHxjFsf6EOv4ekrsZZ 05aAVNspJ37pP4oJFMlKWwIoBWORRcicFq55bUwaVznmzoAKhhZEKOOqa/KPRKC4QiSR VXeA== X-Received: by 10.66.173.74 with SMTP id bi10mr21829155pac.125.1384398556739; Wed, 13 Nov 2013 19:09:16 -0800 (PST) Received: from briankrusicw.logan.tv ([64.17.255.138]) by mx.google.com with ESMTPSA id oj6sm55485044pab.9.2013.11.13.19.09.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Nov 2013 19:09:16 -0800 (PST) Subject: Re: Controller for ZFS Mime-Version: 1.0 (Apple Message framework v1085) From: aurfalien In-Reply-To: Date: Wed, 13 Nov 2013 19:09:15 -0800 Message-Id: <935848BA-63FE-4DC7-908C-14A6230A0270@gmail.com> References: <31CBC0E1-5D63-43E9-981A-72F4B66BF43A@gmail.com> To: Jordan Hubbard X-Mailer: Apple Mail (2.1085) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.16 Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 03:09:17 -0000 On Nov 13, 2013, at 7:06 PM, Jordan Hubbard wrote: >=20 > On Nov 13, 2013, at 11:02 AM, aurfalien wrote: >=20 >> In terms of HBAs, I would go LSI. >=20 > There=92s some other choice? :-) >=20 > - Jordan Well my fine feathered friend, there is always a choice. The question is wether its a good choice or a not so good choice. Which leads me to my next question; To be or not to be...? ... And the answer is... Pfffffffffffffffffttttttt..... - aurf From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 10:59:28 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1A675F4 for ; Thu, 14 Nov 2013 10:59:28 +0000 (UTC) Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com [195.16.150.151]) by mx1.freebsd.org (Postfix) with ESMTP id B5C982FCD for ; Thu, 14 Nov 2013 10:59:28 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id DFF169DC637; Thu, 14 Nov 2013 11:49:27 +0100 (CET) Subject: Re: Controller for ZFS Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: Date: Thu, 14 Nov 2013 11:49:24 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> References: To: Shawn Wallbridge X-Mailer: Apple Mail (2.1283) Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 10:59:29 -0000 On Nov 13, 2013, at 7:41 PM, Shawn Wallbridge wrote: > I was wondering what the preferred/best supported 24port SAS/SATA > controller is for FreeBSD? I have a box with a LSI/3Ware 9750-24i4e in = it, > which I can use in JBOD mode, but it seems like a waste to me. Not only a waste, but a serious problem. You absolutely do not want a "JBOD mode" in which you create so-called = RAID0 1-drive logical volumes. You absolutely do want a silly and stupid HBA which just passes SAS/SATA = commands from the OS to the drives and back.=20 The "JBOD mode" offers a fake device in which the "intelligent" = controller makes its own decisions and, of course, hides the very important SAS/SATA status codes from the OS. ZFS knows better.=20 The one I use is sold by Dell as the "H200". They usually try to disuade = you by saying that it's not intelligent, doesn't offer RAID, some of their "configuration aids" even forbid it... I just = tell the salesman to shut up because I know much better than him. The only problem: beware if you are using a built-in backplane in the = server, some manufacturers insist on using different cabling schemes for different controllers and you could run into stupid = problems because of that. FreeBSD 10 identifies one of my cards as this one: mps0: port 0x7c00-0x7cff mem = 0xd4ff0000-0xd4ffffff,0xd4f80000-0xd4fbffff irq 80 at device 0.0 on = pci67 mps0: Firmware: 07.15.08.00, Driver: 16.00.00.00-fbsd mps0: IOCCapabilities: = 185c Borja. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 11:56:25 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E0DAB434 for ; Thu, 14 Nov 2013 11:56:25 +0000 (UTC) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 70B132477 for ; Thu, 14 Nov 2013 11:56:25 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id q8so256102lbi.2 for ; Thu, 14 Nov 2013 03:56:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1uVbzbjQ1GjVrnSOjCUGyEFMS67XNmtaLEhYUdQD6Nc=; b=WNrjzCnjAFe7HC5eOCmcYILbrbzJvktQnDqvG09wfrjt8/4wXuHg59X+AGCcnbViF5 P2ybEl2YM+DOI8dqGEa36ck7JqX/1Eg/wOPcbGYt6pJT83Mnxija760IthprWRaQuNBt A6A50q9+qC6AI4aLtdOsCSL4xWlaI+FiDYguTvXSEn9BktB8VS+QCksXY/zxI1gZ4tFo fW40jCOHn49Dy75zd9LqMXZzyXXcodItfM0Qg4TamGi/lRkPRzZGqECB2Ikoveth+ROz 7ITy5B2Sn0RRy/UZffxP9E1pAcMMWfWjd0xhaaJiQwEVEmkJV7v1hjMUx8rqiK+q5ikM C/MA== MIME-Version: 1.0 X-Received: by 10.152.22.228 with SMTP id h4mr510988laf.71.1384430183437; Thu, 14 Nov 2013 03:56:23 -0800 (PST) Received: by 10.112.5.138 with HTTP; Thu, 14 Nov 2013 03:56:23 -0800 (PST) In-Reply-To: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> References: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> Date: Thu, 14 Nov 2013 11:56:23 +0000 Message-ID: Subject: Re: Controller for ZFS From: Tom Evans To: Borja Marcos Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 11:56:25 -0000 On Thu, Nov 14, 2013 at 10:49 AM, Borja Marcos wrote: > The one I use is sold by Dell as the "H200". They usually try to disuade you by saying that it's not intelligent, doesn't > offer RAID, some of their "configuration aids" even forbid it... I just tell the salesman to shut up because I know much better than him. The one I use was labelled as "Dell 6GB SAS HBA" (I got it from ebay, ~$100) with 2 external mini-SAS connectors. This could then be flashed with LSI's own firmware to 9211-8i-IT firmware (it doesn't seem to care how the ports are configured). These are then hooked up to a couple of 16 bay enclosures with SAS expanders. This then gives you the perfect ZFS HBA, no more configuration required. Each drive attached appears as /dev/daN. (One warning, if your system is EFI, then LSI's DOS, linux and FreeBSD based flash utils will not work, you'll get a message about "Failed to initialise PAL". Put the card in a BIOS based system, or (much harder) boot an EFI shell and use LSI's EFI utils instead) > > The only problem: beware if you are using a built-in backplane in the server, some manufacturers insist on using different > cabling schemes for different controllers and you could run into stupid problems because of that. > > FreeBSD 10 identifies one of my cards as this one: > mps0: port 0x7c00-0x7cff mem 0xd4ff0000-0xd4ffffff,0xd4f80000-0xd4fbffff irq 80 at device 0.0 on pci67 > mps0: Firmware: 07.15.08.00, Driver: 16.00.00.00-fbsd This is quite old firmware, do you not have problems with this (particularly large drives or SSDs)? I believe I am using 15, and the latest is 16. Cheers Tom From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 12:26:11 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C43C6436 for ; Thu, 14 Nov 2013 12:26:11 +0000 (UTC) Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com [195.16.150.151]) by mx1.freebsd.org (Postfix) with ESMTP id 8759226BE for ; Thu, 14 Nov 2013 12:26:11 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id D188A9DC7AF; Thu, 14 Nov 2013 13:26:09 +0100 (CET) Subject: Re: Controller for ZFS Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: Date: Thu, 14 Nov 2013 13:26:08 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <3E00D7C0-68EE-4838-BD99-0BF2011DBC06@sarenet.es> References: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> To: Tom Evans X-Mailer: Apple Mail (2.1283) Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 12:26:11 -0000 On Nov 14, 2013, at 12:56 PM, Tom Evans wrote: >> The only problem: beware if you are using a built-in backplane in the = server, some manufacturers insist on using different >> cabling schemes for different controllers and you could run into = stupid problems because of that. >>=20 >> FreeBSD 10 identifies one of my cards as this one: >> mps0: port 0x7c00-0x7cff mem = 0xd4ff0000-0xd4ffffff,0xd4f80000-0xd4fbffff irq 80 at device 0.0 on = pci67 >> mps0: Firmware: 07.15.08.00, Driver: 16.00.00.00-fbsd >=20 > This is quite old firmware, do you not have problems with this > (particularly large drives or SSDs)? I believe I am using 15, and the > latest is 16. No problems so far, 2013-08-12.13:02:13 zpool create cashopul raidz /dev/da0.nop = /dev/da1.nop /dev/da2.nop /dev/da3.nop /dev/da4.nop /dev/da5.nop borjam@pruebassd:/home/borjam % zpool status cashopul pool: cashopul state: ONLINE scan: scrub repaired 0 in 0h3m with 0 errors on Fri Sep 20 07:05:42 = 2013 config: NAME STATE READ WRITE CKSUM cashopul ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 errors: No known data errors Even though the disks are OCZ Vertex 4's root@pruebassd:/home/borjam # camcontrol devlist at scbus0 target 3 lun 0 (pass0,ses0) at scbus0 target 4 lun 0 (pass1,da0) at scbus0 target 5 lun 0 (pass2,da1) at scbus0 target 7 lun 0 (pass3,da2) at scbus0 target 9 lun 0 (pass4,da3) at scbus0 target 10 lun 0 (pass5,da4) at scbus0 target 11 lun 0 (pass6,da5) Of course, the slots assignment in the backplane becomes random.=20 Do you recommend more recent firmware versions, though? I was playing = with this for a while and it really was tiresome to be loading different firmware versions. Thanks, Borja. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 12:59:33 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C87D827D for ; Thu, 14 Nov 2013 12:59:33 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 592DB28FF for ; Thu, 14 Nov 2013 12:59:33 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id p9so1485971lbv.21 for ; Thu, 14 Nov 2013 04:59:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D0KUtDwYepGHyLw0+tsj/seS0uFQQXokjBFpnjJ20Kg=; b=w6vEeNftEffFVBL7yiXmrJCZE6+huY/SnWtXR8FczzWihA4FA4zcyObr7Jx24Selpm xtpK0GxTySLGBwb87/Pwt2VP5GILq+thN7gc2uqgjOehGCEZcW0zaQdXtZHNWwciiMsZ qIJcnDcRlXi6PIsONt4q7LpQLZCaiJo+QAh2B9dAVjXS0V4gfqoapDgn1HKHoSt74NPT SSlXQeNd02vst0lGTB+5guWYBo/FuIEYNAP9YjkV7jBXIu6jqTVULX9VLo7w40rcIyma dssx8uJpu53JMIFOoBfZXDRi24sKsmBTHgAiWWU0u8z7pv/BLPUKYY2La9QhwgflpzzO 91xw== MIME-Version: 1.0 X-Received: by 10.112.147.104 with SMTP id tj8mr83579lbb.84.1384433971346; Thu, 14 Nov 2013 04:59:31 -0800 (PST) Received: by 10.112.5.138 with HTTP; Thu, 14 Nov 2013 04:59:31 -0800 (PST) In-Reply-To: <3E00D7C0-68EE-4838-BD99-0BF2011DBC06@sarenet.es> References: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> <3E00D7C0-68EE-4838-BD99-0BF2011DBC06@sarenet.es> Date: Thu, 14 Nov 2013 12:59:31 +0000 Message-ID: Subject: Re: Controller for ZFS From: Tom Evans To: Borja Marcos Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 12:59:33 -0000 On Thu, Nov 14, 2013 at 12:26 PM, Borja Marcos wrote: > Do you recommend more recent firmware versions, though? I was playing with this for a while and it really > was tiresome to be loading different firmware versions. 100% agree on how tiresome it is! I was going from messages on this list, especially from Steven Hartland, who seems to know what he is talking about: http://lists.freebsd.org/pipermail/freebsd-fs/2013-July/017728.html and http://lists.freebsd.org/pipermail/freebsd-fs/2013-May/017284.html """ The conclusion is LSI 2008 HBA with FW below P13 will eat the data on your SATA disks if you use WS16 due to the following bug """ Cheers Tom From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 13:29:30 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA501F06 for ; Thu, 14 Nov 2013 13:29:30 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8A1D42AEE for ; Thu, 14 Nov 2013 13:29:30 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 59B0C28427; Thu, 14 Nov 2013 14:29:22 +0100 (CET) Received: from [192.168.1.2] (ip-89-177-49-222.net.upcbroadband.cz [89.177.49.222]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9F95228426; Thu, 14 Nov 2013 14:29:20 +0100 (CET) Message-ID: <5284D030.30904@quip.cz> Date: Thu, 14 Nov 2013 14:29:20 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Borja Marcos Subject: Re: Controller for ZFS References: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> In-Reply-To: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 13:29:30 -0000 Borja Marcos wrote: > > On Nov 13, 2013, at 7:41 PM, Shawn Wallbridge wrote: [...] > The one I use is sold by Dell as the "H200". They usually try to disuade you by saying that it's not intelligent, doesn't > offer RAID, some of their "configuration aids" even forbid it... I just tell the salesman to shut up because I know much better than him. > > The only problem: beware if you are using a built-in backplane in the server, some manufacturers insist on using different > cabling schemes for different controllers and you could run into stupid problems because of that. The second problem is, that you cannot boot RAIDZ[23] from the H200. I tried it 2 years ago on Dell server and the problem was that BIOS shows only the first drive until the OS is fully booted, so the loader cannot boot from RAIDZ. Workaround: I did a small partition on each drive, created 4 way ZFS mirror with base system and another pool for data as RAIDZ. My controller is identified as: mps0: port 0x2000-0x20ff mem 0xc1240000-0xc124ffff,0xc1200000-0xc123ffff irq 16 at device 0.0 on pci1 mps0: Firmware: 07.15.04.00 mps0: IOCCapabilities: 185c mps0: [ITHREAD] Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 15:51:49 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 096D692A for ; Thu, 14 Nov 2013 15:51:49 +0000 (UTC) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C616E260E for ; Thu, 14 Nov 2013 15:51:48 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id o6so2454778oag.27 for ; Thu, 14 Nov 2013 07:51:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=8jtVGLFoo5AMmDn1AoQG1/W127eW1Nm26B0u2LcCAaU=; b=qveYNGsz1rEqLHW7JKFpg0xBGxuzsDmfowhmojcO2JQQMIvtabeF9Bsbp30x8t8L2J 6wH1ZXIWkMMKK9sInwMSv7c0Dtw8b5bTctZBbqNSFel2ehuaubH8zXg1rdimJa1eAhmP avzfW65E1rTJ0hm6wrcuK6lvkJIlX6CfCUTQ5oANwxkvYKplSV/BxuLJ5oFtyuht1Dtl dUHGh6iVxLq+re8z2E6D8azeeTwB76gW5KvoDrxd8iMphX1jo3RBQ9VYcbZ9XOhoQ9WZ IjKois0uOPdEr8ucPFZL+BExVWyvLDdNTEdxYXlzdvAWk3X3Fh6778yyzmdmtnAaLlx1 UIpg== X-Received: by 10.60.145.136 with SMTP id su8mr2083534oeb.17.1384444307856; Thu, 14 Nov 2013 07:51:47 -0800 (PST) Received: from [192.168.1.74] (75-63-29-182.lightspeed.irvnca.sbcglobal.net. [75.63.29.182]) by mx.google.com with ESMTPSA id qe2sm6033260obc.1.2013.11.14.07.51.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 14 Nov 2013 07:51:46 -0800 (PST) Subject: Re: Controller for ZFS Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: aurfalien In-Reply-To: Date: Thu, 14 Nov 2013 07:51:46 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <1107DEAB-75FD-4967-B7D4-4A29FC9CAB00@gmail.com> References: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> <3E00D7C0-68EE-4838-BD99-0BF2011DBC06@sarenet.es> To: Tom Evans X-Mailer: Apple Mail (2.1085) Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 15:51:49 -0000 On Nov 14, 2013, at 4:59 AM, Tom Evans wrote: > On Thu, Nov 14, 2013 at 12:26 PM, Borja Marcos = wrote: >> Do you recommend more recent firmware versions, though? I was playing = with this for a while and it really >> was tiresome to be loading different firmware versions. >=20 > 100% agree on how tiresome it is! I was going from messages on this > list, especially from Steven Hartland, who seems to know what he is > talking about: >=20 > http://lists.freebsd.org/pipermail/freebsd-fs/2013-July/017728.html >=20 > and >=20 > http://lists.freebsd.org/pipermail/freebsd-fs/2013-May/017284.html >=20 > """ > The conclusion is LSI 2008 HBA with FW below P13 will eat the data on = your SATA > disks if you use WS16 due to the following bug Well, as I understand in general one should match the fw with the = driver. So FreeBSD 9 uses v14 LSI driver, so one would flash v14 fw on the = cards. In FreeBSD 10 it looks as if its v16, so one would flash v16 fw. In my tests in a 9 env, I can confirm that the systems runs better with = v14 all around. Thoughts? - aurf= From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 17:03:00 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B97DB7FC for ; Thu, 14 Nov 2013 17:03:00 +0000 (UTC) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5771A2B66 for ; Thu, 14 Nov 2013 17:03:00 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50006718421.msg for ; Thu, 14 Nov 2013 17:02:56 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 14 Nov 2013 17:02:56 +0000 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=10308a6844=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Tom Evans" , "Borja Marcos" References: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> Subject: Re: Controller for ZFS Date: Thu, 14 Nov 2013 17:02:52 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: "freebsd-fs@FreeBSD.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 17:03:00 -0000 ----- Original Message ----- From: "Tom Evans" To: "Borja Marcos" Cc: "freebsd-fs@FreeBSD.org" Sent: Thursday, November 14, 2013 11:56 AM Subject: Re: Controller for ZFS > On Thu, Nov 14, 2013 at 10:49 AM, Borja Marcos wrote: >> The one I use is sold by Dell as the "H200". They usually try to disuade you by saying that it's not intelligent, doesn't >> offer RAID, some of their "configuration aids" even forbid it... I just tell the salesman to shut up because I know much better >> than him. > > The one I use was labelled as "Dell 6GB SAS HBA" (I got it from ebay, > ~$100) with 2 external mini-SAS connectors. This could then be flashed > with LSI's own firmware to 9211-8i-IT firmware (it doesn't seem to > care how the ports are configured). These are then hooked up to a > couple of 16 bay enclosures with SAS expanders. > > This then gives you the perfect ZFS HBA, no more configuration > required. Each drive attached appears as /dev/daN. > > (One warning, if your system is EFI, then LSI's DOS, linux and FreeBSD > based flash utils will not work, you'll get a message about "Failed to > initialise PAL". Put the card in a BIOS based system, or (much harder) > boot an EFI shell and use LSI's EFI utils instead) > >> >> The only problem: beware if you are using a built-in backplane in the server, some manufacturers insist on using different >> cabling schemes for different controllers and you could run into stupid problems because of that. >> >> FreeBSD 10 identifies one of my cards as this one: >> mps0: port 0x7c00-0x7cff mem 0xd4ff0000-0xd4ffffff,0xd4f80000-0xd4fbffff irq 80 at device 0.0 on pci67 >> mps0: Firmware: 07.15.08.00, Driver: 16.00.00.00-fbsd > > This is quite old firmware, do you not have problems with this > (particularly large drives or SSDs)? I believe I am using 15, and the > latest is 16. Latest is actually P17 for LSI SAS2008's Watch out for Dell kit we just found their chassis can't support SATA 3 in our case the Dell C6220 even though the card we specified (LSI 9210-8i which is also a 2008 based card) can and does support SATA 3. Behavour is some of the disk bays randomly disconnect due phys CRC errors which testing seems to indicate is a problem with the midplane in the chassis. This has been confirmed with retail Seagate Contellation.2 HDD's, Samsung 840 Pro and Kingston HyperX SSD's. Note: Dells OEM Constellation.2 disks are artificially limited to SATA 2, possibly to avoid this very issue? We currently have an open support case with Dell but its unclear at this time if there will be a resolution as they seem to strongly follow the "Its not a certified disk" line. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 17:42:35 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 55056FC9 for ; Thu, 14 Nov 2013 17:42:35 +0000 (UTC) Received: from odin.blazingdot.com (odin.blazingdot.com [199.48.133.254]) by mx1.freebsd.org (Postfix) with ESMTP id 3BFFF2EB6 for ; Thu, 14 Nov 2013 17:42:35 +0000 (UTC) Received: by odin.blazingdot.com (Postfix, from userid 1001) id 2E3A6114154; Thu, 14 Nov 2013 17:34:23 +0000 (UTC) Date: Thu, 14 Nov 2013 17:34:23 +0000 From: Marcus Reid To: freebsd-fs@freebsd.org Subject: Defaults in 10.0 ZFS through bsdinstall Message-ID: <20131114173423.GA21761@blazingdot.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 17:42:35 -0000 Hi, I noticed a couple of things with the ZFS defaults that result from using the new installer in 10.0-BETA3. One, atime is turned off everywhere by default. There was a thread on this list on June 8 with a subject of 'Changing the default for ZFS atime to off?', and from what I can tell the idea of turning off atime by default was not a popular one. Two, and probably less controversial, is that fletcher4 is specified exlicitly on the root pool, even though it is default (wouldn't you just want to go with the default, in case it changes?) Marcus From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 18:35:52 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3FE4DAF1; Thu, 14 Nov 2013 18:35:52 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0C72523BD; Thu, 14 Nov 2013 18:35:51 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id rAEIZjsH016586 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Nov 2013 12:35:45 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.152]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 12:35:44 -0600 From: "Teske, Devin" To: Marcus Reid Subject: Re: Defaults in 10.0 ZFS through bsdinstall Thread-Topic: Defaults in 10.0 ZFS through bsdinstall Thread-Index: AQHO4WP56r1WdCmD2k+in4awofQcqw== Date: Thu, 14 Nov 2013 18:35:43 +0000 Message-ID: <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> In-Reply-To: <5285148E.6020903@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.14, 0.0.0000 definitions=2013-11-14_07:2013-11-13,2013-11-14,1970-01-01 signatures=0 Cc: freebsd-fs , Devin Teske , "Teske, Devin" , Allan Jude X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Devin Teske List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 18:35:52 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCg0KT24g Tm92IDE0LCAyMDEzLCBhdCAxMDoyMSBBTSwgQWxsYW4gSnVkZSB3cm90ZToNCg0KT24gMjAxMy0x MS0xNCA5OjM0LCBSZWlkLCBNYXJjdXMgd3JvdGU6DQoNCkhpLA0KDQpJIG5vdGljZWQgYSBjb3Vw bGUgb2YgdGhpbmdzIHdpdGggdGhlIFpGUyBkZWZhdWx0cyB0aGF0IHJlc3VsdCBmcm9tDQp1c2lu ZyB0aGUgbmV3IGluc3RhbGxlciBpbiAxMC4wLUJFVEEzLg0KDQpPbmUsIGF0aW1lIGlzIHR1cm5l ZCBvZmYgZXZlcnl3aGVyZSBieSBkZWZhdWx0LiAgVGhlcmUgd2FzIGEgdGhyZWFkIG9uDQp0aGlz IGxpc3Qgb24gSnVuZSA4IHdpdGggYSBzdWJqZWN0IG9mICdDaGFuZ2luZyB0aGUgZGVmYXVsdCBm b3IgWkZTDQphdGltZSB0byBvZmY/JywgYW5kIGZyb20gd2hhdCBJIGNhbiB0ZWxsIHRoZSBpZGVh IG9mIHR1cm5pbmcgb2ZmIGF0aW1lDQpieSBkZWZhdWx0IHdhcyBub3QgYSBwb3B1bGFyIG9uZS4N Cg0KVHdvLCBhbmQgcHJvYmFibHkgbGVzcyBjb250cm92ZXJzaWFsLCBpcyB0aGF0IGZsZXRjaGVy NCBpcyBzcGVjaWZpZWQNCmV4bGljaXRseSBvbiB0aGUgcm9vdCBwb29sLCBldmVuIHRob3VnaCBp dCBpcyBkZWZhdWx0ICh3b3VsZG4ndCB5b3UganVzdA0Kd2FudCB0byBnbyB3aXRoIHRoZSBkZWZh dWx0LCBpbiBjYXNlIGl0IGNoYW5nZXM/KQ0KDQpNYXJjdXMNCg0KSSBoYXZlIG5ldmVyIGhlYXJk IGEgZ29vZCBhcmd1bWVudCBmb3IgaGF2aW5nIGF0aW1lIG9uLiBUaGUgcGVyZm9ybWFuY2UNCnBl bmFsdHkgb24gWkZTIGlzIHF1aXRlIGxhcmdlLCBhbmQgaXQgYWxzbyBtYWtlcyB5b3VyIHNuYXBz aG90cyBncm93DQpjb25zdGFudC4gSWYgeW91IGhhdmUgYSB1c2UgZm9yIGl0LCB5b3UgY2FuIHR1 cm4gaXQgb24gSSBndWVzcy4gVGhpcw0Kd291bGQgYmUgc29sdmVkIGJ5IGhhdmluZyB0aGUgZGF0 YXNldCBlZGl0b3Igd2UncmUgcGxhbm5pbmcgZm9yIDEwLjENCg0KDQpTZWVtcyBlYXN5IGVub3Vn aCB0byB0dXJuIG9uIG9uY2UgaW5zdGFsbGVkLiBBbmQgbGlrZSBBbGxhbiBzYXlzLCB0aGUNCmVk aXRvciBmb3IgMTAuMSB3b3VsZCBhbGxvdyBjaGFuZ2luZyBvZiB0aGUgZGVmYXVsdC4NCg0KSSds bCBhZGQgdGhhdCBpZiBzY3JpcHRpbmcgaXQsIHlvdSBjYW4gKGluIGN1cnJlbnQgc3RhdGUgZm9y IDEwLjApIGNoYW5nZSB0aGUNCmRhdGFzZXQgb3B0aW9ucyBhdC13aWxsLg0KDQoNClRoZSBmbGV0 Y2hlcjQgdGhpbmcgaXMgYSBsZWZ0b3ZlciwgZnJvbSBvbGRlciB2ZXJzaW9ucyBvZiBaRlMgd2hl cmUgdGhlDQpkZWZhdWx0IHdhcyBmbGV0Y2hlcjIsIEkgc3VwcG9zZSB3ZSBjYW4gcmVtb3ZlIGl0 DQoNCg0KTGV0IG1lIHB1dCBzb21ldGhpbmcgdG9nZXRoZXIuDQotIC0tIA0KRGV2aW4NCg0KLS0t LS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NCkNvbW1lbnQ6IEdQR1Rvb2xzIC0gaHR0cHM6Ly9n cGd0b29scy5vcmcNCg0KaVFFY0JBRUJDZ0FHQlFKU2hSZi9BQW9KRUtyTW41UjlucHE1VFl3SC9q OFJNY2VNNFNUcENBb01UQXo4emtLbg0KZ3BmdE1yZGYzN1RuQVBIeHNYSmFpWmVqbHArRDg1L2E5 bGdsWWJCN2U0V2Rnb0RYOVpYQTBRTHRDRW1FdE40eQ0Kano3S05hNW9BQnExR2pEdHdtMnhRSVNE SWU4eVlJK3puTFNhSEE5VzE4a0NVWnppOEFPajcwQytPNWd5WTI4Yw0KYzNOM2o2WTRFWlAyd3RR bldTZ3h2Q3dJWDVwODZKdnIzUXZoclJ1dU1uS01DVEFoendJeDI0cWNuQTRFY1R6bg0KcDl3MjVD S0x0T3pGMjNuM01jb2RhVW1pYmJCQ0hPWXlyYUxRSitlSkdEWGNzUEJpcGxzM29pV3lpWXVxcGNR cg0KMThRcExOMWxTMzVSblVMY2I1cHhuUDlPeTlyQXd4SEt2ZXM5TWZ1MFVvV3czcVRqU0FmOGdz R3l1NlFhTWdjPQ0KPUdqWWsNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0KCl9fX19fX19f X19fX18KVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1lc3NhZ2UgaXMgcHJvcHJp ZXRhcnkgYW5kL29yIGNvbmZpZGVudGlhbC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJl Y2lwaWVudCwgcGxlYXNlOiAoaSkgZGVsZXRlIHRoZSBtZXNzYWdlIGFuZCBhbGwgY29waWVzOyAo aWkpIGRvIG5vdCBkaXNjbG9zZSwgZGlzdHJpYnV0ZSBvciB1c2UgdGhlIG1lc3NhZ2UgaW4gYW55 IG1hbm5lcjsgYW5kIChpaWkpIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5LiBJbiBhZGRp dGlvbiwgcGxlYXNlIGJlIGF3YXJlIHRoYXQgYW55IG1lc3NhZ2UgYWRkcmVzc2VkIHRvIG91ciBk b21haW4gaXMgc3ViamVjdCB0byBhcmNoaXZpbmcgYW5kIHJldmlldyBieSBwZXJzb25zIG90aGVy IHRoYW4gdGhlIGludGVuZGVkIHJlY2lwaWVudC4gVGhhbmsgeW91Lgo= From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 18:35:52 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41FE6AF2 for ; Thu, 14 Nov 2013 18:35:52 +0000 (UTC) Received: from unit0.ironport.snap.net.nz (unit0.ironport.snap.net.nz [202.37.100.104]) by mx1.freebsd.org (Postfix) with ESMTP id AE3AB23BB for ; Thu, 14 Nov 2013 18:35:51 +0000 (UTC) X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=iw7iUsToLjcKeDD2xJYUY7vdGlCAuHgOCAeRLiIczvU= c=1 sm=2 a=mzW07HfSzZMA:10 a=NjuLKI5jG4EA:10 a=V6dPbFcDAAAA:8 a=2LRD4gPbZV39fsc-ba8A:9 a=CjuIK1q_8ugA:10 a=CqWZkgPtQDeKha5iNpUA:9 a=ZVk8-NSrHBgA:10 a=TEJWfmVIHgEA:10 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAO8WhVJ7/y9j/2dsb2JhbABbgz9TvxmBIRaDG0UBAThOFIhuDq0OhFIBBY5mBo4zgRE4gwqBEZAzh2CBL5QbgVRA X-IronPort-AV: E=Sophos;i="4.93,700,1378814400"; d="p7s'?scan'208";a="216992651" Received: from rupert.snap.net.nz ([202.37.100.140]) by smtp0.ironport.snap.net.nz with ESMTP; 15 Nov 2013 07:35:43 +1300 X-Sender-IP: 123.255.47.99 Received: from x24.msqr.us (99.47.255.123.static.snap.net.nz [123.255.47.99]) by rupert.snap.net.nz (Postfix) with ESMTPS id B9DF925620 for ; Fri, 15 Nov 2013 07:35:43 +1300 (NZDT) Received: from renton.fritz.box (99.47.255.123.static.snap.net.nz [123.255.47.99]) (authenticated bits=0) by x24.msqr.us (8.14.7/8.14.5) with ESMTP id rAEIZdUL026989 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 15 Nov 2013 07:35:41 +1300 (NZDT) (envelope-from matt@msqr.us) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msqr.us; s=20121026; t=1384454141; bh=6UELbCJXVOXnuZ3++49ONAQ8oqywnff1PYjX+buiE6A=; h=From:Subject:Date:To; b=gIJIw35BXpGCZ1w7FA9GEo4kzCAyAUPajigyYEHdc6fffqkGg+zXd0CdQ4bhamNC9 Y4h2kr62/MRNlOIj0p2zM9/62yMw0KwJcGkiqXRGhB5a5ARrJafXBmV8ppAchTdnxo 0s8G68YJQRI3yoC2hBvVNwlsJnikLm7lfXJntDJQ= X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at msqr.us X-Authentication-Warning: x24.msqr.us: Host 99.47.255.123.static.snap.net.nz [123.255.47.99] claimed to be renton.fritz.box From: Matt Magoffin Content-Type: multipart/signed; boundary="Apple-Mail=_CE034618-948E-4B68-B279-3900679E6636"; protocol="application/pkcs7-signature"; micalg=sha1 Subject: ZFS snapshot renames failing after upgrade to 9.2 Message-Id: <0C9FD4E1-0549-4849-BFC5-D8C5D4A34D64@msqr.us> Date: Fri, 15 Nov 2013 07:35:40 +1300 To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) X-Mailer: Apple Mail (2.1822) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 18:35:52 -0000 --Apple-Mail=_CE034618-948E-4B68-B279-3900679E6636 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hello, I have a system that had been running FreeBSD 9.1 for some time, and I = recently upgraded to 9.2. I've been using this simple script to create = daily, rotating ZFS snapshots via cron: = http://andyleonard.com/2010/04/07/automatic-zfs-snapshot-rotation-on-freeb= sd/ Essentially the snapshots are renamed and then a new snapshot is created = with the same name as the most recently created snapshot. Since the = upgrade to 9.2, however, the snapshots aren't able to be renamed. I end = up with an error like this: cannot rename 'zdata/home': a child dataset already has a snapshot with = the new name cannot create snapshot 'zdata/home@daily.0': dataset already exists Once that happens, zfs will show two snapshots: # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home zdata/home@daily.1 Wed Nov 13 0:00 2013 = 50.5K 91.0G zdata/home@daily.0 Thu Nov 14 0:00 2013 = 0 91.0G However, trying to list the snapshots results in this error: # ls .zfs/snapshot/ ls: daily.1: Device busy daily.0 I can destroy the daily.1 snapshot: # zfs destroy zdata/home@daily.1 # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home zdata/home@daily.0 Thu Nov 14 0:00 2013 = 0 91.0G # ls .zfs/snapshot/ daily.0 Then if I try to rename it like the script would, I end up in the same = "Device busy" state: # zfs rename zdata/home@daily.0 zdata/home@daily.1 # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home zdata/home@daily.1 Thu Nov 14 0:00 2013 = 0 91.0G # ls .zfs/snapshot/ ls: daily.1: Device busy Does anyone have any ideas how to get the renames working? -- m@ --Apple-Mail=_CE034618-948E-4B68-B279-3900679E6636 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIDgTCCA30w ggJloAMCAQICAQIwCwYJKoZIhvcNAQELMGsxEDAOBgNVBAMMB21zcXIgQ0ExDTALBgNVBAoMBG1z cXIxIDAeBgNVBAsMF0NlcnRpZmljYXRpb24gQXV0aG9yaXR5MQswCQYDVQQGEwJVUzEZMBcGCSqG SIb3DQEJARYKY2FAbXNxci51czAeFw0xMzA3MDcyMTI1MTJaFw0yMzA3MDUyMTI1MTJaMHMxFjAU BgNVBAMMDU1hdHQgTWFnb2ZmaW4xDTALBgNVBAoMBG1zcXIxIDAeBgNVBAsMF0NlcnRpZmljYXRp b24gQXV0aG9yaXR5MQswCQYDVQQGEwJVUzEbMBkGCSqGSIb3DQEJARYMbWF0dEBtc3FyLnVzMIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA80JsC5zGa1iuzGVegrbX8kpfIpqTsG4yaTGP 2XwgLpsyGzn0tule6d/6qa3OJRUR4pY8qCmFs2yxQoVfJvQNRfQDkBO/T6gyx5ml2CTppyCQiiRe Ki0BpD2xQB7SJOoKLTEoveWzAdC8sMT+WxYeS8R1i3HFtoth0Ll0u6hP6Ufp0XLOVXdW2jr0l4aY gn1KSM7KmFmLXDpOFlempaxUTXWLaXjGGDjRi5Ev1a1OTHyfPiA4YmC4/y3Npq2bl88/gxGw7u2Y zYshKZ0y24o5HxxmoxpE0EGl7Ub7+2osp54SKurKdFo/9wlNNIEPATDVoAT2NPDIOWBtZ9LUvYvH SQIDAQABoyYwJDAOBgNVHQ8BAf8EBAMCAf4wEgYDVR0lAQH/BAgwBgYEVR0lADANBgkqhkiG9w0B AQsFAAOCAQEAfuWLLZL5kryMYHEY0EE4cocnBTzXXkhDHUpqoWZvd1ivZpVTBizHIuVyCSUO7PL0 nqK5vlS0ldmyLgE8oaDr1yf/swQ6/yRoOH/4FrH/+bHsBtrtyCzWCPKsRfLY3M/pb02UaRt2lL2v H26I1VB7CTd5z9XFcQi4ZKxANPJE2oXqlWwCABmLpJjPzd6JpNIolMMEQL3cpohfHsSg7uKw6Jqk u7O11j9CBBb/YgGddGC95L7sRiSXlxSMRkjoXREngp2U7pWwh8EcFGo5FnVxuAlWIyVU8DdcCYNL r/euF+clJ3J1ztgPKMzY44CDLVLeCiwKU9GOSDCNbCehQ0vLRDGCAv0wggL5AgEBMHAwazEQMA4G A1UEAwwHbXNxciBDQTENMAsGA1UECgwEbXNxcjEgMB4GA1UECwwXQ2VydGlmaWNhdGlvbiBBdXRo b3JpdHkxCzAJBgNVBAYTAlVTMRkwFwYJKoZIhvcNAQkBFgpjYUBtc3FyLnVzAgECMAkGBSsOAwIa BQCgggFiMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEzMTExNDE4 MzU0MVowIwYJKoZIhvcNAQkEMRYEFKN9j4bCNVSfwn7Lrc07RVcJ6VNPMH8GCSsGAQQBgjcQBDFy MHAwazEQMA4GA1UEAwwHbXNxciBDQTENMAsGA1UECgwEbXNxcjEgMB4GA1UECwwXQ2VydGlmaWNh dGlvbiBBdXRob3JpdHkxCzAJBgNVBAYTAlVTMRkwFwYJKoZIhvcNAQkBFgpjYUBtc3FyLnVzAgEC MIGBBgsqhkiG9w0BCRACCzFyoHAwazEQMA4GA1UEAwwHbXNxciBDQTENMAsGA1UECgwEbXNxcjEg MB4GA1UECwwXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxCzAJBgNVBAYTAlVTMRkwFwYJKoZIhvcN AQkBFgpjYUBtc3FyLnVzAgECMA0GCSqGSIb3DQEBAQUABIIBAO0e5wIXUFsE8XWxU1hr4k7XpjYT 1En3rOAD01ue44O5F4CjBCWnpIMa/Z3EEU58pSjj/RJ5T+eqY6JT/k1dtsjB+yp862UwzIPtZDa6 tEi1gGA+rATUKjA53goGN1vwzdrDM899b65yV8y9sKiZNWy+IQNvLb4DEYb6MR+4CVZg7kcNHPfQ kk4dInxIHOLAUFESL31PMqjB2z5oEF+sll//erHveTushOv6CHTM3KiBjjds1PCJsVJRJ+lfwq17 UvTJrIIwORzaPDv4JXsb6FsYRCDJ/pPSgmc+yqcmF/XZWHOFdIFyuOVjBmq2TnpqsKxDrJN7xBOc b6KuK5Lo9boAAAAAAAA= --Apple-Mail=_CE034618-948E-4B68-B279-3900679E6636-- From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 18:42:19 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 136C1E82; Thu, 14 Nov 2013 18:42:19 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D38D52441; Thu, 14 Nov 2013 18:42:18 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id rAEIfdp1001098 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Nov 2013 12:42:12 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.152]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 12:41:50 -0600 From: "Teske, Devin" To: Marcus Reid Subject: Re: Defaults in 10.0 ZFS through bsdinstall Thread-Topic: Defaults in 10.0 ZFS through bsdinstall Thread-Index: AQHO4WP56r1WdCmD2k+in4awofQcqw== Date: Thu, 14 Nov 2013 18:41:49 +0000 Message-ID: <2C8721E4-4BE6-4BB5-B310-02084392D053@fisglobal.com> References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> In-Reply-To: <5285148E.6020903@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.14, 0.0.0000 definitions=2013-11-14_07:2013-11-13,2013-11-14,1970-01-01 signatures=0 Cc: freebsd-fs , Devin Teske , "Teske, Devin" , Allan Jude X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Devin Teske List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 18:42:19 -0000 Let's try this again (darn GPG and it's inline quoting bug on Mac) On Nov 14, 2013, at 10:21 AM, Allan Jude wrote: > On 2013-11-14 9:34, Reid, Marcus wrote: >>=20 >> Hi, >>=20 >> I noticed a couple of things with the ZFS defaults that result from >> using the new installer in 10.0-BETA3. >>=20 >> One, atime is turned off everywhere by default. There was a thread on >> this list on June 8 with a subject of 'Changing the default for ZFS >> atime to off?', and from what I can tell the idea of turning off atime >> by default was not a popular one. >>=20 >> Two, and probably less controversial, is that fletcher4 is specified >> exlicitly on the root pool, even though it is default (wouldn't you just >> want to go with the default, in case it changes?) >>=20 >> Marcus >=20 > I have never heard a good argument for having atime on. The performance > penalty on ZFS is quite large, and it also makes your snapshots grow > constant. If you have a use for it, you can turn it on I guess. This > would be solved by having the dataset editor we're planning for 10.1 >=20 Seems easy enough to turn on once installed. And like Allan says, the editor for 10.1 would allow changing of the default. I'll add that if scripting it, you can (in current state for 10.0) change t= he dataset options at-will. > The fletcher4 thing is a leftover, from older versions of ZFS where the > default was fletcher2, I suppose we can remove it Let me put something together. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 18:43:30 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0640D7 for ; Thu, 14 Nov 2013 18:43:30 +0000 (UTC) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 609AC246C for ; Thu, 14 Nov 2013 18:43:30 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50006719423.msg for ; Thu, 14 Nov 2013 18:43:27 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 14 Nov 2013 18:43:27 +0000 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=10308a6844=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <54D3B3C002184A52BEC9B1543854B87F@multiplay.co.uk> From: "Steven Hartland" To: "Matt Magoffin" , References: <0C9FD4E1-0549-4849-BFC5-D8C5D4A34D64@msqr.us> Subject: Re: ZFS snapshot renames failing after upgrade to 9.2 Date: Thu, 14 Nov 2013 18:43:25 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 18:43:30 -0000 Sounds like you may have an automatic hold still present. What does the following report: zfs holds -r Regards Steve ----- Original Message ----- From: "Matt Magoffin" To: Sent: Thursday, November 14, 2013 6:35 PM Subject: ZFS snapshot renames failing after upgrade to 9.2 Hello, I have a system that had been running FreeBSD 9.1 for some time, and I recently upgraded to 9.2. I've been using this simple script to create daily, rotating ZFS snapshots via cron: http://andyleonard.com/2010/04/07/automatic-zfs-snapshot-rotation-on-freebsd/ Essentially the snapshots are renamed and then a new snapshot is created with the same name as the most recently created snapshot. Since the upgrade to 9.2, however, the snapshots aren't able to be renamed. I end up with an error like this: cannot rename 'zdata/home': a child dataset already has a snapshot with the new name cannot create snapshot 'zdata/home@daily.0': dataset already exists Once that happens, zfs will show two snapshots: # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home zdata/home@daily.1 Wed Nov 13 0:00 2013 50.5K 91.0G zdata/home@daily.0 Thu Nov 14 0:00 2013 0 91.0G However, trying to list the snapshots results in this error: # ls .zfs/snapshot/ ls: daily.1: Device busy daily.0 I can destroy the daily.1 snapshot: # zfs destroy zdata/home@daily.1 # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home zdata/home@daily.0 Thu Nov 14 0:00 2013 0 91.0G # ls .zfs/snapshot/ daily.0 Then if I try to rename it like the script would, I end up in the same "Device busy" state: # zfs rename zdata/home@daily.0 zdata/home@daily.1 # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home zdata/home@daily.1 Thu Nov 14 0:00 2013 0 91.0G # ls .zfs/snapshot/ ls: daily.1: Device busy Does anyone have any ideas how to get the renames working? -- m@ ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 19:30:42 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 883EE4C2 for ; Thu, 14 Nov 2013 19:30:42 +0000 (UTC) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2846E27C3 for ; Thu, 14 Nov 2013 19:30:41 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50006719847.msg for ; Thu, 14 Nov 2013 19:30:39 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 14 Nov 2013 19:30:39 +0000 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=10308a6844=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <333D57C6A4544067880D9CFC04F02312@multiplay.co.uk> From: "Steven Hartland" To: "Steven Hartland" , "Matt Magoffin" , References: <0C9FD4E1-0549-4849-BFC5-D8C5D4A34D64@msqr.us> <54D3B3C002184A52BEC9B1543854B87F@multiplay.co.uk> Subject: Re: ZFS snapshot renames failing after upgrade to 9.2 Date: Thu, 14 Nov 2013 19:30:33 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 19:30:42 -0000 This could also be due to the following issue which there will be a fix soon: https://www.illumos.org/issues/4322 Regards Steve ----- Original Message ----- From: "Steven Hartland" To: "Matt Magoffin" ; Sent: Thursday, November 14, 2013 6:43 PM Subject: Re: ZFS snapshot renames failing after upgrade to 9.2 > Sounds like you may have an automatic hold still present. > > What does the following report: > zfs holds -r > > Regards > Steve > ----- Original Message ----- > From: "Matt Magoffin" > To: > Sent: Thursday, November 14, 2013 6:35 PM > Subject: ZFS snapshot renames failing after upgrade to 9.2 > > > Hello, > > I have a system that had been running FreeBSD 9.1 for some time, and I recently upgraded to 9.2. I've been using this simple > script to create daily, rotating ZFS snapshots via cron: > > http://andyleonard.com/2010/04/07/automatic-zfs-snapshot-rotation-on-freebsd/ > > Essentially the snapshots are renamed and then a new snapshot is created with the same name as the most recently created > snapshot. Since the upgrade to 9.2, however, the snapshots aren't able to be renamed. I end up with an error like this: > > cannot rename 'zdata/home': a child dataset already has a snapshot with the new name > cannot create snapshot 'zdata/home@daily.0': dataset already exists > > Once that happens, zfs will show two snapshots: > > # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home > zdata/home@daily.1 Wed Nov 13 0:00 2013 50.5K 91.0G > zdata/home@daily.0 Thu Nov 14 0:00 2013 0 91.0G > > However, trying to list the snapshots results in this error: > > # ls .zfs/snapshot/ > ls: daily.1: Device busy > daily.0 > > I can destroy the daily.1 snapshot: > > # zfs destroy zdata/home@daily.1 > # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home > zdata/home@daily.0 Thu Nov 14 0:00 2013 0 91.0G > # ls .zfs/snapshot/ > daily.0 > > Then if I try to rename it like the script would, I end up in the same "Device busy" state: > > # zfs rename zdata/home@daily.0 zdata/home@daily.1 > # zfs list -t snapshot -o name,creation,used,referenced |grep zdata/home > zdata/home@daily.1 Thu Nov 14 0:00 2013 0 91.0G > # ls .zfs/snapshot/ > ls: daily.1: Device busy > > Does anyone have any ideas how to get the renames working? > > -- m@ > > > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the > event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any > information contained in it. > In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 20:34:25 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA3F6E41; Thu, 14 Nov 2013 20:34:25 +0000 (UTC) Received: from odin.blazingdot.com (odin.blazingdot.com [199.48.133.254]) by mx1.freebsd.org (Postfix) with ESMTP id A1A972BA9; Thu, 14 Nov 2013 20:34:25 +0000 (UTC) Received: by odin.blazingdot.com (Postfix, from userid 1001) id B3D30114155; Thu, 14 Nov 2013 20:34:24 +0000 (UTC) Date: Thu, 14 Nov 2013 20:34:24 +0000 From: Marcus Reid To: Devin Teske Subject: Re: Defaults in 10.0 ZFS through bsdinstall Message-ID: <20131114203424.GA22267@blazingdot.com> References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs , freebsd-current@freebsd.org, "Teske, Devin" , Allan Jude X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 20:34:25 -0000 On Thu, Nov 14, 2013 at 06:35:43PM +0000, Teske, Devin wrote: > On Nov 14, 2013, at 10:21 AM, Allan Jude wrote: > > On 2013-11-14 9:34, Reid, Marcus wrote: > > > > Hi, > > > > I noticed a couple of things with the ZFS defaults that result from > > using the new installer in 10.0-BETA3. > > > > One, atime is turned off everywhere by default. There was a thread > > on this list on June 8 with a subject of 'Changing the default for > > ZFS atime to off?', and from what I can tell the idea of turning off > > atime by default was not a popular one. > > > > Two, and probably less controversial, is that fletcher4 is specified > > exlicitly on the root pool, even though it is default (wouldn't you > > just want to go with the default, in case it changes?) > > > > Marcus > > I have never heard a good argument for having atime on. Can you address some of the issues that people brought up in the thread I mentioned earlier? I'll summarize some: - breaks some software (MTAs were mentioned), and the admin should know when to turn atime on in those cases. - "any mail program using mbox mail folders uses them to correctly report which mailboxes have not been read yet" - "Of course it can't be turned off by default. It is specified by POSIX." - "If the overhead were a real problem then file systems would use a special atime cache" > The performance penalty on ZFS is quite large This is subjective, and if it were that bad it seems like other ZFS-based systems would have turned it off as well, or done something like caching/logging or relatime it to mitigate the performance hit. > and it also makes your snapshots grow constant. This does not seem to be the case. For example, if I snapshot zroot/usr/src and then tar it up, I generate a bunch of writes and the snapshot grows to 70.5MB. However, when I tar it up a second time, there are writes but the snapshot remains 70.5MB. It seems to use the same blocks for subsequent atime updates. If you made another snapshot, you would see more space used for that one, of course. > If you have a use for it, you can turn it on I guess. This would be > solved by having the dataset editor we're planning for 10.1 > > Seems easy enough to turn on once installed. And like Allan says, the > editor for 10.1 would allow changing of the default. The same case could be made for turning it off, make that an option in the installer instead. Some people don't seem to use atime on a regular basis, but I use it a lot when troubleshooting things, and I think others do to when they get to the point where they realize how useful it is. > I'll add that if scripting it, you can (in current state for 10.0) > change the dataset options at-will. > > The fletcher4 thing is a leftover, from older versions of ZFS where > the default was fletcher2, I suppose we can remove it While I'm picking nits: There are some other locally set things that are default (exec set to on on zroot/var/tmp is one), that might just inherit that from zroot/var. Also, zroot doesn't appear to be mounted on /zroot, as it is on other ZFS-based systems. This has the side-effect of newly created datasets not having a mountpoint by default, instead of /zroot/dataset. I don't know of the reason behind this change either. I'm going to cross-post this to -current, this is a topic that I think warrants a wider audience. Thanks, Marcus > > > Let me put something together. > - -- > Devin > > -----BEGIN PGP SIGNATURE----- > Comment: GPGTools - https://gpgtools.org > > iQEcBAEBCgAGBQJShRf/AAoJEKrMn5R9npq5TYwH/j8RMceM4STpCAoMTAz8zkKn > gpftMrdf37TnAPHxsXJaiZejlp+D85/a9lglYbB7e4WdgoDX9ZXA0QLtCEmEtN4y > jz7KNa5oABq1GjDtwm2xQISDIe8yYI+znLSaHA9W18kCUZzi8AOj70C+O5gyY28c > c3N3j6Y4EZP2wtQnWSgxvCwIX5p86Jvr3QvhrRuuMnKMCTAhzwIx24qcnA4EcTzn > p9w25CKLtOzF23n3McodaUmibbBCHOYyraLQJ+eJGDXcsPBipls3oiWyiYuqpcQr > 18QpLN1lS35RnULcb5pxnP9Oy9rAwxHKves9Mfu0UoWw3qTjSAf8gsGyu6QaMgc= > =GjYk > -----END PGP SIGNATURE----- > > _____________ > The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 20:50:05 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 994493EF for ; Thu, 14 Nov 2013 20:50:05 +0000 (UTC) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6ED5A2C81 for ; Thu, 14 Nov 2013 20:50:04 +0000 (UTC) Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 5DBDD210F4 for ; Thu, 14 Nov 2013 15:49:58 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute1.internal (MEProxy); Thu, 14 Nov 2013 15:49:58 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=xlxw1JPQQdPs935bgXPs6OBb0aE=; b=bxp ykO+3CrDApudf3xKJnqgCDPksFHAqdNMTTl99kIVP30hWJCUUYGh2XiSVAhk+Kqw B+IJwbSyQ2lWnSn+mXsyzEN++NzD8BPbqx2TGUhBm5QZFrBPFoGUqU2KPNC36wGp vk3+4mdjjUpAe0z3mjkYnfz1XiEB9Phg5ywY5X8Y= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 3E1DF1C1E14; Thu, 14 Nov 2013 15:49:58 -0500 (EST) Message-Id: <1384462198.13183.47596065.6F8E7BCD@webmail.messagingengine.com> X-Sasl-Enc: mTYzO+aTVnZsyzb2kaoa7AKU9/YD6hAySiKWS5x8af1A 1384462198 From: Mark Felder To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-d4893488 In-Reply-To: <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> Subject: Re: Defaults in 10.0 ZFS through bsdinstall Date: Thu, 14 Nov 2013 14:49:58 -0600 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 20:50:05 -0000 On Thu, Nov 14, 2013, at 12:35, Teske, Devin wrote: > > I have never heard a good argument for having atime on. The performance > penalty on ZFS is quite large, and it also makes your snapshots grow > constant. If you have a use for it, you can turn it on I guess. This > would be solved by having the dataset editor we're planning for 10.1 > POLA and POSIX, even though it was a bad decision to invent atime :-) We've never turned atime off before and it would be a huge surprise to me, so I'd avocate that we let the admins who know what they're doing turn it off. I know many Linux distros install with noatime and/or nodiratime, but I'm 99% sure tools don't create filesystems with atime flagged to be off by default (tune2fs -O noatime). We don't even do installs on UFS with atime disabled by default in fstab so why should we so suddenly change course for ZFS? -my 2c From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 20:59:21 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3EAE4C17; Thu, 14 Nov 2013 20:59:21 +0000 (UTC) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AE6332D67; Thu, 14 Nov 2013 20:59:20 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50006720458.msg; Thu, 14 Nov 2013 20:59:16 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 14 Nov 2013 20:59:16 +0000 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=10308a6844=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <0CBA81A49FFC447C9452C9A27BC2D017@multiplay.co.uk> From: "Steven Hartland" To: "Mark Felder" , References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> <1384462198.13183.47596065.6F8E7BCD@webmail.messagingengine.com> Subject: Re: Defaults in 10.0 ZFS through bsdinstall Date: Thu, 14 Nov 2013 20:59:14 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 20:59:21 -0000 ----- Original Message ----- From: "Mark Felder" To: Sent: Thursday, November 14, 2013 8:49 PM Subject: Re: Defaults in 10.0 ZFS through bsdinstall > On Thu, Nov 14, 2013, at 12:35, Teske, Devin wrote: >> >> I have never heard a good argument for having atime on. The performance >> penalty on ZFS is quite large, and it also makes your snapshots grow >> constant. If you have a use for it, you can turn it on I guess. This >> would be solved by having the dataset editor we're planning for 10.1 >> > > POLA and POSIX, even though it was a bad decision to invent atime :-) > We've never turned atime off before and it would be a huge surprise to > me, so I'd avocate that we let the admins who know what they're doing > turn it off. I know many Linux distros install with noatime and/or > nodiratime, but I'm 99% sure tools don't create filesystems with atime > flagged to be off by default (tune2fs -O noatime). > > We don't even do installs on UFS with atime disabled by default in fstab > so why should we so suddenly change course for ZFS? While I can see the reason some would argue to keep it on by default I personally think this is a good change. Why punish everyone forever due to poor design decision made in the distant past, just because a few select applications make use of said feature? Is not a change which benefits the masses but comes with a slight inconvenience of the select few, where they need to enable a feature no one else needs a good idea? Sure it needs to be clearly messaged so its not a surprise, but if thats done I'm all for it. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 21:02:36 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 122D1DD6; Thu, 14 Nov 2013 21:02:36 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CFAB92DC2; Thu, 14 Nov 2013 21:02:35 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id rAEL2SHm026874 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Nov 2013 15:02:28 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.152]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 15:02:27 -0600 From: "Teske, Devin" To: Mark Felder Subject: Re: Defaults in 10.0 ZFS through bsdinstall Thread-Topic: Defaults in 10.0 ZFS through bsdinstall Thread-Index: AQHO4WP56r1WdCmD2k+in4awofQcqw== Date: Thu, 14 Nov 2013 21:02:26 +0000 Message-ID: <55232624-3B76-4781-91E0-0C2A6260144D@fisglobal.com> References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> <1384462198.13183.47596065.6F8E7BCD@webmail.messagingengine.com> In-Reply-To: <1384462198.13183.47596065.6F8E7BCD@webmail.messagingengine.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="us-ascii" Content-ID: <36A53F97AF11C24593C905567FFD863C@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.14, 0.0.0000 definitions=2013-11-14_07:2013-11-13,2013-11-14,1970-01-01 signatures=0 Cc: freebsd-fs , Devin Teske , "Teske, Devin" , Allan Jude X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Devin Teske List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 21:02:36 -0000 On Nov 14, 2013, at 12:49 PM, Mark Felder wrote: > On Thu, Nov 14, 2013, at 12:35, Teske, Devin wrote: >>=20 Correction: Allan Jude said the following... NB: You replied to an e-mail that had bad quoting (which I fixed in a later= reply) >> I have never heard a good argument for having atime on. The performance >> penalty on ZFS is quite large, and it also makes your snapshots grow >> constant. If you have a use for it, you can turn it on I guess. This >> would be solved by having the dataset editor we're planning for 10.1 >>=20 >=20 > POLA and POSIX, even though it was a bad decision to invent atime :-) > We've never turned atime off before and it would be a huge surprise to > me, so I'd avocate that we let the admins who know what they're doing > turn it off. I know many Linux distros install with noatime and/or > nodiratime, but I'm 99% sure tools don't create filesystems with atime > flagged to be off by default (tune2fs -O noatime).=20 >=20 Fair enough... I'll hold out for Allan's +1 since I didn't have anything to= do with this. > We don't even do installs on UFS with atime disabled by default in fstab > so why should we so suddenly change course for ZFS? >=20 You've made a good point. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 21:04:11 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 86BFDFD6; Thu, 14 Nov 2013 21:04:11 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5025F2DD9; Thu, 14 Nov 2013 21:04:10 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id rAEL48uY029102 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Nov 2013 15:04:08 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.152]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 15:04:07 -0600 From: "Teske, Devin" To: Steven Hartland Subject: Re: Defaults in 10.0 ZFS through bsdinstall Thread-Topic: Defaults in 10.0 ZFS through bsdinstall Thread-Index: AQHO4WP56r1WdCmD2k+in4awofQcqw== Date: Thu, 14 Nov 2013 21:04:07 +0000 Message-ID: <9A38EBE3-4012-4165-8655-03330277B04A@fisglobal.com> References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> <1384462198.13183.47596065.6F8E7BCD@webmail.messagingengine.com> <0CBA81A49FFC447C9452C9A27BC2D017@multiplay.co.uk> In-Reply-To: <0CBA81A49FFC447C9452C9A27BC2D017@multiplay.co.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="us-ascii" Content-ID: <080B0D740B5A8446A9B20B62862843D2@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.14, 0.0.0000 definitions=2013-11-14_07:2013-11-13,2013-11-14,1970-01-01 signatures=0 Cc: freebsd-fs , Devin Teske , "Teske, Devin" , Allan Jude X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Devin Teske List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 21:04:11 -0000 On Nov 14, 2013, at 12:59 PM, Steven Hartland wrote: > ----- Original Message ----- From: "Mark Felder" > To: > Sent: Thursday, November 14, 2013 8:49 PM > Subject: Re: Defaults in 10.0 ZFS through bsdinstall >=20 >=20 >> On Thu, Nov 14, 2013, at 12:35, Teske, Devin wrote: >>> I have never heard a good argument for having atime on. The performance >>> penalty on ZFS is quite large, and it also makes your snapshots grow >>> constant. If you have a use for it, you can turn it on I guess. This >>> would be solved by having the dataset editor we're planning for 10.1 >> POLA and POSIX, even though it was a bad decision to invent atime :-) >> We've never turned atime off before and it would be a huge surprise to >> me, so I'd avocate that we let the admins who know what they're doing >> turn it off. I know many Linux distros install with noatime and/or >> nodiratime, but I'm 99% sure tools don't create filesystems with atime >> flagged to be off by default (tune2fs -O noatime). We don't even do inst= alls on UFS with atime disabled by default in fstab >> so why should we so suddenly change course for ZFS? >=20 > While I can see the reason some would argue to keep it on by default > I personally think this is a good change. >=20 > Why punish everyone forever due to poor design decision made in the dista= nt > past, just because a few select applications make use of said feature? >=20 > Is not a change which benefits the masses but comes with a slight > inconvenience of the select few, where they need to enable a feature > no one else needs a good idea? >=20 > Sure it needs to be clearly messaged so its not a surprise, but if thats > done I'm all for it. >=20 Sounds like a vote for enabling it where-needed by-default (e.g., /var as a= whole or more selectively, /var/mail) --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 21:04:34 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A5751C3; Thu, 14 Nov 2013 21:04:34 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 549C42DE6; Thu, 14 Nov 2013 21:04:34 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id rAEL4Qb9021943 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Nov 2013 15:04:26 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.152]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 15:04:24 -0600 From: "Teske, Devin" To: Marcus Reid Subject: Re: Defaults in 10.0 ZFS through bsdinstall Thread-Topic: Defaults in 10.0 ZFS through bsdinstall Thread-Index: AQHO4WP56r1WdCmD2k+in4awofQcqw== Date: Thu, 14 Nov 2013 21:04:23 +0000 Message-ID: References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> <20131114203424.GA22267@blazingdot.com> In-Reply-To: <20131114203424.GA22267@blazingdot.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="us-ascii" Content-ID: <7E3EBB51ACF7F3468410C0EEC8412229@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.14, 0.0.0000 definitions=2013-11-14_07:2013-11-13,2013-11-14,1970-01-01 signatures=0 Cc: freebsd-fs , Devin Teske , "Teske, Devin" , FreeBSD Current , Allan Jude X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Devin Teske List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 21:04:34 -0000 On Nov 14, 2013, at 12:34 PM, Marcus Reid wrote: > On Thu, Nov 14, 2013 at 06:35:43PM +0000, Teske, Devin wrote: >> On Nov 14, 2013, at 10:21 AM, Allan Jude wrote: >>> On 2013-11-14 9:34, Reid, Marcus wrote: >>>=20 >>> Hi, >>>=20 >>> I noticed a couple of things with the ZFS defaults that result from >>> using the new installer in 10.0-BETA3. >>>=20 >>> One, atime is turned off everywhere by default. There was a thread >>> on this list on June 8 with a subject of 'Changing the default for >>> ZFS atime to off?', and from what I can tell the idea of turning off >>> atime by default was not a popular one. >>>=20 >>> Two, and probably less controversial, is that fletcher4 is specified >>> exlicitly on the root pool, even though it is default (wouldn't you >>> just want to go with the default, in case it changes?) >>>=20 >>> Marcus >>=20 >> I have never heard a good argument for having atime on. >=20 > Can you address some of the issues that people brought up in the thread > I mentioned earlier? I'll summarize some: >=20 > - breaks some software (MTAs were mentioned), and the admin should > know when to turn atime on in those cases. >=20 > - "any mail program using mbox mail folders uses them to correctly > report which mailboxes have not been read yet" >=20 I'm looking at HEAD and I don't see "atime=3Doff" for the /var dataset. Knowing that most folks (accepting the defaults) will store their mail in /var/mail ... does the concern over atime=3Doff still exist? However, I did notice that before we go creating the /var dataset, we do set "atime=3Doff" for the boot pool/dataset. Is inheritance at-play here? and /var is turning up with atime=3Doff even though it's not specified? In that case, I certainly agree we should remove atime=3Doff from the last place it is used -- the boot pool (nowhere else). > - "Of course it can't be turned off by default. It is specified by > POSIX." >=20 > - "If the overhead were a real problem then file systems would use a > special atime cache" >=20 >> The performance penalty on ZFS is quite large >=20 > This is subjective, and if it were that bad it seems like other > ZFS-based systems would have turned it off as well, or done something > like caching/logging or relatime it to mitigate the performance hit. >=20 I do recall discussions about bringing over relatime and making it the default. Allan was the one that brought up the performance hit... Similarly where I $work, we turn it off where need performance (large storage arrays and such). I gather it's only a matter of time until relatime is default. >> and it also makes your snapshots grow constant. >=20 > This does not seem to be the case. For example, if I snapshot > zroot/usr/src and then tar it up, I generate a bunch of writes and the > snapshot grows to 70.5MB. However, when I tar it up a second time, > there are writes but the snapshot remains 70.5MB. It seems to use the > same blocks for subsequent atime updates. >=20 > If you made another snapshot, you would see more space used for that > one, of course. >=20 I'll defer to Allan to expand (was his recollection on snapshots) >> If you have a use for it, you can turn it on I guess. This would be >> solved by having the dataset editor we're planning for 10.1 >>=20 >> Seems easy enough to turn on once installed. And like Allan says, the >> editor for 10.1 would allow changing of the default. >=20 > The same case could be made for turning it off, make that an option in > the installer instead. >=20 Fair enough. Good idea. > Some people don't seem to use atime on a regular basis, but I use it a > lot when troubleshooting things, and I think others do to when they get > to the point where they realize how useful it is. >=20 >> I'll add that if scripting it, you can (in current state for 10.0) >> change the dataset options at-will. >>=20 >> The fletcher4 thing is a leftover, from older versions of ZFS where >> the default was fletcher2, I suppose we can remove it >=20 > While I'm picking nits: >=20 > There are some other locally set things that are default (exec set to on > on zroot/var/tmp is one), that might just inherit that from zroot/var. >=20 Need a +1 from Allan on that. > Also, zroot doesn't appear to be mounted on /zroot, as it is on other > ZFS-based systems. This has the side-effect of newly created > datasets not having a mountpoint by default, instead of /zroot/dataset. > I don't know of the reason behind this change either. >=20 Hmm, wonder if that's been fixed in HEAD already. > I'm going to cross-post this to -current, this is a topic that I think > warrants a wider audience. >=20 Cool. Thanks. --=20 Devin >> -----BEGIN PGP SIGNATURE----- >> Comment: GPGTools - https://urldefense.proofpoint.com/v1/url?u=3Dhttps:/= /gpgtools.org/&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=3DLTzUWWrRnz2iN3Pt= HDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DwXwxswJCpc3K%2Bud90aYI%2B82v%2Fyfs1= mrTBzzeCe5XIXw%3D%0A&s=3Da9e0697e43ce4744f130997648d0104319221bba6924c28a94= 93ffa1cf6c3719 >>=20 >> iQEcBAEBCgAGBQJShRf/AAoJEKrMn5R9npq5TYwH/j8RMceM4STpCAoMTAz8zkKn >> gpftMrdf37TnAPHxsXJaiZejlp+D85/a9lglYbB7e4WdgoDX9ZXA0QLtCEmEtN4y >> jz7KNa5oABq1GjDtwm2xQISDIe8yYI+znLSaHA9W18kCUZzi8AOj70C+O5gyY28c >> c3N3j6Y4EZP2wtQnWSgxvCwIX5p86Jvr3QvhrRuuMnKMCTAhzwIx24qcnA4EcTzn >> p9w25CKLtOzF23n3McodaUmibbBCHOYyraLQJ+eJGDXcsPBipls3oiWyiYuqpcQr >> 18QpLN1lS35RnULcb5pxnP9Oy9rAwxHKves9Mfu0UoWw3qTjSAf8gsGyu6QaMgc=3D >> =3DGjYk >> -----END PGP SIGNATURE----- >>=20 >> _____________ >> The information contained in this message is proprietary and/or confiden= tial. If you are not the intended recipient, please: (i) delete the message= and all copies; (ii) do not disclose, distribute or use the message in any= manner; and (iii) notify the sender immediately. In addition, please be aw= are that any message addressed to our domain is subject to archiving and re= view by persons other than the intended recipient. Thank you. _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 14 21:04:31 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 743FCC7; Thu, 14 Nov 2013 21:04:31 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3E1D02DE5; Thu, 14 Nov 2013 21:04:31 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id rAEL4Po0021942 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Nov 2013 15:04:25 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.152]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 15:04:24 -0600 From: "Teske, Devin" To: Marcus Reid Subject: Re: Defaults in 10.0 ZFS through bsdinstall Thread-Topic: Defaults in 10.0 ZFS through bsdinstall Thread-Index: AQHO4WP56r1WdCmD2k+in4awofQcqw== Date: Thu, 14 Nov 2013 21:04:23 +0000 Message-ID: <19B09C7A-10E5-41BC-BD5E-B15179651F6D@fisglobal.com> References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> <20131114203424.GA22267@blazingdot.com> In-Reply-To: <20131114203424.GA22267@blazingdot.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.14, 0.0.0000 definitions=2013-11-14_07:2013-11-13,2013-11-14,1970-01-01 signatures=0 Cc: freebsd-fs , Devin Teske , "Teske, Devin" , FreeBSD Current , Allan Jude X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Devin Teske List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 21:04:31 -0000 On Nov 14, 2013, at 12:34 PM, Marcus Reid wrote: > On Thu, Nov 14, 2013 at 06:35:43PM +0000, Teske, Devin wrote: >> On Nov 14, 2013, at 10:21 AM, Allan Jude wrote: >>> On 2013-11-14 9:34, Reid, Marcus wrote: >>>=20 >>> Hi, >>>=20 >>> I noticed a couple of things with the ZFS defaults that result from >>> using the new installer in 10.0-BETA3. >>>=20 >>> One, atime is turned off everywhere by default. There was a thread >>> on this list on June 8 with a subject of 'Changing the default for >>> ZFS atime to off?', and from what I can tell the idea of turning off >>> atime by default was not a popular one. >>>=20 >>> Two, and probably less controversial, is that fletcher4 is specified >>> exlicitly on the root pool, even though it is default (wouldn't you >>> just want to go with the default, in case it changes?) >>>=20 >>> Marcus >>=20 >> I have never heard a good argument for having atime on. >=20 > Can you address some of the issues that people brought up in the thread > I mentioned earlier? I'll summarize some: >=20 > - breaks some software (MTAs were mentioned), and the admin should > know when to turn atime on in those cases. >=20 > - "any mail program using mbox mail folders uses them to correctly > report which mailboxes have not been read yet" >=20 I'm looking at HEAD and I don't see "atime=3Doff" for the /var dataset. Knowing that most folks (accepting the defaults) will store their mail in /var/mail ... does the concern over atime=3Doff still exist? However, I did notice that before we go creating the /var dataset, we do set "atime=3Doff" for the boot pool/dataset. Is inheritance at-play here? and /var is turning up with atime=3Doff even though it's not specified? In that case, I certainly agree we should remove atime=3Doff from the last place it is used -- the boot pool (nowhere else). > - "Of course it can't be turned off by default. It is specified by > POSIX." >=20 > - "If the overhead were a real problem then file systems would use a > special atime cache" >=20 >> The performance penalty on ZFS is quite large >=20 > This is subjective, and if it were that bad it seems like other > ZFS-based systems would have turned it off as well, or done something > like caching/logging or relatime it to mitigate the performance hit. >=20 I do recall discussions about bringing over relatime and making it the default. Allan was the one that brought up the performance hit... Similarly where I $work, we turn it off where need performance (large storage arrays and such). I gather it's only a matter of time until relatime is default. >> and it also makes your snapshots grow constant. >=20 > This does not seem to be the case. For example, if I snapshot > zroot/usr/src and then tar it up, I generate a bunch of writes and the > snapshot grows to 70.5MB. However, when I tar it up a second time, > there are writes but the snapshot remains 70.5MB. It seems to use the > same blocks for subsequent atime updates. >=20 > If you made another snapshot, you would see more space used for that > one, of course. >=20 I'll defer to Allan to expand (was his recollection on snapshots) >> If you have a use for it, you can turn it on I guess. This would be >> solved by having the dataset editor we're planning for 10.1 >>=20 >> Seems easy enough to turn on once installed. And like Allan says, the >> editor for 10.1 would allow changing of the default. >=20 > The same case could be made for turning it off, make that an option in > the installer instead. >=20 Fair enough. Good idea. > Some people don't seem to use atime on a regular basis, but I use it a > lot when troubleshooting things, and I think others do to when they get > to the point where they realize how useful it is. >=20 >> I'll add that if scripting it, you can (in current state for 10.0) >> change the dataset options at-will. >>=20 >> The fletcher4 thing is a leftover, from older versions of ZFS where >> the default was fletcher2, I suppose we can remove it >=20 > While I'm picking nits: >=20 > There are some other locally set things that are default (exec set to on > on zroot/var/tmp is one), that might just inherit that from zroot/var. >=20 Need a +1 from Allan on that. > Also, zroot doesn't appear to be mounted on /zroot, as it is on other > ZFS-based systems. This has the side-effect of newly created > datasets not having a mountpoint by default, instead of /zroot/dataset. > I don't know of the reason behind this change either. >=20 Hmm, wonder if that's been fixed in HEAD already. > I'm going to cross-post this to -current, this is a topic that I think > warrants a wider audience. >=20 Cool. Thanks. --=20 Devin >> -----BEGIN PGP SIGNATURE----- >> Comment: GPGTools - https://urldefense.proofpoint.com/v1/url?u=3Dhttps:/= /gpgtools.org/&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=3DLTzUWWrRnz2iN3Pt= HDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DwXwxswJCpc3K%2Bud90aYI%2B82v%2Fyfs1= mrTBzzeCe5XIXw%3D%0A&s=3Da9e0697e43ce4744f130997648d0104319221bba6924c28a94= 93ffa1cf6c3719 >>=20 >> iQEcBAEBCgAGBQJShRf/AAoJEKrMn5R9npq5TYwH/j8RMceM4STpCAoMTAz8zkKn >> gpftMrdf37TnAPHxsXJaiZejlp+D85/a9lglYbB7e4WdgoDX9ZXA0QLtCEmEtN4y >> jz7KNa5oABq1GjDtwm2xQISDIe8yYI+znLSaHA9W18kCUZzi8AOj70C+O5gyY28c >> c3N3j6Y4EZP2wtQnWSgxvCwIX5p86Jvr3QvhrRuuMnKMCTAhzwIx24qcnA4EcTzn >> p9w25CKLtOzF23n3McodaUmibbBCHOYyraLQJ+eJGDXcsPBipls3oiWyiYuqpcQr >> 18QpLN1lS35RnULcb5pxnP9Oy9rAwxHKves9Mfu0UoWw3qTjSAf8gsGyu6QaMgc=3D >> =3DGjYk >> -----END PGP SIGNATURE----- >>=20 >> _____________ >> The information contained in this message is proprietary and/or confiden= tial. If you are not the intended recipient, please: (i) delete the message= and all copies; (ii) do not disclose, distribute or use the message in any= manner; and (iii) notify the sender immediately. In addition, please be aw= are that any message addressed to our domain is subject to archiving and re= view by persons other than the intended recipient. Thank you. _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-fs@FreeBSD.ORG Fri Nov 15 00:00:44 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C353ED4; Fri, 15 Nov 2013 00:00:44 +0000 (UTC) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C821A2895; Fri, 15 Nov 2013 00:00:42 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 4D75D20B7C; Thu, 14 Nov 2013 19:00:41 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 14 Nov 2013 19:00:41 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=8p8 8q6PbTHj8uK8nD2csTTECGJ4=; b=YxIKSHUaeVUUyHJxZY2R44nLhBWjxBTF8a1 vjmxgfhLEvmN44mSHqRBNI3O8Ghl1R7EeSit4JWG2Ucj8C8ckDlhjAWFaYb5uuxX ZJuEQcqI3Fewr9kbfQ6g3KZeOurQHqk8Rs+KC6UPVcU6CRYbLCTziWjPkIpVfpOf 7h5w+FnE= X-Sasl-enc: p2D3O4OsSqYtX1RgHgUPQwRzAloT3Pjc3TpQcvzV7SB1 1384473641 Received: from [172.16.1.145] (unknown [68.117.126.78]) by mail.messagingengine.com (Postfix) with ESMTPA id 50B84C00E83; Thu, 14 Nov 2013 19:00:40 -0500 (EST) Content-Type: multipart/signed; boundary="Apple-Mail=_F8778D7A-F4EA-47AC-B567-7DEAB74CC4FB"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: Defaults in 10.0 ZFS through bsdinstall From: Mark Felder In-Reply-To: <9A38EBE3-4012-4165-8655-03330277B04A@fisglobal.com> Date: Thu, 14 Nov 2013 18:00:38 -0600 Message-Id: <55AA006F-E70E-4434-84EE-97049150AEDF@FreeBSD.org> References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> <1384462198.13183.47596065.6F8E7BCD@webmail.messagingengine.com> <0CBA81A49FFC447C9452C9A27BC2D017@multiplay.co.uk> <9A38EBE3-4012-4165-8655-03330277B04A@fisglobal.com> To: Devin Teske X-Mailer: Apple Mail (2.1822) Cc: freebsd-fs , "Teske, Devin" , Allan Jude X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 00:00:44 -0000 --Apple-Mail=_F8778D7A-F4EA-47AC-B567-7DEAB74CC4FB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Nov 14, 2013, at 15:04, Teske, Devin = wrote: > On Nov 14, 2013, at 12:59 PM, Steven Hartland wrote: >=20 >> ----- Original Message ----- From: "Mark Felder" >> To: >> Sent: Thursday, November 14, 2013 8:49 PM >> Subject: Re: Defaults in 10.0 ZFS through bsdinstall >>=20 >>=20 >>> On Thu, Nov 14, 2013, at 12:35, Teske, Devin wrote: >>>> I have never heard a good argument for having atime on. The = performance >>>> penalty on ZFS is quite large, and it also makes your snapshots = grow >>>> constant. If you have a use for it, you can turn it on I guess. = This >>>> would be solved by having the dataset editor we're planning for = 10.1 >>> POLA and POSIX, even though it was a bad decision to invent atime = :-) >>> We've never turned atime off before and it would be a huge surprise = to >>> me, so I'd avocate that we let the admins who know what they're = doing >>> turn it off. I know many Linux distros install with noatime and/or >>> nodiratime, but I'm 99% sure tools don't create filesystems with = atime >>> flagged to be off by default (tune2fs -O noatime). We don't even do = installs on UFS with atime disabled by default in fstab >>> so why should we so suddenly change course for ZFS? >>=20 >> While I can see the reason some would argue to keep it on by default >> I personally think this is a good change. >>=20 >> Why punish everyone forever due to poor design decision made in the = distant >> past, just because a few select applications make use of said = feature? >>=20 >> Is not a change which benefits the masses but comes with a slight >> inconvenience of the select few, where they need to enable a feature >> no one else needs a good idea? >>=20 >> Sure it needs to be clearly messaged so its not a surprise, but if = thats >> done I'm all for it. >>=20 >=20 > Sounds like a vote for enabling it where-needed by-default (e.g., /var = as a whole > or more selectively, /var/mail) I'd be OK with FreeBSD taking a stance and moving to noatime by default = but we should be consistent across all filesystems that a user can = install the OS on from our provided installation media. We should make = it obvious to the end users as well. --Apple-Mail=_F8778D7A-F4EA-47AC-B567-7DEAB74CC4FB Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJShWQnAAoJEJg7ZFAfE+JSvt0H/0B8e5R7TNLoruxdvNXzbuPc M5pNCNYcrJxVNWWaMLqivsQqIlDDgOFYZDc88qK7LJKPsMieIo0cjs891M2KXLC+ 5RCTQOrLYeCxfCnoOxbSip/azYjJqC6VbDUe4j59Kgw0SyQ8UNCXrTZbyu+OPL/A DQ5s7EshnjozsJ2I1HDfSPVuUJ81F6rJtoWIbXaemdPZ+rUun/5hF4GMOyYtmMFZ ga+zc84efHXdHN7COcyORWv/F+FSfr7+PlEk3HNUEBSzmh+4SQXDlxGWzcuU5VEs MRW9YcjNWt4oN7JWfAqXLEvHKrbOqO5nbTwe4l/T+ah+xIduNu5qSSOlGaAstOk= =adGZ -----END PGP SIGNATURE----- --Apple-Mail=_F8778D7A-F4EA-47AC-B567-7DEAB74CC4FB-- From owner-freebsd-fs@FreeBSD.ORG Fri Nov 15 03:50:06 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDD6F91D for ; Fri, 15 Nov 2013 03:50:06 +0000 (UTC) Received: from barracuda.imaginaryforces.com (199.193.209.132.static.oneiricsys.com [199.193.209.132]) by mx1.freebsd.org (Postfix) with ESMTP id A665F257E for ; Fri, 15 Nov 2013 03:50:02 +0000 (UTC) X-ASG-Debug-ID: 1384487396-0413ad070f26a20001-dE2xID Received: from newman.IMAGINARYFORCES.LOCAL (newman.imaginaryforces.local [192.168.23.34]) by barracuda.imaginaryforces.com with ESMTP id 3IymLapLzPakEHNu for ; Thu, 14 Nov 2013 19:49:56 -0800 (PST) X-Barracuda-Envelope-From: shawn.wallbridge@imaginaryforces.com Received: from NEWMAN.IMAGINARYFORCES.LOCAL ([192.168.23.34]) by newman.IMAGINARYFORCES.LOCAL ([192.168.23.34]) with mapi id 14.01.0438.000; Thu, 14 Nov 2013 19:49:54 -0800 From: Shawn Wallbridge To: "freebsd-fs@FreeBSD.org" Subject: Re: Controller for ZFS Thread-Topic: Controller for ZFS X-ASG-Orig-Subj: Re: Controller for ZFS Thread-Index: AQHO4KAGQyooEFhCi0SGL6HvFgG6/ZolEzkAgACXAIA= Date: Fri, 15 Nov 2013 03:49:53 +0000 Message-ID: In-Reply-To: <49F719A9-AC50-4917-8809-F51EBD4F5D0F@sarenet.es> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.23.68] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: newman.imaginaryforces.local[192.168.23.34] X-Barracuda-Start-Time: 1384487396 X-Barracuda-URL: http://barracuda.imaginaryforces.com:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at imaginaryforces.com X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.142326 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 03:50:07 -0000 On 11/14/13 2:49 AM, "Borja Marcos" wrote: > >On Nov 13, 2013, at 7:41 PM, Shawn Wallbridge wrote: > >> I was wondering what the preferred/best supported 24port SAS/SATA >> controller is for FreeBSD? I have a box with a LSI/3Ware 9750-24i4e in >>it, >> which I can use in JBOD mode, but it seems like a waste to me. > >Not only a waste, but a serious problem. > >You absolutely do not want a "JBOD mode" in which you create so-called >RAID0 1-drive logical volumes. > >You absolutely do want a silly and stupid HBA which just passes SAS/SATA >commands from the OS to the drives >and back. > >The "JBOD mode" offers a fake device in which the "intelligent" >controller makes its own decisions and, of course, hides >the very important SAS/SATA status codes from the OS. > >ZFS knows better. > >The one I use is sold by Dell as the "H200". They usually try to disuade >you by saying that it's not intelligent, doesn't >offer RAID, some of their "configuration aids" even forbid it... I just >tell the salesman to shut up because I know much better than him. > >The only problem: beware if you are using a built-in backplane in the >server, some manufacturers insist on using different >cabling schemes for different controllers and you could run into stupid >problems because of that. > >FreeBSD 10 identifies one of my cards as this one: >mps0: port 0x7c00-0x7cff mem >0xd4ff0000-0xd4ffffff,0xd4f80000-0xd4fbffff irq 80 at device 0.0 on pci67 >mps0: Firmware: 07.15.08.00, Driver: 16.00.00.00-fbsd >mps0: IOCCapabilities: >185c > >Borja. I was leaning towards two of these. http://www.newegg.com/Product/Product.aspx?&Item=3DN82E16816118142 LSI LSI00244 (9201-16i) PCI-Express 2.0 x8 SATA / SAS Host Bus Adapter Card, What do you guys think? shawn ________________________________ This e-mail is intended only for the named person or entity to which it is = addressed and contains valuable business information that is proprietary, p= rivileged, confidential and/or otherwise protected from disclosure. If you = received this e-mail in error, any review, use, dissemination, distribution= or copying of this e-mail is strictly prohibited. Please notify us immedia= tely of the error via e-mail to postmaster@imaginaryforces.c= om and please delete the e-mail from your system, retaining no copies in an= y media. We appreciate your cooperation. ...imaginaryforces.com...=0D From owner-freebsd-fs@FreeBSD.ORG Fri Nov 15 08:58:24 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7C91A15 for ; Fri, 15 Nov 2013 08:58:24 +0000 (UTC) Received: from nm16.bullet.mail.ir2.yahoo.com (nm16.bullet.mail.ir2.yahoo.com [212.82.96.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F01FB28AC for ; Fri, 15 Nov 2013 08:58:23 +0000 (UTC) Received: from [212.82.98.125] by nm16.bullet.mail.ir2.yahoo.com with NNFMP; 15 Nov 2013 08:58:14 -0000 Received: from [46.228.39.90] by tm18.bullet.mail.ir2.yahoo.com with NNFMP; 15 Nov 2013 08:58:14 -0000 Received: from [127.0.0.1] by smtp127.mail.ir2.yahoo.com with NNFMP; 15 Nov 2013 08:58:14 -0000 X-Yahoo-Newman-Id: 948437.93391.bm@smtp127.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 7YjmUiAVM1lxyjbtl0m9ymTaFTMnAwCzo1llK.i.hsfApDp 9jI4mRHa6o9azh.6MFq_tge8v2Hs2Pn3ZNHHnMRVIcIR7d33.rCwt1CTn_uk y_4nCwvYorraPQtTrpUx8JwrAlcN.cOObVly6.ght.ok2M32fiYMycJDRFWw 9m6BMtMRsPCiZ5HiPkZ3ac7c4laPNGxqIRSnnh9Ac_1MvB6omA13PuVtW0qD FaNfgQ.Xxhbhd2I.fxNyg_uUg3YkOXxpO2U3Ct1NuVDD963s5hX1pV.ZQCgs GVcOv9mABTwhMhXj6xGBZJaFto.Cpkl2RdF1tkt_9ja90azP..DUCaJiCu3G odLD8puj0TUi0Chnxosz.hthglXHJ8QTSkww7ezN0CKf1tO0lIT629rYp8ai gk0SidaRh88KsCLwDkPGNyK7QxqB1QZXeKJQPSg_rvg5Tdj.j3c57lQuwhRg lBTDWnmzsM.WuhwCWbwT4qXMm7iC92ZKZqYfWys4qlcEujr2Op3lZgH7rHeA dmU88RAuft5BA9cxyVoG6BQmLMFXimaaB X-Yahoo-SMTP: iDf2N9.swBDAhYEh7VHfpgq0lnq. X-Rocket-Received: from [192.168.119.11] (se@84.154.100.25 with ) by smtp127.mail.ir2.yahoo.com with SMTP; 15 Nov 2013 08:58:14 +0000 UTC Message-ID: <5285E21D.6050701@freebsd.org> Date: Fri, 15 Nov 2013 09:58:05 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Defaults in 10.0 ZFS through bsdinstall References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> <1384462198.13183.47596065.6F8E7BCD@webmail.messagingengine.com> <0CBA81A49FFC447C9452C9A27BC2D017@multiplay.co.uk> <9A38EBE3-4012-4165-8655-03330277B04A@fisglobal.com> <55AA006F-E70E-4434-84EE-97049150AEDF@FreeBSD.org> In-Reply-To: <55AA006F-E70E-4434-84EE-97049150AEDF@FreeBSD.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 08:58:24 -0000 Am 15.11.2013 01:00, schrieb Mark Felder: > On Nov 14, 2013, at 15:04, Teske, Devin wrote: >> Sounds like a vote for enabling it where-needed by-default (e.g., /var as a whole >> or more selectively, /var/mail) > > I'd be OK with FreeBSD taking a stance and moving to noatime by default but we should be consistent across all filesystems that a user can install the OS on from our provided installation media. We should make it obvious to the end users as well. The cost of atime on UFS and ZFS is quite different. While I understand that consistency is a plus, I do think that there is good reason to have different defaults for UFS and ZFS. It would be good if there was a global parameter which let the user choose the atime setting for all file-systems where this setting is not overridden. Such a parameter could be OFF (noatime) for ZFS and ON for UFS by default, but with a short explanation about the consequences and a way to toggle this setting if desired. Regards, STefan From owner-freebsd-fs@FreeBSD.ORG Fri Nov 15 08:59:45 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9198FBC0 for ; Fri, 15 Nov 2013 08:59:45 +0000 (UTC) Received: from nm19-vm3.bullet.mail.ir2.yahoo.com (nm19-vm3.bullet.mail.ir2.yahoo.com [212.82.96.236]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CC21528CF for ; Fri, 15 Nov 2013 08:59:44 +0000 (UTC) Received: from [212.82.98.63] by nm19.bullet.mail.ir2.yahoo.com with NNFMP; 15 Nov 2013 08:53:27 -0000 Received: from [46.228.39.98] by tm16.bullet.mail.ir2.yahoo.com with NNFMP; 15 Nov 2013 08:53:27 -0000 Received: from [127.0.0.1] by smtp135.mail.ir2.yahoo.com with NNFMP; 15 Nov 2013 08:53:27 -0000 X-Yahoo-Newman-Id: 472508.46461.bm@smtp135.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 9tkUl2QVM1lWXGJ.oUZzij9uPRxvIdZJUnLdAm8vQUO2ivT 7l_9grkEq6nri5vOaTE3TRtbvq7LM266iPzTa6.5kj0ascLzTc3yxqB2izJv y3mwCyUOwPKpU43.L6YPY0GeHz8bxxQtrcGdeq5ZNOefudJU5.wlpFToybS9 z2V3jGpl52KkaB_5eiquA44Z0O2Qsxgf8BqVKx7HVHQOXDUAZP9bcCG2dlsX EC0__8Ro.P0.e1DLFPC58mk4Uq2tZt_Zk0e7Weng8r4HWd2oXqjM_V0kBEgl HL7AcIea3T7tlEftcNIk3ndCJ18fSn3KzWuOZ8jtFEJZ9lN1RpzlVmASS6Ae 3M37LCYsUsBadL1QEeVaE3Hb3zBLGPgyzVrUG0HYE5bO9kugkb3lmP.nSHD6 6M69ul.Ese.Glk5ohmwrB.IeRCrkr6oyG7z1UHlCAb.Ty_wJFUKKCh9XIKA2 omvANpVZp5nmsi8TXR3NVZXfulZYIEAFSIqxw.cQT.Wq_ZaVKTcLdv9.SPhA EejNsjb8C8bJAPP8u15QXaZkzZWbAmw-- X-Yahoo-SMTP: iDf2N9.swBDAhYEh7VHfpgq0lnq. X-Rocket-Received: from [192.168.119.11] (se@84.154.100.25 with ) by smtp135.mail.ir2.yahoo.com with SMTP; 15 Nov 2013 08:53:27 +0000 UTC Message-ID: <5285E0FD.8040205@freebsd.org> Date: Fri, 15 Nov 2013 09:53:17 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Re: Defaults in 10.0 ZFS through bsdinstall References: <20131114173423.GA21761@blazingdot.com> <59A9B68B-4134-4217-83F3-B99759174EFE@fisglobal.com> <5285148E.6020903@allanjude.com> <3D3332FA-0ABF-4573-8E65-4E7FBB37100B@fisglobal.com> <1384462198.13183.47596065.6F8E7BCD@webmail.messagingengine.com> <55232624-3B76-4781-91E0-0C2A6260144D@fisglobal.com> In-Reply-To: <55232624-3B76-4781-91E0-0C2A6260144D@fisglobal.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 08:59:45 -0000 Am 14.11.2013 22:02, schrieb Teske, Devin: > On Nov 14, 2013, at 12:49 PM, Mark Felder wrote: >> We don't even do installs on UFS with atime disabled by default in fstab >> so why should we so suddenly change course for ZFS? >> > > You've made a good point. There is major difference between UFS and ZFS: UFS allows in-place updates of i-node fields (like atime), while ZFS uses COW for all data, file contents and meta-data like the i-nodes. With atime ON on UFS you'll see a small number of writes on file-systems that are only read - we are used to accept that. On ZFS every update of atime causes a write of the meta-data to a free location on disk, then updates of all data structures that reference that meta-data up to the root of the tree (the uberblock). An update of a few bytes turns out to write tens of KB for each atime update (within the TXG sync interval, which defaults to 5 seconds on FreeBSD). If you create snapshots, then each snapshot will contain a copy of the metadata that was valid at the time of the snapshot (well, that's not so different from the situation with UFS snapshots, just that the data structures are much more complex and larger in the ZFS case). Due to the ease and speed of snapshot creation with ZFS there probably are a magnitude or more snapshots on a typical ZFS system than on one using UFS (I currently have a few hundred and have turned off periodic snapshot generation on many unimportant file-systems, already). I really hope that we get relatime (with minor variations that were discussed a few months ago) and that we make it the default in some future release ... Regards, STefan From owner-freebsd-fs@FreeBSD.ORG Fri Nov 15 18:59:21 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E4854AC for ; Fri, 15 Nov 2013 18:59:21 +0000 (UTC) Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0DC732E46 for ; Fri, 15 Nov 2013 18:59:20 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id m1so4424621oag.32 for ; Fri, 15 Nov 2013 10:59:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=ZuzZW4SDwQ3PqNXCglBynQduaLwXPm5e3Kdi3WdJxhI=; b=ftZKOp+nR7xMICUxBzhAT7h4+lDg7SghhE6p4abaVztWvmc5RKRPt3NE/xjLSNIT6/ L6tKzkwWOTNjE94FcYQZmSjnp1+4KKoGQUUx50/2LHUR/LwMRxb8yCtb5iD0pUDSM7AT QHSh1OS0oUaAljIUTOzbtNYvXBCe21xfzFDSQRMH3xPxZ11tJ0Wn+mR5UZpE9yG1lPe3 b1n7tYlLZ1kUS5QxDi2nhzZnqbiFP5Y+U1CtP8oO3GotZdPanOnR0V/f8Sx7aMRAcUcG AbUpq61am80J0zwHqq6xkVIxtvCrsBB5VEvBfdpalQPxjlu4QBlr109j8jpU4ptas4rr ou+g== X-Gm-Message-State: ALoCoQmr9uF5AENuJZBjpWbc7TEUgt2wetNL0Ay7HCReWNxxH6YATBZQmlvcFE9uyf19Li8YxINR MIME-Version: 1.0 X-Received: by 10.60.155.240 with SMTP id vz16mr1949893oeb.102.1384541954121; Fri, 15 Nov 2013 10:59:14 -0800 (PST) Received: by 10.60.165.40 with HTTP; Fri, 15 Nov 2013 10:59:13 -0800 (PST) X-Originating-IP: [217.15.27.35] Date: Fri, 15 Nov 2013 22:59:13 +0400 Message-ID: Subject: What is the way to determine owner of zfs jailed filesystem From: Oleg Ginzburg To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 18:59:21 -0000 Hi maillist, I've playing with zfs jail and could not find out what kind of jail have this or that FS For example: % jls -h jid name path jid name path 1 jail1 /usr/jails/jails/jail1 2 jail2 /usr/jails/jails/jail2 3 testempjail /usr/jails/jails/testempjail % zfs create zroot/j1fs % zfs set jailed=on zroot/j1fs % zfs jail jail2 zroot/j1fs % jexec 2 login -f root root@jail2:~ # zfs list NAME USED AVAIL REFER MOUNTPOINT zroot 39.5G 2.62T 31K none zroot/j1fs 31K 2.62T 31K none root@jail2:~ # zfs set mountpoint=/tmp/zfs zroot/j1fs root@jail2:~ # zfs mount -a root@jail2:~ # logout % zfs list NAME USED AVAIL REFER MOUNTPOINT zroot 39.5G 2.62T 31K none zroot/j1fs 51K 2.62T 51K /tmp/zfs zroot/root 37.4G 2.62T 36.2G / % zfs mount zroot/j1fs cannot mount 'zroot/j1fs': dataset is exported to a local zone On the master system i see that zroot/j1fs has a mount point /tmp/zfs (actually /tmp/zfs) However, documentation and zfs get does not answer how to find out that the owner of zroot/j1fs is jail2 (or jid 2) % zfs get all zroot/j1fs NAME PROPERTY VALUE SOURCE zroot/j1fs type filesystem - zroot/j1fs creation Fri Nov 15 22:41 2013 - zroot/j1fs used 51K - zroot/j1fs available 2.62T - zroot/j1fs referenced 51K - zroot/j1fs compressratio 1.00x - zroot/j1fs mounted yes - zroot/j1fs quota none default zroot/j1fs reservation none default zroot/j1fs recordsize 128K default zroot/j1fs mountpoint /tmp/zfs local zroot/j1fs sharenfs off default zroot/j1fs checksum on default zroot/j1fs compression off default zroot/j1fs atime on default zroot/j1fs devices on default zroot/j1fs exec on default zroot/j1fs setuid on default zroot/j1fs readonly off default zroot/j1fs jailed on local zroot/j1fs snapdir hidden default zroot/j1fs aclmode discard default zroot/j1fs aclinherit restricted default zroot/j1fs canmount on default zroot/j1fs xattr off temporary zroot/j1fs copies 1 default zroot/j1fs version 5 - zroot/j1fs utf8only off - zroot/j1fs normalization none - zroot/j1fs casesensitivity sensitive - zroot/j1fs vscan off default zroot/j1fs nbmand off default zroot/j1fs sharesmb off default zroot/j1fs refquota none default zroot/j1fs refreservation none default zroot/j1fs primarycache all default zroot/j1fs secondarycache all default zroot/j1fs usedbysnapshots 0 - zroot/j1fs usedbydataset 51K - zroot/j1fs usedbychildren 0 - zroot/j1fs usedbyrefreservation 0 - zroot/j1fs logbias latency default zroot/j1fs dedup off default zroot/j1fs mlslabel - zroot/j1fs sync standard default zroot/j1fs refcompressratio 1.00x - zroot/j1fs written 51K - zroot/j1fs logicalused 35.5K - zroot/j1fs logicalreferenced 35.5K - From owner-freebsd-fs@FreeBSD.ORG Fri Nov 15 23:58:06 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A7B5AE39 for ; Fri, 15 Nov 2013 23:58:06 +0000 (UTC) Received: from frv189.fwdcdn.com (frv189.fwdcdn.com [212.42.77.189]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6598E2D80 for ; Fri, 15 Nov 2013 23:58:05 +0000 (UTC) Received: from [10.10.1.30] (helo=frv196.fwdcdn.com) by frv189.fwdcdn.com with esmtp ID 1VhT0D-000NjI-IK for fs@freebsd.org; Sat, 16 Nov 2013 01:40:41 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-Id:To:Subject:From:Date; bh=6CWwsc8GWz2K6SX5Np5Zg3roZTUN6iqUlMv+IFHQZKI=; b=FFFO9EiyDIZMgBIWAIZnirksvknAGTr1osY8Fz1LE0hU2JKGLlT4vJwBIX1YKCK1KIYCGPzsb58GGup0kMNfXx9NCPJzyM+4JyJvu/JGbK9nJnvXBLXWwGjUsWwX2yG64EZNq0ELSYaCgwrwwL40+WSTDQKwWM7EHrNqtqczqro=; Received: from [10.10.10.35] (helo=frv35.ukr.net) by frv196.fwdcdn.com with smtp ID 1VhT01-0000Ta-7m for fs@freebsd.org; Sat, 16 Nov 2013 01:40:29 +0200 Date: Sat, 16 Nov 2013 01:40:28 +0200 From: Vladislav Prodan Subject: [ZFS] cannot detach /dev/gpt/system-disk-60: no valid replicas To: fs@freebsd.org X-Mailer: mail.ukr.net 5.0 Message-Id: <1384558482.622649210.1mfnhjop@frv35.ukr.net> MIME-Version: 1.0 Received: from universite@ukr.net by frv35.ukr.net; Sat, 16 Nov 2013 01:40:29 +0200 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 23:58:06 -0000 root@mfsbsd:~ # zpool status pool: tank state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: resilvered 48.8G in 7h19m with 3 errors on Fri Nov 15 18:43:18 2013 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/system-disk-60 ONLINE 0 0 0 gpt/disk-90 ONLINE 0 0 0 errors: 3 data errors, use '-v' for a list root@mfsbsd:~ # zpool detach tank /dev/gpt/system-disk-60 cannot detach /dev/gpt/system-disk-60: no valid replicas Checking zfs scrub has given nothing. How do I remove the disk gpt/system-disk-60 from the pool zpool without destroying it? -- Vladislav V. Prodan System & Network Administrator http://support.od.ua +380 67 4584408, +380 99 4060508 VVP88-RIPE From owner-freebsd-fs@FreeBSD.ORG Sat Nov 16 00:31:07 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B97C43B1 for ; Sat, 16 Nov 2013 00:31:07 +0000 (UTC) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5BC862F70 for ; Sat, 16 Nov 2013 00:31:07 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50006733269.msg for ; Sat, 16 Nov 2013 00:30:58 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 16 Nov 2013 00:30:58 +0000 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1032b0b9a9=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: fs@freebsd.org Message-ID: <89876A0EAB2247FCB1875DFDE28E2799@multiplay.co.uk> From: "Steven Hartland" To: "Vladislav Prodan" , References: <1384558482.622649210.1mfnhjop@frv35.ukr.net> Subject: Re: [ZFS] cannot detach /dev/gpt/system-disk-60: no valid replicas Date: Sat, 16 Nov 2013 00:30:57 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Nov 2013 00:31:07 -0000 Run zpool status -v and either remove or restore the files indicated to have an issue. Once this is done my may well have more luck removing the device. Regards Steve ----- Original Message ----- From: "Vladislav Prodan" To: Sent: Friday, November 15, 2013 11:40 PM Subject: [ZFS] cannot detach /dev/gpt/system-disk-60: no valid replicas > root@mfsbsd:~ # zpool status > pool: tank > state: ONLINE > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: http://illumos.org/msg/ZFS-8000-8A > scan: resilvered 48.8G in 7h19m with 3 errors on Fri Nov 15 18:43:18 2013 > config: > > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > gpt/system-disk-60 ONLINE 0 0 0 > gpt/disk-90 ONLINE 0 0 0 > > errors: 3 data errors, use '-v' for a list > root@mfsbsd:~ # zpool detach tank /dev/gpt/system-disk-60 > cannot detach /dev/gpt/system-disk-60: no valid replicas > > > Checking zfs scrub has given nothing. > How do I remove the disk gpt/system-disk-60 from the pool zpool without destroying it? > > -- > Vladislav V. Prodan > System & Network Administrator > http://support.od.ua > +380 67 4584408, +380 99 4060508 > VVP88-RIPE > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Sat Nov 16 02:56:21 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A0A7DB8; Sat, 16 Nov 2013 02:56:21 +0000 (UTC) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E47925FE; Sat, 16 Nov 2013 02:56:21 +0000 (UTC) Received: by mail-pa0-f50.google.com with SMTP id kp14so2814214pab.9 for ; Fri, 15 Nov 2013 18:56:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type :thread-index; bh=piMkAEWDSr3k6QkACvuO1D4+jM55vnU/nBArjnWTKsU=; b=XssvStcoSeInI1Or1c5qUdKUj0tZnmon9Kw9tosAFhXt1GziNnsncSfQ2m/CPl46j7 DveeL2/oVFygfQv6YVfmm1TwCO9g0GH6CMqTAlVKB4v6HhVZHHAicENXvC/H0s0UXl22 L/tRAcwbiBWQbY5tSAbAenZ8e3OE2O7qCq1zHrXeFjxO7GIm1rNMJ9D2CnLmgo7jjhbt TgkVONwQLTb5DgCH6myhvyV39PLW/gxdNGqwHlQzmGm1ySZmcsbsshXw1zctZU9glLhg oP6mNbUhmjjdHx33O9yNIjnmvdS9U079B5Os2UMduRZsz3fv0FFXSA3cZLomjxbDCziJ dA9w== X-Received: by 10.66.190.10 with SMTP id gm10mr9748618pac.126.1384570580616; Fri, 15 Nov 2013 18:56:20 -0800 (PST) Received: from d40 (34.sub-70-197-84.myvzw.com. [70.197.84.34]) by mx.google.com with ESMTPSA id og5sm7668227pbb.10.2013.11.15.18.56.17 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 15 Nov 2013 18:56:19 -0800 (PST) From: "John Refling" To: , Subject: rare, random issue with read(), mmap() failing to read entire file Date: Fri, 15 Nov 2013 18:56:09 -0800 Message-ID: <9CB46A22C0BE40029652144B2586462A@d40> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Ac7id2bOvS8Nq/MiRSaxrAx6DDPDxQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Nov 2013 02:56:21 -0000 I'm having some very insidious issues with copying and verifying (identical) data from several hard disks. This might be a hardware issue or something very deep in the disk / filesystem code. I have verified this with several disks and motherboards. It corrupts 0.0096% of my files, different files each time! Background: 1. I have a 500 GB USB hard disk (the new 4,096 [4k] sector size) which I have been using to store a master archive of over 70,000 files. 2. To make a backup of the USB disk, I copied everything over to a 500 GB SATA hard disk. [Various combinations of `cp -r', `scp -r', `tar -cf - . | rsh ... tar -xf -', etc.] 3. To verify that the copy was correct, I did sha256 sums of all files on both disks. 4. When comparing the sha256 sums on both drives, I discovered that 6 or so files did not compare OK from one drive to the other. 5. When I checked the files individually, the files compared OK, and even when I recomputed their individual sha256 sums, I got DIFFERENT sha256 sums which were correct this time! The above lead me to investigate further, and using ONLY the USB disk, I recomputed the sha256 sums for all files ON THAT DISK. A small number (6-12) of files ON THE SAME DISK had different sha256 sums than previously computed! The disk is read-only so nothing could have changed. To try to get to the bottom of this, I took the sha256 code and put it in my own file reading routine, which reads-in data from the file using read(). On summing up the total bytes read in the read() loop, I discovered that on the files that failed to compare, the read() returned EOF before the actual EOF. According to the manual page this is impossible. I compared the total number of bytes read by the read() loop to the stat() file length value, and they were different! Obviously, the sha256 sum will be different since not all the file is read. This happens consistently on 6 to 12 files out of 70,000+ *every* time, and on DIFFERENT files *every* time. So things work 99.9904% of the time. But something fails 0.0096% (one hundredth of one percent) of the time, which with a large number of files is significant! Instead of read(), I tried mmap()ing chunks of the file. Using mmap() to access the data in the file instead of read() resulted in a (different) sha256 sum than the read() version! The mmap() version was correct, except in ONE case where BOTH versions were WRONG, when compared to a 3rd and 4th run! Using `diff -rq disk1 disk2` resulted in similar issues. There were always a few files that failed to compare. Doing another `diff -rq disk1 disk2` resulted in a few *other* files that failed to compare, while the ones that didn't compare OK the first time, DID compare OK the second time. This happened to 6-12 files out of 70,000+. Whatever is affecting my use of read() in my sha256 routine seems to also affect system utilities such as diff! This gets really insidious because I don't know if the original `cp -r disk1 disk2` did these short reads on a few files while copying the files, thus corrupting my archive backup (on 6-12 files)! Some of the files that fail are small (10KB) and some are huge (8GB). HELP! It takes 7 hours to recompute the sha256 sums of the files on the disk so random experiments are time consuming, but I'm willing to try things that are suggested. System details: This is observed with the following disks: Western Digital 500GB SATA 512 byte sectors Hitachi 500GB SATA 512 byte sectors Iomega RPHD-UG3 500GB USB 4096 byte sectors in combination with these motherboards: P4M800Pro-M V2.0: Pentium D 2.66 GHz, 2GB memory HP/Compaq Evo: Pentium 4, 2.8 GHz, 2GB memory OP System version: Freebsd: 9.1 RELEASE #0 no hardware errors noted in /var/log/messages during the file reading did Spinrite on disks to freshen (re-read/write) all sectors, with no errors. The file systems were built using: dd if=/dev/zero of=/dev/xxx bs=2m newfs -m0 /dev/xxx Looked through the mailing lists and bug reports but can't see anything similar. Thanks for your help, John Refling From owner-freebsd-fs@FreeBSD.ORG Sat Nov 16 09:40:10 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1EA66CF8 for ; Sat, 16 Nov 2013 09:40:10 +0000 (UTC) Received: from frv191.fwdcdn.com (frv191.fwdcdn.com [212.42.77.191]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D03872740 for ; Sat, 16 Nov 2013 09:40:09 +0000 (UTC) Received: from [10.10.1.23] (helo=frv199.fwdcdn.com) by frv191.fwdcdn.com with esmtp ID 1Vhc64-0002CY-M6 for fs@freebsd.org; Sat, 16 Nov 2013 11:23:20 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-Id:Cc:To:Subject:From:Date; bh=1+pbcf4NTqz0w6HkJesV/q3InlCXvr7kcZwu8JQ3UEQ=; b=epN3Yql4UW6Apl1HjlGv2oChG3r6qGE+ibYSfnPSnNihZRH/X74/tN6DCKNZKddaiFgyyzTI3kogCo1ssGmTrB8ObJJi34NvWq8LMzWj8mt0qHfPFL8O2T7Bg43QUubn7EuwP9pw4b8KSzm6y1+RI6eoY2SAlu093RbdQK1nKbs=; Received: from [10.10.10.35] (helo=frv35.ukr.net) by frv199.fwdcdn.com with smtp ID 1Vhc5v-00029A-RG for fs@freebsd.org; Sat, 16 Nov 2013 11:23:11 +0200 Date: Sat, 16 Nov 2013 11:23:11 +0200 From: Vladislav Prodan Subject: Re[2]: [ZFS] cannot detach /dev/gpt/system-disk-60: no valid replicas To: Steven Hartland X-Mailer: mail.ukr.net 5.0 Message-Id: <1384593787.502641084.f8mcbhve@frv35.ukr.net> In-Reply-To: <89876A0EAB2247FCB1875DFDE28E2799@multiplay.co.uk> References: <1384558482.622649210.1mfnhjop@frv35.ukr.net> <89876A0EAB2247FCB1875DFDE28E2799@multiplay.co.uk> MIME-Version: 1.0 Received: from universite@ukr.net by frv35.ukr.net; Sat, 16 Nov 2013 11:23:11 +0200 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline Cc: fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Nov 2013 09:40:10 -0000 > Run zpool status -v and either remove or restore the files > indicated to have an issue. > > Once this is done my may well have more luck removing the device. > > Regards > Steve > After removal of snapshots: root@mfsbsd:~ # zpool status -v pool: tank state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Sat Nov 16 00:53:04 2013 44.1G scanned out of 51.8G at 1.48M/s, 1h28m to go 44.1G resilvered, 85.11% done config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 3 replacing-0 ONLINE 0 0 6 gpt/system-disk-60 ONLINE 0 0 6 gpt/disk-90 ONLINE 0 0 6 (resilvering) errors: Permanent errors have been detected in the following files: <0x1618>:<0x9b83> <0x1618>:<0x12c87> <0x161a>:<0x3170> -- Vladislav V. Prodan System & Network Administrator http://support.od.ua +380 67 4584408, +380 99 4060508 VVP88-RIPE From owner-freebsd-fs@FreeBSD.ORG Sat Nov 16 10:33:13 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03F2A127 for ; Sat, 16 Nov 2013 10:33:13 +0000 (UTC) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B4752951 for ; Sat, 16 Nov 2013 10:33:12 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id rAGAUsjo054770; Sat, 16 Nov 2013 14:30:54 +0400 (MSK) (envelope-from marck@rinet.ru) Date: Sat, 16 Nov 2013 14:30:54 +0400 (MSK) From: Dmitry Morozovsky To: Vladislav Prodan Subject: Re[2]: [ZFS] cannot detach /dev/gpt/system-disk-60: no valid replicas In-Reply-To: <1384593787.502641084.f8mcbhve@frv35.ukr.net> Message-ID: References: <1384558482.622649210.1mfnhjop@frv35.ukr.net> <89876A0EAB2247FCB1875DFDE28E2799@multiplay.co.uk> <1384593787.502641084.f8mcbhve@frv35.ukr.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Sat, 16 Nov 2013 14:30:54 +0400 (MSK) Cc: fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Nov 2013 10:33:13 -0000 On Sat, 16 Nov 2013, Vladislav Prodan wrote: > > Run zpool status -v and either remove or restore the files > > indicated to have an issue. > > > > Once this is done my may well have more luck removing the device. > > > > Regards > > Steve > > > After removal of snapshots: > > root@mfsbsd:~ # zpool status -v > pool: tank > state: ONLINE > status: One or more devices is currently being resilvered. The pool will > continue to function, possibly in a degraded state. > action: Wait for the resilver to complete. your current action is described here ;) After resilver sinish, issue 'zpool clear', then I suppose you will be able to detach system-disk-60 > scan: resilver in progress since Sat Nov 16 00:53:04 2013 > 44.1G scanned out of 51.8G at 1.48M/s, 1h28m to go > 44.1G resilvered, 85.11% done > config: > > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 3 > replacing-0 ONLINE 0 0 6 > gpt/system-disk-60 ONLINE 0 0 6 > gpt/disk-90 ONLINE 0 0 6 (resilvering) > > errors: Permanent errors have been detected in the following files: > > <0x1618>:<0x9b83> > <0x1618>:<0x12c87> > <0x161a>:<0x3170> > > > > -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------