From owner-freebsd-fs@FreeBSD.ORG Sun Aug 23 18:38:56 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B6B2106568F; Sun, 23 Aug 2009 18:38:56 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 530338FC19; Sun, 23 Aug 2009 18:38:56 +0000 (UTC) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7NIcuHs018290; Sun, 23 Aug 2009 18:38:56 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7NIcudt018286; Sun, 23 Aug 2009 18:38:56 GMT (envelope-from remko) Date: Sun, 23 Aug 2009 18:38:56 GMT Message-Id: <200908231838.n7NIcudt018286@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: kern/138109: extfs: Minor cleanups to the sys/gnu/fs/ext2fs based on BSD Lite2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 18:38:56 -0000 Old Synopsis: Minor cleanups to the sys/gnu/fs/ext2fs based on BSD Lite2 New Synopsis: extfs: Minor cleanups to the sys/gnu/fs/ext2fs based on BSD Lite2 Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: remko Responsible-Changed-When: Sun Aug 23 18:38:42 UTC 2009 Responsible-Changed-Why: reassign to -fs team. http://www.freebsd.org/cgi/query-pr.cgi?pr=138109 From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 04:20:02 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BC37106568B for ; Mon, 24 Aug 2009 04:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 50BF28FC18 for ; Mon, 24 Aug 2009 04:20:02 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7O4K2IX093422 for ; Mon, 24 Aug 2009 04:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7O4K25S093421; Mon, 24 Aug 2009 04:20:02 GMT (envelope-from gnats) Date: Mon, 24 Aug 2009 04:20:02 GMT Message-Id: <200908240420.n7O4K25S093421@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Aditya Sarawgi Cc: Subject: Re: kern/138109: extfs: Minor cleanups to the sys/gnu/fs/ext2fs based on BSD Lite2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Aditya Sarawgi List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 04:20:02 -0000 The following reply was made to PR kern/138109; it has been noted by GNATS. From: Aditya Sarawgi To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/138109: extfs: Minor cleanups to the sys/gnu/fs/ext2fs based on BSD Lite2 Date: Mon, 24 Aug 2009 03:45:46 +0530 I have merged these changes in my perforce branch. Please refer http://p4db.freebsd.org/branchView.cgi?BRANCH=truncs_ext2fs Cheers, Aditya Sarawgi From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 11:06:54 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 943941065693 for ; Mon, 24 Aug 2009 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 828758FC25 for ; Mon, 24 Aug 2009 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7OB6sTj048558 for ; Mon, 24 Aug 2009 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7OB6rNd048554 for freebsd-fs@FreeBSD.org; Mon, 24 Aug 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Aug 2009 11:06:53 GMT Message-Id: <200908241106.n7OB6rNd048554@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, 24 Aug 2009 11:06:54 -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/138109 fs [extfs] [patch] Minor cleanups to the sys/gnu/fs/ext2f 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/136942 fs [zfs] zvol resize not reflected until reboot 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/136218 fs [zfs] Exported ZFS pools can't be imported into (Open) o kern/135594 fs [zfs] Single dataset unresponsive with Samba o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135480 fs [zfs] panic: lock &arg.lock already initialized o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o bin/135314 fs [zfs] assertion failed for zdb(8) usage o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot f kern/134496 fs [zfs] [panic] ZFS pool export occasionally causes a ke o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133980 fs [panic] [ffs] panic: ffs_valloc: dup alloc o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [smbfs] [panic] panic: ffs_truncate: read-only filesys o kern/133373 fs [zfs] umass attachment causes ZFS checksum errors, dat o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/133134 fs [zfs] Missing ZFS zpool labels o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132597 fs [tmpfs] [panic] tmpfs-related panic while interrupting o kern/132551 fs [zfs] ZFS locks up on extattr_list_link syscall o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes f kern/132068 fs [zfs] page fault when using ZFS over NFS on 7.1-RELEAS o kern/131995 fs [nfs] Failure to mount NFSv4 server o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/131086 fs [ext2fs] [patch] mkfs.ext2 creates rotten partition o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129148 fs [zfs] [panic] panic on concurrent writing & rollback 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/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127659 fs [tmpfs] tmpfs memory leak o kern/127492 fs [zfs] System hang on ZFS input-output o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/125644 fs [zfs] [panic] zfs unfixable fs errors caused panic whe f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o kern/122173 fs [zfs] [panic] Kernel Panic if attempting to replace a o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o kern/122047 fs [ext2fs] [patch] incorrect handling of UF_IMMUTABLE / o kern/122038 fs [tmpfs] [panic] tmpfs: panic: tmpfs_alloc_vp: type 0xc o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o kern/121770 fs [zfs] ZFS on i386, large file or heavy I/O leads to ke o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o bin/120288 fs zfs(8): "zfs share -a" does not send SIGHUP to mountd 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 misc/118855 fs [zfs] ZFS-related commands are nonfunctional in fixit o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118320 fs [zfs] [patch] NFS SETATTR sometimes fails to set file 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 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 kern/113180 fs [zfs] Setting ZFS nfsshare property does not cause inh o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] mount_msdosfs: msdosfs_iconv: Operation not o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/105093 fs [ext2fs] [patch] ext2fs on read-only media cannot be m o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist 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/89991 fs [ufs] softupdates with mount -ur causes fs UNREFS o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o kern/85326 fs [smbfs] [panic] saving a file via samba to an overquot o kern/84589 fs [2TB] 5.4-STABLE unresponsive during background fsck 2 o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o kern/77826 fs [ext2fs] ext2fs usb filesystem will not mount RW o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 150 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 11:52:51 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 645F31065672; Mon, 24 Aug 2009 11:52:51 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3BE858FC1A; Mon, 24 Aug 2009 11:52:51 +0000 (UTC) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7OBqpxh004646; Mon, 24 Aug 2009 11:52:51 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7OBqp0O004642; Mon, 24 Aug 2009 11:52:51 GMT (envelope-from linimon) Date: Mon, 24 Aug 2009 11:52:51 GMT Message-Id: <200908241152.n7OBqp0O004642@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/131441: [unionfs] [nullfs] unionfs and/or nullfs not combineable 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, 24 Aug 2009 11:52:51 -0000 Old Synopsis: unionfs and/or nullfs not combineable New Synopsis: [unionfs] [nullfs] unionfs and/or nullfs not combineable Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Aug 24 11:52:30 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131441 From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 12:28:43 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EA2C106568E for ; Mon, 24 Aug 2009 12:28:43 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id C86BA8FC19 for ; Mon, 24 Aug 2009 12:28:42 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MfXva-0009Cm-L2 for freebsd-fs@freebsd.org; Mon, 24 Aug 2009 13:41:34 +0200 Received: from [206.161.120.61] (helo=[192.168.5.15]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MfXvW-000ANr-0W for freebsd-fs@freebsd.org; Mon, 24 Aug 2009 15:41:30 +0400 Message-ID: <4A927CB3.3040402@plus-plus.su> Date: Mon, 24 Aug 2009 15:42:43 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: need help with 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: Mon, 24 Aug 2009 12:28:43 -0000 Greetings gentlemen, I need your help with ZFS -- how I can diagnose, debug ZFS crashes, and if possible make it more stable. We're running raidz pool and we're having hard time to get it running smooth -- ZFS simply crashes as soon as we put some load on it. Couple months back we've built custom server to replace our old storage system. New server has 7 x 1GB SATA drives, Intel Q6600 Quad core CPU, 8GB RAM. OS: FreeBSD 7.2-RELEASE-p2 amd64, stock GENERIC kernel. So I decided to try ZFS, and I was amazed by it's features. I've read ZFS wiki page and my loader.conf follows: zen# cat loader.conf vm.kmem_size="1536M" vm.kmem_size_max="3072M" vm.pmap.shpgperproc="1024" vfs.zfs.arc_min="256M" vfs.zfs.arc_max="384M" vfs.zfs.vdev.cache.size="50M" vfs.zfs.prefetch_disable="1" kern.maxproc="20000" zen# and zen# zpool status pool: datapool state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM datapool ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad24 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad18 ONLINE 0 0 0 ad20 ONLINE 0 0 0 ad22 ONLINE 0 0 0 ad10 ONLINE 0 0 0 spares ad26 AVAIL errors: No known data errors zen# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT datapool 5.44T 3.54T 1.90T 65% ONLINE - zen# Problem starts as soon as we put some load on FS - e.g. last night I tried to rsync 1TB of different files from above ZFS pool to single hard drive (partitioned UFS2), but server crashed and restarted after copying ~700GB of data. I also tried to stress-test it by running 100 torrent downloads (using rtorrent), and server also crashes and restarts after running for about 30-40 minutes. My guess these crashes happen due to big load on filesystem - ZFS eats all available memory and then server simply crashes. Right now I'm completely lost - I can't even copy 1TB from ZFS to another partition.. How can I diagnose the issue? Is there anything available to make ZFS more stable? Thanks, Mikhail. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 12:57:40 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72295106564A for ; Mon, 24 Aug 2009 12:57:40 +0000 (UTC) (envelope-from p.christias@noc.ntua.gr) Received: from achilles.noc.ntua.gr (achilles.noc.ntua.gr [IPv6:2001:648:2000:de::210]) by mx1.freebsd.org (Postfix) with ESMTP id C88398FC08 for ; Mon, 24 Aug 2009 12:57:39 +0000 (UTC) Received: from ajax.noc.ntua.gr (ajax6.noc.ntua.gr [IPv6:2001:648:2000:dc::1]) by achilles.noc.ntua.gr (8.14.3/8.14.3) with ESMTP id n7OCvbjJ027060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Aug 2009 15:57:37 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) Received: from ajax.noc.ntua.gr (localhost [127.0.0.1]) by ajax.noc.ntua.gr (8.14.3/8.14.3) with ESMTP id n7OCvbge094090 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Aug 2009 15:57:37 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) Received: (from christia@localhost) by ajax.noc.ntua.gr (8.14.3/8.14.3/Submit) id n7OCvbrC094089; Mon, 24 Aug 2009 15:57:37 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) X-Authentication-Warning: ajax.noc.ntua.gr: christia set sender to p.christias@noc.ntua.gr using -f Date: Mon, 24 Aug 2009 15:57:37 +0300 From: Panagiotis Christias To: "Mikhail (Plus Plus)" Message-ID: <20090824125737.GA92643@noc.ntua.gr> References: <4A927CB3.3040402@plus-plus.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A927CB3.3040402@plus-plus.su> User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on achilles.noc.ntua.gr X-Virus-Scanned: clamav-milter 0.95.2 at ajax.noc.ntua.gr X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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: Mon, 24 Aug 2009 12:57:40 -0000 On Mon, Aug 24, 2009 at 03:42:43PM +0400, Mikhail (Plus Plus) wrote: > Greetings gentlemen, > > I need your help with ZFS -- how I can diagnose, debug ZFS crashes, and > if possible make it more stable. We're running raidz pool and we're > having hard time to get it running smooth -- ZFS simply crashes as soon > as we put some load on it. > > Couple months back we've built custom server to replace our old storage > system. New server has 7 x 1GB SATA drives, Intel Q6600 Quad core CPU, > 8GB RAM. OS: FreeBSD 7.2-RELEASE-p2 amd64, stock GENERIC kernel. > > So I decided to try ZFS, and I was amazed by it's features. I've read > ZFS wiki page and my loader.conf follows: > > zen# cat loader.conf > vm.kmem_size="1536M" > vm.kmem_size_max="3072M" > vm.pmap.shpgperproc="1024" > vfs.zfs.arc_min="256M" > vfs.zfs.arc_max="384M" > vfs.zfs.vdev.cache.size="50M" > vfs.zfs.prefetch_disable="1" > kern.maxproc="20000" > zen# > > and > > zen# zpool status > pool: datapool > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > datapool ONLINE 0 0 0 > raidz1 ONLINE 0 0 0 > ad24 ONLINE 0 0 0 > ad8 ONLINE 0 0 0 > ad18 ONLINE 0 0 0 > ad20 ONLINE 0 0 0 > ad22 ONLINE 0 0 0 > ad10 ONLINE 0 0 0 > spares > ad26 AVAIL > > errors: No known data errors > zen# zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > datapool 5.44T 3.54T 1.90T 65% ONLINE - > zen# > > > Problem starts as soon as we put some load on FS - e.g. last night I > tried to rsync 1TB of different files from above ZFS pool to single hard > drive (partitioned UFS2), but server crashed and restarted after > copying ~700GB of data. I also tried to stress-test it by running 100 > torrent downloads (using rtorrent), and server also crashes and restarts > after running for about 30-40 minutes. > My guess these crashes happen due to big load on filesystem - ZFS eats > all available memory and then server simply crashes. > > Right now I'm completely lost - I can't even copy 1TB from ZFS to > another partition.. > How can I diagnose the issue? Is there anything available to make ZFS > more stable? I would suggest you try FreeBSD 8.0 that includes the latest version of ZFS (version 13), which fixed several problems present in 7.x. Then, check for crash dumps (see dumpon(8)), collect any available info and sent it to the list. Regards, Panagiotis -- Panagiotis J. Christias Network Management Center P.Christias@noc.ntua.gr National Technical Univ. of Athens, GREECE From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 13:04:44 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51F82106568D for ; Mon, 24 Aug 2009 13:04:44 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id 15B658FC0A for ; Mon, 24 Aug 2009 13:04:44 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MfZE2-000Gpd-JK; Mon, 24 Aug 2009 15:04:42 +0200 Received: from [206.161.120.61] (helo=[192.168.5.15]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MfZDy-000BE1-8c; Mon, 24 Aug 2009 17:04:38 +0400 Message-ID: <4A92902F.70606@plus-plus.su> Date: Mon, 24 Aug 2009 17:05:51 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Panagiotis Christias References: <4A927CB3.3040402@plus-plus.su> <20090824125737.GA92643@noc.ntua.gr> In-Reply-To: <20090824125737.GA92643@noc.ntua.gr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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: Mon, 24 Aug 2009 13:04:44 -0000 Panagiotis Christias wrote: > I would suggest you try FreeBSD 8.0 that includes the latest version of > ZFS (version 13), which fixed several problems present in 7.x. Then, > check for crash dumps (see dumpon(8)), collect any available info and > sent it to the list. > Does that mean I will have to format my current zpool in order to "upgrade" to ZFS v13? And if it is true then another problem is that I have to backup current data somewhere before I'll be able to format zpool to new version, but I cannot do this because server simply crashes every time I try to copy that much of data to another hdd. Mikhail. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 14:17:58 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 102D4106568D for ; Mon, 24 Aug 2009 14:17:58 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id CE2478FC08 for ; Mon, 24 Aug 2009 14:17:56 +0000 (UTC) Received: (qmail 60650 invoked from network); 24 Aug 2009 14:17:36 -0000 Received: from unknown (HELO ?10.0.0.135?) (spawk@128.238.64.31) by acm.poly.edu with AES256-SHA encrypted SMTP; 24 Aug 2009 14:17:36 -0000 Message-ID: <4A92A0E9.1060508@acm.poly.edu> Date: Mon, 24 Aug 2009 10:17:13 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.19 (X11/20090108) MIME-Version: 1.0 To: "Mikhail (Plus Plus)" References: <4A927CB3.3040402@plus-plus.su> <20090824125737.GA92643@noc.ntua.gr> <4A92902F.70606@plus-plus.su> In-Reply-To: <4A92902F.70606@plus-plus.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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: Mon, 24 Aug 2009 14:17:58 -0000 Mikhail (Plus Plus) wrote: > Panagiotis Christias wrote: > > I would suggest you try FreeBSD 8.0 that includes the latest > version of >> ZFS (version 13), which fixed several problems present in 7.x. Then, >> check for crash dumps (see dumpon(8)), collect any available info and >> sent it to the list. >> > > Does that mean I will have to format my current zpool in order to > "upgrade" to ZFS v13? And if it is true then another problem is that I > have to backup current data somewhere before I'll be able to format > zpool to new version, but I cannot do this because server simply > crashes every time I try to copy that much of data to another hdd. > > Mikhail. > _______________________________________________ > 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" ZFS version 13 refers to two things: the ZFS code, and the on-disk format. Most, if not all of your problems will probably be resolved by upgrading to the new code, as found in 7.2-STABLE and 8.0. New versions of the code are backwards compatible with old on-disk formats. Should you decide to upgrade to the new on-disk format with "zfs set version=3" and "zpool upgrade," the process is documented as keeping your data intact. While it is always a good idea to back up your data before potentially-dangerous filesystem operations, I, along with many other people, have upgraded ZFS on-disk formats without issue. -Boris From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 14:40:04 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B558106568B for ; Mon, 24 Aug 2009 14:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 08C508FC17 for ; Mon, 24 Aug 2009 14:40:04 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7OEe35S072162 for ; Mon, 24 Aug 2009 14:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7OEe3EZ072161; Mon, 24 Aug 2009 14:40:03 GMT (envelope-from gnats) Date: Mon, 24 Aug 2009 14:40:03 GMT Message-Id: <200908241440.n7OEe3EZ072161@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Bruce Evans Cc: Subject: Re: kern/138109: Minor cleanups to the sys/gnu/fs/ext2fs based on BSD Lite2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Evans List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 14:40:04 -0000 The following reply was made to PR kern/138109; it has been noted by GNATS. From: Bruce Evans To: "Pedro F. Giffuni" Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/138109: Minor cleanups to the sys/gnu/fs/ext2fs based on BSD Lite2 Date: Mon, 24 Aug 2009 23:14:47 +1000 (EST) On Sun, 23 Aug 2009, Pedro F. Giffuni wrote: >> Description: > I have been looking at some of the FFS BSD-lite2 fixes to apply them to our ext2fs (based on an older FFS1 from BSD lites). This is helping getting some of the code more in sync with the NetBSD implementation. Please don't format mail for 200+ column terminals. > I am still missing some bigger changes but for now here are pretty simple cleanups, based on these FFS changes: > > ffs_inode.c > ------------ > Use the correct flags (IO_SYNC -> B_SYNC) when deciding to do a sync or > async write in the section that changes the filesize. The bug resulted > in the updates always being async. I tested this a bit after you told me about it a few months ago. > ffs_vfsops.c > ------------- > Speed up for vfs_bio -- addition of a routine bqrelse to greatly diminish > overhead for merged cache. Interesting. I've used this for many years, but didn't notice it reducing overheads. The changes involving vnode_pager_setsize() seem to be bugs: >> How-To-Repeat: > >> Fix: > diff -ruN ext2fs.orig/ext2_inode.c ext2fs/ext2_inode.c > --- ext2fs.orig/ext2_inode.c 2009-08-18 20:32:13.000000000 -0500 > +++ ext2fs/ext2_inode.c 2009-08-23 12:37:18.000000000 -0500 > @@ -126,16 +126,16 @@ > long count, nblocks, blocksreleased = 0; > int aflags, error, i, allerror; > off_t osize; > -/* -printf("ext2_truncate called %d to %d\n", VTOI(ovp)->i_number, length); > -*/ /* > + > + /* > * negative file sizes will totally break the code below and > * are not meaningful anyways. > + * XXX: We should check for max file size here too. > */ > + oip = VTOI(ovp); > if (length < 0) > - return EFBIG; > + return EINVAL; Should also fix the style bugs (indentation, and missing parentheses). These style bugs are missing in the ffs version. > > - oip = VTOI(ovp); > if (ovp->v_type == VLNK && > oip->i_size < ovp->v_mount->mnt_maxsymlinklen) { > #ifdef DIAGNOSTIC This code should be almost identical with that in ffs, and now almost is. Did you get if from FreeBSD or NetBSD? The comments in it don't seem necessary. ffs doesn't have them. Both check for maxfilesize, but only ffs does it at this point, before the VLNK code, but after the extended attributes code). It may be technically correct to not check maxfilesize for either symlinks or extended attributes, since maxfilesize only applies to regular files, but maxfilesize should be larger so checking it first is harmless. ffs is now inconsisent about this for symlinks versus extended attributes. FreeBSD history shows that it is ffs that has the misplaced check for maxfilesize. Lite1 was just missing the check. Lite2 added it where ext2fs has it now. FreeBSD already had it when Lite2 was merged in ffs_inode.c 1.24. FreeBSD had it up-front, and FreeBSD had the wrong error code value for the (length < 0) case (like ext2fs has now). Rev.1.24 merged Lite2 incompletely by fixing the error code but not moving the maxfilesize check. > ... > @@ -167,12 +167,13 @@ > aflags = B_CLRBUF; > if (flags & IO_SYNC) > aflags |= B_SYNC; > - vnode_pager_setsize(ovp, length); Moving this is dangerous. It is inconsistent with ffs and seems wrong. Don't copy NetBSD for this. dyson!@ had to fix many misplaced calls to vnode_pager_setsize(). > - if ((error = ext2_balloc(oip, lbn, offset + 1, cred, &bp, > - aflags)) != 0) > + error = ext2_balloc(oip, lbn, offset + 1, cred, > + &bp, aflags); This line no longer needs splitting. > + if (error) > return (error); Another old bug is not restoring the size on error. This was fixed in ffs (but not here :-() just this year (ffs_inode.c 1.115). Presumably the old code delayed the setting until the space was allocated to avoid having to clean up and/or to avoid having an inconsistent setting while allocating, but in FreeBSD it is necessary to increase the vm size while allocating. > oip->i_size = length; > - if (aflags & IO_SYNC) > + vnode_pager_setsize(ovp, length); Don't move this -- see above. > + if (aflags & B_SYNC) > bwrite(bp); > else > bawrite(bp); > @@ -195,18 +196,20 @@ > aflags = B_CLRBUF; > if (flags & IO_SYNC) > aflags |= B_SYNC; > - if ((error = ext2_balloc(oip, lbn, offset, cred, &bp, > - aflags)) != 0) > + ext2_balloc(oip, lbn, offset, cred, &bp, > + aflags) This line shouldn't be split, much more so than the one above. > + if (error) > return (error); Another place that is missing restoring the vm size on error. > oip->i_size = length; > size = blksize(fs, oip, lbn); > bzero((char *)bp->b_data + offset, (u_int)(size - offset)); > allocbuf(bp, size); > - if (aflags & IO_SYNC) > + if (aflags & B_SYNC) > bwrite(bp); > else > bawrite(bp); > } > + vnode_pager_setsize(ovp, length); Don't move this... > /* > * Calculate index into inode's block list of > * last direct and indirect blocks (if any) > diff -ruN ext2fs.orig/ext2_vfsops.c ext2fs/ext2_vfsops.c > --- ext2fs.orig/ext2_vfsops.c 2009-08-18 20:32:13.000000000 -0500 > +++ ext2fs/ext2_vfsops.c 2009-08-23 12:40:27.000000000 -0500 > @@ -171,10 +171,7 @@ > flags = WRITECLOSE; > if (mp->mnt_flag & MNT_FORCE) > flags |= FORCECLOSE; > - if (vfs_busy(mp, LK_NOWAIT, 0, td)) > - return (EBUSY); > error = ext2_flushfiles(mp, flags, td); > - vfs_unbusy(mp, td); > if (!error && fs->s_wasvalid) { > fs->s_es->s_state |= EXT2_VALID_FS; > ext2_sbupdate(ump, MNT_WAIT); Consistent with ffs, but I don't understand it. > @@ -496,10 +493,10 @@ > * Things to do to update the mount: > * 1) invalidate all cached meta-data. > * 2) re-read superblock from disk. > - * 3) re-read summary information from disk. > - * 4) invalidate all inactive vnodes. > - * 5) invalidate all cached file data. > - * 6) re-read inode data for all active vnodes. > + * 3) (re-read summary information from disk.) > + * - (invalidate all inactive vnodes.) > + * 4) invalidate all cached file data. > + * 5) re-read inode data for all active vnodes. > */ > static int > ext2_reload(struct mount *mp, struct thread *td) Don't renumber this. The meaning of the parentheses is unclear. IIRC, ext2fs doesn't do all the steps here, but it should. Use descriptive comments instead of parentheses to say which ones. > @@ -1007,8 +1004,8 @@ > * still zero, it will be unlinked and returned to the free > * list by vput(). > */ > - vput(vp); > brelse(bp); > + vput(vp); > *vpp = NULL; > return (error); > } Consistent with ffs, and seems to be needed (not just a style fix). > @@ -1032,7 +1029,7 @@ > /* > ext2_print_inode(ip); > */ > - brelse(bp); > + bqrelse(bp); > > /* > * Initialize the vnode from the inode, check for aliases. Though I use it, I'm not sure about the safety of this. Bruce From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 17:01:59 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53AC8106568E for ; Mon, 24 Aug 2009 17:01:59 +0000 (UTC) (envelope-from matt@corp.spry.com) Received: from mail-px0-f198.google.com (mail-px0-f198.google.com [209.85.216.198]) by mx1.freebsd.org (Postfix) with ESMTP id 331D38FC18 for ; Mon, 24 Aug 2009 17:01:58 +0000 (UTC) Received: by pxi36 with SMTP id 36so5074566pxi.7 for ; Mon, 24 Aug 2009 10:01:58 -0700 (PDT) Received: by 10.114.162.33 with SMTP id k33mr6257763wae.128.1251133318571; Mon, 24 Aug 2009 10:01:58 -0700 (PDT) Received: from mattintosh.spry.com (isaid.donotdelete.com [64.79.222.10]) by mx.google.com with ESMTPS id 20sm956622pzk.5.2009.08.24.10.01.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 Aug 2009 10:01:57 -0700 (PDT) Message-Id: <7A60E3BB-04DB-4272-9052-7477FC10DBBA@spry.com> From: Matt Simerson To: freebsd-fs@freebsd.org In-Reply-To: <4A92902F.70606@plus-plus.su> 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, 24 Aug 2009 10:01:56 -0700 References: <4A927CB3.3040402@plus-plus.su> <20090824125737.GA92643@noc.ntua.gr> <4A92902F.70606@plus-plus.su> X-Mailer: Apple Mail (2.936) Subject: Re: need help with 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: Mon, 24 Aug 2009 17:01:59 -0000 On Aug 24, 2009, at 6:05 AM, Mikhail (Plus Plus) wrote: > Panagiotis Christias wrote: >> I would suggest you try FreeBSD 8.0 that includes the latest >> version of >> ZFS (version 13), which fixed several problems present in 7.x. >> Then, check for crash dumps (see dumpon(8)), collect any available >> info and >> sent it to the list. I second this recommendation. The ZFS code in 8.0 is considerably more stable than what's currently in 7.2-STABLE. > Does that mean I will have to format my current zpool in order to > "upgrade" to ZFS v13? And if it is true then another problem is that > I have to backup current data somewhere before I'll be able to > format zpool to new version, but I cannot do this because server > simply crashes every time I try to copy that much of data to another > hdd. Not at all. Simply install 8.0 and do a zpool upgrade. Matt From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 17:44:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1338E106568C for ; Mon, 24 Aug 2009 17:44:04 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 8F73B8FC20 for ; Mon, 24 Aug 2009 17:44:03 +0000 (UTC) Received: by ewy5 with SMTP id 5so1134292ewy.36 for ; Mon, 24 Aug 2009 10:44:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.54.202 with SMTP id i52mr969940wec.196.1251134060728; Mon, 24 Aug 2009 10:14:20 -0700 (PDT) In-Reply-To: <7A60E3BB-04DB-4272-9052-7477FC10DBBA@spry.com> References: <4A927CB3.3040402@plus-plus.su> <20090824125737.GA92643@noc.ntua.gr> <4A92902F.70606@plus-plus.su> <7A60E3BB-04DB-4272-9052-7477FC10DBBA@spry.com> Date: Mon, 24 Aug 2009 19:14:20 +0200 Message-ID: <367b2c980908241014l425b48e3uea765a51f0447ea3@mail.gmail.com> From: Olivier Smedts To: Matt Simerson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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: Mon, 24 Aug 2009 17:44:04 -0000 2009/8/24 Matt Simerson : > > On Aug 24, 2009, at 6:05 AM, Mikhail (Plus Plus) wrote: > >> Panagiotis Christias wrote: >>> >>> I would suggest you try FreeBSD 8.0 that includes the latest version of >>> ZFS (version 13), which fixed several problems present in 7.x. Then, >>> check for crash dumps (see dumpon(8)), collect any available info and >>> sent it to the list. > > I second this recommendation. The ZFS code in 8.0 is considerably more > stable than what's currently in 7.2-STABLE. > >> Does that mean I will have to format my current zpool in order to >> "upgrade" to ZFS v13? And if it is true then another problem is that I have >> to backup current data somewhere before I'll be able to format zpool to new >> version, but I cannot do this because server simply crashes every time I try >> to copy that much of data to another hdd. > > Not at all. Simply install 8.0 and do a zpool upgrade. And don't forget to zfs upgrade after the zpool upgrade ! > > Matt > _______________________________________________ > 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" > -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 18:55:11 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A95A8106568C for ; Mon, 24 Aug 2009 18:55:11 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 40EE88FC08 for ; Mon, 24 Aug 2009 18:55:10 +0000 (UTC) Received: by ewy5 with SMTP id 5so1197369ewy.36 for ; Mon, 24 Aug 2009 11:55:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=4dqgGPkfoXlhP5cq8HopPL/HDwrGu229Xe+iV3+INcM=; b=peVAdqNbnnlErtJUPFGTX6iYClZ4cwA/Ts9YvJIh31f7n+WikWNd8jZoLGadaCtf3W 4pwPFwGuLF/6t/yd9FF9o4SpZUzpzb7LE4MIMhP3kh816xTlsZavD7VTeuVY8rBv/LCS cPxgEZ6uJ3CeR370HHcwXSyfjKlp0dShqLWWs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=j41jUdylQUzWNPe52eqEN2gniuh8d8w2fOokwkhYKpVwVT7gmseFjbGKKzyphtdwBi wJmWYyc5rI6cC+4oH+5HQc7/aD2XKfT05IMLE/W6FGih5EBBHS9jLhEK0eOtERwnytJg QAvjAcprzt5zhJl6J+EvaA8Cjlxe5BSWga1QQ= MIME-Version: 1.0 Received: by 10.210.137.18 with SMTP id k18mr5259646ebd.63.1251138834763; Mon, 24 Aug 2009 11:33:54 -0700 (PDT) Date: Mon, 24 Aug 2009 14:33:54 -0400 Message-ID: From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ZFS versions [was: need help] 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, 24 Aug 2009 18:55:11 -0000 FYI There are both zpool and zfs versions. They are independant. Though to fully enable some features both need upgraded. See zpool(1M), zfs(1M) and the ticket/psarc cases listed in the urls for more. The canonical references and utilities [read-only] are: http://opensolaris.org/os/community/zfs/version/n/ zpool upgrade -v zpool upgrade http://opensolaris.org/os/community/zfs/version/zpl/n/ zfs upgrade -v zfs upgrade The parameter setting method is not preferred. FreeBSD RELENG_7 and above are at: zpool 13 zfs 3 OpenSolaris is at: zpool 18 zfs 4 From owner-freebsd-fs@FreeBSD.ORG Mon Aug 24 20:09:42 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04BB9106568C for ; Mon, 24 Aug 2009 20:09:42 +0000 (UTC) (envelope-from p.christias@noc.ntua.gr) Received: from diomedes.noc.ntua.gr (diomedes.noc.ntua.gr [IPv6:2001:648:2000:de::220]) by mx1.freebsd.org (Postfix) with ESMTP id A65CB8FC19 for ; Mon, 24 Aug 2009 20:09:40 +0000 (UTC) Received: from ajax.noc.ntua.gr (ajax6.noc.ntua.gr [IPv6:2001:648:2000:dc::1]) by diomedes.noc.ntua.gr (8.14.3/8.14.3) with ESMTP id n7OK9dva098924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 24 Aug 2009 23:09:39 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) Received: from ajax.noc.ntua.gr (localhost [127.0.0.1]) by ajax.noc.ntua.gr (8.14.3/8.14.3) with ESMTP id n7OK9cw0019023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 24 Aug 2009 23:09:39 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) Received: (from christia@localhost) by ajax.noc.ntua.gr (8.14.3/8.14.3/Submit) id n7OK9cMV019022 for freebsd-fs@freebsd.org; Mon, 24 Aug 2009 23:09:38 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) X-Authentication-Warning: ajax.noc.ntua.gr: christia set sender to p.christias@noc.ntua.gr using -f Date: Mon, 24 Aug 2009 23:09:38 +0300 From: Panagiotis Christias To: freebsd-fs@freebsd.org Message-ID: <20090824200938.GB13590@noc.ntua.gr> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: clamav-milter 0.95.2 at diomedes.noc.ntua.gr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (diomedes.noc.ntua.gr [IPv6:2001:648:2000:de::220]); Mon, 24 Aug 2009 23:09:39 +0300 (EEST) Subject: Re: ZFS versions [was: need help] 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, 24 Aug 2009 20:09:42 -0000 On Mon, Aug 24, 2009 at 02:33:54PM -0400, grarpamp wrote: > FYI > There are both zpool and zfs versions. > They are independant. Though to fully enable some > features both need upgraded. See zpool(1M), zfs(1M) > and the ticket/psarc cases listed in the urls for more. > > The canonical references and utilities [read-only] are: > > http://opensolaris.org/os/community/zfs/version/n/ > zpool upgrade -v > zpool upgrade > http://opensolaris.org/os/community/zfs/version/zpl/n/ > zfs upgrade -v > zfs upgrade > > The parameter setting method is not preferred. > > FreeBSD RELENG_7 and above are at: > zpool 13 > zfs 3 > > OpenSolaris is at: > zpool 18 > zfs 4 Very useful information. http://wiki.freebsd.org/ZFS would be a good place for it. What I had in mind was the latest MFC regarding ZFS (pool) version 13 on May 20th (two weeks after the 7.2 release): http://svn.freebsd.org/viewvc/base?view=revision&revision=192498 And the corresponding entry in /usr/src/UPDATING: "20090520: Update ZFS to version 13. ZFS users will need to re-build and install both kernel and world simultaneously in order for the ZFS tools to work. Existing pools will continue to work without upgrade. If a pool is upgraded it will no longer be usable by older kernel revs. ZFS send / recv between pool version 6 and pool version 13 is not supported." Regargs, Panagiotis -- Panagiotis J. Christias Network Management Center P.Christias@noc.ntua.gr National Technical Univ. of Athens, GREECE From owner-freebsd-fs@FreeBSD.ORG Tue Aug 25 12:25:08 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6BEE106568D; Tue, 25 Aug 2009 12:25:08 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 9EADF8FC14; Tue, 25 Aug 2009 12:25:08 +0000 (UTC) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:53794 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Mfv58-0000gg-4z; Tue, 25 Aug 2009 14:25:00 +0200 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id CB5721A4748; Tue, 25 Aug 2009 14:24:54 +0200 (CEST) Message-Id: <917520A8-94F5-41CD-8274-EC0228EE70A2@exscape.org> From: Thomas Backman To: Pawel Jakub Dawidek In-Reply-To: <20090821110031.GB1962@garage.freebsd.pl> 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, 25 Aug 2009 14:24:52 +0200 References: <7F161876-8DA7-4617-98B6-7CD54C691BC6@exscape.org> <306284EA-C89C-433C-9D33-E6CF44305800@exscape.org> <20090821110031.GB1962@garage.freebsd.pl> X-Mailer: Apple Mail (2.936) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1Mfv58-0000gg-4z. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1Mfv58-0000gg-4z 2eb25dbe63b93be4148ae89f595f7be3 Cc: freebsd-fs@freebsd.org, FreeBSD current Subject: Re: Yet another ZFS recv panic; old but rarely seen 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, 25 Aug 2009 12:25:09 -0000 On Aug 21, 2009, at 13:00, Pawel Jakub Dawidek wrote: > > Right, the bug is already fixed in OpenSolaris. If you can reproduce > the > problem, you might try this patch: > > http://people.freebsd.org/~pjd/patches/dirtying_dbuf.patch Well, since I wasn't able to reliably reproduce the panic, I can't say if the patch is working or not... but after the stress testing, I applied it anyway to check for regressions, and so far it seems to work. Regards, Thomas From owner-freebsd-fs@FreeBSD.ORG Tue Aug 25 20:30:15 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CD841065691 for ; Tue, 25 Aug 2009 20:30:15 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4B1948FC28 for ; Tue, 25 Aug 2009 20:30:15 +0000 (UTC) Received: from eagle.syrec.org (c-24-6-221-126.hsd1.ca.comcast.net [24.6.221.126]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id n7PK7rEj021969 for ; Tue, 25 Aug 2009 13:07:53 -0700 (PDT) Message-ID: <4A944498.8030203@rawbw.com> Date: Tue, 25 Aug 2009 13:07:52 -0700 From: Yuri User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Is it possible to add this patch to FreeBSD-8.0? (kern/133174: [msdosfs] [patch] msdosfs must support utf-encoded international characters in file names) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 20:30:15 -0000 This PR is pending for a while: http://www.freebsd.org/cgi/query-pr.cgi?pr=133174 I tested the patch many times and never found any problems. Mandarin file names all look good. Is there a way to check this patch into 8.0? I mount disks with the option -L=zh_TW.UTF-8. Not sure if the first part (zh_TW) really matters. ru_RU.UTF-8 works with Chinese file names the same way. I guess it should be just -L=UTF-8 but this makes mount_msdosfs to fail with some strange error message. It's very important to have FreeBSD understand international file names in msdosfs since this will make it's use easier for non-English users. Please let me know what you think. Thank you, Yuri From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 00:00:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 326E5106568D for ; Wed, 26 Aug 2009 00:00:04 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id E56298FC18 for ; Wed, 26 Aug 2009 00:00:03 +0000 (UTC) Received: (qmail 2394 invoked from network); 26 Aug 2009 00:00:02 -0000 Received: from unknown (HELO ?192.168.1.47?) (spawk@70.23.211.249) by acm.poly.edu with AES256-SHA encrypted SMTP; 26 Aug 2009 00:00:02 -0000 Message-ID: <4A947AE6.7070401@acm.poly.edu> Date: Tue, 25 Aug 2009 19:59:34 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.19 (X11/20090108) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4A646DA8.2050201@acm.poly.edu> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: geom_mirror/UFS weirdness with 7.2-STABLE 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, 26 Aug 2009 00:00:04 -0000 Ivan Voras wrote: > Boris Kochergin wrote: > >> Ahoy. I noticed some very odd things in my file server's kernel buffer >> this morning (there were actually a ton of these--this is a snippet): >> >> Jul 20 05:54:10 exodus smartd[763]: Device: /dev/ad1, FAILED SMART >> self-check. BACK UP DATA NOW! >> Jul 20 05:57:57 exodus kernel: >> g_vfs_done():mirror/boots1[READ(offset=-4569735194538825728, >> length=16384)]error = 5 >> Jul 20 05:57:57 exodus kernel: bad block 8806809555123731765, ino 4430620 >> Jul 20 05:57:57 exodus kernel: pid 35 (softdepflush), uid 0 inumber >> 4430620 on /: bad block >> > > >> # df / >> Filesystem 1K-blocks Used Avail >> Capacity Mounted on >> /dev/mirror/boots1 37846636 -4058799239201906816 4058799239236725722 >> -11656883301279% / >> >> The system is a: >> >> # uname -a >> FreeBSD exodus.poly.edu 7.2-STABLE FreeBSD 7.2-STABLE #3: Sat Jul 11 >> 16:22:02 EDT 2009 root@exodus.poly.edu:/usr/obj/usr/src/sys/EXODUS >> amd64 >> >> Regarding smartd yelling at me about /dev/ad1, it's been doing that for >> long while before this. There is one sector on the drive that cannot be >> read, but the disk has otherwise been fine for months. My experience >> with geom_mirror has been that it disconnects members from an array if >> they experience I/O errors, so this seems to be something different. Any >> clues? >> > > It looks like the drive returned corrupted data without returning an > error - which is strange, but not impossible. You are probably seeing > numbers like -4058799239201906816 because some metadata is corrupted. If > so, you should immediately disconnect the problematic drive so that the > errorneous data isn't picked up and written to the good drive. > > > In retrospect, it appears to have been bad RAM. The symptoms were just subtler back then. -Boris From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 00:14:41 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B7A0106568C for ; Wed, 26 Aug 2009 00:14:41 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 3037D8FC18 for ; Wed, 26 Aug 2009 00:14:40 +0000 (UTC) Received: (qmail 2609 invoked from network); 26 Aug 2009 00:14:40 -0000 Received: from unknown (HELO ?192.168.1.47?) (spawk@70.23.211.249) by acm.poly.edu with AES256-SHA encrypted SMTP; 26 Aug 2009 00:14:40 -0000 Message-ID: <4A947E57.6050700@acm.poly.edu> Date: Tue, 25 Aug 2009 20:14:15 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.19 (X11/20090108) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4A78AFB2.10103@acm.poly.edu> <20090805115621.GG1784@garage.freebsd.pl> <4A798A12.4070408@acm.poly.edu> <20090807073738.GA1607@garage.freebsd.pl> <20090807074400.GB1607@garage.freebsd.pl> <4A7C3002.8000003@acm.poly.edu> <20090807191334.GA1814@garage.freebsd.pl> <4A7C81CA.2040303@acm.poly.edu> <20090807193842.GA2487@garage.freebsd.pl> <4A7C87C5.1070608@acm.poly.edu> <20090807202756.GB2487@garage.freebsd.pl> <4A81CF20.7010108@acm.poly.edu> <4A8AA531.2000004@acm.poly.edu> In-Reply-To: <4A8AA531.2000004@acm.poly.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS RAID-Z panic on vdev failure + subsequent panics and hangs 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, 26 Aug 2009 00:14:41 -0000 Boris Kochergin wrote: > Boris Kochergin wrote: >> Pawel Jakub Dawidek wrote: >>> On Fri, Aug 07, 2009 at 04:00:05PM -0400, Boris Kochergin wrote: >>> >>>> Pawel Jakub Dawidek wrote: >>>> >>>>> On Fri, Aug 07, 2009 at 03:34:34PM -0400, Boris Kochergin wrote: >>>>> >>>>> >>>>>> Pawel Jakub Dawidek wrote: >>>>>> >>>>>>> Yeah, that's strange indeed. Could you try: >>>>>>> >>>>>>> print ab->b_arc_node.list_prev >>>>>>> print ab->b_arc_node.list_next >>>>>>> >>>>>>> >>>>>>> >>>>>> (kgdb) print ab->b_arc_node.list_prev >>>>>> $1 = (struct list_node *) 0x1 >>>>>> >>>>> Yeah, list_prev is corrupted. If it panics on you everytime, I could >>>>> send you a patch which will try to catch where the corruption occurs. >>>>> >>>>> >>>>> >>>> I eventually get the arc_evict panic every time I successfully >>>> manage to mount the filesystem, but it usually panics (with the >>>> other backtrace) as soon as I try to mount it, or mount just hangs. >>>> I'll gladly try the patch, though--the data on the array is >>>> important to me. Thanks. >>>> >>> >>> To get the data from there you could also try to 'zfs send' it without >>> mounting the dataset at all (just in case). >>> >>> >> Sorry for the delay. I had to find another machine to move the disks >> into so that I could continue experimenting. Anyway, the filesystem >> didn't have any snapshots I could send, so I tried creating one with >> "zfs snapshot home@1" and the machine hung. >> >> FYI, In the new machine, all disks (including the one with the / >> filesystem) retain their device names. >> >> -Boris >> _______________________________________________ >> 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" > Some more panics using RELENG_8 sources from yesterday: > http://acm.poly.edu/~spawk/zfs/. The one in panic3.txt happens much > more often than the other ones. If any brave soul wants to look into > it, I can provide NFS/geom_gate/whatever access to the disk images (or > actual disks, if there's a difference) so that they can recreate the > problem on a local machine. > > -Boris > _______________________________________________ > 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" For the archives: pjd@ took some time to examine the disk images I made of the RAID-Z pool, but found heavy corruption in the metadata. As it turns out, the machine had bad RAM during the incident, and that is probably what caused it. Unfortunately, I had only started to suspect it recently as random userland application and kernel panics became frequent. This is good news for ZFS users, as it indicates that ZFS did not corrupt my pool on its own. I do, however, advise you to be mindful of the problems bad memory can cause for ZFS. Personally, I will start shelling out a few more bucks for the ECC stuff from now on. (Eagerly awaiting the read-only offline recovery functionality described at http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg20092.html). -Boris From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 04:47:30 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A4F0106568D for ; Wed, 26 Aug 2009 04:47:30 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.freebsd.org (Postfix) with ESMTP id 032BD8FC20 for ; Wed, 26 Aug 2009 04:47:29 +0000 (UTC) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.14.3/8.14.3) with ESMTP id n7Q4KvWw079882 for ; Wed, 26 Aug 2009 00:20:58 -0400 (EDT) (envelope-from mi+thun@aldan.algebra.com) Message-ID: <4A94B829.3090202@aldan.algebra.com> Date: Wed, 26 Aug 2009 00:20:57 -0400 From: "Mikhail T." User-Agent: Thunderbird 2.0.0.22 (X11/20090711) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: semantics of fcntl() with l_len being 0 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, 26 Aug 2009 04:47:30 -0000 Hello! I'm curious, whether a file, that's locked (via fcntl) with l_start and l_len being 0 is supposed to be appendable... I would think so, but I notice, that when spamprobe (see mail/spamprobe) chews on my spam mailbox, I can not append a new piece of spam to the file -- my imap-server is waiting for spamprobe to finish. The fcntl(2) says: ``len = 0 means until end of file''. Is that ``until the end of file AT THE TIME OF LOCKING'' or simply ``no other lock until we are done''? Thanks. Yours, -mi From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 09:09:57 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5EE51065672 for ; Wed, 26 Aug 2009 09:09:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 1EABB8FC1C for ; Wed, 26 Aug 2009 09:09:56 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n7Q99nxj049087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Aug 2009 12:09:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n7Q99nvK049819; Wed, 26 Aug 2009 12:09:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n7Q99mLU049818; Wed, 26 Aug 2009 12:09:48 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 26 Aug 2009 12:09:47 +0300 From: Kostik Belousov To: "Mikhail T." Message-ID: <20090826090947.GS9623@deviant.kiev.zoral.com.ua> References: <4A94B829.3090202@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="A61Eau4L8twGtri1" Content-Disposition: inline In-Reply-To: <4A94B829.3090202@aldan.algebra.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Re: semantics of fcntl() with l_len being 0 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, 26 Aug 2009 09:09:57 -0000 --A61Eau4L8twGtri1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 26, 2009 at 12:20:57AM -0400, Mikhail T. wrote: > Hello! >=20 > I'm curious, whether a file, that's locked (via fcntl) with l_start and > l_len being 0 is supposed to be appendable... >=20 > I would think so, but I notice, that when spamprobe (see mail/spamprobe) > chews on my spam mailbox, I can not append a new piece of spam to the > file -- my imap-server is waiting for spamprobe to finish. >=20 > The fcntl(2) says: ``len =3D 0 means until end of file''. Is that ``until > the end of file AT THE TIME OF LOCKING'' or simply ``no other lock until > we are done''? Thanks. Yours, SUSv3 is definitive on the subject: A lock shall be set to extend to the largest possible value of the file offset for that file by setting l_len to 0. If such a lock also has l_start set to 0 and l_whence is set to SEEK_SET, the whole file shall be locked. =46rom sys/kern/kern_lockf.c, line 464: } else if (fl->l_len =3D=3D 0) { end =3D OFF_MAX; --A61Eau4L8twGtri1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkqU+9sACgkQC3+MBN1Mb4hIhQCdHpyp47SyuxvCHBrZwCojjlrF csYAniFIfgC8HSDBSjcSX6VMw+4iF+fw =Lboc -----END PGP SIGNATURE----- --A61Eau4L8twGtri1-- From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 09:45:55 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ED4C106568B; Wed, 26 Aug 2009 09:45:55 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2581D8FC27; Wed, 26 Aug 2009 09:45:55 +0000 (UTC) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7Q9jsqh050641; Wed, 26 Aug 2009 09:45:54 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7Q9js1Y050637; Wed, 26 Aug 2009 09:45:54 GMT (envelope-from linimon) Date: Wed, 26 Aug 2009 09:45:54 GMT Message-Id: <200908260945.n7Q9js1Y050637@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/138202: mount_msdosfs(1) see only 2Gb 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, 26 Aug 2009 09:45:55 -0000 Old Synopsis: mount_msdosfs see only 2Gb New Synopsis: mount_msdosfs(1) see only 2Gb Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 26 09:45:27 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=138202 From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 13:57:05 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D568110656A8 for ; Wed, 26 Aug 2009 13:57:05 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.freebsd.org (Postfix) with ESMTP id 8D1CC8FC22 for ; Wed, 26 Aug 2009 13:57:05 +0000 (UTC) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.14.3/8.14.3) with ESMTP id n7QDv4Z8082354; Wed, 26 Aug 2009 09:57:04 -0400 (EDT) (envelope-from mi+thun@aldan.algebra.com) Message-ID: <4A953F30.8030202@aldan.algebra.com> Date: Wed, 26 Aug 2009 09:57:04 -0400 From: "Mikhail T." User-Agent: Thunderbird 2.0.0.22 (X11/20090711) MIME-Version: 1.0 To: Kostik Belousov References: <4A94B829.3090202@aldan.algebra.com> <20090826090947.GS9623@deviant.kiev.zoral.com.ua> In-Reply-To: <20090826090947.GS9623@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org Subject: Re: semantics of fcntl() with l_len being 0 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, 26 Aug 2009 13:57:05 -0000 Kostik Belousov ΞΑΠΙΣΑΧ(ΜΑ): > On Wed, Aug 26, 2009 at 12:20:57AM -0400, Mikhail T. wrote: > >> Hello! >> >> I'm curious, whether a file, that's locked (via fcntl) with l_start and >> l_len being 0 is supposed to be appendable... >> >> I would think so, but I notice, that when spamprobe (see mail/spamprobe) >> chews on my spam mailbox, I can not append a new piece of spam to the >> file -- my imap-server is waiting for spamprobe to finish. >> >> The fcntl(2) says: ``len = 0 means until end of file''. Is that ``until >> the end of file AT THE TIME OF LOCKING'' or simply ``no other lock until >> we are done''? Thanks. Yours, >> > > SUSv3 is definitive on the subject: > A lock shall be set to extend to the largest possible value of the file > offset for that file by setting l_len to 0. If such a lock also has > l_start set to 0 and l_whence is set to SEEK_SET, the whole file shall > be locked. > I would not say, this is definitive -- if one attempts to grow a locked file, "the whole file" (as existed at the lock-time) will remain non-violated... The code is more explicit, of course: > From sys/kern/kern_lockf.c, line 464: > } else if (fl->l_len == 0) { > end = OFF_MAX; > So, how can one properly lock only the area, that exists at the time of locking? Perform a stat() first? Thanks! -mi From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 14:06:50 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7197A106568B for ; Wed, 26 Aug 2009 14:06:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id E65638FC14 for ; Wed, 26 Aug 2009 14:06:49 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n7QE6e9Q068311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Aug 2009 17:06:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n7QE6e2F065752; Wed, 26 Aug 2009 17:06:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n7QE6ekW065751; Wed, 26 Aug 2009 17:06:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 26 Aug 2009 17:06:40 +0300 From: Kostik Belousov To: "Mikhail T." Message-ID: <20090826140640.GA9623@deviant.kiev.zoral.com.ua> References: <4A94B829.3090202@aldan.algebra.com> <20090826090947.GS9623@deviant.kiev.zoral.com.ua> <4A953F30.8030202@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cgV9kgQ4vUfIQsP4" Content-Disposition: inline In-Reply-To: <4A953F30.8030202@aldan.algebra.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Re: semantics of fcntl() with l_len being 0 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, 26 Aug 2009 14:06:50 -0000 --cgV9kgQ4vUfIQsP4 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 26, 2009 at 09:57:04AM -0400, Mikhail T. wrote: > Kostik Belousov =CE=C1=D0=C9=D3=C1=D7(=CC=C1): > > On Wed, Aug 26, 2009 at 12:20:57AM -0400, Mikhail T. wrote: > > =20 > >> Hello! > >> > >> I'm curious, whether a file, that's locked (via fcntl) with l_start and > >> l_len being 0 is supposed to be appendable... > >> > >> I would think so, but I notice, that when spamprobe (see mail/spamprob= e) > >> chews on my spam mailbox, I can not append a new piece of spam to the > >> file -- my imap-server is waiting for spamprobe to finish. > >> > >> The fcntl(2) says: ``len =3D 0 means until end of file''. Is that ``un= til > >> the end of file AT THE TIME OF LOCKING'' or simply ``no other lock unt= il > >> we are done''? Thanks. Yours, > >> =20 > > > > SUSv3 is definitive on the subject: > > A lock shall be set to extend to the largest possible value of the file > > offset for that file by setting l_len to 0. If such a lock also has > > l_start set to 0 and l_whence is set to SEEK_SET, the whole file shall > > be locked. > > =20 > I would not say, this is definitive -- if one attempts to grow a locked > file, "the whole file" (as existed at the lock-time) will remain > non-violated... The code is more explicit, of course: > > From sys/kern/kern_lockf.c, line 464: > > } else if (fl->l_len =3D=3D 0) { > > end =3D OFF_MAX; > > =20 > So, how can one properly lock only the area, that exists at the time of > locking? Perform a stat() first? Thanks! You might lock the maximal range, to prevent the modifications from other accessors that honour the protocol, do stat call, and then unlock the range from EOF to 0 (AKA max offset). --cgV9kgQ4vUfIQsP4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkqVQW8ACgkQC3+MBN1Mb4jh7gCg3xq2JSaFOFkMDpgzn4lbb6AL QBUAoMhiprq3bzbjyG+3TLbHCPe0SRKi =fPX3 -----END PGP SIGNATURE----- --cgV9kgQ4vUfIQsP4-- From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 14:11:19 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC8121065690 for ; Wed, 26 Aug 2009 14:11:19 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id 806048FC44 for ; Wed, 26 Aug 2009 14:11:19 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MgJDX-000AMF-Lk; Wed, 26 Aug 2009 16:11:15 +0200 Received: from [206.161.120.61] (helo=[192.168.5.15]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MgJDU-000MPU-Fh; Wed, 26 Aug 2009 18:11:12 +0400 Message-ID: <4A9542D4.8090404@plus-plus.su> Date: Wed, 26 Aug 2009 18:12:36 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Olivier Smedts References: <4A927CB3.3040402@plus-plus.su> <20090824125737.GA92643@noc.ntua.gr> <4A92902F.70606@plus-plus.su> <7A60E3BB-04DB-4272-9052-7477FC10DBBA@spry.com> <367b2c980908241014l425b48e3uea765a51f0447ea3@mail.gmail.com> In-Reply-To: <367b2c980908241014l425b48e3uea765a51f0447ea3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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: Wed, 26 Aug 2009 14:11:19 -0000 Olivier Smedts wrote: > 2009/8/24 Matt Simerson : >> On Aug 24, 2009, at 6:05 AM, Mikhail (Plus Plus) wrote: >> >>> Panagiotis Christias wrote: >>>> I would suggest you try FreeBSD 8.0 that includes the latest version of >>>> ZFS (version 13), which fixed several problems present in 7.x. Then, >>>> check for crash dumps (see dumpon(8)), collect any available info and >>>> sent it to the list. >> I second this recommendation. The ZFS code in 8.0 is considerably more >> stable than what's currently in 7.2-STABLE. >> >>> Does that mean I will have to format my current zpool in order to >>> "upgrade" to ZFS v13? And if it is true then another problem is that I have >>> to backup current data somewhere before I'll be able to format zpool to new >>> version, but I cannot do this because server simply crashes every time I try >>> to copy that much of data to another hdd. >> Not at all. Simply install 8.0 and do a zpool upgrade. > > And don't forget to zfs upgrade after the zpool upgrade ! Thanks everyone who responded. I've followed the advice and installed FreeBSD-8.0BETA3-amd64 on that server. OS resides on dedicated SATA HD, so all other hard drives left untouched. Now I cannot see zfs pool online. I've enabled ZFS in /etc/rc.conf, reboot the server, but I cannot see my zpool. zen# zpool list no pools available zen# I remember ZFS relies on hostid, and I've checked my current hostid is identical to the one that I had when I ran 7.2. What do I do now to see my zpool again? Thanks, Mikhail. From owner-freebsd-fs@FreeBSD.ORG Wed Aug 26 14:22:03 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4E4A106568E for ; Wed, 26 Aug 2009 14:22:03 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id A580E8FC2D for ; Wed, 26 Aug 2009 14:22:03 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MgJNy-0009jH-7x for freebsd-fs@freebsd.org; Wed, 26 Aug 2009 16:22:02 +0200 Received: from [206.161.120.61] (helo=[192.168.5.15]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MgJNu-000CkA-Lv for freebsd-fs@freebsd.org; Wed, 26 Aug 2009 18:21:59 +0400 Message-ID: <4A95455B.9050800@plus-plus.su> Date: Wed, 26 Aug 2009 18:23:23 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4A927CB3.3040402@plus-plus.su> <20090824125737.GA92643@noc.ntua.gr> <4A92902F.70606@plus-plus.su> <7A60E3BB-04DB-4272-9052-7477FC10DBBA@spry.com> <367b2c980908241014l425b48e3uea765a51f0447ea3@mail.gmail.com> <4A9542D4.8090404@plus-plus.su> In-Reply-To: <4A9542D4.8090404@plus-plus.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: need help with 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: Wed, 26 Aug 2009 14:22:04 -0000 Mikhail (Plus Plus) wrote: > What do I do now to see my zpool again? > Replying to myself - Someone contacted me off-list with suggestion to do "zpool import {pool}" and it worked. Mikhail. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 27 09:16:43 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9373D1065694 for ; Thu, 27 Aug 2009 09:16:43 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id 568CB8FC56 for ; Thu, 27 Aug 2009 09:16:43 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mgb61-0009le-OF for freebsd-fs@freebsd.org; Thu, 27 Aug 2009 11:16:41 +0200 Received: from [206.161.120.61] (helo=[192.168.5.15]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mgb5x-0003Kc-3O for freebsd-fs@freebsd.org; Thu, 27 Aug 2009 13:16:37 +0400 Message-ID: <4A964F4E.4080009@plus-plus.su> Date: Thu, 27 Aug 2009 13:18:06 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4A927CB3.3040402@plus-plus.su> In-Reply-To: <4A927CB3.3040402@plus-plus.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: need help with 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, 27 Aug 2009 09:16:43 -0000 Last night I installed FreeBSD-8.0BETA3 AMD64, upgraded zpool and zfs, and this morning I did some load on FS to see if it runs more stable now. To stress-load the system I ran rsync from ZFS to mounted UFS volume and at the same time I started bonie++ benchmark on ZFS volume: bonnie++ -s17000 -d. -n64 Everything worked fine for about ~90 minutes, but then system paniced. I got escaped to "db> " prompt on local console, but I have zero debugging experience, so I just rebooted the server. The only thing I noticed was that last mentioned PID on the panic screen was bonnie++'s process. Also, I'm very confused after re-reading ZFS tuning wiki from here: http://wiki.freebsd.org/ZFSTuningGuide "amd64 FreeBSD 7.2+ has improved kernel memory allocation strategy and no tuning may be necessary on systems with more than 2 GB of RAM." Does that mean I no longer have to tune ZFS via loader.conf? Just better leave it empty on FreeBSD-8.0 installation? Right now I'm going to continue with rsync and will start bonnie++ in parallel keeping my loader.conf with the following values: vm.kmem_size="1536M" vm.kmem_size_max="3072M" vm.pmap.shpgperproc="1024" vfs.zfs.arc_min="256M" vfs.zfs.arc_max="384M" vfs.zfs.vdev.cache.size="50M" vfs.zfs.prefetch_disable="1" kern.maxproc="20000" I would appreciate any tips on showing me how to debug system panic from "db> " prompt in case system panics again.. Thank you. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 27 09:48:41 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C848D10656AC for ; Thu, 27 Aug 2009 09:48:41 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id 8ACC78FC3A for ; Thu, 27 Aug 2009 09:48:41 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mgbay-000NZc-7j for freebsd-fs@freebsd.org; Thu, 27 Aug 2009 11:48:40 +0200 Received: from [206.161.120.61] (helo=[192.168.5.15]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mgbau-0003J3-4n for freebsd-fs@freebsd.org; Thu, 27 Aug 2009 13:48:36 +0400 Message-ID: <4A9656CE.8020107@plus-plus.su> Date: Thu, 27 Aug 2009 13:50:06 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4A927CB3.3040402@plus-plus.su> <4A964F4E.4080009@plus-plus.su> In-Reply-To: <4A964F4E.4080009@plus-plus.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: need help with 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, 27 Aug 2009 09:48:41 -0000 Mikhail (Plus Plus) wrote: > Everything worked fine for about ~90 minutes, but then system paniced. I > got escaped to "db> " prompt on local console, but I have zero debugging > experience, so I just rebooted the server. The only thing I noticed was > that last mentioned PID on the panic screen was bonnie++'s process. Ok, I just ran bonnie++ test on ZFS (no rsync this time, only bonnie++) and system paniced again after ~23 minutes. Right now I see the following on local console: "Memory modified after free 0xffff... val=... @ 0xff.. panic: Most recently used by solaris cpuid = 1 KDB: enter: panic [thread pid 883 tid 10.. ] Stopped at kdb_enter 0x3d: movq ...(%rip) db> " and PID 883 was bonnie++'s PID before system panic. Mikhail. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 27 09:52:25 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E87C0106568C for ; Thu, 27 Aug 2009 09:52:25 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: from web37302.mail.mud.yahoo.com (web37302.mail.mud.yahoo.com [209.191.90.245]) by mx1.freebsd.org (Postfix) with SMTP id A85A08FC39 for ; Thu, 27 Aug 2009 09:52:25 +0000 (UTC) Received: (qmail 31850 invoked by uid 60001); 27 Aug 2009 09:52:25 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1251366744; bh=efpDWp2QmWqSRbHz75yZ5CccCRURVGyMPR108Nyeu84=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=asN6lH3i6fUbXL5E7ftymN9i5i2q3Rl4OiJGhz+hwRAtgHNQIUj5fnPjQkkMaHmVTUTPe+c3TMXsi4s3Em8GzFmlG0k+mdeDUVN0MNAPxW1Yt6FYLMaHR9hKnkrdI4X6J2OxIAycr/3N5eM/oxLjjomAhh9fufhhkYLihSJS+JA= 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=DkaCuJE/QzXAFE9K17ymdqGuCuq5PvW6ObPiwqs0xZs8DyzZAOGqzsQRmuENuXtqPuisAMvP1RzHx55iTtKcNsCduACwoys9lKU08riRyUAmXgwCuo/OvNOukO80Dy5vdnYCSkAXHjA/40UHbdAYcj+DiZDovXd2GWTAEi+CFck=; Message-ID: <941145.26591.qm@web37302.mail.mud.yahoo.com> X-YMail-OSG: U9VPtyIVM1nvGMMJcVNGr96.tySAHAB2fB7jMEv_dXiVkjMrVOwceEb.gEfqw7PwVvTxCKxBHc4L79L2qrawkQd0eibxxPubswFSfHv5iyaw8rbI1ssfBtbizbMjZ8tg.fOHw3uAe7Tjq.1xG5Z0wFGynTCYkjp7DqoTgM_ViJyy_tkeShxvOWq86FleRML2HBLnYUIkg8MfdzcTCuVMvSUrQ34rCuDkaMXL8eQ1fwbr_8cLNR8qL7RBTIqrnasSS8JdRsIEQ8mjmW0nm_R4HWLTCIBNkv_TPRRYdCcP1XdKJfU1sGeCdcvL7JP1McGTMcbnD0O7KpBfbKOUQacH6oKqMYps0itiYi9IUMaf0XgzTPE3ZyCX6Qdw5wUcGx2H_B7aYD2tUwKM Received: from [213.147.110.159] by web37302.mail.mud.yahoo.com via HTTP; Thu, 27 Aug 2009 02:52:24 PDT X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 References: <4A927CB3.3040402@plus-plus.su> <4A964F4E.4080009@plus-plus.su> Date: Thu, 27 Aug 2009 02:52:24 -0700 (PDT) From: Simun Mikecin To: "Mikhail \(Plus Plus\)" In-Reply-To: <4A964F4E.4080009@plus-plus.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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, 27 Aug 2009 09:52:26 -0000 ----- Original Message ---- > From: Mikhail (Plus Plus) > To: freebsd-fs@freebsd.org > Sent: Thursday, August 27, 2009 11:18:06 AM > Subject: Re: need help with ZFS > > Last night I installed FreeBSD-8.0BETA3 AMD64, upgraded zpool and zfs, and this > morning I did some load on FS to see if it runs more stable now. > > To stress-load the system I ran rsync from ZFS to mounted UFS volume and at the > same time I started bonie++ benchmark on ZFS volume: > > bonnie++ -s17000 -d. -n64 > > Everything worked fine for about ~90 minutes, but then system paniced. I got > escaped to "db> " prompt on local console, but I have zero debugging experience, > so I just rebooted the server. The only thing I noticed was that last mentioned > PID on the panic screen was bonnie++'s process. > > Also, I'm very confused after re-reading ZFS tuning wiki from here: > http://wiki.freebsd.org/ZFSTuningGuide ZFSTuningGuide is sometimes misleading. Better look at /usr/src/UPDATING. > > "amd64 > FreeBSD 7.2+ has improved kernel memory allocation strategy and no tuning may be > necessary on systems with more than 2 GB of RAM." > > Does that mean I no longer have to tune ZFS via loader.conf? Just better leave > it empty on FreeBSD-8.0 installation? > > Right now I'm going to continue with rsync and will start bonnie++ in parallel > keeping my loader.conf with the following values: > > vm.kmem_size="1536M" > vm.kmem_size_max="3072M" > vm.pmap.shpgperproc="1024" > vfs.zfs.arc_min="256M" > vfs.zfs.arc_max="384M" > vfs.zfs.vdev.cache.size="50M" > vfs.zfs.prefetch_disable="1" > kern.maxproc="20000" Since FreeBSD 7.2 no additional ZFS tuning in loader.conf is needed (on amd64). You should remove all those settings from loader.conf, reboot, and re-run the tests. Maybe, just maybe you get a panic just because of those settings. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 27 10:16:22 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E614106568C for ; Thu, 27 Aug 2009 10:16:22 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id B2BD58FC2E for ; Thu, 27 Aug 2009 10:16:21 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so238395eyf.9 for ; Thu, 27 Aug 2009 03:16:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.17.212 with SMTP id j62mr1788745wej.132.1251368180519; Thu, 27 Aug 2009 03:16:20 -0700 (PDT) In-Reply-To: <4A9656CE.8020107@plus-plus.su> References: <4A927CB3.3040402@plus-plus.su> <4A964F4E.4080009@plus-plus.su> <4A9656CE.8020107@plus-plus.su> Date: Thu, 27 Aug 2009 12:16:20 +0200 Message-ID: <367b2c980908270316n7a21673ek3a997573f2fadbb0@mail.gmail.com> From: Olivier Smedts To: "Mikhail (Plus Plus)" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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, 27 Aug 2009 10:16:22 -0000 2009/8/27 Mikhail (Plus Plus) : > Mikhail (Plus Plus) wrote: >> >> Everything worked fine for about ~90 minutes, but then system paniced. I >> got escaped to "db> " prompt on local console, but I have zero debugging >> experience, so I just rebooted the server. The only thing I noticed was = that >> last mentioned PID on the panic screen was bonnie++'s process. > > Ok, I just ran bonnie++ test on ZFS (no rsync this time, only bonnie++) a= nd > system paniced again after ~23 minutes. Right now I see the following on > local console: > > "Memory modified after free 0xffff... val=3D... @ 0xff.. > panic: Most recently used by solaris > cpuid =3D 1 > KDB: enter: panic > [thread pid 883 tid 10.. ] > Stopped at =A0 =A0 =A0kdb_enter 0x3d: movq =A0 =A0...(%rip) > db> " You can output the backtrace by entering "bt" at the "db> "prompt. > and PID 883 was bonnie++'s PID before system panic. > > Mikhail. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From owner-freebsd-fs@FreeBSD.ORG Thu Aug 27 11:49:31 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D061106568B for ; Thu, 27 Aug 2009 11:49:31 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id D8D818FC36 for ; Thu, 27 Aug 2009 11:49:30 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MgdTr-000OYS-Va; Thu, 27 Aug 2009 13:49:28 +0200 Received: from [206.161.120.61] (helo=[192.168.5.15]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MgdTn-0007Dx-O2; Thu, 27 Aug 2009 15:49:24 +0400 Message-ID: <4A96731D.20406@plus-plus.su> Date: Thu, 27 Aug 2009 15:50:53 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Olivier Smedts References: <4A927CB3.3040402@plus-plus.su> <4A964F4E.4080009@plus-plus.su> <4A9656CE.8020107@plus-plus.su> <367b2c980908270316n7a21673ek3a997573f2fadbb0@mail.gmail.com> In-Reply-To: <367b2c980908270316n7a21673ek3a997573f2fadbb0@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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, 27 Aug 2009 11:49:31 -0000 Olivier Smedts wrote: > You can output the backtrace by entering "bt" at the "db> "prompt. Thanks. I've booted FreeBSD with empty loader.conf and I tried to run bonnie++ -s17000 -d. -n128 on ZFS. I get 100% panic after 7-10 minutes, I tried 2 times already. I'm going to redirect console to another server so that I can copy "bt" output, it is one screen long and it is really hard to type it by hand. Mikhail. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 27 12:03:55 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADB7E106568B for ; Thu, 27 Aug 2009 12:03:55 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id 724938FC3F for ; Thu, 27 Aug 2009 12:03:55 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mgdhq-000DlQ-Eo for freebsd-fs@freebsd.org; Thu, 27 Aug 2009 14:03:54 +0200 Received: from [206.161.120.61] (helo=[192.168.5.15]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mgdhm-0002WS-JH for freebsd-fs@freebsd.org; Thu, 27 Aug 2009 16:03:51 +0400 Message-ID: <4A967680.2030205@plus-plus.su> Date: Thu, 27 Aug 2009 16:05:20 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4A927CB3.3040402@plus-plus.su> <4A964F4E.4080009@plus-plus.su> <4A9656CE.8020107@plus-plus.su> <367b2c980908270316n7a21673ek3a997573f2fadbb0@mail.gmail.com> <4A96731D.20406@plus-plus.su> In-Reply-To: <4A96731D.20406@plus-plus.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: need help with 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, 27 Aug 2009 12:03:55 -0000 Mikhail (Plus Plus) wrote: > I'm going to redirect console to another server so that I can copy "bt" > output, it is one screen long and it is really hard to type it by hand. Hm, and just as I thought there's no COM port on that server, so I can't redirect console output to another server. Is there any other way to copy "bt" output? I can only think of making a phone camera picture of the screen. Mikhail. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 27 14:50:19 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF7C81065698 for ; Thu, 27 Aug 2009 14:50:19 +0000 (UTC) (envelope-from m@plus-plus.su) Received: from ext-mail2.ux6.net (ext-mail2.ux6.net [213.163.72.53]) by mx1.freebsd.org (Postfix) with ESMTP id 48D7D8FC4D for ; Thu, 27 Aug 2009 14:50:17 +0000 (UTC) Received: from ermik.ux6.net ([91.206.231.146]) by ext-mail2.ux6.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MggIq-000BqT-U9 for freebsd-fs@freebsd.org; Thu, 27 Aug 2009 16:50:16 +0200 Received: from ip-95-220-41-234.bb.netbynet.ru ([95.220.41.234] helo=[192.168.1.99]) by ermik.ux6.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MggIn-000P3K-Ft for freebsd-fs@freebsd.org; Thu, 27 Aug 2009 18:50:13 +0400 Message-ID: <4A969D20.40809@plus-plus.su> Date: Thu, 27 Aug 2009 18:50:08 +0400 From: "Mikhail (Plus Plus)" User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4A927CB3.3040402@plus-plus.su> <4A964F4E.4080009@plus-plus.su> <4A9656CE.8020107@plus-plus.su> <367b2c980908270316n7a21673ek3a997573f2fadbb0@mail.gmail.com> <4A96731D.20406@plus-plus.su> <4A967680.2030205@plus-plus.su> In-Reply-To: <4A967680.2030205@plus-plus.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 27 Aug 2009 17:03:56 +0000 Subject: Re: need help with 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, 27 Aug 2009 14:50:20 -0000 Mikhail (Plus Plus) wrote: > Hm, and just as I thought there's no COM port on that server, so I can't > redirect console output to another server. Is there any other way to > copy "bt" output? I can only think of making a phone camera picture of > the screen. Here's "bt" output I get after system panics on running bonnie++ -s17000 -d. -n128 for about 10 minutes: http://omploader.org/vMjg5aQ/IMG_0057.jpg regards, Mikhail. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 27 19:46:53 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 848C11065691; Thu, 27 Aug 2009 19:46:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5B7978FC33; Thu, 27 Aug 2009 19:46:53 +0000 (UTC) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7RJkrCI045563; Thu, 27 Aug 2009 19:46:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7RJkr43045559; Thu, 27 Aug 2009 19:46:53 GMT (envelope-from linimon) Date: Thu, 27 Aug 2009 19:46:53 GMT Message-Id: <200908271946.n7RJkr43045559@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/138244: [zfs] dd(1) attempts bitwise transfer onto ZFS pool 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, 27 Aug 2009 19:46:53 -0000 Old Synopsis: dd attempts bitwise transfer onto ZFS pool New Synopsis: [zfs] dd(1) attempts bitwise transfer onto ZFS pool Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Aug 27 19:46:17 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=138244 From owner-freebsd-fs@FreeBSD.ORG Fri Aug 28 18:51:28 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98DF5106564A for ; Fri, 28 Aug 2009 18:51:28 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id 34BF78FC0A for ; Fri, 28 Aug 2009 18:51:28 +0000 (UTC) Received: from fuzz.geek.sh (unknown [196.209.244.32]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.geek.sh (Postfix) with ESMTPSA id 38B713BBC8 for ; Fri, 28 Aug 2009 20:36:11 +0200 (SAST) Message-ID: <4A9822FC.2030606@phat.za.net> Date: Fri, 28 Aug 2009 20:33:32 +0200 From: Aragon Gouveia User-Agent: Thunderbird 2.0.0.22 (X11/20090628) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: some of my files have an incorrect block count 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, 28 Aug 2009 18:51:28 -0000 Hi, I'm copying data across to a larger file system and in so doing, I've noticed that some of the files in my old file system have an incorrect block count. After copying all data, df(1) reports that the new file system has more data on it than the old one. I've narrowed most of the difference to one file in particular: %ls -l /data/qemu/winxp.qem /mnt/data/qemu/winxp.qem -rw-r--r-- 1 aragon staff 10737418240 Mar 29 21:57 /data/qemu/winxp.qem -rw-r--r-- 1 aragon staff 10737418240 Mar 29 21:57 /mnt/data/qemu/winxp.qem %du -k /data/qemu/winxp.qem /mnt/data/qemu/winxp.qem 10490896 /data/qemu/winxp.qem 2001728 /mnt/data/qemu/winxp.qem %du -Ak /data/qemu/winxp.qem /mnt/data/qemu/winxp.qem 10485760 /data/qemu/winxp.qem 10485760 /mnt/data/qemu/winxp.qem %stat -f '%N: %z %b' /data/qemu/winxp.qem /mnt/data/qemu/winxp.qem /data/qemu/winxp.qem: 10737418240 20981792 /mnt/data/qemu/winxp.qem: 10737418240 4003456 In the above the new file system is /data, the old /mnt/data. Running fsck(8) on the old file system doesn't show any errors and makes no difference. If dd(1) reads both files in, it counts the correct size, and running md5(1) on both copies of the files produces the same hash, so at least all the data is presumably present. Surely fsck(8) should detect this? Is this inconsistency cause for concern? Thanks, Aragon From owner-freebsd-fs@FreeBSD.ORG Fri Aug 28 19:12:27 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57FB01065670 for ; Fri, 28 Aug 2009 19:12:27 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from hamlet.setfilepointer.com (hamlet.SetFilePointer.com [63.224.10.2]) by mx1.freebsd.org (Postfix) with SMTP id 06E428FC08 for ; Fri, 28 Aug 2009 19:12:26 +0000 (UTC) Received: (qmail 42963 invoked from network); 28 Aug 2009 14:12:26 -0500 Received: from keira.kiwi-computer.com (HELO kiwi-computer.com) (63.224.10.3) by hamlet.setfilepointer.com with SMTP; 28 Aug 2009 14:12:26 -0500 Received: (qmail 77542 invoked by uid 2001); 28 Aug 2009 19:12:25 -0000 Date: Fri, 28 Aug 2009 14:12:25 -0500 From: "Rick C. Petty" To: Aragon Gouveia Message-ID: <20090828191225.GA77462@keira.kiwi-computer.com> References: <4A9822FC.2030606@phat.za.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A9822FC.2030606@phat.za.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org Subject: Re: some of my files have an incorrect block count X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2008@kiwi-computer.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 19:12:27 -0000 On Fri, Aug 28, 2009 at 08:33:32PM +0200, Aragon Gouveia wrote: > > I'm copying data across to a larger file system and in so doing, I've > noticed that some of the files in my old file system have an incorrect > block count. After copying all data, df(1) reports that the new file > system has more data on it than the old one. I've narrowed most of the > difference to one file in particular: Yes, these are called sparse files. Disk images are one example where sparse files come in handy (although some argue that you should fully zero an image initially to prevent fragmentation). Many tools can handle sparse files efficiently. You should read their individual man pages. > If dd(1) reads both files in, it counts the correct size, and running > md5(1) on both copies of the files produces the same hash, so at least > all the data is presumably present. If you want dd to copy sparse files correctly, you need to specify "conv=sparse" in the target dd command. I personally prefer rsync with "-S". > Surely fsck(8) should detect this? No. > Is this inconsistency cause for concern? No. This is just how sparse files work. -- Rick C. Petty From owner-freebsd-fs@FreeBSD.ORG Sat Aug 29 16:00:43 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCBBE106566C for ; Sat, 29 Aug 2009 16:00:43 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id E79B88FC13 for ; Sat, 29 Aug 2009 16:00:42 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 848DA45C9B; Sat, 29 Aug 2009 18:00:40 +0200 (CEST) Received: from localhost (abhv94.neoplus.adsl.tpnet.pl [83.7.111.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 4E5C045B36; Sat, 29 Aug 2009 18:00:35 +0200 (CEST) Date: Sat, 29 Aug 2009 18:00:37 +0200 From: Pawel Jakub Dawidek To: "Mikhail (Plus Plus)" Message-ID: <20090829160037.GA1848@garage.freebsd.pl> References: <4A927CB3.3040402@plus-plus.su> <4A964F4E.4080009@plus-plus.su> <4A9656CE.8020107@plus-plus.su> <367b2c980908270316n7a21673ek3a997573f2fadbb0@mail.gmail.com> <4A96731D.20406@plus-plus.su> <4A967680.2030205@plus-plus.su> <4A969D20.40809@plus-plus.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <4A969D20.40809@plus-plus.su> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: * X-Spam-Status: No, score=1.4 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL, URIBL_PH_SURBL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: need help with 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: Sat, 29 Aug 2009 16:00:43 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 27, 2009 at 06:50:08PM +0400, Mikhail (Plus Plus) wrote: > Mikhail (Plus Plus) wrote: > >Hm, and just as I thought there's no COM port on that server, so I can't= =20 > >redirect console output to another server. Is there any other way to=20 > >copy "bt" output? I can only think of making a phone camera picture of= =20 > >the screen. >=20 > Here's "bt" output I get after system panics on running >=20 > bonnie++ -s17000 -d. -n128 >=20 > for about 10 minutes: >=20 > http://omploader.org/vMjg5aQ/IMG_0057.jpg [...] I'm running your test on pretty low-end h/w (i386, 1GB of RAM, two cores) and cannot reproduce the problem for few hours now. The only tuning I did was to set vm.kmem_size to 1GB. You still need to do this very tuning even on amd64. Could you post output of: # sysctl vm.kmem_size # sysctl vm.kmem_size_max # sysctl vfs.zfs # zpool status # zpool list # zfs get all And place /var/run/dmesg.boot somewhere? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKmVClForvXbEpPzQRAlJ1AKC63NhoFBaQrawNjh/eRZEH/Q9XCwCdG+sR gMxw9ujYYU849dIbWlkbIJo= =hLyx -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga--