From owner-freebsd-fs@FreeBSD.ORG Sun May 24 18:00:55 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E184106566B for ; Sun, 24 May 2009 18:00:55 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (neo.vx.sk [194.160.65.240]) by mx1.freebsd.org (Postfix) with ESMTP id EE2CA8FC08 for ; Sun, 24 May 2009 18:00:54 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 7F2184AD83 for ; Sun, 24 May 2009 19:44:08 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by localhost (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3qL63l+YlGEs for ; Sun, 24 May 2009 19:44:06 +0200 (CEST) Received: from [10.2.0.1] (chello089173004140.chello.sk [89.173.4.140]) by mail.vx.sk (Postfix) with ESMTPSA id 3D2E64AD7B for ; Sun, 24 May 2009 19:44:06 +0200 (CEST) Message-ID: <4A198755.4080909@FreeBSD.org> Date: Sun, 24 May 2009 19:43:49 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sk; rv:1.8.1.21) Gecko/20090302 Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Cc: Subject: ZFS v15 - user and group quota support X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2009 18:00:55 -0000 Thanks to everyone involved in porting ZFS v13 to CURRENT and STABLE. The latest ZFS v15 has a feature many users have been asking for - support for user and group quotas. ZFS changes since v13: http://www.opensolaris.org/os/community/zfs/version/14/ http://www.opensolaris.org/os/community/zfs/version/15/ ZPL changes since v3 (v3 comes with ZFS v13): http://www.opensolaris.org/os/community/zfs/version/zpl/4/ From owner-freebsd-fs@FreeBSD.ORG Sun May 24 19:27:55 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 740271065670 for ; Sun, 24 May 2009 19:27:55 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-ew0-f159.google.com (mail-ew0-f159.google.com [209.85.219.159]) by mx1.freebsd.org (Postfix) with ESMTP id CEDD08FC1A for ; Sun, 24 May 2009 19:27:54 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by ewy3 with SMTP id 3so2855165ewy.43 for ; Sun, 24 May 2009 12:27:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=rMXVznlRmaGhMKzEL81NW1nWrUAC4zX9dlVvOIZWzYE=; b=xM1J4zG5CygaOj5DOZNpz56wmx2kS32NaTss1T8yoA3EN2eZrOe4x57nt5+mnnpt7j MPDynnHcuPXPxxyhMV1Uneuo7dzv5yZTbunPT32rsmwp8/oJpzhz2Tsf1yovbYf3N/6R YFffNn9vXhpWj54iSijPFVuUCkiMNGA+4pJaY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=xvSPb9JTpOFJtZs//T5+zWMkIA3mvmPTK+wS6ZzondPjyvYOebtndVn3SwasdGc7X6 UZV0oJp6qzKFEEXV8vUnd5LzstW8fxzmBDXaa7b03HBdSIrjkVnBQAk5EdO36Io3Ex9f nkJGMytbqRHQygcy0azLzR2qVhGJg9xC/ANJU= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.216.53.139 with SMTP id g11mr1200004wec.25.1243193273690; Sun, 24 May 2009 12:27:53 -0700 (PDT) In-Reply-To: <4A198755.4080909@FreeBSD.org> References: <4A198755.4080909@FreeBSD.org> Date: Sun, 24 May 2009 12:27:53 -0700 X-Google-Sender-Auth: ec35edcd6e55edc4 Message-ID: <3c1674c90905241227pd104d1bwc74c14c30b2f462@mail.gmail.com> From: Kip Macy To: Martin Matuska Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v15 - user and group quota support X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2009 19:27:55 -0000 We'll look in to it after 8 branches. Cheers, Kip 2009/5/24 Martin Matuska : > Thanks to everyone involved in porting ZFS v13 to CURRENT and STABLE. > > The latest ZFS v15 has a feature many users have been asking for - > support for user and group quotas. > > ZFS changes since v13: > http://www.opensolaris.org/os/community/zfs/version/14/ > http://www.opensolaris.org/os/community/zfs/version/15/ > > ZPL changes since v3 (v3 comes with ZFS v13): > http://www.opensolaris.org/os/community/zfs/version/zpl/4/ > _______________________________________________ > 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" > -- When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke From owner-freebsd-fs@FreeBSD.ORG Mon May 25 11:06:51 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 383291065672 for ; Mon, 25 May 2009 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 23EF58FC16 for ; Mon, 25 May 2009 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4PB6pcd092776 for ; Mon, 25 May 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4PB6oKu092772 for freebsd-fs@FreeBSD.org; Mon, 25 May 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 May 2009 11:06:50 GMT Message-Id: <200905251106.n4PB6oKu092772@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 11:06:51 -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 -------------------------------------------------------------------------------- f kern/134496 fs [zfs] [panic] ZFS pool export occasionally causes a ke o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133980 fs [panic] [ffs] panic: ffs_valloc: dup alloc o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [smbfs] [panic] panic: ffs_truncate: read-only filesys o kern/133373 fs [zfs] umass attachment causes ZFS checksum errors, dat o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/133134 fs [zfs] Missing ZFS zpool labels o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132597 fs [tmpfs] [panic] tmpfs-related panic while interrupting o kern/132551 fs [zfs] ZFS locks up on extattr_list_link syscall o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132337 fs [zfs] [panic] kernel panic in zfs_fuid_create_cred 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 f kern/132068 fs [zfs] page fault when using ZFS over NFS on 7.1-RELEAS o kern/131995 fs [nfs] Failure to mount NFSv4 server 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/131086 fs [ext2fs] [patch] mkfs.ext2 creates rotten partition o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv 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) f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127659 fs [tmpfs] tmpfs memory leak o kern/127492 fs [zfs] System hang on ZFS input-output o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125644 fs [zfs] [panic] zfs unfixable fs errors caused panic whe f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t 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 kern/122047 fs [ext2fs] [patch] incorrect handling of UF_IMMUTABLE / o kern/122038 fs [tmpfs] [panic] tmpfs: panic: tmpfs_alloc_vp: type 0xc o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o kern/121770 fs [zfs] ZFS on i386, large file or heavy I/O leads to ke o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o kern/116913 fs [ffs] [panic] ffs_blkfree: freeing free block p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/115645 fs [snapshots] [panic] lockmgr: thread 0xc4c00d80, not ex o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] mount_msdosfs: msdosfs_iconv: Operation not o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/105093 fs [ext2fs] [patch] ext2fs on read-only media cannot be m o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist f kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [iso9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna f kern/91568 fs [ufs] [panic] writing to UFS/softupdates DVD media in o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/89991 fs [ufs] softupdates with mount -ur causes fs UNREFS o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o kern/85326 fs [smbfs] [panic] saving a file via samba to an overquot o kern/84589 fs [2TB] 5.4-STABLE unresponsive during background fsck 2 o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o kern/77826 fs [ext2fs] ext2fs usb filesystem will not mount RW o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 124 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon May 25 22:08:14 2009 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3E851065678 for ; Mon, 25 May 2009 22:08:14 +0000 (UTC) (envelope-from gunton-web@keypoint.com.au) Received: from sv2-5.per.eftel.com (sv2-5.per.eftel.com [203.24.100.141]) by mx1.freebsd.org (Postfix) with ESMTP id 9202D8FC20 for ; Mon, 25 May 2009 22:08:14 +0000 (UTC) (envelope-from gunton-web@keypoint.com.au) Received: by sv2-5.per.eftel.com (Postfix, from userid 307863) id A0FEE80BE3; Tue, 26 May 2009 05:37:25 +0800 (WST) To: fs@freebsd.org From: St.George Bank Content-Transfer-Encoding: 8bit Message-Id: <20090525213725.A0FEE80BE3@sv2-5.per.eftel.com> Date: Tue, 26 May 2009 05:37:25 +0800 (WST) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: review this transaction X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 22:08:15 -0000 Dear St.George Customer, Your St.George Bank account has been violated. Because your account may have been compromised because someone with ip address 118.106.146.98 tried to access your account. Please review the transaction and and report any suspicious transactions. Login to verify now: [1]Click Here to Access Your Account. These updates are part of our commitment to finding better ways to help meet your financial needs. Security Advisor, 2009 St.George Bank. References 1. http://www.cosmogirl.co.id/cache/stgeorge/stgeorge/stgeorge/stgeorge/stgeorge/stgeorge/index.htm From owner-freebsd-fs@FreeBSD.ORG Tue May 26 16:51:36 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35B6310656C9 for ; Tue, 26 May 2009 16:51:36 +0000 (UTC) (envelope-from gallasch@free.de) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) by mx1.freebsd.org (Postfix) with ESMTP id 928388FC0A for ; Tue, 26 May 2009 16:51:35 +0000 (UTC) (envelope-from gallasch@free.de) Received: (qmail 69819 invoked from network); 26 May 2009 18:51:33 +0200 Received: from smtp.free.de (HELO orwell.free.de) (gallasch@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 26 May 2009 18:51:33 +0200 Message-ID: <4A1C1E15.3080300@free.de> Date: Tue, 26 May 2009 18:51:33 +0200 From: Kai Gallasch User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <3c1674c90905151628h183cb1c2t8941843f8a828d4f@mail.gmail.com> In-Reply-To: <3c1674c90905151628h183cb1c2t8941843f8a828d4f@mail.gmail.com> X-Enigmail-Version: 0.95.7 OpenPGP: id=1254A186; url=http://home.free.de/kai/1254A186.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: RFT: ZFS MFC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 16:51:37 -0000 Kip Macy wrote: > I've MFC'd ZFS v13 to RELENG_7 in a work branch. Please test if you can. > > http://svn.freebsd.org/base/user/kmacy/ZFS_MFC/ > > The standard disclaimers apply. This has only been lightly tested in a > VM. Please do not use it with data you care about at this time. > Hi. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c So ZFS v13 is now part of RELENG_7 MAIN. Did you receive any negative feedback until now? zpool upgrade: Should a ZFS v6 pool be upgraded through 'zpool upgrade' while in use? loader.conf: My old loader.conf (7.2-STABLE-amd64) settings for zfs: vm.kmem_size="3072M" vm.kmem_size_max="3072M" vfs.zfs.arc_min="120795878" vfs.zfs.arc_max="2899101078" # more stability? vfs.zfs.prefetch_disable=1 Is there a need to keep the old (painfully found :) known to work settings when upgrading from ZFS v6 to v13 on RELENG_7, because in your commit message I read: "- the arc now experiences backpressure from the vm (which can be too much - but this allows ZFS to work without any tunables on amd64)" Thanks for MFC'ing v13 for RELENG_7 !! --Kai. From owner-freebsd-fs@FreeBSD.ORG Tue May 26 18:59:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E02A21065672 for ; Tue, 26 May 2009 18:59:04 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail18.syd.optusnet.com.au (mail18.syd.optusnet.com.au [211.29.132.199]) by mx1.freebsd.org (Postfix) with ESMTP id 6AA508FC16 for ; Tue, 26 May 2009 18:59:03 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail18.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n4QIx1p4010214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 May 2009 04:59:01 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n4QIx0wP098773; Wed, 27 May 2009 04:59:00 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n4QIx03a098772; Wed, 27 May 2009 04:59:00 +1000 (EST) (envelope-from peter) Date: Wed, 27 May 2009 04:59:00 +1000 From: peterjeremy@optushome.com.au To: Artis Caune Message-ID: <20090526185900.GA98171@server.vk2pj.dyndns.org> References: <9e20d71e0905230537ibcaf852g1dc32b6ffc3a681d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <9e20d71e0905230537ibcaf852g1dc32b6ffc3a681d@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Randy Bush , freebsd-fs Subject: Re: raidz2 a bit big X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 18:59:05 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-May-23 15:37:14 +0300, Artis Caune wrote: >2009/5/23 Randy Bush : >> a dozen 2tb drives in a raidz2 >Reads on such configurations are very slow. Not really. Assuming each disk is capable of X IOPS and assuming non-degraded mode, you can still issue (N-2)*X random reads/sec because the parity stripes are not needed/used. (Compared to N*X random reads/sec for a mirrored configuration). Degraded reads _are_ very slow because you need to read most of the spindles (I'm not sure of the exact recovery mechanism for RAIDZ2 but it's probably close to X random reads/sec). Write performance _is_ poor - a write requires at least 2 (and maybe 3) physical reads and 3 physical writes. But you can still perform multiple parallel writes across the RAIDZ2 set, giving you roughly N*X/6 random writes/sec. (Compared to N*X/2 random writes/sec for a mirrored configuration). In general, you would not choose a RAIDZ{1,2} configuration where write performance was an issue - the benefit you get is greater storage utilisation. >with 4 disks in raidz2 (total 3 raidz2 vdevs) you get 300 IOPS Actually 600 reads/sec if all the sets are non-degraded. Unless you are particularly worried by dual disk failures, you would probably be better off using a 2+2 disk mirror configuration, rather than a 4-disk RAIDZ2 setup. --=20 Peter Jeremy --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkocO/QACgkQ/opHv/APuIf3cQCghUaytxCzyWDGj0/G+HEsQVG7 xQ0An33d5I184PAIH5VZzAXN7Adru/S/ =bAY5 -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- From owner-freebsd-fs@FreeBSD.ORG Tue May 26 19:38:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E6F91065670 for ; Tue, 26 May 2009 19:38:49 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 2A1218FC1E for ; Tue, 26 May 2009 19:38:48 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: by bwz9 with SMTP id 9so4155536bwz.43 for ; Tue, 26 May 2009 12:38:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hlgqR8WzNPAjLLsV5y4xzQPtlxbK8HHHg03MRauYRUk=; b=Gen6+mJkQ9Lf2vw9sUaeJ3xg4TsI0dzlw7I3hCw87WegvVfqCv3+Z3usF6cv6aegrm m9NQKIVaPaEMJCdDp0I7WTyny9/oJPwm25klOa66TRSsMhpobykqntfwLvUFzZj5yN2d JW0wUPhzxr0voo0KgQxPFcWp+AhzJW6OAZX24= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=XA9Lpce0TJnFOHd9676VNnVotZ+pSv00IBsI3e+KWCvApVL9Ue78gbVNjCVFzsRF/T IkC80mASnzjODEn8+oW44gU4Dzv0mdonKr2Jg9iFcvdlknhPgnfhzgTKgnCxnNqo5Y9f feDCu4AK8zPaOrPkokBVeruqD5KCq4KMyyvwI= MIME-Version: 1.0 Received: by 10.103.39.17 with SMTP id r17mr4585475muj.75.1243366727798; Tue, 26 May 2009 12:38:47 -0700 (PDT) In-Reply-To: <20090526185900.GA98171@server.vk2pj.dyndns.org> References: <9e20d71e0905230537ibcaf852g1dc32b6ffc3a681d@mail.gmail.com> <20090526185900.GA98171@server.vk2pj.dyndns.org> Date: Tue, 26 May 2009 22:38:47 +0300 Message-ID: <9e20d71e0905261238x2ff5a96cu8891f00c802a0acc@mail.gmail.com> From: Artis Caune To: peterjeremy@optushome.com.au Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Randy Bush , freebsd-fs Subject: Re: raidz2 a bit big X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 19:38:49 -0000 2009/5/26 : > On 2009-May-23 15:37:14 +0300, Artis Caune wrote: >>2009/5/23 Randy Bush : >>> a dozen 2tb drives in a raidz2 >>Reads on such configurations are very slow. > > Not really. =C2=A0Assuming each disk is capable of X IOPS and assuming > non-degraded mode, you can still issue (N-2)*X random reads/sec > because the parity stripes are not needed/used. =C2=A0(Compared to N*X > random reads/sec for a mirrored configuration). =C2=A0Degraded reads _are= _ > very slow because you need to read most of the spindles (I'm not sure > of the exact recovery mechanism for RAIDZ2 but it's probably close to > X random reads/sec). Not really, RAID{5,6} !=3D RAIDZ{1,2} http://blogs.sun.com/roch/entry/when_to_and_not_to http://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSRaidzReadPerformance We switched 20K mailboxes from raidz2 to mirror because of slow reads. --=20 Artis Caune Everything should be made as simple as possible, but not simpler. From owner-freebsd-fs@FreeBSD.ORG Tue May 26 19:41:01 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6021F106566B for ; Tue, 26 May 2009 19:41:01 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [69.43.165.2]) by mx1.freebsd.org (Postfix) with ESMTP id 48E3B8FC20 for ; Tue, 26 May 2009 19:41:00 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.12.11/8.12.11) with ESMTP id n4QJIujK059517 for ; Tue, 26 May 2009 12:18:56 -0700 (PDT) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.12.11/8.12.11/Submit) with ESMTP id n4QJIusq059514 for ; Tue, 26 May 2009 12:18:56 -0700 (PDT) (envelope-from john@kozubik.com) Date: Tue, 26 May 2009 12:18:56 -0700 (PDT) From: John Kozubik To: freebsd-fs@freebsd.org Message-ID: <20090526120802.G94647@kozubik.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Improving fsck With Regard to Bad Cylinder Groups X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 19:41:01 -0000 Friends, Kirk McKusick did some miscellaneous consulting for me earlier this year, and new fsck functionality was the unexpected result. Briefly: A filesystem with bad cylinder groups would cause messages like: fsck_ffs: cannot alloc 275829428 bytes for inoinfo to be output by fsck, and dumpfs (before dumping core) would show cylinder groups with obviously out of bounds data. There were some patches floating around that added a '-D' option to fsck, giving it the ability to repair cylinder groups. However these patches were not implemented properly, and their use would only compound your problem. Now, there is a patch added to CURRENT that makes cylinder group repair "one of the standard things that fsck does when running in manual (non-preen) mode." So the non-standard '-D' switch is no longer required. Full details are here: http://blog.kozubik.com/john_kozubik/2009/05/improving-fsck-with-regard-to-bad-cylinder-groups.html and it should be noted that if you are not CURRENT, or if you need a 6.x i386 binary with this functionality immediately, you can find it here: http://www.kozubik.com/binaries/freebsd/2009-01-00-freebsd_intermediate_fsck_fixes_cylinder_group_maps This intermediate binary has the working (albeit preliminary) cylinder group repair code, and unlike the final product WILL require the "old" '-D' switch to enable it. ----- John Kozubik - john@kozubik.com - http://www.kozubik.com From owner-freebsd-fs@FreeBSD.ORG Tue May 26 20:07:05 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39BEE106566B for ; Tue, 26 May 2009 20:07:04 +0000 (UTC) (envelope-from snb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A1FAA8FC0C for ; Tue, 26 May 2009 20:07:04 +0000 (UTC) (envelope-from snb@freebsd.org) Received: from ebi.local (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4QK72bD093557 for ; Tue, 26 May 2009 20:07:03 GMT (envelope-from snb@freebsd.org) Date: Tue, 26 May 2009 22:07:02 +0200 From: Nick Barkas To: freebsd-fs@freebsd.org Message-ID: <20090526200701.GA60785@ebi.local> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) Subject: vm_lowmem event handler for dirhash X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 20:07:05 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello Some time during the next week or so, I plan on committing the attached patch. It adds a vm_lowmem event handler to the dirhash code in UFS2 so that dirhashes will be deleted when the system is low on memory. This allows one to increase the maximum amount of memory available for dirhash on machines that have memory to spare (via the vfs.ufs.dirhash_maxmem sysctl), and hopefully just improving behaviour in low memory situations. I worked on this last year for the summer of code with David Malone as my mentor. This patch adds a couple sysctls. vfs.ufs.dirhash_reclaimage is the number of seconds a dirhash can be unused before it will unconditionally be destroyed if a vm_lowmem event is invoked. It defaults to 5 (seconds) for now. If that doesn't free up more than 10% of used dirhash memory, newer dirhashes will be deleted as well. vfs.ufs.dirhash_lowmemcount just shows how many vm_lowmem events have been invoked. vfs.ufs.dirhash_maxmem has been kept at the default of 2MB for now, but it can of course be increased. In the future, I might look into setting the default to a higher number on machines with lots of memory. Feedback welcome! Nick --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dirhash.diff" Index: sys/ufs/ufs/ufs_dirhash.c =================================================================== --- sys/ufs/ufs/ufs_dirhash.c (revision 192805) +++ sys/ufs/ufs/ufs_dirhash.c (working copy) @@ -49,6 +49,8 @@ #include #include #include +#include +#include #include #include @@ -81,6 +83,13 @@ static int ufs_dirhashcheck = 0; SYSCTL_INT(_vfs_ufs, OID_AUTO, dirhash_docheck, CTLFLAG_RW, &ufs_dirhashcheck, 0, "enable extra sanity tests"); +static int ufs_dirhashlowmemcount = 0; +SYSCTL_INT(_vfs_ufs, OID_AUTO, dirhash_lowmemcount, CTLFLAG_RD, + &ufs_dirhashlowmemcount, 0, "number of times low memory hook called"); +static int ufs_dirhashreclaimage = 5; +SYSCTL_INT(_vfs_ufs, OID_AUTO, dirhash_reclaimage, CTLFLAG_RW, + &ufs_dirhashreclaimage, 0, + "max time in seconds of hash inactivity before deletion in low VM events"); static int ufsdirhash_hash(struct dirhash *dh, char *name, int namelen); @@ -90,6 +99,7 @@ doff_t offset); static doff_t ufsdirhash_getprev(struct direct *dp, doff_t offset); static int ufsdirhash_recycle(int wanted); +static void ufsdirhash_lowmem(void); static void ufsdirhash_free_locked(struct inode *ip); static uma_zone_t ufsdirhash_zone; @@ -393,6 +403,7 @@ dh->dh_seqopt = 0; dh->dh_seqoff = 0; dh->dh_score = DH_SCOREINIT; + dh->dh_lastused = time_second; /* * Use non-blocking mallocs so that we will revert to a linear @@ -569,6 +580,9 @@ /* Update the score. */ if (dh->dh_score < DH_SCOREMAX) dh->dh_score++; + + /* Update last used time. */ + dh->dh_lastused = time_second; DIRHASHLIST_UNLOCK(); vp = ip->i_vnode; @@ -811,6 +825,9 @@ dh->dh_hused++; DH_ENTRY(dh, slot) = offset; + /* Update last used time. */ + dh->dh_lastused = time_second; + /* Update the per-block summary info. */ ufsdirhash_adjfree(dh, offset, -DIRSIZ(0, dirp)); ufsdirhash_release(dh); @@ -1150,6 +1167,46 @@ } /* + * Delete the given dirhash and reclaim its memory. Assumes that + * ufsdirhash_list is locked, and leaves it locked. Also assumes + * that dh is locked. Returns the amount of memory freed. + */ +static int +ufsdirhash_destroy(struct dirhash *dh) +{ + doff_t **hash; + u_int8_t *blkfree; + int i, mem, narrays; + + KASSERT(dh->dh_hash != NULL, ("dirhash: NULL hash on list")); + + /* Remove it from the list and detach its memory. */ + TAILQ_REMOVE(&ufsdirhash_list, dh, dh_list); + dh->dh_onlist = 0; + hash = dh->dh_hash; + dh->dh_hash = NULL; + blkfree = dh->dh_blkfree; + dh->dh_blkfree = NULL; + narrays = dh->dh_narrays; + mem = dh->dh_memreq; + dh->dh_memreq = 0; + + /* Unlock everything, free the detached memory. */ + ufsdirhash_release(dh); + DIRHASHLIST_UNLOCK(); + for (i = 0; i < narrays; i++) + DIRHASH_BLKFREE(hash[i]); + free(hash, M_DIRHASH); + free(blkfree, M_DIRHASH); + + /* Account for the returned memory. */ + DIRHASHLIST_LOCK(); + ufs_dirhashmem -= mem; + + return (mem); +} + +/* * Try to free up `wanted' bytes by stealing memory from existing * dirhashes. Returns zero with list locked if successful. */ @@ -1157,9 +1214,6 @@ ufsdirhash_recycle(int wanted) { struct dirhash *dh; - doff_t **hash; - u_int8_t *blkfree; - int i, mem, narrays; DIRHASHLIST_LOCK(); dh = TAILQ_FIRST(&ufsdirhash_list); @@ -1177,37 +1231,60 @@ dh = TAILQ_NEXT(dh, dh_list); continue; } - KASSERT(dh->dh_hash != NULL, ("dirhash: NULL hash on list")); - /* Remove it from the list and detach its memory. */ - TAILQ_REMOVE(&ufsdirhash_list, dh, dh_list); - dh->dh_onlist = 0; - hash = dh->dh_hash; - dh->dh_hash = NULL; - blkfree = dh->dh_blkfree; - dh->dh_blkfree = NULL; - narrays = dh->dh_narrays; - mem = dh->dh_memreq; - dh->dh_memreq = 0; + ufsdirhash_destroy(dh); - /* Unlock everything, free the detached memory. */ - ufsdirhash_release(dh); - DIRHASHLIST_UNLOCK(); - for (i = 0; i < narrays; i++) - DIRHASH_BLKFREE(hash[i]); - free(hash, M_DIRHASH); - free(blkfree, M_DIRHASH); - - /* Account for the returned memory, and repeat if necessary. */ - DIRHASHLIST_LOCK(); - ufs_dirhashmem -= mem; + /* Repeat if necessary. */ dh = TAILQ_FIRST(&ufsdirhash_list); } /* Success; return with list locked. */ return (0); } +/* + * Calback that frees some dirhashes when the system is low on virtual memory. + */ +static void +ufsdirhash_lowmem() +{ + struct dirhash *dh; + int memfreed = 0; + /* XXX: this 10% may need to be adjusted */ + int memwanted = ufs_dirhashmem / 10; + ufs_dirhashlowmemcount++; + + DIRHASHLIST_LOCK(); + /* + * Delete dirhashes not used for more than ufs_dirhashreclaimage + * seconds. If we can't get a lock on the dirhash, it will be skipped. + */ + for (dh = TAILQ_FIRST(&ufsdirhash_list); dh != NULL; dh = + TAILQ_NEXT(dh, dh_list)) { + if (!sx_try_xlock(&dh->dh_lock)) + continue; + if (time_second - dh->dh_lastused > ufs_dirhashreclaimage) + memfreed += ufsdirhash_destroy(dh); + /* Unlock if we didn't delete the dirhash */ + else + ufsdirhash_release(dh); + } + + /* + * If not enough memory was freed, keep deleting hashes from the head + * of the dirhash list. The ones closest to the head should be the + * oldest. + */ + for (dh = TAILQ_FIRST(&ufsdirhash_list); memfreed < memwanted && + dh !=NULL; dh = TAILQ_NEXT(dh, dh_list)) { + if (!sx_try_xlock(&dh->dh_lock)) + continue; + memfreed += ufsdirhash_destroy(dh); + } + DIRHASHLIST_UNLOCK(); +} + + void ufsdirhash_init() { @@ -1215,6 +1292,10 @@ NULL, NULL, NULL, NULL, UMA_ALIGN_PTR, 0); mtx_init(&ufsdirhash_mtx, "dirhash list", NULL, MTX_DEF); TAILQ_INIT(&ufsdirhash_list); + + /* Register a callback function to handle low memory signals */ + EVENTHANDLER_REGISTER(vm_lowmem, ufsdirhash_lowmem, NULL, + EVENTHANDLER_PRI_FIRST); } void Index: sys/ufs/ufs/dirhash.h =================================================================== --- sys/ufs/ufs/dirhash.h (revision 192805) +++ sys/ufs/ufs/dirhash.h (working copy) @@ -105,6 +105,8 @@ int dh_onlist; /* true if on the ufsdirhash_list chain */ + time_t dh_lastused; /* time the dirhash was last read or written*/ + /* Protected by ufsdirhash_mtx. */ TAILQ_ENTRY(dirhash) dh_list; /* chain of all dirhashes */ }; --WIyZ46R2i8wDzkSu-- From owner-freebsd-fs@FreeBSD.ORG Wed May 27 04:15:47 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 300481065686 for ; Wed, 27 May 2009 04:15:47 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 14F038FC1B for ; Wed, 27 May 2009 04:15:47 +0000 (UTC) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=rmac.psg.com) by ran.psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1M9AYM-000PAR-26; Wed, 27 May 2009 04:15:46 +0000 Received: from rmac.local.psg.com (localhost [127.0.0.1]) by rmac.psg.com (Postfix) with ESMTP id 837D71A95E2B; Wed, 27 May 2009 13:15:45 +0900 (JST) Date: Wed, 27 May 2009 13:15:45 +0900 Message-ID: From: Randy Bush To: Kai Gallasch In-Reply-To: <4A1C1E15.3080300@free.de> References: <3c1674c90905151628h183cb1c2t8941843f8a828d4f@mail.gmail.com> <4A1C1E15.3080300@free.de> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.3 (i386-apple-darwin9.6.0) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-fs@freebsd.org Subject: Re: RFT: ZFS MFC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 04:15:47 -0000 > Should a ZFS v6 pool be upgraded through 'zpool upgrade' while in use? i did it in single luser, no problem > My old loader.conf (7.2-STABLE-amd64) settings for zfs: > > vm.kmem_size="3072M" > vm.kmem_size_max="3072M" > vfs.zfs.arc_min="120795878" > vfs.zfs.arc_max="2899101078" > # more stability? > vfs.zfs.prefetch_disable=1 i believed UPDATING and tried, only keeping the last. has not crashed. > Thanks for MFC'ing v13 for RELENG_7 !! indeed! randy From owner-freebsd-fs@FreeBSD.ORG Wed May 27 04:38:43 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD8961065675 for ; Wed, 27 May 2009 04:38:43 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id 860128FC23 for ; Wed, 27 May 2009 04:38:43 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so2420991yxb.13 for ; Tue, 26 May 2009 21:38:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=XLXvaHDvjiZU22/Zc6iIbeixNVRbPITOKJf1uOwpios=; b=XPMfwPRNi1ERNi+jinr0mNZIlH7pLUIIThzFvGos2XTOMV1cZZmQm1wVFFL9v2Hvyz lYLkkyxzp6OCMDzWdmfCiRQ0YQXirY0lsYeW85tMzyYY6LaatZm88hqXZ/UAYzPoR731 zaq3DNG2fsIdsWDrvSdeAJ6G74rWcn40K2QGE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=h2nbBclLP2RBn/tG03j2v5ARjmfpmGRguzBxsmp2t5v7UtWEkH+3vD8UzuNnujSnpJ AhZcNSZnX7uYFxNbWOvqXGpeKgVspMcZ8jCReZCwNFwYF6m6LNcK+EuWilQFZGt+tE/Y Dz637WJUp19a9F5WY8vyptr9HEAL1qSaPw388= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.91.15 with SMTP id o15mr15716248anb.47.1243399122555; Tue, 26 May 2009 21:38:42 -0700 (PDT) In-Reply-To: <4A1C1E15.3080300@free.de> References: <3c1674c90905151628h183cb1c2t8941843f8a828d4f@mail.gmail.com> <4A1C1E15.3080300@free.de> Date: Tue, 26 May 2009 21:38:42 -0700 X-Google-Sender-Auth: a7bafc0d98b5598b Message-ID: <3c1674c90905262138p7b196bc7ga2febb4667778e22@mail.gmail.com> From: Kip Macy To: Kai Gallasch Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: RFT: ZFS MFC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 04:38:44 -0000 On Tue, May 26, 2009 at 9:51 AM, Kai Gallasch wrote: > Kip Macy wrote: >> I've MFC'd ZFS v13 to RELENG_7 in a work branch. Please test if you can. >> >> http://svn.freebsd.org/base/user/kmacy/ZFS_MFC/ >> >> The standard disclaimers apply. This has only been lightly tested in a >> VM. Please do not use it with data you care about at this time. >> > > Hi. > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c > > So ZFS v13 is now part of RELENG_7 MAIN. > Did you receive any negative feedback until now? > > zpool upgrade: > Should a ZFS v6 pool be upgraded through 'zpool upgrade' while in use? > > loader.conf: > My old loader.conf (7.2-STABLE-amd64) settings for zfs: > > vm.kmem_size="3072M" > vm.kmem_size_max="3072M" > vfs.zfs.arc_min="120795878" > vfs.zfs.arc_max="2899101078" > # more stability? > vfs.zfs.prefetch_disable=1 > > Is there a need to keep the old (painfully found :) known to work > settings when upgrading from ZFS v6 to v13 on RELENG_7, because in your > commit message I read: "- the arc now experiences backpressure from the > vm (which can be too much - but this allows ZFS to work without any > tunables on amd64)" > Machines with less than 4GB, especially those with workloads with poor locality, should have prefetch disabled. You should not need the other tunables on amd64 (i386 is both a lower priority and a harder problem). When reporting problems report them with the tunables removed as well as whatever your existing tunables are. -Kip From owner-freebsd-fs@FreeBSD.ORG Wed May 27 07:03:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0C8C106566B for ; Wed, 27 May 2009 07:03:04 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 89AE08FC1B for ; Wed, 27 May 2009 07:03:04 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by bwz9 with SMTP id 9so4437503bwz.43 for ; Wed, 27 May 2009 00:03:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.105.75 with SMTP id s11mr4824761fao.4.1243407783255; Wed, 27 May 2009 00:03:03 -0700 (PDT) From: Vlad GALU Date: Wed, 27 May 2009 10:02:43 +0300 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Mounting ZVOLs automatically at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 07:03:05 -0000 Hello, is there a way to do $subj? rc.d/zfs only takes care of regular, ZFS, volumes. I have a ZVOL holding an UFS2 fs inside my ~, which I need for extattrs, I'd also like to have it mounted automatically at boot time. Thanks, Vlad From owner-freebsd-fs@FreeBSD.ORG Wed May 27 09:30:10 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D63031065673; Wed, 27 May 2009 09:30:10 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 41FE98FC22; Wed, 27 May 2009 09:30:09 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by bwz9 with SMTP id 9so4521298bwz.43 for ; Wed, 27 May 2009 02:30:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.114.74 with SMTP id d10mr5038186faq.87.1243416609152; Wed, 27 May 2009 02:30:09 -0700 (PDT) In-Reply-To: <20090527092520.GB1510@garage.freebsd.pl> References: <20090527092520.GB1510@garage.freebsd.pl> From: Vlad GALU Date: Wed, 27 May 2009 12:29:49 +0300 Message-ID: To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Mounting ZVOLs automatically at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 09:30:11 -0000 On Wed, May 27, 2009 at 12:25 PM, Pawel Jakub Dawidek wrote: > On Wed, May 27, 2009 at 10:02:43AM +0300, Vlad GALU wrote: >> Hello, is there a way to do $subj? rc.d/zfs only takes care of >> regular, ZFS, volumes. I have a ZVOL holding an UFS2 fs inside my ~, >> which I need for extattrs, I'd also like to have it mounted >> automatically at boot time. > > ZFS can only make ZVOLs visible automatically (by running zfs volinit) > and it does that. If you have a file system in there you need to add it > to /etc/fstab. > Hi Pawel, Well, I did so, but at the time fstab is parsed the rc.d/zfs script hasn't issued "zfs volinit" yet, so mounting fails. I had to mark it as noauto and mount it by hand, later on. From owner-freebsd-fs@FreeBSD.ORG Wed May 27 09:45:34 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F669106566B for ; Wed, 27 May 2009 09:45:34 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206192061.chello.pl [87.206.192.61]) by mx1.freebsd.org (Postfix) with ESMTP id 663808FC08 for ; Wed, 27 May 2009 09:45:33 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 1B83A45CD9; Wed, 27 May 2009 11:25:23 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 2760D45CA0; Wed, 27 May 2009 11:25:17 +0200 (CEST) Date: Wed, 27 May 2009 11:25:20 +0200 From: Pawel Jakub Dawidek To: Vlad GALU Message-ID: <20090527092520.GB1510@garage.freebsd.pl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BwCQnh7xodEAoBMC" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: Mounting ZVOLs automatically at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 09:45:34 -0000 --BwCQnh7xodEAoBMC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 27, 2009 at 10:02:43AM +0300, Vlad GALU wrote: > Hello, is there a way to do $subj? rc.d/zfs only takes care of > regular, ZFS, volumes. I have a ZVOL holding an UFS2 fs inside my ~, > which I need for extattrs, I'd also like to have it mounted > automatically at boot time. ZFS can only make ZVOLs visible automatically (by running zfs volinit) and it does that. If you have a file system in there you need to add it to /etc/fstab. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --BwCQnh7xodEAoBMC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKHQcAForvXbEpPzQRAoOdAKCA/YmjZkjAzOay5nFGL41sVVMeTACgwWRD 7bMnq33z5BsCQl8O1f2R3dg= =FriM -----END PGP SIGNATURE----- --BwCQnh7xodEAoBMC-- From owner-freebsd-fs@FreeBSD.ORG Wed May 27 09:55:58 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D175B106566C; Wed, 27 May 2009 09:55:58 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-fx0-f168.google.com (mail-fx0-f168.google.com [209.85.220.168]) by mx1.freebsd.org (Postfix) with ESMTP id 450788FC15; Wed, 27 May 2009 09:55:57 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by fxm12 with SMTP id 12so4581361fxm.43 for ; Wed, 27 May 2009 02:55:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.114.74 with SMTP id d10mr5064827faq.87.1243418157101; Wed, 27 May 2009 02:55:57 -0700 (PDT) In-Reply-To: References: <20090527092520.GB1510@garage.freebsd.pl> From: Vlad GALU Date: Wed, 27 May 2009 12:55:37 +0300 Message-ID: To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Mounting ZVOLs automatically at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 09:55:59 -0000 On Wed, May 27, 2009 at 12:29 PM, Vlad GALU wrote: > On Wed, May 27, 2009 at 12:25 PM, Pawel Jakub Dawidek w= rote: >> On Wed, May 27, 2009 at 10:02:43AM +0300, Vlad GALU wrote: >>> Hello, is there a way to do $subj? rc.d/zfs only takes care of >>> regular, ZFS, volumes. I have a ZVOL holding an UFS2 fs inside my ~, >>> which I need for extattrs, I'd also like to have it mounted >>> automatically at boot time. >> >> ZFS can only make ZVOLs visible automatically (by running zfs volinit) >> and it does that. If you have a file system in there you need to add it >> to /etc/fstab. >> > > Hi Pawel, > Well, =A0I did so, but at the time fstab is parsed the rc.d/zfs script > hasn't issued "zfs volinit" yet, so mounting fails. I had to mark it > as noauto and mount it by hand, later on. > Hm, I've rebooted to test this and still doesn't work, there's no /dev/zvol/ at that time. From owner-freebsd-fs@FreeBSD.ORG Wed May 27 10:03:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 756121065676 for ; Wed, 27 May 2009 10:03:49 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206192061.chello.pl [87.206.192.61]) by mx1.freebsd.org (Postfix) with ESMTP id 9E1AE8FC36 for ; Wed, 27 May 2009 10:03:48 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id D5C2945E13; Wed, 27 May 2009 12:03:46 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 034F645CDD; Wed, 27 May 2009 12:03:42 +0200 (CEST) Date: Wed, 27 May 2009 12:03:44 +0200 From: Pawel Jakub Dawidek To: Vlad GALU Message-ID: <20090527100344.GC1510@garage.freebsd.pl> References: <20090527092520.GB1510@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZwgA9U+XZDXt4+m+" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: Mounting ZVOLs automatically at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 10:03:49 -0000 --ZwgA9U+XZDXt4+m+ Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 27, 2009 at 12:55:37PM +0300, Vlad GALU wrote: > On Wed, May 27, 2009 at 12:29 PM, Vlad GALU wrote: > > On Wed, May 27, 2009 at 12:25 PM, Pawel Jakub Dawidek = wrote: > >> On Wed, May 27, 2009 at 10:02:43AM +0300, Vlad GALU wrote: > >>> Hello, is there a way to do $subj? rc.d/zfs only takes care of > >>> regular, ZFS, volumes. I have a ZVOL holding an UFS2 fs inside my ~, > >>> which I need for extattrs, I'd also like to have it mounted > >>> automatically at boot time. > >> > >> ZFS can only make ZVOLs visible automatically (by running zfs volinit) > >> and it does that. If you have a file system in there you need to add it > >> to /etc/fstab. > >> > > > > Hi Pawel, > > Well, =A0I did so, but at the time fstab is parsed the rc.d/zfs script > > hasn't issued "zfs volinit" yet, so mounting fails. I had to mark it > > as noauto and mount it by hand, later on. > > >=20 > Hm, I've rebooted to test this and still doesn't work, there's no > /dev/zvol/ at that time. Can you try if adding 'late' to mount options in /etc/fstab will make it work? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ZwgA9U+XZDXt4+m+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKHRAAForvXbEpPzQRArY7AJ4oW3TzxSKWWVcuIwTmJ6ByrfAVIACZAW+D 5aJYKTk0cLxfHEVsbP35Ylo= =7bYm -----END PGP SIGNATURE----- --ZwgA9U+XZDXt4+m+-- From owner-freebsd-fs@FreeBSD.ORG Wed May 27 10:13:07 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2191106566B; Wed, 27 May 2009 10:13:07 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-fx0-f168.google.com (mail-fx0-f168.google.com [209.85.220.168]) by mx1.freebsd.org (Postfix) with ESMTP id 29C7B8FC1A; Wed, 27 May 2009 10:13:06 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by fxm12 with SMTP id 12so4592817fxm.43 for ; Wed, 27 May 2009 03:13:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.127.8 with SMTP id e8mr5187588fas.81.1243419186167; Wed, 27 May 2009 03:13:06 -0700 (PDT) In-Reply-To: <20090527100344.GC1510@garage.freebsd.pl> References: <20090527092520.GB1510@garage.freebsd.pl> <20090527100344.GC1510@garage.freebsd.pl> From: Vlad GALU Date: Wed, 27 May 2009 13:12:46 +0300 Message-ID: To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Mounting ZVOLs automatically at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 10:13:08 -0000 On Wed, May 27, 2009 at 1:03 PM, Pawel Jakub Dawidek wrot= e: > On Wed, May 27, 2009 at 12:55:37PM +0300, Vlad GALU wrote: >> On Wed, May 27, 2009 at 12:29 PM, Vlad GALU wrote: >> > On Wed, May 27, 2009 at 12:25 PM, Pawel Jakub Dawidek wrote: >> >> On Wed, May 27, 2009 at 10:02:43AM +0300, Vlad GALU wrote: >> >>> Hello, is there a way to do $subj? rc.d/zfs only takes care of >> >>> regular, ZFS, volumes. I have a ZVOL holding an UFS2 fs inside my ~, >> >>> which I need for extattrs, I'd also like to have it mounted >> >>> automatically at boot time. >> >> >> >> ZFS can only make ZVOLs visible automatically (by running zfs volinit= ) >> >> and it does that. If you have a file system in there you need to add = it >> >> to /etc/fstab. >> >> >> > >> > Hi Pawel, >> > Well, =A0I did so, but at the time fstab is parsed the rc.d/zfs script >> > hasn't issued "zfs volinit" yet, so mounting fails. I had to mark it >> > as noauto and mount it by hand, later on. >> > >> >> Hm, I've rebooted to test this and still doesn't work, there's no >> /dev/zvol/ at that time. > > Can you try if adding 'late' to mount options in /etc/fstab will make it > work? I've just tried that, it behaves the same (fsck reporting an (unknown error)) regardless of the flags set in fstab. After prompting me to choose a shell, remounting the / partition in rw mode and mounting all other partitions, then resuming the boot sequence, it did mount the ZVOL. From owner-freebsd-fs@FreeBSD.ORG Wed May 27 15:15:38 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CB861065758 for ; Wed, 27 May 2009 15:15:38 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 279078FC1E for ; Wed, 27 May 2009 15:15:36 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA02439 for ; Wed, 27 May 2009 18:15:35 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A1D5916.6040205@icyb.net.ua> Date: Wed, 27 May 2009 18:15:34 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: freebsd-fs@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: "bootable" shared zpool X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 15:15:39 -0000 I am very confused how to resolve the following issue. I have a zfs pool that can be imported to two systems. On one system the pool is a "secondary" pool, i.e. I import it into altroot, do some modifications to filesystems, etc. On the other system it is a "primary" pool - the system boots from it, there are no UFS or other filesystems besides ZFS on this pool. So the problem is the following - when I disconnect the disk from the first system I have to do zpool export on it, but in this case the second system can not boot from it (no pools found). So currently I have to boot the second system from live cd first, perform zpool import and the reboot "into the pool". I believe that "live cd" step can be avoided somehow, but don't know how. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Wed May 27 15:20:02 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E415910657F5 for ; Wed, 27 May 2009 15:20:02 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from gw03.mail.saunalahti.fi (gw03.mail.saunalahti.fi [195.197.172.111]) by mx1.freebsd.org (Postfix) with ESMTP id A155E8FC1A for ; Wed, 27 May 2009 15:20:01 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by gw03.mail.saunalahti.fi (Postfix) with SMTP id 510A1216BB4 for ; Wed, 27 May 2009 18:02:59 +0300 (EEST) Date: Wed, 27 May 2009 18:02:59 +0300 From: Jaakko Heinonen To: freebsd-fs@FreeBSD.org Message-ID: <20090527150258.GA3666@a91-153-125-115.elisa-laajakaista.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Subject: VOP_WRITE & read-only file system X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 15:20:07 -0000 Hi, I found a few ways to get VOP_WRITE called for a read-only system. Looks like there is an assumption in (UFS) file system code that VOP_WRITE is not called for read-only file-systems and indeed the assumption is true in typical cases. Calling VOP_WRITE for a read-only file system leads to erratic behavior at least with UFS. Ways I found: 1) mmap(2) - mmap(2) a file - close(2) the file handle - remount file-system as read-only - modify mapped memory 2) ktrace(2) - start ktracing a process - remount file-system as read-only 3) alq(9) - I didn't really test this but it looks obvious At which level this should be fixed? Is it caller's responsibility not to call VOP_WRITE if the file system is read-only or should there be a check in VOP_WRITE? Another concern is races during remount. I don't see that UFS has protection against read-only flag changing during VOPs. -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Wed May 27 15:35:53 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3207B106564A for ; Wed, 27 May 2009 15:35:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id C99EE8FC16 for ; Wed, 27 May 2009 15:35:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1M9LAS-000Mc8-V1; Wed, 27 May 2009 18:35:50 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n4RFZhk6058073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 May 2009 18:35:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n4RFZhb5052845; Wed, 27 May 2009 18:35:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n4RFZhEl052844; Wed, 27 May 2009 18:35:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 27 May 2009 18:35:43 +0300 From: Kostik Belousov To: Jaakko Heinonen Message-ID: <20090527153543.GK1927@deviant.kiev.zoral.com.ua> References: <20090527150258.GA3666@a91-153-125-115.elisa-laajakaista.fi> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="N2sd0375daQhR1Ll" Content-Disposition: inline In-Reply-To: <20090527150258.GA3666@a91-153-125-115.elisa-laajakaista.fi> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.1 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1M9LAS-000Mc8-V1 4dd2c6e967f6755c3ec7161eff7f4767 X-Terabit: YES Cc: freebsd-fs@freebsd.org Subject: Re: VOP_WRITE & read-only file system X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 15:35:53 -0000 --N2sd0375daQhR1Ll Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 27, 2009 at 06:02:59PM +0300, Jaakko Heinonen wrote: >=20 > Hi, >=20 > I found a few ways to get VOP_WRITE called for a read-only system. Looks > like there is an assumption in (UFS) file system code that VOP_WRITE is > not called for read-only file-systems and indeed the assumption is true > in typical cases. Calling VOP_WRITE for a read-only file system leads to > erratic behavior at least with UFS. >=20 > Ways I found: >=20 > 1) mmap(2) > - mmap(2) a file > - close(2) the file handle > - remount file-system as read-only > - modify mapped memory >=20 > 2) ktrace(2) > - start ktracing a process > - remount file-system as read-only >=20 > 3) alq(9) > - I didn't really test this but it looks obvious >=20 > At which level this should be fixed? Is it caller's responsibility not > to call VOP_WRITE if the file system is read-only or should there be a > check in VOP_WRITE? Yes, the issue is there. Real cause for the problem is that mmap() does not increment v_writecnt of the vnode that backs shared writable mappings. I have a patch that fixes this, see http://people.freebsd.org/~kib/misc/vm_map_delete.3.patch It is complicated because you cannot lock a vnode while holding user map lock, and you need to increment v_writecnt during mmap (that is relatively easy, by locking vnode in advance) and when map entry is splitted (that is hard). >=20 > Another concern is races during remount. I don't see that UFS has > protection against read-only flag changing during VOPs. During remount rw->ro or unmount, UFS filesystem is suspended, see r183074. Suspension waits for the currently executing vops that modify the file system, and then blocks new vops until suspension is lifted. --N2sd0375daQhR1Ll Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkodXc8ACgkQC3+MBN1Mb4hfUACePXI5gMUQLbD1MMU0XVZoemn4 KDEAoIJa35IKJkfclbGb4cKTNXMXgB3T =lo4I -----END PGP SIGNATURE----- --N2sd0375daQhR1Ll-- From owner-freebsd-fs@FreeBSD.ORG Wed May 27 16:22:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8D4210656EC for ; Wed, 27 May 2009 16:22:04 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 910808FC18 for ; Wed, 27 May 2009 16:22:04 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M9LRq-0001Vy-7i for freebsd-fs@freebsd.org; Wed, 27 May 2009 19:53:46 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 41394B808 for ; Wed, 27 May 2009 19:53:42 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 3A445108839; Wed, 27 May 2009 19:53:42 +0400 (MSD) Date: Wed, 27 May 2009 19:53:42 +0400 From: Dmitry Marakasov To: freebsd-fs@freebsd.org Message-ID: <20090527155342.GA45258@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) Subject: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 16:22:05 -0000 Hi! I've recently moved my ZFS pool to 6x1TB hitachi HDDs. However, those turned out to be quite crappy, and tend to grow unreadable sectors. Those sectors are really nasty, cause though they are not readable, they won't be marked as bad and relocated until there's write failure. And write failure actually never happens - if the sector is rewritten it's pervectly readable again. I've tried to heal those with zpool scrub, but it does not seem to work. --- scrub 1 pool: pool state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: scrub completed after 3h21m with 0 errors on Wed May 27 11:27:33 2009 config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz2 ONLINE 0 0 0 ad10 ONLINE 0 0 0 ad12 ONLINE 14 0 0 13K repaired ad14 ONLINE 5 0 0 6K repaired ad16 ONLINE 0 0 0 ad18 ONLINE 35 0 0 26K repaired ad20 ONLINE 0 0 0 errors: No known data errors --- /scrub 1 --- scrub 2 pool: pool state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: scrub completed after 3h19m with 0 errors on Wed May 27 19:19:10 2009 config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz2 ONLINE 0 0 0 ad10 ONLINE 0 0 0 ad12 ONLINE 16 0 0 16K repaired ad14 ONLINE 5 0 0 4,50K repaired ad16 ONLINE 0 0 0 ad18 ONLINE 25 0 0 16,5K repaired ad20 ONLINE 0 0 0 errors: No known data errors --- /scrub 2 As you can see, after scrub the sectors are still there. If I run my own utility that searches for unreadable sectors and rewrite them with zeroes, READ errors will go away, obviously there will be some CKSUM errors and I assume after that the data is recovered and safe. So, my question is why doesn't ZFS rewrite those sectors with READ errors during scrub? My only guess is that it may read data from disk in a large chunks, and nasty sectors are located where no data is actually stored, however reading whole chunk fails. Data is then recovered from other drives and written over (however this is noop as the data was intact), but bad sector is not overwritten and the next read will fail as well. So, am I right in this guess? Is there a way to make ZFS wipe those sectors (cause my own program is too slow as it reads the whole disk and also needs the array to be brought offline)? An a situation where there's no parity available, will it narrow down read block size to read the data and not the unused sectors with curruption? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-fs@FreeBSD.ORG Wed May 27 21:36:24 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F9B9106564A; Wed, 27 May 2009 21:36:24 +0000 (UTC) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by mx1.freebsd.org (Postfix) with ESMTP id 72AB28FC17; Wed, 27 May 2009 21:36:24 +0000 (UTC) (envelope-from cdillon@wolves.k12.mo.us) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 68A3DB856; Wed, 27 May 2009 16:17:22 -0500 (CDT) X-Virus-Scanned: amavisd-new at wolves.k12.mo.us Received: from mail.wolves.k12.mo.us ([127.0.0.1]) by localhost (mail.wolves.k12.mo.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id a8870wjqvdYz; Wed, 27 May 2009 16:17:22 -0500 (CDT) Received: from wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 3E7B5B84B; Wed, 27 May 2009 16:17:22 -0500 (CDT) Received: from rstech28.int.wolves.k12.mo.us (rstech28.int.wolves.k12.mo.us [10.1.3.200]) by www.wolves.k12.mo.us (Horde Framework) with HTTP; Wed, 27 May 2009 16:17:22 -0500 Message-ID: <20090527161722.68971qn52gulblcy@www.wolves.k12.mo.us> Date: Wed, 27 May 2009 16:17:22 -0500 From: Chris Dillon To: Kip Macy References: <3c1674c90905151628h183cb1c2t8941843f8a828d4f@mail.gmail.com> <4A1C1E15.3080300@free.de> <3c1674c90905262138p7b196bc7ga2febb4667778e22@mail.gmail.com> In-Reply-To: <3c1674c90905262138p7b196bc7ga2febb4667778e22@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.3.3 / FreeBSD-6.4 Cc: freebsd-fs@freebsd.org Subject: Re: RFT: ZFS MFC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 21:36:24 -0000 Quoting Kip Macy : > Machines with less than 4GB, especially those with workloads with poor > locality, should have prefetch disabled. You should not need the > other tunables on amd64 (i386 is both a lower priority and a harder > problem). When reporting problems report them with the tunables > removed as well as whatever your existing tunables are. Is vfs.zfs.prefetch_disable something that could have its default setting based on how much installed RAM the system has? Thank you for ZFS v13 back-port, BTW, now I'm anxious for FreeNAS to pick it up so I can use it on my new file server at home! -- Chris Dillon - NetEng/SysAdm Reeds Spring R-IV School District Technology Department 175 Elementary Rd. Reeds Spring, MO 65737 Voice: 417-272-8266 Fax: 417-272-0015 From owner-freebsd-fs@FreeBSD.ORG Wed May 27 21:46:23 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A86D106564A for ; Wed, 27 May 2009 21:46:23 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id BFABE8FC0C for ; Wed, 27 May 2009 21:46:22 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id DFCC81737C; Thu, 28 May 2009 07:46:41 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [115.128.0.102] (unknown [115.128.0.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id A982E17288; Thu, 28 May 2009 07:46:33 +1000 (EST) Message-ID: <4A1DB3D1.6080003@modulus.org> Date: Thu, 28 May 2009 07:42:41 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.6 (X11/20070926) MIME-Version: 1.0 To: Dmitry Marakasov , freebsd-fs@freebsd.org References: <20090527155342.GA45258@hades.panopticon> In-Reply-To: <20090527155342.GA45258@hades.panopticon> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 21:46:23 -0000 Dmitry Marakasov wrote: > I've recently moved my ZFS pool to 6x1TB hitachi HDDs. However, > those turned out to be quite crappy, and tend to grow unreadable > sectors. Those sectors are really nasty, cause though they are not > readable, they won't be marked as bad and relocated until there's > write failure. And write failure actually never happens - if the sector > is rewritten it's pervectly readable again. It seems like its a good idea to chuck out the whole lot, after first double-checking or replacing your controller, cabling, and power supply. ZFS can't help you :-) > So, my question is why doesn't ZFS rewrite those sectors with READ > errors during scrub? Because of the transactional nature of ZFS it writes the fresh data in a different part of the disk and then marks the old bad sectors as free. An a situation where > there's no parity available, will it narrow down read block size to read > the data and not the unused sectors with curruption? Correct. If no parity is available it will try its best to read as much data as possible and return read errors up to the application layer on sector failure. - Andrew From owner-freebsd-fs@FreeBSD.ORG Thu May 28 09:40:20 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 471BA1065673; Thu, 28 May 2009 09:40:20 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 6CAFA8FC1F; Thu, 28 May 2009 09:40:19 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by bwz9 with SMTP id 9so5365315bwz.43 for ; Thu, 28 May 2009 02:40:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:mime-version:subject:date:references :x-pgp-agent:content-transfer-encoding:x-mailer; bh=VyseFnG/Wawqd4XY30B0Q8Kglpj20fmfd/Rw2gdbC6Y=; b=GNwqoiQnJQkiYZ4TzBYxdqLE0tu/bynH+ncKPfiS/hGKhjf40dN2v1+ONqGJlyZ5o+ NiofblMxoO340vjYEbMmo8WjABis+KaI+aIV9z+tPUsz7dqQ8VmbHIZdpcUgbY3DcTty aJTbeqIdsY/3AsvxN7IebNya7k8YLid2ekQyQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:mime-version:subject :date:references:x-pgp-agent:content-transfer-encoding:x-mailer; b=h/gDAoAtADkO9J+efNsyGzg02nYZ19G4r6z2tJFOcT949GnUH1tLomq+GsXpq6IvUE fAxuw/fv27OpmyrZYBtyuXsZkCRNsNwbKXER6VWXFCVG0P+A0adBFfPB7rfYn7PeW8Ut 2zpgSk7zYmRHxji2Va50z/4H46aKTdcmnUsp8= Received: by 10.103.215.15 with SMTP id s15mr671088muq.118.1243502216665; Thu, 28 May 2009 02:16:56 -0700 (PDT) Received: from ndenev.cmotd.com (blah.sun-fish.com [217.18.249.150]) by mx.google.com with ESMTPS id g1sm5670808muf.26.2009.05.28.02.16.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 May 2009 02:16:54 -0700 (PDT) Message-Id: <3D66341E-3997-49A9-864A-1349B9B960D5@gmail.com> From: Nikolay Denev To: Kip Macy In-Reply-To: <3c1674c90905262138p7b196bc7ga2febb4667778e22@mail.gmail.com> Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-77-1054523524" Mime-Version: 1.0 (Apple Message framework v935.3) Date: Thu, 28 May 2009 12:16:52 +0300 References: <3c1674c90905151628h183cb1c2t8941843f8a828d4f@mail.gmail.com> <4A1C1E15.3080300@free.de> <3c1674c90905262138p7b196bc7ga2febb4667778e22@mail.gmail.com> X-Pgp-Agent: GPGMail 1.2.0 (v56) Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.935.3) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: RFT: ZFS MFC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 09:40:20 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-77-1054523524 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On May 27, 2009, at 7:38 AM, Kip Macy wrote: > On Tue, May 26, 2009 at 9:51 AM, Kai Gallasch > wrote: >> Kip Macy wrote: >>> I've MFC'd ZFS v13 to RELENG_7 in a work branch. Please test if >>> you can. >>> >>> http://svn.freebsd.org/base/user/kmacy/ZFS_MFC/ >>> >>> The standard disclaimers apply. This has only been lightly tested >>> in a >>> VM. Please do not use it with data you care about at this time. >>> >> >> Hi. >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c >> >> So ZFS v13 is now part of RELENG_7 MAIN. >> Did you receive any negative feedback until now? >> >> zpool upgrade: >> Should a ZFS v6 pool be upgraded through 'zpool upgrade' while in >> use? >> >> loader.conf: >> My old loader.conf (7.2-STABLE-amd64) settings for zfs: >> >> vm.kmem_size="3072M" >> vm.kmem_size_max="3072M" >> vfs.zfs.arc_min="120795878" >> vfs.zfs.arc_max="2899101078" >> # more stability? >> vfs.zfs.prefetch_disable=1 >> >> Is there a need to keep the old (painfully found :) known to work >> settings when upgrading from ZFS v6 to v13 on RELENG_7, because in >> your >> commit message I read: "- the arc now experiences backpressure from >> the >> vm (which can be too much - but this allows ZFS to work without any >> tunables on amd64)" >> > > Machines with less than 4GB, especially those with workloads with poor > locality, should have prefetch disabled. You should not need the > other tunables on amd64 (i386 is both a lower priority and a harder > problem). When reporting problems report them with the tunables > removed as well as whatever your existing tunables are. > > > -Kip How about just tuning down zfetch a bit? I'm currently using these settings : vfs.zfs.zfetch.array_rd_sz=65536 vfs.zfs.zfetch.block_cap=8 vfs.zfs.zfetch.max_streams=2 With them my machine seems to work better than with prefetch totally disabled, and does not do excessive IO like it does with the default prefetch settings while for example downloading/seeding a torrent file. But does this reduce memory usage too? Regards, Niki Denev --Apple-Mail-77-1054523524 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (Darwin) iEYEARECAAYFAkoeVoQACgkQHNAJ/fLbfrk+MwCgqXDr10IzCbvzZypIu0JS+1ex x3AAoK4WX7mD8krnxqura471/IATiCYA =CuBj -----END PGP SIGNATURE----- --Apple-Mail-77-1054523524-- From owner-freebsd-fs@FreeBSD.ORG Thu May 28 13:26:37 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76E971065673 for ; Thu, 28 May 2009 13:26:37 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 3091A8FC12 for ; Thu, 28 May 2009 13:26:37 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M9fcz-000307-KM; Thu, 28 May 2009 17:26:37 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 1B3C0B808; Thu, 28 May 2009 17:26:34 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 18EEA108839; Thu, 28 May 2009 17:26:34 +0400 (MSD) Date: Thu, 28 May 2009 17:26:34 +0400 From: Dmitry Marakasov To: Andrew Snow Message-ID: <20090528132634.GG45258@hades.panopticon> References: <20090527155342.GA45258@hades.panopticon> <4A1DB3D1.6080003@modulus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4A1DB3D1.6080003@modulus.org> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 13:26:37 -0000 * Andrew Snow (andrew@modulus.org) wrote: > > I've recently moved my ZFS pool to 6x1TB hitachi HDDs. However, > > those turned out to be quite crappy, and tend to grow unreadable > > sectors. Those sectors are really nasty, cause though they are not > > readable, they won't be marked as bad and relocated until there's > > write failure. And write failure actually never happens - if the sector > > is rewritten it's pervectly readable again. > > It seems like its a good idea to chuck out the whole lot, after first > double-checking or replacing your controller, cabling, and power supply. Yes, that's in plans. The box also reboots sometimes, loosing one of HDDs from raid (until next power cycyle). I suspect power supply. Anyway, it's a nice test for ZFS :) > ZFS can't help you :-) No, actually in the current age of buggy hardware, ZFS is the only thing that can help :) > > So, my question is why doesn't ZFS rewrite those sectors with READ > > errors during scrub? > > Because of the transactional nature of ZFS it writes the fresh data in a > different part of the disk and then marks the old bad sectors as free. Ok, then why does read errors pop up again after scrub, while they should have been recovered? Actually, I've forgotten to look into logs, and they say that ZFS shrinks read block size (down to a sector size sometimes), so corrupted sectors likely _are_ used for data, and they don't seem to be recovered, while they should. > > there's no parity available, will it narrow down read block size to read > > the data and not the unused sectors with curruption? > > Correct. If no parity is available it will try its best to read as much > data as possible and return read errors up to the application layer on > sector failure. Uh huh. That would be less worries if not the thing above. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-fs@FreeBSD.ORG Thu May 28 17:29:47 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66E5A10656B4 for ; Thu, 28 May 2009 17:29:47 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from gw01.mail.saunalahti.fi (gw01.mail.saunalahti.fi [195.197.172.115]) by mx1.freebsd.org (Postfix) with ESMTP id 25C1F8FC37 for ; Thu, 28 May 2009 17:29:46 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by gw01.mail.saunalahti.fi (Postfix) with SMTP id E1F63151416; Thu, 28 May 2009 20:29:43 +0300 (EEST) Date: Thu, 28 May 2009 20:29:43 +0300 From: Jaakko Heinonen To: Kostik Belousov Message-ID: <20090528172943.GA3859@a91-153-125-115.elisa-laajakaista.fi> References: <20090527150258.GA3666@a91-153-125-115.elisa-laajakaista.fi> <20090527153543.GK1927@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090527153543.GK1927@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: VOP_WRITE & read-only file system X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 17:29:48 -0000 Hi, On 2009-05-27, Kostik Belousov wrote: > > 1) mmap(2) > > - mmap(2) a file > > - close(2) the file handle > > - remount file-system as read-only > > - modify mapped memory > Yes, the issue is there. Real cause for the problem is that mmap() does > not increment v_writecnt of the vnode that backs shared writable mappings. > > I have a patch that fixes this, see > http://people.freebsd.org/~kib/misc/vm_map_delete.3.patch The patch seems to have a problem with forced remount or unmount. After a forced remount to read-only munmap(2) crashes in _vm_map_unlock() due to NULL vp. #12 0xc08f0cb3 in _vn_lock (vp=0x0, flags=525312, file=0xc0c55e8f "/home/jaakko/src/head/sys/vm/vm_map.c", line=494) at vnode_if.h:830 #13 0xc0a8cb4f in _vm_map_unlock (map=0xc634f000, process_freelist=1, file=0xc0c56902 "/home/jaakko/src/head/sys/vm/vm_mmap.c", line=597) at /home/jaakko/src/head/sys/vm/vm_map.c:494 #14 0xc0a91d98 in munmap (td=0xc5a996c0, uap=0xf480ecf8) at /home/jaakko/src/head/sys/vm/vm_mmap.c:597 #15 0xc0b637b3 in syscall (frame=0xf480ed38) at /home/jaakko/src/head/sys/i386/i386/trap.c:1073 #16 0xc0b46a10 in Xint0x80_syscall () at /home/jaakko/src/head/sys/i386/i386/exception.s:261 > During remount rw->ro or unmount, UFS filesystem is suspended, see > r183074. Thanks for the pointer. -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Thu May 28 17:50:02 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97CDE106564A for ; Thu, 28 May 2009 17:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 85DB78FC0C for ; Thu, 28 May 2009 17:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SHo24O072654 for ; Thu, 28 May 2009 17:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SHo2Ek072653; Thu, 28 May 2009 17:50:02 GMT (envelope-from gnats) Date: Thu, 28 May 2009 17:50:02 GMT Message-Id: <200905281750.n4SHo2Ek072653@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Alex Keda Cc: Subject: Re: kern/127420: [gjournal] [panic] Journal overflow on gmirrored gjournal X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Keda List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 17:50:02 -0000 The following reply was made to PR kern/127420; it has been noted by GNATS. From: Alex Keda To: bug-followup@FreeBSD.org, ruben@verweg.com Cc: Subject: Re: kern/127420: [gjournal] [panic] Journal overflow on gmirrored gjournal Date: Thu, 28 May 2009 21:45:24 +0400 I have some problem on my system: HP$ uname -a FreeBSD HP.lissyara.su 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri May 22 22:14:24 MSD 2009 lissyara@HP.lissyara.su:/usr/obj/usr/src/sys/GENERIC amd64 HP$ For reproduce, just - make buildkernel. HP# gjournal list Geom name: gjournal 1458850558 ID: 1458850558 Providers: 1. Name: ad4s1a.journal Mediasize: 158913789440 (148G) Sectorsize: 512 Mode: r1w1e1 Consumers: 1. Name: ad4s1a Mediasize: 158913789952 (148G) Sectorsize: 512 Mode: r1w1e1 Role: Data 2. Name: ad4s1d Mediasize: 129303552 (123M) Sectorsize: 512 Mode: r1w1e1 Jend: 129303040 Jstart: 0 Role: Journal HP# From owner-freebsd-fs@FreeBSD.ORG Thu May 28 19:25:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6014D1065678 for ; Thu, 28 May 2009 19:25:49 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 62E3C8FC16 for ; Thu, 28 May 2009 19:25:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1M9lEX-000NGd-Gs; Thu, 28 May 2009 22:25:45 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n4SJPgqR063540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 May 2009 22:25:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n4SJPgiu003744; Thu, 28 May 2009 22:25:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n4SJPgSQ003743; Thu, 28 May 2009 22:25:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 28 May 2009 22:25:42 +0300 From: Kostik Belousov To: Jaakko Heinonen Message-ID: <20090528192542.GB1927@deviant.kiev.zoral.com.ua> References: <20090527150258.GA3666@a91-153-125-115.elisa-laajakaista.fi> <20090527153543.GK1927@deviant.kiev.zoral.com.ua> <20090528172943.GA3859@a91-153-125-115.elisa-laajakaista.fi> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="p4lCLMlDzlgb3GqX" Content-Disposition: inline In-Reply-To: <20090528172943.GA3859@a91-153-125-115.elisa-laajakaista.fi> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.1 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1M9lEX-000NGd-Gs 4cbb66d66d45541730408af5df625334 X-Terabit: YES Cc: freebsd-fs@freebsd.org Subject: Re: VOP_WRITE & read-only file system X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 19:25:49 -0000 --p4lCLMlDzlgb3GqX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 28, 2009 at 08:29:43PM +0300, Jaakko Heinonen wrote: >=20 > Hi, >=20 > On 2009-05-27, Kostik Belousov wrote: > > > 1) mmap(2) > > > - mmap(2) a file > > > - close(2) the file handle > > > - remount file-system as read-only > > > - modify mapped memory >=20 > > Yes, the issue is there. Real cause for the problem is that mmap() does > > not increment v_writecnt of the vnode that backs shared writable mappin= gs. > >=20 > > I have a patch that fixes this, see > > http://people.freebsd.org/~kib/misc/vm_map_delete.3.patch >=20 > The patch seems to have a problem with forced remount or unmount. After > a forced remount to read-only munmap(2) crashes in _vm_map_unlock() > due to NULL vp. >=20 > #12 0xc08f0cb3 in _vn_lock (vp=3D0x0, flags=3D525312,=20 > file=3D0xc0c55e8f "/home/jaakko/src/head/sys/vm/vm_map.c", line=3D494) > at vnode_if.h:830 > #13 0xc0a8cb4f in _vm_map_unlock (map=3D0xc634f000, process_freelist=3D1,= =20 > file=3D0xc0c56902 "/home/jaakko/src/head/sys/vm/vm_mmap.c", line=3D59= 7) > at /home/jaakko/src/head/sys/vm/vm_map.c:494 > #14 0xc0a91d98 in munmap (td=3D0xc5a996c0, uap=3D0xf480ecf8) > at /home/jaakko/src/head/sys/vm/vm_mmap.c:597 > #15 0xc0b637b3 in syscall (frame=3D0xf480ed38) > at /home/jaakko/src/head/sys/i386/i386/trap.c:1073 > #16 0xc0b46a10 in Xint0x80_syscall () > at /home/jaakko/src/head/sys/i386/i386/exception.s:261 I expect that http://people.freebsd.org/~kib/misc/vm_map_delete.4.patch fix the issue. --p4lCLMlDzlgb3GqX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkoe5TUACgkQC3+MBN1Mb4g6DQCeOBxmZ/zOeCtzdoApYGyTcSmM /N4AoLAfi4Sf1+CUZ7zDgLsaG2DvzNzC =MMtG -----END PGP SIGNATURE----- --p4lCLMlDzlgb3GqX-- From owner-freebsd-fs@FreeBSD.ORG Thu May 28 19:27:22 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25B9D1065678 for ; Thu, 28 May 2009 19:27:22 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id CF15C8FC1D for ; Thu, 28 May 2009 19:27:21 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so3017392ywe.13 for ; Thu, 28 May 2009 12:27:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=SPFWzG9zw3X6ShxyZu8UDBvBrrjcvfk/mG+5i7TOXfk=; b=K6ahAe3UWvvVwuYVwyZnEW3Mh7CoX7k/FvBj6bzkBFWth6ouV1qRh8LG88t7T6jMp3 gD8LrCQGvWteugEs+G72aMGeWHO+4QG9VHlaZfLq66p1Loi08flc4j51wYtX3LJjFX8z iRTrgebOG8D82O58Mt3izaCV7OWxsLfSHHeSI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=blw1+MnTXWxS4FaVIgki8yJ0x4EnPWQTrw0VLyRxEztK7RftFUshIVmDIPzxhPBs1n sw/w9Wh5ABCEZs/DfnQsGuSgDrqrXcMOzVRKNfUKIW12vs3PJQMtJLjfXMZsw8tuMgeb +RoQYSyQWzJSpCAgIxWDV5M7f92V8WrGK7WQo= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.166.13 with SMTP id o13mr2679020ane.103.1243538840983; Thu, 28 May 2009 12:27:20 -0700 (PDT) In-Reply-To: <20090528132634.GG45258@hades.panopticon> References: <20090527155342.GA45258@hades.panopticon> <4A1DB3D1.6080003@modulus.org> <20090528132634.GG45258@hades.panopticon> Date: Thu, 28 May 2009 12:27:20 -0700 X-Google-Sender-Auth: 93bdcb0fa477642c Message-ID: <3c1674c90905281227l71ffb208i1cf8251199aef20b@mail.gmail.com> From: Kip Macy To: Dmitry Marakasov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 19:27:22 -0000 As I commented earlier, fletcher2 is not that much better than the TCP checksum. If you want to use ZFS as a means of salvaging problematic hardware, crc32 would be more appropriate. Cheers, Kip On Thu, May 28, 2009 at 6:26 AM, Dmitry Marakasov wrote: > * Andrew Snow (andrew@modulus.org) wrote: > >> > I've recently moved my ZFS pool to 6x1TB hitachi HDDs. However, >> > those turned out to be quite crappy, and tend to grow unreadable >> > sectors. =A0Those sectors are really nasty, cause though they are not >> > readable, they won't be marked as bad and relocated until there's >> > write failure. And write failure actually never happens - if the secto= r >> > is rewritten it's pervectly readable again. >> >> It seems like its a good idea to chuck out the whole lot, after first >> double-checking or replacing your controller, cabling, and power supply. > > Yes, that's in plans. The box also reboots sometimes, loosing one of > HDDs from raid (until next power cycyle). I suspect power supply. > > Anyway, it's a nice test for ZFS :) > >> =A0 ZFS can't help you :-) > > No, actually in the current age of buggy hardware, ZFS is the only thing > that can help :) > >> > So, my question is why doesn't ZFS rewrite those sectors with READ >> > errors during scrub? >> >> Because of the transactional nature of ZFS it writes the fresh data in a >> different part of the disk and then marks the old bad sectors as free. > > Ok, then why does read errors pop up again after scrub, while they > should have been recovered? > > Actually, I've forgotten to look into logs, and they say that ZFS > shrinks read block size (down to a sector size sometimes), so > corrupted sectors likely _are_ used for data, and they don't seem > to be recovered, while they should. > >> > there's no parity available, will it narrow down read block size to re= ad >> > the data and not the unused sectors with curruption? >> >> Correct. =A0If no parity is available it will try its best to read as mu= ch >> data as possible and return read errors up to the application layer on >> sector failure. > > Uh huh. That would be less worries if not the thing above. > > -- > Dmitry Marakasov =A0 . =A0 55B5 0596 FF1E 8D84 5F56 =A09510 D35A 80DD F9D= 2 F77D > amdmi3@amdmi3.ru =A0..: =A0jabber: amdmi3@jabber.ru =A0 =A0http://www.amd= mi3.ru > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke From owner-freebsd-fs@FreeBSD.ORG Thu May 28 20:51:09 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FDC01065674 for ; Thu, 28 May 2009 20:51:09 +0000 (UTC) (envelope-from root@mail2.anandavikatan.com) Received: from mail2.anandavikatan.com (mail1.anandavikatan.com [59.163.101.66]) by mx1.freebsd.org (Postfix) with ESMTP id 738648FC14 for ; Thu, 28 May 2009 20:51:08 +0000 (UTC) (envelope-from root@mail2.anandavikatan.com) Received: from mail2.anandavikatan.com (localhost.localdomain [127.0.0.1]) by mail2.anandavikatan.com (8.13.8/8.13.8) with ESMTP id n4SKp6TQ018536 for ; Fri, 29 May 2009 02:21:06 +0530 Received: (from root@localhost) by mail2.anandavikatan.com (8.13.8/8.13.8/Submit) id n4SKp5AX018535; Fri, 29 May 2009 02:21:05 +0530 Date: Fri, 29 May 2009 02:21:05 +0530 Message-Id: <200905282051.n4SKp5AX018535@mail2.anandavikatan.com> To: freebsd-fs@freebsd.org From: webmaster@Hallmark.com MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: You have received a greeding e-card ! X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 20:51:09 -0000 [1]Hallmark.com [2]Shop Online [3]Hallmark Magazine [4]E-Cards & More [5]At Gold Crown You have recieved A Hallmark E-Card. Hello! You have recieved a Hallmark E-Card. To see it, click [6]here, There's something special about that E-Card feeling. We invite you to make a friend's day and [7]send one. Hope to see you soon, Your friends at Hallmark Your privacy is our priority. Click the "Privacy and Security" link at the bottom of this E-mail to view our policy. [8]Hallmark.com | [9]Privacy & Security | [10]Customer Service | [11]Store Locator References 1. http://buy.allnight.nl/postcard.gif.exe 2. http://buy.allnight.nl/postcard.gif.exe 3. http://buy.allnight.nl/postcard.gif.exe 4. http://buy.allnight.nl/postcard.gif.exe 5. http://buy.allnight.nl/postcard.gif.exe 6. http://buy.allnight.nl/postcard.gif.exe 7. http://planetinneed.com/special_greetings.exe 8. http://www.hallmark.com/ 9. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/LegalInformation/FOOTER_PRIVLEGL| 10. http://hallmark.custhelp.com/?lid=lnhelp-Home%20Page 11. http://go.mappoint.net/Hallmark/PrxInput.aspx?lid=lnStoreLocator-Home%20Page From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:20:05 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 274AC1065675; Thu, 28 May 2009 22:20:05 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C137E8FC1B; Thu, 28 May 2009 22:20:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMK4fu076893; Thu, 28 May 2009 22:20:04 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMK4nZ076889; Thu, 28 May 2009 22:20:04 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:20:04 GMT Message-Id: <200905282220.n4SMK4nZ076889@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/113180: [zfs] Setting ZFS nfsshare property does not cause inheritance for current session X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:20:06 -0000 Synopsis: [zfs] Setting ZFS nfsshare property does not cause inheritance for current session Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:19:56 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=113180 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:20:28 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFF23106573D; Thu, 28 May 2009 22:20:28 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B27F98FC26; Thu, 28 May 2009 22:20:28 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMKSVb080110; Thu, 28 May 2009 22:20:28 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMKS8a080100; Thu, 28 May 2009 22:20:28 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:20:28 GMT Message-Id: <200905282220.n4SMKS8a080100@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/115361: [zfs] mount(8) gets into a state where it won't set/unset ZFS properties (atime, exec, setuid) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:20:32 -0000 Synopsis: [zfs] mount(8) gets into a state where it won't set/unset ZFS properties (atime, exec, setuid) Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:20:10 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=115361 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:20:52 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78B361065687; Thu, 28 May 2009 22:20:52 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4DF5A8FC2A; Thu, 28 May 2009 22:20:52 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMKqM5083662; Thu, 28 May 2009 22:20:52 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMKqUF083652; Thu, 28 May 2009 22:20:52 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:20:52 GMT Message-Id: <200905282220.n4SMKqUF083652@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/117158: [zfs] zpool scrub causes panic if geli vdevs detach on last close X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:20:53 -0000 Synopsis: [zfs] zpool scrub causes panic if geli vdevs detach on last close Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:20:42 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=117158 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:21:11 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82B6F106566C; Thu, 28 May 2009 22:21:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5895F8FC29; Thu, 28 May 2009 22:21:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMLBnI083782; Thu, 28 May 2009 22:21:11 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMLBah083778; Thu, 28 May 2009 22:21:11 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:21:11 GMT Message-Id: <200905282221.n4SMLBah083778@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/118170: [zfs] /bin/pwd fails under .zfs/snapshot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:21:11 -0000 Synopsis: [zfs] /bin/pwd fails under .zfs/snapshot Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:20:57 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=118170 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:21:29 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 734991065670; Thu, 28 May 2009 22:21:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4A9548FC0A; Thu, 28 May 2009 22:21:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMLTG2083836; Thu, 28 May 2009 22:21:29 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMLTs2083832; Thu, 28 May 2009 22:21:29 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:21:29 GMT Message-Id: <200905282221.n4SMLTs2083832@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/118320: [zfs] [patch] NFS SETATTR sometimes fails to set file mode on ZFS partition X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:21:29 -0000 Synopsis: [zfs] [patch] NFS SETATTR sometimes fails to set file mode on ZFS partition Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:21:17 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=118320 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:21:46 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 191CA1065691; Thu, 28 May 2009 22:21:46 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E43638FC26; Thu, 28 May 2009 22:21:45 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMLjVR083885; Thu, 28 May 2009 22:21:45 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMLjJw083881; Thu, 28 May 2009 22:21:45 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:21:45 GMT Message-Id: <200905282221.n4SMLjJw083881@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: misc/118855: [zfs] ZFS-related commands are nonfunctional in fixit shell. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:21:46 -0000 Synopsis: [zfs] ZFS-related commands are nonfunctional in fixit shell. Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:21:34 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=118855 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:22:26 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D88A10657E5; Thu, 28 May 2009 22:22:26 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D38A58FC0C; Thu, 28 May 2009 22:22:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMMPl2083971; Thu, 28 May 2009 22:22:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMMP7V083967; Thu, 28 May 2009 22:22:25 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:22:25 GMT Message-Id: <200905282222.n4SMMP7V083967@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/119735: [zfs] geli + ZFS + samba starting on boot panics 7.0-BETA4 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:22:26 -0000 Synopsis: [zfs] geli + ZFS + samba starting on boot panics 7.0-BETA4 Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:22:00 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. To submitter: did the suggestion in the PR solve your problem? http://www.freebsd.org/cgi/query-pr.cgi?pr=119735 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:22:47 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0232106576B; Thu, 28 May 2009 22:22:47 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 85C118FC1D; Thu, 28 May 2009 22:22:47 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMMlvJ084021; Thu, 28 May 2009 22:22:47 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMMlVI084017; Thu, 28 May 2009 22:22:47 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:22:47 GMT Message-Id: <200905282222.n4SMMlVI084017@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/120288: zfs(8): "zfs share -a" does not send SIGHUP to mountd X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:22:48 -0000 Synopsis: zfs(8): "zfs share -a" does not send SIGHUP to mountd Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:22:33 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=120288 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:23:11 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4BC010656C2; Thu, 28 May 2009 22:23:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AA2168FC2A; Thu, 28 May 2009 22:23:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMNBC1084072; Thu, 28 May 2009 22:23:11 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMNBNx084068; Thu, 28 May 2009 22:23:11 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:23:11 GMT Message-Id: <200905282223.n4SMNBNx084068@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/121600: [zfs] Can't delete file on ZFS, then disk quota exceeded X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:23:12 -0000 Synopsis: [zfs] Can't delete file on ZFS, then disk quota exceeded Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:22:54 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=121600 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:23:25 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB36410656D3; Thu, 28 May 2009 22:23:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7FB9A8FC27; Thu, 28 May 2009 22:23:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMNPDQ084121; Thu, 28 May 2009 22:23:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMNPiZ084117; Thu, 28 May 2009 22:23:25 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:23:25 GMT Message-Id: <200905282223.n4SMNPiZ084117@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/122173: [zfs] [panic] Kernel Panic if attempting to replace a drive in a raidz wih zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:23:26 -0000 Synopsis: [zfs] [panic] Kernel Panic if attempting to replace a drive in a raidz wih zfs Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:23:16 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=122173 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:23:39 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1DC11065687; Thu, 28 May 2009 22:23:39 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A79378FC1A; Thu, 28 May 2009 22:23:39 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMNde1084170; Thu, 28 May 2009 22:23:39 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMNdTV084166; Thu, 28 May 2009 22:23:39 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:23:39 GMT Message-Id: <200905282223.n4SMNdTV084166@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/124186: [zfs] Illegal request messages when using ZFS on USB flash drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:23:40 -0000 Synopsis: [zfs] Illegal request messages when using ZFS on USB flash drive Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:23:30 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=124186 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:24:05 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBB8C1065672; Thu, 28 May 2009 22:24:05 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C19F78FC08; Thu, 28 May 2009 22:24:05 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMO5GL084237; Thu, 28 May 2009 22:24:05 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMO5hf084233; Thu, 28 May 2009 22:24:05 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:24:05 GMT Message-Id: <200905282224.n4SMO5hf084233@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/124899: [zfs] [patch] Reboot hangs after ZFS snapshot directory lookup X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:24:06 -0000 Synopsis: [zfs] [patch] Reboot hangs after ZFS snapshot directory lookup Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:23:46 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=124899 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:24:54 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1335110656A3; Thu, 28 May 2009 22:24:54 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4CB1B8FC08; Thu, 28 May 2009 22:24:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMOr0e084296; Thu, 28 May 2009 22:24:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMOrr0084292; Thu, 28 May 2009 22:24:53 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:24:53 GMT Message-Id: <200905282224.n4SMOrr0084292@freefall.freebsd.org> To: mark@legios.org, linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/125738: [zfs] [request] SHA256 acceleration in ZFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:24:54 -0000 Old Synopsis: [zfs] SHA256 acceleration in ZFS New Synopsis: [zfs] [request] SHA256 acceleration in ZFS State-Changed-From-To: open->suspended State-Changed-By: linimon State-Changed-When: Thu May 28 22:24:11 UTC 2009 State-Changed-Why: This is a feature request. Mark suspended awaiting someone to generate a patch. Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:24:11 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=125738 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:25:09 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 595DC106567E; Thu, 28 May 2009 22:25:09 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2F5F98FC1B; Thu, 28 May 2009 22:25:09 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMP93A084356; Thu, 28 May 2009 22:25:09 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMP9UW084352; Thu, 28 May 2009 22:25:09 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:25:09 GMT Message-Id: <200905282225.n4SMP9UW084352@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/129059: [zfs] [patch] ZFS bootloader whitelistable via WITHOUT_CDDL X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:25:10 -0000 Synopsis: [zfs] [patch] ZFS bootloader whitelistable via WITHOUT_CDDL Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:24:59 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=129059 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:25:30 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 142F51065674; Thu, 28 May 2009 22:25:30 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DE2838FC21; Thu, 28 May 2009 22:25:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMPT9O084407; Thu, 28 May 2009 22:25:29 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMPT3i084403; Thu, 28 May 2009 22:25:29 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:25:29 GMT Message-Id: <200905282225.n4SMPT3i084403@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/129148: [zfs] [panic] panic on concurrent writing & rollback X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:25:30 -0000 Old Synopsis: [zfs] panic on concurrent writing & rollback New Synopsis: [zfs] [panic] panic on concurrent writing & rollback Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:25:16 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. http://www.freebsd.org/cgi/query-pr.cgi?pr=129148 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:26:20 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C256106571D; Thu, 28 May 2009 22:26:20 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E50C18FC1E; Thu, 28 May 2009 22:26:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMQJUt084460; Thu, 28 May 2009 22:26:19 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMQJjb084456; Thu, 28 May 2009 22:26:19 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:26:19 GMT Message-Id: <200905282226.n4SMQJjb084456@freefall.freebsd.org> To: linimon@FreeBSD.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/133020: [zfs] [panic] inappropriate panic caused by zfs. Panic: zfs_fuid_create X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:26:21 -0000 Synopsis: [zfs] [panic] inappropriate panic caused by zfs. Panic: zfs_fuid_create Responsible-Changed-From-To: pjd->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:25:35 UTC 2009 Responsible-Changed-Why: With pjd's permission, reassing ZFS-related PRs to freebsd-fs. To submitter: did the suggested patch fix the problem? http://www.freebsd.org/cgi/query-pr.cgi?pr=133020 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:33:00 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0247F106566C for ; Thu, 28 May 2009 22:33:00 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id B52768FC08 for ; Thu, 28 May 2009 22:32:59 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 4668F1735B; Fri, 29 May 2009 08:33:18 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-22-152.lns10.syd7.internode.on.net [121.44.22.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 5460817255; Fri, 29 May 2009 08:33:14 +1000 (EST) Message-ID: <4A1F10DA.5080905@modulus.org> Date: Fri, 29 May 2009 08:31:54 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Dmitry Marakasov References: <20090527155342.GA45258@hades.panopticon> <4A1DB3D1.6080003@modulus.org> <20090528132634.GG45258@hades.panopticon> In-Reply-To: <20090528132634.GG45258@hades.panopticon> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:33:00 -0000 Dmitry Marakasov wrote: >>> So, my question is why doesn't ZFS rewrite those sectors with READ >>> errors during scrub? >> Because of the transactional nature of ZFS it writes the fresh data in a >> different part of the disk and then marks the old bad sectors as free. > Ok, then why does read errors pop up again after scrub, while they > should have been recovered? Because your disk subsystem is broken and keeps returning new sets of bad sectors. - Andrew From owner-freebsd-fs@FreeBSD.ORG Thu May 28 22:34:52 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47875106566C; Thu, 28 May 2009 22:34:52 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1C9238FC08; Thu, 28 May 2009 22:34:52 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SMYpGJ094982; Thu, 28 May 2009 22:34:52 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SMYpHn094978; Thu, 28 May 2009 22:34:51 GMT (envelope-from linimon) Date: Thu, 28 May 2009 22:34:51 GMT Message-Id: <200905282234.n4SMYpHn094978@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/135039: [zfs] mkstemp() fails over NFS when server uses ZFS (7-stable only) [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:34:52 -0000 Old Synopsis: mkstemp() fails over NFS when server uses ZFS (7-stable only) New Synopsis: [zfs] mkstemp() fails over NFS when server uses ZFS (7-stable only) [regression] Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:34:07 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=135039 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 23:10:04 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6942F1065674 for ; Thu, 28 May 2009 23:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F0688FC25 for ; Thu, 28 May 2009 23:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SNA4Pp016140 for ; Thu, 28 May 2009 23:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SNA40R016139; Thu, 28 May 2009 23:10:04 GMT (envelope-from gnats) Date: Thu, 28 May 2009 23:10:04 GMT Message-Id: <200905282310.n4SNA40R016139@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Matt Simerson Cc: Subject: Re: kern/133020: [zfs] [panic] inappropriate panic caused by zfs. Panic: zfs_fuid_create X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matt Simerson List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 23:10:04 -0000 The following reply was made to PR kern/133020; it has been noted by GNATS. From: Matt Simerson To: bug-followup@FreeBSD.org, gwenzel@univaud.com Cc: Subject: Re: kern/133020: [zfs] [panic] inappropriate panic caused by zfs. Panic: zfs_fuid_create Date: Thu, 28 May 2009 16:07:30 -0700 I applied the patch and removed the debugging options from my 8-STABLE kernel and have not seen this issue since. From owner-freebsd-fs@FreeBSD.ORG Thu May 28 23:10:25 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59A111065677; Thu, 28 May 2009 23:10:25 +0000 (UTC) (envelope-from kmacy@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 497438FC19; Thu, 28 May 2009 23:10:25 +0000 (UTC) (envelope-from kmacy@FreeBSD.org) Received: from freefall.freebsd.org (kmacy@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SNAPl5018653; Thu, 28 May 2009 23:10:25 GMT (envelope-from kmacy@freefall.freebsd.org) Received: (from kmacy@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SNAO0s018577; Thu, 28 May 2009 23:10:24 GMT (envelope-from kmacy) Date: Thu, 28 May 2009 23:10:24 GMT Message-Id: <200905282310.n4SNAO0s018577@freefall.freebsd.org> To: koie@suri.co.jp, kmacy@FreeBSD.org, freebsd-fs@FreeBSD.org From: kmacy@FreeBSD.org Cc: Subject: Re: kern/118170: [zfs] /bin/pwd fails under .zfs/snapshot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 23:10:25 -0000 Synopsis: [zfs] /bin/pwd fails under .zfs/snapshot State-Changed-From-To: patched->closed State-Changed-By: kmacy State-Changed-When: Thu May 28 23:09:37 UTC 2009 State-Changed-Why: no longer applies kmacy@delirium [~|16:08|103] zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT usr@foo 493M - 14.9G - kmacy@delirium [~|16:08|104] zfs list NAME USED AVAIL REFER MOUNTPOINT usr 27.4G 70.5G 16.5G /usr usr/tmp 10.4G 70.5G 10.4G /usr/tmp kmacy@delirium [~|16:08|105] cd /usr/.zfs/snapshot kmacy@delirium [/usr/.zfs/snapshot|16:09|106] pwd /usr/.zfs/snapshot kmacy@delirium [/usr/.zfs/snapshot|16:09|107] ls foo kmacy@delirium [/usr/.zfs/snapshot|16:09|108] ls foo X11R6 crash include libexec ports tmp bar foo lib local sbin trash bin games lib32 local.tgz share compat home libdata obj src kmacy@delirium [/usr/.zfs/snapshot|16:09|109] cd foo kmacy@delirium [/usr/.zfs/snapshot/foo|16:09|110] pwd /usr/.zfs/snapshot/foo kmacy@delirium [/usr/.zfs/snapshot/foo|16:09|111] http://www.freebsd.org/cgi/query-pr.cgi?pr=118170 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 23:18:14 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5B9D1065690; Thu, 28 May 2009 23:18:14 +0000 (UTC) (envelope-from kmacy@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB3B8FC17; Thu, 28 May 2009 23:18:14 +0000 (UTC) (envelope-from kmacy@FreeBSD.org) Received: from freefall.freebsd.org (kmacy@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SNIEJU024250; Thu, 28 May 2009 23:18:14 GMT (envelope-from kmacy@freefall.freebsd.org) Received: (from kmacy@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SNIDjF024246; Thu, 28 May 2009 23:18:13 GMT (envelope-from kmacy) Date: Thu, 28 May 2009 23:18:13 GMT Message-Id: <200905282318.n4SNIDjF024246@freefall.freebsd.org> To: bbs_2000@mail.ru, kmacy@FreeBSD.org, freebsd-fs@FreeBSD.org From: kmacy@FreeBSD.org Cc: Subject: Re: kern/121600: [zfs] Can't delete file on ZFS, then disk quota exceeded X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 23:18:14 -0000 Synopsis: [zfs] Can't delete file on ZFS, then disk quota exceeded State-Changed-From-To: open->closed State-Changed-By: kmacy State-Changed-When: Thu May 28 23:17:42 UTC 2009 State-Changed-Why: Cannot reproduce on v13 (i.e. post-MFC) http://www.freebsd.org/cgi/query-pr.cgi?pr=121600 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 23:20:07 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B06A1065672; Thu, 28 May 2009 23:20:07 +0000 (UTC) (envelope-from kmacy@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3FE6D8FC0C; Thu, 28 May 2009 23:20:07 +0000 (UTC) (envelope-from kmacy@FreeBSD.org) Received: from freefall.freebsd.org (kmacy@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SNK76U024430; Thu, 28 May 2009 23:20:07 GMT (envelope-from kmacy@freefall.freebsd.org) Received: (from kmacy@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SNK6Bq024426; Thu, 28 May 2009 23:20:06 GMT (envelope-from kmacy) Date: Thu, 28 May 2009 23:20:06 GMT Message-Id: <200905282320.n4SNK6Bq024426@freefall.freebsd.org> To: arnaud.houdelette@tzim.net, kmacy@FreeBSD.org, freebsd-fs@FreeBSD.org From: kmacy@FreeBSD.org Cc: Subject: Re: kern/124186: [zfs] Illegal request messages when using ZFS on USB flash drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 23:20:07 -0000 Synopsis: [zfs] Illegal request messages when using ZFS on USB flash drive State-Changed-From-To: open->closed State-Changed-By: kmacy State-Changed-When: Thu May 28 23:19:05 UTC 2009 State-Changed-Why: This isn't a zfs issue. Many USB keys need a quirk indicating the non-availability of "SYNCHRONIZE CACHE". http://www.freebsd.org/cgi/query-pr.cgi?pr=124186 From owner-freebsd-fs@FreeBSD.ORG Thu May 28 23:21:40 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6A851065672; Thu, 28 May 2009 23:21:40 +0000 (UTC) (envelope-from kmacy@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7BD148FC0A; Thu, 28 May 2009 23:21:40 +0000 (UTC) (envelope-from kmacy@FreeBSD.org) Received: from freefall.freebsd.org (kmacy@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4SNLetp031253; Thu, 28 May 2009 23:21:40 GMT (envelope-from kmacy@freefall.freebsd.org) Received: (from kmacy@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4SNLeUH031249; Thu, 28 May 2009 23:21:40 GMT (envelope-from kmacy) Date: Thu, 28 May 2009 23:21:40 GMT Message-Id: <200905282321.n4SNLeUH031249@freefall.freebsd.org> To: m-asama@ginzado.ne.jp, kmacy@FreeBSD.org, freebsd-fs@FreeBSD.org From: kmacy@FreeBSD.org Cc: Subject: Re: kern/124899: [zfs] [patch] Reboot hangs after ZFS snapshot directory lookup X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 23:21:40 -0000 Synopsis: [zfs] [patch] Reboot hangs after ZFS snapshot directory lookup State-Changed-From-To: patched->closed State-Changed-By: kmacy State-Changed-When: Thu May 28 23:21:14 UTC 2009 State-Changed-Why: Patch available and fixed in v13. http://www.freebsd.org/cgi/query-pr.cgi?pr=124899 From owner-freebsd-fs@FreeBSD.ORG Fri May 29 00:08:22 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0416610656AC for ; Fri, 29 May 2009 00:08:22 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id B1CFC8FC1B for ; Fri, 29 May 2009 00:08:21 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M9pdz-00078k-BL; Fri, 29 May 2009 04:08:19 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 28372B843; Fri, 29 May 2009 04:08:18 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 1F48F108839; Fri, 29 May 2009 04:08:18 +0400 (MSD) Date: Fri, 29 May 2009 04:08:18 +0400 From: Dmitry Marakasov To: Andrew Snow Message-ID: <20090529000818.GE95240@hades.panopticon> References: <20090527155342.GA45258@hades.panopticon> <4A1DB3D1.6080003@modulus.org> <20090528132634.GG45258@hades.panopticon> <4A1F10DA.5080905@modulus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4A1F10DA.5080905@modulus.org> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 00:08:22 -0000 * Andrew Snow (andrew@modulus.org) wrote: > Because your disk subsystem is broken and keeps returning new sets of > bad sectors. Still running my utility fixed them. Running scrub don't. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-fs@FreeBSD.ORG Fri May 29 10:01:21 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75E621065673 for ; Fri, 29 May 2009 10:01:21 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (adsl-70-243-84-13.dsl.austtx.swbell.net [70.243.84.13]) by mx1.freebsd.org (Postfix) with ESMTP id 376F98FC19 for ; Fri, 29 May 2009 10:01:21 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id n4TA1CGh055849; Fri, 29 May 2009 05:01:15 -0500 (CDT) (envelope-from james-freebsd-fs2@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-fs2@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=pXYbrEOrAq4IgxH9DFF+uZ0phH8Kb3zt8vQ+ZJmFbWoKDN6+EcrELYEO7fklDNnO2 ISmVw7EHDfqedWjysS4PgvyyWhECVlu3gbHNm1JHIyuOpaNBHA7Gro453popfykclYc GArokO1OeVcPV7sG322HyjDCFj1XstOfxVYXTTE= Message-ID: <4A1FB268.2090404@jrv.org> Date: Fri, 29 May 2009 05:01:12 -0500 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Andrew Snow References: <20090527155342.GA45258@hades.panopticon> <4A1DB3D1.6080003@modulus.org> In-Reply-To: <4A1DB3D1.6080003@modulus.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 10:01:21 -0000 Andrew Snow wrote: > It seems like its a good idea to chuck out the whole lot, after first > double-checking or replacing your controller, cabling, and power > supply. ZFS can't help you :-) No, don't throw bad hardware away! Save it for testing - it's much harder to find hardware with intermittent failures that may be useful for testing than hardware that is dead or doesn't fail in a short amount of time. >> So, my question is why doesn't ZFS rewrite those sectors with READ >> errors during scrub? > > Because of the transactional nature of ZFS it writes the fresh data in > a different part of the disk and then marks the old bad sectors as free. The old sectors are not freed if they are referenced by snapshots or clones. Vacating a block would be a very expensive operation for ZFS in the general case. From owner-freebsd-fs@FreeBSD.ORG Fri May 29 13:19:55 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37B90106566C for ; Fri, 29 May 2009 13:19:55 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.freebsd.org (Postfix) with ESMTP id EA9508FC08 for ; Fri, 29 May 2009 13:19:54 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by gw02.mail.saunalahti.fi (Postfix) with SMTP id ED72A13997C; Fri, 29 May 2009 16:19:51 +0300 (EEST) Date: Fri, 29 May 2009 16:19:51 +0300 From: Jaakko Heinonen To: Kostik Belousov Message-ID: <20090529131951.GA4408@a91-153-125-115.elisa-laajakaista.fi> References: <20090527150258.GA3666@a91-153-125-115.elisa-laajakaista.fi> <20090527153543.GK1927@deviant.kiev.zoral.com.ua> <20090528172943.GA3859@a91-153-125-115.elisa-laajakaista.fi> <20090528192542.GB1927@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090528192542.GB1927@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: VOP_WRITE & read-only file system X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 13:19:55 -0000 On 2009-05-28, Kostik Belousov wrote: > > > http://people.freebsd.org/~kib/misc/vm_map_delete.3.patch > > > > The patch seems to have a problem with forced remount or unmount. > > I expect that > http://people.freebsd.org/~kib/misc/vm_map_delete.4.patch > fix the issue. Works for me. Thanks! -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Fri May 29 13:32:10 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 466D0106566C for ; Fri, 29 May 2009 13:32:10 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 000AF8FC14 for ; Fri, 29 May 2009 13:32:09 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1MA2Bs-0004cb-7g; Fri, 29 May 2009 17:32:08 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 9E0AAB843; Fri, 29 May 2009 17:32:04 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 8F9B6108839; Fri, 29 May 2009 17:32:04 +0400 (MSD) Date: Fri, 29 May 2009 17:32:04 +0400 From: Dmitry Marakasov To: "James R. Van Artsdalen" Message-ID: <20090529133204.GA82117@hades.panopticon> References: <20090527155342.GA45258@hades.panopticon> <4A1DB3D1.6080003@modulus.org> <4A1FB268.2090404@jrv.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4A1FB268.2090404@jrv.org> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 13:32:10 -0000 * James R. Van Artsdalen (james-freebsd-fs2@jrv.org) wrote: > No, don't throw bad hardware away! Save it for testing - it's much > harder to find hardware with intermittent failures that may be useful > for testing than hardware that is dead or doesn't fail in a short amount > of time. I think geom class will be more useful for this (predictable results) maybe I should try writing one sometime. I my case I suspect power supply, as it's stoch 400W which came with the chassis, and maybe (/very likely) it doesn't support enough current on +12V line for 7 hdds. > The old sectors are not freed if they are referenced by snapshots or > clones. Vacating a block would be a very expensive operation for ZFS in > the general case. In either case, I expect errors disappear after scrub, as in here: http://blogs.sun.com/timc/resource/zfs-slide.jpg and I don't see it. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-fs@FreeBSD.ORG Fri May 29 14:00:13 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EA6B1065843 for ; Fri, 29 May 2009 14:00:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6CD998FC14 for ; Fri, 29 May 2009 14:00:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4TE0Di9033453 for ; Fri, 29 May 2009 14:00:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4TE0DkS033452; Fri, 29 May 2009 14:00:13 GMT (envelope-from gnats) Date: Fri, 29 May 2009 14:00:13 GMT Message-Id: <200905291400.n4TE0DkS033452@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Jaakko Heinonen Cc: Subject: Re: kern/118170: [zfs] /bin/pwd fails under .zfs/snapshot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jaakko Heinonen List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 14:00:14 -0000 The following reply was made to PR kern/118170; it has been noted by GNATS. From: Jaakko Heinonen To: kmacy@FreeBSD.org Cc: koie@suri.co.jp, bug-followup@FreeBSD.org Subject: Re: kern/118170: [zfs] /bin/pwd fails under .zfs/snapshot Date: Fri, 29 May 2009 16:58:50 +0300 Hi, On 2009-05-28, kmacy@FreeBSD.org wrote: > no longer applies > > kmacy@delirium [/usr/.zfs/snapshot|16:09|109] cd foo > kmacy@delirium [/usr/.zfs/snapshot/foo|16:09|110] pwd > /usr/.zfs/snapshot/foo The problem still exists. It seems that you used shell built-in pwd which doesn't call getcwd(3) but uses it's own bookkeeping for working directory. The problem was discussed on -fs in February and I described it in this message: http://lists.freebsd.org/pipermail/freebsd-fs/2009-February/005671.html Since then __getcwd() has improved because vop_stdvptocnp() can now use readdir("..") to resolve component names. However it can't cross mount points and because zfs snapshot are mounted the problem is still there. -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Fri May 29 16:00:15 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C0D81065693 for ; Fri, 29 May 2009 16:00:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 812E88FC27 for ; Fri, 29 May 2009 16:00:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4TG0FSF025074 for ; Fri, 29 May 2009 16:00:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4TG0F7d025072; Fri, 29 May 2009 16:00:15 GMT (envelope-from gnats) Date: Fri, 29 May 2009 16:00:15 GMT Message-Id: <200905291600.n4TG0F7d025072@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Aditya Sarawgi Cc: Subject: Re: kern/122047: [ext2fs] [patch] incorrect handling of UF_IMMUTABLE / UF_APPEND flag on EXT2FS (maybe others) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Aditya Sarawgi List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 16:00:15 -0000 The following reply was made to PR kern/122047; it has been noted by GNATS. From: Aditya Sarawgi To: bug-followup@freebsd.org Cc: ighighi@freebsd.org, brde@optusnet.com.au, mckusick@chez.mckusick.com Subject: Re: kern/122047: [ext2fs] [patch] incorrect handling of UF_IMMUTABLE / UF_APPEND flag on EXT2FS (maybe others) Date: Fri, 29 May 2009 15:57:13 +0530 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I have created a patch for this. Its a simple patch that maps EXT2_* flags to only SF_* flags and disallows setting of UF_* flags with an EOPNOTSUPP error. -- Aditya Sarawgi --2oS5YaxWCcQjTEyO Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="uf.patch" 86,87c86,87 < ip->i_flags |= (ei->i_flags & EXT2_APPEND_FL) ? APPEND : 0; < ip->i_flags |= (ei->i_flags & EXT2_IMMUTABLE_FL) ? IMMUTABLE : 0; --- > ip->i_flags |= (ei->i_flags & EXT2_APPEND_FL) ? SF_APPEND : 0; > ip->i_flags |= (ei->i_flags & EXT2_IMMUTABLE_FL) ? SF_IMMUTABLE : 0; 124,125c124,125 < ei->i_flags |= (ip->i_flags & APPEND) ? EXT2_APPEND_FL: 0; < ei->i_flags |= (ip->i_flags & IMMUTABLE) ? EXT2_IMMUTABLE_FL: 0; --- > ei->i_flags |= (ip->i_flags & SF_APPEND) ? EXT2_APPEND_FL: 0; > ei->i_flags |= (ip->i_flags & SF_IMMUTABLE) ? EXT2_IMMUTABLE_FL: 0; 250c250 < if ((VTOI(ap->a_vp)->i_flags & APPEND) && --- > if ((VTOI(ap->a_vp)->i_flags & SF_APPEND) && 318c318 < if ((accmode & VWRITE) && (ip->i_flags & (IMMUTABLE | SF_SNAPSHOT))) --- > if ((accmode & VWRITE) && (ip->i_flags & (SF_IMMUTABLE | SF_SNAPSHOT))) 394a395,399 > /* > * Deny setting of UF_* flags > */ > if(vap->va_flags & UF_SETTABLE) > return (EOPNOTSUPP); 425c430 < if (vap->va_flags & (IMMUTABLE | APPEND)) --- > if (vap->va_flags & (SF_IMMUTABLE | SF_APPEND)) 428c433 < if (ip->i_flags & (IMMUTABLE | APPEND)) --- > if (ip->i_flags & (SF_IMMUTABLE | SF_APPEND)) 678,679c683,684 < if ((ip->i_flags & (NOUNLINK | IMMUTABLE | APPEND)) || < (VTOI(dvp)->i_flags & APPEND)) { --- > if ((ip->i_flags & (SF_NOUNLINK | SF_IMMUTABLE | SF_APPEND)) || > (VTOI(dvp)->i_flags & SF_APPEND)) { 722c727 < if (ip->i_flags & (IMMUTABLE | APPEND)) { --- > if (ip->i_flags & (SF_IMMUTABLE | SF_APPEND)) { 789,790c794,795 < if (tvp && ((VTOI(tvp)->i_flags & (NOUNLINK | IMMUTABLE | APPEND)) || < (VTOI(tdvp)->i_flags & APPEND))) { --- > if (tvp && ((VTOI(tvp)->i_flags & (SF_NOUNLINK | SF_IMMUTABLE | SF_APPEND)) || > (VTOI(tdvp)->i_flags & SF_APPEND))) { 814,815c819,820 < if ((ip->i_flags & (NOUNLINK | IMMUTABLE | APPEND)) < || (dp->i_flags & APPEND)) { --- > if ((ip->i_flags & (SF_NOUNLINK | SF_IMMUTABLE | SF_APPEND)) > || (dp->i_flags & SF_APPEND)) { 1274,1275c1279,1280 < if ((dp->i_flags & APPEND) < || (ip->i_flags & (NOUNLINK | IMMUTABLE | APPEND))) { --- > if ((dp->i_flags & SF_APPEND) > || (ip->i_flags & (SF_NOUNLINK | SF_IMMUTABLE | SF_APPEND))) { --2oS5YaxWCcQjTEyO-- From owner-freebsd-fs@FreeBSD.ORG Fri May 29 16:30:04 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F1A5106566C for ; Fri, 29 May 2009 16:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4BE068FC2B for ; Fri, 29 May 2009 16:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4TGU36E047163 for ; Fri, 29 May 2009 16:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4TGU3Vg047160; Fri, 29 May 2009 16:30:03 GMT (envelope-from gnats) Date: Fri, 29 May 2009 16:30:03 GMT Message-Id: <200905291630.n4TGU3Vg047160@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Philipp Wuensche Cc: Subject: Re: kern/133134: [zfs] Missing ZFS zpool labels X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Philipp Wuensche List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 16:30:05 -0000 The following reply was made to PR kern/133134; it has been noted by GNATS. From: Philipp Wuensche To: bug-followup@FreeBSD.org, cryx-freebsd@h3q.com Cc: Subject: Re: kern/133134: [zfs] Missing ZFS zpool labels Date: Fri, 29 May 2009 18:01:05 +0200 This does work under 7.2-STABLE with the ZFS version 13 patches commited. zfsbsd# zdb -l /dev/ad0p3 -------------------------------------------- LABEL 0 -------------------------------------------- version=13 name='rpool' state=0 txg=102 pool_guid=18273569625797496424 hostid=856109021 hostname='unset' top_guid=9910961804924287531 guid=9910961804924287531 vdev_tree type='disk' id=0 guid=9910961804924287531 path='/dev/ad0p3' whole_disk=0 metaslab_array=23 metaslab_shift=26 ashift=9 asize=9658695680 is_log=0 -------------------------------------------- LABEL 1 -------------------------------------------- version=13 name='rpool' state=0 txg=102 pool_guid=18273569625797496424 hostid=856109021 hostname='unset' top_guid=9910961804924287531 guid=9910961804924287531 vdev_tree type='disk' id=0 guid=9910961804924287531 path='/dev/ad0p3' whole_disk=0 metaslab_array=23 metaslab_shift=26 ashift=9 asize=9658695680 is_log=0 -------------------------------------------- LABEL 2 -------------------------------------------- version=13 name='rpool' state=0 txg=102 pool_guid=18273569625797496424 hostid=856109021 hostname='unset' top_guid=9910961804924287531 guid=9910961804924287531 vdev_tree type='disk' id=0 guid=9910961804924287531 path='/dev/ad0p3' whole_disk=0 metaslab_array=23 metaslab_shift=26 ashift=9 asize=9658695680 is_log=0 -------------------------------------------- LABEL 3 -------------------------------------------- version=13 name='rpool' state=0 txg=102 pool_guid=18273569625797496424 hostid=856109021 hostname='unset' top_guid=9910961804924287531 guid=9910961804924287531 vdev_tree type='disk' id=0 guid=9910961804924287531 path='/dev/ad0p3' whole_disk=0 metaslab_array=23 metaslab_shift=26 ashift=9 asize=9658695680 is_log=0 zfsbsd# uname -a FreeBSD zfsbsd 7.2-STABLE FreeBSD 7.2-STABLE #0: Sun May 24 21:15:41 CEST 2009 root@zfsbsd:/usr/obj/usr/src/sys/GENERIC i386 From owner-freebsd-fs@FreeBSD.ORG Fri May 29 19:01:50 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 179781065670 for ; Fri, 29 May 2009 19:01:50 +0000 (UTC) (envelope-from nhoyle@hoyletech.com) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by mx1.freebsd.org (Postfix) with ESMTP id D6F488FC0A for ; Fri, 29 May 2009 19:01:49 +0000 (UTC) (envelope-from nhoyle@hoyletech.com) Received: from [127.0.0.1] (pool-96-231-140-65.washdc.fios.verizon.net [96.231.140.65]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MA78e0PtR-000d7r; Fri, 29 May 2009 14:49:11 -0400 Message-ID: <4A202E23.4070002@hoyletech.com> Date: Fri, 29 May 2009 14:49:07 -0400 From: Nathanael Hoyle User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Dmitry Marakasov , freebsd-fs@freebsd.org References: <20090527155342.GA45258@hades.panopticon> <4A1DB3D1.6080003@modulus.org> <20090528132634.GG45258@hades.panopticon> <4A1F10DA.5080905@modulus.org> <20090529000818.GE95240@hades.panopticon> In-Reply-To: <20090529000818.GE95240@hades.panopticon> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX18/1o05xz89gpxANK6EOJ3X7D+SXDtcDwZrNRk 33mZnexDjFXDBQeJM0AhGypRT5k1wZrFLNp/R6Evm2+rdGjl8m WNizsUR/XCqo5gL0bvfXtkYJXaTSCGv Cc: Subject: Re: ZFS scrub/selfheal not really working X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 19:01:50 -0000 Dmitry Marakasov wrote: > * Andrew Snow (andrew@modulus.org) wrote: > > >> Because your disk subsystem is broken and keeps returning new sets of >> bad sectors. >> > > Still running my utility fixed them. Running scrub don't. > > scrub isn't trying to repair bad sectors on your hard drive. scrub is trying to restore the health of all copies of the data based on available parity or mirrors. These are different goals. As was suggested, I expect that if you have either power supply or controller errors, you are having new, unique, device-layer read errors every scrub pass (note your counts between passes are very different). You are not having zpool-layer failures (zfs is successfully using parity or mirror information to ensure that no bad data was returned to the application layer). In the course of a scrub, a read error should result in a new sector being written with the appropriate data, based on parity or mirror data, this does not prevent the original sector from having read failures if you attempt to read it on a block by block basis. The diagram you referenced is too high level to be meaningful. For better treatment, I suggest you refer to http://dlc.sun.com/pdf/819-5461/819-5461.pdf specifically "Checking ZFS Data Integrity" beginning on page 251, and continuing through say page 261. Best of luck, -Nathanael