From owner-freebsd-fs@FreeBSD.ORG Sun Dec 26 10:54:48 2010 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 EBD3F1065670 for ; Sun, 26 Dec 2010 10:54:48 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 75CD38FC0A for ; Sun, 26 Dec 2010 10:54:48 +0000 (UTC) Received: by bwz12 with SMTP id 12so1833396bwz.13 for ; Sun, 26 Dec 2010 02:54:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :x-comment-to:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=cB7liyjac1CHDNION89R+Y5fgYIvNxmP0ma2J0+r0ac=; b=qs80ck5wtsmE/euGdIxkDfNMh2jQpqJcmbzWxRVTqsUMcNYpiYY5oiXrga7ZN8SWuL ZKB0glyV/vYBFs0MPFfIH9rokSG9M7lwHMyZmKheponcx71KD7PLZq2egFQxLQOb+YyJ ak54DEeD/eNM9KSb3TO8JjRDw/IfLX9jXAlnE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=CeCUNg0qr/srzA8SbpjgBuYNfq01AogMV2OjUcMRz+zY8Ef6Me7Hyk41EWqs23/VKo pYH0tfFcDn72B6nDaYYgEBoppUyk8nwmHIynzao2sq17SWuBV7IAJaEliM555YWReYpN QS5HqHaqVltIIeiW+6c66LKXDmhXmZNvckUDY= Received: by 10.204.52.75 with SMTP id h11mr3017777bkg.67.1293359520805; Sun, 26 Dec 2010 02:32:00 -0800 (PST) Received: from localhost ([95.69.174.185]) by mx.google.com with ESMTPS id d27sm7121429bkw.14.2010.12.26.02.31.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 26 Dec 2010 02:31:59 -0800 (PST) From: Mikolaj Golub To: "void" References: <514BA5D75A82411CBE80ECF0303FD425@COMP1> X-Comment-To: void Date: Sun, 26 Dec 2010 12:31:56 +0200 In-Reply-To: <514BA5D75A82411CBE80ECF0303FD425@COMP1> (void@list.ru's message of "Sat, 25 Dec 2010 17:17:05 +0300") Message-ID: <86wrmwkeoz.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@FreeBSD.org Subject: Re: hello 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, 26 Dec 2010 10:54:49 -0000 On Sat, 25 Dec 2010 17:17:05 +0300 void wrote: v> root@ul-farm etc#hastd v> hastd: remote address not configured for resource shared v> v> root@ul-farm etc#cat /etc/hast.conf v> # Global section v> control uds:///var/run/hastctl v> replication fullsync v> timeout 5 v> v> resource shared v> { v> local /dev/da0s2 v> on host1 v> { v> remote tcp4://10.15.0.127 v> } v> on host2 v> { v> remote tcp4://10.15.0.1 v> } v> } node name should be a full hostname as obtained by gethostname(3), or only first part of the hostname, or node's UUID as found in the kern.hostuuid sysctl(8) variable. I suppose yours host1/host2 don't match any. It may be e.g. "ul-farm". -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Mon Dec 27 11:06:58 2010 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 B6162106566B for ; Mon, 27 Dec 2010 11:06:58 +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 806F58FC12 for ; Mon, 27 Dec 2010 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBRB6wU5055743 for ; Mon, 27 Dec 2010 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBRB6vqe055740 for freebsd-fs@FreeBSD.org; Mon, 27 Dec 2010 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Dec 2010 11:06:57 GMT Message-Id: <201012271106.oBRB6vqe055740@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, 27 Dec 2010 11:06:58 -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/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152605 fs [ufs] [panic] handle_workitem_freeblocks: inode 18 blo o kern/152488 fs [tmpfs] [patch] mtime of file updated when only inode o kern/152079 fs [msdosfs] [patch] Small cleanups from the other NetBSD o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o kern/151845 fs [smbfs] [patch] smbfs should be upgraded to support Un o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150796 fs [panic] [suj] [ufs] [softupdates] Panic on portbuild o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/150207 fs zpool(1): zpool import -d /dev tries to open weird dev o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149022 fs [hang] File system operations hangs with suspfs state o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o bin/148296 fs [zfs] [loader] [patch] Very slow probe in /usr/src/sys o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server o kern/146375 fs [nfs] [patch] Typos in macro variables names in sys/fs s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c o kern/144458 fs [nfs] [patch] nfsd fails as a kld p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143345 fs [ext2fs] [patch] extfs minor header cleanups to better o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142924 fs [ext2fs] [patch] Small cleanup for the inode struct in o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142401 fs [ntfs] [patch] Minor updates to NTFS from NetBSD o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs o bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138790 fs [zfs] ZFS ceases caching when mem demand is high o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic o kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135667 fs [lor] LORs causing ufs filesystem corruption on XEN Do o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [panic] panic: ffs_truncate: read-only filesystem o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [ffs] [snapshot] System crashes when manipulat o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with 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 bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o bin/94635 fs snapinfo(8)/libufs only works for disk-backed filesyst o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 214 problems total. From owner-freebsd-fs@FreeBSD.ORG Wed Dec 29 19:48:04 2010 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 0A924106566B for ; Wed, 29 Dec 2010 19:48: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 A0ADE8FC1C for ; Wed, 29 Dec 2010 19:48:01 +0000 (UTC) Received: (qmail 96647 invoked from network); 29 Dec 2010 19:48:01 -0000 Received: from unknown (HELO ?192.168.0.189?) (spawk@66.206.120.2) by acm.poly.edu with CAMELLIA256-SHA encrypted SMTP; 29 Dec 2010 19:48:01 -0000 Message-ID: <4D1B9071.4020403@acm.poly.edu> Date: Wed, 29 Dec 2010 14:48:01 -0500 From: Boris Kochergin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101216 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: SUJ doesn't work with GELI? 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, 29 Dec 2010 19:48:04 -0000 Ahoy. I'm having trouble enabling SUJ on a UFS filesystem that lives on top of a GELI device. The system is an i386 -CURRENT build from December 24th. I first noticed the problem when it happened with an actual disk, but here is an example with a memory disk for ease of reproduction: root@t42 /root # dd if=/dev/zero of=file bs=1m count=500 500+0 records in 500+0 records out 524288000 bytes transferred in 29.282385 secs (17904553 bytes/sec) root@t42 /root # mdconfig -a -t vnode -f file md1 root@t42 /root # dd if=/dev/random of=key bs=64 count=1 1+0 records in 1+0 records out 64 bytes transferred in 0.000082 secs (780336 bytes/sec) root@t42 /root # geli init -s 4096 -K key /dev/md1 Enter new passphrase: Reenter new passphrase: Metadata backup can be found in /var/backups/md1.eli and can be restored with the following command: # geli restore /var/backups/md1.eli /dev/md1 root@t42 /root # geli attach -k key /dev/md1 Enter passphrase: root@t42 /root # newfs /dev/md1.eli /dev/md1.eli: 500.0MB (1023992 sectors) block size 16384, fragment size 4096 using 4 cylinder groups of 125.00MB, 8000 blks, 8000 inodes. super-block backups (for fsck -b #) at: 160, 256160, 512160, 768160 root@t42 /root # fsck_ufs -y /dev/md1.eli ** /dev/md1.eli ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2 files, 2 used, 125944 free (12 frags, 31483 blocks, 0.0% fragmentation) ***** FILE SYSTEM IS CLEAN ***** tunefs -root@t42 /root # tunefs -j enable /dev/md1.eli Using inode 4 in cg 0 for 4194304 byte journal tunefs: Failed to read dir block: Invalid argument tunefs: soft updates journaling can not be enabled If I take GELI out of the picture, it works: root@t42 /root # newfs /dev/md1 /dev/md1: 500.0MB (1024000 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 125.02MB, 8001 blks, 16064 inodes. super-block backups (for fsck -b #) at: 160, 256192, 512224, 768256 root@t42 /root # fsck_ufs -y /dev/md1 ** /dev/md1 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2 files, 2 used, 247861 free (21 frags, 30980 blocks, 0.0% fragmentation) ***** FILE SYSTEM IS CLEAN ***** root@t42 /root # tunefs -j enable /dev/md1 Using inode 4 in cg 0 for 4194304 byte journal tunefs: soft updates journaling set Thoughts? -Boris From owner-freebsd-fs@FreeBSD.ORG Wed Dec 29 22:35:00 2010 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 39B13106564A for ; Wed, 29 Dec 2010 22:35:00 +0000 (UTC) (envelope-from chris@bab.cabstand.com) Received: from bab.cabstand.com (bab.cabstand.com [76.246.87.242]) by mx1.freebsd.org (Postfix) with ESMTP id 0F55D8FC08 for ; Wed, 29 Dec 2010 22:34:59 +0000 (UTC) Received: from bab.cabstand.com (localhost [127.0.0.1]) by bab.cabstand.com (8.13.8/8.13.8) with ESMTP id oBTMI1Bl055057 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Wed, 29 Dec 2010 14:18:01 -0800 (PST) (envelope-from chris@bab.cabstand.com) Received: (from chris@localhost) by bab.cabstand.com (8.13.8/8.13.8/Submit) id oBTMI1BT055056 for freebsd-fs@freebsd.org; Wed, 29 Dec 2010 14:18:01 -0800 (PST) (envelope-from chris) Date: Wed, 29 Dec 2010 14:18:01 -0800 From: Chris Peiffer To: freebsd-fs@freebsd.org Message-ID: <20101229221801.GA48661@cabstand.com> Mail-Followup-To: freebsd-fs@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: how big can kern.maxvnodes get? 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, 29 Dec 2010 22:35:00 -0000 I have a backend server running 8-2-PRERELEASE with lots of independent files that randomly grow and then get truncated to zero. (Think popserver.) Roughly 2.5 million inodes on each of 4 Intel SSD disks. 24 gb of RAM in the system. I want to maximize the buffer cache in RAM. I doubled kern.maxvnodes to 942108 and reads/second went down and memory use went up, (as I expected) but right now there's still about 15g RAM marked as free. vfs.numvnodes crept up to 821704 and has hovered there. The file sizes range to 1 mb but most are in the range 0-10k. Since the server operations are so simple kern.openfiles hovers in the range 100-200. Obviously, all things being equal I'd like to give the filesystem buffer cache access to that free RAM by allowing more vnodes to stay cached. Can I increase kern.maxvnodes by another factor of 2? more? Are there any known problems with stepping it up, besides general memory exhaustion? With so much free RAM I'd like to turn the dial a little bit but I wonder if there are other linked things I should watch out for. Thanks. Here are some lines from vmstat -z that might be relevant: ITEM SIZE LIMIT USED FREE REQUESTS FAILURES VNODE: 472, 0, 779555, 69229, 163219829, 0 VNODEPOLL: 112, 0, 2, 64, 4, 0 S VFS Cache: 108, 0, 761856, 63606, 504696076, 0 L VFS Cache: 328, 0, 0, 228, 300, 0 From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 00:27:40 2010 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 D2D38106564A for ; Thu, 30 Dec 2010 00:27:40 +0000 (UTC) (envelope-from dsamms@nw-ds.com) Received: from nw-ds.com (nw-ds.com [66.165.113.38]) by mx1.freebsd.org (Postfix) with ESMTP id A75708FC0A for ; Thu, 30 Dec 2010 00:27:40 +0000 (UTC) Received: from nw-ds.com (localhost [127.0.0.38]) by nw-ds.com (Postfix) with ESMTP id AD9F24BDEFC for ; Wed, 29 Dec 2010 19:11:34 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nw-ds.com; h= content-transfer-encoding:content-type:content-type:subject :subject:mime-version:user-agent:from:from:date:date:message-id :received:received; s=mail; t=1293667893; x=1295482293; bh=kYGRO Zfx37lwsgTe3jZgzcH78yeoRf4WlWEGKI7qSbQ=; b=erI7EiHHwTtCBPy9HM70t xalQb8C/Iob8eZl0fmudC0wuhlAxy1HePc/z4ETLUBLbi50bZaDPX+ZVDoV1yGxU iZ1Yf0UqyqxF1QY8Fl2xr9AqxzvJx3tqk25RkZvV4CJe/b9eFGXl9pnCRorAGCyD ejKZ8t++HAvVVN6I5TOERM= X-Virus-Scanned: amavisd-new at nw-ds.com Received: from nw-ds.com ([127.0.0.38]) by nw-ds.com (nw-ds.com [127.0.0.38]) (amavisd-new, port 10026) with ESMTP id 6jJjntD1URQB for ; Wed, 29 Dec 2010 19:11:33 -0500 (EST) Received: from [192.168.160.70] (host-174-44-170-66.hln-mt.client.bresnan.net [174.44.170.66]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by nw-ds.com (Postfix) with ESMTPSA id 603F44BDEEB for ; Wed, 29 Dec 2010 19:11:33 -0500 (EST) Message-ID: <4D1BCE34.4090601@nw-ds.com> Date: Wed, 29 Dec 2010 17:11:32 -0700 From: David Samms User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101228 Thunderbird/3.0.11 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 8.2-RC1 and 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, 30 Dec 2010 00:27:40 -0000 I gave ZFS a try again this afternoon and immediately came across what I would consider a problem. Simply running dd causes such IO contention that a GUI desktop is unusable and MP3s stop playing. The problem is very repeatable, just run dd if=/dev/zero of=big bs=1m count=6400 System is amd64, source updated Dec 27. Default ZFS parameters. (no tuning). With the same system but UFS+s dd causes no problems. -- David Samms New World Data Systems (614) 619-0000 From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 01:41:54 2010 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 444C1106566B; Thu, 30 Dec 2010 01:41:54 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 34F398FC08; Thu, 30 Dec 2010 01:41:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBU1fspO013795; Thu, 30 Dec 2010 01:41:54 GMT (envelope-from cperciva@freefall.freebsd.org) Received: (from cperciva@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBU1frE8013791; Thu, 30 Dec 2010 01:41:53 GMT (envelope-from cperciva) Date: Thu, 30 Dec 2010 01:41:53 GMT Message-Id: <201012300141.oBU1frE8013791@freefall.freebsd.org> To: alex.urbanowicz@artegence.com, cperciva@FreeBSD.org, freebsd-fs@FreeBSD.org, freebsd-xen@FreeBSD.org From: cperciva@FreeBSD.org Cc: Subject: Re: kern/135667: ufs filesystem corruption on XEN DomU system X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2010 01:41:54 -0000 Old Synopsis: [lor] LORs causing ufs filesystem corruption on XEN DomU system New Synopsis: ufs filesystem corruption on XEN DomU system State-Changed-From-To: open->feedback State-Changed-By: cperciva State-Changed-When: Thu Dec 30 01:40:36 UTC 2010 State-Changed-Why: Move into state feedback pending confirmation of whether this can still be reproduced (I think I might have fixed it with one of my recent commits). Responsible-Changed-From-To: freebsd-fs->freebsd-xen Responsible-Changed-By: cperciva Responsible-Changed-When: Thu Dec 30 01:40:36 UTC 2010 Responsible-Changed-Why: Reassign Xen bug to freebsd-xen. It's very unlikely that this is filesystem related. http://www.freebsd.org/cgi/query-pr.cgi?pr=135667 From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 02:54:31 2010 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 61A8C106566B for ; Thu, 30 Dec 2010 02:54:31 +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 004D68FC16 for ; Thu, 30 Dec 2010 02:54:30 +0000 (UTC) Received: (qmail 8802 invoked from network); 30 Dec 2010 02:54:30 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@96.224.221.101) by acm.poly.edu with CAMELLIA256-SHA encrypted SMTP; 30 Dec 2010 02:54:30 -0000 Message-ID: <4D1BF45D.7070703@acm.poly.edu> Date: Wed, 29 Dec 2010 21:54:21 -0500 From: Boris Kochergin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.12) Gecko/20101031 Thunderbird/3.1.6 MIME-Version: 1.0 To: Lucius Windschuh References: <4D1B9071.4020403@acm.poly.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Jeff Roberson Subject: Re: SUJ doesn't work with GELI? 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, 30 Dec 2010 02:54:31 -0000 On 12/29/10 21:44, Lucius Windschuh wrote: > 2010/12/29 Boris Kochergin: >> Ahoy. I'm having trouble enabling SUJ on a UFS filesystem that lives on top >> of a GELI device. The system is an i386 -CURRENT build from December 24th. I >> first noticed the problem when it happened with an actual disk, but here is >> an example with a memory disk for ease of reproduction: > Hi Boris. > The problem is, as you may have already noticed, the "non-standard" > block size of 4k of the GELI device. > If you specify the tradiditional block size of 512 bytes when > initializing the GELI provider, it should work. > > I sent an email to Jeff, the answer on April 27 was: >> Thanks for the repro. This is an interesting case. I'll have to slightly rewrite the directory handling code in tunefs but it should not take long. > But I forgot to remind Jeff about this issue, as it seems. So I'll try > again with this mail... > > Regards, > > Lucius Aha. I hadn't thought of that. Thanks for the insight. -Boris From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 03:08:36 2010 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 78385106564A for ; Thu, 30 Dec 2010 03:08:36 +0000 (UTC) (envelope-from lwindschuh@googlemail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 41C5E8FC0A for ; Thu, 30 Dec 2010 03:08:35 +0000 (UTC) Received: by iwn39 with SMTP id 39so10813320iwn.13 for ; Wed, 29 Dec 2010 19:08:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=95sfSvm4Cia4t2qBAWS60CnmIlAnP2Nv5IFJ4XnLaeI=; b=naXig4cfLdnIc3vkqpEIDUB2R108XxvAiPu839QqH8GzQTrwIK6i/BkNmMZeN0fjBI ZcmXkv3mRWqcEshgrCeJQIE3gtKCT+/LlI1EDQJLIJNyHXdXKf84k8AGXtD9lygzl+w9 wHLJ9gMmrUUwUUUndQVIW88KnEmT0YwCxgFC4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=R9c4mYNGymgFRGn6lIZw8By+2p1wDSnNCJLLi3ndNe414xPOTJ91RvR6+1DNRW8gqu FH6GIW2Nn6FHmpphUZrKodBIDl9J/mA9PrDfWG2tZjgKqxCCFowDKFfRf3DhXCcTx7ch HwSVr34VZZd9V6ufpdGsIR4uD/YS5ZkDPu8DU= MIME-Version: 1.0 Received: by 10.231.199.76 with SMTP id er12mr15475519ibb.72.1293677075021; Wed, 29 Dec 2010 18:44:35 -0800 (PST) Received: by 10.231.191.69 with HTTP; Wed, 29 Dec 2010 18:44:34 -0800 (PST) In-Reply-To: <4D1B9071.4020403@acm.poly.edu> References: <4D1B9071.4020403@acm.poly.edu> Date: Thu, 30 Dec 2010 03:44:34 +0100 Message-ID: From: Lucius Windschuh To: Boris Kochergin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, Jeff Roberson Subject: Re: SUJ doesn't work with GELI? 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, 30 Dec 2010 03:08:36 -0000 2010/12/29 Boris Kochergin : > Ahoy. I'm having trouble enabling SUJ on a UFS filesystem that lives on top > of a GELI device. The system is an i386 -CURRENT build from December 24th. I > first noticed the problem when it happened with an actual disk, but here is > an example with a memory disk for ease of reproduction: Hi Boris. The problem is, as you may have already noticed, the "non-standard" block size of 4k of the GELI device. If you specify the tradiditional block size of 512 bytes when initializing the GELI provider, it should work. I sent an email to Jeff, the answer on April 27 was: > Thanks for the repro. This is an interesting case. I'll have to slightly rewrite the directory handling code in tunefs but it should not take long. But I forgot to remind Jeff about this issue, as it seems. So I'll try again with this mail... Regards, Lucius From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 08:57:27 2010 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 6A111106564A for ; Thu, 30 Dec 2010 08:57:27 +0000 (UTC) (envelope-from marco@tolstoy.tols.org) Received: from tolstoy.tols.org (tolstoy.tols.org [IPv6:2a02:898:0:20::57:1]) by mx1.freebsd.org (Postfix) with ESMTP id F39128FC12 for ; Thu, 30 Dec 2010 08:57:26 +0000 (UTC) Received: from tolstoy.tols.org (localhost [127.0.0.1]) by tolstoy.tols.org (8.14.4/8.14.4) with ESMTP id oBU8vNws038491 for ; Thu, 30 Dec 2010 08:57:23 GMT (envelope-from marco@tolstoy.tols.org) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.96.5 at tolstoy.tols.org Received: (from marco@localhost) by tolstoy.tols.org (8.14.4/8.14.4/Submit) id oBU8vNfr038490 for freebsd-fs@freebsd.org; Thu, 30 Dec 2010 09:57:23 +0100 (CET) (envelope-from marco) Date: Thu, 30 Dec 2010 09:57:23 +0100 From: Marco van Tol To: freebsd-fs@freebsd.org Message-ID: <20101230085723.GA38391@tolstoy.tols.org> Mail-Followup-To: freebsd-fs@freebsd.org References: <4D1BCE34.4090601@nw-ds.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D1BCE34.4090601@nw-ds.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on tolstoy.tols.org Subject: Re: 8.2-RC1 and 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, 30 Dec 2010 08:57:27 -0000 On Wed, Dec 29, 2010 at 05:11:32PM -0700, David Samms wrote: > I gave ZFS a try again this afternoon and immediately came across what I > would consider a problem. Simply running dd causes such IO contention > that a GUI desktop is unusable and MP3s stop playing. The problem is > very repeatable, just run dd if=/dev/zero of=big bs=1m count=6400 > > System is amd64, source updated Dec 27. Default ZFS parameters. (no > tuning). With the same system but UFS+s dd causes no problems. Check out this mail from Jeremy Chadwick from December 28th in freebsd-stable@. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=312384+0+current/freebsd-stable I think specifically the comments and tweaks regarding vfs.zfs.txg.timeout="5" and vfs.zfs.txg.write_limit_override=1073741824 should be usefull for you. :-) I'm intentionally not touching the subject why you see what you do without tuning. I'm sure there are a great bunch of different situations for which the defaults are the way they are. :-) Marco van Tol -- "Van Duitsers heb je pas gewonnen als ze met de bus de stad uit zijn." - Youp van 't Hek From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 09:05:21 2010 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 E7544106564A; Thu, 30 Dec 2010 09:05:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 4BBC48FC18; Thu, 30 Dec 2010 09:05:19 +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 oBU959FK000233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Dec 2010 11:05:09 +0200 (EET) (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.4/8.14.4) with ESMTP id oBU9591W072182; Thu, 30 Dec 2010 11:05:09 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id oBU957XW072180; Thu, 30 Dec 2010 11:05:07 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 30 Dec 2010 11:05:07 +0200 From: Kostik Belousov To: Boris Kochergin Message-ID: <20101230090507.GD90883@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="N6OI5UwltL9FF6Nb" Content-Disposition: inline In-Reply-To: <4D1BF45D.7070703@acm.poly.edu> 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=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS,FAKE_REPLY_C autolearn=no 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, Jeff Roberson , Kirk McKusick Subject: Re: SUJ doesn't work with GELI? 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, 30 Dec 2010 09:05:21 -0000 --N6OI5UwltL9FF6Nb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 29, 2010 at 09:54:21PM -0500, Boris Kochergin wrote: > On 12/29/10 21:44, Lucius Windschuh wrote: > >2010/12/29 Boris Kochergin: > >>Ahoy. I'm having trouble enabling SUJ on a UFS filesystem that lives on= =20 > >>top > >>of a GELI device. The system is an i386 -CURRENT build from December=20 > >>24th. I > >>first noticed the problem when it happened with an actual disk, but her= e=20 > >>is > >>an example with a memory disk for ease of reproduction: > >Hi Boris. > >The problem is, as you may have already noticed, the "non-standard" > >block size of 4k of the GELI device. > >If you specify the tradiditional block size of 512 bytes when > >initializing the GELI provider, it should work. > > > >I sent an email to Jeff, the answer on April 27 was: > >>Thanks for the repro. This is an interesting case. I'll have to=20 > >>slightly rewrite the directory handling code in tunefs but it should no= t=20 > >>take long. > >But I forgot to remind Jeff about this issue, as it seems. So I'll try > >again with this mail... > > > >Regards, > > > >Lucius >=20 > Aha. I hadn't thought of that. Thanks for the insight. I had the following patch lurking around for some time. This is only for the kernel, I did not have time to go through the usermode tools. diff --git a/sys/ufs/ffs/ffs_softdep.c b/sys/ufs/ffs/ffs_softdep.c index 002911c..4f4e020 100644 --- a/sys/ufs/ffs/ffs_softdep.c +++ b/sys/ufs/ffs/ffs_softdep.c @@ -747,7 +747,7 @@ static void handle_written_jnewblk(struct jnewblk *); static void handle_written_jfreeblk(struct jfreeblk *); static void handle_written_jfreefrag(struct jfreefrag *); static void complete_jseg(struct jseg *); -static void jseg_write(struct fs *, struct jblocks *, struct jseg *, +static void jseg_write(struct ufsmount *ump, struct jblocks *, struct jseg= *, uint8_t *); static void jaddref_write(struct jaddref *, struct jseg *, uint8_t *); static void jremref_write(struct jremref *, struct jseg *, uint8_t *); @@ -886,7 +886,8 @@ static void handle_jwork(struct workhead *); static struct mkdir *setup_newdir(struct diradd *, ino_t, ino_t, struct bu= f *, struct mkdir **); static struct jblocks *jblocks_create(void); -static ufs2_daddr_t jblocks_alloc(struct jblocks *, int, int *); +static ufs2_daddr_t jblocks_alloc(struct ufsmount *, struct jblocks *, int, + int *); static void jblocks_free(struct jblocks *, struct mount *, int); static void jblocks_destroy(struct jblocks *); static void jblocks_add(struct jblocks *, ufs2_daddr_t, int); @@ -2135,7 +2136,8 @@ jblocks_create(void) } =20 static ufs2_daddr_t -jblocks_alloc(jblocks, bytes, actual) +jblocks_alloc(ump, jblocks, bytes, actual) + struct ufsmount *ump; struct jblocks *jblocks; int bytes; int *actual; @@ -2145,7 +2147,7 @@ jblocks_alloc(jblocks, bytes, actual) int freecnt; int blocks; =20 - blocks =3D bytes / DEV_BSIZE; + blocks =3D bytes / ump->um_devvp->v_bufobj.bo_bsize; jext =3D &jblocks->jb_extent[jblocks->jb_head]; freecnt =3D jext->je_blocks - jblocks->jb_off; if (freecnt =3D=3D 0) { @@ -2157,7 +2159,7 @@ jblocks_alloc(jblocks, bytes, actual) } if (freecnt > blocks) freecnt =3D blocks; - *actual =3D freecnt * DEV_BSIZE; + *actual =3D freecnt * ump->um_devvp->v_bufobj.bo_bsize; daddr =3D jext->je_daddr + jblocks->jb_off; jblocks->jb_off +=3D freecnt; jblocks->jb_free -=3D freecnt; @@ -2172,7 +2174,7 @@ jblocks_free(jblocks, mp, bytes) int bytes; { =20 - jblocks->jb_free +=3D bytes / DEV_BSIZE; + jblocks->jb_free +=3D bytes / VFSTOUFS(mp)->um_devvp->v_bufobj.bo_bsize; if (jblocks->jb_suspended) worklist_speedup(); wakeup(jblocks); @@ -2422,7 +2424,8 @@ journal_space(ump, thresh) thresh =3D jblocks->jb_min; else thresh =3D jblocks->jb_low; - avail =3D (ump->softdep_on_journal * JREC_SIZE) / DEV_BSIZE; + avail =3D (ump->softdep_on_journal * JREC_SIZE) / + ump->um_devvp->v_bufobj.bo_bsize; avail =3D jblocks->jb_free - avail; =20 return (avail > thresh); @@ -2555,8 +2558,8 @@ softdep_prelink(dvp, vp) } =20 static void -jseg_write(fs, jblocks, jseg, data) - struct fs *fs; +jseg_write(ump, jblocks, jseg, data) + struct ufsmount *ump; struct jblocks *jblocks; struct jseg *jseg; uint8_t *data; @@ -2567,9 +2570,9 @@ jseg_write(fs, jblocks, jseg, data) rec->jsr_seq =3D jseg->js_seq; rec->jsr_oldest =3D jblocks->jb_oldestseq; rec->jsr_cnt =3D jseg->js_cnt; - rec->jsr_blocks =3D jseg->js_size / DEV_BSIZE; + rec->jsr_blocks =3D jseg->js_size / ump->um_devvp->v_bufobj.bo_bsize; rec->jsr_crc =3D 0; - rec->jsr_time =3D fs->fs_mtime; + rec->jsr_time =3D ump->um_fs->fs_mtime; } =20 static inline void @@ -2719,19 +2722,21 @@ softdep_process_journal(mp, flags) int size; int cnt; int off; + int devbsize; =20 if ((mp->mnt_kern_flag & MNTK_SUJ) =3D=3D 0) return; ump =3D VFSTOUFS(mp); fs =3D ump->um_fs; jblocks =3D ump->softdep_jblocks; + devbsize =3D ump->um_devvp->v_bufobj.bo_bsize; /* * We write anywhere between a disk block and fs block. The upper * bound is picked to prevent buffer cache fragmentation and limit * processing time per I/O. */ - jrecmin =3D (DEV_BSIZE / JREC_SIZE) - 1; /* -1 for seg header */ - jrecmax =3D (fs->fs_bsize / DEV_BSIZE) * jrecmin; + jrecmin =3D (devbsize / JREC_SIZE) - 1; /* -1 for seg header */ + jrecmax =3D (fs->fs_bsize / devbsize) * jrecmin; segwritten =3D 0; while ((cnt =3D ump->softdep_on_journal) !=3D 0) { /* @@ -2786,7 +2791,7 @@ softdep_process_journal(mp, flags) */ cnt =3D ump->softdep_on_journal; if (cnt < jrecmax) - size =3D howmany(cnt, jrecmin) * DEV_BSIZE; + size =3D howmany(cnt, jrecmin) * devbsize; else size =3D fs->fs_bsize; /* @@ -2794,9 +2799,10 @@ softdep_process_journal(mp, flags) * for truncation of the requested size if enough contiguous * space was not available. */ - bp->b_blkno =3D jblocks_alloc(jblocks, size, &size); + bp->b_blkno =3D jblocks_alloc(ump, jblocks, size, &size) * + btodb(devbsize); bp->b_lblkno =3D bp->b_blkno; - bp->b_offset =3D bp->b_blkno * DEV_BSIZE; + bp->b_offset =3D bp->b_blkno * devbsize; bp->b_bcount =3D size; bp->b_bufobj =3D &ump->um_devvp->v_bufobj; bp->b_flags &=3D ~B_INVAL; @@ -2806,7 +2812,7 @@ softdep_process_journal(mp, flags) * sequence number to it and link it in-order. */ cnt =3D MIN(ump->softdep_on_journal, - (size / DEV_BSIZE) * jrecmin); + (size / devbsize) * jrecmin); jseg->js_buf =3D bp; jseg->js_cnt =3D cnt; jseg->js_refs =3D cnt + 1; /* Self ref. */ @@ -2825,8 +2831,8 @@ softdep_process_journal(mp, flags) while ((wk =3D LIST_FIRST(&ump->softdep_journal_pending)) !=3D NULL) { /* Place a segment header on every device block. */ - if ((off % DEV_BSIZE) =3D=3D 0) { - jseg_write(fs, jblocks, jseg, data); + if ((off % devbsize) =3D=3D 0) { + jseg_write(ump, jblocks, jseg, data); off +=3D JREC_SIZE; data =3D bp->b_data + off; } --N6OI5UwltL9FF6Nb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk0cS0IACgkQC3+MBN1Mb4g8bACgqesddF3TRiNB/4pZ0V693ZAh ggAAn3+XCUz+bba8rE/1tBT85JCW0p6n =Tk3e -----END PGP SIGNATURE----- --N6OI5UwltL9FF6Nb-- From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 14:37:40 2010 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 23BD7106564A for ; Thu, 30 Dec 2010 14:37:40 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id EC3748FC0A for ; Thu, 30 Dec 2010 14:37:39 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id A64AC46B06 for ; Thu, 30 Dec 2010 09:37:39 -0500 (EST) Received: from John-Baldwins-Macbook-Pro.local (c-68-36-150-83.hsd1.nj.comcast.net [68.36.150.83]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 45E9D8A009 for ; Thu, 30 Dec 2010 09:37:38 -0500 (EST) Message-ID: <4D1C9931.2060209@FreeBSD.org> Date: Thu, 30 Dec 2010 09:37:37 -0500 From: John Baldwin User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20101229221801.GA48661@cabstand.com> In-Reply-To: <20101229221801.GA48661@cabstand.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 30 Dec 2010 09:37:38 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-0.9 required=4.2 tests=BAYES_00,RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Subject: Re: how big can kern.maxvnodes get? 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, 30 Dec 2010 14:37:40 -0000 Chris Peiffer wrote: > I have a backend server running 8-2-PRERELEASE with lots of > independent files that randomly grow and then get truncated to > zero. (Think popserver.) > > Roughly 2.5 million inodes on each of 4 Intel SSD disks. 24 gb of RAM > in the system. I want to maximize the buffer cache in RAM. > > I doubled kern.maxvnodes to 942108 and reads/second went down and > memory use went up, (as I expected) but right now there's still about > 15g RAM marked as free. > > vfs.numvnodes crept up to 821704 and has hovered there. The file > sizes range to 1 mb but most are in the range 0-10k. Since the server > operations are so simple kern.openfiles hovers in the range 100-200. > > Obviously, all things being equal I'd like to give the filesystem > buffer cache access to that free RAM by allowing more vnodes to stay > cached. > > Can I increase kern.maxvnodes by another factor of 2? more? Are there > any known problems with stepping it up, besides general memory > exhaustion? With so much free RAM I'd like to turn the dial a little > bit but I wonder if there are other linked things I should watch out > for. You can increase it, but if numvnodes is less than maxvnodes then it won't help you as the system hasn't had to recycle any vnodes yet. It is already caching all the vnodes you have accessed in that case. If the files are frequently truncated then you may end up with a lot of free RAM simply because there isn't enough recently used data to cache. The VM system will cache everything that is accessed until either 1) the pages become invalid (e.g. due to an unlink or truncate) or 2) free memory runs low enough to trigger pagedaemon to harvest some inactive pages. If you have 15G of free RAM, then 2) isn't happening and your working set is less than your RAM. -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 16:54:43 2010 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 26E9E1065696 for ; Thu, 30 Dec 2010 16:54:43 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id A29A08FC1D for ; Thu, 30 Dec 2010 16:54:42 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PYLlx-0006dP-CV for freebsd-fs@freebsd.org; Thu, 30 Dec 2010 17:54:41 +0100 Received: from host-174-44-170-66.hln-mt.client.bresnan.net ([174.44.170.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 30 Dec 2010 17:54:41 +0100 Received: from dsamms by host-174-44-170-66.hln-mt.client.bresnan.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 30 Dec 2010 17:54:41 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: David Samms Date: Thu, 30 Dec 2010 09:54:28 -0700 Lines: 64 Message-ID: References: <4D1BCE34.4090601@nw-ds.com> <20101230085723.GA38391@tolstoy.tols.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: host-174-44-170-66.hln-mt.client.bresnan.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101228 Thunderbird/3.0.11 In-Reply-To: <20101230085723.GA38391@tolstoy.tols.org> Subject: Re: 8.2-RC1 and 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, 30 Dec 2010 16:54:43 -0000 On 12/30/10 01:57, Marco van Tol wrote: > On Wed, Dec 29, 2010 at 05:11:32PM -0700, David Samms wrote: >> I gave ZFS a try again this afternoon and immediately came across what I >> would consider a problem. Simply running dd causes such IO contention >> that a GUI desktop is unusable and MP3s stop playing. The problem is >> very repeatable, just run dd if=/dev/zero of=big bs=1m count=6400 >> >> System is amd64, source updated Dec 27. Default ZFS parameters. (no >> tuning). With the same system but UFS+s dd causes no problems. > > Check out this mail from Jeremy Chadwick from December 28th in > freebsd-stable@. > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=312384+0+current/freebsd-stable > > I think specifically the comments and tweaks regarding > vfs.zfs.txg.timeout="5" and vfs.zfs.txg.write_limit_override=1073741824 > should be usefull for you. :-) > > I'm intentionally not touching the subject why you see what you do > without tuning. I'm sure there are a great bunch of different > situations for which the defaults are the way they are. > > :-) > > Marco van Tol > Marco, thank you for your reply. Jeremy, thank you for your tuning suggestions. It does appear that the default setting for ZFS are NOT well suited for a single drive setup. Based on Jeremy's suggestions I made the following changes from the defaults: vfs.zfs.txg.timeout="5" vfs.zfs.txg.write_limit_override=268435456 # (System has 4G of RAM) kern.maxvnodes=250000 I tested both UFS+s and ZFS for desktop usability while running "dd" to create IO contention. System has two identical 300G WD drives that are about 4 years old. For testing I switch at boot between the drives, one is ZFS the other UFS+s. Test was performed using XFCE4 with xmms playing MP3s while "dd" was creating a large file and OpenOffice was launching. ZFS ---------------------------------------------------------------------- %dd if=/dev/zero of=big bs=1m count=6400 6710886400 bytes transferred in 177.418146 secs (37825254 bytes/sec) openoffice startup about 185 sec No MP3 skips XFCE4 popup menus took 1-3 seconds to appear UFS+s ---------------------------------------------------------------------- dd if=/dev/zero of=big bs=1m count=6400 6710886400 bytes transferred in 165.061623 secs (40656855 bytes/sec) openoffice startup about 185 sec No MP3 skips XFCE4 popup menus took 5-25 seconds to appear While dd IO was slower with the new ZFS parameters, the desktop was very usable, and its responsiveness was better than USF+s. I will be upgrading to ZFSv28 and repeating this rudimentary desktop usability test. From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 20:19:17 2010 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 06CB5106564A for ; Thu, 30 Dec 2010 20:19:17 +0000 (UTC) (envelope-from chris@bab.cabstand.com) Received: from bab.cabstand.com (bab.cabstand.com [76.246.87.242]) by mx1.freebsd.org (Postfix) with ESMTP id D03278FC13 for ; Thu, 30 Dec 2010 20:19:16 +0000 (UTC) Received: from bab.cabstand.com (localhost [127.0.0.1]) by bab.cabstand.com (8.13.8/8.13.8) with ESMTP id oBUKJFph007683 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Dec 2010 12:19:15 -0800 (PST) (envelope-from chris@bab.cabstand.com) Received: (from chris@localhost) by bab.cabstand.com (8.13.8/8.13.8/Submit) id oBUKJFxq007681 for freebsd-fs@freebsd.org; Thu, 30 Dec 2010 12:19:15 -0800 (PST) (envelope-from chris) Date: Thu, 30 Dec 2010 12:19:15 -0800 From: Chris Peiffer To: freebsd-fs@freebsd.org Message-ID: <20101230201915.GA3256@cabstand.com> Mail-Followup-To: freebsd-fs@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: truncate vs. unlink, unexpected results 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, 30 Dec 2010 20:19:17 -0000 As I stated in another question about vnodes, I have a backend server running 8.2-PRERELEASE that processes a lot of independent files that grow randomly and then go to zero. (Like a popserver.) The disks are Intel SSD drives with default newfs settings-- 16k blocks, 2k frags, soft updates. In trying to improve perf we made an application-level change so that instead of deleting files once they are popped, the file is kept and truncated to zero. The thinking was that this would save the write and metadata write to the directory information (since metadata writes are expensive, in that they force a semi-synchronous write operation in noasync+SU mode) at the expense of more used inodes and bigger directories. The server architecture consists of two machines running the same set of operations on the same dataset via erlang mirroring, so we were able to change the code on one and observe the differences. On the truncate machine, the number of write operations is now indeed lower, as expected. It's usually 10-15% lower over long (100-second) intervals. But the total data written went up by about 30%. svc_t went up by 100-200% and %b was slightly higher. Why does truncate result in more data written and worse performance across fewer write operations? Most of the files are small, under 10k, but some are up to 1m. The blocks have to be reclaimed either way, right? My understanding of what happens in each case: unlink: dir modified, dir inode modified, file inode freed, blocks freed truncate: file inode modified, blocks freed Is it possible I'm seeing an SSD-related issue-- truncate is forcing more expensive overwrites, whereas unlink lets the filesystem write new data into empty space? (for a while anyway.) I hope I'm making a simple mistake in my thinking about the fs that someone can correct me on. Thanks. From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 20:27:57 2010 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 AB102106566C for ; Thu, 30 Dec 2010 20:27:57 +0000 (UTC) (envelope-from chris@bab.cabstand.com) Received: from bab.cabstand.com (bab.cabstand.com [76.246.87.242]) by mx1.freebsd.org (Postfix) with ESMTP id 612FE8FC0A for ; Thu, 30 Dec 2010 20:27:55 +0000 (UTC) Received: from bab.cabstand.com (localhost [127.0.0.1]) by bab.cabstand.com (8.13.8/8.13.8) with ESMTP id oBUKRtBO008152 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Thu, 30 Dec 2010 12:27:55 -0800 (PST) (envelope-from chris@bab.cabstand.com) Received: (from chris@localhost) by bab.cabstand.com (8.13.8/8.13.8/Submit) id oBUKRtZC008151; Thu, 30 Dec 2010 12:27:55 -0800 (PST) (envelope-from chris) Date: Thu, 30 Dec 2010 12:27:55 -0800 From: Chris Peiffer To: John Baldwin Message-ID: <20101230202755.GB3256@cabstand.com> Mail-Followup-To: John Baldwin , freebsd-fs@freebsd.org References: <20101229221801.GA48661@cabstand.com> <4D1C9931.2060209@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D1C9931.2060209@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org Subject: Re: how big can kern.maxvnodes get? 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, 30 Dec 2010 20:27:57 -0000 On Thu, Dec 30, 2010 at 09:37:37AM -0500, John Baldwin wrote: > Chris Peiffer wrote: > >I have a backend server running 8-2-PRERELEASE with lots of > >independent files that randomly grow and then get truncated to > >zero. (Think popserver.) > > > >Roughly 2.5 million inodes on each of 4 Intel SSD disks. 24 gb of RAM > >in the system. I want to maximize the buffer cache in RAM. > > > >I doubled kern.maxvnodes to 942108 and reads/second went down and > >memory use went up, (as I expected) but right now there's still about > >15g RAM marked as free. > > > >vfs.numvnodes crept up to 821704 and has hovered there. The file > >sizes range to 1 mb but most are in the range 0-10k. Since the server > >operations are so simple kern.openfiles hovers in the range 100-200. > > > >Obviously, all things being equal I'd like to give the filesystem > >buffer cache access to that free RAM by allowing more vnodes to stay > >cached. > > > >Can I increase kern.maxvnodes by another factor of 2? more? Are there > >any known problems with stepping it up, besides general memory > >exhaustion? With so much free RAM I'd like to turn the dial a little > >bit but I wonder if there are other linked things I should watch out > >for. > > You can increase it, but if numvnodes is less than maxvnodes then it > won't help you as the system hasn't had to recycle any vnodes yet. It > is already caching all the vnodes you have accessed in that case. > > If the files are frequently truncated then you may end up with a lot of > free RAM simply because there isn't enough recently used data to cache. > The VM system will cache everything that is accessed until either 1) > the pages become invalid (e.g. due to an unlink or truncate) or 2) free > memory runs low enough to trigger pagedaemon to harvest some inactive > pages. If you have 15G of free RAM, then 2) isn't happening and your > working set is less than your RAM. > Thanks John. The system has around 2m non-empty data files. I assumed that since the numvnodes quickly jumped to 820k and hovered, there must be some "min free" threshold below maxvnodes that an unloaded system would try to maintain. But I will investigate my exact working set before I tune maxvnodes up. From owner-freebsd-fs@FreeBSD.ORG Thu Dec 30 22:19:01 2010 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 4DADA10656A7; Thu, 30 Dec 2010 22:19:01 +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 24D078FC1C; Thu, 30 Dec 2010 22:19:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBUMJ1Wx079389; Thu, 30 Dec 2010 22:19:01 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBUMJ0UH079385; Thu, 30 Dec 2010 22:19:01 GMT (envelope-from linimon) Date: Thu, 30 Dec 2010 22:19:01 GMT Message-Id: <201012302219.oBUMJ0UH079385@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/153552: [zfs] zfsboot from 8.2-RC1 freeze at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2010 22:19:01 -0000 Old Synopsis: 'zfsboot from 8.2-RC1 freeze at boot time New Synopsis: [zfs] zfsboot from 8.2-RC1 freeze at boot time Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Dec 30 22:18:50 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=153552 From owner-freebsd-fs@FreeBSD.ORG Fri Dec 31 02:58:52 2010 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 51FC7106566C for ; Fri, 31 Dec 2010 02:58:52 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id D25338FC0C for ; Fri, 31 Dec 2010 02:58:51 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PYVCc-0006YE-Ek for freebsd-fs@freebsd.org; Fri, 31 Dec 2010 03:58:50 +0100 Received: from host-174-44-170-66.hln-mt.client.bresnan.net ([174.44.170.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 31 Dec 2010 03:58:50 +0100 Received: from dsamms by host-174-44-170-66.hln-mt.client.bresnan.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 31 Dec 2010 03:58:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: David Samms Date: Thu, 30 Dec 2010 19:58:37 -0700 Lines: 93 Message-ID: References: <4D1BCE34.4090601@nw-ds.com> <20101230085723.GA38391@tolstoy.tols.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: host-174-44-170-66.hln-mt.client.bresnan.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101228 Thunderbird/3.0.11 In-Reply-To: Subject: Re: 8.2-RC1 and 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: Fri, 31 Dec 2010 02:58:52 -0000 On 12/30/10 09:54, David Samms wrote: > On 12/30/10 01:57, Marco van Tol wrote: >> On Wed, Dec 29, 2010 at 05:11:32PM -0700, David Samms wrote: >>> I gave ZFS a try again this afternoon and immediately came across what I >>> would consider a problem. Simply running dd causes such IO contention >>> that a GUI desktop is unusable and MP3s stop playing. The problem is >>> very repeatable, just run dd if=/dev/zero of=big bs=1m count=6400 >>> >>> System is amd64, source updated Dec 27. Default ZFS parameters. (no >>> tuning). With the same system but UFS+s dd causes no problems. >> >> Check out this mail from Jeremy Chadwick from December 28th in >> freebsd-stable@. >> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=312384+0+current/freebsd-stable >> >> >> I think specifically the comments and tweaks regarding >> vfs.zfs.txg.timeout="5" and vfs.zfs.txg.write_limit_override=1073741824 >> should be usefull for you. :-) >> >> I'm intentionally not touching the subject why you see what you do >> without tuning. I'm sure there are a great bunch of different >> situations for which the defaults are the way they are. >> >> :-) >> >> Marco van Tol >> > > Marco, thank you for your reply. Jeremy, thank you for your tuning > suggestions. It does appear that the default setting for ZFS are NOT > well suited for a single drive setup. Based on Jeremy's suggestions I > made the following changes from the defaults: > > vfs.zfs.txg.timeout="5" > vfs.zfs.txg.write_limit_override=268435456 # (System has 4G of RAM) > kern.maxvnodes=250000 > > I tested both UFS+s and ZFS for desktop usability while running "dd" to > create IO contention. System has two identical 300G WD drives that are > about 4 years old. For testing I switch at boot between the drives, one > is ZFS the other UFS+s. Test was performed using XFCE4 with xmms playing > MP3s while "dd" was creating a large file and OpenOffice was launching. > > ZFS > ---------------------------------------------------------------------- > %dd if=/dev/zero of=big bs=1m count=6400 > 6710886400 bytes transferred in 177.418146 secs (37825254 bytes/sec) > > openoffice startup about 185 sec > No MP3 skips > XFCE4 popup menus took 1-3 seconds to appear > > UFS+s > ---------------------------------------------------------------------- > dd if=/dev/zero of=big bs=1m count=6400 > 6710886400 bytes transferred in 165.061623 secs (40656855 bytes/sec) > > openoffice startup about 185 sec > No MP3 skips > XFCE4 popup menus took 5-25 seconds to appear > > While dd IO was slower with the new ZFS parameters, the desktop was very > usable, and its responsiveness was better than USF+s. I will be > upgrading to ZFSv28 and repeating this rudimentary desktop usability test. The same test with ZFSv28 and ZFSv28 + tuning ZFSv28 ---------------------------------------------------------------------- dd if=/dev/zero of=big bs=1m count=6400 6710886400 bytes transferred in 158.205268 secs (42418855 bytes/sec) OpenOffice 197sec MP3 skips XFCE4 popup menus took 5-15 seconds to appear ZFSv28 + tuning --vfs.zfs.txg.timeout="5" --vfs.zfs.txg.write_limit_override=268435456 --kern.maxvnodes=250000 ---------------------------------------------------------------------- dd if=/dev/zero of=big bs=1m count=6400 6710886400 bytes transferred in 167.316444 secs (40108947 bytes/sec) OpenOffice 190sec No MP3 skips during "dd", but one skip while OpenOffice was starting XFCE4 popup menus took 2-13 seconds to appear From owner-freebsd-fs@FreeBSD.ORG Fri Dec 31 06:02:19 2010 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 91EEA1065672; Fri, 31 Dec 2010 06:02:19 +0000 (UTC) (envelope-from mckusick@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 688008FC13; Fri, 31 Dec 2010 06:02:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBV62J1J085147; Fri, 31 Dec 2010 06:02:19 GMT (envelope-from mckusick@freefall.freebsd.org) Received: (from mckusick@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBV62Jnu085143; Fri, 31 Dec 2010 06:02:19 GMT (envelope-from mckusick) Date: Fri, 31 Dec 2010 06:02:19 GMT Message-Id: <201012310602.oBV62Jnu085143@freefall.freebsd.org> To: mckusick@FreeBSD.org, freebsd-fs@FreeBSD.org, mckusick@FreeBSD.org From: mckusick@FreeBSD.org Cc: Subject: Re: kern/150796: [panic] [suj] [ufs] [softupdates] Panic on portbuild 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, 31 Dec 2010 06:02:19 -0000 Synopsis: [panic] [suj] [ufs] [softupdates] Panic on portbuild Responsible-Changed-From-To: freebsd-fs->mckusick Responsible-Changed-By: mckusick Responsible-Changed-When: Fri Dec 31 06:01:39 UTC 2010 Responsible-Changed-Why: ng over responsibility for this bug report. http://www.freebsd.org/cgi/query-pr.cgi?pr=150796 From owner-freebsd-fs@FreeBSD.ORG Fri Dec 31 10:10:11 2010 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 413361065674 for ; Fri, 31 Dec 2010 10:10:11 +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 1720D8FC1C for ; Fri, 31 Dec 2010 10:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBVAAAKZ045713 for ; Fri, 31 Dec 2010 10:10:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBVAAAli045712; Fri, 31 Dec 2010 10:10:10 GMT (envelope-from gnats) Date: Fri, 31 Dec 2010 10:10:10 GMT Message-Id: <201012311010.oBVAAAli045712@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Matuska Cc: Subject: Re: kern/153552: [zfs] zfsboot from 8.2-RC1 freeze at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Matuska List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2010 10:10:11 -0000 The following reply was made to PR kern/153552; it has been noted by GNATS. From: Martin Matuska To: bug-followup@FreeBSD.org, hlh@restart.be Cc: Subject: Re: kern/153552: [zfs] zfsboot from 8.2-RC1 freeze at boot time Date: Fri, 31 Dec 2010 11:05:04 +0100 Just a question - is there any particular reason why you are not using GPT partitioning? From owner-freebsd-fs@FreeBSD.ORG Fri Dec 31 15:10:12 2010 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 B288E106566C for ; Fri, 31 Dec 2010 15:10:12 +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 A1A198FC12 for ; Fri, 31 Dec 2010 15:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBVFAC56070709 for ; Fri, 31 Dec 2010 15:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBVFACuj070708; Fri, 31 Dec 2010 15:10:12 GMT (envelope-from gnats) Date: Fri, 31 Dec 2010 15:10:12 GMT Message-Id: <201012311510.oBVFACuj070708@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Henri Hennebert Cc: Subject: Re: kern/153552: [zfs] zfsboot from 8.2-RC1 freeze at boot time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Henri Hennebert List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2010 15:10:12 -0000 The following reply was made to PR kern/153552; it has been noted by GNATS. From: Henri Hennebert To: bug-followup@FreeBSD.org, hlh@restart.be Cc: Subject: Re: kern/153552: [zfs] zfsboot from 8.2-RC1 freeze at boot time Date: Fri, 31 Dec 2010 16:07:45 +0100 I'm using gpt on all my computers except the one which is hosted at OVH (http://www.ovh.com/). The standard procedure offered by OVH use MBR and install a slice of 6GB with FreeBSD 8.0. In case of problem I may ask (with the web interface) a net boot giving me a mfsBSD under FreeBSD 8.0. As I want to follow each release and use the latest ZFS, I keep the first slice under UFS and upgrade it to 8.x. The rest of the disk is a slice with ZFS. In normal use, this slice is used. In case of problem, I can switch to the first slice and make any repair on the second one because it contain a kernel able to import the ZPOOL. If the kernel is bad, I can netboot under 8.0, push any correction on the UFS slice, reboot from it and put the correction on the ZFS slice. I can repartition the disk with gpt but I would lost my data under ZFS. (Yes I have a backup but I prefer to keep all this running). On my netbook, I have a first slice with Windows7 preinstalled and the second one with ZFS. I have no CD allowing me to reinstall windows7. BTW thank you for your great work on ZFS. Henri From owner-freebsd-fs@FreeBSD.ORG Fri Dec 31 15:39:32 2010 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 B033C106564A for ; Fri, 31 Dec 2010 15:39:32 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5E5428FC13 for ; Fri, 31 Dec 2010 15:39:32 +0000 (UTC) Received: by qwj9 with SMTP id 9so11550088qwj.13 for ; Fri, 31 Dec 2010 07:39:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :date:in-reply-to:message-id:user-agent:mime-version:content-type; bh=4WxskeKtpqi0ttsSN+nC7DcO9PSWU568b6tymiDe3uQ=; b=LrjpLg2/P+1ldxdu9tfwBoe+G7EFMJrKISatzzZsJdhTZB4k3XP20SG0Bp4DPSTiW/ kVKHPnBZwC//Qcy6C1WRBlTPDDiOFgCDZYazY2QC/yXvm0yeWciXLWnRAd2IKTXP9A8l sqBfS57axCra8qSZ3+txihwcGTx64KPdbBzQ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=HTB1Q8Meu2djm5piXmk8uwHQsExPb6cW5SQVe9lfphVD35Qr36vccVu829LANr0I/D U6li6eMiglYXwqSzSltPgTSXkkCy/eflSd/WHA1cbeZv8eaERQ62fRCSsJRGbl3ACAu9 evUPMAf5rV6Pom3ujp7t7xTZ3Z1SLT10+kfuE= Received: by 10.229.191.130 with SMTP id dm2mr15646628qcb.16.1293808514670; Fri, 31 Dec 2010 07:15:14 -0800 (PST) Received: from localhost ([199.48.147.38]) by mx.google.com with ESMTPS id l12sm10039246qcu.19.2010.12.31.07.15.11 (version=SSLv3 cipher=RC4-MD5); Fri, 31 Dec 2010 07:15:14 -0800 (PST) From: Anonymous To: David Samms References: <4D1BCE34.4090601@nw-ds.com> <20101230085723.GA38391@tolstoy.tols.org> Date: Fri, 31 Dec 2010 18:14:56 +0300 In-Reply-To: (David Samms's message of "Thu, 30 Dec 2010 19:58:37 -0700") Message-ID: <8639pe55zj.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: freebsd-fs@freebsd.org Subject: Re: 8.2-RC1 and 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: Fri, 31 Dec 2010 15:39:32 -0000 David Samms writes: [...] > The same test with ZFSv28 and ZFSv28 + tuning > > ZFSv28 > ---------------------------------------------------------------------- > dd if=/dev/zero of=big bs=1m count=6400 > 6710886400 bytes transferred in 158.205268 secs (42418855 bytes/sec) > > OpenOffice 197sec > MP3 skips > XFCE4 popup menus took 5-15 seconds to appear > > > ZFSv28 + tuning > --vfs.zfs.txg.timeout="5" the tunable defaults to "5" in v28, see txg.c int zfs_txg_timeout = 5; /* max seconds worth of delta per txg */ > --vfs.zfs.txg.write_limit_override=268435456 No such tunable/sysctl. It was renamed to vfs.zfs.write_limit_override in v28 (note ".txg." absence). > --kern.maxvnodes=250000 > ---------------------------------------------------------------------- > dd if=/dev/zero of=big bs=1m count=6400 > 6710886400 bytes transferred in 167.316444 secs (40108947 bytes/sec) > > OpenOffice 190sec > No MP3 skips during "dd", but one skip while OpenOffice was starting > XFCE4 popup menus took 2-13 seconds to appear From owner-freebsd-fs@FreeBSD.ORG Fri Dec 31 16:10:12 2010 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 639251065675 for ; Fri, 31 Dec 2010 16:10:12 +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 39C898FC16 for ; Fri, 31 Dec 2010 16:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBVGACHY034954 for ; Fri, 31 Dec 2010 16:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBVGAC5S034953; Fri, 31 Dec 2010 16:10:12 GMT (envelope-from gnats) Date: Fri, 31 Dec 2010 16:10:12 GMT Message-Id: <201012311610.oBVGAC5S034953@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: "Pedro F. Giffuni" Cc: Subject: Re: kern/143345: [ext2fs] [patch] extfs minor header cleanups to better match NetBSD/UFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Pedro F. Giffuni" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2010 16:10:12 -0000 The following reply was made to PR kern/143345; it has been noted by GNATS. From: "Pedro F. Giffuni" To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/143345: [ext2fs] [patch] extfs minor header cleanups to better match NetBSD/UFS Date: Fri, 31 Dec 2010 08:06:49 -0800 (PST) Please close: this has been superceeded by PR 153584. From owner-freebsd-fs@FreeBSD.ORG Fri Dec 31 16:20:08 2010 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 8FA441065672 for ; Fri, 31 Dec 2010 16:20:08 +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 5C4328FC0A for ; Fri, 31 Dec 2010 16:20:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBVGK8o6046013 for ; Fri, 31 Dec 2010 16:20:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBVGK8ms046012; Fri, 31 Dec 2010 16:20:08 GMT (envelope-from gnats) Date: Fri, 31 Dec 2010 16:20:08 GMT Message-Id: <201012311620.oBVGK8ms046012@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: "Pedro F. Giffuni" Cc: Subject: Re: kern/142924: [ext2fs] [patch] Small cleanup for the inode struct in ext2fs (based on UFS) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Pedro F. Giffuni" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2010 16:20:08 -0000 The following reply was made to PR kern/142924; it has been noted by GNATS. From: "Pedro F. Giffuni" To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/142924: [ext2fs] [patch] Small cleanup for the inode struct in ext2fs (based on UFS) Date: Fri, 31 Dec 2010 08:05:23 -0800 (PST) Please close: this has been superceeded by PR 153584. From owner-freebsd-fs@FreeBSD.ORG Fri Dec 31 17:39:31 2010 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 D6E9C106564A for ; Fri, 31 Dec 2010 17:39:31 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6246E8FC23 for ; Fri, 31 Dec 2010 17:39:31 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PYiwr-000128-Q7 for freebsd-fs@freebsd.org; Fri, 31 Dec 2010 18:39:29 +0100 Received: from host-174-44-170-66.hln-mt.client.bresnan.net ([174.44.170.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 31 Dec 2010 18:39:29 +0100 Received: from dsamms by host-174-44-170-66.hln-mt.client.bresnan.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 31 Dec 2010 18:39:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: David Samms Date: Fri, 31 Dec 2010 10:39:09 -0700 Lines: 79 Message-ID: References: <4D1BCE34.4090601@nw-ds.com> <20101230085723.GA38391@tolstoy.tols.org> <8639pe55zj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: host-174-44-170-66.hln-mt.client.bresnan.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101228 Thunderbird/3.0.11 In-Reply-To: <8639pe55zj.fsf@gmail.com> Subject: Re: 8.2-RC1 and 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: Fri, 31 Dec 2010 17:39:32 -0000 On 12/31/10 08:14, Anonymous wrote: > David Samms writes: > > [...] >> The same test with ZFSv28 and ZFSv28 + tuning >> >> ZFSv28 >> ---------------------------------------------------------------------- >> dd if=/dev/zero of=big bs=1m count=6400 >> 6710886400 bytes transferred in 158.205268 secs (42418855 bytes/sec) >> >> OpenOffice 197sec >> MP3 skips >> XFCE4 popup menus took 5-15 seconds to appear >> >> >> ZFSv28 + tuning >> --vfs.zfs.txg.timeout="5" > > the tunable defaults to "5" in v28, see txg.c > > int zfs_txg_timeout = 5; /* max seconds worth of delta per txg */ > >> --vfs.zfs.txg.write_limit_override=268435456 > > No such tunable/sysctl. It was renamed to vfs.zfs.write_limit_override > in v28 (note ".txg." absence). > >> --kern.maxvnodes=250000 > >> ---------------------------------------------------------------------- >> dd if=/dev/zero of=big bs=1m count=6400 >> 6710886400 bytes transferred in 167.316444 secs (40108947 bytes/sec) >> >> OpenOffice 190sec >> No MP3 skips during "dd", but one skip while OpenOffice was starting >> XFCE4 popup menus took 2-13 seconds to appear Thank you for the correction. Please disregard my previous test results for ZFS+tuning. Below are the corrected results: ZFSv28 defaults + -- vfs.zfs.write_limit_override: 268435456 -- kern.maxvnodes=250000 ---------------------------------------------------------------------- dd if=/dev/zero of=big bs=1m count=6400 6710886400 bytes transferred in 254.771374 secs (26340818 bytes/sec) OpenOffice 82sec No Skips menus 0-1 sec ZFSv28 defaults + -- vfs.zfs.write_limit_override: 1073741824 -- kern.maxvnodes=250000 ---------------------------------------------------------------------- dd if=/dev/zero of=big bs=1m count=6400 6710886400 bytes transferred in 189.671025 secs (35381716 bytes/sec) OpenOffice 190sec No Skips menus 0-2 sec Setting vfs.zfs.write_limit_override: 268435456 significantly slows writes but make reads wonderful. Not ideal though. Setting vfs.zfs.write_limit_override: 1073741824 brings writes up to 87% of UFS+s and _dramatically_ improves GUI responsiveness. Very good setting for an old desktop machine. Being a ZFS novice, I would appreciate any links to tuning information. The default ZFS tuning do not seem good for a web-server or desktop which is fine, but guiding sysadmins to typical settings for their application would be helpful.