From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 00:26:07 2011 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 7A2531065670 for ; Sun, 27 Feb 2011 00:26:07 +0000 (UTC) (envelope-from vermaden@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id C95F38FC1A for ; Sun, 27 Feb 2011 00:26:06 +0000 (UTC) Received: (qmail 2088 invoked by uid 0); 27 Feb 2011 00:26:05 -0000 Received: from 85.89.187.172 by rms-eu005.v300.gmx.net with HTTP Content-Type: text/plain; charset="utf-8" Date: Sun, 27 Feb 2011 00:26:04 +0000 From: "Slawomir Wojtczak" Message-ID: <20110227002604.92530@gmx.com> MIME-Version: 1.0 To: freebsd-questions@freebsd.org X-Authenticated: #68675852 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: JK1ceVBjTiE+KX+IcGBw8UR9ZUVSRBet Cc: freebsd-fs@freebsd.org Subject: ROOT on ZFS with MBR partitions 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, 27 Feb 2011 00:26:07 -0000 Hi, I have tried these guides: http://wiki.freebsd.org/RootOnZFS/ZFSBootSlice http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition ... but none of them seems to work, after installation it hangs at boot like that: http://ompldr.org/vN2tscQ I am using these guides with 8.2-RELEASE amd64 version. I know that there is way to do this on GPT partitions, but I need MBR ones ... Any help appreciated, vermaden From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 03:00:20 2011 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 7EAD8106567A for ; Sun, 27 Feb 2011 03:00:20 +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 400368FC13 for ; Sun, 27 Feb 2011 03:00:20 +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 p1R30K4x026294 for ; Sun, 27 Feb 2011 03:00:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1R30KbE026293; Sun, 27 Feb 2011 03:00:20 GMT (envelope-from gnats) Date: Sun, 27 Feb 2011 03:00:20 GMT Message-Id: <201102270300.p1R30KbE026293@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Carl Cc: Subject: Re: kern/154228: [md] md getting stuck in wdrain state X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Carl List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2011 03:00:20 -0000 The following reply was made to PR kern/154228; it has been noted by GNATS. From: Carl To: bug-followup@FreeBSD.org, k0802647@telus.net Cc: Subject: Re: kern/154228: [md] md getting stuck in wdrain state Date: Sat, 26 Feb 2011 18:23:38 -0800 I applied the patch to the FreeBSD-8.1-RELEASE-amd64 system for which I'd filed the bug report. It solved the problem I reported for the scenario in question. Thanks. Carl / K0802647 From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 12:55:04 2011 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 692AE106566C for ; Sun, 27 Feb 2011 12:55:04 +0000 (UTC) (envelope-from tim.bishop@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 219248FC13 for ; Sun, 27 Feb 2011 12:55:03 +0000 (UTC) Received: by gxk7 with SMTP id 7so1417151gxk.13 for ; Sun, 27 Feb 2011 04:55:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:date:message-id:subject :from:to:content-type; bh=5s1WRRMofUmP8vkcR0wA49bPyYxARH0kKWea4hboh9M=; b=bD9eHs9sRrhWDAJSYPzzGFSZY1Zhptnumqe0CEYt0wBCnxddjA18drYzQTz1nF20F5 JuYN1JpdMCAX18nvX92gOAHCdcPa0iw/kiMbl0mHHwY9g/ip+ueLjDsG/TI7aHVzDdEu IipCDd2Zr/RMFOSVkOfqpUJNz9mym5Z8VAt0g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=vqqphp6ijRaAyPl4PBQOe+k3UlUPJjQqpb2yL/LqEVETCDB6eO1mzko64ImSHe5hia NW/cZKoJadmYXpjkjV+/P7e7/BpDeAowzdVORliM0iYWDjGMSnFLzKFfUzDuw5EGWLEx EvZ+kPKnXwQ7A3EXAFb2ReQFwulUjzgadynXc= MIME-Version: 1.0 Received: by 10.147.51.7 with SMTP id d7mr2739386yak.4.1298809937284; Sun, 27 Feb 2011 04:32:17 -0800 (PST) Received: by 10.147.136.20 with HTTP; Sun, 27 Feb 2011 04:32:17 -0800 (PST) Date: Sun, 27 Feb 2011 12:32:17 +0000 Message-ID: From: Tim Bishop To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: ZFS system unresponsive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tim@bishnet.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2011 12:55:04 -0000 Hi all, I have a ZFS system that has become unresponsive. It's running amd64 8-STABLE as of approximately 20 Dec. It has a UFS-based root file system and then a ZFS mirror for a handful of jails. It seems to get in to this state occasionally, but eventually can unblock itself. This may take hours though. top -HSj shows the following processes active: PID JID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 0 0 root -16 0 0K 1456K zio->i 0 28.9H 7.08% {zio_write_issue} 5 0 root -8 - 0K 60K zio->i 0 776:59 0.29% {txg_thread_enter} A procstat on those processes shows: 0 100068 kernel zio_write_issue mi_switch sleepq_wait _cv_wait zio_wait dmu_buf_hold_array_by_dnode dmu_read space_map_load metaslab_activate metaslab_alloc zio_dva_allocate zio_execute taskq_run_safe taskqueue_run_locked taskqueue_thread_loop fork_exit fork_trampoline 5 100094 zfskern txg_thread_enter mi_switch sleepq_wait _cv_wait txg_thread_wait txg_quiesce_thread fork_exit fork_trampoline 5 100095 zfskern txg_thread_enter mi_switch sleepq_wait _cv_wait zio_wait dsl_pool_sync spa_sync txg_sync_thread fork_exit fork_trampoline (I have the full procstat -k output for those PIDs if needed) Other processes, such as my hourly zfs snapshots appear to be wedged: root 7407 0.0 0.0 14672 1352 ?? D 10:00AM 0:00.46 /sbin/zfs snapshot -r pool0@2011-02-27_10.00.01--1d root 10184 0.0 0.0 14672 1444 ?? D 11:00AM 0:00.36 /sbin/zfs snapshot -r pool0@2011-02-27_11.00.00--1d root 12938 0.0 0.0 14672 1516 ?? D 12:00PM 0:00.11 /sbin/zfs snapshot -r pool0@2011-02-27_12.00.01--1d PID TID COMM TDNAME KSTACK 7407 100563 zfs - mi_switch sleepq_wait _cv_wait txg_wait_synced dsl_sync_task_group_wait dmu_objset_snapshot zfs_ioc_snapshot zfsdev_ioctl devfs_ioctl_f kern_ioctl ioctl syscallenter syscall Xfast_syscall 10184 100707 zfs - mi_switch sleepq_wait _cv_wait txg_wait_synced dsl_sync_task_group_wait dmu_objset_snapshot zfs_ioc_snapshot zfsdev_ioctl devfs_ioctl_f kern_ioctl ioctl syscallenter syscall Xfast_syscall 12938 100159 zfs - mi_switch sleepq_wait _cv_wait txg_wait_synced dsl_sync_task_group_wait dmu_objset_snapshot zfs_ioc_snapshot zfsdev_ioctl devfs_ioctl_f kern_ioctl ioctl syscallenter syscall Xfast_syscall zfs-stats output as follows: ------------------------------------------------------------------------ ZFS Subsystem Report Sun Feb 27 12:20:20 2011 ------------------------------------------------------------------------ System Information: Kernel Version: 801501 (osreldate) Hardware Platform: amd64 Processor Architecture: amd64 FreeBSD 8.2-PRERELEASE #3: Mon Dec 20 20:54:55 GMT 2010 tdb 12:23pm up 68 days, 14:07, 2 users, load averages: 0.35, 0.39, 0.35 ------------------------------------------------------------------------ System Memory Statistics: Physical Memory: 3061.63M Kernel Memory: 1077.46M DATA: 99.12% 1067.93M TEXT: 0.88% 9.53M ------------------------------------------------------------------------ ZFS pool information: Storage pool Version (spa): 15 Filesystem Version (zpl): 4 ------------------------------------------------------------------------ ARC Misc: Deleted: 148418216 Recycle Misses: 51095797 Mutex Misses: 370820 Evict Skips: 370820 ARC Size: Current Size (arcsize): 55.86% 1087.64M Target Size (Adaptive, c): 56.50% 1100.22M Min Size (Hard Limit, c_min): 12.50% 243.40M Max Size (High Water, c_max): ~8:1 1947.20M ARC Size Breakdown: Recently Used Cache Size (p): 6.25% 68.77M Freq. Used Cache Size (c-p): 93.75% 1031.45M ARC Hash Breakdown: Elements Max: 398079 Elements Current: 38.65% 153870 Collisions: 230805591 Chain Max: 34 Chains: 24344 ARC Eviction Statistics: Evicts Total: 4560897494528 Evicts Eligible for L2: 99.99% 4560573588992 Evicts Ineligible for L2: 0.01% 323905536 Evicts Cached to L2: 0 ARC Efficiency: Cache Access Total: 1761824967 Cache Hit Ratio: 84.82% 1494437389 Cache Miss Ratio: 15.18% 267387578 Actual Hit Ratio: 84.82% 1494411236 Data Demand Efficiency: 83.35% CACHE HITS BY CACHE LIST: Most Recently Used (mru): 7.86% 117410213 Most Frequently Used (mfu): 92.14% 1377001023 MRU Ghost (mru_ghost): 0.63% 9445180 MFU Ghost (mfu_ghost): 7.99% 119349696 CACHE HITS BY DATA TYPE: Demand Data: 35.75% 534254771 Prefetch Data: 0.00% 0 Demand Metadata: 64.25% 960153880 Prefetch Metadata: 0.00% 28738 CACHE MISSES BY DATA TYPE: Demand Data: 39.91% 106712177 Prefetch Data: 0.00% 0 Demand Metadata: 60.01% 160446249 Prefetch Metadata: 0.09% 229152 ------------------------------------------------------------------------ VDEV Cache Summary: Access Total: 155663083 Hits Ratio: 70.91% 110387854 Miss Ratio: 29.09% 45275229 Delegations: 91183 ------------------------------------------------------------------------ ZFS Tunable (sysctl): kern.maxusers=384 vfs.zfs.l2c_only_size=0 vfs.zfs.mfu_ghost_data_lsize=23343104 vfs.zfs.mfu_ghost_metadata_lsize=302204928 vfs.zfs.mfu_ghost_size=325548032 vfs.zfs.mfu_data_lsize=524091904 vfs.zfs.mfu_metadata_lsize=52224 vfs.zfs.mfu_size=533595136 vfs.zfs.mru_ghost_data_lsize=30208 vfs.zfs.mru_ghost_metadata_lsize=727952896 vfs.zfs.mru_ghost_size=727983104 vfs.zfs.mru_data_lsize=100169216 vfs.zfs.mru_metadata_lsize=0 vfs.zfs.mru_size=339522048 vfs.zfs.anon_data_lsize=0 vfs.zfs.anon_metadata_lsize=0 vfs.zfs.anon_size=10959360 vfs.zfs.l2arc_norw=1 vfs.zfs.l2arc_feed_again=1 vfs.zfs.l2arc_noprefetch=0 vfs.zfs.l2arc_feed_min_ms=200 vfs.zfs.l2arc_feed_secs=1 vfs.zfs.l2arc_headroom=2 vfs.zfs.l2arc_write_boost=8388608 vfs.zfs.l2arc_write_max=8388608 vfs.zfs.arc_meta_limit=510447616 vfs.zfs.arc_meta_used=513363680 vfs.zfs.mdcomp_disable=0 vfs.zfs.arc_min=255223808 vfs.zfs.arc_max=2041790464 vfs.zfs.zfetch.array_rd_sz=1048576 vfs.zfs.zfetch.block_cap=256 vfs.zfs.zfetch.min_sec_reap=2 vfs.zfs.zfetch.max_streams=8 vfs.zfs.prefetch_disable=1 vfs.zfs.check_hostid=1 vfs.zfs.recover=0 vfs.zfs.txg.write_limit_override=0 vfs.zfs.txg.synctime=5 vfs.zfs.txg.timeout=30 vfs.zfs.scrub_limit=10 vfs.zfs.vdev.cache.bshift=16 vfs.zfs.vdev.cache.size=10485760 vfs.zfs.vdev.cache.max=16384 vfs.zfs.vdev.aggregation_limit=131072 vfs.zfs.vdev.ramp_rate=2 vfs.zfs.vdev.time_shift=6 vfs.zfs.vdev.min_pending=4 vfs.zfs.vdev.max_pending=10 vfs.zfs.cache_flush_disable=0 vfs.zfs.zil_disable=0 vfs.zfs.zio.use_uma=0 vfs.zfs.version.zpl=4 vfs.zfs.version.spa=15 vfs.zfs.version.dmu_backup_stream=1 vfs.zfs.version.dmu_backup_header=2 vfs.zfs.version.acl=1 vfs.zfs.debug=0 vfs.zfs.super_owner=0 vm.kmem_size=3115532288 vm.kmem_size_scale=1 vm.kmem_size_min=0 vm.kmem_size_max=329853485875 ------------------------------------------------------------------------ I hope somebody can give me some pointers on where to go with this. I'm just about to reboot (when it unwedges) and upgrade to the latest 8-STABLE to see if that helps. Thanks, Tim. From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 18:53:35 2011 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 3E5D4106566B for ; Sun, 27 Feb 2011 18:53:35 +0000 (UTC) (envelope-from royce.williams@gmail.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 0A85D8FC16 for ; Sun, 27 Feb 2011 18:53:34 +0000 (UTC) Received: by iwn33 with SMTP id 33so2839450iwn.13 for ; Sun, 27 Feb 2011 10:53:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=JxwaHhmqF8/T4ZCzS7moix8yIWb9s2kL74mJ9XKYok8=; b=PeAxdiAhFoQpjM1SO+TScMHPR/I14PaBfNrjLEMFxDPaMc2GOaKGTTkFQN/uXwGe8G PqXYIhiAKG9ce2LZ4TFvyrxC4wAxHdY15yAEM1wP0IOweIITUhvVzbXqFUGeDe8KjpPQ UxVXubnWfCUEJBpdStNiPhlg+Ch6+pQoc70fc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=AkB3SHr0SVHUiyMiFLO+PUA7LGFnOV0nHHA+w1qkQ0sOvnqFbIxH9lTSUw1A8THU8x 2gW9oi8jNIORoHml+ZBUG7a6AgVaaH9J/gXJWSOQsLZana0nO4tUzZZJ3UP2Pj1+q82c uAOB63Swol36dszZtIjgxAJ5hZQ4TeI3+KjnU= Received: by 10.231.12.131 with SMTP id x3mr4777810ibx.76.1298831458366; Sun, 27 Feb 2011 10:30:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.183.139 with HTTP; Sun, 27 Feb 2011 10:30:38 -0800 (PST) From: Royce Williams Date: Sun, 27 Feb 2011 09:30:38 -0900 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: slow "zfs destroy snapshot" with predictable time pattern 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, 27 Feb 2011 18:53:35 -0000 I thought that 'zfs snapshot destroy' should be fast (on the order of a few seconds), but mine are taking a predictably long time on a pretty modest filesystem (details below). I discovered this when a typo caused many more snapshots than I intended (every minute!); I had about 12,000 of them before I noticed. Destroying the first snapshot took about 39 wallclock seconds on an otherwise idle system. A few more destroys took almost exactly the same amount of time. I know little about ZFS under the hood, but I wanted to investigate a little bit. I scripted a loop of 'time zfs destroy snapshot' and let it run overnight. Each destroy was consistently taking 37-40 seconds, but then after hundreds of deletions in that time range, I saw a jagged spike, followed by a consistent drop that has stayed in the 23-25s range: [hours of 38-39s destroys snipped] real 0m38.205s real 0m38.455s real 0m38.580s real 0m37.414s real 0m35.330s <-- small drop here real 0m35.347s real 0m35.380s real 0m35.355s real 0m35.255s real 0m35.514s real 0m35.422s real 0m35.464s real 0m46.121s <-- small spike here real 0m44.630s real 0m46.021s real 1m19.443s <-- big spike here real 0m40.896s real 0m22.848s <-- drop into the 20s range real 0m29.039s real 0m29.831s real 0m26.348s real 0m22.623s real 0m29.314s real 0m29.589s real 0m26.573s real 0m22.773s [hours of of 23-25s destroys snipped] I know very little about ZFS under the hood, but this model might fit the facts: * Normally, 'zfs destroy snapshot' is fast (on the order of a few seconds); * 'zfs destroy snapshot' has to briefly analyze all snapshots prior to destruction; * A particular 'problem' snapshot can slow that full analysis by a consistent amount of time; * Destroying that 'problem' snapshot drops the analysis time by that amount. If my model is correct, I'm going to see one or more spikes, followed by corresponding drops, until the destroys return to a reasonable rate. This guy had a problem that might also fit that model -- that particular snapshots can be very slow, and removing them removes the time delay. That thread notes that it was due to a low-memory condition, and OpenSolaris bug 6542681 was filed for it. I do not think that my problem is because of low memory. http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg07647.html I have stopped the destroys in case the remaining 'problem' snapshot is useful. The system is 8.1-SECURITY, amd64, 4GB RAM, no sysctl or loader tweaks, ZFS v3, zpool v14, single 58GB ZFS pool. # zfs list NAME USED AVAIL REFER MOUNTPOINT atoz-backup 15.4G 58.0G 25.5K /atoz-backup atoz-backup/usr 15.3G 58.0G 14.8G /atoz-backup/usr # df -ki | egrep 'atoz|Filesystem' Filesystem 1024-blocks Used Avail Capacity iused ifree %iused Mounted on atoz-backup 60789979 25 60789953 0% 6 121579907 0% /atoz-backup atoz-backup/usr 76281655 15491701 60789953 20% 714124 121579907 1% /atoz-backup/usr Royce From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 20:13:16 2011 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 69B4B106566B for ; Sun, 27 Feb 2011 20:13:16 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id C21828FC08 for ; Sun, 27 Feb 2011 20:13:15 +0000 (UTC) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.4/8.14.4) with ESMTP id p1RJvEuu034603; Sun, 27 Feb 2011 13:57:16 -0600 (CST) (envelope-from james-freebsd-fs2@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-fs2@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=PY7VHWf4zM8ussgqcA51qEIV9Vml6H/eRFOSfiqDPB2VTZYS9ni56IVy6Pj8tfhKb 3w/lFkklXSj6om0SimpFRG6z+VFRlWzrsOIs1YLcyAwQ315DPUtGpkut1TgJrO/QNbL QIDiHcvq4ggDjrJY5pvemd4dtyo6HC3nUoyY88M= Message-ID: <4D6AAC9A.4000602@jrv.org> Date: Sun, 27 Feb 2011 13:57:14 -0600 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Emil Smolenski References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: [ZFS] Booting from zpool created on 4k-sector drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2011 20:13:16 -0000 Emil Smolenski wrote: > Hello, > > There is a hack to force zpool creation with minimum sector size equal > to 4k: > > # gnop create -S 4096 ${DEV0} > # zpool create tank ${DEV0}.nop > # zpool export tank > # gnop destroy ${DEV0}.nop > # zpool import tank > > This change is permanent. The only possibility to change the value of > ashift is: zpool destroy/create and restoring pool from backup. Is ashift a property of the pool or a property of the device? I'm wonder about the disk replacement scenario, where the replacement disk cannot be smaller than the disk it replaces. From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 20:30:34 2011 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 942CC1065670 for ; Sun, 27 Feb 2011 20:30:34 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 166F98FC13 for ; Sun, 27 Feb 2011 20:30:33 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 0620045C9C; Sun, 27 Feb 2011 21:30:31 +0100 (CET) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 47DC845684; Sun, 27 Feb 2011 21:30:23 +0100 (CET) Date: Sun, 27 Feb 2011 21:29:57 +0100 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20110227202957.GD1992@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oj4kGyHlBMXGt3Le" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-current@FreeBSD.org Subject: HEADS UP: ZFSv28 is in! 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, 27 Feb 2011 20:30:34 -0000 --oj4kGyHlBMXGt3Le Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. I just committed ZFSv28 to HEAD. New major features: - Data deduplication. - Triple parity RAIDZ (RAIDZ3). - zfs diff. - zpool split. - Snapshot holds. - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. PS. If you like my work, you help me to promote yomoli.com:) http://yomoli.com http://www.facebook.com/pages/Yomolicom/178311095544155 --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --oj4kGyHlBMXGt3Le Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk1qtEUACgkQForvXbEpPzR2rgCcCIqDfc1NGwMPN2ap2tQMCVmn uhIAn0S6O68p2vYowR5v1b02nDBpY5pr =TmvH -----END PGP SIGNATURE----- --oj4kGyHlBMXGt3Le-- From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 21:12:51 2011 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 09E0F106564A for ; Sun, 27 Feb 2011 21:12:51 +0000 (UTC) (envelope-from universite@ukr.net) Received: from otrada.od.ua (universite-1-pt.tunnel.tserv24.sto1.ipv6.he.net [IPv6:2001:470:27:140::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6C4B38FC12 for ; Sun, 27 Feb 2011 21:12:50 +0000 (UTC) Received: from [10.0.0.10] (phenom.otrada.od.ua [10.0.0.10]) (authenticated bits=0) by otrada.od.ua (8.14.4/8.14.4) with ESMTP id p1RL8wSh085159; Sun, 27 Feb 2011 23:08:58 +0200 (EET) (envelope-from universite@ukr.net) X-Authentication-Warning: otrada.od.ua: Host phenom.otrada.od.ua [10.0.0.10] claimed to be [10.0.0.10] Message-ID: <4D6ABD53.5090709@ukr.net> Date: Sun, 27 Feb 2011 23:08:35 +0200 From: "Vladislav V. Prodan" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: tim@bishnet.net References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,AWL autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mary-teresa.otrada.od.ua X-Virus-Scanned: clamav-milter 0.97 at mary-teresa.otrada.od.ua X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: ZFS system unresponsive 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, 27 Feb 2011 21:12:51 -0000 27.02.2011 14:32, Tim Bishop wrote: > I have a ZFS system that has become unresponsive. It's running amd64 > 8-STABLE as of approximately 20 Dec. It has a UFS-based root file > system and then a ZFS mirror for a handful of jails. > > It seems to get in to this state occasionally, but eventually can > unblock itself. This may take hours though. In such cases, only helps the reset button. I already wrote about this bug - kern/153351 I have one machine updated to 8.2-PRERELEASE # 0: Fri Feb 18 18:27:12 EET 2011 bug does not pop up yet ... -- Vladislav V. Prodan VVP24-UANIC +38[067]4584408 +38[099]4060508 vlad11@jabber.ru From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 23:00:25 2011 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 CD1341065670 for ; Sun, 27 Feb 2011 23:00:25 +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 8EC788FC17 for ; Sun, 27 Feb 2011 23:00:25 +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 p1RN0Pj4086566 for ; Sun, 27 Feb 2011 23:00:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1RN0P1A086549; Sun, 27 Feb 2011 23:00:25 GMT (envelope-from gnats) Resent-Date: Sun, 27 Feb 2011 23:00:25 GMT Resent-Message-Id: <201102272300.p1RN0P1A086549@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-fs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Anonymous Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22E7E106564A for ; Sun, 27 Feb 2011 22:55:16 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id ACCC48FC12 for ; Sun, 27 Feb 2011 22:55:15 +0000 (UTC) Received: by wwb31 with SMTP id 31so4323849wwb.31 for ; Sun, 27 Feb 2011 14:55:14 -0800 (PST) Received: by 10.227.23.200 with SMTP id s8mr1113040wbb.196.1298847314026; Sun, 27 Feb 2011 14:55:14 -0800 (PST) Received: from localhost (tor-exit-router36-readme.formlessnetworking.net [199.48.147.36]) by mx.google.com with ESMTPS id o6sm2761295wbo.9.2011.02.27.14.55.11 (version=SSLv3 cipher=OTHER); Sun, 27 Feb 2011 14:55:13 -0800 (PST) Message-Id: <86ipw5xf3r.fsf@gmail.com> Date: Mon, 28 Feb 2011 01:55:04 +0300 From: Anonymous To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: bin/155104: [zfs][patch] use /dev prefix by default when importing 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, 27 Feb 2011 23:00:25 -0000 >Number: 155104 >Category: bin >Synopsis: [zfs][patch] use /dev prefix by default when importing >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-fs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 27 23:00:24 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Anonymous >Release: FreeBSD 9.0-CURRENT amd64 >Organization: >Environment: >Description: Don't use Solaris prefix /dev/dsk when trying zpool_{find,search}_import() without arguments. cf. http://docs.freebsd.org/cgi/mid.cgi?86lj1s3pv0.fsf >How-To-Repeat: $ zdb -e tank >Fix: --- a.diff begins here --- Index: cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c =================================================================== --- cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c (revision 219090) +++ cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c (working copy) @@ -1129,7 +1129,11 @@ zpool_find_import_impl(libzfs_handle_t *hdl, impor char *end, **dir = iarg->path; size_t pathleft; nvlist_t *ret = NULL; +#ifdef sun static char *default_dir = "/dev/dsk"; +#else + static char *default_dir = "/dev"; +#endif pool_list_t pools = { 0 }; pool_entry_t *pe, *penext; vdev_entry_t *ve, *venext; --- a.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 23:30:11 2011 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 5A1A2106566B for ; Sun, 27 Feb 2011 23:30:06 +0000 (UTC) (envelope-from lattera@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id CF6E88FC0A for ; Sun, 27 Feb 2011 23:30:05 +0000 (UTC) Received: by wwb31 with SMTP id 31so4343253wwb.31 for ; Sun, 27 Feb 2011 15:30:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=lX+HUic8hVypuzbhQqTPsXXi8PGqBTx2p+9ypjN9qKE=; b=K6EMWJ/rH8CoL3opE+JVO06ojDp006NT/UZb826+jLTricwWhLIzgDhz25FEsHfpnc C6P58aCXS5N+WKJj5IZ+CTEIL2WWUrSjBQJxlKq/Y+B8DTbBIHtDmYdlP/BgiEuBzvCN j35wASKjAaY48U6J61PlxDcDfmr+OCFyZCtrI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GQolK0HratR1hYw+bXdV3cej9lKPmDtEg83orC2dGMEEuYreab7h5rgk3sh+ZZTchW j8qwth751wm9CwRuTxmDsAaETTslvvipWH5f4JA16UtnsHSfUkJaA1/kkkyHRWY+75ao ddM7+QtG/NfXu5xmvtqCrCwzIplo2JiD1+opo= MIME-Version: 1.0 Received: by 10.227.9.211 with SMTP id m19mr566940wbm.132.1298847782890; Sun, 27 Feb 2011 15:03:02 -0800 (PST) Received: by 10.227.127.68 with HTTP; Sun, 27 Feb 2011 15:03:01 -0800 (PST) Received: by 10.227.127.68 with HTTP; Sun, 27 Feb 2011 15:03:01 -0800 (PST) In-Reply-To: <20110227202957.GD1992@garage.freebsd.pl> References: <20110227202957.GD1992@garage.freebsd.pl> Date: Sun, 27 Feb 2011 16:03:01 -0700 Message-ID: From: Shawn Webb To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: HEADS UP: ZFSv28 is in! 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, 27 Feb 2011 23:30:11 -0000 I'm so excited for your work. Thanks so much for bringing zpool v28 to FreeBSD. Will v28 come to 8-stable? Thanks, Shawn On Feb 27, 2011 1:56 PM, "Pawel Jakub Dawidek" wrote: > Hi. > > I just committed ZFSv28 to HEAD. > > New major features: > > - Data deduplication. > - Triple parity RAIDZ (RAIDZ3). > - zfs diff. > - zpool split. > - Snapshot holds. > - zpool import -F. Allows to rewind corrupted pool to earlier > transaction group. > - Possibility to import pool in read-only mode. > > PS. If you like my work, you help me to promote yomoli.com:) > > http://yomoli.com > http://www.facebook.com/pages/Yomolicom/178311095544155 > > -- > Pawel Jakub Dawidek http://www.wheelsystems.com > FreeBSD committer http://www.FreeBSD.org > Am I Evil? Yes, I Am! http://yomoli.com From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 23:30:48 2011 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 3818E106566C; Sun, 27 Feb 2011 23:30:48 +0000 (UTC) (envelope-from cforgeron@acsi.ca) Received: from mta04.eastlink.ca (mta04.eastlink.ca [24.224.136.10]) by mx1.freebsd.org (Postfix) with ESMTP id F050A8FC16; Sun, 27 Feb 2011 23:30:47 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from ip05.eastlink.ca ([unknown] [24.222.39.68]) by mta04.eastlink.ca (Sun Java(tm) System Messaging Server 7.3-11.01 64bit (built Sep 1 2009)) with ESMTP id <0LHA00CR6UNA2GJ0@mta04.eastlink.ca>; Sun, 27 Feb 2011 19:30:46 -0400 (AST) X-CMAE-Score: 0 X-CMAE-Analysis: v=1.1 cv=mORQtGzMSGJSBwuMSvVfB0MKjPGmXehAuj88Uvu04o4= c=1 sm=1 a=LcMMunZ7XbEA:10 a=kj9zAlcOel0A:10 a=6I5d2MoRAAAA:8 a=3GfhBCVjAAAA:8 a=3j4BkbkPAAAA:8 a=T-mGKmPgAAAA:8 a=1Ta-wnCemMmeNz1v2KIA:9 a=tj04XEdOMHQgi8OafbUA:7 a=LN401u0E5gCyUU3NdRtgLm_gEBkA:4 a=CjuIK1q_8ugA:10 a=ZLR890v9WDgA:10 a=SV7veod9ZcQA:10 a=/bLbuBD0lrv91xL1PDQKaA==:117 Received: from blk-222-10-85.eastlink.ca (HELO server7.acsi.ca) ([24.222.10.85]) by ip05.eastlink.ca with ESMTP; Sun, 27 Feb 2011 19:30:46 -0400 Received: from server7.acsi.ca ([192.168.9.7]) by server7.acsi.ca ([192.168.9.7]) with mapi; Sun, 27 Feb 2011 19:30:33 -0400 From: Chris Forgeron To: Pawel Jakub Dawidek , "freebsd-fs@FreeBSD.org" Date: Sun, 27 Feb 2011 19:30:32 -0400 Thread-topic: HEADS UP: ZFSv28 is in! Thread-index: AcvWvTqNJlzVqRnzQWC/iBBVnTKDhgAEb4RA Message-id: References: <20110227202957.GD1992@garage.freebsd.pl> In-reply-to: <20110227202957.GD1992@garage.freebsd.pl> Accept-Language: en-US Content-language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Cc: "freebsd-current@FreeBSD.org" Subject: RE: HEADS UP: ZFSv28 is in! 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, 27 Feb 2011 23:30:48 -0000 Yay! Thanks for all of your work on ZFS. I was just about to inquire about when this was going to happen. I've been having great success with v28 in the Dec 12 2010 version, other than my minor complaints about imports and speed. Concerning speed, I've been running further speed tests this weekend with FreeBSD trying to isolate what effect NFS has on my tests. Earlier I found a Solaris 11 box being faster than a FreeBSD 9 box for the same hardware. I notice giant-lock logic in the NFS server code, and while it shouldn't be in play for a MP safe fs like ZFS, I'm not sure. I have a few NFS custom tests, including forcing async in the code even when VMWare opens it as O_SYNC. Judging by the Solaris speed difference, I think they must be silently doing something similar to get the speed they do on ZFS with a ZIL enabled. I also need to look into how the Intel X520 card is setup in Solaris compared to FreeBSD, as it may be my speed limiter. This will make further testing much easier now that I no longer need to juggle patches. Thanks again. -----Original Message----- From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] On Behalf Of Pawel Jakub Dawidek Sent: Sunday, February 27, 2011 4:30 PM To: freebsd-fs@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: HEADS UP: ZFSv28 is in! Hi. I just committed ZFSv28 to HEAD. New major features: - Data deduplication. - Triple parity RAIDZ (RAIDZ3). - zfs diff. - zpool split. - Snapshot holds. - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. PS. If you like my work, you help me to promote yomoli.com:) http://yomoli.com http://www.facebook.com/pages/Yomolicom/178311095544155 -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 00:05:11 2011 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 3C3531065673 for ; Mon, 28 Feb 2011 00:05:11 +0000 (UTC) (envelope-from royce.williams@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 03F658FC1C for ; Mon, 28 Feb 2011 00:05:10 +0000 (UTC) Received: by iyj12 with SMTP id 12so2786275iyj.13 for ; Sun, 27 Feb 2011 16:05:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; bh=IUplPnyBe5ghF5oV0yD/TELy/dq3sLIJOlROukjcrfk=; b=Gn6Cocd2taZUfMux4QXfNdGo1JBuuOSaiI3eWA/JAqdCC1SgCCuW9a6O7kMVAc1D9U AA5HBOtMgMxNYF0pc3Nfo77MtDnGO7QbeWrOKMyL5fxnNN72H8X52oUfjZJWnrdhMx5D r8DucGekxpqOaRjZ/U2poetyx3MYHnrUGbKI8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=hWtQzPNxY4HBv9U4D7U9FP2Zc3WvgDHIkYf/Qah2wXBvJVnZgvCN7C4HQOUgKQAXPi 41qfyGRIKNTKl87LsXtjrFhlpwIJjh+9RC29RB2BxrUjrh3SJXKjovM+vUrPQfkekF22 CvDdJ1aixgNQkhbA3Dm39NomOnlNP7NHDW+nI= Received: by 10.42.224.136 with SMTP id io8mr4167289icb.202.1298851510089; Sun, 27 Feb 2011 16:05:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.183.139 with HTTP; Sun, 27 Feb 2011 16:04:50 -0800 (PST) In-Reply-To: References: From: Royce Williams Date: Sun, 27 Feb 2011 15:04:50 -0900 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: slow "zfs destroy snapshot" with predictable time pattern 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, 28 Feb 2011 00:05:11 -0000 On Sun, Feb 27, 2011 at 9:30 AM, Royce Williams wrote: > I thought that 'zfs snapshot destroy' should be fast (on the order of > a few seconds), but mine are taking a predictably long time on a > pretty modest filesystem (details below). > > I discovered this when a typo caused many more snapshots than I > intended (every minute!); I had about 12,000 of them before I noticed. > =A0Destroying the first snapshot took about 39 wallclock seconds on an > otherwise idle system. =A0A few more destroys took almost exactly the > same amount of time. > > I know little about ZFS under the hood, but I wanted to investigate a > little bit. I scripted a loop of 'time zfs destroy snapshot' and let > it run overnight. =A0Each destroy was consistently taking 37-40 seconds, > but then after hundreds of deletions in that time range, I saw a > jagged spike, followed by a consistent drop that has stayed in the > 23-25s range: > > [hours of 38-39s destroys snipped] > > real =A0 =A00m38.205s > real =A0 =A00m38.455s > real =A0 =A00m38.580s > real =A0 =A00m37.414s > real =A0 =A00m35.330s <-- small drop here > real =A0 =A00m35.347s > real =A0 =A00m35.380s > real =A0 =A00m35.355s > real =A0 =A00m35.255s > real =A0 =A00m35.514s > real =A0 =A00m35.422s > real =A0 =A00m35.464s > real =A0 =A00m46.121s =A0 <-- small spike here > real =A0 =A00m44.630s > real =A0 =A00m46.021s > real =A0 =A01m19.443s =A0 <-- big spike here > real =A0 =A00m40.896s > real =A0 =A00m22.848s =A0<-- drop into the 20s range > real =A0 =A00m29.039s > real =A0 =A00m29.831s > real =A0 =A00m26.348s > real =A0 =A00m22.623s > real =A0 =A00m29.314s > real =A0 =A00m29.589s > real =A0 =A00m26.573s > real =A0 =A00m22.773s > > [hours of of 23-25s destroys snipped] > > I know very little about ZFS under the hood, but this model might fit the= facts: > > * Normally, 'zfs destroy snapshot' is fast (on the order of a few seconds= ); > > * 'zfs destroy snapshot' has to briefly analyze all snapshots prior to > destruction; > > * A particular 'problem' snapshot can slow that full analysis by a > consistent amount of time; > > * Destroying that 'problem' snapshot drops the analysis time by that amou= nt. > > > If my model is correct, I'm going to see one or more spikes, followed > by corresponding drops, until the destroys return to a reasonable > rate. > > This guy had a problem that might also fit that model -- that > particular snapshots can be very slow, and removing them removes the > time delay. That thread notes that it was due to a low-memory > condition, and OpenSolaris bug 6542681 was filed for it. =A0I do not > think that my problem is because of low memory. > > =A0 =A0http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg07647.h= tml > > > I have stopped the destroys in case the remaining 'problem' snapshot is u= seful. > > The system is 8.1-SECURITY, amd64, 4GB RAM, no sysctl or loader > tweaks, ZFS v3, zpool v14, single 58GB ZFS pool. > > # zfs list > NAME =A0 =A0 =A0 =A0 =A0 =A0 =A0USED =A0AVAIL =A0REFER =A0MOUNTPOINT > atoz-backup =A0 =A0 =A015.4G =A058.0G =A025.5K =A0/atoz-backup > atoz-backup/usr =A015.3G =A058.0G =A014.8G =A0/atoz-backup/usr > > # df -ki | egrep 'atoz|Filesystem' > Filesystem =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 10= 24-blocks =A0 =A0 Used > Avail Capacity iused =A0 =A0 ifree %iused =A0Mounted on > atoz-backup =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 60789979 =A0 =A0 =A0 25 > 60789953 =A0 =A0 0% =A0 =A0 =A0 6 121579907 =A0 =A00% =A0 /atoz-backup > atoz-backup/usr =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 7= 6281655 15491701 > 60789953 =A0 =A020% =A0714124 121579907 =A0 =A01% =A0 /atoz-backup/usr I left this message open-ended. I also left out the hardware info. What I meant to get at was: * Is ~35 seconds roughly normal for a "zfs destroy snapshot" on a filesystem with 723K files, single disk, under no other I/O or CPU load, with an Intel ICH9 SATA300 talking to a Seagate ST3160812AS (SATA 3)? Googling seems to indicate that it's not, even if I had 12,000 snapshots. * If this speed is not normal, does this smell like a bug? If so, I can help recreate or test, maybe on 8.2 or 9-CURRENT. * If this speed is normal, what search terms would have yielded that fact? (slow OR speed OR problem OR performance) plus "zfs destroy snapshot" didn't yield much that applied. * Is my model valid? I reasoned that if a snapshot is a separate set of references to all files in the filesystem, and the filesystem hasn't changed much over time, then destroying each snapshot should take a relatively constant amount of time. Even if my time expectation was wrong (that it would be quite a bit shorter, even for 723,000 files), I would not expect the destroy time to drop by 50% in the middle of the destroy series ... so I think that I'm missing something. * If my model isn't valid, what is a better model? For example, I had gotten down to just over 10,000 snapshots when I stopped the series of destroys; could there be a snapshot count threshold, under which each destroy now takes less time, in stair-step fashion? In other words: I'm trying to understand what I'm seeing. :-) Also, sorry for the bad subject line - "zfs destroy snapshot" is obviously the correct command; I've updated the subject line. Royce From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 04:09:13 2011 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 3CD23106566B; Mon, 28 Feb 2011 04:09:13 +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 1399A8FC12; Mon, 28 Feb 2011 04:09:13 +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 p1S49CL0022999; Mon, 28 Feb 2011 04:09:12 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1S49CUo022995; Mon, 28 Feb 2011 04:09:12 GMT (envelope-from linimon) Date: Mon, 28 Feb 2011 04:09:12 GMT Message-Id: <201102280409.p1S49CUo022995@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-usb@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154828: [msdosfs] Unable to create directories on external USB HDD with large msdosfs (g_vfs_done():da0s1[WRITE(offset=- ... , length=16384)]error = 5) 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, 28 Feb 2011 04:09:13 -0000 Old Synopsis: Unable to create directories on external USB HDD with large msdosfs (g_vfs_done():da0s1[WRITE(offset=- ... , length=16384)]error = 5) New Synopsis: [msdosfs] Unable to create directories on external USB HDD with large msdosfs (g_vfs_done():da0s1[WRITE(offset=- ... , length=16384)]error = 5) Responsible-Changed-From-To: freebsd-usb->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Feb 28 04:07:34 UTC 2011 Responsible-Changed-Why: hselasky thinks this is unrelated to usb. http://www.freebsd.org/cgi/query-pr.cgi?pr=154828 From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 08:48:12 2011 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 E9A65106566C; Mon, 28 Feb 2011 08:48:12 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 948908FC18; Mon, 28 Feb 2011 08:48:12 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 10D1C45EA7; Mon, 28 Feb 2011 09:48:11 +0100 (CET) Received: from localhost (58.wheelsystems.com [83.12.187.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 00C4045C9F; Mon, 28 Feb 2011 09:48:04 +0100 (CET) Date: Mon, 28 Feb 2011 09:47:44 +0100 From: Pawel Jakub Dawidek To: Shawn Webb Message-ID: <20110228084744.GB1819@garage.freebsd.pl> References: <20110227202957.GD1992@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cmJC7u66zC7hs+87" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-3.9 required=4.5 tests=ALL_TRUSTED,BAYES_00, RCVD_IN_SORBS_DUL autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: HEADS UP: ZFSv28 is in! 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, 28 Feb 2011 08:48:13 -0000 --cmJC7u66zC7hs+87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 27, 2011 at 04:03:01PM -0700, Shawn Webb wrote: > I'm so excited for your work. Thanks so much for bringing zpool v28 to > FreeBSD. Will v28 come to 8-stable? Yes, hopefully in 1-2 month(s). --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --cmJC7u66zC7hs+87 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk1rYTAACgkQForvXbEpPzTs0QCgmWmAJ9UwC/bm03lNA89VAdtD naAAnA4VEEvLIWJHkKDRT+J0wsegBQyk =tFmk -----END PGP SIGNATURE----- --cmJC7u66zC7hs+87-- From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 10:37:29 2011 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 60DA2106566C; Mon, 28 Feb 2011 10:37:29 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id C00D68FC0C; Mon, 28 Feb 2011 10:37:28 +0000 (UTC) Received: by wwb31 with SMTP id 31so4747569wwb.31 for ; Mon, 28 Feb 2011 02:37:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=86tSbK3rMOjNgat5ZXpC8IZnBZMw4ssDE9jBruI2e1A=; b=u+qqdFlg5/a8f+tqGqm9h9Z5m0bAiDxYRBiq8DLWif+NBtJX/yp8OKmcRzo5l3NLhj 8Hxav2PoWT3Ud+Q3D6KZrSDn1IDknN4zvZ3jgvC4apy7nKIOsHpz6srdv843JPppb7e6 5bdRz4UuJVRMzGierlB4vGtdfXKmn1mg0hSMc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=AYd4MO1mab4DsI3oXnuuIOdJQpt3HHyVWWYJIA079S7VE/GFRyKdtxuw2ABQUPQazH sBCvIPAdhwiVMiQySDzMxToNDws3m747Lfga6OyZ/DIu6yJSeDaCQqIJujzbdD0kvlMq D6NOYSoCCBi99x/WpQuqSyGgKopJwx/5SLTns= MIME-Version: 1.0 Received: by 10.216.18.76 with SMTP id k54mr2006293wek.61.1298889446007; Mon, 28 Feb 2011 02:37:26 -0800 (PST) Received: by 10.216.80.147 with HTTP; Mon, 28 Feb 2011 02:37:25 -0800 (PST) In-Reply-To: <20110228084744.GB1819@garage.freebsd.pl> References: <20110227202957.GD1992@garage.freebsd.pl> <20110228084744.GB1819@garage.freebsd.pl> Date: Mon, 28 Feb 2011 10:37:25 +0000 Message-ID: From: krad To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Shawn Webb Subject: Re: HEADS UP: ZFSv28 is in! 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, 28 Feb 2011 10:37:29 -0000 On 28 February 2011 08:47, Pawel Jakub Dawidek wrote: > On Sun, Feb 27, 2011 at 04:03:01PM -0700, Shawn Webb wrote: >> I'm so excited for your work. Thanks so much for bringing zpool v28 to >> FreeBSD. Will v28 come to 8-stable? > > Yes, hopefully in 1-2 month(s). > > -- > Pawel Jakub Dawidek =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://ww= w.wheelsystems.com > FreeBSD committer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://= www.FreeBSD.org > Am I Evil? Yes, I Am! =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://yomo= li.com > ive never managed to be able to boot off my 4k aligned pool (ashift=3D12) on stable, does the import to head provide all the patches for this or is it a case of using the latest zfs v28 patch set for stable? I have no dying need for v28 yet, it just want to be able to boot onto the 4k drive and tidy things up. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 10:55:55 2011 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 D4EEC106566C; Mon, 28 Feb 2011 10:55:55 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 7A38A8FC0A; Mon, 28 Feb 2011 10:55:54 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 515F845CD9; Mon, 28 Feb 2011 11:55:53 +0100 (CET) Received: from localhost (58.wheelsystems.com [83.12.187.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 97D6F45C9F; Mon, 28 Feb 2011 11:55:47 +0100 (CET) Date: Mon, 28 Feb 2011 11:55:26 +0100 From: Pawel Jakub Dawidek To: krad Message-ID: <20110228105526.GD1819@garage.freebsd.pl> References: <20110227202957.GD1992@garage.freebsd.pl> <20110228084744.GB1819@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0IvGJv3f9h+YhkrH" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-3.9 required=4.5 tests=ALL_TRUSTED,BAYES_00, RCVD_IN_SORBS_DUL autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Shawn Webb Subject: Re: HEADS UP: ZFSv28 is in! 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, 28 Feb 2011 10:55:55 -0000 --0IvGJv3f9h+YhkrH Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 28, 2011 at 10:37:25AM +0000, krad wrote: > On 28 February 2011 08:47, Pawel Jakub Dawidek wrote: > > On Sun, Feb 27, 2011 at 04:03:01PM -0700, Shawn Webb wrote: > >> I'm so excited for your work. Thanks so much for bringing zpool v28 to > >> FreeBSD. Will v28 come to 8-stable? > > > > Yes, hopefully in 1-2 month(s). > > > > -- > > Pawel Jakub Dawidek =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://= www.wheelsystems.com > > FreeBSD committer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http:= //www.FreeBSD.org > > Am I Evil? Yes, I Am! =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://yo= moli.com > > >=20 > ive never managed to be able to boot off my 4k aligned pool > (ashift=3D12) on stable, does the import to head provide all the patches > for this or is it a case of using the latest zfs v28 patch set for > stable? I have no dying need for v28 yet, it just want to be able to > boot onto the 4k drive and tidy things up. Support for this is included in what I committed to HEAD. Even HEAD couldn't boot off of pools with ashift !=3D 9 until now. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --0IvGJv3f9h+YhkrH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk1rfx4ACgkQForvXbEpPzQ0gQCgyH/gNB+NFUa0PnyosrQveu6T 1oIAniCJi1R/WjYAvx3DR9YHiuZN2j9N =0osC -----END PGP SIGNATURE----- --0IvGJv3f9h+YhkrH-- From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 11:06:58 2011 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 7FFA3106566C for ; Mon, 28 Feb 2011 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 53EA98FC19 for ; Mon, 28 Feb 2011 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 p1SB6wBi011961 for ; Mon, 28 Feb 2011 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 p1SB6vIE011959 for freebsd-fs@FreeBSD.org; Mon, 28 Feb 2011 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Feb 2011 11:06:57 GMT Message-Id: <201102281106.p1SB6vIE011959@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, 28 Feb 2011 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 bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154681 fs [zfs] [panic] panic with FreeBSD-8 STABLE o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 o kern/154447 fs [zfs] [panic] Occasional panics - solaris assert somew f kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153847 fs [nfs] [panic] Kernel panic from incorrect m_free in nf o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153552 fs [zfs] zfsboot from 8.2-RC1 freeze at boot time o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable 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 p 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/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 f 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 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/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR 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 p 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 p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis 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/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 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 221 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 11:27:37 2011 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 A090B106564A for ; Mon, 28 Feb 2011 11:27:37 +0000 (UTC) (envelope-from quazi@bk.ru) Received: from fallback2.mail.ru (fallback2.mail.ru [94.100.176.87]) by mx1.freebsd.org (Postfix) with ESMTP id 554308FC1A for ; Mon, 28 Feb 2011 11:27:37 +0000 (UTC) Received: from smtp5.mail.ru (smtp5.mail.ru [94.100.176.132]) by fallback2.mail.ru (mPOP.Fallback_MX) with ESMTP id 56C843CC7140 for ; Mon, 28 Feb 2011 14:11:49 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=ZT6ymYOPE320EX60UjFs2QbPm2t6gYzQRulSgY38ie8=; b=xDp9iZgruK8glGYrzC6fcdZujWghSIOcDxRpEfzVT+VBeKW4FDE4lfUlITm5shxFmhipOYcitRVuBEvPgwyFexJfWa4I6InoZWrDduVmFE4UQW2xPIJArUb0WpRVe6Ri; Received: from [178.122.194.13] (port=60899 helo=QUAZIS.SNNLAN.local) by smtp5.mail.ru with asmtp id 1Pu111-0000ed-00 for freebsd-fs@freebsd.org; Mon, 28 Feb 2011 14:11:47 +0300 Message-ID: <4D6B8618.40205@bk.ru> Date: Mon, 28 Feb 2011 13:25:12 +0200 From: Ruslan Yakovlev User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20110118 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 X-Spam: Not detected X-Mras: Ok Subject: ZFS, booting trouble 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, 28 Feb 2011 11:27:37 -0000 Hi I install 8.2-RELEASE root on ZFS with GPT and all works fine if I don't use zpool export. FreeBSD can't boot if bootable pool exported (when we unmount zfs after installation finished or when we connect disk to other machine for data copy): gptzfsboot: No ZFS pools located, can't boot Now it can be fixed (zpool imported) only from other machine/OS/boot device. Can bootable pool will be protected from full export? From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 11:34:25 2011 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 256EF1065676 for ; Mon, 28 Feb 2011 11:34:25 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 0B3758FC12 for ; Mon, 28 Feb 2011 11:34:24 +0000 (UTC) Received: from omta08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by qmta10.emeryville.ca.mail.comcast.net with comcast id DPaQ1g0010FhH24AAPaQX1; Mon, 28 Feb 2011 11:34:24 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta08.emeryville.ca.mail.comcast.net with comcast id DPaP1g0050PUQVN8UPaP9B; Mon, 28 Feb 2011 11:34:24 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 657B19B427; Mon, 28 Feb 2011 03:34:23 -0800 (PST) Date: Mon, 28 Feb 2011 03:34:23 -0800 From: Jeremy Chadwick To: Pawel Jakub Dawidek Message-ID: <20110228113423.GA21258@icarus.home.lan> References: <20110227202957.GD1992@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110227202957.GD1992@garage.freebsd.pl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: HEADS UP: ZFSv28 is in! 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, 28 Feb 2011 11:34:25 -0000 On Sun, Feb 27, 2011 at 09:29:57PM +0100, Pawel Jakub Dawidek wrote: > I just committed ZFSv28 to HEAD. Thank you so much for this effort! I look forward to trying this once it's MFC'd to RELENG_8 in the upcoming future. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 13:50:23 2011 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 86F4510656B4; Mon, 28 Feb 2011 13:50:23 +0000 (UTC) (envelope-from lhmwzy@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 224128FC12; Mon, 28 Feb 2011 13:50:22 +0000 (UTC) Received: by qyk35 with SMTP id 35so2069119qyk.13 for ; Mon, 28 Feb 2011 05:50:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=37MLyZ3q5lGel3Oy2nQFINpTH7trz6hIg8g5a6WmKEc=; b=KBptLgxJF9B4s8GNJW4G6NBZui2TYYQ44IGViwpvY6IiYvaNVvRmuMKmZ9GtLKAk1m 9jspat+plko8jVaYbYuooHTzULNcOznqgvgXgJBBY5HDKD1rdfVE57vqo5x34JQyvOYk Z9sB30qNY0g4U9ShES8abA/7eUAsQqE9h0SMQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=AvSnXqbJBn/pLEQURGIz3Z5QBJ81a/wwmToYPf/wMETUZacNvmNEyOWN8Ne6xAV0e6 H9kHKtozFLK4z3AN09PkzkRqpuLJYXi1Z6U6rjWREe5F6MlpgFmYmWFduqg4RLbYR7Xj x7U6X4HwjPNceOV73oI8II85rqHSGJ1biE2nI= MIME-Version: 1.0 Received: by 10.229.95.200 with SMTP id e8mr4205284qcn.116.1298899457990; Mon, 28 Feb 2011 05:24:17 -0800 (PST) Received: by 10.229.182.20 with HTTP; Mon, 28 Feb 2011 05:24:17 -0800 (PST) In-Reply-To: <20110227202957.GD1992@garage.freebsd.pl> References: <20110227202957.GD1992@garage.freebsd.pl> Date: Mon, 28 Feb 2011 21:24:17 +0800 Message-ID: From: lhmwzy To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Pawel Jakub Dawidek Subject: Re: HEADS UP: ZFSv28 is in! 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, 28 Feb 2011 13:50:23 -0000 Tks for PJD's work for zfs. Would V28 is the last version of zfs because oracle don't open the zfs code after V28? 2011/2/28 Pawel Jakub Dawidek : > Hi. > > I just committed ZFSv28 to HEAD. > > New major features: > > - Data deduplication. > - Triple parity RAIDZ (RAIDZ3). > - zfs diff. > - zpool split. > - Snapshot holds. > - zpool import -F. Allows to rewind corrupted pool to earlier > =A0transaction group. > - Possibility to import pool in read-only mode. > > PS. If you like my work, you help me to promote yomoli.com:) > > =A0 =A0 =A0 =A0http://yomoli.com > =A0 =A0 =A0 =A0http://www.facebook.com/pages/Yomolicom/178311095544155 > > -- > Pawel Jakub Dawidek =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://ww= w.wheelsystems.com > FreeBSD committer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://= www.FreeBSD.org > Am I Evil? Yes, I Am! =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://yomo= li.com > From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 18:12:55 2011 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 A19C9106566B for ; Mon, 28 Feb 2011 18:12:55 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 48A548FC18 for ; Mon, 28 Feb 2011 18:12:54 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 2FCC645C9C; Mon, 28 Feb 2011 19:12:53 +0100 (CET) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 1016445C8A; Mon, 28 Feb 2011 19:12:47 +0100 (CET) Date: Mon, 28 Feb 2011 19:12:26 +0100 From: Pawel Jakub Dawidek To: Ruslan Yakovlev Message-ID: <20110228181226.GA2288@garage.freebsd.pl> References: <4D6B8618.40205@bk.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline In-Reply-To: <4D6B8618.40205@bk.ru> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS, booting trouble 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, 28 Feb 2011 18:12:55 -0000 --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 28, 2011 at 01:25:12PM +0200, Ruslan Yakovlev wrote: > Hi >=20 > I install 8.2-RELEASE root on ZFS with GPT and all works fine if I don't= =20 > use zpool export. > FreeBSD can't boot if bootable pool exported (when we unmount zfs after= =20 > installation finished or when we connect disk to other machine for data= =20 > copy): > gptzfsboot: No ZFS pools located, can't boot >=20 > Now it can be fixed (zpool imported) only from other machine/OS/boot devi= ce. > Can bootable pool will be protected from full export? In the recent ZFSv28 import I changed that. Now only destroyed pools are skipped, so you can boot off of exported pool. If you want to do it now in FreeBSD 8.x try this patch: Index: sys/boot/zfs/zfsimpl.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/boot/zfs/zfsimpl.c (wersja 218013) +++ sys/boot/zfs/zfsimpl.c (kopia robocza) @@ -814,17 +814,8 @@ return (EIO); } =20 -#ifndef TEST - if (val !=3D POOL_STATE_ACTIVE) { - /* - * Don't print a message here. If we happen to reboot - * while where is an exported pool around, we don't - * need a cascade of confusing messages during boot. - */ - /*printf("ZFS: pool is not active\n");*/ + if (val =3D=3D POOL_STATE_DESTROYED) return (EIO); - } -#endif =20 if (nvlist_find(nvlist, ZPOOL_CONFIG_POOL_TXG, You need to recompile gptzfsboot and install it with gpart(8). --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk1r5YoACgkQForvXbEpPzQzdgCfZpNPZTAxYFxz+lussbi0FLlR atEAoJd+W5dgNnYn5nlZ5J8O2eZloodK =4kOT -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 18:34:21 2011 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 84F2C106566B; Mon, 28 Feb 2011 18:34:21 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.27]) by mx1.freebsd.org (Postfix) with ESMTP id 4090A8FC17; Mon, 28 Feb 2011 18:34:21 +0000 (UTC) Received: from [78.34.134.52] (helo=r500.local) by smtprelay04.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1Pu7jP-0000km-6A; Mon, 28 Feb 2011 19:22:03 +0100 Date: Mon, 28 Feb 2011 19:21:29 +0100 From: Fabian Keil To: Pawel Jakub Dawidek Message-ID: <20110228192129.119cac0c@r500.local> In-Reply-To: <20110227202957.GD1992@garage.freebsd.pl> References: <20110227202957.GD1992@garage.freebsd.pl> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; amd64-portbld-freebsd9.0) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/fRlH.x0m6Y9akYPdbdZ42Lo"; protocol="application/pgp-signature" X-Df-Sender: 775067 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: HEADS UP: ZFSv28 is in! 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, 28 Feb 2011 18:34:21 -0000 --Sig_/fRlH.x0m6Y9akYPdbdZ42Lo Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Pawel Jakub Dawidek wrote: > I just committed ZFSv28 to HEAD. I updated the system without removing the tuning for ZFSv15 first, and somehow this completely messed up the performance. Booting the system took more than ten minutes and even once it was up it was next to unresponsive. I'm not sure which sysctl was to blame, but after removing all but vfs.zfs.arc_max=3D"800M" and rebooting, the problem was gone. I haven't seen this issue with earlier ZFS updates, so maybe this would be worth mentioning in UPDATING? Anyway, the things I tested so far (zfs/zpool upgrade, delegation, send, receive, snapshot) worked fine. Thanks a lot. Fabian --Sig_/fRlH.x0m6Y9akYPdbdZ42Lo Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAk1r56wACgkQBYqIVf93VJ2kOgCdGadLXaY/LllO7L5HEG4BSAZ1 YtkAnA8D8O6UxW8hw3o9rTCEOfvKSX9t =UdGi -----END PGP SIGNATURE----- --Sig_/fRlH.x0m6Y9akYPdbdZ42Lo-- From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 20:48:57 2011 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 126D91065672; Mon, 28 Feb 2011 20:48:57 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id B41BE8FC0C; Mon, 28 Feb 2011 20:48:56 +0000 (UTC) Received: from outgoing.leidinger.net (p5B32E9EA.dip.t-dialin.net [91.50.233.234]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 052EA844015; Mon, 28 Feb 2011 21:48:52 +0100 (CET) Received: from unknown (IO.Leidinger.net [192.168.2.110]) by outgoing.leidinger.net (Postfix) with ESMTP id DF2D6204E; Mon, 28 Feb 2011 21:48:48 +0100 (CET) Date: Mon, 28 Feb 2011 21:48:47 +0100 From: Alexander Leidinger To: Fabian Keil Message-ID: <20110228214847.0000078c@unknown> In-Reply-To: <20110228192129.119cac0c@r500.local> References: <20110227202957.GD1992@garage.freebsd.pl> <20110228192129.119cac0c@r500.local> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 052EA844015.A733E X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1299530933.12804@nV6lTlzH+baCVUHGlPholw X-EBL-Spam-Status: No Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: HEADS UP: ZFSv28 is in! 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, 28 Feb 2011 20:48:57 -0000 On Mon, 28 Feb 2011 19:21:29 +0100 Fabian Keil wrote: > Pawel Jakub Dawidek wrote: > > > I just committed ZFSv28 to HEAD. > > I updated the system without removing the tuning for ZFSv15 > first, and somehow this completely messed up the performance. > Booting the system took more than ten minutes and even once > it was up it was next to unresponsive. > > I'm not sure which sysctl was to blame, but after removing > all but vfs.zfs.arc_max="800M" and rebooting, the problem > was gone. When you add the tuning back, does it take minutes again to boot? If not, I assume it was cleaning up some leftovers the old version was not able to cleanup. Bye, Alexander. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 22:18:04 2011 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 185241065672 for ; Mon, 28 Feb 2011 22:18:04 +0000 (UTC) (envelope-from am@raisa.eu.org) Received: from raisa.eu.org (178-73-15-208.home.aster.pl [178.73.15.208]) by mx1.freebsd.org (Postfix) with ESMTP id CA3078FC0A for ; Mon, 28 Feb 2011 22:18:03 +0000 (UTC) Received: from bolt.zol (nereis.pl [62.121.98.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by raisa.eu.org (Postfix) with ESMTP id 15D7F244; Mon, 28 Feb 2011 21:08:48 +0100 (CET) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes In-Reply-To: <4D6AAC9A.4000602@jrv.org> References: <4D6AAC9A.4000602@jrv.org> To: "James R. Van Artsdalen" From: "Emil Smolenski" Date: Mon, 28 Feb 2011 21:08:19 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera Mail/11.01 (FreeBSD) Cc: freebsd-fs@freebsd.org Subject: Re: [ZFS] Booting from zpool created on 4k-sector drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2011 22:18:04 -0000 On Sun, 27 Feb 2011 20:57:14 +0100, James R. Van Artsdalen wrote: > Emil Smolenski wrote: >> Hello, >> >> There is a hack to force zpool creation with minimum sector size equal >> to 4k: >> >> # gnop create -S 4096 ${DEV0} >> # zpool create tank ${DEV0}.nop >> # zpool export tank >> # gnop destroy ${DEV0}.nop >> # zpool import tank >> >> This change is permanent. The only possibility to change the value of >> ashift is: zpool destroy/create and restoring pool from backup. > > Is ashift a property of the pool or a property of the device? It is property of the ZFS pool. It is calculated when the pool is created based on the sector size advertised by devices. > I'm wonder about the disk replacement scenario, where the replacement > disk cannot be smaller than the disk it replaces. And the new disk must advertise sector size equal or smaller than 2**ashift of the existing pool. -- am From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 23:13:34 2011 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 E355E106564A for ; Mon, 28 Feb 2011 23:13:34 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8808FC0A for ; Mon, 28 Feb 2011 23:13:34 +0000 (UTC) Received: by gxk7 with SMTP id 7so2013436gxk.13 for ; Mon, 28 Feb 2011 15:13:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LQfGJyjJKbLIkoPvwnQb+W87X08s75vFxyGK1sh4M3g=; b=td/qsBXw4gZTiF7Fy20DQUR94OrZEn1zH0vf5SBkx18M832eqV9MGqh8aRU54Hn0Zd M/IpcmFxDsSvhkI2V6tRuYIevUHLl+2pGaXfmwLgWh1v/PzjrUDIFzuCGyVEmBTnkb8n 3yRzIw1wUgR+umMslrr5oSgKNZ5RqZuHS4Z/w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=C4Zjq9wB52kstHQXv5xg6E3JWGqhNwBd0UGwglj1UpwOfOEIugXcjIeJhqhq4JXfV8 8+P2UnNmGeVMOj9gSVzI1Nmoa26Vr35xITHz5uU57v7fmH1eIHZ8V3AT8aAhxmQE+eOA dsfsWVawFlCXjoXtKbRPbeQV6n9GN5UEzybbo= MIME-Version: 1.0 Received: by 10.100.32.2 with SMTP id f2mr2470935anf.177.1298934813848; Mon, 28 Feb 2011 15:13:33 -0800 (PST) Received: by 10.100.171.8 with HTTP; Mon, 28 Feb 2011 15:13:33 -0800 (PST) In-Reply-To: References: <4D6AAC9A.4000602@jrv.org> Date: Mon, 28 Feb 2011 15:13:33 -0800 Message-ID: From: Freddie Cash To: Emil Smolenski Content-Type: text/plain; charset=UTF-8 Cc: freebsd-fs@freebsd.org Subject: Re: [ZFS] Booting from zpool created on 4k-sector drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2011 23:13:35 -0000 On Mon, Feb 28, 2011 at 12:08 PM, Emil Smolenski wrote: > On Sun, 27 Feb 2011 20:57:14 +0100, James R. Van Artsdalen > wrote: >> Emil Smolenski wrote: >>> There is a hack to force zpool creation with minimum sector size equal >>> to 4k: >>> >>> # gnop create -S 4096 ${DEV0} >>> # zpool create tank ${DEV0}.nop >>> # zpool export tank >>> # gnop destroy ${DEV0}.nop >>> # zpool import tank >>> >>> This change is permanent. The only possibility to change the value of >>> ashift is: zpool destroy/create and restoring pool from backup. >> >> Is ashift a property of the pool or a property of the device? > > It is property of the ZFS pool. It is calculated when the pool is created > based on the sector size advertised by devices. Can you point to where in the source this is set? And where it's used? I'd like to have this confirmed once and for all. :) I've seen conflicting reports around the web that it's a per-vdev setting and that it's a per-pool setting. For example, this thread in the FreeBSD Forums shows it to be a per-vdev setting: https://forums.freebsd.org/showthread.php?t=21644 Yet many threads on the zfs-discuss mailing list say it's a per-pool setting based on the first vdev added to the pool. >> I'm wonder about the disk replacement scenario, where the replacement >> disk cannot be smaller than the disk it replaces. > > And the new disk must advertise sector size equal or smaller than > 2**ashift of the existing pool. Why? What's the harm in running with ashift=12 (4 KB) on a drive that uses 0.5 KB sectors? Wouldn't that be the best setup to use, to future-proof the pool? -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 01:07:22 2011 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 BD6931065691 for ; Tue, 1 Mar 2011 01:07:22 +0000 (UTC) (envelope-from am@raisa.eu.org) Received: from raisa.eu.org (178-73-15-208.home.aster.pl [178.73.15.208]) by mx1.freebsd.org (Postfix) with ESMTP id 79E2C8FC15 for ; Tue, 1 Mar 2011 01:07:21 +0000 (UTC) Received: from bolt.zol (nereis.pl [62.121.98.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by raisa.eu.org (Postfix) with ESMTP id 93A171AF; Tue, 1 Mar 2011 02:07:42 +0100 (CET) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Freddie Cash" References: <4D6AAC9A.4000602@jrv.org> Date: Tue, 01 Mar 2011 02:07:14 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Emil Smolenski" Message-ID: In-Reply-To: User-Agent: Opera Mail/11.01 (FreeBSD) Cc: freebsd-fs@freebsd.org Subject: Re: [ZFS] Booting from zpool created on 4k-sector drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2011 01:07:22 -0000 On Tue, 01 Mar 2011 00:13:33 +0100, Freddie Cash wrote: > On Mon, Feb 28, 2011 at 12:08 PM, Emil Smolenski wrote: >> On Sun, 27 Feb 2011 20:57:14 +0100, James R. Van Artsdalen >> wrote: >>> Emil Smolenski wrote: >>>> There is a hack to force zpool creation with minimum sector size equal >>>> to 4k: >>>> >>>> # gnop create -S 4096 ${DEV0} >>>> # zpool create tank ${DEV0}.nop >>>> # zpool export tank >>>> # gnop destroy ${DEV0}.nop >>>> # zpool import tank >>>> >>>> This change is permanent. The only possibility to change the value of >>>> ashift is: zpool destroy/create and restoring pool from backup. >>> >>> Is ashift a property of the pool or a property of the device? >> >> It is property of the ZFS pool. It is calculated when the pool is >> created >> based on the sector size advertised by devices. > > Can you point to where in the source this is set? And where it's used? > > I'd like to have this confirmed once and for all. :) > > I've seen conflicting reports around the web that it's a per-vdev > setting and that it's a per-pool setting. > > For example, this thread in the FreeBSD Forums shows it to be a > per-vdev setting: > https://forums.freebsd.org/showthread.php?t=21644 > > Yet many threads on the zfs-discuss mailing list say it's a per-pool > setting based on the first vdev added to the pool. It is property of vdev actually. I wrote ``it is property of ZFS pool'' in opposite to ``it is property of device''. Sorry for the confusion. There is no need to read sources to obtain this information -- zdb(1m) is sufficient. >>> I'm wonder about the disk replacement scenario, where the replacement >>> disk cannot be smaller than the disk it replaces. >> >> And the new disk must advertise sector size equal or smaller than >> 2**ashift of the existing pool. > > Why? What's the harm in running with ashift=12 (4 KB) on a drive that > uses 0.5 KB sectors? Wouldn't that be the best setup to use, to > future-proof the pool? Yes. That is exactly what I mean. See my first message in this thread for reference: http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010350.html James asks about disk replacement scenario. In this case you cannot use device with greater sector size than 2**ashift of the existing vdev as replacement: # diskinfo -v md0 |grep sectorsize 512 # sectorsize # zpool create test0 md0 # zdb test0 |grep ashift ashift=9 # diskinfo -v md1.nop |grep sectorsize 4096 # sectorsize # zpool replace test0 md0 md1.nop cannot replace md0 with md1.nop: devices have different sector alignment -- am From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 04:01:55 2011 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 4EECA106566C for ; Tue, 1 Mar 2011 04:01:55 +0000 (UTC) (envelope-from ethernext@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 064938FC19 for ; Tue, 1 Mar 2011 04:01:54 +0000 (UTC) Received: by qyk35 with SMTP id 35so2699392qyk.13 for ; Mon, 28 Feb 2011 20:01:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=H1r6ph9IRLXr3Fiepfr8GZuNxirs85FE+mpFuGFxqTY=; b=LETpwF3UJ5MlxkKTvEHEDDE2hbL6JhZD6nD8oQ+VkouCv83vqimC26/Wro2Mf+RYo6 xjdSiKto6vI0zk7ruFlsmDN2pkr8DeU5ndutl1BW9QCFbrvR8Q7q8i1zG56lhVibeeL3 hssnVrB/zGyyr+tFYMfSYn/rcqpe1khFfjZQg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=J9IOzJvYnfHE8kT+0zb69PDC/1DGDOBByXqpkDYWgv5Vm+0N6uG39H3RwTK8i54g24 x1vp0+cLItO+aR2NuWR8YZFz192JIlZF59ahdcFhXWi+UZLJMhIejJiHzI0zMpHy46dJ HNq3IYiA6mg4bfPIuWt5MJs6ukRDBsoOSukXA= MIME-Version: 1.0 Received: by 10.229.81.15 with SMTP id v15mr4783724qck.209.1298950524987; Mon, 28 Feb 2011 19:35:24 -0800 (PST) Sender: ethernext@gmail.com Received: by 10.229.102.67 with HTTP; Mon, 28 Feb 2011 19:35:24 -0800 (PST) Date: Mon, 28 Feb 2011 22:35:24 -0500 X-Google-Sender-Auth: tXb92c1hwHap1e3IkqyK2-XcdPk Message-ID: From: Bill Desjardins To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: HAST, zvols, istgt and carp working... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2011 04:01:55 -0000 Hello All, as an experiment today I setup a couple 8-stable guests on vmware ESXI to test hast with zfs, carp and istgt for a redundant nas system I am putting together. I havent seen any mention that anyone has used hast to mirror a zfs zvol so I figured I would try it and atleast my proof of concept seems to work just fine. is anyone doing this and using it in a production environment? heres how I setup the testing environment... - created (2) 8-stable hosts on esxi 4.1: hast-1 & hast-2 (os on da0) on both hast-1 and hast-2 - added 4 x 8GB disk's to each (da1 - da4) - glabel'd disks disk1 - disk4 - zpool create tank mirror disk1 disk2 mirror disk3 disk4 - zfs create -p -s -b 64k -V 4G tank/hzvol.1 hast.conf on each resource tank_hzvol.1 { local /dev/zvol/tank/hzvol.1 on hast-1 { remote x.x.x.9 } on hast-2 { remote x.x.x.8 } } on hast-1 and hast-2 > hastd_enable="YES" in rc.conf > hastctl create tank_hzvol.1 > /etc/rc.d/hastd start on hast-2 > hastctl role secondary tank_hzvol.1 on hast-1 > hastctl role primary tank_hzvol.1 hastctl status reports all is well so far... next I configured istgt identically on hast-1 and hast-2 for the hast device >> LUN0 Storage /dev/hast/tank_hzvol.1 3G istgt was started (istgt onestart) and the zvol target was setup on another vmware esxi server which then was formatted as a vmfs volume. I created a 2GB disk on this volume and added it to another 8-stable host as a ufs disk mounted on /mnt. so far going good, everything working as expected. to test hast replication, I created a few 200MB files on the host with the ufs vmdk volume and seen traffic over the hast network from hast-1 to hast-2. on hast-1, the zvol size reflected correct sparse disk space usage, but hast-2 showed the full 4GB zvol allocated which I suspect is due to hast. to test failover of the isci zvol target from hast-1 to hast-2: on hast-1 > istgt stop > hastctl role secondary tank_hzvol.1 on hast-2 > hastctl role primary tank_hzvol.1 > istgt onestart NOTE: carp does not seem to work on esxi for me so between hast-1 and hast-2 I manually moved the IP for istgt to hast-2. the result was that the istgt hast zvol successfully failed over to hast-2 with only a brief stall while I manually performed the failover process. I only performed the ideal manual failover scenario for proof of concept. I will be testing this on 2 real development servers later this week for a more complete understanding. I see some real advantages for zvols only hast: ++++++++++++++++++++++++++++++++++++++++++++++++ + no need to hast each individual disk in the zpool so you can access all available storage on either storage unit + maintaining storage units remains functionally consistent between them + once setup, zvols are easily migrated to new storage environments in real-time since there is only a single zvol hast resource to replicate. (no need to have all matching zpool hast members, just reconfigure the primary zvol hast resource to point to a new secondary server and swap roles/failover when ready) + can have active hast zvols on each unit to distribute IO + no need for zpool export/import on failover + hast easily added to current zvols + retains performance of entire zpool + zpool can be expanded without changing hast config + minimizes hast replication traffic between storage units + hast split-brain localized to specific zvol's + can use ufs on hast zvol resource for things like samba and nfs cons ------------------------------------------- - performace impact (???) - each hast zvol requires distinct application configurations (more confgurations to deal with/screw up) - zfs sparse volumes seem not to be working correctly via hast (???) - expanding zvol requires hastctl create, init, startup plus may need application specific changes/restart. - other methods needed to replicate data in rest of pool - possible long rebuild time on large zvols? - snapshots / rollbacks (???) - many more??? my main question is if using hast to replicate a zvol is a supported configuration and what are the possible drawbacks? Its more than likely I am overlooking some very basic requirement/restrictions and am blatantly wrong in all this, but if it can perform, I think its a big+ for freebsd and zfs useability as a nas server. thoughts? comments? criticisms? :) Best, Bill From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 13:36:05 2011 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 8E4261065676 for ; Tue, 1 Mar 2011 13:36:05 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 351288FC14 for ; Tue, 1 Mar 2011 13:36:04 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id AB36E45C9C; Tue, 1 Mar 2011 14:36:02 +0100 (CET) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id A303E45C8A; Tue, 1 Mar 2011 14:35:56 +0100 (CET) Date: Tue, 1 Mar 2011 14:35:33 +0100 From: Pawel Jakub Dawidek To: Bill Desjardins Message-ID: <20110301133533.GD2288@garage.freebsd.pl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sXc4Kmr5FA7axrvy" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: HAST, zvols, istgt and carp working... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2011 13:36:05 -0000 --sXc4Kmr5FA7axrvy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 28, 2011 at 10:35:24PM -0500, Bill Desjardins wrote: [...] > - zfs sparse volumes seem not to be working correctly via hast (???) You have two options: 1. Connect both nodes _before_ doing any writes to HAST provider. This way HAST on first connect won't synchronize any data. In other case it will perform full synchronization which in turn will allocate entire ZVOL. 2. Turn on compression (lzjb) on ZVOLs. This should be very fast and when compression is on all-zeros blocks are turned into holes, so after synchronizing whole thing, you will see space in ZVOL allocated only for real data. > - possible long rebuild time on large zvols? HAST rebuild time depends on the traffic, not components size. > my main question is if using hast to replicate a zvol is a supported > configuration and what are the possible drawbacks? [...] Well, you definiately can do it, but have you considered putting entire pool on HAST device? This way you can have multiple ZVOLs, snapshots and rollbacks. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --sXc4Kmr5FA7axrvy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk1s9iUACgkQForvXbEpPzTz/wCg3cX8uPxIUnLt+tBHXvlSs2NB 5NoAoMsn12v4AMw3SZ+YWJjLDhJH8Z9p =5H/+ -----END PGP SIGNATURE----- --sXc4Kmr5FA7axrvy-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 15:15:03 2011 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 EEDD81065693; Tue, 1 Mar 2011 15:15:02 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A099A8FC21; Tue, 1 Mar 2011 15:15:02 +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 p21FF2fA062442; Tue, 1 Mar 2011 15:15:02 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p21FF2UO062438; Tue, 1 Mar 2011 10:15:02 -0500 (EST) (envelope-from eadler) Date: Tue, 1 Mar 2011 10:15:02 -0500 (EST) Message-Id: <201103011515.p21FF2UO062438@freefall.freebsd.org> To: eugen@grosbein.pp.ru, eadler@FreeBSD.org, freebsd-fs@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/116608: [msdosfs] [patch] msdosfs fails to check mount options 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, 01 Mar 2011 15:15:03 -0000 Synopsis: [msdosfs] [patch] msdosfs fails to check mount options State-Changed-From-To: patched->closed State-Changed-By: eadler State-Changed-When: Tue Mar 1 10:15:02 EST 2011 State-Changed-Why: This PR is fixed in head, 8.x and 7.x, but will not be merged to 6.x now that that branch is unsupported, sorry http://www.freebsd.org/cgi/query-pr.cgi?pr=116608 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 15:15:42 2011 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 D6E6A10656AB; Tue, 1 Mar 2011 15:15:42 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AEE8E8FC0C; Tue, 1 Mar 2011 15:15:42 +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 p21FFgmP063303; Tue, 1 Mar 2011 15:15:42 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p21FFgr0063299; Tue, 1 Mar 2011 10:15:42 -0500 (EST) (envelope-from eadler) Date: Tue, 1 Mar 2011 10:15:42 -0500 (EST) Message-Id: <201103011515.p21FFgr0063299@freefall.freebsd.org> To: danny@cs.huji.ac.il, eadler@FreeBSD.org, freebsd-fs@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/144458: [nfs] [patch] nfsd fails as a kld 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, 01 Mar 2011 15:15:42 -0000 Synopsis: [nfs] [patch] nfsd fails as a kld State-Changed-From-To: open->patched State-Changed-By: eadler State-Changed-When: Tue Mar 1 10:15:42 EST 2011 State-Changed-Why: committed in head (r209191) http://www.freebsd.org/cgi/query-pr.cgi?pr=144458 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 15:15:51 2011 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 114D81065670; Tue, 1 Mar 2011 15:15:51 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DD55E8FC16; Tue, 1 Mar 2011 15:15:50 +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 p21FFobL063463; Tue, 1 Mar 2011 15:15:50 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p21FForF063458; Tue, 1 Mar 2011 10:15:50 -0500 (EST) (envelope-from eadler) Date: Tue, 1 Mar 2011 10:15:50 -0500 (EST) Message-Id: <201103011515.p21FForF063458@freefall.freebsd.org> To: mi@aldan.algebra.com, eadler@FreeBSD.org, freebsd-fs@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/133614: [panic] panic: ffs_truncate: read-only filesystem 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, 01 Mar 2011 15:15:51 -0000 Synopsis: [panic] panic: ffs_truncate: read-only filesystem State-Changed-From-To: open->patched State-Changed-By: eadler State-Changed-When: Tue Mar 1 10:15:49 EST 2011 State-Changed-Why: committed in head (r218852) http://www.freebsd.org/cgi/query-pr.cgi?pr=133614 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 15:16:06 2011 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 4195110656E9; Tue, 1 Mar 2011 15:16:06 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 18A828FC28; Tue, 1 Mar 2011 15:16:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p21FG5RI063792; Tue, 1 Mar 2011 15:16:05 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p21FG5oH063787; Tue, 1 Mar 2011 10:16:05 -0500 (EST) (envelope-from eadler) Date: Tue, 1 Mar 2011 10:16:05 -0500 (EST) Message-Id: <201103011516.p21FG5oH063787@freefall.freebsd.org> To: pmc@citylink.dinoex.sub.org, eadler@FreeBSD.org, freebsd-fs@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/138790: [zfs] ZFS ceases caching when mem demand is high 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, 01 Mar 2011 15:16:06 -0000 Synopsis: [zfs] ZFS ceases caching when mem demand is high State-Changed-From-To: open->patched State-Changed-By: eadler State-Changed-When: Tue Mar 1 10:16:05 EST 2011 State-Changed-Why: committed in head (r212783) http://www.freebsd.org/cgi/query-pr.cgi?pr=138790 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 15:23:03 2011 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 7E7EF1065672; Tue, 1 Mar 2011 15:23:03 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 55CE48FC16; Tue, 1 Mar 2011 15:23:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p21FN37X074450; Tue, 1 Mar 2011 15:23:03 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p21FN3Gw074446; Tue, 1 Mar 2011 10:23:03 -0500 (EST) (envelope-from eadler) Date: Tue, 1 Mar 2011 10:23:03 -0500 (EST) Message-Id: <201103011523.p21FN3Gw074446@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-fs@FreeBSD.org, rmacklem@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/144458: [nfs] [patch] nfsd fails as a kld 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, 01 Mar 2011 15:23:03 -0000 Synopsis: [nfs] [patch] nfsd fails as a kld Responsible-Changed-From-To: freebsd-fs->rmacklem Responsible-Changed-By: eadler Responsible-Changed-When: Tue Mar 1 10:23:02 EST 2011 Responsible-Changed-Why: same as above http://www.freebsd.org/cgi/query-pr.cgi?pr=144458 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 15:23:10 2011 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 4CA5F106564A; Tue, 1 Mar 2011 15:23:10 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 23ECC8FC23; Tue, 1 Mar 2011 15:23:10 +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 p21FNAJM074615; Tue, 1 Mar 2011 15:23:10 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p21FNAhJ074611; Tue, 1 Mar 2011 10:23:10 -0500 (EST) (envelope-from eadler) Date: Tue, 1 Mar 2011 10:23:10 -0500 (EST) Message-Id: <201103011523.p21FNAhJ074611@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-fs@FreeBSD.org, jh@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/133614: [panic] panic: ffs_truncate: read-only filesystem 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, 01 Mar 2011 15:23:10 -0000 Synopsis: [panic] panic: ffs_truncate: read-only filesystem Responsible-Changed-From-To: freebsd-fs->jh Responsible-Changed-By: eadler Responsible-Changed-When: Tue Mar 1 10:23:09 EST 2011 Responsible-Changed-Why: same as above http://www.freebsd.org/cgi/query-pr.cgi?pr=133614 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 15:23:16 2011 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 A3FDC10656D3; Tue, 1 Mar 2011 15:23:16 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7B54C8FC0C; Tue, 1 Mar 2011 15:23:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p21FNGVq074784; Tue, 1 Mar 2011 15:23:16 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p21FNG1l074780; Tue, 1 Mar 2011 10:23:16 -0500 (EST) (envelope-from eadler) Date: Tue, 1 Mar 2011 10:23:16 -0500 (EST) Message-Id: <201103011523.p21FNG1l074780@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-fs@FreeBSD.org, avg@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/138790: [zfs] ZFS ceases caching when mem demand is high 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, 01 Mar 2011 15:23:16 -0000 Synopsis: [zfs] ZFS ceases caching when mem demand is high Responsible-Changed-From-To: freebsd-fs->avg Responsible-Changed-By: eadler Responsible-Changed-When: Tue Mar 1 10:23:16 EST 2011 Responsible-Changed-Why: same as above http://www.freebsd.org/cgi/query-pr.cgi?pr=138790 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 17:11:16 2011 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 DE83D106566B for ; Tue, 1 Mar 2011 17:11:16 +0000 (UTC) (envelope-from a.smith@ukgrid.net) Received: from mx0.ukgrid.net (mx0.ukgrid.net [89.21.28.41]) by mx1.freebsd.org (Postfix) with ESMTP id A78958FC0A for ; Tue, 1 Mar 2011 17:11:16 +0000 (UTC) Received: from [89.21.28.38] (port=51113 helo=omicron.ukgrid.net) by mx0.ukgrid.net with esmtp (Exim 4.74; FreeBSD) envelope-from a.smith@ukgrid.net envelope-to freebsd-fs@freebsd.org id 1PuSmz-0002DR-Ej; Tue, 01 Mar 2011 16:51:09 +0000 Received: from voip.ukgrid.net (voip.ukgrid.net [89.107.16.9]) by webmail2.ukgrid.net (Horde Framework) with HTTP; Tue, 01 Mar 2011 16:51:09 +0000 Message-ID: <20110301165109.15323wik427mxjs4@webmail2.ukgrid.net> Date: Tue, 01 Mar 2011 16:51:09 +0000 From: a.smith@ukgrid.net To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) / FreeBSD-8.1 Subject: ZFS disk names and gptid under 8.2-RELEASE 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, 01 Mar 2011 17:11:16 -0000 Hi, I've just upgraded my first production server to 8.2-RELEASE, all fine except for one thing. ZFS is now listing my disk devices by their gptid names, ie # zpool status pool: nfsen state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM nfsen ONLINE 0 0 0 mirror ONLINE 0 0 0 gptid/55c03af2-5c54-11df-af69-001143d8b2eb ONLINE 0 0 0 gptid/58ef6152-5c54-11df-af69-001143d8b2eb ONLINE 0 0 0 errors: No known data errors Previously they were showing as ada0p1 etc. I was quite happy with the previous method as I'd fixed the device names via /boot/device.hints and this made it (to me) perfectly human readable without having to use labels. Is this something that in 8.2 is now hard coded into ZFS? Ie I am forced to use gptid or disk labelling? thanks Andy. From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 17:39:54 2011 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 AFF251065676 for ; Tue, 1 Mar 2011 17:39:54 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward7.mail.yandex.net (forward7.mail.yandex.net [77.88.61.37]) by mx1.freebsd.org (Postfix) with ESMTP id 3E12B8FC18 for ; Tue, 1 Mar 2011 17:39:53 +0000 (UTC) Received: from smtp7.mail.yandex.net (smtp7.mail.yandex.net [77.88.61.55]) by forward7.mail.yandex.net (Yandex) with ESMTP id E628B1C1006; Tue, 1 Mar 2011 20:39:51 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1299001191; bh=tS4sPXCiDSs/LvWNTlBfUWEGG9nvaqOzj4FZxcMwBpQ=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=FkwocSy14FjWDQyKym6Apjnrp0vsXi8RpNU2YXOoC7OXdVcxslDH5XXoC3FXig70x KI8ds+C/0TF8/dZE61gu7eQS8cQeXfWvdREx0bq/6TTH2KK6YlS80tJJU6nR9JRA/B 7aHWzYcUPblXSmJ8q1+1MRIHYWXO4FC43hjgqNJQ= Received: from [178.141.6.53] (dynamic-178-141-6-53.kirov.comstar-r.ru [178.141.6.53]) by smtp7.mail.yandex.net (Yandex) with ESMTPSA id A6AAE48C805B; Tue, 1 Mar 2011 20:39:51 +0300 (MSK) Message-ID: <4D6D2F56.6040805@yandex.ru> Date: Tue, 01 Mar 2011 20:39:34 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110122 Thunderbird/3.1.7 MIME-Version: 1.0 To: a.smith@ukgrid.net References: <20110301165109.15323wik427mxjs4@webmail2.ukgrid.net> In-Reply-To: <20110301165109.15323wik427mxjs4@webmail2.ukgrid.net> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig10BA319D67B3F42A41431416" Cc: freebsd-fs@freebsd.org Subject: Re: ZFS disk names and gptid under 8.2-RELEASE 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, 01 Mar 2011 17:39:54 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig10BA319D67B3F42A41431416 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On 01.03.2011 19:51, a.smith@ukgrid.net wrote: > Previously they were showing as ada0p1 etc. I was quite happy with the > previous method as I'd fixed the device names via /boot/device.hints an= d > this made it (to me) perfectly human readable without having to use > labels. Is this something that in 8.2 is now hard coded into ZFS? Ie I > am forced to use gptid or disk labelling? Hi, Andy. You can disable gpt/gptid labels via device.hints or loader prompt: kern.geom.label.gptid.enable=3D0 kern.geom.label.gpt.enable=3D0 When they will be disabled ZFS will use just device names. I think :) --=20 WBR, Andrey V. Elsukov --------------enig10BA319D67B3F42A41431416 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBAgAGBQJNbS9WAAoJEAHF6gQQyKF6IfIH/0F89S9CV86aOyUoYcJauQBs omE+MhEpPsXuFC3LO6cI0PTK1vTKbhrbnxGZvqxJhfiDsbfb+R0pfRJjDQxhNNQn IhJ3wMAcer2n9Zl2JX6L7hydAE5pPPFKfVlnpRN7sSb5ik4kxF8j/OUl+vCZPnMM V24new4T9MUuORl4OqJ8gSny5P/71v1kJ8uI2PD7JxLGJ7OichoAmAAO+t211jxl 3wZoCsQomZeN4GxUZO6WB2btEg787xZLIO/O9pvlbiRou6T9SZ0gq+jtxyBo9qMr DPnLE7bz7qF+FfTLyYmMKr9aDtJXqRNTQ+MNEU+Xr7/y9jZ4kAg/MDr1i0Jd674= =BBZ2 -----END PGP SIGNATURE----- --------------enig10BA319D67B3F42A41431416-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 19:13:20 2011 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 8CFB0106566B for ; Tue, 1 Mar 2011 19:13:20 +0000 (UTC) (envelope-from a.smith@ukgrid.net) Received: from mx1.ukgrid.net (mx1.ukgrid.net [89.107.22.36]) by mx1.freebsd.org (Postfix) with ESMTP id 529E08FC16 for ; Tue, 1 Mar 2011 19:13:20 +0000 (UTC) Received: from [89.21.28.38] (port=54221 helo=omicron.ukgrid.net) by mx1.ukgrid.net with esmtp (Exim 4.74; FreeBSD) envelope-from a.smith@ukgrid.net id 1PuV0Y-0001Vr-58; Tue, 01 Mar 2011 19:13:18 +0000 Received: from voip.ukgrid.net (voip.ukgrid.net [89.107.16.9]) by webmail2.ukgrid.net (Horde Framework) with HTTP; Tue, 01 Mar 2011 19:13:18 +0000 Message-ID: <20110301191318.24823v2351epn0w0@webmail2.ukgrid.net> Date: Tue, 01 Mar 2011 19:13:18 +0000 From: a.smith@ukgrid.net To: "Andrey V. Elsukov" References: <20110301165109.15323wik427mxjs4@webmail2.ukgrid.net> <4D6D2F56.6040805@yandex.ru> In-Reply-To: <4D6D2F56.6040805@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) / FreeBSD-8.1 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS disk names and gptid under 8.2-RELEASE 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, 01 Mar 2011 19:13:20 -0000 Quoting "Andrey V. Elsukov" : > Hi, Andy. > > You can disable gpt/gptid labels via device.hints or loader prompt: > > kern.geom.label.gptid.enable=0 > kern.geom.label.gpt.enable=0 > > When they will be disabled ZFS will use just device names. I think :) > > -- > WBR, Andrey V. Elsukov > thanks Andrey, that worked for me! cheers Andy. From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 21:03:26 2011 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 6A13F106564A for ; Tue, 1 Mar 2011 21:03:26 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id BAD848FC15 for ; Tue, 1 Mar 2011 21:03:25 +0000 (UTC) Received: (qmail invoked by alias); 01 Mar 2011 21:03:23 -0000 Received: from adsl-93.109.242.21.tellas.gr (EHLO [192.168.73.192]) [109.242.21.93] by mail.gmx.com (mp-eu001) with SMTP; 01 Mar 2011 22:03:23 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX19fE9hG9jlfp3zs2AmFW21eA6JJKyYZoLHhOl+l4e 7lw4PDO7C9O2Ah Message-ID: <4D6D5F15.4080009@gmx.com> Date: Tue, 01 Mar 2011 23:03:17 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 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 X-Y-GMX-Trusted: 0 Subject: panic: ffx_valloc: dup alloc + SU+J + fsck 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, 01 Mar 2011 21:03:26 -0000 Hello, I am seeing this kernel panic on a su+j ufs. It seems that a su+j aware fsck cannot repair the file system, fsck corrects all fs-problems it finds but the kernel panics on the first write operation. The file system is corrected when a full fsck takes place. This fs lives on a virtual machine and I do have a snapshot of the fs in this problematic state in case someone wants to investigate further. The panic: http://img135.imageshack.us/img135/1111/panicw.png and a backtrace: http://img856.imageshack.us/img856/7516/65759196.png Thanks, Nikos From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 23:03:30 2011 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 39AFC106564A for ; Tue, 1 Mar 2011 23:03:30 +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 923D78FC0C for ; Tue, 1 Mar 2011 23:03:29 +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 p21N3PJZ095633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Mar 2011 01:03:25 +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 p21N3P8I034839; Wed, 2 Mar 2011 01:03:25 +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 p21N3Pkg034838; Wed, 2 Mar 2011 01:03:25 +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: Wed, 2 Mar 2011 01:03:25 +0200 From: Kostik Belousov To: Nikos Vassiliadis Message-ID: <20110301230325.GX78089@deviant.kiev.zoral.com.ua> References: <4D6D5F15.4080009@gmx.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JApREUx0IJoLZdd8" Content-Disposition: inline In-Reply-To: <4D6D5F15.4080009@gmx.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS 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 Subject: Re: panic: ffx_valloc: dup alloc + SU+J + fsck 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, 01 Mar 2011 23:03:30 -0000 --JApREUx0IJoLZdd8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 01, 2011 at 11:03:17PM +0200, Nikos Vassiliadis wrote: > Hello, >=20 > I am seeing this kernel panic on a su+j ufs. It seems that > a su+j aware fsck cannot repair the file system, fsck corrects > all fs-problems it finds but the kernel panics on the first > write operation. The file system is corrected when a full fsck > takes place. This fs lives on a virtual machine and I do have a > snapshot of the fs in this problematic state in case someone > wants to investigate further. >=20 > The panic: > http://img135.imageshack.us/img135/1111/panicw.png >=20 > and a backtrace: > http://img856.imageshack.us/img856/7516/65759196.png >=20 Note that if your fs somehow managed to get a corruption by whatever means, then neither journaling not background fsck can repair it. UFS panic that explicitely mentions fs corruption shall be always followed by full fsck. --JApREUx0IJoLZdd8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk1tez0ACgkQC3+MBN1Mb4hayACfYc+g1FsaOtelr61JNseqNqME Qc4AoJ0UpgVnTdydpi3+RiIDEDAJSNwR =2efO -----END PGP SIGNATURE----- --JApREUx0IJoLZdd8-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 23:45:15 2011 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 EACD71065674 for ; Tue, 1 Mar 2011 23:45:15 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id B22B28FC12 for ; Tue, 1 Mar 2011 23:45:15 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id C73B81076ECE; Tue, 1 Mar 2011 23:28:06 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 34834-04; Tue, 1 Mar 2011 23:27:56 +0000 (GMT) Received: from [90.155.77.76] (unknown [90.155.77.76]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id 0ABD01076E4D; Tue, 1 Mar 2011 23:27:56 +0000 (GMT) From: Dr Josef Karthauser Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 1 Mar 2011 23:27:55 +0000 To: freebsd-fs@freebsd.org Message-Id: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Subject: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2011 23:45:16 -0000 Does it make sense to run zfs on a single disk? I'm setting up a FreeBSD host over at a Xen provider, with a single 80GB = disk image. Ideally I'd like to run ZFS on this system, for snapshot and = flexible creation of filesystems and quotas. Has anyone got any = recommendations for me in this regard? Am I crazy? Joe= From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 00:00:36 2011 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 B5051106564A for ; Wed, 2 Mar 2011 00:00:36 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id 792348FC0A for ; Wed, 2 Mar 2011 00:00:36 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id 2E66D1077158; Wed, 2 Mar 2011 00:00:35 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 42028-05; Wed, 2 Mar 2011 00:00:24 +0000 (GMT) Received: from [90.155.77.76] (unknown [90.155.77.76]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id 8A8E21077152; Wed, 2 Mar 2011 00:00:24 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> Date: Wed, 2 Mar 2011 00:00:24 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> To: Mark Blackman X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 00:00:36 -0000 On 1 Mar 2011, at 23:49, Mark Blackman wrote: >=20 > On 1 Mar 2011, at 23:27, Dr Josef Karthauser wrote: >=20 >> Does it make sense to run zfs on a single disk? >>=20 >> I'm setting up a FreeBSD host over at a Xen provider, with a single = 80GB disk image. Ideally I'd like to run ZFS on this system, for = snapshot and flexible creation of filesystems and quotas. Has anyone got = any recommendations for me in this regard? Am I crazy? >=20 > Not crazy, I do this as well, all the time just to get the management = capabilities and > leave hardware RAID to manage the availability. >=20 > - Mark Any idea what the performance implications are? Can I get away without a = ZIL or ARC and still get a decent performance? Joe= From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 00:12:17 2011 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 BC3E6106566C for ; Wed, 2 Mar 2011 00:12:17 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from relay0.exonetric.net (relay0.exonetric.net [82.138.248.161]) by mx1.freebsd.org (Postfix) with ESMTP id 834348FC1B for ; Wed, 2 Mar 2011 00:12:17 +0000 (UTC) Received: from [192.168.0.7] (unknown [78.86.207.85]) by relay0.exonetric.net (Postfix) with ESMTP id AEB4057009; Tue, 1 Mar 2011 23:49:24 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Mark Blackman In-Reply-To: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> Date: Tue, 1 Mar 2011 23:49:24 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> To: Dr Josef Karthauser X-Mailer: Apple Mail (2.1082) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 00:12:17 -0000 On 1 Mar 2011, at 23:27, Dr Josef Karthauser wrote: > Does it make sense to run zfs on a single disk? >=20 > I'm setting up a FreeBSD host over at a Xen provider, with a single = 80GB disk image. Ideally I'd like to run ZFS on this system, for = snapshot and flexible creation of filesystems and quotas. Has anyone got = any recommendations for me in this regard? Am I crazy? Not crazy, I do this as well, all the time just to get the management = capabilities and leave hardware RAID to manage the availability. - Mark From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 00:14:25 2011 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 567B21065672 for ; Wed, 2 Mar 2011 00:14:25 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by mx1.freebsd.org (Postfix) with ESMTP id 195448FC0C for ; Wed, 2 Mar 2011 00:14:24 +0000 (UTC) Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta14.westchester.pa.mail.comcast.net with comcast id E0C91g0071uE5Es5E0ERnd; Wed, 02 Mar 2011 00:14:25 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta16.westchester.pa.mail.comcast.net with comcast id E0EF1g01Z0PUQVN3c0EKi3; Wed, 02 Mar 2011 00:14:23 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 637BB9B422; Tue, 1 Mar 2011 16:14:14 -0800 (PST) Date: Tue, 1 Mar 2011 16:14:14 -0800 From: Jeremy Chadwick To: Dr Josef Karthauser Message-ID: <20110302001414.GA49147@icarus.home.lan> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 00:14:25 -0000 On Tue, Mar 01, 2011 at 11:27:55PM +0000, Dr Josef Karthauser wrote: > Does it make sense to run zfs on a single disk? Yes, the majority of our Solaris servers (thousands) at my workplace use ZFS on a single disk (particularly the root disk). We do this solely for convenience (ZFS offers a lot of management advantages), and consistency. At home, I also use FreeBSD ZFS with single disks. I still do not trust ZFS-on-root when it comes to FreeBSD. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 00:16:58 2011 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 D7CC41065672 for ; Wed, 2 Mar 2011 00:16:58 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id B824D8FC13 for ; Wed, 2 Mar 2011 00:16:58 +0000 (UTC) Received: from omta18.emeryville.ca.mail.comcast.net ([76.96.30.74]) by qmta06.emeryville.ca.mail.comcast.net with comcast id E0Ek1g0071bwxycA60GyE9; Wed, 02 Mar 2011 00:16:58 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta18.emeryville.ca.mail.comcast.net with comcast id E0Gq1g0190PUQVN8e0GtjV; Wed, 02 Mar 2011 00:16:56 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id BC83C9B422; Tue, 1 Mar 2011 16:16:50 -0800 (PST) Date: Tue, 1 Mar 2011 16:16:50 -0800 From: Jeremy Chadwick To: Dr Josef Karthauser Message-ID: <20110302001650.GB49147@icarus.home.lan> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 00:16:58 -0000 On Wed, Mar 02, 2011 at 12:00:24AM +0000, Dr Josef Karthauser wrote: > On 1 Mar 2011, at 23:49, Mark Blackman wrote: > > > > On 1 Mar 2011, at 23:27, Dr Josef Karthauser wrote: > > > >> Does it make sense to run zfs on a single disk? > >> > >> I'm setting up a FreeBSD host over at a Xen provider, with a single 80GB disk image. Ideally I'd like to run ZFS on this system, for snapshot and flexible creation of filesystems and quotas. Has anyone got any recommendations for me in this regard? Am I crazy? > > > > Not crazy, I do this as well, all the time just to get the management capabilities and > > leave hardware RAID to manage the availability. > > > > - Mark > > Any idea what the performance implications are? Can I get away without a ZIL or ARC and still get a decent performance? Do not disable the ZIL. I hate referring to the Solaris documentation for FreeBSD, but it applies: http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Disabling_the_ZIL_.28Don.27t.29 And you cannot disable the ARC, so just tune it appropriately (which you'll need to do on FreeBSD anyway). In fact, by getting rid of the ARC (as you proposed), you would suffer worse performance than if you had it in use. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 00:46:25 2011 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 5EFE7106566C for ; Wed, 2 Mar 2011 00:46:25 +0000 (UTC) (envelope-from feld@feld.me) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 33C458FC1D for ; Wed, 2 Mar 2011 00:46:24 +0000 (UTC) Received: by iwn33 with SMTP id 33so5321670iwn.13 for ; Tue, 01 Mar 2011 16:46:24 -0800 (PST) Received: by 10.42.247.202 with SMTP id md10mr533083icb.277.1299025108807; Tue, 01 Mar 2011 16:18:28 -0800 (PST) Received: from tech304 (supranet-tech.secure-on.net [66.170.8.18]) by mx.google.com with ESMTPS id uf10sm2639413icb.17.2011.03.01.16.18.27 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 16:18:27 -0800 (PST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-fs@freebsd.org Date: Tue, 01 Mar 2011 18:18:26 -0600 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: User-Agent: Opera Mail/11.01 (FreeBSD) Subject: HAST and volume sizes 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, 02 Mar 2011 00:46:25 -0000 Hi all, There doesn't seem to be any documentation on the effects of having differing volume sizes for HAST. What happens if my MASTER is 1TB and the BACKUP is 1.5TB for example? Does it simply only care about the first 1TB of that volume because that's all the MASTER has? Would it make things easier when we replaced the MASTER's disk with a larger disk? Or will it just resync because HAST would be fresh (like I expect). Thanks, Mark From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 08:57:35 2011 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 9F131106564A for ; Wed, 2 Mar 2011 08:57:35 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 5129F8FC0A for ; Wed, 2 Mar 2011 08:57:35 +0000 (UTC) Received: from outgoing.leidinger.net (p5B32E950.dip.t-dialin.net [91.50.233.80]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id A735B844015; Wed, 2 Mar 2011 09:57:31 +0100 (CET) Received: from webmail.leidinger.net (unknown [IPv6:fd73:10c7:2053:1::2:102]) by outgoing.leidinger.net (Postfix) with ESMTP id 6EB7221F0; Wed, 2 Mar 2011 09:57:28 +0100 (CET) Received: (from www@localhost) by webmail.leidinger.net (8.14.4/8.13.8/Submit) id p228vCLI096409; Wed, 2 Mar 2011 09:57:12 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.ec.europa.eu (pslux.ec.europa.eu [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Wed, 02 Mar 2011 09:57:12 +0100 Message-ID: <20110302095712.129650oisvocoq4o@webmail.leidinger.net> Date: Wed, 02 Mar 2011 09:57:12 +0100 From: Alexander Leidinger To: Dr Josef Karthauser References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> In-Reply-To: <20110302001650.GB49147@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.4) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: A735B844015.A4926 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=1.351, required 6, autolearn=disabled, RDNS_NONE 1.27, TW_ZF 0.08) X-EBL-MailScanner-SpamScore: s X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1299661052.07987@VexDM1/JqGwVK6GB3BHYfg X-EBL-Spam-Status: No Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 08:57:35 -0000 Quoting Jeremy Chadwick (from Tue, 1 Mar 2011 16:16:50 -0800): > On Wed, Mar 02, 2011 at 12:00:24AM +0000, Dr Josef Karthauser wrote: >> On 1 Mar 2011, at 23:49, Mark Blackman wrote: >> > >> > On 1 Mar 2011, at 23:27, Dr Josef Karthauser wrote: >> > >> >> Does it make sense to run zfs on a single disk? >> >> >> >> I'm setting up a FreeBSD host over at a Xen provider, with a >> single 80GB disk image. Ideally I'd like to run ZFS on this system, >> for snapshot and flexible creation of filesystems and quotas. Has >> anyone got any recommendations for me in this regard? Am I crazy? >> > >> > Not crazy, I do this as well, all the time just to get the >> management capabilities and >> > leave hardware RAID to manage the availability. >> > >> > - Mark >> >> Any idea what the performance implications are? Can I get away >> without a ZIL or ARC and still get a decent performance? > > Do not disable the ZIL. I hate referring to the Solaris documentation > for FreeBSD, but it applies: > > http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Disabling_the_ZIL_.28Don.27t.29 > > And you cannot disable the ARC, so just tune it appropriately (which > you'll need to do on FreeBSD anyway). In fact, by getting rid of the > ARC (as you proposed), you would suffer worse performance than if you > had it in use. If you are not satisfied with the performance, you can add a USB memory stick as a cache device to the pool. See the following link to get a glue about what to expect and when it makes sense and when not: http://www.leidinger.net/blog/2010/02/10/making-zfs-faster/ Bye, Alexander. -- To add insult to injury. -- Phaedrus http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 10:10:11 2011 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 1243C1065672 for ; Wed, 2 Mar 2011 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 01DF28FC0A for ; Wed, 2 Mar 2011 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 p22AAA1G083537 for ; Wed, 2 Mar 2011 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 p22AAAHI083536; Wed, 2 Mar 2011 10:10:10 GMT (envelope-from gnats) Date: Wed, 2 Mar 2011 10:10:10 GMT Message-Id: <201103021010.p22AAAHI083536@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Robert Schulze Cc: Subject: Re: kern/154681: [zfs] [panic] panic with FreeBSD-8 STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Schulze List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 10:10:11 -0000 The following reply was made to PR kern/154681; it has been noted by GNATS. From: Robert Schulze To: bug-followup@freebsd.org Cc: Subject: Re: kern/154681: [zfs] [panic] panic with FreeBSD-8 STABLE Date: Wed, 02 Mar 2011 11:02:07 +0100 Hi, bumping that up, the problem still exists with FreeBSD-8.2-STABLE csup'd and built yesterday. In the debugger, I did a "continue", maybe these information are valuable: --- Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x29 fault code = supervisort read data, page not present instruction pointer = 0x20:0xffffffff80173330 stack pointer = 0x28:0xffffff80000b6af0 frame pointer = 0x28:0xffffff80000b6b20 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def 32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (swi2: cambio) [thread pid 12 tid 100024 ] Stopped at camisr_runqueue+0x6e: cmpq %rax,0x28(%rdx%) --- I may provider further debugging information if I get a hint which information and how to do so. with kind regards, Robert Schulze From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 10:29:13 2011 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 C33091065674 for ; Wed, 2 Mar 2011 10:29:13 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id 85D848FC18 for ; Wed, 2 Mar 2011 10:29:13 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id 150351076C80; Wed, 2 Mar 2011 10:29:12 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 35370-06; Wed, 2 Mar 2011 10:29:01 +0000 (GMT) Received: from [90.155.77.76] (unknown [90.155.77.76]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id 4B3A41076CA5; Wed, 2 Mar 2011 10:28:53 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <20110302001650.GB49147@icarus.home.lan> Date: Wed, 2 Mar 2011 10:28:50 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 10:29:13 -0000 On 2 Mar 2011, at 00:16, Jeremy Chadwick wrote: > Do not disable the ZIL. I hate referring to the Solaris documentation > for FreeBSD, but it applies: >=20 > = http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Disab= ling_the_ZIL_.28Don.27t.29 >=20 > And you cannot disable the ARC, so just tune it appropriately (which > you'll need to do on FreeBSD anyway). In fact, by getting rid of the > ARC (as you proposed), you would suffer worse performance than if you > had it in use. I guess I should have been a bit clearer, I mean without any external = devices backing them. Seeing as this is to be running on a VPS/Xen at a = hosting environment I'm not able to add any additional devices. I'm not = memory starved however. Is it madness to use a memory disk? (The = instance in question will have 6gb of ram total to play with.). Joe From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 10:49:55 2011 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 82DC7106566C for ; Wed, 2 Mar 2011 10:49:55 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id 45FF18FC24 for ; Wed, 2 Mar 2011 10:49:54 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id 4BA911076D39; Wed, 2 Mar 2011 10:49:52 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 39060-04; Wed, 2 Mar 2011 10:49:41 +0000 (GMT) Received: from [90.155.77.76] (unknown [90.155.77.76]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id 2F36E1076C80; Wed, 2 Mar 2011 10:49:38 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> Date: Wed, 2 Mar 2011 10:49:37 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <5D6A412F-9701-47A1-AF7E-1F9C20D1A60E@tao.org.uk> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> To: Mark Blackman X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 10:49:55 -0000 On 1 Mar 2011, at 23:49, Mark Blackman wrote: >=20 > On 1 Mar 2011, at 23:27, Dr Josef Karthauser wrote: >=20 >> Does it make sense to run zfs on a single disk? >>=20 >> I'm setting up a FreeBSD host over at a Xen provider, with a single = 80GB disk image. Ideally I'd like to run ZFS on this system, for = snapshot and flexible creation of filesystems and quotas. Has anyone got = any recommendations for me in this regard? Am I crazy? >=20 > Not crazy, I do this as well, all the time just to get the management = capabilities and > leave hardware RAID to manage the availability. >=20 I thought so :). Next thing to work out is how to best deploy this on a xen instance. Joe From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 10:50:13 2011 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 CFA261065686 for ; Wed, 2 Mar 2011 10:50:13 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.net (centre.keltia.net [IPv6:2a01:240:fe5c::41]) by mx1.freebsd.org (Postfix) with ESMTP id 50F988FC18 for ; Wed, 2 Mar 2011 10:50:08 +0000 (UTC) Received: from roberto-al.eurocontrol.fr (aran.keltia.net [88.191.250.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.net (Postfix/TLS) with ESMTPSA id BBBE6DB7A for ; Wed, 2 Mar 2011 11:50:05 +0100 (CET) Date: Wed, 2 Mar 2011 11:50:00 +0100 From: Ollivier Robert To: freebsd-fs@freebsd.org Message-ID: <20110302105000.GA38004@roberto-al.eurocontrol.fr> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7.2 / Dell D820 SMP User-Agent: Mutt/1.5.20 (2009-06-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (keltia.net); Wed, 02 Mar 2011 11:50:06 +0100 (CET) Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 10:50:13 -0000 According to Dr Josef Karthauser: > I guess I should have been a bit clearer, I mean without any external devices backing them. Seeing as this is to be running on a VPS/Xen at a hosting environment I'm not able to add any additional devices. It will work even w/o anything added. I've run an amd64 VM for several months like that. > I'm not memory starved however. Is it madness to use a memory disk? (The instance in question will have 6gb of ram total to play with.). You could use an md device to serve as a cache but with only 6 GB, just let ZFS use whatever it needs. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/ From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 11:31:40 2011 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 8D7F3106564A for ; Wed, 2 Mar 2011 11:31:40 +0000 (UTC) (envelope-from numisemis@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 17E548FC1D for ; Wed, 2 Mar 2011 11:31:39 +0000 (UTC) Received: by bwz12 with SMTP id 12so57310bwz.13 for ; Wed, 02 Mar 2011 03:31:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=btmdVBlSgF2DCs+YMo5Jlt+7jthCgm1efk4VG3BZSLM=; b=RSe5Yf+fxgtHskctRTvRPhQzTOmywonMomA9fCiA3O7z1+eFf8itujUB7dAE7BPODM UpsER+ZKf2KyXfpq5dqyGEfRSIaTC71VazvkKwMZQJWkVEgWd9tOkhLkOUHiA6l2JwLN KijtWgA2TniEqb8mmLQ28IAaOe3RRCMV2rqDU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=nI4W7CZrrqI4CAPmcmRrFzvaaY7JQRS5YBQCjkcstnJKlujyYkPh4EUuCrTHT8kOQJ apq5uXuE7eagiw7mYe5e3JIMlMX35e4wvbgC42N5Eja1QJgoKB/3xla8KvMd+XJlL0ja U3ITApKgEuVw5hkhjslztYOKyyjIK53hjWbvE= MIME-Version: 1.0 Received: by 10.204.26.214 with SMTP id f22mr1155231bkc.100.1299063750053; Wed, 02 Mar 2011 03:02:30 -0800 (PST) Received: by 10.204.115.211 with HTTP; Wed, 2 Mar 2011 03:02:30 -0800 (PST) In-Reply-To: <20110302105000.GA38004@roberto-al.eurocontrol.fr> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302105000.GA38004@roberto-al.eurocontrol.fr> Date: Wed, 2 Mar 2011 12:02:30 +0100 Message-ID: From: =?UTF-8?Q?=C5=A0imun_Mikecin?= To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 11:31:40 -0000 2011/3/2 Ollivier Robert > According to Dr Josef Karthauser: > > I guess I should have been a bit clearer, I mean without any external > devices backing them. Seeing as this is to be running on a VPS/Xen at a > hosting environment I'm not able to add any additional devices. > > It will work even w/o anything added. I've run an amd64 VM for several > months like that. > > > I'm not memory starved however. Is it madness to use a memory disk? (The > instance in question will have 6gb of ram total to play with.). > > You could use an md device to serve as a cache but with only 6 GB, just let > ZFS use whatever it needs. > ZFS cache device (L2ARC) are beneficial when their size can be much larger than size of your ARC cache. If you have much RAM, use it for ARC. L2ARC acts like an extension of ARC, but is slower than ARC. It would really be madness to use that RAM for a memory disk on which you configure a ZFS cache device (L2ARC). From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 12:16:14 2011 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 B3CCC106566B for ; Wed, 2 Mar 2011 12:16:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id 928798FC12 for ; Wed, 2 Mar 2011 12:16:14 +0000 (UTC) Received: from omta24.emeryville.ca.mail.comcast.net ([76.96.30.92]) by qmta05.emeryville.ca.mail.comcast.net with comcast id EC1x1g0021zF43QA5CGEgv; Wed, 02 Mar 2011 12:16:14 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta24.emeryville.ca.mail.comcast.net with comcast id ECGC1g0060PUQVN8kCGCFn; Wed, 02 Mar 2011 12:16:13 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 414169B422; Wed, 2 Mar 2011 04:16:12 -0800 (PST) Date: Wed, 2 Mar 2011 04:16:12 -0800 From: Jeremy Chadwick To: Dr Josef Karthauser Message-ID: <20110302121612.GA61020@icarus.home.lan> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 12:16:14 -0000 On Wed, Mar 02, 2011 at 10:28:50AM +0000, Dr Josef Karthauser wrote: > On 2 Mar 2011, at 00:16, Jeremy Chadwick wrote: > > > Do not disable the ZIL. I hate referring to the Solaris documentation > > for FreeBSD, but it applies: > > > > http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Disabling_the_ZIL_.28Don.27t.29 > > > > And you cannot disable the ARC, so just tune it appropriately (which > > you'll need to do on FreeBSD anyway). In fact, by getting rid of the > > ARC (as you proposed), you would suffer worse performance than if you > > had it in use. > > I guess I should have been a bit clearer, I mean without any external > devices backing them. Seeing as this is to be running on a VPS/Xen at > a hosting environment I'm not able to add any additional devices. I'm > not memory starved however. Is it madness to use a memory disk? (The > instance in question will have 6gb of ram total to play with.). Again: don't disable the ZIL, and adjust the ARC to whatever size you want using a combo of vm.kmem_size and vfs.zfs.arc_max. Make use of the RAM you have available to you. :-) -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 12:24:12 2011 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 9895A106564A for ; Wed, 2 Mar 2011 12:24:12 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id 58DA98FC0C for ; Wed, 2 Mar 2011 12:24:12 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id D98111076DFD; Wed, 2 Mar 2011 12:24:10 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 59978-07; Wed, 2 Mar 2011 12:23:59 +0000 (GMT) Received: from [90.155.77.76] (unknown [90.155.77.76]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id 2F9DB1076C9A; Wed, 2 Mar 2011 12:23:58 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <20110302121612.GA61020@icarus.home.lan> Date: Wed, 2 Mar 2011 12:23:57 +0000 Content-Transfer-Encoding: 7bit Message-Id: <79FD1098-FB13-4F1E-8440-32EF87EC718D@tao.org.uk> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 12:24:12 -0000 On 2 Mar 2011, at 12:16, Jeremy Chadwick wrote: >> >> I guess I should have been a bit clearer, I mean without any external >> devices backing them. Seeing as this is to be running on a VPS/Xen at >> a hosting environment I'm not able to add any additional devices. I'm >> not memory starved however. Is it madness to use a memory disk? (The >> instance in question will have 6gb of ram total to play with.). > > Again: don't disable the ZIL, and adjust the ARC to whatever size you > want using a combo of vm.kmem_size and vfs.zfs.arc_max. Make use of the > RAM you have available to you. :-) Good good :). Thanks, Joe From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 12:40:17 2011 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 EC5DF106566B for ; Wed, 2 Mar 2011 12:40:17 +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 7656C8FC08 for ; Wed, 2 Mar 2011 12:40:17 +0000 (UTC) Received: by bwz12 with SMTP id 12so106239bwz.13 for ; Wed, 02 Mar 2011 04:40:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:organization:references:date :in-reply-to:message-id:user-agent:mime-version:content-type; bh=nfuS/UOvoaxsJYMl8MzHXhth9jwpz3McE+LpRwHY3BU=; b=GH7e7jb/lzY1nRI/Q5SodXaepj0v0ONJHc9RvzjDCQEMfTOT4cTCbjhwuHpdOCPlOI PLr9mZouYUzcVh3VcBUI9m9PR7R/JLhULqI9cFgc4fb3/MTphFA7plV9R1aWDUfKBeUK dnpZ6ShpT4QhHQrzHV9nl86XIjZqJS6rmoWEU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:organization:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=NZ3JQn/c4hfNUgFwHHEOLCfA7B3JJ2JpGUNMlCghwpvEEVXZlaOFn9i1+Pa2FAkk8h wfi24YOrhb1nzWa8DkSnxvH3EdgRzrmHYngC0T/rT91Sr3jrgkN2TS5Y+SUx3PGcH+Kr 9gY3wjiuY70o7zH+iXNIB7rPmBCtEmd5oDK6g= Received: by 10.204.33.5 with SMTP id f5mr4330342bkd.103.1299069616248; Wed, 02 Mar 2011 04:40:16 -0800 (PST) Received: from localhost ([94.27.39.186]) by mx.google.com with ESMTPS id a15sm38360faw.3.2011.03.02.04.40.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Mar 2011 04:40:14 -0800 (PST) From: Mikolaj Golub To: "Mark Felder" Organization: TOA Ukraine References: Date: Wed, 02 Mar 2011 14:40:13 +0200 In-Reply-To: (Mark Felder's message of "Tue, 01 Mar 2011 18:18:26 -0600") Message-ID: <861v2pzoeq.fsf@in138.ua3> 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: HAST and volume sizes 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, 02 Mar 2011 12:40:18 -0000 On Tue, 01 Mar 2011 18:18:26 -0600 Mark Felder wrote: MF> Hi all, MF> There doesn't seem to be any documentation on the effects of having MF> differing volume sizes for HAST. What happens if my MASTER is 1TB and MF> the BACKUP is 1.5TB for example? Does it simply only care about the MF> first 1TB of that volume because that's all the MASTER has? Would it MF> make things easier when we replaced the MASTER's disk with a larger MF> disk? Or will it just resync because HAST would be fresh (like I MF> expect). In hastctl(8) for create command: -m mediasize Size of the smaller provider used as backend stor- age on both nodes. This option can be omitted if node providers have the same size on both sides. So if you have disks of different sizes you have to specify the smallest size on the resource creation. It won't automagically resize when you replace the disk with larger one. The way i see is (if you have A(1Tb), B(1.5Tb) and are replacing A with 1.5Tb): 1) B: start as primary, mount FS; 2) A: after replacing the disk recreate the resource, newfs, mount; 3) copy data form B:/mount to A:/mount manually; 4) B: change role to init, recreate device, switch to secondary. -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 15:57:05 2011 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 EAAE8106566B for ; Wed, 2 Mar 2011 15:57:05 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 3E5238FC12 for ; Wed, 2 Mar 2011 15:57:05 +0000 (UTC) Received: (qmail invoked by alias); 02 Mar 2011 15:57:03 -0000 Received: from adsl-93.109.242.21.tellas.gr (EHLO [192.168.73.192]) [109.242.21.93] by mail.gmx.com (mp-eu004) with SMTP; 02 Mar 2011 16:57:03 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX18fvLgwOkYfKIsDWEym5DZsA6SKwMr5rBESgivxzk K3UEBx2EbILqMX Message-ID: <4D6E68CD.60507@gmx.com> Date: Wed, 02 Mar 2011 17:57:01 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Kostik Belousov References: <4D6D5F15.4080009@gmx.com> <20110301230325.GX78089@deviant.kiev.zoral.com.ua> In-Reply-To: <20110301230325.GX78089@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-fs@freebsd.org Subject: Re: panic: ffx_valloc: dup alloc + SU+J + fsck 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, 02 Mar 2011 15:57:06 -0000 On 3/2/2011 1:03 AM, Kostik Belousov wrote: > Note that if your fs somehow managed to get a corruption by whatever > means, then neither journaling not background fsck can repair it. The corruption was the result of an unrelated to ufs kernel panic. > UFS panic that explicitely mentions fs corruption shall be always > followed by full fsck. That makes sense, a ufs related panic should be followed by a full fsck. And indeed, a full fsck fixes the fs just fine. Thanks, Nikos From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 16:34:48 2011 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 B299B1065694 for ; Wed, 2 Mar 2011 16:34:48 +0000 (UTC) (envelope-from feld@feld.me) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 732F88FC0A for ; Wed, 2 Mar 2011 16:34:47 +0000 (UTC) Received: by vxc34 with SMTP id 34so128494vxc.13 for ; Wed, 02 Mar 2011 08:34:46 -0800 (PST) Received: by 10.52.166.226 with SMTP id zj2mr13830363vdb.295.1299083685964; Wed, 02 Mar 2011 08:34:45 -0800 (PST) Received: from tech304 (supranet-tech.secure-on.net [66.170.8.18]) by mx.google.com with ESMTPS id l6sm54743vcp.38.2011.03.02.08.34.44 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Mar 2011 08:34:44 -0800 (PST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Mikolaj Golub" References: <861v2pzoeq.fsf@in138.ua3> Date: Wed, 02 Mar 2011 10:34:38 -0600 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: In-Reply-To: <861v2pzoeq.fsf@in138.ua3> User-Agent: Opera Mail/11.01 (FreeBSD) Cc: freebsd-fs@freebsd.org Subject: Re: HAST and volume sizes 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, 02 Mar 2011 16:34:48 -0000 On Wed, 02 Mar 2011 06:40:13 -0600, Mikolaj Golub wrote: > So if you have disks of different sizes you have to specify the smallest > size > on the resource creation. Thanks! I somehow missed that when looking at all of the HAST documentation. As a followup question: what exactly is the -m command looking for as far as syntax? It doesn't specify if I have to list it in bytes or if I can do 1T or 1000G, etc. Regards, Mark From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 19:37:37 2011 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 874B4106564A for ; Wed, 2 Mar 2011 19:37:37 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CF9138FC19 for ; Wed, 2 Mar 2011 19:37:36 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id VAA25284; Wed, 02 Mar 2011 21:27:08 +0200 (EET) (envelope-from avg@freebsd.org) Message-ID: <4D6E9A0C.4090704@freebsd.org> Date: Wed, 02 Mar 2011 21:27:08 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101213 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Robert Schulze References: <201103021010.p22AAAHI083536@freefall.freebsd.org> In-Reply-To: <201103021010.p22AAAHI083536@freefall.freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: kern/154681: [zfs] [panic] panic with FreeBSD-8 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, 02 Mar 2011 19:37:37 -0000 on 02/03/2011 12:10 Robert Schulze said the following: > The following reply was made to PR kern/154681; it has been noted by GNATS. > > From: Robert Schulze > To: bug-followup@freebsd.org > Cc: > Subject: Re: kern/154681: [zfs] [panic] panic with FreeBSD-8 STABLE > Date: Wed, 02 Mar 2011 11:02:07 +0100 > > Hi, > > bumping that up, the problem still exists with FreeBSD-8.2-STABLE csup'd > and built yesterday. In the debugger, I did a "continue", maybe these > information are valuable: "bt" command would have been far more useful. Looks like a NULL pointer problem somewhere. > --- > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x29 > fault code = supervisort read data, page not present > instruction pointer = 0x20:0xffffffff80173330 > stack pointer = 0x28:0xffffff80000b6af0 > frame pointer = 0x28:0xffffff80000b6b20 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def 32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (swi2: cambio) > [thread pid 12 tid 100024 ] > Stopped at camisr_runqueue+0x6e: cmpq %rax,0x28(%rdx%) > --- > > I may provider further debugging information if I get a hint which > information and how to do so. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 21:15:09 2011 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 CA7581065672 for ; Wed, 2 Mar 2011 21:15:09 +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 56B518FC18 for ; Wed, 2 Mar 2011 21:15:09 +0000 (UTC) Received: by bwz12 with SMTP id 12so624403bwz.13 for ; Wed, 02 Mar 2011 13:15:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to:date :in-reply-to:message-id:user-agent:mime-version:content-type; bh=x9sT6BQim8jrwcrkt/HknVfJxiMbyzHcvxgzqSb8s00=; b=MXtHYT8Y3rgDH4n8XlcEC+9m9uMmuDohEzn8sC5S5AQt9UbieaGsG/bqOy2WKJVyGy RxKoerLIrm1SUwmk67QRt/Ndnk/1ikndiHddRqTQE+zLe2vWK/gMNEhieI58+q9x1GFY fxv+OJffa5Qbv71XO1rRnj3hjY6Ua/6xs+/rk= 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=jlvg1uBbHS5x4h6kRRL8rkvxioGGDbNSaxYMlEEJ0PFHhUCJ2huP9z8w0Bf5zAVUQe lAWRNljXMyKZ78N15oVGKDDFCNInqT1UeAOEiXKqeoQ/M+eGOHQXsYbuCIcjEAgjuWAL A6QAXvqbGVTi6e5mjB7+0G3iwI1Nv773Vjxzk= Received: by 10.204.169.193 with SMTP id a1mr592891bkz.11.1299100508285; Wed, 02 Mar 2011 13:15:08 -0800 (PST) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id f20sm286012bkf.4.2011.03.02.13.15.07 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Mar 2011 13:15:07 -0800 (PST) From: Mikolaj Golub To: "Mark Felder" References: <861v2pzoeq.fsf@in138.ua3> X-Comment-To: Mark Felder Date: Wed, 02 Mar 2011 23:15:05 +0200 In-Reply-To: (Mark Felder's message of "Wed, 02 Mar 2011 10:34:38 -0600") Message-ID: <86lj0x8bs6.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: HAST and volume sizes 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, 02 Mar 2011 21:15:09 -0000 On Wed, 02 Mar 2011 10:34:38 -0600 Mark Felder wrote: MF> On Wed, 02 Mar 2011 06:40:13 -0600, Mikolaj Golub MF> wrote: >> So if you have disks of different sizes you have to specify the >> smallest size >> on the resource creation. MF> Thanks! I somehow missed that when looking at all of the HAST MF> documentation. As a followup question: what exactly is the -m command MF> looking for as far as syntax? It doesn't specify if I have to list it MF> in bytes or if I can do 1T or 1000G, etc. It is in bytes. Suffixes are not supported. Note, the value should be multiple of 512 (sector size). -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 23:28:08 2011 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 AA5931065676 for ; Wed, 2 Mar 2011 23:28:08 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id 6B58B8FC15 for ; Wed, 2 Mar 2011 23:28:08 +0000 (UTC) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.4/8.14.4) with ESMTP id p22NS5uG089971; Wed, 2 Mar 2011 17:28:07 -0600 (CST) (envelope-from james-freebsd-fs2@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-fs2@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=vKQT+efpa2KltR/y0Zu+58Fl8Msyz3IkQuBdtWfYCrxYTCLJ5LpFyYxHvhPSXRxym CdbhhsTCHZned/NUZIfkFpCgkq8+mPv0NhcSgB3FxIdi4H97Jzj6ZCYkM1wtJLHTImt Ik/6QFzbGe6sd0mBBTio5CHf+wLAiWqPavrbMwk= Message-ID: <4D6ED285.6010105@jrv.org> Date: Wed, 02 Mar 2011 17:28:05 -0600 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Emil Smolenski References: <4D6AAC9A.4000602@jrv.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: [ZFS] Booting from zpool created on 4k-sector drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 23:28:08 -0000 Emil Smolenski wrote: > James asks about disk replacement scenario. In this case you cannot > use device with greater sector size than 2**ashift of the existing > vdev as replacement: > > # diskinfo -v md0 |grep sectorsize > 512 # sectorsize > # zpool create test0 md0 > # zdb test0 |grep ashift > ashift=9 > # diskinfo -v md1.nop |grep sectorsize > 4096 # sectorsize > # zpool replace test0 md0 md1.nop > cannot replace md0 with md1.nop: devices have different sector alignment I was thinking of the capacity of the drive as a problem, not the sector sizes. I wrongly thought gnop consumed space on the drive (like gmirror) and this might make it hard to replace an ashift=12 disk with a 512-byte-sector disk. But this is not the case. It might be a good idea now to start using the gnop trick to force vdev's to use ashift=12 in case disks begin advertising themselvess as 4096-byte-sector. From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 00:31:56 2011 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 11074106564A; Thu, 3 Mar 2011 00:31:56 +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 DB4128FC12; Thu, 3 Mar 2011 00:31:55 +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 p230VtK0021015; Thu, 3 Mar 2011 00:31:55 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p230VtUg021011; Thu, 3 Mar 2011 00:31:55 GMT (envelope-from linimon) Date: Thu, 3 Mar 2011 00:31:55 GMT Message-Id: <201103030031.p230VtUg021011@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/155199: [ext2fs] ext3fs mounted as ext2fs gives I/O errors 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, 03 Mar 2011 00:31:56 -0000 Old Synopsis: ext3fs mounted as ext2 gives I/O errors New Synopsis: [ext2fs] ext3fs mounted as ext2fs gives I/O errors Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Mar 3 00:31:24 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=155199 From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 00:41:31 2011 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 5F992106566B for ; Thu, 3 Mar 2011 00:41:31 +0000 (UTC) (envelope-from jackieit@gmail.com) Received: from mail-vw0-f74.google.com (mail-vw0-f74.google.com [209.85.212.74]) by mx1.freebsd.org (Postfix) with ESMTP id 15C168FC08 for ; Thu, 3 Mar 2011 00:41:30 +0000 (UTC) Received: by vws3 with SMTP id 3so49630vws.1 for ; Wed, 02 Mar 2011 16:41:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=Enita2l0N05EHLohNqhU0lix3kX56KxUgqnkIvq/LDY=; b=ExyTeaRZUqYBlT11dLdaqR4uZYD7mpfA7OB3vtkWJ4T1ODj/dn1zznWNOF7QYwIzKO 4duiGgzT19WZ8TinRdmlU8hG5axbG9dv1dQYfEPBYnsS/nqWjHOxhTswCLML+gSi92eR hyFByeJlYQLVioqCt4FzQxN1stsuxtbgRciwo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dJagv3+j6e82OS5C9Dg6y/umUbGO+YqrP1yc8JP+sG23dSdslwilt8O/igWv+1Q9L5 n+YPsvLh4cYh0kBLYo/Qur8wR3DfSh+rwhLCZTtPpZSikZQCCF+oL3OJYk5r9zyvQEmw Fb7FJt94M2cMKiWy4+bJgSdHA6hh2poqQNq64= MIME-Version: 1.0 Received: by 10.52.89.34 with SMTP id bl2mr723268vdb.239.1299111470248; Wed, 02 Mar 2011 16:17:50 -0800 (PST) Date: Wed, 2 Mar 2011 16:17:50 -0800 Message-ID: From: jackie wang To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: jackie wang wants to chat 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, 03 Mar 2011 00:41:31 -0000 ----------------------------------------------------------------------- jackie wang wants to stay in better touch using some of Google's coolest new products. If you already have Gmail or Google Talk, visit: http://mail.google.com/mail/b-3ff662238b-b6996bee36-cmItq8RQ0K-Xzwffz3NXF2-hGLo You'll need to click this link to be able to chat with jackie wang. To get Gmail - a free email account from Google with over 2,800 megabytes of storage - and chat with jackie wang, visit: http://mail.google.com/mail/a-3ff662238b-b6996bee36-cmItq8RQ0K-Xzwffz3NXF2-hGLo Gmail offers: - Instant messaging right inside Gmail - Powerful spam protection - Built-in search for finding your messages and a helpful way of organizing emails into "conversations" - No pop-up ads or untargeted banners - just text ads and related information that are relevant to the content of your messages All this, and its yours for free. But wait, there's more! By opening a Gmail account, you also get access to Google Talk, Google's instant messaging service: http://www.google.com/talk/ Google Talk offers: - Web-based chat that you can use anywhere, without a download - A contact list that's synchronized with your Gmail account - Free, high quality PC-to-PC voice calls when you download the Google Talk client We're working hard to add new features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making our products even better! Thanks, The Google Team To learn more about Gmail and Google Talk, visit: http://mail.google.com/mail/help/about.html http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser). From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 04:20:10 2011 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 0A9AD106566B for ; Thu, 3 Mar 2011 04:20:10 +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 EB8648FC0C for ; Thu, 3 Mar 2011 04:20:09 +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 p234K7Ye032717 for ; Thu, 3 Mar 2011 04:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p234K7Fj032716; Thu, 3 Mar 2011 04:20:07 GMT (envelope-from gnats) Date: Thu, 3 Mar 2011 04:20:07 GMT Message-Id: <201103030420.p234K7Fj032716@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: "Pedro F. Giffuni" Cc: Subject: Re: kern/155199: [ext2fs] ext3fs mounted as ext2fs gives I/O errors 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: Thu, 03 Mar 2011 04:20:10 -0000 The following reply was made to PR kern/155199; it has been noted by GNATS. From: "Pedro F. Giffuni" To: bug-followup@FreeBSD.org, cheeky.m@live.com Cc: Subject: Re: kern/155199: [ext2fs] ext3fs mounted as ext2fs gives I/O errors Date: Wed, 2 Mar 2011 20:04:40 -0800 (PST) Hello; Some notes.. from your original posting it seemed like the symlink issue was due to our lack of support for fast symlinks. Those may be interesting to implement. (I won't volunteer though). The unreadable files are something new. Perhaps they have extended attributes or ACLs? We don't support those and they would be difficult to support because of implementation differences with our native EAs. cheers, Pedro. From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 05:00:23 2011 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 E2F00106564A for ; Thu, 3 Mar 2011 05:00:23 +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 CF79F8FC16 for ; Thu, 3 Mar 2011 05:00:23 +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 p2350Nvj070400 for ; Thu, 3 Mar 2011 05:00:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p2350NS7070391; Thu, 3 Mar 2011 05:00:23 GMT (envelope-from gnats) Date: Thu, 3 Mar 2011 05:00:23 GMT Message-Id: <201103030500.p2350NS7070391@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Roger Hammerstein Cc: Subject: RE: kern/155199: [ext2fs] ext3fs mounted as ext2fs gives I/O errors X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roger Hammerstein List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2011 05:00:24 -0000 The following reply was made to PR kern/155199; it has been noted by GNATS. From: Roger Hammerstein To: , Cc: Subject: RE: kern/155199: [ext2fs] ext3fs mounted as ext2fs gives I/O errors Date: Wed, 2 Mar 2011 23:43:18 -0500 --_6f81a817-3b1a-463b-b71c-49f0f91b67a5_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you for the followup. > Some notes.. from your original posting it seemed like > the symlink issue was due to our lack of support for > fast symlinks.=20 At the time=2C I thought it the filesystem was ext2 and was not expecting those errors. I was doing directory listings across the filesystem=2C and the log was showing the g_vfs_done errors. I tracked the log entries to traversals of the symlinks=2C and then posted. I hadn't done much individual file accesses at the time. > The unreadable files are something new. Perhaps they > have extended attributes or ACLs? We don't support > those and they would be difficult to support because > of implementation differences with our native EAs. Nothing special on the files (that I know of). They don't have any acls or= =20 extended attributes. Errors occur on mnay different types of files=2C READMEs=2C jpgs=2C mp3s=2C txts=2C gifs. Sometimes in a single directory=2C the first couple of files will read just fine=2C and the rest will give errors. = --_6f81a817-3b1a-463b-b71c-49f0f91b67a5_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you for the followup.
>=3B Some notes.. from your original posti= ng it seemed like
>=3B the symlink issue was due to our lack of suppor= t for
>=3B fast symlinks.

At the time=2C I thought it the file= system was ext2 and was not expecting
those errors.
I was doing direc= tory listings across the filesystem=2C and the
log was showing the g_vfs= _done errors.
I tracked the log entries to traversals of the symlinks=2C= and then posted.

I hadn't done much individual file accesses at the= time.

>=3B The unreadable files are something new. Perhaps they>=3B have extended attributes or ACLs? We don't support
>=3B those= and they would be difficult to support because
>=3B of implementation= differences with our native EAs.

Nothing special on the files (that= I know of). =3B They don't have any acls or
extended attributes.&n= bsp=3B =3B Errors occur on mnay different
types of files=2C READMEs= =2C jpgs=2C mp3s=2C txts=2C gifs.
Sometimes in a single directory=2C the= first couple of files
will read just fine=2C and the rest will give err= ors.

= --_6f81a817-3b1a-463b-b71c-49f0f91b67a5_-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 12:01:35 2011 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 20F89106566C; Thu, 3 Mar 2011 12:01:35 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.29.7]) by mx1.freebsd.org (Postfix) with ESMTP id 8C08B8FC23; Thu, 3 Mar 2011 12:01:34 +0000 (UTC) Received: from [78.34.179.69] (helo=r500.local) by smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1Pv7Dp-0001AN-4O; Thu, 03 Mar 2011 13:01:33 +0100 Date: Thu, 3 Mar 2011 13:01:30 +0100 From: Fabian Keil To: Alexander Leidinger Message-ID: <20110303130130.29a066a1@r500.local> In-Reply-To: <20110228214847.0000078c@unknown> References: <20110227202957.GD1992@garage.freebsd.pl> <20110228192129.119cac0c@r500.local> <20110228214847.0000078c@unknown> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; amd64-portbld-freebsd9.0) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/GTZoCaocHGHA_suBK/lf3JR"; protocol="application/pgp-signature" X-Df-Sender: 775067 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: HEADS UP: ZFSv28 is in! 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, 03 Mar 2011 12:01:35 -0000 --Sig_/GTZoCaocHGHA_suBK/lf3JR Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Alexander Leidinger wrote: > On Mon, 28 Feb 2011 19:21:29 +0100 Fabian Keil > wrote: >=20 > > Pawel Jakub Dawidek wrote: > >=20 > > > I just committed ZFSv28 to HEAD. > >=20 > > I updated the system without removing the tuning for ZFSv15 > > first, and somehow this completely messed up the performance. > > Booting the system took more than ten minutes and even once > > it was up it was next to unresponsive. > >=20 > > I'm not sure which sysctl was to blame, but after removing > > all but vfs.zfs.arc_max=3D"800M" and rebooting, the problem > > was gone. >=20 > When you add the tuning back, does it take minutes again to boot? If > not, I assume it was cleaning up some leftovers the old version was not > able to cleanup. I haven't tried that yet, but as I didn't upgrade the system's storage pool I don't think ZFS is supposed to do any such clean-ups. I also don't see any similar issues when importing other v15 pools. Fabian --Sig_/GTZoCaocHGHA_suBK/lf3JR Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAk1vgx4ACgkQBYqIVf93VJ2xRACggaiNusIyN5wOVSj1J4vIu+8R RwoAoMtO/24s2dJxEjujCEYDr9VxdA7G =89QC -----END PGP SIGNATURE----- --Sig_/GTZoCaocHGHA_suBK/lf3JR-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 12:52:13 2011 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 BA0CB106566B; Thu, 3 Mar 2011 12:52:13 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 6C8888FC08; Thu, 3 Mar 2011 12:52:13 +0000 (UTC) Received: from outgoing.leidinger.net (p5B32EB58.dip.t-dialin.net [91.50.235.88]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 02A53844015; Thu, 3 Mar 2011 13:52:06 +0100 (CET) Received: from webmail.leidinger.net (unknown [IPv6:fd73:10c7:2053:1::2:102]) by outgoing.leidinger.net (Postfix) with ESMTP id B2AD42426; Thu, 3 Mar 2011 13:52:02 +0100 (CET) Received: (from www@localhost) by webmail.leidinger.net (8.14.4/8.13.8/Submit) id p23CpleD022635; Thu, 3 Mar 2011 13:51:47 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.ec.europa.eu (pslux.ec.europa.eu [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Thu, 03 Mar 2011 13:51:47 +0100 Message-ID: <20110303135147.20096fpe1ntz75k8@webmail.leidinger.net> Date: Thu, 03 Mar 2011 13:51:47 +0100 From: Alexander Leidinger To: Fabian Keil References: <20110227202957.GD1992@garage.freebsd.pl> <20110228192129.119cac0c@r500.local> <20110228214847.0000078c@unknown> <20110303130130.29a066a1@r500.local> In-Reply-To: <20110303130130.29a066a1@r500.local> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.4) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 02A53844015.A5B6F X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=1.274, required 6, autolearn=disabled, RDNS_NONE 1.27) X-EBL-MailScanner-SpamScore: s X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1299761529.2035@9Ov1BlmNLtBzEt2VPIk/JA X-EBL-Spam-Status: No Cc: freebsd-fs@FreeBSD.org, Pawel, freebsd-current@FreeBSD.org, Dawidek Subject: Re: HEADS UP: ZFSv28 is in! 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, 03 Mar 2011 12:52:13 -0000 Quoting Fabian Keil (from Thu, 3 Mar 2011 13:01:30 +0100): > Alexander Leidinger wrote: > >> On Mon, 28 Feb 2011 19:21:29 +0100 Fabian Keil >> wrote: >> >> > Pawel Jakub Dawidek wrote: >> > >> > > I just committed ZFSv28 to HEAD. >> > >> > I updated the system without removing the tuning for ZFSv15 >> > first, and somehow this completely messed up the performance. >> > Booting the system took more than ten minutes and even once >> > it was up it was next to unresponsive. >> > >> > I'm not sure which sysctl was to blame, but after removing >> > all but vfs.zfs.arc_max="800M" and rebooting, the problem >> > was gone. >> >> When you add the tuning back, does it take minutes again to boot? If >> not, I assume it was cleaning up some leftovers the old version was not >> able to cleanup. > > I haven't tried that yet, but as I didn't upgrade the system's > storage pool I don't think ZFS is supposed to do any such clean-ups. AFAIK the new code knows how to remove some superfluous parts in your pool (no matter at which version the pool is), which the old code just skipped over. Such leftovers may not be in all pools, they show up just in some use cases. For this reason I asked to verify by adding the tuning back to this system (if possible). If it is not a production-like system which does not accept downtime, this verification consumes less resources than sending out a developer hunting for a problem which may not even exist. Bye, Alexander. -- A short cut is the longest distance between two points. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 14:51:24 2011 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 9CC4D1065676 for ; Thu, 3 Mar 2011 14:51:24 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 63C038FC1B for ; Thu, 3 Mar 2011 14:51:24 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id p23EpKD5007524; Thu, 3 Mar 2011 08:51:21 -0600 (CST) Date: Thu, 3 Mar 2011 08:51:20 -0600 (CST) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Fabian Keil In-Reply-To: <20110303130130.29a066a1@r500.local> Message-ID: References: <20110227202957.GD1992@garage.freebsd.pl> <20110228192129.119cac0c@r500.local> <20110228214847.0000078c@unknown> <20110303130130.29a066a1@r500.local> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Thu, 03 Mar 2011 08:51:21 -0600 (CST) Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: HEADS UP: ZFSv28 is in! 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, 03 Mar 2011 14:51:24 -0000 On Thu, 3 Mar 2011, Fabian Keil wrote: >> >> When you add the tuning back, does it take minutes again to boot? If >> not, I assume it was cleaning up some leftovers the old version was not >> able to cleanup. > > I haven't tried that yet, but as I didn't upgrade the system's > storage pool I don't think ZFS is supposed to do any such clean-ups. The new code likely does things like search for and reclaim leaked space. Older zfs versions had some some bugs which could result in failing to reclaim space after a large file is deleted. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 19:23:47 2011 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 0946E106566B; Thu, 3 Mar 2011 19:23:47 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.31]) by mx1.freebsd.org (Postfix) with ESMTP id 8B2968FC0C; Thu, 3 Mar 2011 19:23:46 +0000 (UTC) Received: from [78.34.156.215] (helo=r500.local) by smtprelay04.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1PvE7k-0002Pi-Ha; Thu, 03 Mar 2011 20:23:44 +0100 Date: Thu, 3 Mar 2011 20:23:39 +0100 From: Fabian Keil To: Alexander Leidinger Message-ID: <20110303202339.585b0c0b@r500.local> In-Reply-To: <20110303135147.20096fpe1ntz75k8@webmail.leidinger.net> References: <20110227202957.GD1992@garage.freebsd.pl> <20110228192129.119cac0c@r500.local> <20110228214847.0000078c@unknown> <20110303130130.29a066a1@r500.local> <20110303135147.20096fpe1ntz75k8@webmail.leidinger.net> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; amd64-portbld-freebsd9.0) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/rAZvbCaHCnRG73fv8zdj+23"; protocol="application/pgp-signature" X-Df-Sender: 775067 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: HEADS UP: ZFSv28 is in! 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, 03 Mar 2011 19:23:47 -0000 --Sig_/rAZvbCaHCnRG73fv8zdj+23 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Alexander Leidinger wrote: > Quoting Fabian Keil (from Thu, 3 Mar =20 > 2011 13:01:30 +0100): >=20 > > Alexander Leidinger wrote: > > > >> On Mon, 28 Feb 2011 19:21:29 +0100 Fabian Keil > >> wrote: > >> > >> > Pawel Jakub Dawidek wrote: > >> > > >> > > I just committed ZFSv28 to HEAD. > >> > > >> > I updated the system without removing the tuning for ZFSv15 > >> > first, and somehow this completely messed up the performance. > >> > Booting the system took more than ten minutes and even once > >> > it was up it was next to unresponsive. > >> > > >> > I'm not sure which sysctl was to blame, but after removing > >> > all but vfs.zfs.arc_max=3D"800M" and rebooting, the problem > >> > was gone. > >> > >> When you add the tuning back, does it take minutes again to boot? If > >> not, I assume it was cleaning up some leftovers the old version was not > >> able to cleanup. > > > > I haven't tried that yet, but as I didn't upgrade the system's > > storage pool I don't think ZFS is supposed to do any such clean-ups. >=20 > AFAIK the new code knows how to remove some superfluous parts in your =20 > pool (no matter at which version the pool is), which the old code just =20 > skipped over. Such leftovers may not be in all pools, they show up =20 > just in some use cases. For this reason I asked to verify by adding =20 > the tuning back to this system (if possible). I don't have an exact list of sysctls I used earlier, but after commenting in all the zfs sysctls in loader.conf (some of which must have been commented out for quite some time) the problem was back. I interrupted the boot process after 14 minutes at which point the ezjail rc script was running for several minutes already, but still busy with the first jail. Usually this takes only a few seconds. The sysctls used were: #vfs.zfs.txg.timeout=3D5 Seems to be the default now. # vfs.zfs.zil_disable=3D1 No longer supported. # vfs.zfs.prefetch_disable=3D0 The default seems to be 1. # vfs.zfs.write_limit_override=3D15 Clearly the value makes no sense, so this may not have been active at the time of the update. I had a back-ported patch to add the sysctl, so at least in theory it should have caused problems with v15, too, unless there was a sanity check to ignore obviously incorrect values. The auto-tuned write-limit values are: vfs.zfs.write_limit_max: 258863616 vfs.zfs.write_limit_min: 33554432 # vfs.zfs.vdev.max_pending=3D15 The auto-tuned value is 10. vfs.zfs.arc_max=3D"800M" # vfs.zfs.arc_min=3D"500M" # vfs.zfs.vdev.cache.size=3D"5M" The auto-tuned value is 10485760 which seems close enough. # vfs.zfs.txg.synctime=3D1 This sysctl doesn't seem to exist (anymore). #vfs.zfs.cache_flush_disable=3D1 The default is 0. # vfs.zfs.txg.write_limit_override=3D134217728 Doesn't seem to exist (anymore) either. #vfs.zfs.vdev.max_pending=3D2 #vfs.zfs.vdev.min_pending=3D1 The auto-tuned values are vfs.zfs.vdev.min_pending: 4 vfs.zfs.vdev.max_pending: 10 > If it is not a production-like system which does not accept downtime, =20 > this verification consumes less resources than sending out a developer =20 > hunting for a problem which may not even exist. It wasn't my intention to send anyone hunting. Fabian --Sig_/rAZvbCaHCnRG73fv8zdj+23 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAk1v6sEACgkQBYqIVf93VJ1ryACgsaHxQhqQqQLB594YBLCtmZlS K/kAn0Cf3I6HqwPrhQJBE/+t+E8H+gz5 =WKq1 -----END PGP SIGNATURE----- --Sig_/rAZvbCaHCnRG73fv8zdj+23-- From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 01:51:14 2011 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 E1EF3106566B for ; Fri, 4 Mar 2011 01:51:14 +0000 (UTC) (envelope-from baitisj@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6766E8FC13 for ; Fri, 4 Mar 2011 01:51:14 +0000 (UTC) Received: by ywf9 with SMTP id 9so675480ywf.13 for ; Thu, 03 Mar 2011 17:51:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=jfgfB5pJq7i0vXfbDeELACK/Ww4ed7Bf0EH9G9RNGnw=; b=mcN4YDbpuyn+9dzT4yCyp70lOXrcQx8Vy7v5hUO61Ut0tcTJWpvlGWM5wkphHDDgEU 85sD29nFb7WAVloA5htbDy14UGSS1bV47lZ4xFP5uoQseT8gx/sWiBlPaZQ8TP947TA4 DgVeUZ1oB5XoSycM7tyl0APU2a9r04WKeeG1w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=ss0BLTu8WB2AwbygdAwJa+4sKZgyH6Pli/ez2IKDvU7z2h2wT9AKLlOzmmgQti+qga GlOfULOxVsLPigh3xM/EW4uCNYKpbgBRt2CwnGinFdxTS81fV2sBsSa+oBPnlxuagFag nYVMH8oCsetzIZpn2LwwHSnzVleqq6oGneesM= Received: by 10.150.92.7 with SMTP id p7mr2692725ybb.208.1299201662098; Thu, 03 Mar 2011 17:21:02 -0800 (PST) MIME-Version: 1.0 Sender: baitisj@gmail.com Received: by 10.151.49.21 with HTTP; Thu, 3 Mar 2011 17:20:42 -0800 (PST) From: Jeffrey Baitis Date: Thu, 3 Mar 2011 17:20:42 -0800 X-Google-Sender-Auth: FxiohSY0h_bqDi0msXlkFI5B_fc Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Experience testing recent -mm ZFS patches: WARNING: releng-8.2-zfsv28-20110301 will eat your cookie 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, 04 Mar 2011 01:51:15 -0000 Caveat: I have been using FreeBSD for five days now (shun the noob). That stated, I built world using http://people.freebsd.org/~mm/patches/zfs/v28/releng-8.2-zfsv28-20110301-nopython.patch.xz and http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20110301-nopython.patch.xz. I am running a single-disk ZFS root filesystem (version 15). My make.conf contains CPUTYPE?=athlon64, machine has 4GB RAM. After extremely extensive testing, the RELENG_8 kernel is working well thus far (uptime 4:36), cvsup performed last night. RELENG_8_2 caused processes on the system to grind to an unrecoverable halt. As soon as I noticed my skype application taking 100% CPU time, my next attempt was to launch firefox. truss -f firefox revealed that the process hung after a stat call to a specific file: 67894: stat("/usr/local/etc/fonts/fonts.conf",{ mode=-rwxr-xr-x ,inode=240214,size=5223,blksize=5632 }) = 0 (0x0) As an experiment, I performed the following: ls /usr/local/etc/fonts/fonts.conf This command hung immediately and, like my other processes, was un-killable. Any attempts to stat the inode in question resulted in further cookie-eating. In order to rectify the issue, the machine required reboot; of course, rebooting was impossible without pulling the plug. Please let me know if further information / test cases executed on the RELENG_8_2 patched kernel. Regards, Jeff From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 09:17:02 2011 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 C4D68106564A for ; Fri, 4 Mar 2011 09:17:02 +0000 (UTC) (envelope-from canevet@embl.fr) Received: from emblmta1.embl.fr (emblmta1.embl.fr [193.49.43.176]) by mx1.freebsd.org (Postfix) with ESMTP id 777808FC0C for ; Fri, 4 Mar 2011 09:16:57 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.62,263,1297033200"; d="asc'?png'150?scan'150,208,150";a="1305850" Received: from unknown (HELO [172.26.15.11]) ([172.26.15.11]) by emblmta1.embl.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 04 Mar 2011 10:16:56 +0100 From: =?ISO-8859-1?Q?Micka=EBl_Can=E9vet?= To: freebsd-fs@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-b+Ay8tYp1UNUFZDYauXt" Date: Fri, 04 Mar 2011 09:23:05 +0100 Message-ID: <1299226985.3391.18.camel@pc286.embl.fr> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 09:17:02 -0000 --=-b+Ay8tYp1UNUFZDYauXt Content-Type: multipart/mixed; boundary="=-2veXdhvUEj85EjdT/NE6" --=-2veXdhvUEj85EjdT/NE6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, I know there is a lot of threads about "kmem_map too small" problems on former versions of FreeBSD with ZFS, but on the wiki (http://wiki.freebsd.org/ZFSTuningGuide) it is said that "FreeBSD 7.2+ has improved kernel memory allocation strategy and no tuning may be necessary on systems with more than 2 GB of RAM." I have a 64bits machine with 16GB of RAM with FreeBSD 8.2-RELEASE and no tuning: # sysctl -a | grep -e "vm.kmem_size_max:" -e "vm.kmem_size:" -e "vfs.zfs.arc_max:" vm.kmem_size_max: 329853485875 vm.kmem_size: 16624558080 vfs.zfs.arc_max: 15550816256 This morning this server crashed with: panic: kmem_malloc(1048576): kmem_map too small: 8658309120 total allocated At that time I was doing a quite huge "zfs send | zfs recv" to another server, this is maybe the origin of the memory consumption. Does anybody knows why the kernel crashed at around 8GB allocated while vm.kmem_size and vfs.zfs.arc_max are set at around 16GB and vm.kmem_size_max is set at around 300GB (is it not a little big huge by the way ?). Should I increase this values ? Thanks a lot for your answers. Micka=C3=ABl --=-2veXdhvUEj85EjdT/NE6-- --=-b+Ay8tYp1UNUFZDYauXt Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAk1woWkACgkQZjBmN5Hi/YZDzgCgpzbiFO0PMm2RIwvMQZLEdM6A fsgAn3yOd3ASQ06wagVqoUWQsXz2h/fu =kQcD -----END PGP SIGNATURE----- --=-b+Ay8tYp1UNUFZDYauXt-- From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 09:35:04 2011 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 2567F106566B for ; Fri, 4 Mar 2011 09:35:04 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.net (centre.keltia.net [IPv6:2a01:240:fe5c::41]) by mx1.freebsd.org (Postfix) with ESMTP id C6E7A8FC0A for ; Fri, 4 Mar 2011 09:35:03 +0000 (UTC) Received: from roberto-al.eurocontrol.fr (aran.keltia.net [88.191.250.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.net (Postfix/TLS) with ESMTPSA id 9AF66DDED for ; Fri, 4 Mar 2011 10:35:01 +0100 (CET) Date: Fri, 4 Mar 2011 10:34:52 +0100 From: Ollivier Robert To: freebsd-fs@freebsd.org Message-ID: <20110304093451.GA43078@roberto-al.eurocontrol.fr> References: <1299226985.3391.18.camel@pc286.embl.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1299226985.3391.18.camel@pc286.embl.fr> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7.2 / Dell D820 SMP User-Agent: Mutt/1.5.20 (2009-06-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (keltia.net); Fri, 04 Mar 2011 10:35:01 +0100 (CET) Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 09:35:04 -0000 According to Mickaël Canévet: > panic: kmem_malloc(1048576): kmem_map too small: 8658309120 total > allocated I'd use vm.kmem_size="32G" (i.e. twice your RAM) and that's it. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/ From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 09:48:57 2011 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 8B3E1106566B for ; Fri, 4 Mar 2011 09:48:57 +0000 (UTC) (envelope-from canevet@embl.fr) Received: from emblmta1.embl.fr (emblmta1.embl.fr [193.49.43.176]) by mx1.freebsd.org (Postfix) with ESMTP id 095568FC12 for ; Fri, 4 Mar 2011 09:48:56 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.62,263,1297033200"; d="asc'?scan'208";a="1306199" Received: from unknown (HELO [172.26.15.11]) ([172.26.15.11]) by emblmta1.embl.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 04 Mar 2011 10:48:55 +0100 From: =?ISO-8859-1?Q?Micka=EBl_Can=E9vet?= To: freebsd-fs@freebsd.org In-Reply-To: 1299226985.3391.18.camel@pc286.embl.fr Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-apj153HSuq6CQo7G05bJ" Date: Fri, 04 Mar 2011 10:48:53 +0100 Message-ID: <1299232133.18671.3.camel@pc286.embl.fr> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Cc: Subject: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 09:48:57 -0000 --=-apj153HSuq6CQo7G05bJ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > I'd use vm.kmem_size=3D"32G" (i.e. twice your RAM) and that's it. Should I also increase vfs.zfs.arc_max ? Do you have any idea why the kernel panicked at only 8GB allocated ? Thank you --=-apj153HSuq6CQo7G05bJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAk1wtYIACgkQZjBmN5Hi/YZ6GgCfUphGJjupb//ZHuxHao4NCm2B pj4AnRvgcYFnMTedouaPnsGkFrMc/Ayz =n+mQ -----END PGP SIGNATURE----- --=-apj153HSuq6CQo7G05bJ-- From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 10:05:20 2011 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 66EFB1065674 for ; Fri, 4 Mar 2011 10:05:20 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id 11BFC8FC1E for ; Fri, 4 Mar 2011 10:05:19 +0000 (UTC) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta09.westchester.pa.mail.comcast.net with comcast id Ey5L1g0010SCNGk59y5L7r; Fri, 04 Mar 2011 10:05:20 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta09.westchester.pa.mail.comcast.net with comcast id Ey5J1g00L0PUQVN3Vy5K0q; Fri, 04 Mar 2011 10:05:19 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 6370E9B422; Fri, 4 Mar 2011 02:05:17 -0800 (PST) Date: Fri, 4 Mar 2011 02:05:17 -0800 From: Jeremy Chadwick To: =?iso-8859-1?Q?Micka=EBl_Can=E9vet?= Message-ID: <20110304100517.GA23249@icarus.home.lan> References: <1299232133.18671.3.camel@pc286.embl.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1299232133.18671.3.camel@pc286.embl.fr> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 10:05:20 -0000 On Fri, Mar 04, 2011 at 10:48:53AM +0100, Mickaël Canévet wrote: > > I'd use vm.kmem_size="32G" (i.e. twice your RAM) and that's it. > > Should I also increase vfs.zfs.arc_max ? You should adjust vm.kmem_size, but not vm.kmem_size_max. You can adjust vfs.zfs.arc_max to basically ensure system stability. This thread is acting as evidence that there are probably edge cases where the kmem too small panic can still happen despite the limited ARC maximum defaults. For a 16GB system, I'd probably use these settings: vm.kmem_size="16384M" vfs.zfs.arc_max="13312M" I would also use these two settings: # Disable ZFS prefetching # http://southbrain.com/south/2008/04/the-nightmare-comes-slowly-zfs.html # Increases overall speed of ZFS, but when disk flushing/writes occur, # system is less responsive (due to extreme disk I/O). # NOTE: Systems with 8GB of RAM or more have prefetch enabled by # default. vfs.zfs.prefetch_disable="1" # Decrease ZFS txg timeout value from 30 (default) to 5 seconds. This # should increase throughput and decrease the "bursty" stalls that # happen during immense I/O with ZFS. # http://lists.freebsd.org/pipermail/freebsd-fs/2009-December/007343.html # http://lists.freebsd.org/pipermail/freebsd-fs/2009-December/007355.html vfs.zfs.txg.timeout="5" The advice in the Wiki is outdated, especially for 8.2-RELEASE. Best not to follow it as of this writing. > Do you have any idea why the kernel panicked at only 8GB allocated ? I do not. A kernel developer will have to comment on that. Please attempt to reproduce the problem. If you can reproduce it reliably, this will greatly help kernel developers tracking down the source of the problem. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 10:56:11 2011 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 59ACE106566C for ; Fri, 4 Mar 2011 10:56:11 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 035868FC16 for ; Fri, 4 Mar 2011 10:56:10 +0000 (UTC) Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta10.westchester.pa.mail.comcast.net with comcast id EysY1g0030xGWP85AywBZ1; Fri, 04 Mar 2011 10:56:11 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta12.westchester.pa.mail.comcast.net with comcast id Eyw91g00r0PUQVN3YywADw; Fri, 04 Mar 2011 10:56:10 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 4C0F89B422; Fri, 4 Mar 2011 02:56:08 -0800 (PST) Date: Fri, 4 Mar 2011 02:56:08 -0800 From: Jeremy Chadwick To: Matthias Gamsjager Message-ID: <20110304105608.GA23887@icarus.home.lan> References: <1299232133.18671.3.camel@pc286.embl.fr> <20110304100517.GA23249@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, =?iso-8859-1?Q?Micka=EBl_Can=E9vet?= Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 10:56:11 -0000 On Fri, Mar 04, 2011 at 11:30:04AM +0100, Matthias Gamsjager wrote: > > # Disable ZFS prefetching > > # http://southbrain.com/south/2008/04/the-nightmare-comes-slowly-zfs.html > > # Increases overall speed of ZFS, but when disk flushing/writes occur, > > # system is less responsive (due to extreme disk I/O). > > # NOTE: Systems with 8GB of RAM or more have prefetch enabled by > > # default. > > vfs.zfs.prefetch_disable="1" > > > > > > I wonder if this is still the case since the website you referring to was > from 2008 and I guess a lot has changed since then. Yes, this is still the case. The website I linked in the comment is dated, but still applicable in my experience (at least to FreeBSD). On Solaris it doesn't appear applicable (every x86 Solaris 10 system at my workplace uses ZFS exclusively, and we do not have to disable prefetching; the performance is fine). We do have one Sol10 system though that's IMAP-centric, uses a 3-disk raidz1, but has severe performance (I/O) issues sometimes, but I'm chalking that up to being it running Dovecot 1.0.0. Circling back to FreeBSD: if you want further confirmations, you can read about my findings with 8.0-RC1 here -- scroll down to about the half way mark: http://koitsu.wordpress.com/2009/10/12/testing-out-freebsd-8-0-rc1/ As far as I can tell from following commits since 8.0-RC1, nothing has changed about the prefetch mechanism in FreeBSD (developers please correct me if I'm wrong here). I should also note that I think my "# NOTE:" comment is inaccurate; I believe it should read "Systems with more than 4GB usable RAM default to having prefetch enabled". I'll have to update my /boot/loader.conf files. > For example I get horrible performance with prefech disabled. (running on 4 > disk striped mirror) Every system I manage (personally; unrelated to my above workplace) has 8GB of RAM in it and run amd64. Some contain 2-disk mirrors, some contain single-disk pools, and a few are 3-disk raidz1. *All* of those systems have historically seen abysmal I/O performance when prefetching was enabled. The hardware is mostly the same (different CPU models, but the same SATA controllers (ICH9R)), so it's not an issue with a single system. If you get better performance -- really, truly, honestly -- with prefetch enabled on your system, then I strongly recommend you keep it enabled. However, for what it's worth (probably not much), this is the first I've ever heard of a FreeBSD system performing better with prefetch enabled. To be completely fair: I should probably dig out my test/stress system and re-test performance with prefetch enabled, keeping in mind the other tunables I use for ZFS (some loader, some sysctl). But those settings are performance-related, and the initial topic of discussion was kmem exhaustion. I don't want to get off-topic for the OP's sake. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 10:56:22 2011 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 B919710656B9 for ; Fri, 4 Mar 2011 10:56:22 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by mx1.freebsd.org (Postfix) with ESMTP id 71E178FC0C for ; Fri, 4 Mar 2011 10:56:22 +0000 (UTC) Received: by gwaa18 with SMTP id a18so1679012gwa.17 for ; Fri, 04 Mar 2011 02:56:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Wqm2Bp5hoyYc9TJE8yPdOqJ0sfFTMezWKxVOpWZac8w=; b=KYPiT/kS8ouPoIUKLhucEj0v45O5HX0ppk0E8KtGFoof+YXrSOLrRJQJqjQ5PrZUMd x16ZfeEDExglwS6jBnyKV00nFJ1HUBztb/RN+a4wxYOhjTUyP86G55u5zrQBpvOPRW1c SfpLxLmiEORfBQS6n3rn8wQCDYJ8P8mRwBCD8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=Dt2ffDmlEk6ppzny0okPh5o4WiHaI2sjCR0ehlNFwJoQEt23li4vR5Ia5mRH9Zp+00 9PoGE1EreNXoraBxV6gs3dsCkobhofuixHs2Up71ATmOw9NmbHJn1yFui0jaPihbum0q jakTisP21Vmi+ZchtwTs2ZCmCXSplKuH4N7LM= Received: by 10.100.195.5 with SMTP id s5mr175834anf.224.1299234634113; Fri, 04 Mar 2011 02:30:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.8.2 with HTTP; Fri, 4 Mar 2011 02:30:04 -0800 (PST) In-Reply-To: <20110304100517.GA23249@icarus.home.lan> References: <1299232133.18671.3.camel@pc286.embl.fr> <20110304100517.GA23249@icarus.home.lan> From: Matthias Gamsjager Date: Fri, 4 Mar 2011 11:30:04 +0100 Message-ID: To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, =?ISO-8859-1?Q?Micka=EBl_Can=E9vet?= Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 10:56:22 -0000 > # Disable ZFS prefetching > # http://southbrain.com/south/2008/04/the-nightmare-comes-slowly-zfs.html > # Increases overall speed of ZFS, but when disk flushing/writes occur, > # system is less responsive (due to extreme disk I/O). > # NOTE: Systems with 8GB of RAM or more have prefetch enabled by > # default. > vfs.zfs.prefetch_disable="1" > > > I wonder if this is still the case since the website you referring to was from 2008 and I guess a lot has changed since then. For example I get horrible performance with prefech disabled. (running on 4 disk striped mirror) From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 11:13:59 2011 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 254AA106564A for ; Fri, 4 Mar 2011 11:13:59 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.net (centre.keltia.net [IPv6:2a01:240:fe5c::41]) by mx1.freebsd.org (Postfix) with ESMTP id CBD0A8FC0A for ; Fri, 4 Mar 2011 11:13:58 +0000 (UTC) Received: from roberto-al.eurocontrol.fr (aran.keltia.net [88.191.250.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.net (Postfix/TLS) with ESMTPSA id 83ED7DEDC; Fri, 4 Mar 2011 12:13:57 +0100 (CET) Date: Fri, 4 Mar 2011 12:13:55 +0100 From: Ollivier Robert To: =?iso-8859-15?Q?Micka=EBl_Can=E9vet?= Message-ID: <20110304111354.GB43078@roberto-al.eurocontrol.fr> References: <1299232133.18671.3.camel@pc286.embl.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1299232133.18671.3.camel@pc286.embl.fr> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7.2 / Dell D820 SMP User-Agent: Mutt/1.5.20 (2009-06-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (keltia.net); Fri, 04 Mar 2011 12:13:57 +0100 (CET) Cc: freebsd-fs@freebsd.org Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 11:13:59 -0000 Mickaël Canévet disait : > Should I also increase vfs.zfs.arc_max ? Unless you have a very busy server, I do not think so. Jeremy Chedwick has a very nice post about several sysctl/loader.conf tunables, did you see it? http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061642.html > Do you have any idea why the kernel panicked at only 8GB allocated ? No. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/ From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 11:37:49 2011 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 85D22106566B for ; Fri, 4 Mar 2011 11:37:49 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) by mx1.freebsd.org (Postfix) with ESMTP id 0321C8FC17 for ; Fri, 4 Mar 2011 11:37:49 +0000 (UTC) Received: from amavis-proxy-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id D25D01D1CED for ; Fri, 4 Mar 2011 12:37:47 +0100 (CET) Authentication-Results: mail.ijs.si; dkim=pass (1024-bit key) header.i=@ijs.si header.b=Q4IlxwO2; dkim-adsp=pass DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= message-id:content-transfer-encoding:content-type:content-type :mime-version:organization:user-agent:date:date:subject:subject :from:from:received:received:received:vbr-info; s=jakla2; t= 1299238665; x=1301830666; bh=a5Ka+94/KXroP8ev1Vws5X7k+5eOG//ad93 gRBXi4Pc=; b=Q4IlxwO2mxTM26aakemyMgswEc9QzTGS7KIAU8g13Il0mTH6Bo2 CR70cPE9BboPjB6cyz3OTPZ1xfQ5r/6e7ZxNnAjdhMW5Y891LL83Hiny7eY2fi9d btEEJ5VZDoE1BXGHs+Ke5qbyu0mzzWXuzgJykxD2/1oIJJEn+H2Hv0No= VBR-Info: md=ijs.si; mc=all; mv=dwl.spamhaus.org; X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([127.0.0.1]) by amavis-proxy-ori.ijs.si (mail.ijs.si [127.0.0.1]) (amavisd-new, port 10012) with ESMTP id NQRefQBok7sX for ; Fri, 4 Mar 2011 12:37:45 +0100 (CET) Received: from edina.ijs.si (unknown [IPv6:2001:1470:ff80:0:2e0:81ff:fe72:51d]) by mail.ijs.si (Postfix) with ESMTP for ; Fri, 4 Mar 2011 12:37:45 +0100 (CET) Received: from siesta.ijs.si (upc.si.94.140.92.23.dc.cable.static.telemach.net [94.140.92.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by edina.ijs.si (Postfix) with ESMTPSA id 38EF422F37B for ; Fri, 4 Mar 2011 12:37:44 +0100 (CET) From: Mark Martinec To: freebsd-fs@freebsd.org Date: Fri, 4 Mar 2011 12:37:43 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-RELEASE; KDE/4.5.5; amd64; ; ) Organization: J. Stefan Institute MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201103041237.44240.Mark.Martinec+freebsd@ijs.si> Subject: ftruncate under ZFS incorrectly checks permissions 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, 04 Mar 2011 11:37:49 -0000 Any takers for the: http://www.freebsd.org/cgi/query-pr.cgi?pr=154873 ? Summary: ftruncate under ZFS requires W file access permission, instead of testing file open mode (O_RDWR), (violating POSIX.1-2008 and breaking Postfix mailer) (FreeBSD 8.2, ZFS: pool version 15, ZFS version 4, and earlier) Mark From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 12:02:32 2011 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 EA3BF106567F for ; Fri, 4 Mar 2011 12:02:32 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id AAB5B8FC2D for ; Fri, 4 Mar 2011 12:02:32 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id DBCE51076C76; Fri, 4 Mar 2011 12:02:30 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 53905-01-3; Fri, 4 Mar 2011 12:02:19 +0000 (GMT) Received: from [10.0.2.3] (unknown [90.155.77.78]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id 432681076E4D; Fri, 4 Mar 2011 12:01:56 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <20110302121612.GA61020@icarus.home.lan> Date: Fri, 4 Mar 2011 12:01:55 +0000 Content-Transfer-Encoding: 7bit Message-Id: <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 12:02:33 -0000 On 2 Mar 2011, at 12:16, Jeremy Chadwick wrote: > On Wed, Mar 02, 2011 at 10:28:50AM +0000, Dr Josef Karthauser wrote: >> >> I guess I should have been a bit clearer, I mean without any external >> devices backing them. Seeing as this is to be running on a VPS/Xen at >> a hosting environment I'm not able to add any additional devices. I'm >> not memory starved however. Is it madness to use a memory disk? (The >> instance in question will have 6gb of ram total to play with.). > > Again: don't disable the ZIL, and adjust the ARC to whatever size you > want using a combo of vm.kmem_size and vfs.zfs.arc_max. Make use of the > RAM you have available to you. :-) > Ok. That sounds like a plan. Next question, if I may. It looks like a XENHVM environment is unavailable to me, so I'm going have to stick with i386, and PAE to make the additional memory available. Given this constraint, does it still make sense to be trying to use ZFS? I had imagined that with 6GB to play with, I could dedicate 2GB of kernel space to the ZFS, leaving most of the rest for user land to play with. I've never played with PAE so I don't know whether I'm making any stupid assumptions here. Could I be, or is this still a sensible configuration to be thinking about? The grand picture is something like this then: - Hardware environment: XEN with 6GB ram, ample processor, 80GB disk. - O/S environment: FreeBSD 8.2 + PAE + XEN_PV + ZFS. - Goal: Host a number of ZFS managed jails in a secure and reliable way. Am I asking for trouble, or am I on the money? Joe p.s. there are some HVM XEN hosts out there, but it looks like they're all _much_ more expensive that the hosting provider that I'm considering, which appears to be offering a sweet spot of memory/cost. From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 12:14:00 2011 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 3C244106566B for ; Fri, 4 Mar 2011 12:14:00 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id DE2068FC17 for ; Fri, 4 Mar 2011 12:13:59 +0000 (UTC) Received: by qyk27 with SMTP id 27so1797691qyk.13 for ; Fri, 04 Mar 2011 04:13:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=iyXjeUwrl1N2fyvUO5NQHSvlT4e8FULVA4Swf5jl62o=; b=SpZJc7puyp+TzCBVmypjf98lMlWXEAU7ASxx+oP8/M6+1wk63eLrB4zsKdwPxvuTEL 3VodRQ6IUY4L23P3uXwTuKCWj/OgOugyym7vfRxwoi6mj0sOIsXdNF1ubI8wdDlsmZx1 qPpkUDE4As8dGsutywfHn7jMPVoOoNvoJ4+XA= 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:content-transfer-encoding; b=UKSUWox2rZFxPVCdFRL2HYFiptu3+hcYCyy6gRWPKqDTBLVC6lS3tDUB4GXpKl9K1d ooxe/YmSz1gqDiKqf7OTRZVFY8VYTesO905EaLmAQHh4Gm/6mLfFKAbdp63Y93CppkdN rf6gKen8VvQNQtscgRzxJ5z+Gly4ZsmSmXsRM= MIME-Version: 1.0 Received: by 10.229.68.36 with SMTP id t36mr380632qci.203.1299240838935; Fri, 04 Mar 2011 04:13:58 -0800 (PST) Received: by 10.229.68.144 with HTTP; Fri, 4 Mar 2011 04:13:58 -0800 (PST) In-Reply-To: <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> Date: Fri, 4 Mar 2011 12:13:58 +0000 Message-ID: From: Tom Evans To: Dr Josef Karthauser Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 12:14:00 -0000 On Fri, Mar 4, 2011 at 12:01 PM, Dr Josef Karthauser wrote= : > On 2 Mar 2011, at 12:16, Jeremy Chadwick wrote: > >> On Wed, Mar 02, 2011 at 10:28:50AM +0000, Dr Josef Karthauser wrote: >>> >>> I guess I should have been a bit clearer, I mean without any external >>> devices backing them. Seeing as this is to be running on a VPS/Xen at >>> a hosting environment I'm not able to add any additional devices. I'm >>> not memory starved however. Is it madness to use a memory disk? (The >>> instance in question will have 6gb of ram total to play with.). >> >> Again: don't disable the ZIL, and adjust the ARC to whatever size you >> want using a combo of vm.kmem_size and vfs.zfs.arc_max. =C2=A0Make use o= f the >> RAM you have available to you. =C2=A0:-) >> > > Ok. That sounds like a plan. > > Next question, if I may. It looks like a XENHVM environment is unavailabl= e > to me, so I'm going have to stick with i386, and PAE to make the addition= al > memory available. Given this constraint, does it still make sense to be > trying to use ZFS? I had imagined that with 6GB to play with, I could > dedicate 2GB of kernel space to the ZFS, leaving most of the rest for use= r > land to play with. I've never played with PAE so I don't know whether I'm > making any stupid assumptions here. > > Could I be, or is this still a sensible configuration to be thinking abou= t? > > The grand picture is something like this then: > > - Hardware environment: XEN with 6GB ram, ample processor, 80GB disk. > - O/S environment: FreeBSD 8.2 + PAE + XEN_PV + ZFS. > - Goal: Host a number of ZFS managed jails in a secure and reliable way. > > Am I asking for trouble, or am I on the money? > > Joe > > p.s. there are some HVM XEN hosts out there, but it looks like they're al= l > _much_ more expensive that the hosting provider that I'm considering, whi= ch > appears to be offering a sweet spot of memory/cost. PAE? What is this, the 90s? ;) i386 + ZFS is not a wise move IMO. Any reason why you cannot use amd64? Cheers Tom From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 12:33:24 2011 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 A39CF106566C for ; Fri, 4 Mar 2011 12:33:24 +0000 (UTC) (envelope-from canevet@embl.fr) Received: from emblmta1.embl.fr (emblmta1.embl.fr [193.49.43.176]) by mx1.freebsd.org (Postfix) with ESMTP id 36AC28FC16 for ; Fri, 4 Mar 2011 12:33:23 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.62,263,1297033200"; d="asc'?scan'208";a="1308741" Received: from unknown (HELO [172.26.15.11]) ([172.26.15.11]) by emblmta1.embl.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 04 Mar 2011 13:33:22 +0100 From: =?ISO-8859-1?Q?Micka=EBl_Can=E9vet?= To: Ollivier Robert In-Reply-To: <20110304111354.GB43078@roberto-al.eurocontrol.fr> References: <1299232133.18671.3.camel@pc286.embl.fr> <20110304111354.GB43078@roberto-al.eurocontrol.fr> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-NBTa6uaFDO5s9ED/MSQn" Date: Fri, 04 Mar 2011 13:33:20 +0100 Message-ID: <1299242000.18671.16.camel@pc286.embl.fr> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Cc: freebsd-fs@freebsd.org Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 12:33:24 -0000 --=-NBTa6uaFDO5s9ED/MSQn Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2011-03-04 at 12:13 +0100, Ollivier Robert wrote: > Micka=C3=ABl Can=C3=A9vet disait : > > Should I also increase vfs.zfs.arc_max ? >=20 > Unless you have a very busy server, I do not think so. Jeremy Chedwick h= as a very nice post about several sysctl/loader.conf tunables, did you see = it? >=20 > http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061642.ht= ml >=20 > > Do you have any idea why the kernel panicked at only 8GB allocated ? >=20 > No. >=20 Thank you I will read that carefully. --=-NBTa6uaFDO5s9ED/MSQn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAk1w3BAACgkQZjBmN5Hi/YYnzQCgnpalp2pfke2KI1R7KwtiwUll ShQAnRfA+teLZMc+mvM7BFQqmu6A4E4y =pf/N -----END PGP SIGNATURE----- --=-NBTa6uaFDO5s9ED/MSQn-- From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 13:18:52 2011 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 E39FB106566B for ; Fri, 4 Mar 2011 13:18:52 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id C44988FC0A for ; Fri, 4 Mar 2011 13:18:52 +0000 (UTC) Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta06.emeryville.ca.mail.comcast.net with comcast id F1Jk1g0050lTkoCA61Js5K; Fri, 04 Mar 2011 13:18:52 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta04.emeryville.ca.mail.comcast.net with comcast id F1Jp1g00c0PUQVN8Q1JpVg; Fri, 04 Mar 2011 13:18:50 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 236189B422; Fri, 4 Mar 2011 05:18:49 -0800 (PST) Date: Fri, 4 Mar 2011 05:18:49 -0800 From: Jeremy Chadwick To: Tom Evans Message-ID: <20110304131849.GA26774@icarus.home.lan> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, Dr Josef Karthauser Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 13:18:53 -0000 On Fri, Mar 04, 2011 at 12:13:58PM +0000, Tom Evans wrote: > On Fri, Mar 4, 2011 at 12:01 PM, Dr Josef Karthauser wrote: > > On 2 Mar 2011, at 12:16, Jeremy Chadwick wrote: > > > >> On Wed, Mar 02, 2011 at 10:28:50AM +0000, Dr Josef Karthauser wrote: > >>> > >>> I guess I should have been a bit clearer, I mean without any external > >>> devices backing them. Seeing as this is to be running on a VPS/Xen at > >>> a hosting environment I'm not able to add any additional devices. I'm > >>> not memory starved however. Is it madness to use a memory disk? (The > >>> instance in question will have 6gb of ram total to play with.). > >> > >> Again: don't disable the ZIL, and adjust the ARC to whatever size you > >> want using a combo of vm.kmem_size and vfs.zfs.arc_max.  Make use of the > >> RAM you have available to you.  :-) > >> > > > > Ok. That sounds like a plan. > > > > Next question, if I may. It looks like a XENHVM environment is unavailable > > to me, so I'm going have to stick with i386, and PAE to make the additional > > memory available. Given this constraint, does it still make sense to be > > trying to use ZFS? I had imagined that with 6GB to play with, I could > > dedicate 2GB of kernel space to the ZFS, leaving most of the rest for user > > land to play with. I've never played with PAE so I don't know whether I'm > > making any stupid assumptions here. > > > > Could I be, or is this still a sensible configuration to be thinking about? > > > > The grand picture is something like this then: > > > > - Hardware environment: XEN with 6GB ram, ample processor, 80GB disk. > > - O/S environment: FreeBSD 8.2 + PAE + XEN_PV + ZFS. > > - Goal: Host a number of ZFS managed jails in a secure and reliable way. > > > > Am I asking for trouble, or am I on the money? > > > > Joe > > > > p.s. there are some HVM XEN hosts out there, but it looks like they're all > > _much_ more expensive that the hosting provider that I'm considering, which > > appears to be offering a sweet spot of memory/cost. > > PAE? What is this, the 90s? ;) > > i386 + ZFS is not a wise move IMO. Any reason why you cannot use amd64? Not to mention, as I understand it, PAE induces all *sorts* of driver incompatibilities and technical hurdles when it comes to the kernel. I believe there are features/drivers/etc. which also do not build/work if PAE is used in the kernel. If something suddenly starts acting "oddly" on a PAE system, it wouldn't surprise me if PAE was to blame. Joe should be aware that amd64 does offer i386 compatibility libraries (referred to as "lib32") so you definitely can run i386 binaries on amd64. Speculative: Joe may be in the same boat I am with one of my customers: they use PHP eAccelerator (binary-only, only works on i386 *and* uses compat6x) as well as ZendOptimizer (works on amd64 but I'm not sure if this works with newer PHP), plus cannot upgrade to PHP 5.3 for a multitude of reasons. I also have no idea how the above two PHP extensions would play with a PHP built natively for amd64 (e.g. PHP amd64, eAcclerator i386 + compat6x libraries/libc/etc., ZendOptimizer amd64). I have fought time and time again with this customer about the use of this software ("is there REALLY any way you can get rid of it?"), but they absolutely will not budge. Anyway, you can see my predicament, but I'm not sure what Joe's is. I tend to build all of my systems with WITHOUT_LIB32=true in src.conf and without COMPAT_FREEBSD32 in the kernel, simply because I'd rather as much as possible of the system as possible be true 64-bit. Mix-matching the two has never sat well with me; probably the OCD part... :-) -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 13:39:02 2011 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 C2B13106564A for ; Fri, 4 Mar 2011 13:39:02 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 68CE48FC17 for ; Fri, 4 Mar 2011 13:39:02 +0000 (UTC) Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta02.westchester.pa.mail.comcast.net with comcast id F1KW1g0051ZXKqc521f2C9; Fri, 04 Mar 2011 13:39:02 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta21.westchester.pa.mail.comcast.net with comcast id F1ez1g00d0PUQVN3h1f0Hy; Fri, 04 Mar 2011 13:39:01 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E95999B422; Fri, 4 Mar 2011 05:38:57 -0800 (PST) Date: Fri, 4 Mar 2011 05:38:57 -0800 From: Jeremy Chadwick To: Tom Evans Message-ID: <20110304133857.GA27130@icarus.home.lan> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> <20110304131849.GA26774@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110304131849.GA26774@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, Dr Josef Karthauser Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 13:39:02 -0000 On Fri, Mar 04, 2011 at 05:18:49AM -0800, Jeremy Chadwick wrote: > Speculative: Joe may be in the same boat I am with one of my customers: > they use PHP eAccelerator (binary-only, only works on i386 *and* uses > compat6x) as well as ZendOptimizer (works on amd64 but I'm not sure if > this works with newer PHP), plus cannot upgrade to PHP 5.3 for a > multitude of reasons. I also have no idea how the above two PHP > extensions would play with a PHP built natively for amd64 (e.g. PHP > amd64, eAcclerator i386 + compat6x libraries/libc/etc., ZendOptimizer > amd64). I have fought time and time again with this customer about the > use of this software ("is there REALLY any way you can get rid of it?"), > but they absolutely will not budge. Off-topic: I just re-reviewed this. I'm trying to recall the "doesn't work on amd64" bits I kept encountering when dealing with either www/eaccelerator or devel/ZendOptimizer, or maybe something one of those two depended on. I'm looking at the Makefiles for both ports and neither seem to indicate this is the case, so I'm at a bit of a loss and feel ashamed stating something that may not be true. But rest assured there was, for quite some time, something related to those two which did not work/build on amd64. (Even file annotations aren't really helping me track down what I was encountering) I guess I'll need to re-visit this situation with a test/devel box for the customer. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 13:41:18 2011 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 1A9901065673 for ; Fri, 4 Mar 2011 13:41:18 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (gribble.egr.msu.edu [35.9.37.169]) by mx1.freebsd.org (Postfix) with ESMTP id E3A348FC17 for ; Fri, 4 Mar 2011 13:41:17 +0000 (UTC) Received: from gribble (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 9E1FD6E9F2 for ; Fri, 4 Mar 2011 08:23:29 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by gribble (gribble.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bl83YsjmY0JX for ; Fri, 4 Mar 2011 08:23:29 -0500 (EST) Received: from [35.9.44.65] (daemon.egr.msu.edu [35.9.44.65]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mcdouga9) by mail.egr.msu.edu (Postfix) with ESMTPSA id 7A78C6E9BA for ; Fri, 4 Mar 2011 08:23:29 -0500 (EST) Message-ID: <4D70E7D1.5030205@egr.msu.edu> Date: Fri, 04 Mar 2011 08:23:29 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110101 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <1299232133.18671.3.camel@pc286.embl.fr> In-Reply-To: <1299232133.18671.3.camel@pc286.embl.fr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 13:41:18 -0000 On 03/04/11 04:48, Mickaël Canévet wrote: >> I'd use vm.kmem_size="32G" (i.e. twice your RAM) and that's it. > > Should I also increase vfs.zfs.arc_max ? > > Do you have any idea why the kernel panicked at only 8GB allocated ? > > Thank you I believe ARC allocations in kmem can become fragmented, so when it is searching for a place to store a new contiguous segment of memory, the remaining fragmented free spaces may all be too small. I also set vm.kmem_size to about twice the amount of ram to help it avoid this issue. I suspect if kmem is badly fragmented then performance of ZFS can downgrade, so that is another reason to keep kmem bigger. From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 13:46:36 2011 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 8C3AA10657E1 for ; Fri, 4 Mar 2011 13:46:36 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id 4AA108FC1D for ; Fri, 4 Mar 2011 13:46:36 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id E6E521076C93; Fri, 4 Mar 2011 13:46:34 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 75972-06; Fri, 4 Mar 2011 13:46:24 +0000 (GMT) Received: from [90.155.77.76] (unknown [90.155.77.76]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id A283E1076D1D; Fri, 4 Mar 2011 13:46:23 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: Date: Fri, 4 Mar 2011 13:46:22 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> To: Tom Evans X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 13:46:36 -0000 On 4 Mar 2011, at 12:13, Tom Evans wrote: > On Fri, Mar 4, 2011 at 12:01 PM, Dr Josef Karthauser = wrote: >>=20 >> p.s. there are some HVM XEN hosts out there, but it looks like = they're all >> _much_ more expensive that the hosting provider that I'm considering, = which >> appears to be offering a sweet spot of memory/cost. >=20 > PAE? What is this, the 90s? ;) >=20 > i386 + ZFS is not a wise move IMO. Any reason why you cannot use = amd64? >=20 Hey Tom, The problem actually boils down to the fact that our amd64 XEN support = isn't entirely para-virtualized, which means it needs hardware = virtualisation support (HVM) to run. There hosting provider I'm looking = at doesn't support HVM, leaving me unable to take advantage of amd64 in = this scenario. There are other providers that do, but they are twice as = much cost for half as much ram. Joe From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 13:49:29 2011 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 5A62A1065679 for ; Fri, 4 Mar 2011 13:49:29 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id 195108FC15 for ; Fri, 4 Mar 2011 13:49:28 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id 33B981076C93; Fri, 4 Mar 2011 13:49:28 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 77103-07; Fri, 4 Mar 2011 13:49:17 +0000 (GMT) Received: from [90.155.77.76] (unknown [90.155.77.76]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id DB0D91076C78; Fri, 4 Mar 2011 13:49:16 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <20110304131849.GA26774@icarus.home.lan> Date: Fri, 4 Mar 2011 13:49:15 +0000 Content-Transfer-Encoding: 7bit Message-Id: <0A0632A0-24C3-4B11-8542-37A58DCA6390@tao.org.uk> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> <20110304131849.GA26774@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Cc: Tom Evans , freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 13:49:29 -0000 On 4 Mar 2011, at 13:18, Jeremy Chadwick wrote: > > Not to mention, as I understand it, PAE induces all *sorts* of driver > incompatibilities and technical hurdles when it comes to the kernel. I > believe there are features/drivers/etc. which also do not build/work if > PAE is used in the kernel. If something suddenly starts acting "oddly" > on a PAE system, it wouldn't surprise me if PAE was to blame. > > Joe should be aware that amd64 does offer i386 compatibility libraries > (referred to as "lib32") so you definitely can run i386 binaries on > amd64. Hey Jeremy, I don't believe that that's an issue anymore. The XEN kernel comes configured with PAE as a default option, and I've seen elsewhere that there is no technical problems running ZFS in a PAE environment. (The PAE docs are out of date when they say we can't use kernel modules, and any 64 bit aware kernel model should run with PAE with no difficulties). Joe From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 14:00:31 2011 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 77721106568D for ; Fri, 4 Mar 2011 14:00:31 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF518FC1E for ; Fri, 4 Mar 2011 14:00:20 +0000 (UTC) Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta13.westchester.pa.mail.comcast.net with comcast id F1Xe1g0031ei1Bg5D20MPp; Fri, 04 Mar 2011 14:00:21 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta24.westchester.pa.mail.comcast.net with comcast id F20H1g00n0PUQVN3k20HDH; Fri, 04 Mar 2011 14:00:19 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id AF3EF9B422; Fri, 4 Mar 2011 06:00:15 -0800 (PST) Date: Fri, 4 Mar 2011 06:00:15 -0800 From: Jeremy Chadwick To: Dr Josef Karthauser Message-ID: <20110304140015.GA27523@icarus.home.lan> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> <20110304131849.GA26774@icarus.home.lan> <0A0632A0-24C3-4B11-8542-37A58DCA6390@tao.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0A0632A0-24C3-4B11-8542-37A58DCA6390@tao.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Tom Evans , freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 14:00:31 -0000 On Fri, Mar 04, 2011 at 01:49:15PM +0000, Dr Josef Karthauser wrote: > On 4 Mar 2011, at 13:18, Jeremy Chadwick wrote: > > > > Not to mention, as I understand it, PAE induces all *sorts* of driver > > incompatibilities and technical hurdles when it comes to the kernel. I > > believe there are features/drivers/etc. which also do not build/work if > > PAE is used in the kernel. If something suddenly starts acting "oddly" > > on a PAE system, it wouldn't surprise me if PAE was to blame. > > > > Joe should be aware that amd64 does offer i386 compatibility libraries > > (referred to as "lib32") so you definitely can run i386 binaries on > > amd64. > > Hey Jeremy, > > I don't believe that that's an issue anymore. The XEN kernel comes > configured with PAE as a default option, and I've seen elsewhere that > there is no technical problems running ZFS in a PAE environment. (The > PAE docs are out of date when they say we can't use kernel modules, > and any 64 bit aware kernel model should run with PAE with no > difficulties). XEN isn't something I'm familiar with, which is obviously a huge part of the problem with me trying to give you advice on the matter. :-) The only virtualisation "system" I'm familiar with is VMware Workstation, which isn't anything like XEN. What I'm going off of is /sys/i386/conf/PAE vs. /sys/i386/conf/XEN. Be sure to notice all the "nodevice" lines in /sys/i386/conf/PAE, and the comment directly above those. The XEN configuration file has "options PAE", which is ultimately what a driver/piece of kernel code would use for compile-time detection for supporting/working under PAE. For example, arcmsr(4) will flat out panic() (intentionally) if PAE is used. bge(4) and twa(4) appear to have a 4GB boundary on DMA; I don't know the implications of this. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 14:06:29 2011 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 485DD106566B for ; Fri, 4 Mar 2011 14:06:29 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from alpha.tao.org.uk (alpha.tao.org.uk [212.42.1.232]) by mx1.freebsd.org (Postfix) with ESMTP id 05D078FC13 for ; Fri, 4 Mar 2011 14:06:28 +0000 (UTC) Received: from localhost (alpha.tao.org.uk [212.42.1.232]) by alpha.tao.org.uk (Postfix) with ESMTP id D9F161076C85; Fri, 4 Mar 2011 14:06:27 +0000 (GMT) Received: from alpha.tao.org.uk ([212.42.1.232]) by localhost (mail.tao.org.uk [212.42.1.232]) (amavisd-maia, port 10024) with LMTP id 82437-06; Fri, 4 Mar 2011 14:06:16 +0000 (GMT) Received: from [90.155.77.76] (unknown [90.155.77.76]) (Authenticated sender: joemail@alpha.tao.org.uk) by alpha.tao.org.uk (Postfix) with ESMTPA id C0AEA1076C76; Fri, 4 Mar 2011 14:06:13 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <20110304140015.GA27523@icarus.home.lan> Date: Fri, 4 Mar 2011 14:06:12 +0000 Content-Transfer-Encoding: 7bit Message-Id: References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> <20110304131849.GA26774@icarus.home.lan> <0A0632A0-24C3-4B11-8542-37A58DCA6390@tao.org.uk> <20110304140015.GA27523@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.2a Cc: Tom Evans , freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 14:06:29 -0000 On 4 Mar 2011, at 14:00, Jeremy Chadwick wrote: > On Fri, Mar 04, 2011 at 01:49:15PM +0000, Dr Josef Karthauser wrote: >> I don't believe that that's an issue anymore. The XEN kernel comes >> configured with PAE as a default option, and I've seen elsewhere that >> there is no technical problems running ZFS in a PAE environment. (The >> PAE docs are out of date when they say we can't use kernel modules, >> and any 64 bit aware kernel model should run with PAE with no >> difficulties). > > XEN isn't something I'm familiar with, which is obviously a huge part of > the problem with me trying to give you advice on the matter. :-) The > only virtualisation "system" I'm familiar with is VMware Workstation, > which isn't anything like XEN. > > What I'm going off of is /sys/i386/conf/PAE vs. /sys/i386/conf/XEN. > > Be sure to notice all the "nodevice" lines in /sys/i386/conf/PAE, and > the comment directly above those. The XEN configuration file has > "options PAE", which is ultimately what a driver/piece of kernel code > would use for compile-time detection for supporting/working under PAE. > > For example, arcmsr(4) will flat out panic() (intentionally) if PAE > is used. bge(4) and twa(4) appear to have a 4GB boundary on DMA; I > don't know the implications of this. Luckily I care not about device support. As long as the paravirtualised devices work, and zfs works, I need nothing else. So, I guess the zfs question boils down to whether (given everything else being equal with PAE support) I could consider zfs on i386 with a PAE memory model to be stable enough for a production server (on 8.2). Joe From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 14:38:13 2011 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 104501065692 for ; Fri, 4 Mar 2011 14:38:13 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id EB8688FC15 for ; Fri, 4 Mar 2011 14:38:12 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta10.emeryville.ca.mail.comcast.net with comcast id F2K11g00A1u4NiLAA2eCMP; Fri, 04 Mar 2011 14:38:12 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta21.emeryville.ca.mail.comcast.net with comcast id F2e21g00G0PUQVN8h2e7M0; Fri, 04 Mar 2011 14:38:09 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 21FE49B422; Fri, 4 Mar 2011 06:38:01 -0800 (PST) Date: Fri, 4 Mar 2011 06:38:01 -0800 From: Jeremy Chadwick To: Adam McDougall Message-ID: <20110304143801.GA1734@icarus.home.lan> References: <1299232133.18671.3.camel@pc286.embl.fr> <4D70E7D1.5030205@egr.msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4D70E7D1.5030205@egr.msu.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 04 Mar 2011 14:38:13 -0000 On Fri, Mar 04, 2011 at 08:23:29AM -0500, Adam McDougall wrote: > On 03/04/11 04:48, Mickaël Canévet wrote: > >>I'd use vm.kmem_size="32G" (i.e. twice your RAM) and that's it. > > > >Should I also increase vfs.zfs.arc_max ? > > > >Do you have any idea why the kernel panicked at only 8GB allocated ? > > > >Thank you > > I believe ARC allocations in kmem can become fragmented, so when it > is searching for a place to store a new contiguous segment of > memory, the remaining fragmented free spaces may all be too small. > I also set > vm.kmem_size to about twice the amount of ram to help it avoid this > issue. I suspect if kmem is badly fragmented then performance of > ZFS can downgrade, so that is another reason to keep kmem bigger. My findings on 8.2-RELEASE indicate that doing this results in very unexpected behaviour regarding the ARC maximum. As such, I cannot recommend this model. For example, on an amd64 system with 8GB physical RAM and these two settings in /boot/loader.conf: vm.kmem_size="8192M" vfs.zfs.arc_max="6144M" kstat.zfs.misc.arcstats.size tops out at around 6240986896, with Wired in top(1) showing ~6.3GB. This is expected behaviour and fits (I think) what people expect. However, on the exact same system with these two settings: vm.kmem_size="16384M" vfs.zfs.arc_max="6144M" The above ARC numbers are exactly *half* that amount. This is easily reproducible. Can someone 1) justify the "2x the amount of RAM for vm.kmem_size" setting, and 2) explain in detail the above behaviour? -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 15:12:22 2011 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 E0287106566C for ; Fri, 4 Mar 2011 15:12:22 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 92C468FC0C for ; Fri, 4 Mar 2011 15:12:21 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id 0934474FC99; Fri, 4 Mar 2011 16:12:21 +0100 (CET) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.2 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 10.3004] X-CRM114-CacheID: sfid-20110304_16122_67F89D49 X-CRM114-Status: Good ( pR: 10.3004 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Fri Mar 4 16:12:20 2011 X-DSPAM-Confidence: 0.7008 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4d710154273061365812542 X-DSPAM-Factors: 27, From*Attila Nagy , 0.00010, struct, 0.00212, struct, 0.00212, NULL), 0.00367, error+=, 0.00423, files+with, 0.00500, h>, 0.00550, I+guess, 0.00610, #ifdef, 0.00686, files, 0.00741, defined, 0.00783, relevant, 0.00783, seems+to, 0.00843, implemented, 0.00995, Subject*files, 0.01000, Hi+Is, 0.01000, Received*online.private, 0.99000, ZFS, 0.01000, is+described, 0.99000, Date*16+12, 0.99000, arguments, 0.01000, might+not, 0.01000, header, 0.01000, the+source, 0.01093, of+data, 0.01093, [+], 0.01093, X-Spambayes-Classification: ham; 0.00 Received: from japan.t-online.private (japan.t-online.co.hu [195.228.243.99]) by people.fsn.hu (Postfix) with ESMTPSA id 994BF74FC8B for ; Fri, 4 Mar 2011 16:12:20 +0100 (CET) Message-ID: <4D710154.90409@fsn.hu> Date: Fri, 04 Mar 2011 16:12:20 +0100 From: Attila Nagy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090817 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Punching holes into (sparse) files - porting Solaris fcntl(F_FREESP) to FreeBSD? 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, 04 Mar 2011 15:12:23 -0000 Hi, Is it possible to make regions of files, with already written data sparse? (I'm interested to do this on ZFS) All I could find in this topic is: http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg29047.html grepping through the source gives a match for VOP_SPACE in cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_replay.c: zfs_replay_truncate(zfsvfs_t *zfsvfs, lr_truncate_t *lr, boolean_t byteswap) { #ifdef sun [...] error = VOP_SPACE(ZTOV(zp), F_FREESP, &fl, FWRITE | FOFFMAX, lr->lr_offset, kcred, NULL); And the relevant section from fcntl(2) in Solaris: F_FREESP Free storage space associated with a section of the ordinary file fildes. The section is specified by a variable of data type struct flock pointed to by arg. The data type struct flock is defined in the header (see fcntl.h(3HEAD)) and is described below. Note that all file systems might not support all possible variations of F_FREESP arguments. In particular, many file systems allow space to be freed only at the end of a file. F_FREESP seems to be my friend, and it's implemented in Solaris's ZFS. How hard would it be to complete the port and make it accessible from FreeBSD? I guess it was left out with a reason... Thanks, From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 16:39:34 2011 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 5D8C7106566B for ; Fri, 4 Mar 2011 16:39:34 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id E54CB8FC19 for ; Fri, 4 Mar 2011 16:39:33 +0000 (UTC) Received: by fxm19 with SMTP id 19so2639406fxm.13 for ; Fri, 04 Mar 2011 08:39:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=nX8XXXpNPgooKsI4Q0bBrporeFtDX1Mlig2ZO1YWdEE=; b=f32BAaAqR9dYFV46bxwqrOxiuIXCL5mj3aXYjP1s8b1yn4s5QV1mvVVbeREZx22biB eQCHSjSgK+1u8y3dJqPQQDgBmvgb0HHSJ3wKhuytly6GOhd6fWa6Dmw2MbRfZC0gPijr UNX1cfmCaPBSWoTTC4Slff9aI3yY3qm/3QH24= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=C/zop4bPjR2Bvb3PzluEKt65Lx+Mh8D8NpXtS52SpDQsKlFviOAPAuGOCBBngCGdFq wrCJMagn8z7b59TMoCmYsqVNleEJADxUApKE8uBSbDnWuteI8/fhGH3aKZ6WWx/FxMsY B5EQl9LO/on/+FHXAGtM2bSERZ4pxyYSo4BXw= MIME-Version: 1.0 Received: by 10.223.99.213 with SMTP id v21mr411586fan.129.1299256772544; Fri, 04 Mar 2011 08:39:32 -0800 (PST) Received: by 10.223.94.67 with HTTP; Fri, 4 Mar 2011 08:39:32 -0800 (PST) In-Reply-To: <4D710154.90409@fsn.hu> References: <4D710154.90409@fsn.hu> Date: Fri, 4 Mar 2011 10:39:32 -0600 Message-ID: From: Adam Vande More To: Attila Nagy Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Punching holes into (sparse) files - porting Solaris fcntl(F_FREESP) to FreeBSD? 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, 04 Mar 2011 16:39:34 -0000 > > > Is it possible to make regions of files, with already written data sparse? > (I'm interested to do this on ZFS) > > Well thereis sysutils/phantom HTH -- Adam Vande More From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 21:12:52 2011 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 8B9231065674 for ; Fri, 4 Mar 2011 21:12:52 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 38BA48FC12 for ; Fri, 4 Mar 2011 21:12:51 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id 30AC3750ECE; Fri, 4 Mar 2011 22:12:50 +0100 (CET) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000050, version=1.2.2 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 15.4187] X-CRM114-CacheID: sfid-20110304_22124_5FADEC3C X-CRM114-Status: Good ( pR: 15.4187 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Fri Mar 4 22:12:50 2011 X-DSPAM-Confidence: 0.8513 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4d7155d2710527667723524 X-DSPAM-Factors: 27, From*Attila Nagy , 0.00010, wrote+>, 0.00209, >+>, 0.00262, >+>, 0.00262, References*mail.gmail.com>, 0.00310, wrote, 0.00443, >+Is, 0.00458, In-Reply-To*mail.gmail.com>, 0.00471, files+with, 0.00500, files, 0.00741, rewriting, 0.00913, Adam, 0.00913, Subject*files, 0.01000, >+Well, 0.01000, to+rewrite, 0.01000, Date*49+0100, 0.99000, 05+39, 0.01000, rewrite, 0.01000, References*fsn.hu>, 0.01000, To*gmail.com>, 0.01273, User-Agent*i686, 0.01363, PM, 0.01497, User-Agent*i686+en, 0.01631, User-Agent*Linux+i686, 0.01631, obvious, 0.01809, is+obvious, 0.01809, X-Spambayes-Classification: ham; 0.01 Message-ID: <4D7155D1.6000600@fsn.hu> Date: Fri, 04 Mar 2011 22:12:49 +0100 From: Attila Nagy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090817 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0 MIME-Version: 1.0 To: Adam Vande More References: <4D710154.90409@fsn.hu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Punching holes into (sparse) files - porting Solaris fcntl(F_FREESP) to FreeBSD? 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, 04 Mar 2011 21:12:52 -0000 On 03/04/2011 05:39 PM, Adam Vande More wrote: > > > Is it possible to make regions of files, with already written data > sparse? (I'm interested to do this on ZFS) > > > > Well thereis sysutils/phantom Thanks, but I don't want to rewrite the file. I thought that this is obvious from the other part of the e-mail, sorry. So I would like to make existing, non-sparse regions sparse, without rewriting the file. This is what F_FREESP is for. From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 21:15:17 2011 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 4694F106564A for ; Fri, 4 Mar 2011 21:15:17 +0000 (UTC) (envelope-from gallasch@free.de) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) by mx1.freebsd.org (Postfix) with ESMTP id A9C658FC1B for ; Fri, 4 Mar 2011 21:15:16 +0000 (UTC) Received: (qmail 8719 invoked by uid 98); 4 Mar 2011 21:48:34 +0100 Received: from 91.204.4.103 by smtp.free.de (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.96.5/12494. Clear:RC:1(91.204.4.103):. Processed in 0.04103 secs); 04 Mar 2011 20:48:34 -0000 X-Qmail-Scanner-Mail-From: gallasch@free.de via smtp.free.de X-Qmail-Scanner: 1.25 (Clear:RC:1(91.204.4.103):. Processed in 0.04103 secs) Received: from smtp.free.de (HELO [192.168.1.119]) (gallasch@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 4 Mar 2011 21:48:34 +0100 From: Kai Gallasch Content-Type: text/plain; charset=us-ascii Message-Id: Date: Fri, 4 Mar 2011 21:48:34 +0100 To: freebsd-fs@freebsd.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Subject: gmirror + gjournal and write cache on drives enabled 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, 04 Mar 2011 21:15:17 -0000 Hi. I'm currently installing a server with 4 x SAS JBOD connected to an = mpt(4) pseudo-raid controller. # gmirror status Name Status Components mirror/gm0 COMPLETE da0 da1 /dev/mirror/gm0s1a.journal / /dev/mirror/gm0s1d.journal /var /dev/mirror/gm0s1e.journal /usr /dev/mirror/gm0s1f.journal /usr/local /dev/mirror/gm0s1g.journal /usr/src /dev/mirror/gm0s1h.journal /usr/obj in gjournal(8) I read: "When gjournal is configured on top of gmirror(8) or graid3(8) = providers, it also keeps them in a consistent state, thus automatic = synchronization on power failure or system crash may be disabled on those providers." Is this statement also true, if the JBODs have their write-cache = enabled? If yes, I'd gladly "gmirror configure -F" to avoid a full sync in case = of a server crash, power loss, etc. Kai.= From owner-freebsd-fs@FreeBSD.ORG Sat Mar 5 09:47:18 2011 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 A6A1B1065674 for ; Sat, 5 Mar 2011 09:47:18 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 00C4A8FC1E for ; Sat, 5 Mar 2011 09:47:17 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id E927CE7F82; Sat, 5 Mar 2011 09:47:16 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=date:from :to:cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=mail; bh=SV4kVTL1jCp2 +K5AqpLXPb9m7ws=; b=OnyIUlI/85WAPT8zyviq3l6unSOR/8rkcMMtQkqL8tkS QgjJ1M3g9ifyTOj4STw2z5siaQbY8emNN+HaELIglLGa4lVWHEW/Av3YtFmlNtZ0 XOaU4Cv1TL/yx2h8o4jqtomKUGw3IQY6uyJeDXpdCTyB/vDW2atybFtIN5G2Uoo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=date:from:to :cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=mail; b=E5sBld L1D8sifOb4qbjmj6Wbb54tYAMa/1cc1DDBWwchnqGpNO9IXaEQeocu/vic9sVI1c ujhjZ+6U05wqUhS2FT8db/W/xAk3/kdUXBVyLhBETqGkKRJxE84Zf/9bn7BO8AUX B1GyzZPSrgwSA2Ij6VT6jd1S1TkUMQreTVZLw= Received: from unknown (client-86-31-236-253.oxfd.adsl.virginmedia.com [86.31.236.253]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id A0255E7F74; Sat, 5 Mar 2011 09:47:16 +0000 (GMT) Date: Sat, 5 Mar 2011 09:46:32 +0000 From: Bruce Cran To: Christian Gusenbauer Message-ID: <20110305094632.00004edd@unknown> In-Reply-To: <201103050851.38930.c47g@gmx.at> References: <201103050851.38930.c47g@gmx.at> X-Mailer: Claws Mail 3.7.8cvs9 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: FS errors during unmount after dump'ing 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, 05 Mar 2011 09:47:18 -0000 On Sat, 5 Mar 2011 08:51:38 +0100 Christian Gusenbauer wrote: > Note, I get these messages *only* after dumping filesystems! > > Is there anything wrong with my filesystems? I assume you're running -CURRENT? What type of filesystem are you using - UFS1, UFS2, UFS2+SUJ etc.? -- Bruce Cran From owner-freebsd-fs@FreeBSD.ORG Sat Mar 5 09:58:10 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 192F0106564A for ; Sat, 5 Mar 2011 09:58:10 +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 6EB228FC12 for ; Sat, 5 Mar 2011 09:58:08 +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 p259aeps091342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Mar 2011 11:36:40 +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 p259aeA4070519; Sat, 5 Mar 2011 11:36:40 +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 p259aePn070518; Sat, 5 Mar 2011 11:36:40 +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: Sat, 5 Mar 2011 11:36:40 +0200 From: Kostik Belousov To: Christian Gusenbauer Message-ID: <20110305093640.GL78089@deviant.kiev.zoral.com.ua> References: <201103050851.38930.c47g@gmx.at> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nWNdv2OBEEbmfXKO" Content-Disposition: inline In-Reply-To: <201103050851.38930.c47g@gmx.at> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: current@freebsd.org, fs@freebsd.org Subject: Re: FS errors during unmount after dump'ing 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, 05 Mar 2011 09:58:10 -0000 --nWNdv2OBEEbmfXKO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Added fs, please remove current on reply]. On Sat, Mar 05, 2011 at 08:51:38AM +0100, Christian Gusenbauer wrote: > Hi! >=20 > Once in a week I backup my PC using amanda (which uses dump(8)). Subseque= ntly=20 > unmounting a filesystem (or during shutdown) I get errors like these: >=20 > handle_workitem_freeblocks: inode 3579904 block count 384 > handle_workitem_freeblocks: inode 3579962 block count 384 > /spare: unmount pending error: blocks 768 files 0 > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > softdep_waitidle: Failed to flush worklist for 0xc5be2510 > softdep_waitidle: Failed to flush worklist for 0xc5be2510 > /data: unmount pending error: blocks 84 files 0 >=20 > Note, I get these messages *only* after dumping filesystems! >=20 > Is there anything wrong with my filesystems? >=20 > Any clues? No clues, you did not provided information even to start looking. What version of the OS you are using ? How do you call dump, in particular, did you specified -L ? Are there any hung (unkillable) processes after the issue appeared ? Please show all kernel messages, not only the tail of it. --nWNdv2OBEEbmfXKO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk1yBCgACgkQC3+MBN1Mb4gSygCfYknQ8omTO9e31/fGXnukR96x 9G0AnRD6JCFYAfRYz7DPKghAppAUQFKX =jLsV -----END PGP SIGNATURE----- --nWNdv2OBEEbmfXKO-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 5 15:10:29 2011 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 ECB311065673 for ; Sat, 5 Mar 2011 15:10:29 +0000 (UTC) (envelope-from andriy@irbisnet.com) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by mx1.freebsd.org (Postfix) with SMTP id 965368FC13 for ; Sat, 5 Mar 2011 15:10:29 +0000 (UTC) Received: (qmail 52096 invoked from network); 5 Mar 2011 14:43:49 -0000 Received: from smtp.irbisnet.com (andriy@99.235.226.221 with login) by smtp104.rog.mail.re2.yahoo.com with SMTP; 05 Mar 2011 06:43:46 -0800 PST X-Yahoo-SMTP: dz9sigaswBA5kWoYWVTZrGHmIs2vaKgG1w-- X-YMail-OSG: 7DBWu_IVM1kvxl2EtZHWY8pdoAXvVuPAJ.MgF8KGhlnCtgs Kw_A6yFG9141ivX32C1dS9tihZqInnIf2oAoeTjsLA8QqdgDjekSxofMjXNt mB9JGxlkTWruhu.GCKXVInVExNjvRwlKJr7Q.naQbIxAcuDrXk8ikpFOzdqU 1bCtAmsSI6eLIEMhx4ZdwDbHW9DShQvJ997hwFc4lFUCTX.Q4JxFIs5lp9O1 FX_1Ed0X7gPEg.hiAVc8JbhI82AUh5X7nx6urZyl.Mryx X-Yahoo-Newman-Property: ymail-3 Received: from [192.168.0.40] (unknown [192.168.0.40]) by smtp.irbisnet.com (Postfix) with ESMTPSA id 063F22658F; Sat, 5 Mar 2011 09:43:45 -0500 (EST) References: <1299232133.18671.3.camel@pc286.embl.fr> <4D70E7D1.5030205@egr.msu.edu> <20110304143801.GA1734@icarus.home.lan> In-Reply-To: <20110304143801.GA1734@icarus.home.lan> Mime-Version: 1.0 (iPhone Mail 8C148) Message-Id: <625F7D8A-78F5-426B-B2C3-A1B4D289FD5F@irbisnet.com> X-Mailer: iPhone Mail (8C148) From: Andriy Bakay Date: Sat, 5 Mar 2011 09:42:47 -0500 To: Jeremy Chadwick Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-fs@freebsd.org" , "pjd@FreeBSD.org" Subject: Re: kmem_map too small with ZFS and 8.2-RELEASE 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, 05 Mar 2011 15:10:30 -0000 On 2011-03-04, at 9:38, Jeremy Chadwick wrote: > On Fri, Mar 04, 2011 at 08:23:29AM -0500, Adam McDougall wrote: >> On 03/04/11 04:48, Micka=C3=ABl Can=C3=A9vet wrote: >>>> I'd use vm.kmem_size=3D"32G" (i.e. twice your RAM) and that's it. >>>=20 >>> Should I also increase vfs.zfs.arc_max ? >>>=20 >>> Do you have any idea why the kernel panicked at only 8GB allocated ? >>>=20 >>> Thank you >>=20 >> I believe ARC allocations in kmem can become fragmented, so when it >> is searching for a place to store a new contiguous segment of >> memory, the remaining fragmented free spaces may all be too small. >> I also set >> vm.kmem_size to about twice the amount of ram to help it avoid this >> issue. I suspect if kmem is badly fragmented then performance of >> ZFS can downgrade, so that is another reason to keep kmem bigger. >=20 > My findings on 8.2-RELEASE indicate that doing this results in very > unexpected behaviour regarding the ARC maximum. As such, I cannot > recommend this model. >=20 > For example, on an amd64 system with 8GB physical RAM and these two > settings in /boot/loader.conf: >=20 > vm.kmem_size=3D"8192M" > vfs.zfs.arc_max=3D"6144M" >=20 > kstat.zfs.misc.arcstats.size tops out at around 6240986896, with Wired > in top(1) showing ~6.3GB. This is expected behaviour and fits (I > think) what people expect. >=20 > However, on the exact same system with these two settings: >=20 > vm.kmem_size=3D"16384M" > vfs.zfs.arc_max=3D"6144M" >=20 > The above ARC numbers are exactly *half* that amount. This is easily > reproducible. >=20 > Can someone 1) justify the "2x the amount of RAM for vm.kmem_size" > setting, and 2) explain in detail the above behaviour? >=20 > --=20 > | Jeremy Chadwick jdc@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP 4BD6C0CB | >=20 > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" I guess Pawel can: vm.kmem_size=3D=E2=80=9D6G=E2=80=9D # This should be 150% of your RAM. http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-confi= guration/ From owner-freebsd-fs@FreeBSD.ORG Sat Mar 5 16:47:09 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2CCB106564A for ; Sat, 5 Mar 2011 16:47:09 +0000 (UTC) (envelope-from c47g@gmx.at) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 45B9F8FC0C for ; Sat, 5 Mar 2011 16:47:08 +0000 (UTC) Received: (qmail invoked by alias); 05 Mar 2011 16:47:07 -0000 Received: from cm203-32.liwest.at (EHLO bones.gusis.at) [81.10.203.32] by mail.gmx.net (mp068) with SMTP; 05 Mar 2011 17:47:07 +0100 X-Authenticated: #9978462 X-Provags-ID: V01U2FsdGVkX19rvKdzpoBrOHZ1fB/GwcCfFFfjwerEvgBuYtZp8A lwcS34vh0Dfksl From: Christian Gusenbauer To: freebsd-current@freebsd.org, fs@freebsd.org Date: Sat, 5 Mar 2011 17:48:44 +0100 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.5; i386; ; ) References: <201103050851.38930.c47g@gmx.at> <20110305093640.GL78089@deviant.kiev.zoral.com.ua> <201103051736.04605.c47g@gmx.at> In-Reply-To: <201103051736.04605.c47g@gmx.at> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201103051748.44554.c47g@gmx.at> X-Y-GMX-Trusted: 0 Cc: Subject: Re: FS errors during unmount after dump'ing 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, 05 Mar 2011 16:47:09 -0000 OK, the attachment got lost, so here's the dmesg output: Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #48 r219265: Fri Mar 4 18:51:23 CET 2011 root@bones.gusis.at:/usr/obj/jail/mytestjail/usr/src/sys/BONES i386 CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2401.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Family = 6 Model = f Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2086711296 (1990 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7ff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 ACPI Warning: Incorrect checksum in table [OEMB] - 0xD6, should be 0xC9 (20110211/tbutils-282) cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xac00-0xac7f mem 0xfd000000-0xfdffffff,0xc0000000-0xcfffffff,0xfc000000-0xfcffffff irq 16 at device 0.0 on pci1 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_io vgapci0: child nvidia0 requested pci_enable_io uhci0: port 0xe000-0xe01f irq 16 at device 26.0 on pci0 usbus0: on uhci0 uhci1: port 0xe080-0xe09f irq 17 at device 26.1 on pci0 usbus1: on uhci1 ehci0: mem 0xfebff400-0xfebff7ff irq 18 at device 26.7 on pci0 usbus2: EHCI version 1.0 usbus2: on ehci0 hdac0: mem 0xfebf8000-0xfebfbfff irq 22 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20100226_0142 pcib2: irq 16 at device 28.0 on pci0 pci4: on pcib2 pcib3: irq 19 at device 28.3 on pci0 pci3: on pcib3 pci3: at device 0.0 (no driver attached) pcib4: irq 16 at device 28.4 on pci0 pci2: on pcib4 ahci0: mem 0xfe8fe000-0xfe8fffff irq 16 at device 0.0 on pci2 ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 atapci0: port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f at device 0.1 on pci2 ata2: on atapci0 uhci2: port 0xd800-0xd81f irq 23 at device 29.0 on pci0 usbus3: on uhci2 uhci3: port 0xd880-0xd89f irq 19 at device 29.1 on pci0 usbus4: on uhci3 uhci4: port 0xdc00-0xdc1f irq 18 at device 29.2 on pci0 usbus5: on uhci4 ehci1: mem 0xfebff000-0xfebff3ff irq 23 at device 29.7 on pci0 usbus6: EHCI version 1.0 usbus6: on ehci1 pcib5: at device 30.0 on pci0 pci5: on pcib5 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xcc00-0xcc3f irq 23 at device 2.0 on pci5 miibus0: on xl0 nsphy0: PHY 24 on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:60:97:11:d6:21 pci5: at device 3.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 ahci1: port 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe41f mem 0xfebff800-0xfebfffff irq 19 at device 31.2 on pci0 ahci1: AHCI v1.10 with 6 3Gbps ports, Port Multiplier supported ahcich2: at channel 0 on ahci1 ahcich3: at channel 1 on ahci1 ahcich4: at channel 2 on ahci1 ahcich5: at channel 3 on ahci1 ahcich6: at channel 4 on ahci1 ahcich7: at channel 5 on ahci1 ichsmb0: port 0x400-0x41f irq 18 at device 31.3 on pci0 smbus0: on ichsmb0 smb0: on smbus0 acpi_button0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 coretemp0: on cpu0 est0: on cpu0 p4tcc0: on cpu0 coretemp1: on cpu1 est1: on cpu1 p4tcc1: on cpu1 Timecounters tick every 1.000 msec vboxdrv: fAsync=0 offMin=0x132 offMax=0x369 hdac0: HDA Codec #0: Analog Devices AD1988A pcm0: at cad 0 nid 1 on hdac0 pcm1: at cad 0 nid 1 on hdac0 pcm2: at cad 0 nid 1 on hdac0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ugen6.1: at usbus6 uhub6: on usbus6 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered uhub5: 2 ports with 2 removable, self powered ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 305245MB (625142448 512 byte sectors: 16H 63S/T 16383C) cd0 at ahcich6 bus 0 scbus6 target 0 lun 0SMP: AP CPU #1 Launched! cd0: Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, WDMA2, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed Root mount waiting for: usbus6 usbus2 uhub2: 4 ports with 4 removable, self powered uhub6: 6 ports with 6 removable, self powered Trying to mount root from ufs:/dev/label/root [rw]... ada1 at ahcich0 bus 0 scbus0 target 0 lun 0 ada1: ATA-7 SATA 2.x device ada1: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C) GEOM: ada1s1: geometry does not match label (255h,63s != 16h,63s). GEOM: label/amanda: geometry does not match label (255h,63s != 16h,63s). GEOM: ufsid/4a9e8e3d6361b6c0: geometry does not match label (255h,63s != 16h,63s). handle_workitem_freeblocks: inode 5 block count 84 handle_workitem_freeblocks: inode 328 block count 112 handle_workitem_freeblocks: inode 5 block count 84 GEOM: ada1s1: geometry does not match label (255h,63s != 16h,63s). GEOM: label/amanda: geometry does not match label (255h,63s != 16h,63s). (ada1:ahcich0:0:0:0): lost device (ada1:ahcich0:0:0:0): removing device entry ROOT LOGIN (root) ON ttyv0 exiting on signal 15 kernel boot file is /boot/kernel/kernel /jail: unmount pending error: blocks 112 files 0 softdep_waitidle: Failed to flush worklist for 0xc5bdb510 /data: unmount pending error: blocks 84 files 0 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...1 0 0 done All buffers synced. softdep_waitidle: Failed to flush worklist for 0xc5bdb510 unmount of /home failed (BUSY) On Saturday 05 March 2011 17:36:04 Christian Gusenbauer wrote: > On Saturday 05 March 2011 10:36:40 Kostik Belousov wrote: > > [Added fs, please remove current on reply]. > > > > On Sat, Mar 05, 2011 at 08:51:38AM +0100, Christian Gusenbauer wrote: > > > Hi! > > > > > > Once in a week I backup my PC using amanda (which uses dump(8)). > > > Subsequently unmounting a filesystem (or during shutdown) I get errors > > > like these: > > > > > > handle_workitem_freeblocks: inode 3579904 block count 384 > > > handle_workitem_freeblocks: inode 3579962 block count 384 > > > /spare: unmount pending error: blocks 768 files 0 > > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > > softdep_waitidle: Failed to flush worklist for 0xc5be2510 > > > softdep_waitidle: Failed to flush worklist for 0xc5be2510 > > > /data: unmount pending error: blocks 84 files 0 > > > > > > Note, I get these messages *only* after dumping filesystems! > > > > > > Is there anything wrong with my filesystems? > > > > > > Any clues? > > > > No clues, you did not provided information even to start looking. > > > > What version of the OS you are using ? > > How do you call dump, in particular, did you specified -L ? > > Are there any hung (unkillable) processes after the issue appeared ? > > Please show all kernel messages, not only the tail of it. > > Hi! > > I'm running current revision 219265. Amanda calls dump like this (ps ax > output): > > 2607 ?? DL 0:00.04 dump 0ubLshf 64 1048576 0 - /dev/label/home (dump) > > so the -L is specified. There are no hung processes. > > I attach a compressed dmesg output. It appears to me, that the > 'handle_workitem_freeblocks' message is printed during the backup. The > other messages are printed during shutdown. > > Thanks, > Christian. From owner-freebsd-fs@FreeBSD.ORG Sat Mar 5 16:52:41 2011 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 E01251065673 for ; Sat, 5 Mar 2011 16:52:41 +0000 (UTC) (envelope-from c47g@gmx.at) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id 360528FC18 for ; Sat, 5 Mar 2011 16:52:40 +0000 (UTC) Received: (qmail invoked by alias); 05 Mar 2011 16:25:59 -0000 Received: from cm203-32.liwest.at (EHLO bones.gusis.at) [81.10.203.32] by mail.gmx.net (mp055) with SMTP; 05 Mar 2011 17:25:59 +0100 X-Authenticated: #9978462 X-Provags-ID: V01U2FsdGVkX1+gKdJPItCgye4XJlN9Y8AGyer/mGYvs4IkAw3dLe 3oKt9TYb4j/2dI From: Christian Gusenbauer To: Bruce Cran Date: Sat, 5 Mar 2011 17:27:36 +0100 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.5; i386; ; ) References: <201103050851.38930.c47g@gmx.at> <20110305094632.00004edd@unknown> In-Reply-To: <20110305094632.00004edd@unknown> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201103051727.36518.c47g@gmx.at> X-Y-GMX-Trusted: 0 Cc: freebsd-fs@freebsd.org Subject: Re: FS errors during unmount after dump'ing 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, 05 Mar 2011 16:52:42 -0000 On Saturday 05 March 2011 10:46:32 Bruce Cran wrote: > On Sat, 5 Mar 2011 08:51:38 +0100 > > Christian Gusenbauer wrote: > > Note, I get these messages *only* after dumping filesystems! > > > > Is there anything wrong with my filesystems? > > I assume you're running -CURRENT? > What type of filesystem are you using - UFS1, UFS2, UFS2+SUJ etc.? Hi Bruce! Yes, I'm runninc current, revision 219265. All filesystems are UFS2+SUJ, only / (root) is UFS2 without softupdates. But the root filesystem never showed that problem. Ciao, Christian. From owner-freebsd-fs@FreeBSD.ORG Sat Mar 5 17:01:10 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22D33106564A for ; Sat, 5 Mar 2011 17:01:10 +0000 (UTC) (envelope-from c47g@gmx.at) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 041B78FC12 for ; Sat, 5 Mar 2011 17:01:08 +0000 (UTC) Received: (qmail invoked by alias); 05 Mar 2011 16:34:27 -0000 Received: from cm203-32.liwest.at (EHLO bones.gusis.at) [81.10.203.32] by mail.gmx.net (mp028) with SMTP; 05 Mar 2011 17:34:27 +0100 X-Authenticated: #9978462 X-Provags-ID: V01U2FsdGVkX18j1xwoTkcjwwbsTsBk1mu4srChR/Sh/N9JWNgr+A pW+vmogqJvyJY7 From: Christian Gusenbauer To: Kostik Belousov Date: Sat, 5 Mar 2011 17:36:04 +0100 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.5; i386; ; ) References: <201103050851.38930.c47g@gmx.at> <20110305093640.GL78089@deviant.kiev.zoral.com.ua> In-Reply-To: <20110305093640.GL78089@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_0ZmcNdyTe41Uqef" Message-Id: <201103051736.04605.c47g@gmx.at> X-Y-GMX-Trusted: 0 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org, fs@freebsd.org Subject: Re: FS errors during unmount after dump'ing 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, 05 Mar 2011 17:01:10 -0000 --Boundary-00=_0ZmcNdyTe41Uqef Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Saturday 05 March 2011 10:36:40 Kostik Belousov wrote: > [Added fs, please remove current on reply]. > > On Sat, Mar 05, 2011 at 08:51:38AM +0100, Christian Gusenbauer wrote: > > Hi! > > > > Once in a week I backup my PC using amanda (which uses dump(8)). > > Subsequently unmounting a filesystem (or during shutdown) I get errors > > like these: > > > > handle_workitem_freeblocks: inode 3579904 block count 384 > > handle_workitem_freeblocks: inode 3579962 block count 384 > > /spare: unmount pending error: blocks 768 files 0 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2510 > > softdep_waitidle: Failed to flush worklist for 0xc5be2510 > > /data: unmount pending error: blocks 84 files 0 > > > > Note, I get these messages *only* after dumping filesystems! > > > > Is there anything wrong with my filesystems? > > > > Any clues? > > No clues, you did not provided information even to start looking. > > What version of the OS you are using ? > How do you call dump, in particular, did you specified -L ? > Are there any hung (unkillable) processes after the issue appeared ? > Please show all kernel messages, not only the tail of it. Hi! I'm running current revision 219265. Amanda calls dump like this (ps ax output): 2607 ?? DL 0:00.04 dump 0ubLshf 64 1048576 0 - /dev/label/home (dump) so the -L is specified. There are no hung processes. I attach a compressed dmesg output. It appears to me, that the 'handle_workitem_freeblocks' message is printed during the backup. The other messages are printed during shutdown. Thanks, Christian. --Boundary-00=_0ZmcNdyTe41Uqef-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 5 18:13:15 2011 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 2E52B106564A; Sat, 5 Mar 2011 18:13:15 +0000 (UTC) (envelope-from c.kworr@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 7FD4E8FC17; Sat, 5 Mar 2011 18:13:14 +0000 (UTC) Received: by bwz12 with SMTP id 12so3076189bwz.13 for ; Sat, 05 Mar 2011 10:13:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hBgi/Uav+YSJXaDOJRVDrh/XPUg5RWSIyDvYUZWjhKY=; b=vrHKQO0eyHujPbnZ4bTy0Tbm4TYM4x5H82FYWSb5NUL3zENsQnY6qdVu/6zwhd/oXv uqVa9o4auyzFuRXg0qVh01dkS//Rp5G6gz0IvR7ftKTk0lGOE9LgNnYgOrDgoDJpg/0K T09CTtPzbtmb2Lt9aVEEOjbf9kao8ooZDec1U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=T3I87fPMXyercDR30fZ9TEVc+++xT/7w8qGlgzyVRcTqSRqAy5N02j/zNn/fTlfVwU EVYqQZhgLicbDMPCIkgRA8zEXPPfQFMvDgichiwyNIjCNE2+oTajvjNeF4OA2Cv1eSqa STh/irmzGLLG78W0br/5+y6WYXqungCu6s/eM= Received: by 10.204.38.88 with SMTP id a24mr124809bke.130.1299347116407; Sat, 05 Mar 2011 09:45:16 -0800 (PST) Received: from limbo.lan ([193.33.173.33]) by mx.google.com with ESMTPS id q18sm496744bka.15.2011.03.05.09.45.14 (version=SSLv3 cipher=OTHER); Sat, 05 Mar 2011 09:45:15 -0800 (PST) Message-ID: <4D7276A9.6000905@gmail.com> Date: Sat, 05 Mar 2011 19:45:13 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; uk-UA; rv:1.9.2.14) Gecko/20110302 Thunderbird/3.1.8 MIME-Version: 1.0 To: lhmwzy References: <20110227202957.GD1992@garage.freebsd.pl> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: HEADS UP: ZFSv28 is in! 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, 05 Mar 2011 18:13:15 -0000 28.02.2011 15:24, lhmwzy wrote: > Tks for PJD's work for zfs. > > Would V28 is the last version of zfs because oracle don't open the zfs > code after V28? 1. Oracle opens the code, but only after some time. AFAIR they do open the code after the major releases. 2. All head developers have quit Oracle. They say technology is complete an should go on by itself. 3. With current work going on in Illumos aren't we sharing the role of 'core' for ZFS development? -- Sphinx of black quartz judge my vow.