From owner-freebsd-fs@FreeBSD.ORG Mon May 3 10:55:56 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1C4F1065670 for ; Mon, 3 May 2010 10:55:56 +0000 (UTC) (envelope-from hali@datapipe.com) Received: from EXFESMQ01.datapipe-corp.net (exchange.datapipe.net [64.106.130.71]) by mx1.freebsd.org (Postfix) with ESMTP id ABDA18FC15 for ; Mon, 3 May 2010 10:55:56 +0000 (UTC) Received: from EXMBSMQ06.datapipe-corp.net ([64.106.130.36]) by EXFESMQ01.datapipe-corp.net ([64.106.130.71]) with mapi; Mon, 3 May 2010 06:55:49 -0400 From: Hussain Ali To: "'freebsd-fs@freebsd.org'" Date: Mon, 3 May 2010 06:55:49 -0400 Thread-Topic: Commercial FreeBSD ZFS implementatoin Thread-Index: AcrqrzENSHrBNssQR++vWMvqj4c0PA== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Commercial FreeBSD ZFS implementatoin 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, 03 May 2010 10:55:57 -0000 Hi, I just read this article: http://tinyurl.com/39do89u was wondering if anyon= e had any insight into the following quote: ' I'm therefore glad to say that SpectraLogic is working on a port of ZFS t= o FreeBSD.' -- -hussain This message may contain confidential or privileged information. If you ar= e not the intended recipient, please advise us immediately and delete this = message. See http://www.datapipe.com/about-us-legal-email-disclaimer.htm f= or further information on confidentiality and the risks of non-secure elect= ronic communication. If you cannot access these links, please notify us by = reply message and we will send the contents to you. From owner-freebsd-fs@FreeBSD.ORG Mon May 3 11:08:04 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4F431065672 for ; Mon, 3 May 2010 11:08:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id BA14B8FC23 for ; Mon, 3 May 2010 11:08:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o43B84mB033589 for ; Mon, 3 May 2010 11:08:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o43B84fT033587 for freebsd-fs@FreeBSD.org; Mon, 3 May 2010 11:08:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 May 2010 11:08:04 GMT Message-Id: <201005031108.o43B84fT033587@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, 03 May 2010 11:08:05 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/145802 fs [zfs] page fault under load o kern/145778 fs [zfs] [panic] panic in zfs_fuid_map_id (known issue fi o kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145424 fs [zfs] [patch] move source closer to v15 o kern/145423 fs [zfs] ZFS/zpool status shows deleted/not present pools o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o kern/145339 fs [zfs] deadlock after detaching block device from raidz o kern/145309 fs [disklabel]: Editing disk label invalidates the whole o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c o kern/144458 fs [nfs] [patch] nfsd fails as a kld o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o bin/144214 fs zfsboot fails on gang block after upgrade to zfs v14 o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o kern/143345 fs [ext2fs] [patch] extfs minor header cleanups to better o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142924 fs [ext2fs] [patch] Small cleanup for the inode struct in o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142401 fs [ntfs] [patch] Minor updates to NTFS from NetBSD o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140433 fs [zfs] [panic] panic while replaying ZIL after crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs o bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/139363 fs [nfs] diskless root nfs mount from non FreeBSD server o kern/138790 fs [zfs] ZFS ceases caching when mem demand is high o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb f kern/137037 fs [zfs] [hang] zfs rollback on root causes FreeBSD to fr o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic o kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [panic] panic: ffs_truncate: read-only filesystem 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/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/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) o kern/129059 fs [zfs] [patch] ZFS bootloader whitelistable via WITHOUT f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS p 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/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t 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 f kern/119735 fs [zfs] geli + ZFS + samba starting on boot panics 7.0-B 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 kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/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 bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] 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/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes 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/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/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/53137 fs [ffs] [panic] background fscking causing ffs_valloc pa o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 173 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon May 3 15:48:33 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D123D106564A for ; Mon, 3 May 2010 15:48:33 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-iw0-f180.google.com (mail-iw0-f180.google.com [209.85.223.180]) by mx1.freebsd.org (Postfix) with ESMTP id 93E778FC2A for ; Mon, 3 May 2010 15:48:33 +0000 (UTC) Received: by iwn10 with SMTP id 10so3486739iwn.13 for ; Mon, 03 May 2010 08:48:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=m5HfCq/L5R74kh9O3vtE9gPBOlsb6tf/ujVInXAGLME=; b=Z9RPa1ySEZWebV2jVpqsZMD/03r6uel5Rb9Eq1DwSSEmgUMvEvOcMo0GJiLB9UaoP4 zBIydtb+7m5+8WqZLryVsnvHCUh8DYaup5x1znt8SZy65sk4wZE9djnM4veQngR03wRe tZDOThbQnxbXKkBTalJ11FTMTi1vJSarsXUck= 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 :content-type; b=GauXr94E4qWtwG861N3irIBp5Z/FJlAJshimGAEaMbeAUamhCCOAH2wvIXIRIJq7ic XsNBx4G2I1LqMkK7Og1RgLRHmIUxn7sYA9ncqiYBNOt+vPpQ9DyZ6TZlXTE8UfiQwT3D to8ByvNtl6PB6T5AvdiqKIu8/6sAF99L0ZF3A= MIME-Version: 1.0 Received: by 10.231.153.130 with SMTP id k2mr1532872ibw.78.1272901663819; Mon, 03 May 2010 08:47:43 -0700 (PDT) Received: by 10.231.11.205 with HTTP; Mon, 3 May 2010 08:47:43 -0700 (PDT) In-Reply-To: References: Date: Mon, 3 May 2010 08:47:43 -0700 Message-ID: From: Freddie Cash To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS: "Cannot replace a replacing 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: Mon, 03 May 2010 15:48:33 -0000 On Fri, Apr 30, 2010 at 1:59 PM, Wes Morgan wrote: > On Fri, 30 Apr 2010, Wes Morgan wrote: > > On Thu, 29 Apr 2010, Freddie Cash wrote: > > > > > On Thu, Apr 29, 2010 at 6:06 PM, Wes Morgan > wrote: > > > > > > > On Wed, 28 Apr 2010, Freddie Cash wrote: > > > > > > > > > Going through the archives, I see that others have run into this > issue, > > > > and > > > > > managed to solve it via "zpool detach". However, looking closely > at the > > > > > archived messages, all the successful tests had one thing in > common: 1 > > > > > drive ONLINE, 1 drive FAULTED. If a drive is online, obviously it > can be > > > > > detached. In all the cases where people have been unsuccessful at > fixing > > > > > this situation, 1 drive is OFFLINE, and 1 drive is FAULTED. As is > our > > > > case: > > > > > > > > > > > > > What happened to the drive to fault it? > > > > > > > > Am in the process of replacing 500 GB drives with 1.5 TB drives, to > > > increase the available storage space in the pool (process went > flawlessly on > > > the other storage server). First 3 disks in the vdev replaced without > > > issues. > > Also, where is the original 500gb drive (#4) that you replaced? You should > be able to put that drive back in and let it resilver itself to catch back > up to the other devices, then cancel the replacement. > That worked. :) I pulled the 1.5 TB drive from the system, inserted the original 500 GB drive, and ZFS detected it and marked it as online, with the 1.5 TB as faulted. At that point, I was able to "zpool detach" the 1.5 TB drive, putting the pool back into the original configuration, and online state. After that, I "zpool offline" the 500 GB drive, replace it with a new 1.5 TB drive, and "zpool replace". And it's happily re-silvering the drive. In 35h, it should be complete. Thankfully, the original drive was not faulty and was only being replaced to increase the size. If the original drive was dead, I'd probably be hooped. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Mon May 3 16:32:16 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 092EA1065672 for ; Mon, 3 May 2010 16:32:16 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id C6C8B8FC22 for ; Mon, 3 May 2010 16:32:15 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.13.8+Sun/8.13.8) with ESMTP id o43GW93K000661; Mon, 3 May 2010 11:32:10 -0500 (CDT) Date: Mon, 3 May 2010 11:32:09 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Hussain Ali In-Reply-To: Message-ID: References: User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Mon, 03 May 2010 11:32:10 -0500 (CDT) Cc: "'freebsd-fs@freebsd.org'" Subject: Re: Commercial FreeBSD ZFS implementatoin 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, 03 May 2010 16:32:16 -0000 On Mon, 3 May 2010, Hussain Ali wrote: > I just read this article: http://tinyurl.com/39do89u was wondering > if anyone had any insight into the following quote: > > ' I'm therefore glad to say that SpectraLogic is working on a port of ZFS to FreeBSD.' Presumably this means that they are sponsoring one or more FreeBSD developers to improve/update the existing FreeBSD port. FreeBSD developers need to eat too. However, it could also be that they are doing their own independent port. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Mon May 3 17:06:26 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 02CFC1065677 for ; Mon, 3 May 2010 17:06:26 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from worf.ds9.tecnik93.com (worf.ds9.tecnik93.com [81.196.207.130]) by mx1.freebsd.org (Postfix) with ESMTP id 65FF78FC23 for ; Mon, 3 May 2010 17:06:25 +0000 (UTC) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by worf.ds9.tecnik93.com (Postfix) with ESMTPSA id F39E322C50C6 for ; Mon, 3 May 2010 19:48:58 +0300 (EEST) Date: Mon, 3 May 2010 19:48:58 +0300 From: Ion-Mihai Tetcu To: freebsd-fs@FreeBSD.org Message-ID: <20100503194858.1cfaa3f9@it.buh.tecnik93.com> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/jmmr8z2E+jxWsD9impDX8+="; protocol="application/pgp-signature" Cc: Subject: ZFS: old drive still in use after zfs replace 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, 03 May 2010 17:06:26 -0000 --Sig_/jmmr8z2E+jxWsD9impDX8+= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, I have a zpool over 4 disks. Since after a scrub ad6 showed some errors, I did a=20 zpool replace tank /dev/ad6 /dev/ad14 which completed with: scrub: resilver completed after 6h36m with 4 errors on Fri Apr 9 07:06:2= 4 2010 However, status in that moment was showing for the two drives in question: replacing ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad14 ONLINE 0 0 0 371G resilvered Rebooting didn't help, not did zfs export tank=20 followed by zfs import -f tank, both with and then without ad6 connected. Now, without ad6 connected: # zpool status -v pool: tank state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scrub: none requested config: NAME STATE READ WRITE CKSUM tank DEGRADED 0 0 0 raidz1 DEGRADED 0 0 0 ad10 ONLINE 0 0 0 replacing DEGRADED 0 0 0 1729652906707038827 UNAVAIL 0 1.34M 0 was /dev/ad6 ad14 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad12 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: /tank/usr/home/some/file1 tank/usr/home:<0xb846> /tank/usr/home/some/file3 /tank/usr/home/some/file4 What should I do next? Thanks, = =20 --=20 IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B --Sig_/jmmr8z2E+jxWsD9impDX8+= Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkve/noACgkQJ7GIuiH/oeXXKgCeObNZvvnKsmdb0S7s5lFFdEjE jtEAoKaO8JSre2LtaV0xXr7UZTZXicnf =Moj0 -----END PGP SIGNATURE----- --Sig_/jmmr8z2E+jxWsD9impDX8+=-- From owner-freebsd-fs@FreeBSD.ORG Mon May 3 17:52:00 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 93468106566B for ; Mon, 3 May 2010 17:52:00 +0000 (UTC) (envelope-from josh@multipart-mixed.com) Received: from joshcarter.com (67-207-137-80.slicehost.net [67.207.137.80]) by mx1.freebsd.org (Postfix) with ESMTP id 7427C8FC0C for ; Mon, 3 May 2010 17:52:00 +0000 (UTC) Received: from [192.168.4.134] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) by joshcarter.com (Postfix) with ESMTPSA id DA0E91C003; Mon, 3 May 2010 17:51:59 +0000 (UTC) Message-Id: <623C8EAA-1AA6-4293-8A72-C8875E3D615B@multipart-mixed.com> From: Josh Carter To: Hussain Ali , freebsd-fs@freebsd.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 3 May 2010 11:51:57 -0600 References: X-Mailer: Apple Mail (2.936) Cc: Subject: Re: Commercial FreeBSD ZFS implementatoin 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, 03 May 2010 17:52:00 -0000 Hi all, That should read, Spectra Logic is working with ZFS on FreeBSD. We have a couple FreeBSD committers working here but our efforts have lately been focused more on Xen stability, most of which we've submitted back to the project already. We'll turn our attention soon to the storage side. Anything we do with ZFS will be working *with* PJD, Kip, and other members of the community -- we're not looking to do our own port. Best regards, Josh On May 3, 2010, at 4:55 AM, Hussain Ali wrote: > Hi, > > I just read this article: http://tinyurl.com/39do89u was wondering > if anyone had any insight into the following quote: > > ' I'm therefore glad to say that SpectraLogic is working on a port > of ZFS to FreeBSD.' > > > -- > -hussain > > This message may contain confidential or privileged information. If > you are not the intended recipient, please advise us immediately and > delete this message. See http://www.datapipe.com/about-us-legal-email-disclaimer.htm > for further information on confidentiality and the risks of non- > secure electronic communication. If you cannot access these links, > please notify us by reply message and we will send the contents to > you. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Mon May 3 18:19:57 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A9291065674 for ; Mon, 3 May 2010 18:19:57 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id 0E0B88FC12 for ; Mon, 3 May 2010 18:19:56 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id l26so896639fgb.13 for ; Mon, 03 May 2010 11:19:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:to:subject:organization:from :date:message-id:user-agent:mime-version:content-type; bh=cSAL4towBMRdCk/XxVDJK5yBfAIr59CwZVEiai0sLbE=; b=QJv/IDGTbFeZDtmtdTCIpqm5TyyhtMcmD85gnRf/riE9aSA5ntT5APtkb5kQvamn62 7NzPE1LG7KLxXZRSDl5Jn5k7HAN/QiTJ38GuibqqBfdp1GQyNI9qG5vwWm6fBF+nU8Qe lUVvDveLYETa62YxOuw+LzAJmUFyfRMP7+0l8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=to:subject:organization:from:date:message-id:user-agent :mime-version:content-type; b=GI0NvsQTuPazYIA3MrPrRnXsrAhiHic95G+TBthOMJ8Ef06oqItAzZW3p2/zvo0D9d 8TZJukUGISIIyfHr+q2YgcAwO1gvpIxHLFZFRMMtfIDx6EW0GkDJOd1LtKzXFY7NgHOM b77ky3GH4GFOcPoLJ32wB4QwFnMcAFI3/bo7U= Received: by 10.87.5.30 with SMTP id h30mr10979605fgi.3.1272910795956; Mon, 03 May 2010 11:19:55 -0700 (PDT) Received: from localhost ([95.69.170.5]) by mx.google.com with ESMTPS id 12sm8738976fgg.14.2010.05.03.11.19.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 03 May 2010 11:19:55 -0700 (PDT) To: freebsd-fs@FreeBSD.org Organization: Home From: Mikolaj Golub Date: Mon, 03 May 2010 21:19:52 +0300 Message-ID: <86bpcwluev.fsf@kopusha.onet> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: SUJ: fsck_ufs: Sparse journal inode 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, 03 May 2010 18:19:57 -0000 Hi, Experimenting with journaled soft-updates on HAST I observed the error when fscking fs on the secondary after primary "crash": # fsck -y -t ufs /dev/hast/tank ** /dev/hast/tank USE JOURNAL?? yes ** SU+J Recovering /dev/hast/tank ** Reading 33554384 byte journal from inode 4. fsck_ufs: Sparse journal inode 4 (blocks = 16376, numfrags = 16383). (The text between the parentheses is a local modification to the fsck code to output some useful values). So to recover I needed to run fsck and type "no" when prompted "USE JOURNAL?". But I am looking for a way to script automatic recovering from this situation. Currently the only way I have found is to disable journal, run fsck, mount fs somewhere temporary, remove .sujournal, unmount, enable journal. Is this really so complicated or may I just miss something? BTW, I used to observe this error on every "crash" test. And "blocks" value was always the same: 16376. So I changed journal size to 16376 * 2048 = 33538048. It looks like after this the issue has gone. -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Mon May 3 23:28:05 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3F7B3106566B for ; Mon, 3 May 2010 23:28:05 +0000 (UTC) (envelope-from rabe@uugrn.org) Received: from mail.uugrn.org (mail.uugrn.org [195.49.138.123]) by mx1.freebsd.org (Postfix) with ESMTP id BF1708FC0A for ; Mon, 3 May 2010 23:28:04 +0000 (UTC) Received: from rabe.uugrn.org (root@rabe.uugrn.org [195.49.138.102]) by mail.uugrn.org (8.14.3/8.14.3) with ESMTP id o43N8jCw085613 for ; Tue, 4 May 2010 01:08:55 +0200 (CEST) (envelope-from rabe@uugrn.org) Received: from daemon.ma.sigsys.de (rabe@rabe.uugrn.org [195.49.138.102]) by rabe.uugrn.org (8.14.3/8.13.8) with ESMTP id o43N8ie5085609 for ; Tue, 4 May 2010 01:08:44 +0200 (CEST) (envelope-from rabe@uugrn.org) Received: from daemon.ma.sigsys.de (localhost [127.0.0.1]) by daemon.ma.sigsys.de (8.14.3/8.14.3) with ESMTP id o43N6p9G023379 for ; Tue, 4 May 2010 01:06:51 +0200 (CEST) (envelope-from rabe@uugrn.org) Received: (from rabe@localhost) by daemon.ma.sigsys.de (8.14.3/8.14.3/Submit) id o43N6pl9023378 for freebsd-fs@freebsd.org; Tue, 4 May 2010 01:06:51 +0200 (CEST) (envelope-from rabe@uugrn.org) X-Authentication-Warning: daemon.ma.sigsys.de: rabe set sender to rabe@uugrn.org using -f Date: Tue, 4 May 2010 01:06:51 +0200 From: Raphael Becker To: freebsd-fs@freebsd.org Message-ID: <20100503230651.GH2763@ma.sigsys.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gTtJ75FAzB1T2CN6" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: Re: ZFS raidz and 4k sector disks 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, 03 May 2010 23:28:05 -0000 --gTtJ75FAzB1T2CN6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi *, On Thu, Apr 08, 2010 at 05:55:33PM +0400, Alexey Tarasov wrote: > I've tried all methods and realized that unfortunately the only working m= ethod is gnop. So you can't use these disks for ZFS at all now. I'm planning to buy two 2-TB-drives for ZFS with FreeBSD 8.0. I don't know about the sector size of this drives, but lets assume 4k I there any documented and recommend way to get 4k-drives working with=20 ZFS with *good* performance? Do we need a workaround here or is updating to a latest -STABLE a solution here?=20 TIA Raphael Becker --=20 Raphael Becker http://rabe.uugrn.org/ https://www.xing.com/profile/Raphael_Becker GnuPG: E7B2 1D66 3AF2 EDC7 9828 6D7A 9CDA 3E7B 10CA 9F2D =2E........|.........|.........|.........|.........|.........|.........|.. --gTtJ75FAzB1T2CN6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvfVwsACgkQnNo+exDKny05SwCffiejbql00TmPA/bbKEk9bpJF 8jUAn1cLfBF4wRAFjZKb8GDmsRJ9hkXp =JwK3 -----END PGP SIGNATURE----- --gTtJ75FAzB1T2CN6-- From owner-freebsd-fs@FreeBSD.ORG Mon May 3 23:30:04 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53C6A106564A for ; Mon, 3 May 2010 23:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 2663E8FC12 for ; Mon, 3 May 2010 23:30:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o43NU36P020634 for ; Mon, 3 May 2010 23:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o43NU3GM020629; Mon, 3 May 2010 23:30:03 GMT (envelope-from gnats) Date: Mon, 3 May 2010 23:30:03 GMT Message-Id: <201005032330.o43NU3GM020629@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Alex Bakhtin Cc: Subject: Re: kern/145339: [zfs] deadlock after detaching block device from raidz pool X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Bakhtin List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 May 2010 23:30:04 -0000 The following reply was made to PR kern/145339; it has been noted by GNATS. From: Alex Bakhtin To: Andriy Gapon Cc: bug-followup@freebsd.org, Pawel Jakub Dawidek Subject: Re: kern/145339: [zfs] deadlock after detaching block device from raidz pool Date: Tue, 4 May 2010 03:23:35 +0400 Andriy, Upgraded to today's stable. Reproduced the problem. On GENERIC the system just hangs with the following output: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D ad12: FAILURE - WRITE_DMA48 status=3D7f error=3D0 LBA=3D2312588250^ Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0x48 fault code =3D supervisor write data, page not present instruction pointer =3D 0x20:0xffffffff80593e95 stack pointer =3D 0x28:0xffffff8000065ba0 frame pointer =3D 0x28:0xffffff8000065bb0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 3 (g_up) trap number =3D 12 panic: page fault cpuid =3D 1 Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x0 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80545a28 stack pointer =3D 0x28:0xffffff80eada2a40 frame pointer =3D 0x28:0xffffff80eada2a90 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (spa_zio) trap number =3D 12 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D With GENERIG + DDB/KDB enabled I got the following (it seems that first time I detached the device when there was no active transaction - can try to reproduce): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D ad12: FAILURE - device detached Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0x48 fault code =3D supervisor write data, page not present instruction pointer =3D 0x20:0xffffffff805a0345 Fatal double fault stack pointer =3D 0x28:0xffffff800006aba0 rip =3D 0xffffffff808085ad frame pointer =3D 0x28:0xffffff800006abb0 rsp =3D 0xffffff80ead87000 code segment =3D base 0x0, limit 0xfffff, type 0x1b rbp =3D 0xffffff80ead87070 =3D DPL 0, pres 1, long 1, def32 0, gran 1 cpuid =3D 0; processor eflags =3D apic id =3D 00 interrupt enabled, panic: double fault resume, cpuid =3D 0 IOPL =3D 0 KDB: enter: panic c[thread pid 0 tid 100113 ] Stopped at kdb_enter+0x3d: movq $0,0x69cee0(%rip) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D And another one =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D ad12: FAILURE - WRITE_DMA status=3D7f error=3D0 LBA=3D111033498^M ^M ^M Fatal trap 12: page fault while in kernel mode^M cpuid =3D 1; apic id =3D 01^M fault virtual address =3D 0x48^M fault code =3D supervisor write data, page not present^M instruction pointer =3D 0x20:0xffffffff805a0345^M stack pointer =3D 0x28:0xffffff800006aba0^M frame pointer =3D 0x28:0xffffff800006abb0^M code segment =3D base 0x0, limit 0xfffff, type 0x1b^M =3D DPL 0, pres 1, long 1, def32 0, gran 1^M processor eflags =3D interrupt enabled, resume, IOPL =3D 0^M current process =3D 3 (g_up)^M [thread pid 3 tid 100011 ] Stopped at _mtx_lock_flags+0x15: lock cmpxchgq %rsi,0x18(%rdi) db:0:kdb.enter.default> capture on =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D And with your patch the system doesn't detect that device is detached and seems to be dead-locked (doesn't respond to power-button): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D acpi0: suspend request ignored (not ready yet) acpi0: request to enter state S5 failed (err 6) acpi0: suspend request ignored (not ready yet) acpi0: request to enter state S5 failed (err 6) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D So, I can still easily reproduce this problem on 8-STABLE. Your simple patch helps to avoid page fault but dead-locks the system. Are you sure that you can just return at this point? Probably it make sense to set some error flag before return? Alex Bakhtin 2010/4/23 Andriy Gapon : > > Can you try this patch? > > --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_geom.c > +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_geom.c > @@ -603,6 +603,9 @@ vdev_geom_io_intr(struct bio *bp) > =A0 =A0 =A0 =A0zio =3D bp->bio_caller1; > =A0 =A0 =A0 =A0ctx =3D zio->io_vd->vdev_tsd; > > + =A0 =A0 =A0 if (ctx =3D=3D NULL) > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 return; > + > =A0 =A0 =A0 =A0if ((zio->io_error =3D bp->bio_error) =3D=3D 0 && bp->bio_= resid !=3D 0) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0zio->io_error =3D EIO; > > > -- > Andriy Gapon > From owner-freebsd-fs@FreeBSD.ORG Mon May 3 23:33:31 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 673441065678 for ; Mon, 3 May 2010 23:33:31 +0000 (UTC) (envelope-from Lassi.Tuura@cern.ch) Received: from CERNMX31.cern.ch (cernmx31.cern.ch [137.138.144.179]) by mx1.freebsd.org (Postfix) with ESMTP id 0422F8FC21 for ; Mon, 3 May 2010 23:33:30 +0000 (UTC) Received: from cernfe10.cern.ch (137.138.140.34) by cernmxgwlb2.cern.ch (137.138.144.179) with Microsoft SMTP Server (TLS) id 14.0.639.21; Tue, 4 May 2010 01:22:36 +0200 Received: from pb-d-128-141-134-74.cern.ch (128.141.134.74) by smtp.cern.ch (137.138.140.59) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 4 May 2010 01:22:35 +0200 From: Lassi Tuura Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 4 May 2010 01:22:35 +0200 Message-ID: <4529AF96-4BFF-4424-B77F-FE5BC8AE43D3@cern.ch> To: MIME-Version: 1.0 (Apple Message framework v1078) X-Mailer: Apple Mail (2.1078) Keywords: CERN SpamKiller Note: -50 Subject: Instant crash with ZFS + iozone? 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, 03 May 2010 23:33:31 -0000 Hi, I've just started playing with FreeBSD and ZFS. I installed 8.0-RELEASE, then 8.0-STABLE 201004 (amd64) on a system with = 4 * 1TB hard drives for ZFS (2 * Hitachi Deskstar 7K2000, 2 * Samsung = SpinPoint F3), plus 2GB IDE flash for OS itself (Transcend), 4GB ECC = RAM, AMD Athlon II X2 235e CPU, Asus M4A78L-M LE motherboard. I can use the basic system fine. However when I create a ZFS volume out = of the 4 disks and run iozone on it, the system will reliably die within = 5 seconds or so, sometimes it takes a little longer, up to a minute or = so. By "die" I mean the screen goes completely blank, and it will no longer = respond to anything - no network, not even ping and any existing network = connections will die, no keyboard, screen totally black without as much = as a cursor... nothing. The soft power button won't work either. AFAIK = the only thing that works is the reset button. When the system comes back, /var/log is silent on last 30 seconds = preceding the crash. The same thing occurs with drives in ATA and = SATA/AHCI mode in BIOS, with or without "ahci_load=3D"YES"" in = /boot/loader.conf. So my first question as a FreeBSD newbie is: how do I get to see why = this happens? It could be some simple hardware conflict, but how do I = get the system to tell me what is wrong? Without even a panic message on = screen I am a bit lost... If I get a serial-to-usb cable and send = console there, would I see more? I don't currently configure a swap = device; would that help to get a crash dump? As far as I can tell, this is not caused by ZFS ARC. When I manage to = run arcstats.pl and the system runs long enough, ARC size remains = tolerable (~1GB) as long as I get output on screen. I did do the ZFS = tuning guide's config in /boot/loader.conf, but it doesn't change = anything. So far I am assuming some bad hardware interaction = somewhere... Regards, Lassi= From owner-freebsd-fs@FreeBSD.ORG Tue May 4 00:49:08 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99DBD106566B for ; Tue, 4 May 2010 00:49:08 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by mx1.freebsd.org (Postfix) with ESMTP id 49FC98FC18 for ; Tue, 4 May 2010 00:49:07 +0000 (UTC) Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by QMTA11.westchester.pa.mail.comcast.net with comcast id CyTL1e0021uE5Es5BCp86F; Tue, 04 May 2010 00:49:08 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta16.westchester.pa.mail.comcast.net with comcast id DCp71e0043S48mS3cCp72n; Tue, 04 May 2010 00:49:08 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id B07769B425; Mon, 3 May 2010 17:49:05 -0700 (PDT) Date: Mon, 3 May 2010 17:49:05 -0700 From: Jeremy Chadwick To: Lassi Tuura Message-ID: <20100504004905.GA12233@icarus.home.lan> References: <4529AF96-4BFF-4424-B77F-FE5BC8AE43D3@cern.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4529AF96-4BFF-4424-B77F-FE5BC8AE43D3@cern.ch> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: Instant crash with ZFS + iozone? 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, 04 May 2010 00:49:08 -0000 On Tue, May 04, 2010 at 01:22:35AM +0200, Lassi Tuura wrote: > I installed 8.0-RELEASE, then 8.0-STABLE 201004 (amd64) on a system > with 4 * 1TB hard drives for ZFS (2 * Hitachi Deskstar 7K2000, 2 * > Samsung SpinPoint F3), plus 2GB IDE flash for OS itself (Transcend), > 4GB ECC RAM, AMD Athlon II X2 235e CPU, Asus M4A78L-M LE motherboard. > > I can use the basic system fine. However when I create a ZFS volume > out of the 4 disks and run iozone on it, the system will reliably die > within 5 seconds or so, sometimes it takes a little longer, up to a > minute or so. > > By "die" I mean the screen goes completely blank, and it will no > longer respond to anything - no network, not even ping and any > existing network connections will die, no keyboard, screen totally > black without as much as a cursor... nothing. The soft power button > won't work either. AFAIK the only thing that works is the reset > button. This sounds like a hardware problem to me -- particularly excessive draw on the PSU, voltage issues, or other whatnots. Especially if the screen goes black (no cursor, monitor not in power save mode) and requires a hard reset. Possibly the problem is only witnessed under extreme disk I/O combined with high CPU usage + memory I/O. You might try removing some disks (drop it from 4 down to 2 and use a ZFS mirror) and see if you can reproduce the problem. If it doesn't happen with 2 disks then my guess is what I described in the 1st paragraph. I would then advise trying to find a hardware stress test environment of some sort (Linux may provide something like this; bootable CD which beats on all the hardware simultaneously) and running it through that. Windows has quite a few suites that do this as well. Otherwise, replace the mainboard and/or PSU (try one at a time) and see what happens. If it is indeed a hardware problem, expect to spend time and money trying to track down the root cause -- there's no easy way otherwise. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue May 4 08:13:42 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A40731065670 for ; Tue, 4 May 2010 08:13:42 +0000 (UTC) (envelope-from yuwen@exodus.cs.ccu.edu.tw) Received: from se5.mail2000.com.tw (se5.mail2000.com.tw [203.69.82.95]) by mx1.freebsd.org (Postfix) with SMTP id 845998FC23 for ; Tue, 4 May 2010 08:13:41 +0000 (UTC) Received: from 10.0.0.83 by mx6.mail2000.com.tw with Mail2000 ESMTP Server V3.20M(211:0:AUTH_RELAY) (envelope-from ); Tue, 04 May 2010 16:13:33 +0800 (CST) Received: from 10.0.0.47 by bak3.mail2000.com.tw with Mail2000 ESMTP Server V4.50S(11790:0:AUTH_LOGIN) (envelope-from ); Tue, 04 May 2010 16:01:03 +0800 (CST) Received: By OpenMail Mailer;Tue, 04 May 2010 16:01:00 +0800 (CST) From: "Cheng-Lin Yang" Message-ID: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> To: "freebsd-fs" Date: Tue, 04 May 2010 16:01:00 +0800 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: quoted-printable Cc: lab Subject: Struggling on NFS problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuwen@exodus.cs.ccu.edu.tw List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2010 08:13:42 -0000 Dear=20all, Currently,=20we=20have=20a=20NFS=20server=20which=20runs=20FreeBSD8=20with=20= ZFS=20and=20few=20workstations=20as=20NFS=20client=20(2=20*=20FreeBSD8=20amd= 64=20+=201=20*=20FreeBSD7.2=20i386=20+=202=20*=20Fedora=20+=20Debian).=20We=20= spotted=20that=20NFS=20performs=20weirdly=20on=20FreeBSD=20clients,=20which=20= will=20significantly=20slow=20down=20the=20system=20response.=20The=20only=20= solution=20to=20it=20is=20to=20reboot=20the=20clients=20(Linux=20client=20ru= ns=20smoothly).=20So=20we=20try=20to=20use=20"nfsstat=20-c"=20on=20FreeBSD=20= client=20to=20dig=20into=20the=20problem=20and=20found=20strange=20result=20= (http://pastebin.com/K71qpEDG)=20: csie0[~]#=20nfsstat=20-c Client=20Info: Rpc=20Counts: =20=20Getattr=20=20=20Setattr=20=20=20=20Lookup=20=20Readlink=20=20=20=20=20= =20Read=20=20=20=20=20Write=20=20=20=20Create=20=20=20=20Remove =20=203595047=20=20=20=20=2075100=20=20=201089213=20=20=20=20=20=201095=20=20= =201258311=20=2048664374=20=20=20=20104346=20=20=20=20116376 =20=20=20Rename=20=20=20=20=20=20Link=20=20=20Symlink=20=20=20=20=20Mkdir=20= =20=20=20=20Rmdir=20=20=20Readdir=20=20RdirPlus=20=20=20=20Access =20=20=20=2017621=20=20=20=20=20=201644=20=20=20=20=20=20=20=2077=20=20=20=20= =2019569=20=20=20=20=20=209459=20=20=20=20=2045177=20=20=20=20=20=20=20=20=20= 0=20=20=20=20323665 =20=20=20=20Mknod=20=20=20=20Fsstat=20=20=20=20Fsinfo=20=20PathConf=20=20=20= =20Commit =20=20=20=20=20=20=20=200=20=20=20=20111262=20=20=20=20=20=20=20=20=203=20=20= =20=20=20=20=20=20=200=20=20=20=20590876 Rpc=20Info: =20TimedOut=20=20=20Invalid=20X=20Replies=20=20=20Retries=20=20Requests =20=20=20=20=20=20=20=200=20=20=20=20=20=20=20=20=200=20=20=20=20=20=20=20=20= =200=20=20=20=20=20=20=20=20=200=20=2056022746 Cache=20Info: Attr=20Hits=20=20=20=20Misses=20Lkup=20Hits=20=20=20=20Misses=20BioR=20Hits=20= =20=20=20Misses=20BioW=20Hits=20=20=20=20Misses 198414412=20=20=203595052=20112100649=20=20=201088903=20=2062793893=20=20=20= 1253320=20=20-1008715=20=2048664379 BioRLHits=20=20=20=20Misses=20BioD=20Hits=20=20=20=20Misses=20DirE=20Hits=20= =20=20=20Misses =20=20=20=20=203751=20=20=20=20=20=201095=20=20=20=20204326=20=20=20=20=2045= 191=20=20=20=20109194=20=20=20=20=20=20=20=20=208 As=20you=20can=20see,=20the=20value=20of=20"BioW=20Hits"=20is=20a=20negative= =20number.=20Shouldn't=20it=20be=20equal=20or=20larger=20than=20zero?=20We=20= have=20totally=20no=20idea=20on=20this=20issue.=20Please=20kindly=20help=20u= s=20on=20investigating=20the=20problem.=20Any=20suggestion=20is=20extremely=20= welcomed.=20Thank=20you. Regards, George From owner-freebsd-fs@FreeBSD.ORG Tue May 4 08:26:37 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 449061065672 for ; Tue, 4 May 2010 08:26:37 +0000 (UTC) (envelope-from erich@fuujingroup.com) Received: from fluorine.fuujinnetworks.com (fluorine.fuujinnetworks.com [64.90.67.234]) by mx1.freebsd.org (Postfix) with ESMTP id 1FF3E8FC13 for ; Tue, 4 May 2010 08:26:36 +0000 (UTC) Received: from [10.168.1.8] (copper.fuujinnetworks.com [64.90.67.254]) by fluorine.fuujinnetworks.com (Postfix) with ESMTPA id 160F6439E38; Tue, 4 May 2010 03:27:00 -0500 (CDT) Message-ID: <4BDFE843.7050600@fuujingroup.com> Date: Tue, 04 May 2010 03:26:27 -0600 From: "Erich Jenkins, Fuujin Group Ltd" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: yuwen@exodus.cs.ccu.edu.tw References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> In-Reply-To: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: 7bit Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem 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, 04 May 2010 08:26:37 -0000 Cheng-Lin Yang wrote: > Dear all, > Currently, we have a NFS server which runs FreeBSD8 with ZFS and few workstations as NFS client (2 * FreeBSD8 amd64 + 1 * FreeBSD7.2 i386 + 2 * Fedora + Debian). We spotted that NFS performs weirdly on FreeBSD clients, which will significantly slow down the system response. The only solution to it is to reboot the clients (Linux client runs smoothly). So we try to use "nfsstat -c" on FreeBSD client to dig into the problem and found strange result (http://pastebin.com/K71qpEDG) : > csie0[~]# nfsstat -c > Client Info: > Rpc Counts: > Getattr Setattr Lookup Readlink Read Write Create Remove > 3595047 75100 1089213 1095 1258311 48664374 104346 116376 > Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access > 17621 1644 77 19569 9459 45177 0 323665 > Mknod Fsstat Fsinfo PathConf Commit > 0 111262 3 0 590876 > Rpc Info: > TimedOut Invalid X Replies Retries Requests > 0 0 0 0 56022746 > Cache Info: > Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses > 198414412 3595052 112100649 1088903 62793893 1253320 -1008715 48664379 > BioRLHits Misses BioD Hits Misses DirE Hits Misses > 3751 1095 204326 45191 109194 8 > > As you can see, the value of "BioW Hits" is a negative number. Shouldn't it be equal or larger than zero? We have totally no idea on this issue. Please kindly help us on investigating the problem. Any suggestion is extremely welcomed. Thank you. > > Regards, > George > _______________________________________________ > 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" Cheng-Lin Could you provide a bit more info about your system and setup? How much RAM, what type of raidz config? Do you have a separate ZIL device like a solid state drive? Often, you'll experience severe NFS performance degradation when using raidz and nfs if the zil logs are on the same drives as the raidz volume. Erich M. Jenkins Fuujin Group Limited "You should never, never doubt what no one is sure about." -- Gene Wilder From owner-freebsd-fs@FreeBSD.ORG Tue May 4 08:34:34 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8CF84106566C for ; Tue, 4 May 2010 08:34:34 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 76E1D8FC0A for ; Tue, 4 May 2010 08:34:34 +0000 (UTC) Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta10.emeryville.ca.mail.comcast.net with comcast id DLaa1e0031afHeLAALaaAn; Tue, 04 May 2010 08:34:34 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta17.emeryville.ca.mail.comcast.net with comcast id DLaY1e0053S48mS8dLaYUD; Tue, 04 May 2010 08:34:34 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 1A6B39B425; Tue, 4 May 2010 01:34:31 -0700 (PDT) Date: Tue, 4 May 2010 01:34:31 -0700 From: Jeremy Chadwick To: Cheng-Lin Yang Message-ID: <20100504083431.GA23784@icarus.home.lan> References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem 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, 04 May 2010 08:34:34 -0000 On Tue, May 04, 2010 at 04:01:00PM +0800, Cheng-Lin Yang wrote: > Dear all, > Currently, we have a NFS server which runs FreeBSD8 ... Can you please provide "uname -a" output? -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue May 4 10:22:04 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C14091065673 for ; Tue, 4 May 2010 10:22:04 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 540A98FC18 for ; Tue, 4 May 2010 10:22:03 +0000 (UTC) Received: by wyb36 with SMTP id 36so2589841wyb.13 for ; Tue, 04 May 2010 03:21:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=+ta5CVCkYC3uyzpLHTXFcr8xkA6p8GY1kXdIbSR/uIs=; b=MBQh8NBy7PA6YyWG7yOgcjzp/zxXTI8+Lq7d8CLR20+TIEjsXZa/cEtwqo9J2/L5y1 nyF+HtYm/031J0ZoQ4FvG9W5GsVnNU1DvMbLCZNGft+AIPyHGkZjACWqwwzZFgRNC5CE gJkMhZgzyPXcoxXwewAUmb3afieLAd2Lvo2fM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=ETO4uBYplOe136k50ILcM6qN8tpk9U50TcpgYTm/wLqepEWDQ+DMFpwM8HAPheITqI 3gi381Twp4nInd9PKwWIV+egIP/UxmyNQd/e24mRQs9pbem22yQ72PJQd3gxn7qiilQX eV2v/anqIFdeP6mEUhhTIAwPCuc391UKg/l48= Received: by 10.227.142.13 with SMTP id o13mr945225wbu.71.1272968515721; Tue, 04 May 2010 03:21:55 -0700 (PDT) Received: from [192.168.2.5] (5ED0B7FD.cable.ziggo.nl [94.208.183.253]) by mx.google.com with ESMTPS id b2sm42459547wbb.14.2010.05.04.03.21.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 04 May 2010 03:21:54 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Matthias In-Reply-To: <20100503230651.GH2763@ma.sigsys.de> Date: Tue, 4 May 2010 12:21:53 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20100503230651.GH2763@ma.sigsys.de> To: Raphael Becker X-Mailer: Apple Mail (2.1078) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS raidz and 4k sector disks 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, 04 May 2010 10:22:04 -0000 Right now only WD uses 4k. There are still other manufacturers who = supply old-style 2TB drives. =20 On 4 mei 2010, at 01:06, Raphael Becker wrote: > Hi *, >=20 > On Thu, Apr 08, 2010 at 05:55:33PM +0400, Alexey Tarasov wrote: >> I've tried all methods and realized that unfortunately the only = working method is gnop. So you can't use these disks for ZFS at all now. >=20 > I'm planning to buy two 2-TB-drives for ZFS with FreeBSD 8.0. > I don't know about the sector size of this drives, but lets assume 4k >=20 > I there any documented and recommend way to get 4k-drives working with=20= > ZFS with *good* performance? Do we need a workaround here or is = updating > to a latest -STABLE a solution here?=20 >=20 > TIA > Raphael Becker >=20 > --=20 > Raphael Becker = http://rabe.uugrn.org/ > = https://www.xing.com/profile/Raphael_Becker > GnuPG: E7B2 1D66 3AF2 EDC7 9828 6D7A 9CDA 3E7B 10CA = 9F2D > = .........|.........|.........|.........|.........|.........|.........|.. From owner-freebsd-fs@FreeBSD.ORG Tue May 4 10:58:16 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F9E9106564A; Tue, 4 May 2010 10:58:16 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4619F8FC16; Tue, 4 May 2010 10:58:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44AwGnE049924; Tue, 4 May 2010 10:58:16 GMT (envelope-from mm@freefall.freebsd.org) Received: (from mm@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44AwG0b049920; Tue, 4 May 2010 10:58:16 GMT (envelope-from mm) Date: Tue, 4 May 2010 10:58:16 GMT Message-Id: <201005041058.o44AwG0b049920@freefall.freebsd.org> To: mm@FreeBSD.org, mm@FreeBSD.org, freebsd-fs@FreeBSD.org From: mm@FreeBSD.org Cc: Subject: Re: kern/145424: [zfs] [patch] move source closer to v15 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, 04 May 2010 10:58:16 -0000 Synopsis: [zfs] [patch] move source closer to v15 State-Changed-From-To: open->suspended State-Changed-By: mm State-Changed-When: Tue May 4 10:57:27 UTC 2010 State-Changed-Why: Suspending due to possible risk and upcoming v24 progress. http://www.freebsd.org/cgi/query-pr.cgi?pr=145424 From owner-freebsd-fs@FreeBSD.ORG Tue May 4 12:28:06 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3B206106566C for ; Tue, 4 May 2010 12:28:06 +0000 (UTC) (envelope-from me@lexasoft.ru) Received: from relay.wahome.ru (relay.wahome.ru [95.211.21.141]) by mx1.freebsd.org (Postfix) with ESMTP id 046028FC14 for ; Tue, 4 May 2010 12:28:04 +0000 (UTC) Received: from mmx.lexasoft.ru (mmx.lexasoft.ru [92.241.160.6]) by relay.wahome.ru (Postfix) with ESMTP id 6ACFE6B194C; Tue, 4 May 2010 16:24:59 +0400 (MSD) Received: from [92.241.160.200] (unknown [92.241.160.200]) by mmx.lexasoft.ru (Postfix) with ESMTPSA id 9A95928490; Tue, 4 May 2010 16:28:02 +0400 (MSD) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=utf-8 From: Alexey Tarasov In-Reply-To: <20100503230651.GH2763@ma.sigsys.de> Date: Tue, 4 May 2010 16:28:01 +0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20100503230651.GH2763@ma.sigsys.de> To: Raphael Becker , freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.1078) Cc: Subject: Re: ZFS raidz and 4k sector disks 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, 04 May 2010 12:28:06 -0000 On 04.05.2010, at 3:06, Raphael Becker wrote: > I'm planning to buy two 2-TB-drives for ZFS with FreeBSD 8.0. > I don't know about the sector size of this drives, but lets assume 4k >=20 > I there any documented and recommend way to get 4k-drives working with=20= > ZFS with *good* performance? Do we need a workaround here or is = updating > to a latest -STABLE a solution here?=20 If the disk exposes to OS right sector size, ZFS works good with it. = Proved on gnop+zfs over fake 512 drives (WD15-EARS). >=20 > TIA > Raphael Becker >=20 > --=20 > Raphael Becker = http://rabe.uugrn.org/ > = https://www.xing.com/profile/Raphael_Becker > GnuPG: E7B2 1D66 3AF2 EDC7 9828 6D7A 9CDA 3E7B 10CA = 9F2D > = .........|.........|.........|.........|.........|.........|.........|.. -- Alexey Tarasov (\__/)=20 (=3D'.'=3D)=20 E[: | | | | :]=D0=97=20 (")_(") From owner-freebsd-fs@FreeBSD.ORG Tue May 4 14:19:25 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ABE091065674 for ; Tue, 4 May 2010 14:19:25 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 612A18FC20 for ; Tue, 4 May 2010 14:19:25 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEADvJ30uDaFvK/2dsb2JhbACdMXG8M4UTBI88 X-IronPort-AV: E=Sophos;i="4.52,327,1270440000"; d="scan'208";a="74767559" Received: from fraser.cs.uoguelph.ca ([131.104.91.202]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 04 May 2010 10:19:24 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 56BD6109C318; Tue, 4 May 2010 10:19:24 -0400 (EDT) X-Virus-Scanned: amavisd-new at fraser.cs.uoguelph.ca Received: from fraser.cs.uoguelph.ca ([127.0.0.1]) by localhost (fraser.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zh7eoXHBkqUd; Tue, 4 May 2010 10:19:23 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 94F35109C30C; Tue, 4 May 2010 10:19:23 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o44EY2916756; Tue, 4 May 2010 10:34:03 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 4 May 2010 10:34:02 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Cheng-Lin Yang In-Reply-To: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> Message-ID: References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem 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, 04 May 2010 14:19:25 -0000 On Tue, 4 May 2010, Cheng-Lin Yang wrote: > Dear all, > Currently, we have a NFS server which runs FreeBSD8 with ZFS and few workstations as NFS client (2 * FreeBSD8 amd64 + 1 * FreeBSD7.2 i386 + 2 * Fedora + Debian). We spotted that NFS performs weirdly on FreeBSD clients, which will significantly slow down the system response. The only solution to it is to reboot the clients (Linux client runs smoothly). So we try to use "nfsstat -c" on FreeBSD client to dig into the problem and found strange result (http://pastebin.com/K71qpEDG) : > csie0[~]# nfsstat -c [stuff snipped] > > As you can see, the value of "BioW Hits" is a negative number. Shouldn't it be equal or larger than zero? We have totally no idea on this issue. Please kindly help us on investigating the problem. Any suggestion is extremely welcomed. Thank you. > I suspect that the negative value is just a wrap around (assuming you're on a 32bit arch) and hust means lottsa hits. If that is the case, it suggests a fairly heavy write load, which can be an issue for servers using ZFS (as others have already posted about). There are a # of patches for FreeBSD8.0 related to NFS (one specifically w.r.t. the server using ZFS) at: http://people.freebsd.org/~rmacklem If you are using FreeBSD8.0 for the server, it would be worth trying these patches (they are all independent, in that any of them can be applied, in any order). (If you are using a recent stable/8, then you should already have the patches.) In particular, one of them fixes a case where FreeBSD clients will get stuck looping trying to access a file after it has been deleted on the server, because the server reported EIO instead of ESTALE for this case. If the patches don't help, please try to collect more information from both the slow clients and server. "ps axl" on them all can be useful. Also, you can use "tcpdump -s 0 -w host " to capture traffic between the slow client and server which can be looked at via wireshark. (tcpdump doesn't decode NFS traffic well, but a binary capture from tcpdump goes into wireshark ok and it does understand NFS traffic) If you get to this point, you can email me the "" as an attachment and I can take a look at it. If you look at it, one scenario that is of interest is where the client just keeps retrying the same NFS RPC. Good luck with it and let us know how it goes, rick From owner-freebsd-fs@FreeBSD.ORG Tue May 4 14:41:18 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7D6F91065670 for ; Tue, 4 May 2010 14:41:18 +0000 (UTC) (envelope-from josh@multipart-mixed.com) Received: from joshcarter.com (67-207-137-80.slicehost.net [67.207.137.80]) by mx1.freebsd.org (Postfix) with ESMTP id 5F8AC8FC16 for ; Tue, 4 May 2010 14:41:18 +0000 (UTC) Received: from [192.168.4.129] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) by joshcarter.com (Postfix) with ESMTPSA id C8A1512804A for ; Tue, 4 May 2010 14:41:17 +0000 (UTC) Message-Id: From: Josh Carter To: freebsd-fs@freebsd.org In-Reply-To: <4529AF96-4BFF-4424-B77F-FE5BC8AE43D3@cern.ch> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 4 May 2010 08:41:16 -0600 References: <4529AF96-4BFF-4424-B77F-FE5BC8AE43D3@cern.ch> X-Mailer: Apple Mail (2.936) Subject: Re: Instant crash with ZFS + iozone? 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, 04 May 2010 14:41:18 -0000 Tangental note re iozone on FreeBSD's ZFS, if you run it as a normal user (not root) you'll see iozone exit prematurely with a message to the effect of "filesystem is not sane." This is due to an issue with checking permissions on a ftruncate, it's a bug that I'll hopefully get time to poke at myself if someone doesn't beat me to it. In the meantime, run iozone as root. (However that doesn't help Lassi, just FYI for others.) -Josh On May 3, 2010, at 5:22 PM, Lassi Tuura wrote: > I can use the basic system fine. However when I create a ZFS volume > out of the 4 disks and run iozone on it, the system will reliably > die within 5 seconds or so, sometimes it takes a little longer, up > to a minute or so. From owner-freebsd-fs@FreeBSD.ORG Tue May 4 15:58:54 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3D611106566B; Tue, 4 May 2010 15:58:54 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 150028FC08; Tue, 4 May 2010 15:58:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44FwrOi015258; Tue, 4 May 2010 15:58:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44FwrgB015254; Tue, 4 May 2010 15:58:53 GMT (envelope-from linimon) Date: Tue, 4 May 2010 15:58:53 GMT Message-Id: <201005041558.o44FwrgB015254@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/146296: [zfs] [patch] fix deadlock during zfs receive (onnv 9299) 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, 04 May 2010 15:58:54 -0000 Synopsis: [zfs] [patch] fix deadlock during zfs receive (onnv 9299) Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue May 4 15:58:45 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=146296 From owner-freebsd-fs@FreeBSD.ORG Tue May 4 15:59:06 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3DEF810656AE; Tue, 4 May 2010 15:59:06 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 1640A8FC13; Tue, 4 May 2010 15:59:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44Fx5Ou015303; Tue, 4 May 2010 15:59:05 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44Fx5sC015299; Tue, 4 May 2010 15:59:05 GMT (envelope-from linimon) Date: Tue, 4 May 2010 15:59:05 GMT Message-Id: <201005041559.o44Fx5sC015299@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/146297: [zfs] [patch] zfs list improvements (onnv 8415, 10474) 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, 04 May 2010 15:59:06 -0000 Synopsis: [zfs] [patch] zfs list improvements (onnv 8415, 10474) Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue May 4 15:58:57 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=146297 From owner-freebsd-fs@FreeBSD.ORG Tue May 4 16:16:41 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34BAF106566C for ; Tue, 4 May 2010 16:16:41 +0000 (UTC) (envelope-from Lassi.Tuura@cern.ch) Received: from CERNMX30.cern.ch (cernmx30.cern.ch [137.138.144.177]) by mx1.freebsd.org (Postfix) with ESMTP id BDA608FC20 for ; Tue, 4 May 2010 16:16:40 +0000 (UTC) Received: from cernfe12.cern.ch (137.138.140.37) by cernmxgwlb2.cern.ch (137.138.144.177) with Microsoft SMTP Server (TLS) id 14.0.639.21; Tue, 4 May 2010 18:16:36 +0200 Received: from cmsmac01.cern.ch (137.138.52.75) by smtp.cern.ch (137.138.140.59) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 4 May 2010 18:16:35 +0200 MIME-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset="us-ascii" From: Lassi Tuura In-Reply-To: <20100504004905.GA12233@icarus.home.lan> Date: Tue, 4 May 2010 18:16:35 +0200 Content-Transfer-Encoding: 7bit Message-ID: <43B635E5-A901-4EA4-AE03-8A61E8F3F200@cern.ch> References: <4529AF96-4BFF-4424-B77F-FE5BC8AE43D3@cern.ch> <20100504004905.GA12233@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1078) Keywords: CERN SpamKiller Note: -50 Cc: freebsd-fs@freebsd.org Subject: Re: Instant crash with ZFS + iozone? 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, 04 May 2010 16:16:41 -0000 Hi, > This sounds like a hardware problem to me -- particularly excessive draw > on the PSU, voltage issues, or other whatnots. Especially if the screen > goes black (no cursor, monitor not in power save mode) and requires a > hard reset. Possibly the problem is only witnessed under extreme disk > I/O combined with high CPU usage + memory I/O. Thanks, that does look like plausible explanation here. I'll see what I can do. As you suggested, I made some tests with various number of disks and read/write patterns; ZFS is totally peripheral to this, I can get dd to induce similar failures. Two drives is ok, three only if there's not a lot of seeking, four only if two are reading and two are writing sequentially (no seeking at all). Selectively taking drives out and/or rearranging drives doesn't change this - it's not an issue with any one drive that I can tell - so will focus on PSU next. (Re Josh' reply I was in fact running iozone as root. Will keep in mind.) Regards, Lassi From owner-freebsd-fs@FreeBSD.ORG Tue May 4 17:40:04 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DE9031065674 for ; Tue, 4 May 2010 17:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B57AE8FC1E for ; Tue, 4 May 2010 17:40:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44He3kk001258 for ; Tue, 4 May 2010 17:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44He3Rt001257; Tue, 4 May 2010 17:40:03 GMT (envelope-from gnats) Date: Tue, 4 May 2010 17:40:03 GMT Message-Id: <201005041740.o44He3Rt001257@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/146296: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2010 17:40:04 -0000 The following reply was made to PR kern/146296; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/146296: commit references a PR Date: Tue, 4 May 2010 17:30:27 +0000 (UTC) Author: mm Date: Tue May 4 17:30:07 2010 New Revision: 207624 URL: http://svn.freebsd.org/changeset/base/207624 Log: Fix deadlock during zfs receive. OpenSolaris onnv revision: 9299:8809e849f63e PR: kern/146296 Submitted by: myself Approved by: pjd, delphij (mentor) Obtained from: OpenSolaris (Bug ID 6783818, 6826836) MFC after: 1 week Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_object.c Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c ============================================================================== --- head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c Tue May 4 17:12:36 2010 (r207623) +++ head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c Tue May 4 17:30:07 2010 (r207624) @@ -464,15 +464,15 @@ dbuf_read_impl(dmu_buf_impl_t *db, zio_t ASSERT(db->db_buf == NULL); if (db->db_blkid == DB_BONUS_BLKID) { - int bonuslen = dn->dn_bonuslen; + int bonuslen = MIN(dn->dn_bonuslen, dn->dn_phys->dn_bonuslen); ASSERT3U(bonuslen, <=, db->db.db_size); db->db.db_data = zio_buf_alloc(DN_MAX_BONUSLEN); arc_space_consume(DN_MAX_BONUSLEN); if (bonuslen < DN_MAX_BONUSLEN) bzero(db->db.db_data, DN_MAX_BONUSLEN); - bcopy(DN_BONUS(dn->dn_phys), db->db.db_data, - bonuslen); + if (bonuslen) + bcopy(DN_BONUS(dn->dn_phys), db->db.db_data, bonuslen); dbuf_update_data(db); db->db_state = DB_CACHED; mutex_exit(&db->db_mtx); Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_object.c ============================================================================== --- head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_object.c Tue May 4 17:12:36 2010 (r207623) +++ head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_object.c Tue May 4 17:30:07 2010 (r207624) @@ -128,15 +128,6 @@ dmu_object_reclaim(objset_t *os, uint64_ return (0); } - tx = dmu_tx_create(os); - dmu_tx_hold_bonus(tx, object); - err = dmu_tx_assign(tx, TXG_WAIT); - if (err) { - dmu_tx_abort(tx); - dnode_rele(dn, FTAG); - return (err); - } - nblkptr = 1 + ((DN_MAX_BONUSLEN - bonuslen) >> SPA_BLKPTRSHIFT); /* @@ -144,16 +135,27 @@ dmu_object_reclaim(objset_t *os, uint64_ * be a new file instance. We must clear out the previous file * contents before we can change this type of metadata in the dnode. */ - if (dn->dn_nblkptr > nblkptr || dn->dn_datablksz != blocksize) - dmu_free_long_range(os, object, 0, DMU_OBJECT_END); + if (dn->dn_nblkptr > nblkptr || dn->dn_datablksz != blocksize) { + err = dmu_free_long_range(os, object, 0, DMU_OBJECT_END); + if (err) + goto out; + } + + tx = dmu_tx_create(os); + dmu_tx_hold_bonus(tx, object); + err = dmu_tx_assign(tx, TXG_WAIT); + if (err) { + dmu_tx_abort(tx); + goto out; + } dnode_reallocate(dn, ot, blocksize, bonustype, bonuslen, tx); dmu_tx_commit(tx); - +out: dnode_rele(dn, FTAG); - return (0); + return (err); } int _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue May 4 17:50:03 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EEF571065673 for ; Tue, 4 May 2010 17:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id C4D668FC1A for ; Tue, 4 May 2010 17:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44Ho3cD009343 for ; Tue, 4 May 2010 17:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44Ho3Wp009342; Tue, 4 May 2010 17:50:03 GMT (envelope-from gnats) Date: Tue, 4 May 2010 17:50:03 GMT Message-Id: <201005041750.o44Ho3Wp009342@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/146297: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2010 17:50:04 -0000 The following reply was made to PR kern/146297; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/146297: commit references a PR Date: Tue, 4 May 2010 17:40:33 +0000 (UTC) Author: mm Date: Tue May 4 17:40:24 2010 New Revision: 207626 URL: http://svn.freebsd.org/changeset/base/207626 Log: Speed up ZFS list operation with objset prefetching. Partial import of OpenSolaris onnv revisions: 8415:8809e849f63e, 10474:0e96dd3b905a PR: kern/146297 Submitted by: myself Approved by: pjd, delphij (mentor) Obtained from: OpenSolaris (Bug ID 6386929, 6755389, 6847118) MFC after: 2 weeks Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_objset.c head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dmu_objset.h head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_objset.c ============================================================================== --- head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_objset.c Tue May 4 17:34:00 2010 (r207625) +++ head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_objset.c Tue May 4 17:40:24 2010 (r207626) @@ -1213,6 +1213,39 @@ dmu_objset_find_spa(spa_t *spa, const ch return (err); } +/* ARGSUSED */ +int +dmu_objset_prefetch(char *name, void *arg) +{ + dsl_dataset_t *ds; + + if (dsl_dataset_hold(name, FTAG, &ds)) + return (0); + + if (!BP_IS_HOLE(&ds->ds_phys->ds_bp)) { + mutex_enter(&ds->ds_opening_lock); + if (!dsl_dataset_get_user_ptr(ds)) { + uint32_t aflags = ARC_NOWAIT | ARC_PREFETCH; + zbookmark_t zb; + + zb.zb_objset = ds->ds_object; + zb.zb_object = 0; + zb.zb_level = -1; + zb.zb_blkid = 0; + + (void) arc_read_nolock(NULL, dsl_dataset_get_spa(ds), + &ds->ds_phys->ds_bp, NULL, NULL, + ZIO_PRIORITY_ASYNC_READ, + ZIO_FLAG_CANFAIL | ZIO_FLAG_SPECULATIVE, + &aflags, &zb); + } + mutex_exit(&ds->ds_opening_lock); + } + + dsl_dataset_rele(ds, FTAG); + return (0); +} + void dmu_objset_set_user(objset_t *os, void *user_ptr) { Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dmu_objset.h ============================================================================== --- head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dmu_objset.h Tue May 4 17:34:00 2010 (r207625) +++ head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dmu_objset.h Tue May 4 17:40:24 2010 (r207626) @@ -26,8 +26,6 @@ #ifndef _SYS_DMU_OBJSET_H #define _SYS_DMU_OBJSET_H -#pragma ident "%Z%%M% %I% %E% SMI" - #include #include #include @@ -118,6 +116,7 @@ int dmu_objset_find(char *name, int func int flags); int dmu_objset_find_spa(spa_t *spa, const char *name, int func(spa_t *, uint64_t, const char *, void *), void *arg, int flags); +int dmu_objset_prefetch(char *name, void *arg); void dmu_objset_byteswap(void *buf, size_t size); int dmu_objset_evict_dbufs(objset_t *os); Modified: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c ============================================================================== --- head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c Tue May 4 17:34:00 2010 (r207625) +++ head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c Tue May 4 17:40:24 2010 (r207626) @@ -1349,6 +1349,14 @@ zfs_ioc_dataset_list_next(zfs_cmd_t *zc) (void) strlcat(zc->zc_name, "/", sizeof (zc->zc_name)); p = zc->zc_name + strlen(zc->zc_name); + if (zc->zc_cookie == 0) { + uint64_t cookie = 0; + int len = sizeof (zc->zc_name) - (p - zc->zc_name); + + while (dmu_dir_list_next(os, len, p, NULL, &cookie) == 0) + dmu_objset_prefetch(p, NULL); + } + do { error = dmu_dir_list_next(os, sizeof (zc->zc_name) - (p - zc->zc_name), p, @@ -1387,6 +1395,9 @@ zfs_ioc_snapshot_list_next(zfs_cmd_t *zc objset_t *os; int error; + if (zc->zc_cookie == 0) + dmu_objset_find(zc->zc_name, dmu_objset_prefetch, + NULL, DS_FIND_SNAPSHOTS); error = dmu_objset_open(zc->zc_name, DMU_OST_ANY, DS_MODE_USER | DS_MODE_READONLY, &os); if (error) _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue May 4 17:50:07 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D11E1065672 for ; Tue, 4 May 2010 17:50:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 5CB388FC0C for ; Tue, 4 May 2010 17:50:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44Ho70W009397 for ; Tue, 4 May 2010 17:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44Ho7ew009396; Tue, 4 May 2010 17:50:07 GMT (envelope-from gnats) Date: Tue, 4 May 2010 17:50:07 GMT Message-Id: <201005041750.o44Ho7ew009396@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/146297: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2010 17:50:07 -0000 The following reply was made to PR kern/146297; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/146297: commit references a PR Date: Tue, 4 May 2010 17:44:54 +0000 (UTC) Author: mm Date: Tue May 4 17:44:40 2010 New Revision: 207627 URL: http://svn.freebsd.org/changeset/base/207627 Log: Enable "zfs list" to list explicitly requested snapshots. Partial import of OpenSolaris onnv revision: 8415:8809e849f63e PR: kern/146297 Submitted by: myself Approved by: pjd, delphij (mentor) Obtained from: OpenSolaris (Bug ID 6758338) MFC after: 2 weeks Modified: head/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c Modified: head/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c ============================================================================== --- head/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c Tue May 4 17:40:24 2010 (r207626) +++ head/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c Tue May 4 17:44:40 2010 (r207627) @@ -1790,7 +1790,7 @@ zfs_do_list(int argc, char **argv) boolean_t scripted = B_FALSE; static char default_fields[] = "name,used,available,referenced,mountpoint"; - int types = ZFS_TYPE_FILESYSTEM | ZFS_TYPE_VOLUME; + int types = ZFS_TYPE_DATASET; boolean_t types_specified = B_FALSE; char *fields = NULL; list_cbdata_t cb = { 0 }; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue May 4 21:05:07 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A79041065698 for ; Tue, 4 May 2010 21:05:07 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f227.google.com (mail-bw0-f227.google.com [209.85.218.227]) by mx1.freebsd.org (Postfix) with ESMTP id 05E7D8FC1C for ; Tue, 4 May 2010 21:05:03 +0000 (UTC) Received: by bwz27 with SMTP id 27so2855372bwz.13 for ; Tue, 04 May 2010 14:04:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:to:cc:subject:references :organization:from:date:in-reply-to:message-id:user-agent :mime-version:content-type; bh=U4kV0S3QPC7HVR12hAEkTNL8e16heHr0BCKaj7e/O2M=; b=lMA5z+ls/FU7jq0MT20rHhZxGoHoQ4rWSj27rdiqBKpkWM6cmxyuqqhHNS28zP/3bm h5Jp2R0YKGUyMnv5mm9WwqalbET/0J6n8BLeKjnzrXMygD6T5xrILJ7BCjuXMbYKKF0b tBLVN04jKp62Wbl0HH6YickIBDbykDUp3J4sE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=to:cc:subject:references:organization:from:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=Dq3NSU1KLk17u3KKV7Gls6H+D1zdDlIV85SigP4RaM6dPEVsW+Bs2W2TWsCVLE579z mXpSw35FAHylmcJQTYwbyCOLM1xL/jMPqb/10lbCrx+oYhY5QLAkctlEl2CHqmrR5e9l gzC5zXRmiciAVwYP8/01Nei50c7M575VQ+2pg= Received: by 10.204.152.13 with SMTP id e13mr466119bkw.30.1273007092653; Tue, 04 May 2010 14:04:52 -0700 (PDT) Received: from localhost ([95.69.164.134]) by mx.google.com with ESMTPS id 15sm2190474bwz.12.2010.05.04.14.04.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 04 May 2010 14:04:51 -0700 (PDT) To: freebsd-fs@FreeBSD.org References: <86bpcwluev.fsf@kopusha.onet> Organization: Home From: Mikolaj Golub Date: Wed, 05 May 2010 00:04:49 +0300 In-Reply-To: <86bpcwluev.fsf@kopusha.onet> (Mikolaj Golub's message of "Mon\, 03 May 2010 21\:19\:52 +0300") Message-ID: <86r5lr5qfi.fsf@kopusha.onet> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jeff Roberson Subject: Re: SUJ: fsck_ufs: Sparse journal inode 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, 04 May 2010 21:05:07 -0000 On Mon, 03 May 2010 21:19:52 +0300 Mikolaj Golub wrote: > Hi, > > Experimenting with journaled soft-updates on HAST I observed the error when > fscking fs on the secondary after primary "crash": > > # fsck -y -t ufs /dev/hast/tank > ** /dev/hast/tank > > USE JOURNAL?? yes > > ** SU+J Recovering /dev/hast/tank > ** Reading 33554384 byte journal from inode 4. > fsck_ufs: Sparse journal inode 4 (blocks = 16376, numfrags = 16383). > > (The text between the parentheses is a local modification to the fsck code to > output some useful values). > > So to recover I needed to run fsck and type "no" when prompted "USE > JOURNAL?". But I am looking for a way to script automatic recovering from this > situation. Currently the only way I have found is to disable journal, run > fsck, mount fs somewhere temporary, remove .sujournal, unmount, enable > journal. Is this really so complicated or may I just miss something? > > BTW, I used to observe this error on every "crash" test. And "blocks" value was > always the same: 16376. So I changed journal size to 16376 * 2048 = 33538048. > It looks like after this the issue has gone. Actually, this is tunefs who creates a sparse journal :-) When creating a journal tunefs allocates size/fs_bsize blocks (journal_alloc(size)). But if the journal size is not multiple of fs_bsize a block for tail fragments is not allocated and we have sparse file. Steps to reproduce: Choose a journal size: (blocksize * N) + fragsize + something. E.g. 4198400 (2048*2048 + 2*2048). [root@hasta ~]# newfs /dev/$dev /dev/md0: 10.0MB (20480 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 2.52MB, 161 blks, 384 inodes. super-block backups (for fsck -b #) at: 160, 5312, 10464, 15616 [root@hasta ~]# tunefs -j enable -S 4198400 /dev/$dev Using inode 4 in cg 0 for 4198400 byte journal tunefs: soft updates journaling set [root@hasta ~]# fsck -f -t ufs /dev/$dev ** /dev/md0 USE JOURNAL?? [yn] y ** SU+J Recovering /dev/md0 ** Reading 4198400 byte journal from inode 4. fsck_ufs: Sparse journal inode 4. Note, the size should be so that tail has at least one full fragment, because in the code we have: blocks = ino_visit(jip, sujino, suj_add_block, 0); if (blocks != numfrags(fs, DIP(jip, di_size))) errx(1, "Sparse journal inode %d.\n", sujino); with only one non-full fragment numfrags() will return the value equal to blocks. BTW, I am not sure this check would be correct even if tunefs allocated tail fragments. As I see in indir_visit() for every found block it adds: (*frags) += fs->fs_frag; so the same would be for the tail block, and ino_visit() in the code above would return more then numfrags(). -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Tue May 4 21:08:35 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF1CF106567A; Tue, 4 May 2010 21:08:35 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 988C58FC12; Tue, 4 May 2010 21:08:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44L8ZQQ079548; Tue, 4 May 2010 21:08:35 GMT (envelope-from mm@freefall.freebsd.org) Received: (from mm@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44L8ZGe079544; Tue, 4 May 2010 21:08:35 GMT (envelope-from mm) Date: Tue, 4 May 2010 21:08:35 GMT Message-Id: <201005042108.o44L8ZGe079544@freefall.freebsd.org> To: mm@FreeBSD.org, mm@FreeBSD.org, freebsd-fs@FreeBSD.org From: mm@FreeBSD.org Cc: Subject: Re: kern/146296: [zfs] [patch] fix deadlock during zfs receive (onnv 9299) 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, 04 May 2010 21:08:35 -0000 Synopsis: [zfs] [patch] fix deadlock during zfs receive (onnv 9299) State-Changed-From-To: open->patched State-Changed-By: mm State-Changed-When: Tue May 4 21:08:22 UTC 2010 State-Changed-Why: Scheduled for MFC http://www.freebsd.org/cgi/query-pr.cgi?pr=146296 From owner-freebsd-fs@FreeBSD.ORG Tue May 4 21:09:04 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D7731065673; Tue, 4 May 2010 21:09:04 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D8C7E8FC1D; Tue, 4 May 2010 21:09:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44L93tL079598; Tue, 4 May 2010 21:09:03 GMT (envelope-from mm@freefall.freebsd.org) Received: (from mm@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44L93WQ079594; Tue, 4 May 2010 21:09:03 GMT (envelope-from mm) Date: Tue, 4 May 2010 21:09:03 GMT Message-Id: <201005042109.o44L93WQ079594@freefall.freebsd.org> To: mm@FreeBSD.org, mm@FreeBSD.org, freebsd-fs@FreeBSD.org, mm@FreeBSD.org From: mm@FreeBSD.org Cc: Subject: Re: kern/146297: [zfs] [patch] zfs list improvements (onnv 8415, 10474) 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, 04 May 2010 21:09:04 -0000 Synopsis: [zfs] [patch] zfs list improvements (onnv 8415, 10474) State-Changed-From-To: open->patched State-Changed-By: mm State-Changed-When: Tue May 4 21:08:38 UTC 2010 State-Changed-Why: Scheduled for MFC Responsible-Changed-From-To: freebsd-fs->mm Responsible-Changed-By: mm Responsible-Changed-When: Tue May 4 21:08:38 UTC 2010 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=146297 From owner-freebsd-fs@FreeBSD.ORG Tue May 4 21:09:22 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 72A63106566C; Tue, 4 May 2010 21:09:22 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4BFF58FC12; Tue, 4 May 2010 21:09:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o44L9Mfv079643; Tue, 4 May 2010 21:09:22 GMT (envelope-from mm@freefall.freebsd.org) Received: (from mm@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o44L9M9s079639; Tue, 4 May 2010 21:09:22 GMT (envelope-from mm) Date: Tue, 4 May 2010 21:09:22 GMT Message-Id: <201005042109.o44L9M9s079639@freefall.freebsd.org> To: mm@FreeBSD.org, freebsd-fs@FreeBSD.org, mm@FreeBSD.org From: mm@FreeBSD.org Cc: Subject: Re: kern/146296: [zfs] [patch] fix deadlock during zfs receive (onnv 9299) 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, 04 May 2010 21:09:22 -0000 Synopsis: [zfs] [patch] fix deadlock during zfs receive (onnv 9299) Responsible-Changed-From-To: freebsd-fs->mm Responsible-Changed-By: mm Responsible-Changed-When: Tue May 4 21:09:08 UTC 2010 Responsible-Changed-Why: Take PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=146296 From owner-freebsd-fs@FreeBSD.ORG Tue May 4 22:51:04 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2071B106566C for ; Tue, 4 May 2010 22:51:04 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id A434D8FC17 for ; Tue, 4 May 2010 22:51:03 +0000 (UTC) Received: by fxm15 with SMTP id 15so4177495fxm.13 for ; Tue, 04 May 2010 15:51:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=TKCVhPPVQf+j+hSj4EG7W3pF62L1wp5BWU5SgwH3zrk=; b=rzMInNqW+2WD7t4pFCKLXgp0hhmc6Nmi7xdiipQ895qEFoz1/gY3F7qOaOrjIKf/ic Kx45MR4fy5gr0dYjcdsvmVfm8JS3cvjjHt7+KUL3un4R7p4mNPRKrI2VuLi7mu/VWdw8 MkC8Ewq85Ji2F1IEc8MNXwWT+pk1eGPgC6ZOc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=jLY78hJQCw7sHLAXiNwKGcoDTdLGYYGTokeYXL4VUdmybGB+mowndh46FVHTa538NI fJ3B2JSLFR4n/ZV0nGUwI8USOd6r73VXcCPJ/sAyj1WwJzG+NyyN1PtBRUYasA/vAkRI Z66W24Bw4gh3cvMMbkx1rlzltJgszq0EzwqjA= Received: by 10.102.206.23 with SMTP id d23mr10520070mug.54.1273012066522; Tue, 04 May 2010 15:27:46 -0700 (PDT) Received: from limbo.lan ([193.33.173.33]) by mx.google.com with ESMTPS id t10sm2127145muh.59.2010.05.04.15.27.44 (version=SSLv3 cipher=RC4-MD5); Tue, 04 May 2010 15:27:44 -0700 (PDT) Message-ID: <4BE09F5D.2080100@gmail.com> Date: Wed, 05 May 2010 01:27:41 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.1.9) Gecko/20100428 Thunderbird/3.0.4 MIME-Version: 1.0 To: Andriy Gapon References: <201004291220.o3TCK3Bo029643@freefall.freebsd.org> In-Reply-To: <201004291220.o3TCK3Bo029643@freefall.freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: bin/144214: zfsboot fails on gang block after upgrade to zfs v14 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, 04 May 2010 22:51:04 -0000 On 29.04.2010 15:20, Andriy Gapon wrote: > Just to be on the sure side: have you guys actually updated bootblocks on your system? > I.e. the code that runs before loader and that resides beyond filesystems. Yes, I do. Actually I was hit by the same bug recently one more time. After rebuild machine refuses to boot because of some gang blocks. I've tried to use i386 for the restoration purpose and set up a virtualbox in which I more then ten times tried to rewrite /boot and reboot from pool. Possible results were: * instant crash with colorful junk on the screen, just after the wiggling dash appear - seems like corrupted zfsloader; * refusing to load kernel showing the error; * lotsa gibberish about forth words unknown - seems like loader or some config files corrupted. Having played for 1 day with the disk I find that amount of luck for me to boot should be heavy, so I switched virtualbox to amd64 and just after the first rewrite of /boot system was up and running. 1. I used the same FreeBSD version to rewrite the data: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201004/FreeBSD-8.0-STABLE-201004-amd64-livefs.iso ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201004/FreeBSD-8.0-STABLE-201004-i386-livefs.iso 2. I used the same boot code and haven't changed it. So it looks like ZFS is writing data to the disks differently on i386. Just "the other way". -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@FreeBSD.ORG Wed May 5 01:15:19 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9C0D106566B for ; Wed, 5 May 2010 01:15:19 +0000 (UTC) (envelope-from yuwen@exodus.cs.ccu.edu.tw) Received: from pya.mail2000.com.tw (pya.mail2000.com.tw [203.69.82.99]) by mx1.freebsd.org (Postfix) with SMTP id 2CA7E8FC1D for ; Wed, 5 May 2010 01:15:18 +0000 (UTC) Received: from 10.0.0.47 by bak3.mail2000.com.tw with Mail2000 ESMTP Server V4.50S(11790:0:AUTH_LOGIN) (envelope-from ); Wed, 05 May 2010 09:14:00 +0800 (CST) Received: By OpenMail Mailer;Wed, 05 May 2010 09:14:00 +0800 (CST) From: "Cheng-Lin Yang" Message-ID: <1273022040.28218.yuwen@exodus.cs.ccu.edu.tw> In-Reply-To: <4BDFE843.7050600@fuujingroup.com> References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> <4BDFE843.7050600@fuujingroup.com> To: "erich" Date: Wed, 05 May 2010 09:14:00 +0800 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuwen@exodus.cs.ccu.edu.tw List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2010 01:15:19 -0000 Hi=20Erich, Here=20is=20the=20detail=20information: 1.=20The=20RAM=20on=20machine=20is:=20hw.physmem:=204278906880=20 2.=20My=20RAIDZ=20config $=20zpool=20status=20csdata =20=20pool:=20csdata =20state:=20ONLINE =20scrub:=20none=20requested config: =09NAME=20=20=20=20=20=20=20=20STATE=20=20=20=20=20READ=20WRITE=20CKSUM =09csdata=20=20=20=20=20=20ONLINE=20=20=20=20=20=20=200=20=20=20=20=200=20=20= =20=20=200 =09=20=20da0=20=20=20=20=20=20=20ONLINE=20=20=20=20=20=20=200=20=20=20=20=20= 0=20=20=20=20=200 errors:=20No=20known=20data=20errors 3.=20I=20do=20not=20have=20a=20separate=20ZIL=20device=20like=20a=20solid=20= state=20drive 4.=20uname=20-a FreeBSD=20cs1.cs.ccu.edu.tw=208.0-RELEASE=20FreeBSD=208.0-RELEASE=20#0:=20Sa= t=20Nov=2021=2015:02:08=20UTC=202009=20=20=20=20=20root@mason.cse.buffalo.ed= u:/usr/obj/usr/src/sys/GENERIC=20=20amd64 Also,=20the=20detail=20dmesg=20output=20can=20be=20found=20here:=20http://ww= w.cs.ccu.edu.tw/~hsp97m/dmesg.txt I'm=20looking=20forward=20to=20have=20your=20suggestions.=20Thank=20you=20:)= Regards, Cheng-Lin=20Yang -----Original=20message----- From:Erich=20Jenkins,=20Fuujin=20Group=20Ltd=20 To:yuwen@exodus.cs.ccu.edu.tw Cc:freebsd-fs=20,lab=20 Date:Tue,=2004=20May=202010=2003:26:27=20-0600 Subject:Re:=20Struggling=20on=20NFS=20problem Cheng-Lin=20Yang=20wrote: >=20Dear=20all, >=20Currently,=20we=20have=20a=20NFS=20server=20which=20runs=20FreeBSD8=20wi= th=20ZFS=20and=20few=20workstations=20as=20NFS=20client=20(2=20*=20FreeBSD8=20= amd64=20+=201=20*=20FreeBSD7.2=20i386=20+=202=20*=20Fedora=20+=20Debian).=20= We=20spotted=20that=20NFS=20performs=20weirdly=20on=20FreeBSD=20clients,=20w= hich=20will=20significantly=20slow=20down=20the=20system=20response.=20The=20= only=20solution=20to=20it=20is=20to=20reboot=20the=20clients=20(Linux=20clie= nt=20runs=20smoothly).=20So=20we=20try=20to=20use=20"nfsstat=20-c"=20on=20Fr= eeBSD=20client=20to=20dig=20into=20the=20problem=20and=20found=20strange=20r= esult=20(http://pastebin.com/K71qpEDG)=20: >=20csie0[~]#=20nfsstat=20-c >=20Client=20Info: >=20Rpc=20Counts: >=20=20=20Getattr=20=20=20Setattr=20=20=20=20Lookup=20=20Readlink=20=20=20=20= =20=20Read=20=20=20=20=20Write=20=20=20=20Create=20=20=20=20Remove >=20=20=203595047=20=20=20=20=2075100=20=20=201089213=20=20=20=20=20=201095=20= =20=201258311=20=2048664374=20=20=20=20104346=20=20=20=20116376 >=20=20=20=20Rename=20=20=20=20=20=20Link=20=20=20Symlink=20=20=20=20=20Mkdi= r=20=20=20=20=20Rmdir=20=20=20Readdir=20=20RdirPlus=20=20=20=20Access >=20=20=20=20=2017621=20=20=20=20=20=201644=20=20=20=20=20=20=20=2077=20=20=20= =20=2019569=20=20=20=20=20=209459=20=20=20=20=2045177=20=20=20=20=20=20=20=20= =200=20=20=20=20323665 >=20=20=20=20=20Mknod=20=20=20=20Fsstat=20=20=20=20Fsinfo=20=20PathConf=20=20= =20=20Commit >=20=20=20=20=20=20=20=20=200=20=20=20=20111262=20=20=20=20=20=20=20=20=203=20= =20=20=20=20=20=20=20=200=20=20=20=20590876 >=20Rpc=20Info: >=20=20TimedOut=20=20=20Invalid=20X=20Replies=20=20=20Retries=20=20Requests >=20=20=20=20=20=20=20=20=200=20=20=20=20=20=20=20=20=200=20=20=20=20=20=20=20= =20=200=20=20=20=20=20=20=20=20=200=20=2056022746 >=20Cache=20Info: >=20Attr=20Hits=20=20=20=20Misses=20Lkup=20Hits=20=20=20=20Misses=20BioR=20H= its=20=20=20=20Misses=20BioW=20Hits=20=20=20=20Misses >=20198414412=20=20=203595052=20112100649=20=20=201088903=20=2062793893=20=20= =201253320=20=20-1008715=20=2048664379 >=20BioRLHits=20=20=20=20Misses=20BioD=20Hits=20=20=20=20Misses=20DirE=20Hit= s=20=20=20=20Misses >=20=20=20=20=20=203751=20=20=20=20=20=201095=20=20=20=20204326=20=20=20=20=20= 45191=20=20=20=20109194=20=20=20=20=20=20=20=20=208 >=20 >=20As=20you=20can=20see,=20the=20value=20of=20"BioW=20Hits"=20is=20a=20nega= tive=20number.=20Shouldn't=20it=20be=20equal=20or=20larger=20than=20zero?=20= We=20have=20totally=20no=20idea=20on=20this=20issue.=20Please=20kindly=20hel= p=20us=20on=20investigating=20the=20problem.=20Any=20suggestion=20is=20extre= mely=20welcomed.=20Thank=20you. >=20 >=20Regards, >=20George >=20_______________________________________________ >=20freebsd-fs@freebsd.org=20mailing=20list >=20http://lists.freebsd.org/mailman/listinfo/freebsd-fs >=20To=20unsubscribe,=20send=20any=20mail=20to=20"freebsd-fs-unsubscribe@fre= ebsd.org" Cheng-Lin Could=20you=20provide=20a=20bit=20more=20info=20about=20your=20system=20and=20= setup?=20How=20much RAM,=20what=20type=20of=20raidz=20config?=20Do=20you=20have=20a=20separate=20= ZIL=20device=20like=20a solid=20state=20drive?=20Often,=20you'll=20experience=20severe=20NFS=20perfo= rmance degradation=20when=20using=20raidz=20and=20nfs=20if=20the=20zil=20logs=20are= =20on=20the=20same drives=20as=20the=20raidz=20volume. Erich=20M.=20Jenkins Fuujin=20Group=20Limited "You=20should=20never,=20never=20doubt=20what=20no=20one=20is=20sure=20about= ." --=20Gene=20Wilder ---------------------------------- Cheng-Lin=20Yang Sun=20Certified=20Java=20Programmer High=20Speed=20Network=20Group=20Lab=20(HSNG) Institute=20of=20Computer=20Science=20&=20Info.=20Engineering, National=20Chung=20Cheng=20Univerisity,=20Taiwan E-mail:=20yuwen@exodus.cs.ccu.edu.tw From owner-freebsd-fs@FreeBSD.ORG Wed May 5 01:27:50 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EAE99106566C for ; Wed, 5 May 2010 01:27:50 +0000 (UTC) (envelope-from yuwen@exodus.cs.ccu.edu.tw) Received: from pya.mail2000.com.tw (pya.mail2000.com.tw [203.69.82.99]) by mx1.freebsd.org (Postfix) with SMTP id 8D6FE8FC16 for ; Wed, 5 May 2010 01:27:48 +0000 (UTC) Received: from 10.0.0.47 by bak3.mail2000.com.tw with Mail2000 ESMTP Server V4.50S(11804:0:AUTH_LOGIN) (envelope-from ); Wed, 05 May 2010 09:20:53 +0800 (CST) Received: By OpenMail Mailer;Wed, 05 May 2010 09:20:52 +0800 (CST) From: "Cheng-Lin Yang" Message-ID: <1273022452.30713.yuwen@exodus.cs.ccu.edu.tw> In-Reply-To: References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> To: "rmacklem" Date: Wed, 05 May 2010 09:20:52 +0800 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuwen@exodus.cs.ccu.edu.tw List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2010 01:27:51 -0000 Hi=20Rick, Unfortunately,=20the=20machine=20which=20shows=20negative=20number,=20it's=20= amd64=20not=20i386: FreeBSD=20csie0.cs.ccu.edu.tw=208.0-RELEASE-p2=20FreeBSD=208.0-RELEASE-p2=20= #0:=20Tue=20Jan=20=205=2021:11:58=20UTC=202010=20=20=20=20=20root@amd64-buil= der.daemonology.net:/usr/obj/usr/src/sys/GENERIC=20=20amd64 I'll=20try=20to=20apply=20all=20the=20patches=20on=20my=20NFS=20server=20to=20= see=20if=20it=20can=20fix=20the=20problem.=20Also,=20I've=20replyed=20a=20ma= il=20which=20contains=20more=20information=20about=20NFS=20server.=20Could=20= you=20also=20take=20a=20look=20on=20it=20to=20see=20if=20there's=20anything=20= wrong? If=20the=20problem=20shows=20up=20again=20(I'm=20sure=20it=20will),=20I'll=20= try=20to=20capture=20the=20NFS=20traffic=20between=20server=20and=20clients.= =20Thank=20you!=20:) Regards, Cheng-Lin=20Yang -----Original=20message----- From:Rick=20Macklem=20 To:Cheng-Lin=20Yang=20 Cc:freebsd-fs=20,lab=20 Date:Tue,=204=20May=202010=2010:34:02=20-0400=20(EDT) Subject:Re:=20Struggling=20on=20NFS=20problem On=20Tue,=204=20May=202010,=20Cheng-Lin=20Yang=20wrote: >=20Dear=20all, >=20Currently,=20we=20have=20a=20NFS=20server=20which=20runs=20FreeBSD8=20wi= th=20ZFS=20and=20few=20workstations=20as=20NFS=20client=20(2=20*=20FreeBSD8=20= amd64=20+=201=20*=20FreeBSD7.2=20i386=20+=202=20*=20Fedora=20+=20Debian).=20= We=20spotted=20that=20NFS=20performs=20weirdly=20on=20FreeBSD=20clients,=20w= hich=20will=20significantly=20slow=20down=20the=20system=20response.=20The=20= only=20solution=20to=20it=20is=20to=20reboot=20the=20clients=20(Linux=20clie= nt=20runs=20smoothly).=20So=20we=20try=20to=20use=20"nfsstat=20-c"=20on=20Fr= eeBSD=20client=20to=20dig=20into=20the=20problem=20and=20found=20strange=20r= esult=20(http://pastebin.com/K71qpEDG)=20: >=20csie0[~]#=20nfsstat=20-c [stuff=20snipped] > >=20As=20you=20can=20see,=20the=20value=20of=20"BioW=20Hits"=20is=20a=20nega= tive=20number.=20Shouldn't=20it=20be=20equal=20or=20larger=20than=20zero?=20= We=20have=20totally=20no=20idea=20on=20this=20issue.=20Please=20kindly=20hel= p=20us=20on=20investigating=20the=20problem.=20Any=20suggestion=20is=20extre= mely=20welcomed.=20Thank=20you. > I=20suspect=20that=20the=20negative=20value=20is=20just=20a=20wrap=20around=20= (assuming=20you're on=20a=2032bit=20arch)=20and=20hust=20means=20lottsa=20hits.=20If=20that=20i= s=20the=20case,=20it suggests=20a=20fairly=20heavy=20write=20load,=20which=20can=20be=20an=20issu= e=20for=20servers using=20ZFS=20(as=20others=20have=20already=20posted=20about). There=20are=20a=20#=20of=20patches=20for=20FreeBSD8.0=20related=20to=20NFS=20= (one=20specifically w.r.t.=20the=20server=20using=20ZFS)=20at: =20=09http://people.freebsd.org/~rmacklem If=20you=20are=20using=20FreeBSD8.0=20for=20the=20server,=20it=20would=20be=20= worth=20trying these=20patches=20(they=20are=20all=20independent,=20in=20that=20any=20of=20= them=20can=20be applied,=20in=20any=20order).=20(If=20you=20are=20using=20a=20recent=20stabl= e/8,=20then you=20should=20already=20have=20the=20patches.) In=20particular,=20one=20of=20them=20fixes=20a=20case=20where=20FreeBSD=20cl= ients=20will get=20stuck=20looping=20trying=20to=20access=20a=20file=20after=20it=20has=20= been=20deleted on=20the=20server,=20because=20the=20server=20reported=20EIO=20instead=20of=20= ESTALE=20for this=20case. If=20the=20patches=20don't=20help,=20please=20try=20to=20collect=20more=20in= formation from=20both=20the=20slow=20clients=20and=20server.=20"ps=20axl"=20on=20them=20= all=20can=20be useful.=20Also,=20you=20can=20use=20"tcpdump=20-s=200=20-w=20=20host=20= " to=20capture=20traffic=20between=20the=20slow=20client=20and=20server=20whic= h=20can=20be looked=20at=20via=20wireshark.=20(tcpdump=20doesn't=20decode=20NFS=20traffic= =20well, but=20a=20binary=20capture=20from=20tcpdump=20goes=20into=20wireshark=20ok=20= and=20it=20does understand=20NFS=20traffic)=20If=20you=20get=20to=20this=20point,=20you=20ca= n=20email=20me the=20""=20as=20an=20attachment=20and=20I=20can=20take=20a=20look=20at= =20it.=20If=20you look=20at=20it,=20one=20scenario=20that=20is=20of=20interest=20is=20where=20= the=20client just=20keeps=20retrying=20the=20same=20NFS=20RPC. Good=20luck=20with=20it=20and=20let=20us=20know=20how=20it=20goes,=20rick ---------------------------------- Cheng-Lin=20Yang Sun=20Certified=20Java=20Programmer High=20Speed=20Network=20Group=20Lab=20(HSNG) Institute=20of=20Computer=20Science=20&=20Info.=20Engineering, National=20Chung=20Cheng=20Univerisity,=20Taiwan E-mail:=20yuwen@exodus.cs.ccu.edu.tw From owner-freebsd-fs@FreeBSD.ORG Wed May 5 01:31:39 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4F4FF106564A for ; Wed, 5 May 2010 01:31:39 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by mx1.freebsd.org (Postfix) with ESMTP id 364558FC0C for ; Wed, 5 May 2010 01:31:38 +0000 (UTC) Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta13.emeryville.ca.mail.comcast.net with comcast id DQgm1e00D1wfjNsADdXfKw; Wed, 05 May 2010 01:31:39 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta23.emeryville.ca.mail.comcast.net with comcast id DdXd1e00d3S48mS8jdXeZM; Wed, 05 May 2010 01:31:39 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 647969B425; Tue, 4 May 2010 18:31:36 -0700 (PDT) Date: Tue, 4 May 2010 18:31:36 -0700 From: Jeremy Chadwick To: Cheng-Lin Yang Message-ID: <20100505013136.GA48843@icarus.home.lan> References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> <4BDFE843.7050600@fuujingroup.com> <1273022040.28218.yuwen@exodus.cs.ccu.edu.tw> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1273022040.28218.yuwen@exodus.cs.ccu.edu.tw> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem 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, 05 May 2010 01:31:39 -0000 On Wed, May 05, 2010 at 09:14:00AM +0800, Cheng-Lin Yang wrote: > 4. uname -a > FreeBSD cs1.cs.ccu.edu.tw 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Can you please try upgrading to RELENG_8 and see if the problem goes away? Rick has made/committed many improvements to NFS in RELENG_8 that don't exist in 8.0-RELEASE. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed May 5 02:28:09 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67FA31065670 for ; Wed, 5 May 2010 02:28:09 +0000 (UTC) (envelope-from yuwen@exodus.cs.ccu.edu.tw) Received: from pya.mail2000.com.tw (pya.mail2000.com.tw [203.69.82.99]) by mx1.freebsd.org (Postfix) with SMTP id E1B4D8FC08 for ; Wed, 5 May 2010 02:28:08 +0000 (UTC) Received: from 10.0.0.47 by bak3.mail2000.com.tw with Mail2000 ESMTP Server V4.50S(11798:0:AUTH_LOGIN) (envelope-from ); Wed, 05 May 2010 10:28:03 +0800 (CST) Received: By OpenMail Mailer;Wed, 05 May 2010 10:27:59 +0800 (CST) From: "Cheng-Lin Yang" Message-ID: <1273026479.56161.yuwen@exodus.cs.ccu.edu.tw> In-Reply-To: <20100505013136.GA48843@icarus.home.lan> References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> <4BDFE843.7050600@fuujingroup.com> <1273022040.28218.yuwen@exodus.cs.ccu.edu.tw> <20100505013136.GA48843@icarus.home.lan> To: "freebsd" Date: Wed, 05 May 2010 10:27:59 +0800 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuwen@exodus.cs.ccu.edu.tw List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2010 02:28:09 -0000 Hi=20Jeremy, I=20certainly=20will,=20it=20seems=20to=20upgrading=20to=20RELENG_8=20will=20= be=20a=20highly=20possible=20solution=20for=20the=20issue.=20Therefore,=20I=20= already=20scheduled=20a=20upgrade=20window=20on=20this=20Friday=20night=20an= d=20will=20keep=20updating=20you=20guys=20the=20result=20once=20the=20upgrad= e=20is=20done. I=20would=20also=20like=20to=20know=20that=20is=20it=20ok=20to=20update=20th= e=20source=20up=20to=20RELENG_8=20by=20applying=20all=20NFS=20patches=20at=20= the=20same=20time?=20Since=20it's=20a=20production=20machine,=20I=20have=20t= o=20make=20sure=20these=20two=20steps=20can=20be=20perform=20at=20the=20same= =20time=20without=20any=20concern.=20 Finally,=20just=20curious=20that=20why=20the=20problem=20only=20shows=20up=20= on=20FreeBSD=20clients? Regards, Cheng-Lin=20Yang -----Original=20message----- From:Jeremy=20Chadwick=20 To:Cheng-Lin=20Yang=20 Cc:erich=20,freebsd-fs=20,lab= =20 Date:Tue,=204=20May=202010=2018:31:36=20-0700 Subject:Re:=20Struggling=20on=20NFS=20problem On=20Wed,=20May=2005,=202010=20at=2009:14:00AM=20+0800,=20Cheng-Lin=20Yang=20= wrote: >=204.=20uname=20-a >=20FreeBSD=20cs1.cs.ccu.edu.tw=208.0-RELEASE=20FreeBSD=208.0-RELEASE=20#0:=20= Sat=20Nov=2021=2015:02:08=20UTC=202009=20=20=20=20=20root@mason.cse.buffalo.= edu:/usr/obj/usr/src/sys/GENERIC=20=20amd64 Can=20you=20please=20try=20upgrading=20to=20RELENG_8=20and=20see=20if=20the=20= problem=20goes away?=20=20Rick=20has=20made/committed=20many=20improvements=20to=20NFS=20in= =20RELENG_8=20that don't=20exist=20in=208.0-RELEASE. --=20 |=20Jeremy=20Chadwick=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20jdc@parodius.com=20| |=20Parodius=20Networking=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20http://www.parodius.com/=20| |=20UNIX=20Systems=20Administrator=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20Mountain=20View,=20CA,=20USA=20| |=20Making=20life=20hard=20for=20others=20since=201977.=20=20=20=20=20=20=20= =20=20=20=20=20=20=20PGP:=204BD6C0CB=20| ---------------------------------- Cheng-Lin=20Yang Sun=20Certified=20Java=20Programmer High=20Speed=20Network=20Group=20Lab=20(HSNG) Institute=20of=20Computer=20Science=20&=20Info.=20Engineering, National=20Chung=20Cheng=20Univerisity,=20Taiwan E-mail:=20yuwen@exodus.cs.ccu.edu.tw From owner-freebsd-fs@FreeBSD.ORG Wed May 5 09:05:14 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4959E106566B for ; Wed, 5 May 2010 09:05:14 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mail.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with ESMTP id CAD3F8FC12 for ; Wed, 5 May 2010 09:05:13 +0000 (UTC) Received: from localhost (unknown [192.168.1.2]) by mail.zirakzigil.org (Postfix) with ESMTP id 649C19645F; Wed, 5 May 2010 10:46:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at zirakzigil.org Received: from mail.zirakzigil.org ([192.168.1.2]) by localhost (ext.zirakzigil.org [192.168.1.2]) (amavisd-new, port 10024) with ESMTP id Tu79RjZ5Aib0; Wed, 5 May 2010 10:46:30 +0200 (CEST) Received: from aurynmob2.giulioferro.it (unknown [192.168.1.2]) (Authenticated sender: auryn@zirakzigil.org) by mail.zirakzigil.org (Postfix) with ESMTPA id C7BFB96454; Wed, 5 May 2010 10:46:30 +0200 (CEST) Message-ID: <4BE13067.1060606@zirakzigil.org> Date: Wed, 05 May 2010 10:46:31 +0200 From: Giulio Ferro User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100223 Thunderbird/3.0.1 MIME-Version: 1.0 To: Jeremy Chadwick , freebsd-stable@freebsd.org, freebsd-fs@freebsd.org References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <20100505075242.GA57550@icarus.home.lan> In-Reply-To: <20100505075242.GA57550@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Freebsd 8.0 kmem map too small 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, 05 May 2010 09:05:14 -0000 On 05.05.2010 09:52, Jeremy Chadwick wrote: Nope, it's happened again... Now I've tried to rise vm.kmem_size to 6G... > Did you set both vm.kmem_size and vfs.zfs.arc_max, setting the latter to > something *less* than vm.kmem_size? > > Yes. After your suggestion, I set vfs.zfs.arc_max: 3758096384 vm.kmem_size: 4G Now: vfs.zfs.arc_max: 3758096384 vm.kmem_size: 6392119296 >> I'm really astounded at how unstable zfs is, it's causing me a lot >> of problem. >> >> Why isn't it stated in the handbook that zfs isn't up to production yet? >> > I'm not at liberty to comment + answer this question. > > Why people responsible for ZFS on freebsd aren't saying anything? What's the status of this issue? Is someone working on this??? From owner-freebsd-fs@FreeBSD.ORG Wed May 5 09:11:09 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34F841065672 for ; Wed, 5 May 2010 09:11:09 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: from web112403.mail.gq1.yahoo.com (web112403.mail.gq1.yahoo.com [98.137.26.129]) by mx1.freebsd.org (Postfix) with SMTP id 03F6A8FC13 for ; Wed, 5 May 2010 09:11:08 +0000 (UTC) Received: (qmail 66413 invoked by uid 60001); 5 May 2010 09:11:08 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1273050668; bh=2HMP4Y2jcGYxf+YoN05byS6VTxlxohHyVp9ua4uQG7c=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=GUk1qAH5BqVrEknQrpcGshQnJyLdgtdTQ0LF2YM9KJ0xx9sbRCCA3KJzxKK509SuA3YxMa1sUPvXSn7nUXVkgLJt5h9eXi4gU+nEWpaGtsIaw4Jkfb85hZsfyQVCX2MZwq3wdlHe/GioA7Y2Y93+Qwkx0em9xb5JCR9F8D9oZo4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=g6HTwcEwGddaHgbLpV5sSfpChQxBfkznqJ4OUVNzFalK68Jsnug9XnVfWLRke5jkebhq5MgMqaBTHq+q1J1+Ti/+wkZnV5z5hExlajpyZDpAjnZaFN9Rhe7fY6/ZXWT6jPMQPJiK8rWM7WFmmTdjGrLS864RQIPqglya6ht/Abg=; Message-ID: <483679.65695.qm@web112403.mail.gq1.yahoo.com> X-YMail-OSG: lwMjwt4VM1mRNr_J6onqhc7JNirh1Wk4AKXeFzAOV7n_GIC 8IzBCyZrPvL3BYwNtgqj.tyKx2Ff7LYmO4hLwM4Xmf7vm7L9PxEUZwSBATlH GZNqgeOuApWqJeiGby9hbCI6RhC74oK7miyUCgqPfAocpNEilzUdgEJjbIun aXlvfNP1x.B2aclEYzgQ23NMXl9LSEyUxo2mwzP6EE9_a9rlNWUGkejhxhkU FpUeiNBOqx3UiuacThQgfVploimSM0e3ld6q6dFsg6yp_tO07s2ADliA5YXL NumgC.3TWx8JisKSsRbg4qBNtk2p4a0zmAj5NpL5LPIg6Cwwvf4XhASo- Received: from [213.147.110.159] by web112403.mail.gq1.yahoo.com via HTTP; Wed, 05 May 2010 02:11:08 PDT X-Mailer: YahooMailRC/348.5 YahooMailWebService/0.8.103.269680 References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <20100505075242.GA57550@icarus.home.lan> <4BE13067.1060606@zirakzigil.org> Date: Wed, 5 May 2010 02:11:08 -0700 (PDT) From: Simun Mikecin To: Giulio Ferro In-Reply-To: <4BE13067.1060606@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org Subject: Re: Freebsd 8.0 kmem map too small 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, 05 May 2010 09:11:09 -0000 ----- Original Message ---- >> I'm really astounded at how unstable zfs is, it's > causing me a lot >> of problem. >> >> Why isn't it > stated in the handbook that zfs isn't up to production yet? >> > Why people responsible for ZFS on > freebsd aren't saying anything? What's the status of this issue? Is someone > working on this??? How much RAM do you have? Are you using i386 or amd64? Have you tried removing all zfs and kmem sysctl's so the system uses default values? From owner-freebsd-fs@FreeBSD.ORG Wed May 5 09:14:10 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ABBE8106564A; Wed, 5 May 2010 09:14:10 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mail.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with ESMTP id 1CCCF8FC08; Wed, 5 May 2010 09:14:09 +0000 (UTC) Received: from localhost (unknown [192.168.1.2]) by mail.zirakzigil.org (Postfix) with ESMTP id 25C9096ABD; Wed, 5 May 2010 11:14:09 +0200 (CEST) X-Virus-Scanned: amavisd-new at zirakzigil.org Received: from mail.zirakzigil.org ([192.168.1.2]) by localhost (ext.zirakzigil.org [192.168.1.2]) (amavisd-new, port 10024) with ESMTP id ZuP0nMVb+KUZ; Wed, 5 May 2010 11:14:06 +0200 (CEST) Received: from aurynmob2.giulioferro.it (unknown [192.168.1.2]) (Authenticated sender: auryn@zirakzigil.org) by mail.zirakzigil.org (Postfix) with ESMTPA id 0D03996AAF; Wed, 5 May 2010 11:14:06 +0200 (CEST) Message-ID: <4BE136DE.5010904@zirakzigil.org> Date: Wed, 05 May 2010 11:14:06 +0200 From: Giulio Ferro User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100223 Thunderbird/3.0.1 MIME-Version: 1.0 To: Simun Mikecin References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <20100505075242.GA57550@icarus.home.lan> <4BE13067.1060606@zirakzigil.org> <483679.65695.qm@web112403.mail.gq1.yahoo.com> In-Reply-To: <483679.65695.qm@web112403.mail.gq1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Freebsd 8.0 kmem map too small 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, 05 May 2010 09:14:10 -0000 On 05.05.2010 11:11, Simun Mikecin wrote: > ----- Original Message ---- > >>> I'm really astounded at how unstable zfs is, it's >>> >> causing me a lot >> >>> of problem. >>> >>> Why isn't it >>> >> stated in the handbook that zfs isn't up to production yet? >> >>> >>> >> Why people responsible for ZFS on >> freebsd aren't saying anything? What's the status of this issue? Is someone >> working on this??? >> > > How much RAM do you have? Are you using i386 or amd64? Have you tried removing all zfs and kmem sysctl's so the system uses default values? > > This is the first post of the current thread: it should tell you everything -------------------------------------------------------------------- NFS server amd64 Freebsd 8.0 recent (2 days ago) This server has been running for several months without problems. Beginning last week, however, I'm experiencing panics (about 1 per day) with the error in the subject Current settings: vm.kmem_size_scale: 3 vm.kmem_size_max: 329853485875 vm.kmem_size_min: 0 vm.kmem_size: 2764046336 ... hw.physmem: 8568225792 hw.usermem: 6117404672 hw.realmem: 9395240960 ... vfs.zfs.l2arc_noprefetch: 0 vfs.zfs.l2arc_feed_secs_shift: 1 vfs.zfs.l2arc_feed_secs: 1 vfs.zfs.l2arc_headroom: 128 vfs.zfs.l2arc_write_boost: 67108864 vfs.zfs.l2arc_write_max: 67108864 vfs.zfs.arc_meta_limit: 431882240 vfs.zfs.arc_meta_used: 431874720 vfs.zfs.arc_min: 215941120 vfs.zfs.arc_max: 1727528960 I've set nothing in either /boot/loader.conf or sysctl.conf What should I do? -------------------------------------------------------------------- From owner-freebsd-fs@FreeBSD.ORG Wed May 5 13:33:15 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A00E106564A; Wed, 5 May 2010 13:33:15 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello089077043238.chello.pl [89.77.43.238]) by mx1.freebsd.org (Postfix) with ESMTP id 51A1C8FC1F; Wed, 5 May 2010 13:33:13 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 8603945F22; Wed, 5 May 2010 15:33:11 +0200 (CEST) Received: from localhost (pdawidek.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 E431845E49; Wed, 5 May 2010 15:33:06 +0200 (CEST) Date: Wed, 5 May 2010 15:33:02 +0200 From: Pawel Jakub Dawidek To: Giulio Ferro Message-ID: <20100505133302.GB1626@garage.freebsd.pl> References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <20100505075242.GA57550@icarus.home.lan> <4BE13067.1060606@zirakzigil.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj" Content-Disposition: inline In-Reply-To: <4BE13067.1060606@zirakzigil.org> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 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=4.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Freebsd 8.0 kmem map too small 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, 05 May 2010 13:33:15 -0000 --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 05, 2010 at 10:46:31AM +0200, Giulio Ferro wrote: > On 05.05.2010 09:52, Jeremy Chadwick wrote: >=20 > Nope, it's happened again... Now I've tried to rise vm.kmem_size to 6G... >=20 >=20 > >Did you set both vm.kmem_size and vfs.zfs.arc_max, setting the latter to > >something *less* than vm.kmem_size? > > > > =20 >=20 > Yes. > After your suggestion, I set > vfs.zfs.arc_max: 3758096384 > vm.kmem_size: 4G >=20 > Now: > vfs.zfs.arc_max: 3758096384 > vm.kmem_size: 6392119296 Could you try to track down the commit that is causing your problems? Could you try 8-STABLE kernel from before r206815? --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvhc40ACgkQForvXbEpPzQDMgCg3wAjzXe1GtF6AQFHxSKjt0zs NVMAoJEU5jdMGAFYPSI1vWlMRY4fTE+w =Q7ev -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj-- From owner-freebsd-fs@FreeBSD.ORG Wed May 5 14:39:53 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 54EB01065673 for ; Wed, 5 May 2010 14:39:53 +0000 (UTC) (envelope-from ben@wanderview.com) Received: from mail.wanderview.com (mail.wanderview.com [66.92.166.102]) by mx1.freebsd.org (Postfix) with ESMTP id 631AA8FC13 for ; Wed, 5 May 2010 14:39:51 +0000 (UTC) Received: from xykon.in.wanderview.com (xykon.in.wanderview.com [10.76.10.152]) (authenticated bits=0) by mail.wanderview.com (8.14.4/8.14.4) with ESMTP id o45ECnqS027944 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 May 2010 14:12:49 GMT (envelope-from ben@wanderview.com) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Ben Kelly In-Reply-To: <20100505133302.GB1626@garage.freebsd.pl> Date: Wed, 5 May 2010 10:12:49 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <533152DA-3B2F-4994-9206-727A2B0010AD@wanderview.com> References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <20100505075242.GA57550@icarus.home.lan> <4BE13067.1060606@zirakzigil.org> <20100505133302.GB1626@garage.freebsd.pl> To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.1078) X-Spam-Score: -1.01 () ALL_TRUSTED,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.67 on 10.76.20.1 Cc: freebsd-fs@freebsd.org, FreeBSD Stable Subject: Re: Freebsd 8.0 kmem map too small 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, 05 May 2010 14:39:53 -0000 On May 5, 2010, at 9:33 AM, Pawel Jakub Dawidek wrote: > On Wed, May 05, 2010 at 10:46:31AM +0200, Giulio Ferro wrote: >> On 05.05.2010 09:52, Jeremy Chadwick wrote: >>=20 >> Nope, it's happened again... Now I've tried to rise vm.kmem_size to = 6G... >>=20 >>=20 >>> Did you set both vm.kmem_size and vfs.zfs.arc_max, setting the = latter to >>> something *less* than vm.kmem_size? >>>=20 >>>=20 >>=20 >> Yes. >> After your suggestion, I set >> vfs.zfs.arc_max: 3758096384 >> vm.kmem_size: 4G >>=20 >> Now: >> vfs.zfs.arc_max: 3758096384 >> vm.kmem_size: 6392119296 >=20 > Could you try to track down the commit that is causing your problems? > Could you try 8-STABLE kernel from before r206815? Are others generally able to run ARC values so close to kmem size? My = experience has been that you really need the ARC to be much smaller than = the kmem limit (like 25% or less) due to fragmentation of kmem_map. - Ben= From owner-freebsd-fs@FreeBSD.ORG Wed May 5 14:46:25 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1B8CD1065747 for ; Wed, 5 May 2010 14:46:25 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by mx1.freebsd.org (Postfix) with ESMTP id BAB438FC0C for ; Wed, 5 May 2010 14:46:24 +0000 (UTC) Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta15.westchester.pa.mail.comcast.net with comcast id Dn5n1e0031ap0As5FqmRh3; Wed, 05 May 2010 14:46:25 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by omta22.westchester.pa.mail.comcast.net with comcast id Dqm81e00H4Mx3R23iqmCdQ; Wed, 05 May 2010 14:46:23 +0000 Message-ID: <4BE184AE.7070307@comcast.net> Date: Wed, 05 May 2010 10:46:06 -0400 From: Steve Polyack User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100311 Thunderbird/3.0.1 MIME-Version: 1.0 To: Ben Kelly References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <20100505075242.GA57550@icarus.home.lan> <4BE13067.1060606@zirakzigil.org> <20100505133302.GB1626@garage.freebsd.pl> <533152DA-3B2F-4994-9206-727A2B0010AD@wanderview.com> In-Reply-To: <533152DA-3B2F-4994-9206-727A2B0010AD@wanderview.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, FreeBSD Stable , Pawel Jakub Dawidek Subject: Re: Freebsd 8.0 kmem map too small 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, 05 May 2010 14:46:25 -0000 On 05/05/10 10:12, Ben Kelly wrote: > On May 5, 2010, at 9:33 AM, Pawel Jakub Dawidek wrote: > > >> On Wed, May 05, 2010 at 10:46:31AM +0200, Giulio Ferro wrote: >> >>> On 05.05.2010 09:52, Jeremy Chadwick wrote: >>> >>> Nope, it's happened again... Now I've tried to rise vm.kmem_size to 6G... >>> >>> >>> >>>> Did you set both vm.kmem_size and vfs.zfs.arc_max, setting the latter to >>>> something *less* than vm.kmem_size? >>>> >>>> >>>> >>> Yes. >>> After your suggestion, I set >>> vfs.zfs.arc_max: 3758096384 >>> vm.kmem_size: 4G >>> >>> Now: >>> vfs.zfs.arc_max: 3758096384 >>> vm.kmem_size: 6392119296 >>> >> Could you try to track down the commit that is causing your problems? >> Could you try 8-STABLE kernel from before r206815? >> > > Are others generally able to run ARC values so close to kmem size? My experience has been that you really need the ARC to be much smaller than the kmem limit (like 25% or less) due to fragmentation of kmem_map. > > On a system here with 8GB of RAM and a very large zpool consisting of multiple zdevs, little tuning was needed. The system is running 8-STABLE(amd64) as of a month or two ago. The only things I have set in /boot/loader.conf are: vm.kmem_size="12G" vfs.zfs.arc_max="4G" Setting kmem_size to 12G came from a combination of recommendations I saw in various mailing list posts (you can probably dig them up). Setting it to the physical memory size was the initial recommendation, while others recommended 1.5x physical memory size to help prevent fragmentation/wasted space in kmem. Regardless, this has served us quite well for the ~6 months the system has been in use. It has never crashed, even under intensive multi-threaded benchmarking. -Steve From owner-freebsd-fs@FreeBSD.ORG Wed May 5 14:53:03 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7ED571065672 for ; Wed, 5 May 2010 14:53:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3210D8FC0C for ; Wed, 5 May 2010 14:53:02 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAPoi4UuDaFvI/2dsb2JhbACdRnG+FYUTBA X-IronPort-AV: E=Sophos;i="4.52,333,1270440000"; d="scan'208";a="74918481" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 05 May 2010 10:53:01 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id A48F4940140; Wed, 5 May 2010 10:53:01 -0400 (EDT) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hAnCkEmEzTdV; Wed, 5 May 2010 10:52:59 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 9ECAE9400AA; Wed, 5 May 2010 10:52:59 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o45F7gu17593; Wed, 5 May 2010 11:07:42 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Wed, 5 May 2010 11:07:42 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Jeremy Chadwick In-Reply-To: <20100505013136.GA48843@icarus.home.lan> Message-ID: References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> <4BDFE843.7050600@fuujingroup.com> <1273022040.28218.yuwen@exodus.cs.ccu.edu.tw> <20100505013136.GA48843@icarus.home.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs , Cheng-Lin Yang , lab Subject: Re: Struggling on NFS problem 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, 05 May 2010 14:53:03 -0000 On Tue, 4 May 2010, Jeremy Chadwick wrote: > On Wed, May 05, 2010 at 09:14:00AM +0800, Cheng-Lin Yang wrote: >> 4. uname -a >> FreeBSD cs1.cs.ccu.edu.tw 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > Can you please try upgrading to RELENG_8 and see if the problem goes > away? Rick has made/committed many improvements to NFS in RELENG_8 that > don't exist in 8.0-RELEASE. > Since he is going to apply the patches at people.freebsd.org/~rmacklem, that should cover the important stuff. I have no idea if any of them will help. (One might explain why the clients become unusable. As for performance related to ZFS, I don't know anything about that. I've seen the emails go by on the mailing lists. I am hoping we can capture that information and put it in one place for users someday soon.) rick From owner-freebsd-fs@FreeBSD.ORG Wed May 5 14:56:20 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1923D1065670 for ; Wed, 5 May 2010 14:56:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id BFE4B8FC14 for ; Wed, 5 May 2010 14:56:19 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAGYj4UuDaFvG/2dsb2JhbACdRnG+D4UTBI8/ X-IronPort-AV: E=Sophos;i="4.52,333,1270440000"; d="scan'208";a="75461695" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 05 May 2010 10:56:17 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id E9AF82101F3; Wed, 5 May 2010 10:56:17 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TcbASlkF+xcw; Wed, 5 May 2010 10:56:17 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 71D482101F1; Wed, 5 May 2010 10:56:16 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o45FB0n18071; Wed, 5 May 2010 11:11:00 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Wed, 5 May 2010 11:11:00 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Cheng-Lin Yang In-Reply-To: <1273026479.56161.yuwen@exodus.cs.ccu.edu.tw> Message-ID: References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> <4BDFE843.7050600@fuujingroup.com> <1273022040.28218.yuwen@exodus.cs.ccu.edu.tw> <20100505013136.GA48843@icarus.home.lan> <1273026479.56161.yuwen@exodus.cs.ccu.edu.tw> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem 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, 05 May 2010 14:56:20 -0000 On Wed, 5 May 2010, Cheng-Lin Yang wrote: > Hi Jeremy, > I certainly will, it seems to upgrading to RELENG_8 will be a highly possible solution for the issue. Therefore, I already scheduled a upgrade window on this Friday night and will keep updating you guys the result once the upgrade is done. > > I would also like to know that is it ok to update the source up to RELENG_8 by applying all NFS patches at the same time? Since it's a production machine, I have to make sure these two steps can be perform at the same time without any concern. > The patches at people.freebsd.org/~rmacklem are already in stable/8, so you shouldn't need to apply them. > Finally, just curious that why the problem only shows up on FreeBSD clients? > If it is the case where the server doesn't return ESTALE when a file has been deleted on the server, the FreeBSD client will loop retrying the RPC for EIO, but other clients might not. That is the only case where I can suggest there is a difference, other than the type of traffic and load different clients will generate. rick From owner-freebsd-fs@FreeBSD.ORG Wed May 5 19:54:36 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D955F1065678 for ; Wed, 5 May 2010 19:54:36 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by mx1.freebsd.org (Postfix) with ESMTP id 6770E8FC30 for ; Wed, 5 May 2010 19:54:35 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id l26so96135fgb.13 for ; Wed, 05 May 2010 12:54:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=B4UbFrgvRLVajVpEmPRAW7HnBpy5qf2iG8y45o32g3g=; b=fM2Jd+KRy9zT7udvUzK7y2odj/ZvradwSTl9BNNrrLcXSXX4HYEkvMhpFKTWK+Ij3o ziXHbDKi3JQT2oJjOZFgAynZk4vcgS0qEQSIDZ4mvwPtQRx3avOwbkinvY7jUEZ7aS+z MLmdlSfRkjCFmAahBWKpOcA+pTLhHcrp8hRSE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=CpAFQ6yr6c24vRQw8sqqSEn87fZQmI03Gs28NM1csT1BQzdwCfwofxSD1FRkCbEsdW LcfiSNq8JXvtJjThT157cTr72HFC8xW3UizgUDUdt9U66HfeGup9gPeDqKGY87tak8cv EBA8aW4kg5HSY0ohtBvw80owsRyf4g8sEt2N0= Received: by 10.103.144.37 with SMTP id w37mr11488624mun.19.1273089267733; Wed, 05 May 2010 12:54:27 -0700 (PDT) Received: from limbo.lan ([193.33.173.33]) by mx.google.com with ESMTPS id n7sm874286mue.45.2010.05.05.12.54.25 (version=SSLv3 cipher=RC4-MD5); Wed, 05 May 2010 12:54:26 -0700 (PDT) Message-ID: <4BE1CCEF.4040604@gmail.com> Date: Wed, 05 May 2010 22:54:23 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.1.9) Gecko/20100428 Thunderbird/3.0.4 MIME-Version: 1.0 To: Martin Simmons References: <201004221441.PAA07296@wratting.cam.lispworks.com> In-Reply-To: <201004221441.PAA07296@wratting.cam.lispworks.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: zfs: unexpected resilver of old disk when attaching a new mirror disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2010 19:54:37 -0000 On 22.04.2010 17:41, Martin Simmons wrote: > When I attach a second disk to a single-disk zpool to make a mirrored pool, > the original disk is partially resilvered. Is that expected? It makes me > worry that some of the good data is being overwritten. > > NAME STATE READ WRITE CKSUM > ztest ONLINE 0 0 0 > mirror ONLINE 0 0 0 > /tmp/zdisk0 ONLINE 0 0 0 86K resilvered > /tmp/zdisk1 ONLINE 0 0 0 16.1M resilvered > > errors: No known data errors 1. ZFS tries to store checksums as far as it can. Another drive preferrably. 2. ZFS tries to store metadata copies in different location as far as it can. -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@FreeBSD.ORG Thu May 6 01:42:50 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B0E11065675 for ; Thu, 6 May 2010 01:42:50 +0000 (UTC) (envelope-from staale@kristoffersen.ws) Received: from mail-forward.uio.no (mail-forward.uio.no [129.240.10.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2505F8FC0C for ; Thu, 6 May 2010 01:42:49 +0000 (UTC) Received: from mail-mx2.uio.no ([129.240.10.30]) by pat.uio.no with esmtp (Exim 4.67) (envelope-from ) id 1O9pn8-0004u7-KY for freebsd-fs@freebsd.org; Thu, 06 May 2010 03:22:18 +0200 Received: from putsch.kolbu.ws ([158.36.191.193]) by mail-mx2.uio.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1O9pn8-00036F-0z for freebsd-fs@freebsd.org; Thu, 06 May 2010 03:22:18 +0200 Received: from chiller by putsch.kolbu.ws with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1O9pn7-000BeM-Pn for freebsd-fs@freebsd.org; Thu, 06 May 2010 03:22:17 +0200 Date: Thu, 6 May 2010 03:22:17 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: freebsd-fs@freebsd.org Message-ID: <20100506012217.GA41806@putsch.kolbu.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.18 (2008-05-17) X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 9366186A0607D88E4E8511B24A4A2ADE5E567E9D X-UiO-SPAM-Test: remote_host: 158.36.191.193 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 584 max/h 11 blacklist 0 greylist 0 ratelimit 0 Subject: Bad hardware + zfs = panic 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, 06 May 2010 01:42:50 -0000 I've been debugging a hardware error for the past few days, and I think it was the CPU and that it is now fixed. But reading a file that was written to a zfs-pool when stuff got corrupted still triggered a panic in ZFS code: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x28 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff8106f2d3 stack pointer = 0x28:0xffffff80774914e0 frame pointer = 0x28:0xffffff8077491510 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1350 (smbd) trap number = 12 panic: page fault cpuid = 0 Uptime: 2m53s The lines in the backtrace that got my attention was: #6 0xffffffff80847c73 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:224 #7 0xffffffff8106f2d3 in vdev_is_dead (vd=0x0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c:1847 #8 0xffffffff8106f2ed in vdev_readable (vd=0x0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c:1854 The complete bt is available here: http://heim.ifi.uio.no/staalebk/zfs-panic.txt As you can see vd=0x0, and I think that caused the panic, since it tried to follow that pointer: return (vd->vdev_state < VDEV_STATE_DEGRADED); I then tried to remove the file and I got this: Solaris: WARNING: metaslab_free_dva(): bad DVA 199476166:1296607792756162560 Solaris: WARNING: metaslab_free_dva(): bad DVA 4236221:7256850009726709760 Solaris: WARNING: metaslab_free_dva(): bad DVA 935912721:16480078061480073216 Maybe there should be a test to check if vd was zero, and throw an io-error or something, instead of panicing? I'm new to debugging kernels, so if what I'm typing makes no sense, just tell me. Kernel version is: FreeBSD fs2 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5 21:11:58 UTC 2010 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- Ståle Kristoffersen From owner-freebsd-fs@FreeBSD.ORG Thu May 6 16:14:24 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DDEAD1065673; Thu, 6 May 2010 16:14:24 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from erg.verweg.com (erg.verweg.com [94.142.245.8]) by mx1.freebsd.org (Postfix) with ESMTP id 5AE898FC08; Thu, 6 May 2010 16:14:23 +0000 (UTC) Received: from [192.168.1.27] (helium.xs4all.nl [83.163.52.241]) (authenticated bits=0) by erg.verweg.com (8.14.4/8.14.3) with ESMTP id o46G0YHi085469 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 6 May 2010 16:00:40 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host helium.xs4all.nl [83.163.52.241] claimed to be [192.168.1.27] Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Ruben van Staveren In-Reply-To: <20100505133302.GB1626@garage.freebsd.pl> Date: Thu, 6 May 2010 18:00:33 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <20100505075242.GA57550@icarus.home.lan> <4BE13067.1060606@zirakzigil.org> <20100505133302.GB1626@garage.freebsd.pl> To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.1078) X-Spam-Status: No, score=2.5 required=5.0 tests=DATE_IN_FUTURE_12_24 autolearn=no version=3.3.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on erg.verweg.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (erg.verweg.com [94.142.245.8]); Thu, 06 May 2010 16:00:41 +0000 (UTC) Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Freebsd 8.0 kmem map too small 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, 06 May 2010 16:14:25 -0000 On 5 May 2010, at 15:33, Pawel Jakub Dawidek wrote: > Could you try to track down the commit that is causing your problems? > Could you try 8-STABLE kernel from before r206815? I do suspect something similar like that, and try to roll the kernel = back too. I was just fine with 8.0 with zfs-on-root till the last update when my = typical workload (portupgrade every now and then, make world) resulted = in kmem map too small panics and more sluggish performance (spending = most time in zio->io_cv) during pkgdb -F on a i386 system with 2gb = memory. I have 1gb memory sized amd64 vmware fusion vm's that run = without incident using the same workload. I had to bump KVA_PAGES to 512 and set vm.kmem_size=3D1024M to have this = i386 system stable again. Prior to that I tried to lower the arc cache = size but that resulted in a unresponsive system that I could not = diagnose. Regards, Ruben From owner-freebsd-fs@FreeBSD.ORG Thu May 6 22:27:03 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D1AC21065670 for ; Thu, 6 May 2010 22:27:03 +0000 (UTC) (envelope-from dnewman@networktest.com) Received: from mail3.networktest.com (mail3.networktest.com [69.55.234.60]) by mx1.freebsd.org (Postfix) with ESMTP id B5BDA8FC0A for ; Thu, 6 May 2010 22:27:03 +0000 (UTC) Received: from localhost (localhost [69.55.234.60]) by mail3.networktest.com (Postfix) with ESMTP id 3D3B59592D for ; Thu, 6 May 2010 15:10:09 -0700 (PDT) Received: from mail3.networktest.com ([69.55.234.60]) by localhost (mail3.networktest.com [69.55.234.60]) (amavisd-maia, port 10024) with ESMTP id 95081-03 for ; Thu, 6 May 2010 15:10:09 -0700 (PDT) Received: from dhcp130.eng.networktest.com (ns.networktest.com [216.240.60.130]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dnewman@networktest.com) by mail3.networktest.com (Postfix) with ESMTPSA id 0DD21958C9 for ; Thu, 6 May 2010 15:10:09 -0700 (PDT) Message-ID: <4BE33E40.6080905@networktest.com> Date: Thu, 06 May 2010 15:10:08 -0700 From: David Newman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Aligning VMware VMFS on 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, 06 May 2010 22:27:03 -0000 Greetings. I am trying to use 8.0-RELEASE, ZFS and the istgt port as an iSCSI target for VMware ESX virtual machines. A vSphere client (the management box that looks after VMware hosts and VMs) sees the target just fine, but the FreeBSD machine returns alignment error messages like these after the vSphere box formats a VMFS datastore: May 6 14:29:15 bettini kernel: GEOM: zvol/tank/bettini0: partition 1 does not start on a track boundary. May 6 14:29:15 bettini kernel: GEOM: zvol/tank/bettini0: partition 1 does not end on a track boundary. These errors occur only after formatting the VMFS datastore from the VMware vSphere 4 client. The errors occur on bootup and on restarting istgt. Steps I've already tried: - using this guide for ZFS setup: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 - rebuilding so that ZFS partition starts on block 128 and ZFS partition size is a multiple of 512 and 8192, e.g.: bettini# gpart show da0 => 34 1953103805 da0 GPT (931G) 34 94 1 freebsd-boot (47K) 128 1944584192 2 freebsd-zfs (927G) 1944584320 8388608 3 freebsd-swap (4.0G) 1952972928 130911 - free - (64M) - defining different volume sizes in ZFS ranging from 512G to 2T. I'm currently using a 1-Tbyte ZFS filesystem as the iSCSI target. (There are 8 disks using raidz1 on this system, so available space is much higher than the 927G shown above.) - contacted the maintainer of istgt port, who suggests a possible VMFS and GEOM problem such as GEOM not recognizing the VMFS format. Thanks in advance for clues on getting VMFS aligned on ZFS. dn From owner-freebsd-fs@FreeBSD.ORG Thu May 6 23:18:51 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 809F9106566B for ; Thu, 6 May 2010 23:18:51 +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 45BAC8FC15 for ; Thu, 6 May 2010 23:18:50 +0000 (UTC) Received: by email.octopus.com.au (Postfix, from userid 1002) id 4A7B15CB954; Fri, 7 May 2010 09:07:31 +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=4.4 required=10.0 tests=ALL_TRUSTED, DNS_FROM_OPENWHOIS,FH_DATE_PAST_20XX autolearn=no version=3.2.3 Received: from [220.233.52.14] (14.52.233.220.static.exetel.com.au [220.233.52.14]) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id F38015CB951; Fri, 7 May 2010 09:07:26 +1000 (EST) Message-ID: <4BE34E52.7050407@modulus.org> Date: Fri, 07 May 2010 09:18:42 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.24 (X11/20100411) MIME-Version: 1.0 To: David Newman , freebsd-fs@freebsd.org References: <4BE33E40.6080905@networktest.com> In-Reply-To: <4BE33E40.6080905@networktest.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Aligning VMware VMFS on 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, 06 May 2010 23:18:51 -0000 David Newman wrote: > - contacted the maintainer of istgt port, who suggests a possible VMFS > and GEOM problem such as GEOM not recognizing the VMFS format. This is the correct answer. GEOM simply doesn't understand how VMware is formatting the disk. By default, VMware aligns VMFS partitions inside the LUN you give to it, so you don't really have to do anything when using it with ZVOLs. From owner-freebsd-fs@FreeBSD.ORG Thu May 6 23:20:03 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99127106566B for ; Thu, 6 May 2010 23:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 69B228FC15 for ; Thu, 6 May 2010 23:20:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o46NK342041008 for ; Thu, 6 May 2010 23:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o46NK32E041007; Thu, 6 May 2010 23:20:03 GMT (envelope-from gnats) Date: Thu, 6 May 2010 23:20:03 GMT Message-Id: <201005062320.o46NK32E041007@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Tsurutani Naoki Cc: Subject: kern/145309: [disklabel]: Editing disk label invalidates the whole device X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tsurutani Naoki List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2010 23:20:03 -0000 The following reply was made to PR kern/145309; it has been noted by GNATS. From: Tsurutani Naoki To: bug-followup@FreeBSD.org, yar@FreeBSD.org Cc: Subject: kern/145309: [disklabel]: Editing disk label invalidates the whole device Date: Fri, 07 May 2010 08:12:35 +0900 I found bsdlabel: Class not found many times, and I have no solution. I saw it even on single user mode. Please help me, for I cannot update my boot code by bsdlabel -B, and I cannot use ahci. From owner-freebsd-fs@FreeBSD.ORG Thu May 6 23:22:11 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 028561065674 for ; Thu, 6 May 2010 23:22:11 +0000 (UTC) (envelope-from dnewman@networktest.com) Received: from mail3.networktest.com (mail3.networktest.com [69.55.234.60]) by mx1.freebsd.org (Postfix) with ESMTP id D98A28FC12 for ; Thu, 6 May 2010 23:22:10 +0000 (UTC) Received: from localhost (localhost [69.55.234.60]) by mail3.networktest.com (Postfix) with ESMTP id 6979D95933 for ; Thu, 6 May 2010 16:22:10 -0700 (PDT) Received: from mail3.networktest.com ([69.55.234.60]) by localhost (mail3.networktest.com [69.55.234.60]) (amavisd-maia, port 10024) with ESMTP id 98168-04 for ; Thu, 6 May 2010 16:22:10 -0700 (PDT) Received: from dhcp130.eng.networktest.com (ns.networktest.com [216.240.60.130]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dnewman@networktest.com) by mail3.networktest.com (Postfix) with ESMTPSA id 3AF609592D for ; Thu, 6 May 2010 16:22:10 -0700 (PDT) Message-ID: <4BE34F21.6040806@networktest.com> Date: Thu, 06 May 2010 16:22:09 -0700 From: David Newman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 CC: freebsd-fs@freebsd.org References: <4BE33E40.6080905@networktest.com> <4BE34E52.7050407@modulus.org> In-Reply-To: <4BE34E52.7050407@modulus.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Aligning VMware VMFS on 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, 06 May 2010 23:22:11 -0000 On 5/6/10 4:18 PM, Andrew Snow wrote: > David Newman wrote: >> - contacted the maintainer of istgt port, who suggests a possible VMFS >> and GEOM problem such as GEOM not recognizing the VMFS format. > > This is the correct answer. GEOM simply doesn't understand how VMware > is formatting the disk. By default, VMware aligns VMFS partitions > inside the LUN you give to it, so you don't really have to do anything > when using it with ZVOLs. Thanks. So, just so I understand, you're saying there's no alignment possible with VMFS on ZFS -- just ignore those messages and proceed? thanks again dn From owner-freebsd-fs@FreeBSD.ORG Thu May 6 23:24:54 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D5D4B1065675 for ; Thu, 6 May 2010 23:24:54 +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 9A1828FC13 for ; Thu, 6 May 2010 23:24:54 +0000 (UTC) Received: by email.octopus.com.au (Postfix, from userid 1002) id 179C05CB955; Fri, 7 May 2010 09:13:36 +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=4.4 required=10.0 tests=ALL_TRUSTED, DNS_FROM_OPENWHOIS,FH_DATE_PAST_20XX autolearn=no version=3.2.3 Received: from [220.233.52.14] (14.52.233.220.static.exetel.com.au [220.233.52.14]) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 418E05CB8EA; Fri, 7 May 2010 09:13:31 +1000 (EST) Message-ID: <4BE34FBF.30007@modulus.org> Date: Fri, 07 May 2010 09:24:47 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.24 (X11/20100411) MIME-Version: 1.0 To: David Newman , freebsd-fs@freebsd.org References: <4BE33E40.6080905@networktest.com> <4BE34E52.7050407@modulus.org> <4BE34F21.6040806@networktest.com> In-Reply-To: <4BE34F21.6040806@networktest.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Aligning VMware VMFS on 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, 06 May 2010 23:24:54 -0000 David Newman wrote: > Thanks. So, just so I understand, you're saying there's no alignment > possible with VMFS on ZFS -- just ignore those messages and proceed? Yes: with simpler block storage storage systems you need to make sure you assign a LUN that is aligned on the underlying block device. But this is not applicable to ZFS with ZVOLs. From owner-freebsd-fs@FreeBSD.ORG Fri May 7 05:58:49 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D487E1065675 for ; Fri, 7 May 2010 05:58:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id 840588FC13 for ; Fri, 7 May 2010 05:58:48 +0000 (UTC) Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta09.westchester.pa.mail.comcast.net with comcast id EVyn1e0011vXlb859VypLT; Fri, 07 May 2010 05:58:49 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta17.westchester.pa.mail.comcast.net with comcast id EVyn1e00B3S48mS3dVyoih; Fri, 07 May 2010 05:58:48 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 4CBE69B425; Thu, 6 May 2010 22:58:46 -0700 (PDT) Date: Thu, 6 May 2010 22:58:46 -0700 From: Jeremy Chadwick To: Tsurutani Naoki Message-ID: <20100507055846.GA42751@icarus.home.lan> References: <201005062320.o46NK32E041007@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201005062320.o46NK32E041007@freefall.freebsd.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@FreeBSD.org Subject: Re: kern/145309: [disklabel]: Editing disk label invalidates the whole device X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 May 2010 05:58:49 -0000 On Thu, May 06, 2010 at 11:20:03PM +0000, Tsurutani Naoki wrote: > From: Tsurutani Naoki > > I found > bsdlabel: Class not found > many times, and I have no solution. > I saw it even on single user mode. > Please help me, for I cannot update my boot code by > bsdlabel -B, and I cannot use ahci. http://lists.freebsd.org/pipermail/freebsd-fs/2010-April/008312.html http://lists.freebsd.org/pipermail/freebsd-fs/2010-April/008323.html -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri May 7 12:50:04 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0E623106564A for ; Fri, 7 May 2010 12:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id F24228FC15 for ; Fri, 7 May 2010 12:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o47Co3JN057822 for ; Fri, 7 May 2010 12:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o47Co37S057821; Fri, 7 May 2010 12:50:03 GMT (envelope-from gnats) Date: Fri, 7 May 2010 12:50:03 GMT Message-Id: <201005071250.o47Co37S057821@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andrey Simonenko Cc: Subject: Re: kern/136865: NFS exports atomic and on-the-fly atomic updates X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrey Simonenko List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 May 2010 12:50:04 -0000 The following reply was made to PR kern/136865; it has been noted by GNATS. From: Andrey Simonenko To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/136865: NFS exports atomic and on-the-fly atomic updates Date: Fri, 7 May 2010 15:42:48 +0300 New version nfse-20100507 was released. Important changes: * Now there is no any limitation on file system's mount point directory renaming, original file system's mount point directory can be renamed and the NFSE code will work. This is new implementation that does not use f_mntonname values from the struct statfs{}. * Now signals and a socket for control commands in nfse are handled in kqueue(2). * Now NFSE code verifies whether a file system supports NFS exports. * Now NFSE code does not allow symlinks in pathnames in nfs.exports(5). * Now when a file system mounted or unmounted on the local system NFSE code also checks whether NFSv4 root directory still can be exported. URL: http://nfse.sourceforge.net/ From owner-freebsd-fs@FreeBSD.ORG Fri May 7 14:06:48 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8F6F01065672 for ; Fri, 7 May 2010 14:06:48 +0000 (UTC) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (comsys.kpi.ua [77.47.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 11E208FC1F for ; Fri, 7 May 2010 14:06:47 +0000 (UTC) Received: from pm513-1.comsys.kpi.ua ([10.18.52.101] helo=pm513-1.comsys.ntu-kpi.kiev.ua) by comsys.ntu-kpi.kiev.ua with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1OANYQ-0000gT-Gw for freebsd-fs@freebsd.org; Fri, 07 May 2010 16:25:22 +0300 Received: by pm513-1.comsys.ntu-kpi.kiev.ua (Postfix, from userid 1001) id 0AE971CC44; Fri, 7 May 2010 16:25:23 +0300 (EEST) Date: Fri, 7 May 2010 16:25:22 +0300 From: Andrey Simonenko To: freebsd-fs@freebsd.org Message-ID: <20100507132522.GA67068@pm513-1.comsys.ntu-kpi.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Authenticated-User: simon@comsys.ntu-kpi.kiev.ua X-Authenticator: plain X-Invalid-HELO: Host impersonating [comsys.ntu-kpi.kiev.ua] X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.63 (build at 06-Jan-2007 23:14:37) X-Date: 2010-05-07 16:25:22 X-Connected-IP: 10.18.52.101:31192 X-Message-Linecount: 66 X-Body-Linecount: 54 X-Message-Size: 2420 X-Body-Size: 1914 Subject: CFT: nfse compatible mode with mountd (NFS exports file) 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, 07 May 2010 14:06:48 -0000 Hello, NFSE is a new NFS exports support for FreeBSD 9.0-CURRENT and 8.0-STABLE. NFSE distribution consists of changes for the regular and experimental NFS servers and the nfse utility. The nfse utility uses new NFS exports file format that looks like exports(5), but has different semantics of export entities. Also nfse has the compatible mode with mountd that allows to continue to use existent configurations for NFS exports. I made tests on my NFS exports configurations to verify correctness of the compatible mode with mountd, but want to ask other administrators to check nfse with their exports(5) files. Only compilation of the userland program is required, even if you run nfse with wrong options under root privileges it will not modify any NFS exports settings in the kernel, since it uses a new API. How to check: 1. FreeBSD 8.0 or 9.0 is required. 2. Download new version of NFSE updates from http://nfse.sourceforge.net/ 3. Build nfse using the TESTING-BUILD script (result in usr.sbin/nfse/). 4. Run "nfse -Ct /etc/exports" and compare output with your exports(5) file and your understanding of your NFS exports settings (nfse program should be run on the NFS server, it should see mount points). 5. Send me results of testing with comments if possible (here or in a private message). Example (/home is a mount point of some file system): % cat exports /home/simon 1.2.3.4 % ./nfse -Ct exports configure: reading file exports configure: converting configuration to native format Pathname /home Export specifications: -rw -sec sys -maproot=-2:-2 -host 1.2.3.4 Subdirectories for NFSv2/3: /home/simon -host 1.2.3.4 Warning: subdirectories exports are insecure % Since NFS server exports file systems, then here there is one export of file system /home and one administrative subdirectory export from this file system for NFSv2/3 clients. From owner-freebsd-fs@FreeBSD.ORG Fri May 7 21:38:52 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 227291065672; Fri, 7 May 2010 21:38:52 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id EEBC18FC25; Fri, 7 May 2010 21:38:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o47LcpXw010663; Fri, 7 May 2010 21:38:51 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o47LcpKU010659; Fri, 7 May 2010 21:38:51 GMT (envelope-from linimon) Date: Fri, 7 May 2010 21:38:51 GMT Message-Id: <201005072138.o47LcpKU010659@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/146375: [nfs] [patch] Typos in macro variables names in sys/fs/nfs/*.h 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, 07 May 2010 21:38:52 -0000 Old Synopsis: Typos in macro variables names in sys/fs/nfs/*.h New Synopsis: [nfs] [patch] Typos in macro variables names in sys/fs/nfs/*.h Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Fri May 7 21:38:31 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=146375 From owner-freebsd-fs@FreeBSD.ORG Fri May 7 21:40:00 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 06A751065675; Fri, 7 May 2010 21:40:00 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D2BDB8FC08; Fri, 7 May 2010 21:39:59 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o47LdxxG010715; Fri, 7 May 2010 21:39:59 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o47LdxXh010711; Fri, 7 May 2010 21:39:59 GMT (envelope-from linimon) Date: Fri, 7 May 2010 21:39:59 GMT Message-Id: <201005072139.o47LdxXh010711@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/146377: [ppp] [tun] Interface doesn't clear addresses when PPPoE connection closes 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, 07 May 2010 21:40:00 -0000 Old Synopsis: Interface doesn't clear addresses when PPPoE connection closes New Synopsis: [ppp] [tun] Interface doesn't clear addresses when PPPoE connection closes Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Fri May 7 21:39:05 UTC 2010 Responsible-Changed-Why: Assign to wrong mailing list. erk. http://www.freebsd.org/cgi/query-pr.cgi?pr=146377 From owner-freebsd-fs@FreeBSD.ORG Fri May 7 21:40:14 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 780F6106566C; Fri, 7 May 2010 21:40:14 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 500F98FC17; Fri, 7 May 2010 21:40:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o47LeEsM011664; Fri, 7 May 2010 21:40:14 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o47LeESI011660; Fri, 7 May 2010 21:40:14 GMT (envelope-from linimon) Date: Fri, 7 May 2010 21:40:14 GMT Message-Id: <201005072140.o47LeESI011660@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-fs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/146377: [ppp] [tun] Interface doesn't clear addresses when PPPoE connection closes 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, 07 May 2010 21:40:14 -0000 Synopsis: [ppp] [tun] Interface doesn't clear addresses when PPPoE connection closes Responsible-Changed-From-To: freebsd-fs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri May 7 21:40:04 UTC 2010 Responsible-Changed-Why: Assign to right mailing list. http://www.freebsd.org/cgi/query-pr.cgi?pr=146377 From owner-freebsd-fs@FreeBSD.ORG Sat May 8 15:00:14 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E03611065673 for ; Sat, 8 May 2010 15:00:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D14048FC0C for ; Sat, 8 May 2010 15:00:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o48F0Ef8035782 for ; Sat, 8 May 2010 15:00:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o48F0Efb035781; Sat, 8 May 2010 15:00:14 GMT (envelope-from gnats) Date: Sat, 8 May 2010 15:00:14 GMT Message-Id: <201005081500.o48F0Efb035781@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/146375: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 May 2010 15:00:15 -0000 The following reply was made to PR kern/146375; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/146375: commit references a PR Date: Sat, 8 May 2010 14:50:30 +0000 (UTC) Author: rmacklem Date: Sat May 8 14:50:12 2010 New Revision: 207785 URL: http://svn.freebsd.org/changeset/base/207785 Log: Fix typos in macros. PR: kern/146375 Submitted by: simon AT comsys.ntu-kpi.kiev.ua MFC after: 1 week Modified: head/sys/fs/nfs/nfskpiport.h head/sys/fs/nfs/nfsport.h Modified: head/sys/fs/nfs/nfskpiport.h ============================================================================== --- head/sys/fs/nfs/nfskpiport.h Sat May 8 14:12:04 2010 (r207784) +++ head/sys/fs/nfs/nfskpiport.h Sat May 8 14:50:12 2010 (r207785) @@ -27,7 +27,7 @@ */ #ifndef _NFS_NFSKPIPORT_H_ -#define _NFSKPIPORT_NFS_H_ +#define _NFS_NFSKPIPORT_H_ /* * These definitions are needed since the generic code is now using Darwin8 * KPI stuff. (I know, seems a bit silly, but I want the code to build on @@ -70,4 +70,4 @@ typedef struct mbuf * mbuf_t; #define uio_iov_len(p) ((p)->uio_iov->iov_len) #define uio_iov_len_add(p, v) ((p)->uio_iov->iov_len += (v)) -#endif /* _NFSKPIPORT_NFS_H */ +#endif /* _NFS_NFSKPIPORT_H */ Modified: head/sys/fs/nfs/nfsport.h ============================================================================== --- head/sys/fs/nfs/nfsport.h Sat May 8 14:12:04 2010 (r207784) +++ head/sys/fs/nfs/nfsport.h Sat May 8 14:50:12 2010 (r207785) @@ -33,7 +33,7 @@ */ #ifndef _NFS_NFSPORT_H_ -#define _NFSPORT_NFS_H_ +#define _NFS_NFSPORT_H_ /* * In general, I'm not fond of #includes in .h files, but this seems @@ -918,4 +918,4 @@ struct nfsreq { #endif /* _KERNEL */ -#endif /* _NFSPORT_NFS_H */ +#endif /* _NFS_NFSPORT_H */ _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Sat May 8 17:34:39 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BF97106564A for ; Sat, 8 May 2010 17:34:39 +0000 (UTC) (envelope-from yuwen@exodus.cs.ccu.edu.tw) Received: from pya.mail2000.com.tw (pya.mail2000.com.tw [203.69.82.99]) by mx1.freebsd.org (Postfix) with SMTP id 0C6CF8FC1C for ; Sat, 8 May 2010 17:34:38 +0000 (UTC) Received: from 10.0.0.47 by bak3.mail2000.com.tw with Mail2000 ESMTP Server V4.50S(11787:0:AUTH_LOGIN) (envelope-from ); Sun, 09 May 2010 01:34:24 +0800 (CST) Received: By OpenMail Mailer;Sun, 09 May 2010 01:34:21 +0800 (CST) From: "Cheng-Lin Yang" Message-ID: <1273340061.16836.yuwen@exodus.cs.ccu.edu.tw> In-Reply-To: References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> <4BDFE843.7050600@fuujingroup.com> <1273022040.28218.yuwen@exodus.cs.ccu.edu.tw> <20100505013136.GA48843@icarus.home.lan> <1273026479.56161.yuwen@exodus.cs.ccu.edu.tw> To: "rmacklem" Date: Sun, 09 May 2010 01:34:21 +0800 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuwen@exodus.cs.ccu.edu.tw List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 May 2010 17:34:39 -0000 Hi=20Rick=20and=20all, I've=20upgrade=20the=20NFS=20server=20up=20to=20RELENG_8_0=20with=20Rick's=20= patches.=20I=20still=20see=20the=20negative=20"BioW=20Hits"=20on=20my=20Free= BSD=20NFS=20clients=20but=20the=20system=20is=20not=20hanged=20as=20before.=20= So=20I=20would=20say=20somehow=20the=20upgrade=20is=20"partially=20successfu= l"=20to=20solve=20the=20issue. Howerver,=20new=20issue=20bumps=20up=20after=20the=20upgrade,=20My=20mail=20= server=20which=20runs=20Dovecot=20also=20mounted=20on=20NFS=20server,=20show= s=20the=20following=20error=20message=20after=20the=20upgrade =3D=3D=3D=3D May=20=208=2021:46:24=20mail=20dovecot:=20IMAP(USERID):=20fcntl(write-lock)=20= locking=20failed=20for=20file=20cshome/professor/USERID/Maildir/.OLD2/doveco= t.index.log:=20Operation=20not=20supported May=20=208=2021:46:24=20mail=20dovecot:=20IMAP(USERID):=20mail_index_wait_lo= ck_fd()=20failed=20with=20file=20=20cshome/professor/USERID/Maildir/.OLD2/do= vecot.index.log:=20Operation=20not=20supported May=20=208=2021:46:24=20mail=20dovecot:=20IMAP(USERID):=20fcntl(write-lock)=20= locking=20failed=20for=20file=20=20cshome/professor/USERID/Maildir/.OLD2/dov= ecot.index.log:=20Operation=20not=20supported May=20=208=2021:46:24=20mail=20dovecot:=20IMAP(USERID):=20mail_index_wait_lo= ck_fd()=20failed=20with=20file=20/cshome/professor/USERID/Maildir/.OLD2/dove= cot.index.log:=20Operation=20not=20supported =3D=3D=3D=3D Could=20you=20please=20kindly=20take=20a=20look=20on=20this=20new=20issue?=20= Thank=20you.=20:) Regards, Cheng-Lin=20Yang -----Original=20message----- From:Rick=20Macklem=20 To:Cheng-Lin=20Yang=20 Cc:freebsd=20,freebsd-fs=20,lab=20 Date:Wed,=205=20May=202010=2011:11:00=20-0400=20(EDT) Subject:Re:=20Struggling=20on=20NFS=20problem On=20Wed,=205=20May=202010,=20Cheng-Lin=20Yang=20wrote: >=20Hi=20Jeremy, >=20I=20certainly=20will,=20it=20seems=20to=20upgrading=20to=20RELENG_8=20wi= ll=20be=20a=20highly=20possible=20solution=20for=20the=20issue.=20Therefore,= =20I=20already=20scheduled=20a=20upgrade=20window=20on=20this=20Friday=20nig= ht=20and=20will=20keep=20updating=20you=20guys=20the=20result=20once=20the=20= upgrade=20is=20done. > >=20I=20would=20also=20like=20to=20know=20that=20is=20it=20ok=20to=20update=20= the=20source=20up=20to=20RELENG_8=20by=20applying=20all=20NFS=20patches=20at= =20the=20same=20time?=20Since=20it's=20a=20production=20machine,=20I=20have=20= to=20make=20sure=20these=20two=20steps=20can=20be=20perform=20at=20the=20sam= e=20time=20without=20any=20concern. > The=20patches=20at=20people.freebsd.org/~rmacklem=20are=20already=20in=20sta= ble/8,=20so you=20shouldn't=20need=20to=20apply=20them. >=20Finally,=20just=20curious=20that=20why=20the=20problem=20only=20shows=20= up=20on=20FreeBSD=20clients? > If=20it=20is=20the=20case=20where=20the=20server=20doesn't=20return=20ESTALE= =20when=20a=20file has=20been=20deleted=20on=20the=20server,=20the=20FreeBSD=20client=20will=20= loop=20retrying the=20RPC=20for=20EIO,=20but=20other=20clients=20might=20not.=20That=20is=20= the=20only=20case where=20I=20can=20suggest=20there=20is=20a=20difference,=20other=20than=20th= e=20type=20of traffic=20and=20load=20different=20clients=20will=20generate. rick From owner-freebsd-fs@FreeBSD.ORG Sat May 8 19:10:05 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 860711065674 for ; Sat, 8 May 2010 19:10:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 2C7FF8FC16 for ; Sat, 8 May 2010 19:10:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o48JA5tu047818 for ; Sat, 8 May 2010 19:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o48JA58i047816; Sat, 8 May 2010 19:10:05 GMT (envelope-from gnats) Date: Sat, 8 May 2010 19:10:05 GMT Message-Id: <201005081910.o48JA58i047816@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Alistair Phipps Cc: Subject: Re: kern/145778: [zfs] [panic] panic in zfs_fuid_map_id (known issue fixed in opensolaris) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alistair Phipps List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 May 2010 19:10:05 -0000 The following reply was made to PR kern/145778; it has been noted by GNATS. From: Alistair Phipps To: bug-followup@FreeBSD.org, pjd@freebsd.org Cc: Subject: Re: kern/145778: [zfs] [panic] panic in zfs_fuid_map_id (known issue fixed in opensolaris) Date: Sat, 8 May 2010 14:37:08 -0400 The box is crashing nightly with this panic when running /etc/periodic/daily/450.status-security. I figured out how to get a crash dump and think I was too hasty in associating this with the opensolaris bug. Here's the backtrace: #0 doadump () at pcpu.h:246 #1 0x805b1447 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0x805b1739 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:579 #3 0x84cd17ad in zfs_fuid_map_id (zfsvfs=0x86573000, fuid=4294967314, cr=0x86a6c980, type=ZFS_GROUP) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_fuid.c:395 #4 0x84cd181f in zfs_groupmember (zfsvfs=0x86573000, id=Unhandled dwarf expression opcode 0x93 ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_fuid.c:713 #5 0x84ce1a9d in zfs_zaccess_common (zp=0x88033000, v4_mode=Variable "v4_mode" is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_acl.c:2292 #6 0x84ce1dc7 in zfs_zaccess (zp=0x88033000, mode=128, flags=0, skipaclchk=0, cr=0x86a6c980) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_acl.c:2411 #7 0x84cf6ab4 in zfs_freebsd_getattr (ap=0xd6ac7ac4) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:2356 #8 0x80844ea2 in VOP_GETATTR_APV (vop=0x84d5aaa0, a=0xd6ac7ac4) at vnode_if.c:697 #9 0x806490c9 in vn_stat (vp=0x879a5c90, sb=0xd6ac7afc, active_cred=0x86a6c980, file_cred=0x0, td=0x86ff4000) at vnode_if.h:309 #10 0x806404ed in kern_statat_vnhook (td=0x86ff4000, flag=512, fd=-100, path=0x2824b6b8
, pathseg=UIO_USERSPACE, sbp=0xd6ac7c18, hook=0) at /usr/src/sys/kern/vfs_syscalls.c:2358 #11 0x8064062c in kern_statat (td=0x86ff4000, flag=512, fd=-100, path=0x2824b6b8
, pathseg=UIO_USERSPACE, sbp=0xd6ac7c18) at /usr/src/sys/kern/vfs_syscalls.c:2336 #12 0x80640666 in kern_lstat (td=0x86ff4000, path=0x2824b6b8
, pathseg=UIO_USERSPACE, sbp=0xd6ac7c18) at /usr/src/sys/kern/vfs_syscalls.c:2409 #13 0x8064070f in lstat (td=0x86ff4000, uap=0xd6ac7cf8) at /usr/src/sys/kern/vfs_syscalls.c:2399 #14 0x8082fb93 in syscall (frame=0xd6ac7d38) at /usr/src/sys/i386/i386/trap.c:1111 #15 0x80812390 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:261 #16 0x00000033 in ?? () Here's the offending code: #ifdef TODO if (type == ZFS_OWNER || type == ZFS_ACE_USER) { (void) kidmap_getuidbysid(crgetzone(cr), domain, FUID_RID(fuid), &id); } else { (void) kidmap_getgidbysid(crgetzone(cr), domain, FUID_RID(fuid), &id); } #else panic(__func__); #endif The code in opensolaris doesn't have the ifdef TODO block: http://src.opensolaris.org/source/xref/systemz/sirius/usr/src/uts/common/fs/zfs/zfs_fuid.c Based on the function names, it *sounds* as if Windows/CIFS SIDs are stored instead of UIDs when a ZFS partition is accessed using the sharesmb functionality on OpenSolaris. However, sharesmb appears to not be supported under FreeBSD (reports "unsupported share protocol: 1") and it looks like FreeBSD has some unimplemented code where it will panic upon encountering files with associated SIDs set up on OpenSolaris (the TODO block above). Should this be listed on the ZFS known issues page (http://wiki.freebsd.org/ZFS)? Is there a workaround for this, e.g. some way to strip the SIDs from my ZFS? I don't have a need to preserve them. If I change the panic line to return 0, will that make the offending files owned by root? Thanks for any help. From owner-freebsd-fs@FreeBSD.ORG Sat May 8 23:50:04 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E1B01065677 for ; Sat, 8 May 2010 23:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 64CA18FC0A for ; Sat, 8 May 2010 23:50:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o48No4Eo087281 for ; Sat, 8 May 2010 23:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o48No4S2087280; Sat, 8 May 2010 23:50:04 GMT (envelope-from gnats) Date: Sat, 8 May 2010 23:50:04 GMT Message-Id: <201005082350.o48No4S2087280@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Alistair Phipps Cc: Subject: Re: kern/145778: [zfs] [panic] panic in zfs_fuid_map_id (known issue fixed in opensolaris) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alistair Phipps List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 May 2010 23:50:04 -0000 The following reply was made to PR kern/145778; it has been noted by GNATS. From: Alistair Phipps To: bug-followup@freebsd.org, pjd@freebsd.org Cc: Subject: Re: kern/145778: [zfs] [panic] panic in zfs_fuid_map_id (known issue fixed in opensolaris) Date: Sat, 8 May 2010 19:40:22 -0400 I tried changing the panic to a return (uid_t) 0; and it seems to have worked -- no more panic and I'm able to access my files. This seems to be an acceptable workaround for others in the same situation. I think the files now have uid/gid 0 (root:wheel) which could be a security risk on a multi-user system.