From owner-freebsd-fs@FreeBSD.ORG Sun Apr 12 03:37:02 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B60D92B1 for ; Sun, 12 Apr 2015 03:37:02 +0000 (UTC) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by mx1.freebsd.org (Postfix) with ESMTP id 4F461F88 for ; Sun, 12 Apr 2015 03:37:01 +0000 (UTC) Received: from ppp118-210-45-229.lns20.adl2.internode.on.net (HELO leader.local) ([118.210.45.229]) by ipmail04.adl6.internode.on.net with ESMTP; 12 Apr 2015 13:01:53 +0930 Message-ID: <5529E727.9050800@ShaneWare.Biz> Date: Sun, 12 Apr 2015 13:01:51 +0930 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: javocado , FreeBSD Filesystems Subject: Re: Migrating ZFS from 8.3 to 10.1 References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2015 03:37:02 -0000 On 11/04/2015 07:13, javocado wrote: > Hello, > > I am planning to migrate (upgrade) my system from FreeBSD 8.3 RELEASE to > 10.1 RELEASE (both amd64). My zfs pool exists on it's own physical > device(s) so my upgrade will consist of: > > 1. install FreeBSD 10.1 on boot device (in a temp system) > 2. remove 8.3 boot device (from production system) > 3. install new 10.1 boot device and boot up production system > 4. re-mount zfs FS > > My question is, what do I need to know about how this change will affect or > impact the zpool and datasets? Is there any chance zfs data could be lost > or destroyed? Might there be a performance loss due to version differences? > Is upgrading the zpool (once booted to 10.1) strongly advised? Any > downsides or dangers there? Once you upgrade your zpool in 10.1 you can't mount it in < 10.1 I think you can selectively enable features if you want to keep old system compatibility. Not sure if there is a list of what features are available for each system version. Exporting your zpool as you shutdown 8.x will make it easier to import into 10.1 > Some other info worth considering (production system): > > ZFS filesystem version 5 > ZFS storage pool version 28 > > Thanks! -- FreeBSD - the place to B...Storing Data Shane Ambler From owner-freebsd-fs@FreeBSD.ORG Sun Apr 12 03:49:21 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 15A264A4 for ; Sun, 12 Apr 2015 03:49:21 +0000 (UTC) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by mx1.freebsd.org (Postfix) with ESMTP id A1778C9 for ; Sun, 12 Apr 2015 03:49:20 +0000 (UTC) Received: from ppp118-210-45-229.lns20.adl2.internode.on.net (HELO leader.local) ([118.210.45.229]) by ipmail04.adl6.internode.on.net with ESMTP; 12 Apr 2015 13:19:15 +0930 Message-ID: <5529EB3A.8050508@ShaneWare.Biz> Date: Sun, 12 Apr 2015 13:19:14 +0930 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Matthias Gamsjager , freebsd-fs@freebsd.org Subject: Re: FreeBSD/ZFS on [HEAD] chews up memory References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2015 03:49:21 -0000 On 09/04/2015 20:41, Matthias Gamsjager wrote: > When you decided to use ZFS did you read up on the design of it? Most > of the RAM goes to ARC which caches all the read files for you. > Beside that you can tame the ARC with parameters and FreeBSD should > shrink the ARC when more memory is needed. That isn't the issue on 10.1 I have 8GB RAM and have set arc_max to 2G - 3 disk raidz Booting my machine with 10.1-RELEASE into single user mode and writing to disk can take wired up to 7G which locks up the machine and only takes 10 mins Even running a recent 10-STABLE build I can get over 6GB wired, but now I can allocate ram to pressure out the wired allocation, the arc amount reported in top stays relatively stable during this time. -- FreeBSD - the place to B...Storing Data Shane Ambler From owner-freebsd-fs@FreeBSD.ORG Sun Apr 12 16:54:22 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 23E1A950 for ; Sun, 12 Apr 2015 16:54:22 +0000 (UTC) Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A7BAEA7F for ; Sun, 12 Apr 2015 16:54:21 +0000 (UTC) X-AuditID: 1209190e-f79a76d000000d1b-02-552aa3361a2a Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 92.AC.03355.633AA255; Sun, 12 Apr 2015 12:54:14 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id t3CGsDVE020023; Sun, 12 Apr 2015 12:54:13 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t3CGsBiO020463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 12 Apr 2015 12:54:12 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t3CGsAVE025545; Sun, 12 Apr 2015 12:54:10 -0400 (EDT) Date: Sun, 12 Apr 2015 12:54:10 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: Garrett Wollman Subject: Re: ZFS compiler warnings In-Reply-To: <21800.25526.8680.435299@khavrinen.csail.mit.edu> Message-ID: References: <21800.25526.8680.435299@khavrinen.csail.mit.edu> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDIsWRmVeSWpSXmKPExsUixG6nomu2WCvU4H2vgsWxxz/ZHBg9Znya zxLAGMVlk5Kak1mWWqRvl8CVceLAJ5aCqQIVP5epNDB+5+li5OSQEDCR+LblCBOELSZx4d56 ti5GLg4hgcVMEo3Ld7FCOBsZJdZcnckI4RxikriwdAozSIuQQAOjxKe9gSA2i4C2xKr/IEWc HGwCahKP9zazQoxVlNh8ahJYvQhQzccll4FsDg5mASmJO2srQExhASWJ5VdZQCo4Bewkzjx9 BGbzCjgCHTePHWKTrcSGG0/ApogK6Eis3j8FqkZQ4uTMJ2A2s4CWxPLp21gmMArNQpKahSS1 gJFpFaNsSm6Vbm5iZk5xarJucXJiXl5qka6xXm5miV5qSukmRlCgckry7WD8elDpEKMAB6MS D++F35qhQqyJZcWVuYcYJTmYlER5Y0u1QoX4kvJTKjMSizPii0pzUosPMUpwMCuJ8M6YB5Tj TUmsrEotyodJSXOwKInzbvrBFyIkkJ5YkpqdmlqQWgSTleHgUJLgnbIQqFGwKDU9tSItM6cE Ic3EwQkynAdo+HWQGt7igsTc4sx0iPwpRkUpcd6dIAkBkERGaR5cLyyRvGIUB3pFmPcdSBUP MAnBdb8CGswENDhLBWxwSSJCSqqBkat777+XsTc+m/fLql+Q3HDjrb9NRNKbhCVXZim+nCl0 gft1yLXsvX6TWbZ6Lzex27A8hUv/szaLmtuN11vkzG++nH7Q+86ZwPgr0hd159cfb/z5wGCr mH3rj2XBs1etnaPrcOmZ/UQfl3OqTZGhJZ0sCapvK2MrP67/9veO0RPltq08lg1sYkosxRmJ hlrMRcWJAJQfKzP/AgAA Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2015 16:54:22 -0000 On Fri, 10 Apr 2015, Garrett Wollman wrote: > I notice on my 10.1 kernel builds warnings like the following: > > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:2855:12: warning: comparison of constant -1 with expression of type 'zfs_prop_t' is always true [-Wtautological-constant-out-of-range-compare] > if (prop != ZPROP_INVAL && !zfs_prop_inheritable(prop)) > ~~~~ ^ ~~~~~~~~~~~ > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3810:11: warning: comparison of constant -1 with expression of type 'zfs_prop_t' is always false [-Wtautological-constant-out-of-range-compare] > if (prop == ZPROP_INVAL) { > ~~~~ ^ ~~~~~~~~~~~ > > The warnings indicate that these checks are being optimized away by > clang. The code in head is the same. Does anyone have an idea of how > this should be fixed, in a way that would be acceptable upstream? (Do > we have someone who is the "official" liaison with the OpenZFS > project?) > > My guess is that the definition of the zfs_prop_t enum itself needs to > include these two constants explicitly -- but that also has the effect > of changing the type of ZPROP_INVAL, which then means that > zpool_prop_t needs to have its own version of "invalid property" > defined, and that then requires cascading changes in a bunch of other > places. n1256.pdf lists as a "common warning" (annex I) the case where a value is assigned to a variable of enumerated type and the value is not from the same set of enumerated constants, so any assignment of ZPROP_INVAL to a variable of type zpool_prop_t should trigger a warning with the current code. (If there are no such assignments, then why are we bothering to check against it?) > The following is a minimal change that fixes the warnings in the > kernel alone (beware whitespace lossage) -- I haven't checked the > userland side: It seems like the right thing to do, to me, but I am not really a ZFS guy. -Ben From owner-freebsd-fs@FreeBSD.ORG Sun Apr 12 21:00:32 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2CA5B591 for ; Sun, 12 Apr 2015 21:00:32 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 04087776 for ; Sun, 12 Apr 2015 21:00:32 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3CL0VKv034936 for ; Sun, 12 Apr 2015 21:00:31 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201504122100.t3CL0VKv034936@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Date: Sun, 12 Apr 2015 21:00:31 +0000 Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2015 21:00:32 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f 3 problems total for which you should take action. From owner-freebsd-fs@FreeBSD.ORG Mon Apr 13 14:58:21 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A78A22B for ; Mon, 13 Apr 2015 14:58:21 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70A0C77A for ; Mon, 13 Apr 2015 14:58:21 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3DEwL7H000886 for ; Mon, 13 Apr 2015 14:58:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 195746] zfs L2ARC wrong alloc/free size Date: Mon, 13 Apr 2015 14:58:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gkontos@aicom.gr X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 14:58:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195746 gkontos@aicom.gr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gkontos@aicom.gr --- Comment #2 from gkontos@aicom.gr --- I have exactly the same problem with 2X Intel DC S3500 Series 600GB ------------------------------------------------------------------------ ZFS Subsystem Report Mon Apr 13 10:56:52 2015 ------------------------------------------------------------------------ L2 ARC Summary: (DEGRADED) Passed Headroom: 69.29m Tried Lock Failures: 316.43k IO In Progress: 86 Low Memory Aborts: 648 Free on Write: 1.01m Writes While Full: 202.57k R/W Clashes: 1.32k Bad Checksums: 17.34m IO Errors: 3.23m SPA Mismatch: 49.06m L2 ARC Size: (Adaptive) 3.21 TiB Header Size: 0.19% 6.21 GiB L2 ARC Evicts: Lock Retries: 146 Upon Reading: 0 L2 ARC Breakdown: 103.52m Hit Ratio: 34.77% 35.99m Miss Ratio: 65.23% 67.53m Feeds: 1.28m L2 ARC Buffer: Bytes Scanned: 116.31 TiB Buffer Iterations: 1.28m List Iterations: 78.60m NULL List Iterations: 2.68m L2 ARC Writes: Writes Sent: 100.00% 620.76k ------------------------------------------------------------------------ NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 multipath/disk1 ONLINE 0 0 0 multipath/disk2 ONLINE 0 0 0 multipath/disk25 ONLINE 0 0 0 multipath/disk4 ONLINE 0 0 0 multipath/disk5 ONLINE 0 0 0 multipath/disk6 ONLINE 0 0 0 raidz2-1 ONLINE 0 0 0 multipath/disk7 ONLINE 0 0 0 multipath/disk8 ONLINE 0 0 0 multipath/disk9 ONLINE 0 0 0 multipath/disk26 ONLINE 0 0 0 multipath/disk11 ONLINE 0 0 0 multipath/disk12 ONLINE 0 0 0 raidz2-2 ONLINE 0 0 0 multipath/disk13 ONLINE 0 0 0 multipath/disk14 ONLINE 0 0 0 multipath/disk15 ONLINE 0 0 0 multipath/disk16 ONLINE 0 0 0 multipath/disk17 ONLINE 0 0 0 multipath/disk18 ONLINE 0 0 0 raidz2-3 ONLINE 0 0 0 multipath/disk19 ONLINE 0 0 0 multipath/disk20 ONLINE 0 0 0 multipath/disk21 ONLINE 0 0 0 multipath/disk22 ONLINE 0 0 0 multipath/disk23 ONLINE 0 0 0 multipath/disk24 ONLINE 0 0 0 logs mirror-4 ONLINE 0 0 0 gpt/zil0 ONLINE 0 0 0 gpt/zil1 ONLINE 0 0 0 cache gpt/cache0 ONLINE 0 0 0 gpt/cache1 ONLINE 0 0 0 spares multipath/disk3 AVAIL multipath/disk27 AVAIL multipath/disk28 AVAIL multipath/disk10 AVAIL -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Mon Apr 13 15:37:30 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 383AC921 for ; Mon, 13 Apr 2015 15:37:30 +0000 (UTC) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9507BCA for ; Mon, 13 Apr 2015 15:37:29 +0000 (UTC) Received: by lagv1 with SMTP id v1so60757208lag.3 for ; Mon, 13 Apr 2015 08:37:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphix.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DQo401mk3SKPrmQDfNM/7VOkswgCeZCNX4XBZCre158=; b=SuM0NtvmiJzvA0wYFyDJrGdYHOrYiCri0Y7kADvGlvuxt9njNM/lvG3jrHu63VnKVF //o9t52doxVsnD9UOhBTM4Z2GQvN7oHDMhgkiaprK3XMrfPucIUQ5IjpVxJs4p26fEnH oHkT4E265xLiG8pRwPrWhUfHC8JQYbQknGHNw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DQo401mk3SKPrmQDfNM/7VOkswgCeZCNX4XBZCre158=; b=bzUt1rTUI5WsVcVAQKLJqPjIkjzNXYQikErtrDHFjbDvovaaRt6qpkP2mm3VJnHtDi 0WutxVMDwhoD84NVL54bgR+icGZwoqQgphh8bdz5IAMTi8zsdMzL+PPSbjmYnwD2uf/d 0TeL+WkXUBxajnoAnnlObSX7wTZb0YNbgiMcXg8W4ctMLXXpdMEutvPuMP+PTL3hfihy Y2BzP8KZmq7q90Ri/u27uHom6OTlN8WEB1Ieci8/gzuqgCxksIi/9L1NXwoW8jgQGkDG Flv/CygFJdy784xuYMbPSAPQ64L190ZgPXXtih07Q7w44zikq+l1FO5U5/jAtgmqudNA h4nA== X-Gm-Message-State: ALoCoQmnPw90nAryR/elYjBarMCBf0l62/SYYBsGVm/qE2v1PkM38WVcLKhQ+dPrXROaIy89cJBQ MIME-Version: 1.0 X-Received: by 10.112.98.201 with SMTP id ek9mr13857118lbb.68.1428939447624; Mon, 13 Apr 2015 08:37:27 -0700 (PDT) Received: by 10.25.44.130 with HTTP; Mon, 13 Apr 2015 08:37:27 -0700 (PDT) In-Reply-To: <21800.25526.8680.435299@khavrinen.csail.mit.edu> References: <21800.25526.8680.435299@khavrinen.csail.mit.edu> Date: Mon, 13 Apr 2015 08:37:27 -0700 Message-ID: Subject: Re: ZFS compiler warnings From: Matthew Ahrens To: Garrett Wollman Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 15:37:30 -0000 On Fri, Apr 10, 2015 at 4:58 PM, Garrett Wollman wrote: > I notice on my 10.1 kernel builds warnings like the following: > > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:2855:12: > warning: comparison of constant -1 with expression of type 'zfs_prop_t' is > always true [-Wtautological-constant-out-of-range-compare] > if (prop != ZPROP_INVAL && !zfs_prop_inheritable(prop)) > ~~~~ ^ ~~~~~~~~~~~ > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3810:11: > warning: comparison of constant -1 with expression of type 'zfs_prop_t' is > always false [-Wtautological-constant-out-of-range-compare] > if (prop == ZPROP_INVAL) { > ~~~~ ^ ~~~~~~~~~~~ > > The warnings indicate that these checks are being optimized away by > clang. The code in head is the same. Does anyone have an idea of how > this should be fixed, in a way that would be acceptable upstream? (Do > we have someone who is the "official" liaison with the OpenZFS > project?) > You change makes sense to me. I'd be happy to see it go upstream in illumos too. --matt > > My guess is that the definition of the zfs_prop_t enum itself needs to > include these two constants explicitly -- but that also has the effect > of changing the type of ZPROP_INVAL, which then means that > zpool_prop_t needs to have its own version of "invalid property" > defined, and that then requires cascading changes in a bunch of other > places. > > The following is a minimal change that fixes the warnings in the > kernel alone (beware whitespace lossage) -- I haven't checked the > userland side: > > Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c > =================================================================== > --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c (revision > 281265) > +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c (working > copy) > @@ -332,7 +332,7 @@ > zprop_source_t src = ZPROP_SRC_DEFAULT; > zpool_prop_t prop; > > - if ((prop = zpool_name_to_prop(za.za_name)) == ZPROP_INVAL) > + if ((prop = zpool_name_to_prop(za.za_name)) == > ZPOOL_PROP_INVAL) > continue; > > switch (za.za_integer_length) { > @@ -422,7 +422,7 @@ > zpool_prop_t prop = zpool_name_to_prop(propname); > > switch (prop) { > - case ZPROP_INVAL: > + case ZPOOL_PROP_INVAL: > if (!zpool_prop_feature(propname)) { > error = SET_ERROR(EINVAL); > break; > @@ -662,7 +662,7 @@ > prop == ZPOOL_PROP_READONLY) > continue; > > - if (prop == ZPOOL_PROP_VERSION || prop == ZPROP_INVAL) { > + if (prop == ZPOOL_PROP_VERSION || prop == > ZPOOL_PROP_INVAL) { > uint64_t ver; > > if (prop == ZPOOL_PROP_VERSION) { > @@ -6308,7 +6308,7 @@ > spa_feature_t fid; > > switch (prop = zpool_name_to_prop(nvpair_name(elem))) { > - case ZPROP_INVAL: > + case ZPOOL_PROP_INVAL: > /* > * We checked this earlier in spa_prop_validate(). > */ > Index: sys/cddl/contrib/opensolaris/uts/common/sys/fs/zfs.h > =================================================================== > --- sys/cddl/contrib/opensolaris/uts/common/sys/fs/zfs.h (revision > 281265) > +++ sys/cddl/contrib/opensolaris/uts/common/sys/fs/zfs.h (working > copy) > @@ -152,7 +152,9 @@ > ZFS_PROP_SNAPSHOT_COUNT, > ZFS_PROP_REDUNDANT_METADATA, > ZFS_PROP_PREV_SNAP, > - ZFS_NUM_PROPS > + ZFS_NUM_PROPS, > + ZPROP_INVAL = -1, > + ZPROP_CONT = -2 > } zfs_prop_t; > > typedef enum { > @@ -196,14 +198,18 @@ > ZPOOL_PROP_FREEING, > ZPOOL_PROP_FRAGMENTATION, > ZPOOL_PROP_LEAKED, > - ZPOOL_NUM_PROPS > + ZPOOL_NUM_PROPS, > + ZPOOL_PROP_INVAL = -1, > + ZPOOL_PROP_CONT = -2 > } zpool_prop_t; > > /* Small enough to not hog a whole line of printout in zpool(1M). */ > #define ZPROP_MAX_COMMENT 32 > > +/* > #define ZPROP_CONT -2 > #define ZPROP_INVAL -1 > +*/ > > #define ZPROP_VALUE "value" > #define ZPROP_SOURCE "source" > > There is also one spot in zio_checksum.c that has a similar problem, > but in this case the issue is that it assumes that an out-of-range > value can be bitwise-or'ed with a small enum. (The C standard allows > the compiler to use an eight-bit integer type as the underlying type > of 'enum zio_checksum', so to bitwise-or it with ZIO_CHECKSUM_VERIFY, > defined to be 256, is undefined.) A similar change eliminates this > warning. (The effect in both cases is to convince the compiler to > model the enum with a larger underlying type.) > > -GAWollman > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Mon Apr 13 21:57:02 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5A21A06 for ; Mon, 13 Apr 2015 21:57:02 +0000 (UTC) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF12E6F for ; Mon, 13 Apr 2015 21:57:02 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CmBAC+OixV/95baINchD+DEMIHhHOCXAKBeBMBAQEBAQEBfYQmIwSBFhkCBFUGLogPp0aPVZZUAQEBAQYBAQEBAQEcj1wCFS8MgmiBRQWSep0NIoIDHIFsIoE0QX8BAQE X-IronPort-AV: E=Sophos;i="5.11,572,1422939600"; d="scan'208";a="203641714" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 13 Apr 2015 17:57:01 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 6B26BB3F47 for ; Mon, 13 Apr 2015 17:57:01 -0400 (EDT) Date: Mon, 13 Apr 2015 17:57:01 -0400 (EDT) From: Rick Macklem To: FreeBSD Filesystems Message-ID: <1831222043.18160009.1428962221426.JavaMail.root@uoguelph.ca> In-Reply-To: <935099613.18159086.1428962088350.JavaMail.root@uoguelph.ca> Subject: bugfix for nfsd commit for ZFS MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_18160007_1810024754.1428962221422" X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 21:57:02 -0000 ------=_Part_18160007_1810024754.1428962221422 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, mav@ identified a fairly serious problem with the NFS server when ZFS volumes are exported. After a series of Unstable Write RPCs, the NFS client will do a Commit RPC to ensure the data is safely on stable storage. The NFS server implementation did this with a loop running through the buffer cache blocks for smaller commit sizes. This obviously doesn't work for ZFS, since it doesn't use the buffer cache. To fix this, ZFS must always call VOP_FSYNC() instead of doing this loop. After discussion with mav@ and kib@, it seemed that the preferred solution is to have file systems that use the buffer cache set MNTK_USES_BCACHE, so that the NFS server's commit will always use VOP_FSYNC() for file systems that don't set this. Old file system modules that do not set the flag should be ok, since always calling VOP_FSYNC() may be suboptimal, but will still be correct. "unionfs" never sets this flag, since it would be incorrect if one of the file systems has it set and the other not set. (Since unionfs mounts cannot be exported for NFS, I think this is ok.) If anyone has comments w.r.t. this or would like to review the patch (already reviewed by kib@), I've attached the current patch. rick ------=_Part_18160007_1810024754.1428962221422 Content-Type: text/x-patch; name=commit.patch Content-Disposition: attachment; filename=commit.patch Content-Transfer-Encoding: base64 LS0tIGtlcm4vdmZzX3N1YnIuYy5zYXZjb21taXQJMjAxNS0wNC0xMSAyMDowNjo0Ny4wMDAwMDAw MDAgLTA0MDAKKysrIGtlcm4vdmZzX3N1YnIuYwkyMDE1LTA0LTExIDIwOjE0OjA2LjAwMDAwMDAw MCAtMDQwMApAQCAtMzEzNCw2ICszMTM0LDcgQEAgREJfU0hPV19DT01NQU5EKG1vdW50LCBkYl9z aG93X21vdW50KQogCU1OVF9LRVJOX0ZMQUcoTU5US19WR09ORV9XQUlURVIpOwogCU1OVF9LRVJO X0ZMQUcoTU5US19MT09LVVBfRVhDTF9ET1RET1QpOwogCU1OVF9LRVJOX0ZMQUcoTU5US19NQVJL RVIpOworCU1OVF9LRVJOX0ZMQUcoTU5US19VU0VTX0JDQUNIRSk7CiAJTU5UX0tFUk5fRkxBRyhN TlRLX05PQVNZTkMpOwogCU1OVF9LRVJOX0ZMQUcoTU5US19VTk1PVU5UKTsKIAlNTlRfS0VSTl9G TEFHKE1OVEtfTVdBSVQpOwotLS0gZnMvZnVzZS9mdXNlX3Zmc29wcy5jLnNhdmNvbW1pdAkyMDE1 LTA0LTEyIDE1OjU5OjIzLjAwMDAwMDAwMCAtMDQwMAorKysgZnMvZnVzZS9mdXNlX3Zmc29wcy5j CTIwMTUtMDQtMTIgMTY6MDU6MzQuMDAwMDAwMDAwIC0wNDAwCkBAIC0zMzcsNiArMzM3LDcgQEAg ZnVzZV92ZnNvcF9tb3VudChzdHJ1Y3QgbW91bnQgKm1wKQogCU1OVF9JTE9DSyhtcCk7CiAJbXAt Pm1udF9kYXRhID0gZGF0YTsKIAltcC0+bW50X2ZsYWcgfD0gTU5UX0xPQ0FMOworCW1wLT5tbnRf a2Vybl9mbGFnIHw9IE1OVEtfVVNFU19CQ0FDSEU7CiAJTU5UX0lVTkxPQ0sobXApOwogCS8qIFdl IG5lZWQgdGhpcyBoZXJlIGFzIHRoaXMgc2xvdCBpcyB1c2VkIGJ5IGdldG5ld3Zub2RlKCkgKi8K IAltcC0+bW50X3N0YXQuZl9pb3NpemUgPSBQQUdFX1NJWkU7Ci0tLSBmcy9udWxsZnMvbnVsbF92 ZnNvcHMuYy5zYXZjb21taXQJMjAxNS0wNC0xMSAyMDo0MDowMS4wMDAwMDAwMDAgLTA0MDAKKysr IGZzL251bGxmcy9udWxsX3Zmc29wcy5jCTIwMTUtMDQtMTEgMjA6NDQ6MzYuMDAwMDAwMDAwIC0w NDAwCkBAIC0xOTksNyArMTk5LDcgQEAgbnVsbGZzX21vdW50KHN0cnVjdCBtb3VudCAqbXApCiAJ fQogCW1wLT5tbnRfa2Vybl9mbGFnIHw9IE1OVEtfTE9PS1VQX0VYQ0xfRE9URE9UOwogCW1wLT5t bnRfa2Vybl9mbGFnIHw9IGxvd2Vycm9vdHZwLT52X21vdW50LT5tbnRfa2Vybl9mbGFnICYKLQkg ICAgTU5US19TVVNQRU5EQUJMRTsKKwkgICAgKE1OVEtfU1VTUEVOREFCTEUgfCBNTlRLX1VTRVNf QkNBQ0hFKTsKIAlNTlRfSVVOTE9DSyhtcCk7CiAJbXAtPm1udF9kYXRhID0geG1wOwogCXZmc19n ZXRuZXdmc2lkKG1wKTsKLS0tIGZzL25hbmRmcy9uYW5kZnNfdmZzb3BzLmMuc2F2Y29tbWl0CTIw MTUtMDQtMTIgMTY6MDc6NDkuMDAwMDAwMDAwIC0wNDAwCisrKyBmcy9uYW5kZnMvbmFuZGZzX3Zm c29wcy5jCTIwMTUtMDQtMTIgMTY6MTA6MDguMDAwMDAwMDAwIC0wNDAwCkBAIC0xMzkxLDYgKzEz OTEsNyBAQCBuYW5kZnNfbW91bnRmcyhzdHJ1Y3Qgdm5vZGUgKmRldnZwLCBzdHJ1CiAJbm1wLT5u bV9yb25seSA9IHJvbmx5OwogCU1OVF9JTE9DSyhtcCk7CiAJbXAtPm1udF9mbGFnIHw9IE1OVF9M T0NBTDsKKwltcC0+bW50X2tlcm5fZmxhZyB8PSBNTlRLX1VTRVNfQkNBQ0hFOwogCU1OVF9JVU5M T0NLKG1wKTsKIAlubXAtPm5tX25hbmRmc2RldiA9IG5hbmRmc2RldjsKIAkvKiBBZGQgb3VyIG1v dW50cG9pbnQgKi8KLS0tIGZzL2V4dDJmcy9leHQyX3Zmc29wcy5jLnNhdmNvbW1pdAkyMDE1LTA0 LTEyIDE2OjE2OjE0LjAwMDAwMDAwMCAtMDQwMAorKysgZnMvZXh0MmZzL2V4dDJfdmZzb3BzLmMJ MjAxNS0wNC0xMiAxNjoxNjo0OS4wMDAwMDAwMDAgLTA0MDAKQEAgLTY3NCw3ICs2NzQsOCBAQCBl eHQyX21vdW50ZnMoc3RydWN0IHZub2RlICpkZXZ2cCwgc3RydWN0CiAJICogSW5pdGlhbGl6ZSBm aWxlc3lzdGVtIHN0YXQgaW5mb3JtYXRpb24gaW4gbW91bnQgc3RydWN0LgogCSAqLwogCU1OVF9J TE9DSyhtcCk7Ci0JbXAtPm1udF9rZXJuX2ZsYWcgfD0gTU5US19MT09LVVBfU0hBUkVEIHwgTU5U S19FWFRFTkRFRF9TSEFSRUQ7CisJbXAtPm1udF9rZXJuX2ZsYWcgfD0gTU5US19MT09LVVBfU0hB UkVEIHwgTU5US19FWFRFTkRFRF9TSEFSRUQgfAorCSAgICBNTlRLX1VTRVNfQkNBQ0hFOwogCU1O VF9JVU5MT0NLKG1wKTsKIAlyZXR1cm4gKDApOwogb3V0OgotLS0gZnMvbmZzc2VydmVyL25mc19u ZnNkcG9ydC5jLnNhdmNvbW1pdAkyMDE1LTA0LTExIDIwOjAxOjE5LjAwMDAwMDAwMCAtMDQwMAor KysgZnMvbmZzc2VydmVyL25mc19uZnNkcG9ydC5jCTIwMTUtMDQtMTIgMTc6MDA6MjguMDAwMDAw MDAwIC0wNDAwCkBAIC0xMjc0LDcgKzEyNzQsOCBAQCBuZnN2bm9fZnN5bmMoc3RydWN0IHZub2Rl ICp2cCwgdV9pbnQ2NF90CiAJICogYnl0ZSBjb3VudCBwYXJhbWV0ZXJzIHNvIGNhbGwgVk9QX0ZT WU5DIHRoZSB3aG9sZSBmaWxlIGZvciBub3cuCiAJICogVGhlIHNhbWUgaXMgdHJ1ZSBmb3IgTkZT djQ6IFJGQyAzNTMwIFNlYy4gMTQuMi4zLgogCSAqLwotCWlmIChjbnQgPT0gMCB8fCBjbnQgPiBN QVhfQ09NTUlUX0NPVU5UKSB7CisJaWYgKGNudCA9PSAwIHx8IGNudCA+IE1BWF9DT01NSVRfQ09V TlQgfHwKKwkgICAgKHZwLT52X21vdW50LT5tbnRfa2Vybl9mbGFnICYgTU5US19VU0VTX0JDQUNI RSkgPT0gMCkgewogCQkvKgogCQkgKiBHaXZlIHVwIGFuZCBkbyB0aGUgd2hvbGUgdGhpbmcKIAkJ ICovCi0tLSBmcy9tc2Rvc2ZzL21zZG9zZnNfdmZzb3BzLmMuc2F2Y29tbWl0CTIwMTUtMDQtMTIg MTY6MTg6MzkuMDAwMDAwMDAwIC0wNDAwCisrKyBmcy9tc2Rvc2ZzL21zZG9zZnNfdmZzb3BzLmMJ MjAxNS0wNC0xMyAwODo0Njo1MC4wMDAwMDAwMDAgLTA0MDAKQEAgLTc1OSw2ICs3NTksNyBAQCBt b3VudG1zZG9zZnMoc3RydWN0IHZub2RlICpkZXZ2cCwgc3RydWN0CiAJbXAtPm1udF9zdGF0LmZf ZnNpZC52YWxbMV0gPSBtcC0+bW50X3ZmYy0+dmZjX3R5cGVudW07CiAJTU5UX0lMT0NLKG1wKTsK IAltcC0+bW50X2ZsYWcgfD0gTU5UX0xPQ0FMOworCW1wLT5tbnRfa2Vybl9mbGFnIHw9IE1OVEtf VVNFU19CQ0FDSEU7CiAJTU5UX0lVTkxPQ0sobXApOwogCiAJaWYgKHBtcC0+cG1fZmxhZ3MgJiBN U0RPU0ZTX0xBUkdFRlMpCi0tLSBmcy9uZnNjbGllbnQvbmZzX2NsdmZzb3BzLmMuc2F2Y29tbWl0 CTIwMTUtMDQtMTIgMTY6MjM6MTcuMDAwMDAwMDAwIC0wNDAwCisrKyBmcy9uZnNjbGllbnQvbmZz X2NsdmZzb3BzLmMJMjAxNS0wNC0xMiAxNjoyMzo1NC4wMDAwMDAwMDAgLTA0MDAKQEAgLTExOTgs NyArMTE5OCw4IEBAIG5mc19tb3VudChzdHJ1Y3QgbW91bnQgKm1wKQogb3V0OgogCWlmICghZXJy b3IpIHsKIAkJTU5UX0lMT0NLKG1wKTsKLQkJbXAtPm1udF9rZXJuX2ZsYWcgfD0gTU5US19MT09L VVBfU0hBUkVEIHwgTU5US19OT19JT1BGOworCQltcC0+bW50X2tlcm5fZmxhZyB8PSBNTlRLX0xP T0tVUF9TSEFSRUQgfCBNTlRLX05PX0lPUEYgfAorCQkgICAgTU5US19VU0VTX0JDQUNIRTsKIAkJ TU5UX0lVTkxPQ0sobXApOwogCX0KIAlyZXR1cm4gKGVycm9yKTsKLS0tIHN5cy9tb3VudC5oLnNh dmNvbW1pdAkyMDE1LTA0LTExIDIwOjAzOjMwLjAwMDAwMDAwMCAtMDQwMAorKysgc3lzL21vdW50 LmgJMjAxNS0wNC0xMSAyMDoxMjozNS4wMDAwMDAwMDAgLTA0MDAKQEAgLTM1NSw2ICszNTUsNyBA QCB2b2lkICAgICAgICAgIF9fbW50X3Zub2RlX21hcmtlcmZyZWVfYWN0CiAjZGVmaW5lCU1OVEtf TE9PS1VQX0VYQ0xfRE9URE9UCTB4MDAwMDA4MDAKICNkZWZpbmUJTU5US19NQVJLRVIJCTB4MDAw MDEwMDAKICNkZWZpbmUJTU5US19VTk1BUFBFRF9CVUZTCTB4MDAwMDIwMDAKKyNkZWZpbmUJTU5U S19VU0VTX0JDQUNIRQkweDAwMDA0MDAwIC8qIEZTIHVzZXMgdGhlIGJ1ZmZlciBjYWNoZS4gKi8K ICNkZWZpbmUgTU5US19OT0FTWU5DCTB4MDA4MDAwMDAJLyogZGlzYWJsZSBhc3luYyAqLwogI2Rl ZmluZSBNTlRLX1VOTU9VTlQJMHgwMTAwMDAwMAkvKiB1bm1vdW50IGluIHByb2dyZXNzICovCiAj ZGVmaW5lCU1OVEtfTVdBSVQJMHgwMjAwMDAwMAkvKiB3YWl0aW5nIGZvciB1bm1vdW50IHRvIGZp bmlzaCAqLwotLS0gdWZzL2Zmcy9mZnNfdmZzb3BzLmMuc2F2Y29tbWl0CTIwMTUtMDQtMTEgMjA6 MTU6MDEuMDAwMDAwMDAwIC0wNDAwCisrKyB1ZnMvZmZzL2Zmc192ZnNvcHMuYwkyMDE1LTA0LTEx IDIwOjE2OjA3LjAwMDAwMDAwMCAtMDQwMApAQCAtMTA1NSw3ICsxMDU1LDggQEAgZmZzX21vdW50 ZnMoZGV2dnAsIG1wLCB0ZCkKIAkgKi8KIAlNTlRfSUxPQ0sobXApOwogCW1wLT5tbnRfa2Vybl9m bGFnIHw9IE1OVEtfTE9PS1VQX1NIQVJFRCB8IE1OVEtfRVhURU5ERURfU0hBUkVEIHwKLQkgICAg TU5US19OT19JT1BGIHwgTU5US19VTk1BUFBFRF9CVUZTIHwgTU5US19TVVNQRU5EQUJMRTsKKwkg ICAgTU5US19OT19JT1BGIHwgTU5US19VTk1BUFBFRF9CVUZTIHwgTU5US19TVVNQRU5EQUJMRSB8 CisJICAgIE1OVEtfVVNFU19CQ0FDSEU7CiAJTU5UX0lVTkxPQ0sobXApOwogI2lmZGVmIFVGU19F WFRBVFRSCiAjaWZkZWYgVUZTX0VYVEFUVFJfQVVUT1NUQVJUCg== ------=_Part_18160007_1810024754.1428962221422-- From owner-freebsd-fs@FreeBSD.ORG Mon Apr 13 22:19:16 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB6701A8 for ; Mon, 13 Apr 2015 22:19:16 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B79610C for ; Mon, 13 Apr 2015 22:19:16 +0000 (UTC) Received: by lbbqq2 with SMTP id qq2so70577840lbb.3 for ; Mon, 13 Apr 2015 15:19:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zR+Vr6hQaVcAl7Pp6ko2IcCHR8vL+9R5nxw5yNXoHw8=; b=JCZ64XYZljhhRDF9PEm7BxsoTe3z211dKasnZDEzmWyfPwnxl+y6o0i1mgtV+qvPSC xfr8UQmjSBn6C3v3qQQ2HdgI0GStclGJfdSqp2X55Lfo0htYr4BEOT0xYzzEUOfCUzzP wzwvNSNXFnLujRSC7k28CvdQqs9rJlA1OhiHEgfb8A/nQZR1aC0/A6msFDaWD6GDVdjy rXGx7JpVpvvo1BF3714Pl+cYOvlPgZIGRNyD7JR6PxUcprr8DUWzqdGBgnecgnbXdH0J BvSBvNt/wRpfeA1i7HX2vkFLWzVu9yrzrgj7u9Bs//Ky+qA8UAEC9/c2AqouT5FSdU9i yUlw== MIME-Version: 1.0 X-Received: by 10.112.205.225 with SMTP id lj1mr6043503lbc.27.1428963554348; Mon, 13 Apr 2015 15:19:14 -0700 (PDT) Received: by 10.114.18.137 with HTTP; Mon, 13 Apr 2015 15:19:14 -0700 (PDT) In-Reply-To: <5529E727.9050800@ShaneWare.Biz> References: <5529E727.9050800@ShaneWare.Biz> Date: Mon, 13 Apr 2015 15:19:14 -0700 Message-ID: Subject: Re: Migrating ZFS from 8.3 to 10.1 From: javocado To: Shane Ambler Cc: FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 22:19:16 -0000 Thank you for that info. A couple more questions... So would this sequence go like this?: freebsd 8.3# zpool export tank (shut down) (replace boot device with new device pre-loaded with 10.1) (boot up to 10.1) freebsd 10.1# zpool upgrade tank freebsd 10.1# zpool import tank And that command should complete quickly, regardless of the size of the pool, number of inodes, etc, correct? Next, we would want to consider what's involved with upgrading the zfs filesystems. We have many filesystems (~500-1000) with 40-70 TB of data (pool just under 100 TB in size) with thousands of snapshots (evenly spread amongst the filesystems), and some filesystems are very dense with millions of inodes. - What are the advantages, disadvantages, pitfalls and caveats to be aware of here? We know that the filesystems will no longer be readable by older systems. Is there anything else? - We wonder if the time it will take to upgrade all these is substantial- i.e. will the upgrade parse through all this data in each filesystem or just flip a few switches in each filesystem, completing quickly? - Any impact on the (old) snapshots already in place? Any issues with having a mix of old and new (post upgrade) snapshots in a filesystem? On Sat, Apr 11, 2015 at 8:31 PM, Shane Ambler wrote: > On 11/04/2015 07:13, javocado wrote: > >> Hello, >> >> I am planning to migrate (upgrade) my system from FreeBSD 8.3 RELEASE to >> 10.1 RELEASE (both amd64). My zfs pool exists on it's own physical >> device(s) so my upgrade will consist of: >> >> 1. install FreeBSD 10.1 on boot device (in a temp system) >> 2. remove 8.3 boot device (from production system) >> 3. install new 10.1 boot device and boot up production system >> 4. re-mount zfs FS >> >> My question is, what do I need to know about how this change will affect >> or >> impact the zpool and datasets? Is there any chance zfs data could be lost >> or destroyed? Might there be a performance loss due to version >> differences? >> Is upgrading the zpool (once booted to 10.1) strongly advised? Any >> downsides or dangers there? >> > > Once you upgrade your zpool in 10.1 you can't mount it in < 10.1 > I think you can selectively enable features if you want to keep old > system compatibility. Not sure if there is a list of what features are > available for each system version. > > Exporting your zpool as you shutdown 8.x will make it easier to import > into 10.1 > > > Some other info worth considering (production system): >> >> ZFS filesystem version 5 >> ZFS storage pool version 28 >> >> Thanks! >> > > > -- > FreeBSD - the place to B...Storing Data > > Shane Ambler > > From owner-freebsd-fs@FreeBSD.ORG Tue Apr 14 00:19:42 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5F65C56B for ; Tue, 14 Apr 2015 00:19:42 +0000 (UTC) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8A3AF84 for ; Tue, 14 Apr 2015 00:19:41 +0000 (UTC) Received: by wiun10 with SMTP id n10so3350092wiu.1 for ; Mon, 13 Apr 2015 17:19:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UkR2QlpyolncqtoTCXYxTwLHbJkjHTftr0fcFqStJWU=; b=iuf2CxST33y6OahnzeX2PkJ6TalZxQpneijA1Y4VQF7U+fm/wvb/b/Mrk709xyxK0s +XmxSb1vBFBGn2YrzFU6uw5wzbKgoE+efUOnM4hCzqDVHGZDsjtzkjXbSj6aG3KHcPcS mphAXUU4IsKApSfxKxL6Zy7O0bNhlX+SCZMd2rZA0/gkv/JdnGI7RILT7ZVfgyS0MOEe HMfAyO+OQj7VKVmDxsO1sRqoc029meT5W0B4YSpe65YtHQ4LtO+l8Fa1QgqcAwYERHqC /dT51M6hmveCB6aeFIy4PBKuqtHTuZL+biWizD5ZVkx0KRKlepzM5ZlTOCBxrsIHOIpd JLew== X-Gm-Message-State: ALoCoQlHAggRmk8S5sksU59Q9JjdSpiMPYp/JnHJPSszwgZ/otesQg1Cv8d6rYhIIPcxLptayvkF X-Received: by 10.194.6.228 with SMTP id e4mr32952751wja.63.1428970774602; Mon, 13 Apr 2015 17:19:34 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id l10sm13540513wje.15.2015.04.13.17.19.33 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Apr 2015 17:19:33 -0700 (PDT) Message-ID: <552C5D1C.4090708@multiplay.co.uk> Date: Tue, 14 Apr 2015 01:19:40 +0100 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Re: [Bug 195746] zfs L2ARC wrong alloc/free size References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2015 00:19:42 -0000 There is a know upstream issue regarding L2ARC accounting see: https://reviews.csiden.org/r/175/ On 13/04/2015 15:58, bugzilla-noreply@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195746 > > gkontos@aicom.gr changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |gkontos@aicom.gr > > --- Comment #2 from gkontos@aicom.gr --- > I have exactly the same problem with 2X Intel DC S3500 Series 600GB > > ------------------------------------------------------------------------ > ZFS Subsystem Report Mon Apr 13 10:56:52 2015 > ------------------------------------------------------------------------ > > L2 ARC Summary: (DEGRADED) > Passed Headroom: 69.29m > Tried Lock Failures: 316.43k > IO In Progress: 86 > Low Memory Aborts: 648 > Free on Write: 1.01m > Writes While Full: 202.57k > R/W Clashes: 1.32k > Bad Checksums: 17.34m > IO Errors: 3.23m > SPA Mismatch: 49.06m > > L2 ARC Size: (Adaptive) 3.21 TiB > Header Size: 0.19% 6.21 GiB > > L2 ARC Evicts: > Lock Retries: 146 > Upon Reading: 0 > > L2 ARC Breakdown: 103.52m > Hit Ratio: 34.77% 35.99m > Miss Ratio: 65.23% 67.53m > Feeds: 1.28m > > L2 ARC Buffer: > Bytes Scanned: 116.31 TiB > Buffer Iterations: 1.28m > List Iterations: 78.60m > NULL List Iterations: 2.68m > > L2 ARC Writes: > Writes Sent: 100.00% 620.76k > ------------------------------------------------------------------------ > > > NAME STATE READ WRITE CKSUM > storage ONLINE 0 0 0 > raidz2-0 ONLINE 0 0 0 > multipath/disk1 ONLINE 0 0 0 > multipath/disk2 ONLINE 0 0 0 > multipath/disk25 ONLINE 0 0 0 > multipath/disk4 ONLINE 0 0 0 > multipath/disk5 ONLINE 0 0 0 > multipath/disk6 ONLINE 0 0 0 > raidz2-1 ONLINE 0 0 0 > multipath/disk7 ONLINE 0 0 0 > multipath/disk8 ONLINE 0 0 0 > multipath/disk9 ONLINE 0 0 0 > multipath/disk26 ONLINE 0 0 0 > multipath/disk11 ONLINE 0 0 0 > multipath/disk12 ONLINE 0 0 0 > raidz2-2 ONLINE 0 0 0 > multipath/disk13 ONLINE 0 0 0 > multipath/disk14 ONLINE 0 0 0 > multipath/disk15 ONLINE 0 0 0 > multipath/disk16 ONLINE 0 0 0 > multipath/disk17 ONLINE 0 0 0 > multipath/disk18 ONLINE 0 0 0 > raidz2-3 ONLINE 0 0 0 > multipath/disk19 ONLINE 0 0 0 > multipath/disk20 ONLINE 0 0 0 > multipath/disk21 ONLINE 0 0 0 > multipath/disk22 ONLINE 0 0 0 > multipath/disk23 ONLINE 0 0 0 > multipath/disk24 ONLINE 0 0 0 > logs > mirror-4 ONLINE 0 0 0 > gpt/zil0 ONLINE 0 0 0 > gpt/zil1 ONLINE 0 0 0 > cache > gpt/cache0 ONLINE 0 0 0 > gpt/cache1 ONLINE 0 0 0 > spares > multipath/disk3 AVAIL > multipath/disk27 AVAIL > multipath/disk28 AVAIL > multipath/disk10 AVAIL > From owner-freebsd-fs@FreeBSD.ORG Tue Apr 14 02:36:58 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9EC2F07 for ; Tue, 14 Apr 2015 02:36:58 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B0CE2F7C for ; Tue, 14 Apr 2015 02:36:58 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3E2awXb059591 for ; Tue, 14 Apr 2015 02:36:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Tue, 14 Apr 2015 02:36:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2015 02:36:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 14 07:39:05 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B501526 for ; Tue, 14 Apr 2015 07:39:05 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 517D42BD for ; Tue, 14 Apr 2015 07:39:05 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3E7d5lQ086822 for ; Tue, 14 Apr 2015 07:39:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Tue, 14 Apr 2015 07:39:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2015 07:39:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 Steven Hartland changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smh@FreeBSD.org --- Comment #1 from Steven Hartland --- Have you tried importing with 10-Stable or current to see if they help? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 14 18:05:44 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9509AF1D for ; Tue, 14 Apr 2015 18:05:44 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 581A58CC for ; Tue, 14 Apr 2015 18:05:44 +0000 (UTC) Received: from [127.0.0.1] (users-nat.in.devexperts.com [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 8480356400 for ; Tue, 14 Apr 2015 21:05:21 +0300 (MSK) Message-ID: <552D56E0.2040307@FreeBSD.org> Date: Tue, 14 Apr 2015 21:05:20 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: =?UTF-8?B?WkZTOiByZXBsYWNlIGFsbCBkaXNrcyBvbiBuZXcsIGxhcmdlciBvbmU=?= =?UTF-8?B?cywgaW4gbWlycm9yIG9yIHpyYWlkWzJdIOKAlCB3aWxsIGl0IHdvcms/?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2015 18:05:44 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Say, I have ZFS pool consist of raidz vdev with 3x1TB disks. It is 2Tb effective storage space, right? Now I could remove 1 disk (as failed one) and replace it with new, 2TB HDD. After resilvering I could replace second 1TB HDD, and, then, third one. Now I have raidz vdev with 3x2TB disks. Will I have 4TB effective storage space in my poo l? I know, that it is impossible to add NEW disk to raidz, but here is replacement smaller disks with larger ones, one-by-one. The same question could be asked about mirror and raidz2/raidz3 :) - -- // Lev Serebryakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJVLVbfXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePRBEQALq1JdNodoJ124n00xIb+cL/ mMNHB16nuPgov66KULkJf4a0AtVilfcofq0DPg0puyTnZr5Q/1UJYK+43NTHW2fj i4ew3LwKnj1D0Ej7svwsm5hYqJG/GQU0i07l9k23BYiBKanT4LedtKJlwgHAIq97 YU94wUTPw93hAe3w738qlyAbj09rSJg3IU7U2i2ISVNfxNFj7FrzJ5SL9S1NFG3u 5PR7DRH1/0R/s0zojjg4xhwJ7PiGOC1wjsa9Dfub1JU8bpMbti0srztKnUKCm/Zl hqXJAB9e7xDZa8iZjeUfmyX5XIlZN/N9urrGmxXo8SMk71Z0MEWVdKvLTV1BNo4I RS9v3mQHjuP8lR1AC1IWkLGrXduId4kKQORwiGSjSb9376eqhKYuSSjBGEfBYUdL EE1PtsXXQ1bPznU/nWR+MguwI9IYQko4EzUCtxba9Asf9MvXwsIA8Cp5ZJ6De6/g AXx9crdk1Cj7azOYQJkSR/mmiZfDlcbwhbvJ1o1beGmlCvpz4D7+6PT+lAr8K6vA sJKRVpEYtdHsk5eOPhRRTMuD0r18GKhvJMUBOBx/EKqUxf7t8rIf8ajyzXde6l7o XNji2beX3oGtZ7nutp/5ovp2YAo1LI3EWQssZ/5gUWSh1+YRqZSUm4KmE0GBHAhM epOndpbBh15dAI0zCJUR =Kxwu -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Tue Apr 14 18:13:46 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 494801DE; Tue, 14 Apr 2015 18:13:46 +0000 (UTC) Received: from webmail2.jnielsen.net (webmail2.jnielsen.net [50.114.224.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 265CC9D6; Tue, 14 Apr 2015 18:13:45 +0000 (UTC) Received: from [10.10.1.196] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by webmail2.jnielsen.net (8.15.1/8.15.1) with ESMTPSA id t3EIDfeA088917 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Apr 2015 12:13:43 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail2.jnielsen.net: Host office.betterlinux.com [199.58.199.60] claimed to be [10.10.1.196] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: =?utf-8?Q?Re=3A_ZFS=3A_replace_all_disks_on_new=2C_larger_ones?= =?utf-8?Q?=2C_in_mirror_or_zraid=5B2=5D_=E2=80=94_will_it_work?= =?utf-8?Q?=3F?= From: John Nielsen In-Reply-To: <552D56E0.2040307@FreeBSD.org> Date: Tue, 14 Apr 2015 12:13:40 -0600 Cc: freebsd-fs@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <58B1231B-5408-443F-B5E3-4086CE618D47@jnielsen.net> References: <552D56E0.2040307@FreeBSD.org> To: lev@FreeBSD.org X-Mailer: Apple Mail (2.2098) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2015 18:13:46 -0000 On Apr 14, 2015, at 12:05 PM, Lev Serebryakov wrote: > Say, I have ZFS pool consist of raidz vdev with 3x1TB disks. It is > 2Tb effective storage space, right? Now I could remove 1 disk (as > failed one) and replace it with new, 2TB HDD. After resilvering I > could replace second 1TB HDD, and, then, third one. Now I have raidz > vdev with 3x2TB disks. Will I have 4TB effective storage space in my = poo > l? >=20 > I know, that it is impossible to add NEW disk to raidz, but here is > replacement smaller disks with larger ones, one-by-one. >=20 > The same question could be asked about mirror and raidz2/raidz3 :) Yes, that is the recommended way to increase the capacity of an existing = vdev and I have done that more than once. Once you have replaced all the = devices and the vdev is finished resilvering, a =E2=80=9Czpool online -e = =E2=80=A6=E2=80=9D will make the additional space available. JN From owner-freebsd-fs@FreeBSD.ORG Tue Apr 14 21:02:52 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5A3DF28F for ; Tue, 14 Apr 2015 21:02:52 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 26BCFFEE for ; Tue, 14 Apr 2015 21:02:52 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3EL2pZk021602 for ; Tue, 14 Apr 2015 21:02:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Tue, 14 Apr 2015 21:02:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: drsmithy@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2015 21:02:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 --- Comment #2 from Chris Smith --- (In reply to Steven Hartland from comment #1) Hi, Tried with 10-STABLE this morning and no luck, though it's a different line reported in space_map.c. root@freebsd:~ # cat /var/crash/core.txt.0 freebsd dumped core - see /var/crash/vmcore.0 Tue Apr 14 20:58:16 UTC 2015 FreeBSD freebsd 10.1-STABLE FreeBSD 10.1-STABLE #0 r281528: Tue Apr 14 20:40:23 UTC 2015 root@freebsd:/usr/obj/usr/src/sys/GENERIC amd64 panic: solaris assert: range_tree_space(rt) == space (0x6b34cb000 == 0x6b3525000), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/space_map.c, line: 131 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: panic: solaris assert: range_tree_space(rt) == space (0x6b34cb000 == 0x6b3525000), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/space_map.c, line: 131 cpuid = 1 KDB: stack backtrace: #0 0xffffffff80973b90 at kdb_backtrace+0x60 #1 0xffffffff80937c15 at panic+0x155 #2 0xffffffff81c0922f at assfail3+0x2f #3 0xffffffff81a8c5a5 at space_map_load+0x3d5 #4 0xffffffff81a721be at metaslab_load+0x2e #5 0xffffffff81a73da7 at metaslab_alloc+0x777 #6 0xffffffff81ab4166 at zio_dva_allocate+0x76 #7 0xffffffff81ab1542 at zio_execute+0x162 #8 0xffffffff80981f75 at taskqueue_run_locked+0xe5 #9 0xffffffff80982a08 at taskqueue_thread_loop+0xa8 #10 0xffffffff80906d6a at fork_exit+0x9a #11 0xffffffff80d1d5de at fork_trampoline+0xe Uptime: 54s Dumping 408 out of 8167 MB:..4%..12%..24%..32%..44%..51%..63%..71%..83%..91% Will compile -CURRENT and try that tonight. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 14 22:48:35 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F5F7EBD; Tue, 14 Apr 2015 22:48:35 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id C5536DC5; Tue, 14 Apr 2015 22:48:34 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CkBADKly1V/95baINchD+DEMJlh0+CABIBAQEBAQEBfYRJBFItCAINGQJLFIg9tDiWIwEBAQEGAQEBAQEBHIEhjjsXNIJvgUUFnDyDN4ZsiSwihAsigXV/AQEB X-IronPort-AV: E=Sophos;i="5.11,578,1422939600"; d="scan'208";a="205655340" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 14 Apr 2015 18:47:26 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id F3722B3FEA; Tue, 14 Apr 2015 18:47:25 -0400 (EDT) Date: Tue, 14 Apr 2015 18:47:25 -0400 (EDT) From: Rick Macklem To: FreeBSD Filesystems Cc: Alexander Motin Message-ID: <547186349.19019357.1429051645985.JavaMail.root@uoguelph.ca> Subject: RFC: increasing NFS server max I/O size to 128K MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2015 22:48:35 -0000 Hi, mav@ has suggested that 128K will provide better performance for NFS servers using ZFS, since 128K is the default block size used by ZFS. I can't see any reason why changing the NFS server's maximum I/O size from 64K->128K will cause problems. However, if you think there will be issues related to this, please let us know. Note that the FreeBSD NFS client will still use 64K, because changing the client is more problematic, due to its use of the buffer cache. (I will be proposing a patch that will allow buffer cache sizing to be architecture dependent, but that's not this post.;-) The actual patch I have renames NFS_MAXDATA (which is the NFS server's maximum I/O size) to NFS_SRVMAXIO for a couple of reasons: 1 - I wanted the name to make it clear that it applies to the server side only. 2 - I want the name to be different from the NFS_MAXDATA defined in /usr/include/rpcsvc/nfs_prot.h, which has nothing to do with the one defined in the kernel for the NFS server. Any comments/concerns? rick From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 00:29:27 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 436C0E83 for ; Wed, 15 Apr 2015 00:29:27 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 284C0A2A for ; Wed, 15 Apr 2015 00:29:27 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3F0TQiZ068372 for ; Wed, 15 Apr 2015 00:29:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Wed, 15 Apr 2015 00:29:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: drsmithy@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 00:29:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 --- Comment #3 from Chris Smith --- (In reply to Chris Smith from comment #0) Also tried importing the pool to a fresh 8.4 install and had the same panic. I was able to determine (based on the pool that's still OK) that the zpool version is from 8.x. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 00:36:38 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 68F1390 for ; Wed, 15 Apr 2015 00:36:38 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 2F5EFB51 for ; Wed, 15 Apr 2015 00:36:37 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CoBADPsS1V/95baINcg15cBYMQwmaBToYBAoF9EwEBAQEBAQF9hB8BAQEDASMEUgUWDgoCAg0ZAlkGiDUIDbEdhVOQUQEBAQEBAQEDAQEBAQEBAQEWBIEhigqEGREBBhc0B4JogUUFsAsihAsiMgGBCTl/AQEB X-IronPort-AV: E=Sophos;i="5.11,579,1422939600"; d="scan'208";a="205667232" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 14 Apr 2015 20:36:36 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 84081B3F13; Tue, 14 Apr 2015 20:36:36 -0400 (EDT) Date: Tue, 14 Apr 2015 20:36:36 -0400 (EDT) From: Rick Macklem To: Adam Guimont Cc: freebsd-fs@freebsd.org Message-ID: <238081719.19055888.1429058196527.JavaMail.root@uoguelph.ca> In-Reply-To: <551F072C.1000505@tezzaron.com> Subject: Re: NFSD high CPU usage MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 00:36:38 -0000 Adam Guimont wrote: > Rick Macklem wrote: > > I can think of two explanations for this. > > 1 - The server nfsd threads get confused when the TCP recv Q fills > > and start looping around. > > OR > > 2 - The client is sending massive #s of RPCs (or crap that is > > incomplete RPCs). > > > > To get a better idea w.r.t. what is going on, I'd suggest that > > you capture packets (for a relatively short period) when the > > server is 100% CPU busy. > > # tcpdump -s 0 -w out.pcap host > > - run on the server should do it. > > Then look at out.pcap in wireshark and see what the packets > > look like. (wireshark understands NFS, whereas tcpdump doesn't) > > If #1, I'd guess very little traffic (maybe TCP layer stuff), > > if #2, I'd guess you'll see a lot of RPC requests or garbage > > that isn't a valid request. (This latter case would suggest a > > CentOS problem.) > > > > If you capture the packets but can't look at them in wireshark, > > you could email me the packet capture as an attachment and I > > can look at it after Apr. 10, when I get home. > > > > rick > > > > Thanks Rick, > > I was able to capture this today while it was happening. The capture > is > for about 100 seconds. I took a look at it in wireshark and to me it > appears like the #2 situation you were describing. > > If you would like to confirm that I've uploaded the pcap file here: > > https://www.dropbox.com/s/pdhwj5z5tz7iwou/out.pcap.20150403 > Well, I took a look, but I'll admit I couldn't figure out much from it. It appears that the TCP connection is in a pretty degraded state. - FreeBSD is sending a whole bunch of TCP segments with 164bytes of data (that appears to be the same for each one, but I didn't look at them closely). Each of them has a Window size == 0 (PUSH + ACK). --> Linux responds with an ACK and no data (which makes sense because of the 0 length Window) eventually FreeBSD does open up the Window after something like 1200 of the above TCP segments. --> It is possible that all these segments are RPC replies to similar requests, but Wireshark just think they're all RPC continuations and doesn't recognize an RPC message. (I couldn't be bothered to try and decode one manually.) One thing I see is that the Linux window size is 24576. If TSO is enabled in FreeBSD's net device, you might try disabling TSO, in case it is sending too much or somehow getting confused. Other than that, I think it would take a packet capture just when the trouble starts to try and figure out how things get messed up. I'm not good enough w.r.t. TCP to have any idea what might be happening. Maybe someone conversant with TCP can look at the trace? rick > I will continue running some tests and trying to gather as much data > as > I can. > > Regards, > > Adam Guimont > From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 00:44:32 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3191D18B for ; Wed, 15 Apr 2015 00:44:32 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 189FCC20 for ; Wed, 15 Apr 2015 00:44:32 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3F0iVca083523 for ; Wed, 15 Apr 2015 00:44:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Wed, 15 Apr 2015 00:44:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: delphij@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 00:44:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 Xin LI changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |delphij@FreeBSD.org --- Comment #4 from Xin LI --- (In reply to Chris Smith from comment #3) The backtrace suggests that you have a space map corruption, but the validation code is only nominally different so it's not clear to me why it won't panic on 8.x. Will the system allow you to import the pool read-only? (zpool import -o readonly=on)? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 00:50:16 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2845224F for ; Wed, 15 Apr 2015 00:50:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0EEF1C40 for ; Wed, 15 Apr 2015 00:50:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3F0oFwP086614 for ; Wed, 15 Apr 2015 00:50:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Wed, 15 Apr 2015 00:50:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: drsmithy@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 00:50:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 --- Comment #5 from Chris Smith --- (In reply to Xin LI from comment #4) Sorry if that wasn't clear. Trying to mount the pool on a fresh 8.4 system DOES cause a panic, same as 9.3 and 10.1. I did try -o readonly on 10.1 and 9.3, but not 8.4. I'm at work at the moment and can't access the system. I'll try -o readonly on 8.4 when I get home. Is there any chance using the -F "Recovery mode" switch to zpool import may help ? The data in this pool is primarily archival, so I don't mind losing recent changes. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 01:16:06 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1A9E60F for ; Wed, 15 Apr 2015 01:16:06 +0000 (UTC) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9995FEC9 for ; Wed, 15 Apr 2015 01:16:06 +0000 (UTC) Received: by igbpi8 with SMTP id pi8so58016917igb.0 for ; Tue, 14 Apr 2015 18:16:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=TNzJCeZtj38z1tD/Lp9BWKAmJ5TnUrjthQnPywHluY0=; b=wFQJQwfR7GvhH3fp89z/3/OQhBT3ZHuCWvS3V9GFkNd2yFCcDx6KeH65c1GuFU2F2A 1/6msqWYjiSuxR1YLpF9bOpdESw7yK6oqHrIjcC7HunPuC3liGjBBFvrjzTVRrbGtIuI +JkzVs+6Y1CXaAWcn695qH4qtBAb6SHCxk8aO0l4+m5cQZJjxGrZmEbLB7v2rftzcqBP FIOzRKRm1fdfZBjqj7tUCSiTJltzf+HNATVcuIDihqfUikYwCOiIuZ9KfNjGTZ4+zl08 PIZUZEPVjmNBnsmf73pzZY+B4fccuqAaZY88MGQeeu/5HAt1x/hCl/6FeUkgKNHj1grZ vHuQ== MIME-Version: 1.0 X-Received: by 10.107.170.135 with SMTP id g7mr33378275ioj.2.1429060565931; Tue, 14 Apr 2015 18:16:05 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.36.67.139 with HTTP; Tue, 14 Apr 2015 18:16:05 -0700 (PDT) Date: Tue, 14 Apr 2015 21:16:05 -0400 X-Google-Sender-Auth: jLNaZoNLIXzOeN4p1xIMUYWkaFM Message-ID: Subject: FreeBSD 10.1 can't "make -j5 buildworld" over NFS? From: J David To: "freebsd-fs@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 01:16:06 -0000 On identical hardware, against the exact same NFS server, FreeBSD 9.3 can do a parallel buildworld, but FreeBSD 10.1 dies in cleandir with a bunch of "stale NFS file handle" errors. The mount options are the same on both clients: 192.168.20.161:/data/software/freebsd/releng-9.3/src /usr/src nfs rw,tcp,nfsv3,noauto 0 0 192.168.20.161:/data/software/freebsd/releng-9.3/amd64/obj /usr/obj nfs rw,tcp,nfsv3,noauto 0 0 192.168.20.161:/data/software/freebsd/releng-10.1/src /usr/src nfs rw,tcp,nfsv3,noauto 0 0 192.168.20.161:/data/software/freebsd/releng-10.1/amd64/obj /usr/obj nfs rw,tcp,nfsv3,noauto 0 0 FreeBSD 9.3 build output: $ sudo make -j 5 buildworld -------------------------------------------------------------- >>> World build started on Tue Apr 14 23:47:38 UTC 2015 -------------------------------------------------------------- [ ... time passes ... ] -------------------------------------------------------------- >>> World build completed on Wed Apr 15 00:51:24 UTC 2015 -------------------------------------------------------------- FreeBSD 10.1 build output: c$ sudo make -j 5 buildworld --- buildworld --- --- buildworld_prologue --- -------------------------------------------------------------- >>> World build started on Wed Apr 15 01:01:09 UTC 2015 -------------------------------------------------------------- [ ... time passes ... ] ===> lib/libthr (cleandir) --- usr.sbin.cleandir__D --- --- cleandir_subdir_bhyve --- ===> usr.sbin/bhyve (cleandir) --- usr.bin.cleandir__D --- --- cleandir_subdir_gzip --- ===> usr.bin/gzip (cleandir) --- usr.sbin.cleandir__D --- --- cleanobj --- --- share.cleandir__D --- cat: .tmpfiles: Stale NFS file handle bmake[6]: "/usr/src/share/i18n/esdb/Makefile.part" line 78: warning: "cat .tmpfiles" returned non-zero status --- usr.bin.cleandir__D --- --- cleanobj --- --- lib.cleandir__D --- --- cleanobj --- --- usr.bin.cleandir__D --- --- cleandir_subdir_head --- ===> usr.bin/head (cleandir) --- usr.sbin.cleandir__D --- --- cleandir_subdir_bhyvectl --- ===> usr.sbin/bhyvectl (cleandir) --- share.cleandir__D --- --- clean --- rm -f Big5-2003.esdb Big5-E.esdb Big5-ETen.esdb Big5-HKSCS.esdb Big5-IBM.esdb Big5-Plus.esdb esdb.dir.BIG5 esdb.alias.BIG5 .tmpfiles rm: Big5-2003.esdb: Stale NFS file handle rm: Big5-E.esdb: Stale NFS file handle rm: Big5-ETen.esdb: Stale NFS file handle rm: Big5-HKSCS.esdb: Stale NFS file handle rm: Big5-IBM.esdb: Stale NFS file handle rm: Big5-Plus.esdb: Stale NFS file handle rm: esdb.dir.BIG5: Stale NFS file handle rm: esdb.alias.BIG5: Stale NFS file handle rm: .tmpfiles: Stale NFS file handle *** [clean] Error code 1 bmake[6]: stopped in /usr/src/share/i18n/esdb/BIG5 1 error bmake[6]: stopped in /usr/src/share/i18n/esdb/BIG5 *** [_sub.cleandir] Error code 2 bmake[5]: stopped in /usr/src/share/i18n/esdb --- usr.bin.cleandir__D --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/usr.bin/head *** [cleandir_subdir_head] Error code 2 bmake[3]: stopped in /usr/src/usr.bin 1 error bmake[3]: stopped in /usr/src/usr.bin *** [usr.bin.cleandir__D] Error code 2 bmake[2]: stopped in /usr/src --- usr.sbin.cleandir__D --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/usr.sbin/bhyvectl *** [cleandir_subdir_bhyvectl] Error code 2 bmake[3]: stopped in /usr/src/usr.sbin 1 error bmake[3]: stopped in /usr/src/usr.sbin *** [usr.sbin.cleandir__D] Error code 2 bmake[2]: stopped in /usr/src --- share.cleandir__D --- 1 error bmake[5]: stopped in /usr/src/share/i18n/esdb *** [_sub.cleandir] Error code 2 bmake[4]: stopped in /usr/src/share/i18n 1 error bmake[4]: stopped in /usr/src/share/i18n *** [_sub.cleandir] Error code 2 bmake[3]: stopped in /usr/src/share 1 error bmake[3]: stopped in /usr/src/share *** [share.cleandir__D] Error code 2 bmake[2]: stopped in /usr/src --- lib.cleandir__D --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/lib/libthr *** [cleandir_subdir_libthr] Error code 2 bmake[3]: stopped in /usr/src/lib 1 error bmake[3]: stopped in /usr/src/lib *** [lib.cleandir__D] Error code 2 bmake[2]: stopped in /usr/src 4 errors bmake[2]: stopped in /usr/src *** [_cleanobj] Error code 2 bmake[1]: stopped in /usr/src 1 error bmake[1]: stopped in /usr/src *** [buildworld] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src What could be going wrong here? Thanks for any advice! From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 06:51:47 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 447BC512 for ; Wed, 15 Apr 2015 06:51:47 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2AE0592C for ; Wed, 15 Apr 2015 06:51:47 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3F6pl5s027242 for ; Wed, 15 Apr 2015 06:51:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Wed, 15 Apr 2015 06:51:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: drsmithy@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 06:51:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 --- Comment #6 from Chris Smith --- Success ! I was able to mount the pool read-only on the 8.3 system. I'll backup my data off the pool first, but after that if you want me to dump any info out of the pool to help you debug the problem, I'm happy to leave it a few days before nuking and recreating the pool. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 08:29:13 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16AC1E88 for ; Wed, 15 Apr 2015 08:29:13 +0000 (UTC) Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com [209.85.218.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D58993E7 for ; Wed, 15 Apr 2015 08:29:12 +0000 (UTC) Received: by oiko83 with SMTP id o83so13903738oik.1 for ; Wed, 15 Apr 2015 01:29:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=kNKFXAX9ezS+AtEzAU61HGW1RC+atOb6uo45bqJsazg=; b=YbJ9hRVH9NiR0fkNHod9SeCSOFw/uyA23ncoHtLDkPZ88cYIIIZds4ejUvHEGkwBSW 0TWgfmndoJSZ9TU3PBhfPA/50ZHwdzIE6PQIRYKd8BJ8CJscW52aQbsA+VYpiW4+txbf pMB5ts1Xd6Vjt/konDZVzosREGV0xa0pPkZXfux8Mc6RADRHU6eV5cyR2eFoHCd1r8c+ vRT+6ZsomeA4PBJGH2f+Qx8vbPWdBNUC6ySiVSq0Q42ZDDhSfHJn/JPoHSjzT3Xw7Rr1 kBpk+qSfsTvolLSiLmVL6ggXuL/exyshDAylYBrd4tz+YiUnXVfg9mzjYaipL6flgb6j UrUQ== X-Gm-Message-State: ALoCoQnNkMdrhEJ2R4FNWAuch464ZgpYbZLr/yvgFyT6Pxb3c+tepvbpt5QBPogYaA5AU0aUsOOh MIME-Version: 1.0 X-Received: by 10.107.3.199 with SMTP id e68mr30322914ioi.92.1429085059781; Wed, 15 Apr 2015 01:04:19 -0700 (PDT) Received: by 10.36.107.150 with HTTP; Wed, 15 Apr 2015 01:04:19 -0700 (PDT) Date: Wed, 15 Apr 2015 13:34:19 +0530 Message-ID: Subject: ZFS Test Suite in FreeBSD From: Amit Das To: freebsd-fs@freebsd.org Cc: Kiran Mova Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 08:29:13 -0000 Hi All, I was curious to know about the FreeBSD plans w.r.t ZFS test suite. Has there been any efforts to build ZFS test suite on top of FreeBSD KYUA port? Are there any plans to port the ZFS Test Suite from Illumos gate? It will be great if someone can point me to any references or links w.r.t FreeBSD's test strategy for ZFS. Regards, Amit *CloudByte Inc.* From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 14:18:22 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 269C4237 for ; Wed, 15 Apr 2015 14:18:22 +0000 (UTC) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id CF6496E8 for ; Wed, 15 Apr 2015 14:18:21 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2C6CAA5ci5V/95baINcg15cBYMQujqIEwmBRQqFNU4CgXIUAQEBAQEBAX1BA4NcAQEBAwEBAQEgKyALBRYYAgINGQIpAQkmBggHBAEcBIV0gg0IDa5kliMBAQEBAQEEAQEBAQEBARuBIYoKhCoBAQUXNAeCaIFFBYYmjmGDb4QAkxgihAsiMQd7CRcifwEBAQ X-IronPort-AV: E=Sophos;i="5.11,582,1422939600"; d="scan'208";a="203950636" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 15 Apr 2015 10:18:15 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 21EC0B3F88; Wed, 15 Apr 2015 10:18:15 -0400 (EDT) Date: Wed, 15 Apr 2015 10:18:15 -0400 (EDT) From: Rick Macklem To: J David Cc: freebsd-fs@freebsd.org Message-ID: <718753704.19327489.1429107495125.JavaMail.root@uoguelph.ca> In-Reply-To: Subject: Re: FreeBSD 10.1 can't "make -j5 buildworld" over NFS? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 14:18:22 -0000 J David wrote: > On identical hardware, against the exact same NFS server, FreeBSD 9.3 > can do a parallel buildworld, but FreeBSD 10.1 dies in cleandir with > a > bunch of "stale NFS file handle" errors. > Well, the NFS client is almost identical in the two systems. (A couple of NFSv4 specific changes and a removal of a redundant check for creation of a hard link across mount points are the only ones I can see.) As such, I'd suspect userland differences. There is a different "make" in 10 (which I don't think is in 9.3?), so this would be a good starting point. Btw, "stale NFS file handle" means that the file has been deleted on the server. rick > The mount options are the same on both clients: > > 192.168.20.161:/data/software/freebsd/releng-9.3/src /usr/src nfs > rw,tcp,nfsv3,noauto 0 0 > 192.168.20.161:/data/software/freebsd/releng-9.3/amd64/obj /usr/obj > nfs rw,tcp,nfsv3,noauto 0 0 > > > 192.168.20.161:/data/software/freebsd/releng-10.1/src /usr/src nfs > rw,tcp,nfsv3,noauto 0 0 > 192.168.20.161:/data/software/freebsd/releng-10.1/amd64/obj /usr/obj > nfs rw,tcp,nfsv3,noauto 0 0 > > FreeBSD 9.3 build output: > > $ sudo make -j 5 buildworld > -------------------------------------------------------------- > >>> World build started on Tue Apr 14 23:47:38 UTC 2015 > -------------------------------------------------------------- > [ ... time passes ... ] > -------------------------------------------------------------- > >>> World build completed on Wed Apr 15 00:51:24 UTC 2015 > -------------------------------------------------------------- > > FreeBSD 10.1 build output: > > c$ sudo make -j 5 buildworld > --- buildworld --- > --- buildworld_prologue --- > -------------------------------------------------------------- > >>> World build started on Wed Apr 15 01:01:09 UTC 2015 > -------------------------------------------------------------- > [ ... time passes ... ] > ===> lib/libthr (cleandir) > --- usr.sbin.cleandir__D --- > --- cleandir_subdir_bhyve --- > ===> usr.sbin/bhyve (cleandir) > --- usr.bin.cleandir__D --- > --- cleandir_subdir_gzip --- > ===> usr.bin/gzip (cleandir) > --- usr.sbin.cleandir__D --- > --- cleanobj --- > --- share.cleandir__D --- > cat: .tmpfiles: Stale NFS file handle > bmake[6]: "/usr/src/share/i18n/esdb/Makefile.part" line 78: warning: > "cat .tmpfiles" returned non-zero status > --- usr.bin.cleandir__D --- > --- cleanobj --- > --- lib.cleandir__D --- > --- cleanobj --- > --- usr.bin.cleandir__D --- > --- cleandir_subdir_head --- > ===> usr.bin/head (cleandir) > --- usr.sbin.cleandir__D --- > --- cleandir_subdir_bhyvectl --- > ===> usr.sbin/bhyvectl (cleandir) > --- share.cleandir__D --- > --- clean --- > rm -f Big5-2003.esdb Big5-E.esdb Big5-ETen.esdb Big5-HKSCS.esdb > Big5-IBM.esdb Big5-Plus.esdb esdb.dir.BIG5 esdb.alias.BIG5 .tmpfiles > rm: Big5-2003.esdb: Stale NFS file handle > rm: Big5-E.esdb: Stale NFS file handle > rm: Big5-ETen.esdb: Stale NFS file handle > rm: Big5-HKSCS.esdb: Stale NFS file handle > rm: Big5-IBM.esdb: Stale NFS file handle > rm: Big5-Plus.esdb: Stale NFS file handle > rm: esdb.dir.BIG5: Stale NFS file handle > rm: esdb.alias.BIG5: Stale NFS file handle > rm: .tmpfiles: Stale NFS file handle > *** [clean] Error code 1 > > bmake[6]: stopped in /usr/src/share/i18n/esdb/BIG5 > 1 error > > bmake[6]: stopped in /usr/src/share/i18n/esdb/BIG5 > *** [_sub.cleandir] Error code 2 > > bmake[5]: stopped in /usr/src/share/i18n/esdb > --- usr.bin.cleandir__D --- > A failure has been detected in another branch of the parallel make > > bmake[4]: stopped in /usr/src/usr.bin/head > *** [cleandir_subdir_head] Error code 2 > > bmake[3]: stopped in /usr/src/usr.bin > 1 error > > bmake[3]: stopped in /usr/src/usr.bin > *** [usr.bin.cleandir__D] Error code 2 > > bmake[2]: stopped in /usr/src > --- usr.sbin.cleandir__D --- > A failure has been detected in another branch of the parallel make > > bmake[4]: stopped in /usr/src/usr.sbin/bhyvectl > *** [cleandir_subdir_bhyvectl] Error code 2 > > bmake[3]: stopped in /usr/src/usr.sbin > 1 error > > bmake[3]: stopped in /usr/src/usr.sbin > *** [usr.sbin.cleandir__D] Error code 2 > > bmake[2]: stopped in /usr/src > --- share.cleandir__D --- > 1 error > > bmake[5]: stopped in /usr/src/share/i18n/esdb > *** [_sub.cleandir] Error code 2 > > bmake[4]: stopped in /usr/src/share/i18n > 1 error > > bmake[4]: stopped in /usr/src/share/i18n > *** [_sub.cleandir] Error code 2 > > bmake[3]: stopped in /usr/src/share > 1 error > > bmake[3]: stopped in /usr/src/share > *** [share.cleandir__D] Error code 2 > > bmake[2]: stopped in /usr/src > --- lib.cleandir__D --- > A failure has been detected in another branch of the parallel make > > bmake[4]: stopped in /usr/src/lib/libthr > *** [cleandir_subdir_libthr] Error code 2 > > bmake[3]: stopped in /usr/src/lib > 1 error > > bmake[3]: stopped in /usr/src/lib > *** [lib.cleandir__D] Error code 2 > > bmake[2]: stopped in /usr/src > 4 errors > > bmake[2]: stopped in /usr/src > *** [_cleanobj] Error code 2 > > bmake[1]: stopped in /usr/src > 1 error > > bmake[1]: stopped in /usr/src > *** [buildworld] Error code 2 > > make: stopped in /usr/src > 1 error > > make: stopped in /usr/src > > > What could be going wrong here? > > Thanks for any advice! > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 16:00:47 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C416D3E3 for ; Wed, 15 Apr 2015 16:00:47 +0000 (UTC) Received: from nm22-vm1.bullet.mail.bf1.yahoo.com (nm22-vm1.bullet.mail.bf1.yahoo.com [98.139.212.127]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6CC113C9 for ; Wed, 15 Apr 2015 16:00:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1429113639; bh=aPQU5FZk8fSKOqxGnK6+WDAhZMMqTK039UgYOwWJaRM=; h=Date:From:To:CC:Subject:From:Subject; b=QVSeB+32W14PxuFOwGoAkJaPIRxcVBiG9b/my0chwWDTsAWIZ+b/TY1FZTs3qzap/c3IWLTar04w0obEZUuB2x8pb8YYcgjR6JDIPo+uw4SEis+Jxw1u20yPO28b4QXd9XtzyZVmYdE6oIPnXwjsQgE9nOi/oBg5wp9aM3ixs7RDkafbNwXAIc4DLcZDZul78yTZI7YrotBKXwZ5sXp3T2ZCLx1b0HhIDZVVXxVjNj9pCF5qob14qlsonyIipDAggf7iTHUuFs3shM9FhOUnwjIbyErx3N88RSNE96lbNt1NnhglF6QWWv2wy1B8AWlQol827ouuiNWxj3DsatjC8Q== Received: from [98.139.170.179] by nm22.bullet.mail.bf1.yahoo.com with NNFMP; 15 Apr 2015 16:00:39 -0000 Received: from [98.139.211.163] by tm22.bullet.mail.bf1.yahoo.com with NNFMP; 15 Apr 2015 16:00:39 -0000 Received: from [127.0.0.1] by smtp220.mail.bf1.yahoo.com with NNFMP; 15 Apr 2015 16:00:39 -0000 X-Yahoo-Newman-Id: 962148.40687.bm@smtp220.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Lo7CKN8VM1lo_IDBZ5_lYUxnxEOvHUCuyf4Vepxy3_jtZei 0bVYnrEL8baf3zNWPXsAs46_Ztqz0655VMoNCtlZFaBiV01Xrz_f0MfJAv9w uauJN5DlkjvOMrhp79hu.XlDgXM52ydMF1p262qzRZJJCsSrFpUpSr2SsICG rpNt7N2HpzCcoF8p0nNcl4CWAqgv_1MW3GxG7un.7Jb.9TRGmGP7gFlX_BGF yhBSCk41MlUODhSnRzdsZWaWZFgMRv4LgmUS7KiZX1nL2dSnwcTJ7lPKlAYD xqC3kRKQbtvfiMUGs98RYaKP8q_FiO36X24PFxrKHvK11uOJLIXV300TraRw 5xKKR2k7t_rLm0MUpsSP4rLyTVbtmqLYIovwC0cIJaEIda8SPIv.CRcIjKTp _qMtfBk6QMm3VAIGPgpZdzNrd.9XDKd1s5Yd7q4.BU5euh4OyK6M9NkZKKnP YfET8_oBtEDrGTsd.IlCZcOusbSWu.qbjaNtTQGlPhggJxoQ8_VFypJVUktG yaaqOQ6P1UtcJ9284IEc77qi9sODr_1Rw X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf Message-ID: <552E8B2A.1010801@FreeBSD.org> Date: Wed, 15 Apr 2015 11:00:42 -0500 From: Pedro Giffuni Organization: FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Amit Das , freebsd-fs@freebsd.org CC: Kiran Mova Subject: Re: ZFS Test Suite in FreeBSD Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 16:00:47 -0000 Hello; Late last year there was some discussion about this in freebsd-testing: https://lists.freebsd.org/pipermail/freebsd-testing/2014-September/000508.html You also want to look at this link: https://svnweb.freebsd.org/base?view=revision&revision=270604 regards, Pedro. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 17:28:51 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95FD5E8E for ; Wed, 15 Apr 2015 17:28:51 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7BFB4CA for ; Wed, 15 Apr 2015 17:28:51 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3FHSpqc008843 for ; Wed, 15 Apr 2015 17:28:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199140] unlinking symlinks oddly slow on UFS Date: Wed, 15 Apr 2015 17:28:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 17:28:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199140 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 17:31:52 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9695E8 for ; Wed, 15 Apr 2015 17:31:52 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AEEE619F for ; Wed, 15 Apr 2015 17:31:52 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3FHVqIE015149 for ; Wed, 15 Apr 2015 17:31:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199189] SWAP on ZFS can crash server Date: Wed, 15 Apr 2015 17:31:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 17:31:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199189 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 17:34:36 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A35562FB for ; Wed, 15 Apr 2015 17:34:36 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 880621D8 for ; Wed, 15 Apr 2015 17:34:36 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3FHYajP017316 for ; Wed, 15 Apr 2015 17:34:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199309] Kernel panic "binsfree: free buffer onto another queue???" extracting tar to ext2fs partition. Date: Wed, 15 Apr 2015 17:34:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 17:34:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199309 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 17:59:34 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C46349F9 for ; Wed, 15 Apr 2015 17:59:34 +0000 (UTC) Received: from mail-oi0-f42.google.com (mail-oi0-f42.google.com [209.85.218.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 863B66EE for ; Wed, 15 Apr 2015 17:59:34 +0000 (UTC) Received: by oica37 with SMTP id a37so31041997oic.0 for ; Wed, 15 Apr 2015 10:59:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hl0XJuYxNth7Q34XeXgsiqyYAC764UM4DKzvQlCBom0=; b=O0ESV7Z/AOpQldk4vSA+nnj/YN3IGtzFqn8CxhfrM4FtgH8FM3p6DdH66ax7Hz5Abh AU2nBvKUVDsaCQ9W19jIbVjYyrbeF7b+rEGE9tsUWzxfxPN3z9R5OOv2AOiaUkXKb2A7 6x6RsFLU9CO7h8VDa1KmCZ0eSlfffUlsgbXah9xEThB29Uzq1B+otZ7PF9bRwi1+DEVN UyO2N/8WAifr4u47Ft/XSjoiNnArLsZBYwPN7mLZnL1PXskQBvcQqwoOm/gPZRJ5ZeYJ ds4JtA/BNYKRHrXKwU1KmVbvJxfQejK4O/p8mixyGX/fLHOYzqjSoOSpadCeAcMpz4zY y9xg== X-Gm-Message-State: ALoCoQnEAAVMqgaRtU1Da08kkVDFwqqUY6928vbN6Bo4vVzapwU8gwhVqyZ6csZ41py0PBcIDav0 MIME-Version: 1.0 X-Received: by 10.42.52.4 with SMTP id h4mr33298128icg.32.1429117196341; Wed, 15 Apr 2015 09:59:56 -0700 (PDT) Received: by 10.36.107.150 with HTTP; Wed, 15 Apr 2015 09:59:56 -0700 (PDT) In-Reply-To: <552E8B2A.1010801@FreeBSD.org> References: <552E8B2A.1010801@FreeBSD.org> Date: Wed, 15 Apr 2015 22:29:56 +0530 Message-ID: Subject: Re: ZFS Test Suite in FreeBSD From: Amit Das To: Pedro Giffuni Cc: freebsd-fs@freebsd.org, Kiran Mova Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 17:59:35 -0000 Thanks Pedro. Regards, Amit *CloudByte Inc.* On Wed, Apr 15, 2015 at 9:30 PM, Pedro Giffuni wrote: > Hello; > > Late last year there was some discussion about this in freebsd-testing: > https://lists.freebsd.org/pipermail/freebsd-testing/ > 2014-September/000508.html > > You also want to look at this link: > > https://svnweb.freebsd.org/base?view=revision&revision=270604 > > regards, > > Pedro. > From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 20:14:58 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE98D4BA for ; Wed, 15 Apr 2015 20:14:58 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 510D9CF8 for ; Wed, 15 Apr 2015 20:14:58 +0000 (UTC) Received: by widdi4 with SMTP id di4so168909533wid.0 for ; Wed, 15 Apr 2015 13:14:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=lejn8BIV7Yt03WeTn0yfOph8UbSuu5JtT1dX/GwmCRc=; b=MWKt2+T77//4+7An7gNdRhH4UA2Wlr2mb3hNMiHeqxMo2HxbdT6X8wNjI3BYrSIjBY b0aVUpAnrgS5bBSgUbAlxtC0c3iioUbtX2yQri45YgDg3CAa25ySyfuxLMIIO1FfRtX/ s0v7DVwtb8y6dHOGkgJLplRNNk1AjHE00TBz2+krm46fTkzysCK/MIx/i/6kKd65hz8u +1ryoe7D7ptF0sRCnlX+ogtL7QlB4lMs2W3GG3in3NXKUonQKmglZskIlsEHT9VFkPr0 42mnn8svrW1tQSVqGS0/ocjieX/O5hgcPJAPbwtL+5G1Hh3vJT27XKeyVznsWBb5HZMi xHKQ== X-Received: by 10.194.174.225 with SMTP id bv1mr53698577wjc.101.1429128896814; Wed, 15 Apr 2015 13:14:56 -0700 (PDT) Received: from [192.168.1.210] (5ED0CC40.cm-7-1d.dynamic.ziggo.nl. [94.208.204.64]) by mx.google.com with ESMTPSA id g5sm7385603wjr.19.2015.04.15.13.14.51 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Apr 2015 13:14:56 -0700 (PDT) Message-ID: <552EC6BA.8050407@gmail.com> Date: Wed, 15 Apr 2015 22:14:50 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: setfacl recursive support Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 20:14:58 -0000 Hello all. I saw on the hardenedbsd project that they had added recursive support to setfacl https://github.com/HardenedBSD/hardenedBSD-stable/commit/5f3929f072e0581330ce7e11a2ee40d79ccb7707 Is this going to be backported to FreeBSD itself? It would be nice to have. regards From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 22:37:47 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F319F78B for ; Wed, 15 Apr 2015 22:37:47 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE108EC2 for ; Wed, 15 Apr 2015 22:37:46 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5C94D28427; Thu, 16 Apr 2015 00:30:58 +0200 (CEST) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 5EDDB28423; Thu, 16 Apr 2015 00:30:57 +0200 (CEST) Message-ID: <552EE6A1.3010402@quip.cz> Date: Thu, 16 Apr 2015 00:30:57 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Johan Hendriks , freebsd-fs@freebsd.org Subject: Re: setfacl recursive support References: <552EC6BA.8050407@gmail.com> In-Reply-To: <552EC6BA.8050407@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 22:37:48 -0000 Johan Hendriks wrote on 04/15/2015 22:14: > Hello all. > > I saw on the hardenedbsd project that they had added recursive support > to setfacl > https://github.com/HardenedBSD/hardenedBSD-stable/commit/5f3929f072e0581330ce7e11a2ee40d79ccb7707 > > Is this going to be backported to FreeBSD itself? It would be nice to have. It will be really useful, if FreeBSD have getfacl and setfacl recursive as they are in "another OS". Then we can do backup and restore of permissions of some directory tree very easily. This feature is missing for years (for me, personaly) Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 23:08:16 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4CF5E9B for ; Wed, 15 Apr 2015 23:08:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC1D7231 for ; Wed, 15 Apr 2015 23:08:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3FN8G6c013392 for ; Wed, 15 Apr 2015 23:08:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199189] SWAP on ZFS can crash server Date: Wed, 15 Apr 2015 23:08:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: nowak@tepeserwery.pl X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 23:08:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199189 nowak@tepeserwery.pl changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nowak@tepeserwery.pl --- Comment #1 from nowak@tepeserwery.pl --- Increasing v_free_severe to give zfs some room seems to help. sysctl vm.v_free_target=60000 sysctl vm.v_free_min=55000 sysctl vm.v_free_severe=50000 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 23:12:43 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A668A5 for ; Wed, 15 Apr 2015 23:12:43 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 01A09329 for ; Wed, 15 Apr 2015 23:12:43 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3FNCgJ8020480 for ; Wed, 15 Apr 2015 23:12:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199189] SWAP on ZFS can crash server Date: Wed, 15 Apr 2015 23:12:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 23:12:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199189 Steven Hartland changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smh@FreeBSD.org --- Comment #2 from Steven Hartland --- Without some serious work, swap on ZFS will be error prone as ZFS can require memory to complete its IO pipeline and swap data to its vdevs so if memory is really short it can easily cause a deadlock. So while light use of swap on ZFS can work, heavy use of it will almost certainly fail. Given this I would never recommend ZFS backed swap. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 15 23:20:51 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B250E19D for ; Wed, 15 Apr 2015 23:20:51 +0000 (UTC) Received: from sdf.lonestar.org (mx.sdf.org [192.94.73.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "SDF.ORG" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 658025F6 for ; Wed, 15 Apr 2015 23:20:50 +0000 (UTC) Received: from ma.sdf.org (IDENT:U2FsdGVkX18WeTiOcbPvzvEPkmHZ/7xi73qbHiPbxpM@ma.sdf.org [192.94.73.31]) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id t3FMsBxr013921 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Wed, 15 Apr 2015 22:54:11 GMT Received: (from cpet@localhost) by ma.sdf.org (8.14.4/8.14.4/Submit) id t3FMsJVE014159; Wed, 15 Apr 2015 22:54:19 GMT Date: Wed, 15 Apr 2015 22:54:19 +0000 From: cpet@sdf.org To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Johan Hendriks , freebsd-fs@freebsd.org Subject: Re: setfacl recursive support Message-ID: <20150415225418.GA10215@ma.sdf.org> References: <552EC6BA.8050407@gmail.com> <552EE6A1.3010402@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <552EE6A1.3010402@quip.cz> User-Agent: Mutt/1.5.20 (2009-12-10) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 23:20:51 -0000 On Thu, Apr 16, 2015 at 12:30:57AM +0200, Miroslav Lachman wrote: > Johan Hendriks wrote on 04/15/2015 22:14: > >Hello all. > > > >I saw on the hardenedbsd project that they had added recursive support > >to setfacl > >https://github.com/HardenedBSD/hardenedBSD-stable/commit/5f3929f072e0581330ce7e11a2ee40d79ccb7707 > > > >Is this going to be backported to FreeBSD itself? It would be nice to have. > > It will be really useful, if FreeBSD have getfacl and setfacl > recursive as they are in "another OS". Then we can do backup and > restore of permissions of some directory tree very easily. > This feature is missing for years (for me, personaly) > > Miroslav Lachman > > _______________________________________________ > 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 recently am using this cmd a lot so I might look into creating recursion for it. as currently i do some magic with xargs which I am sure would be better to have a -r. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 16 05:32:21 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2CEBBF29 for ; Thu, 16 Apr 2015 05:32:21 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 138D4E26 for ; Thu, 16 Apr 2015 05:32:21 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3G5WKh0053310 for ; Thu, 16 Apr 2015 05:32:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199189] SWAP on ZFS can crash server Date: Thu, 16 Apr 2015 05:32:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: vermaden@interia.pl X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2015 05:32:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199189 --- Comment #3 from vermaden@interia.pl --- My thought was that if its 'production ready' on Solaris, then it would be the same (or better) on FreeBSD ... http://docs.oracle.com/cd/E26502_01/html/E29006/gizfl.html Regards, vermaden -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 16 07:30:53 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1C8BA12 for ; Thu, 16 Apr 2015 07:30:53 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C9342C3E for ; Thu, 16 Apr 2015 07:30:53 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3G7UrxW080830 for ; Thu, 16 Apr 2015 07:30:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199189] SWAP on ZFS can crash server Date: Thu, 16 Apr 2015 07:30:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2015 07:30:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199189 --- Comment #4 from Steven Hartland --- I'm afraid not -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 16 15:49:48 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3FD071B1 for ; Thu, 16 Apr 2015 15:49:48 +0000 (UTC) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 025C5DFA for ; Thu, 16 Apr 2015 15:49:48 +0000 (UTC) Received: by iejt8 with SMTP id t8so54611101iej.2 for ; Thu, 16 Apr 2015 08:49:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=1dkMf76VZOMd4E/98jG1KnQ/PmBESd3edreFtc7o8hE=; b=Z3kWWfO1aso9MlHeEjwAp/N1bnoKflkIRsLtSzHtwAEyZEz8q5PU3ntDFkQtd3kNS/ rgkVfN2+WuIjWnFJsXa1VEQDAWvymcQdGYpkN0kRFClbAmulgDDl3x73QUvzYJCoTcpA fWpTq62qZriZAsvZmMxvwvFYwjxbqFAHxp3I6HXPMnEhW1xK6hOR8JPqiCGUPh6fIHZ3 weeFpjBeEJBBCpeGnsiBxru2WmGR7HHuG1ifWsj72t9V+hRkhfIlenEmQCrmU7MiZ1eB 65VEAKmW/yUgCgi68gkApW/SPs5F0hh+6bLElaKFIn0WEJHgDv005KaALRXwla0MxQY0 T+rg== MIME-Version: 1.0 X-Received: by 10.43.60.14 with SMTP id wq14mr38491874icb.60.1429199387445; Thu, 16 Apr 2015 08:49:47 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.36.67.2 with HTTP; Thu, 16 Apr 2015 08:49:47 -0700 (PDT) In-Reply-To: <718753704.19327489.1429107495125.JavaMail.root@uoguelph.ca> References: <718753704.19327489.1429107495125.JavaMail.root@uoguelph.ca> Date: Thu, 16 Apr 2015 11:49:47 -0400 X-Google-Sender-Auth: zrM4dSIL4pJbra25JfLDhPHBdgw Message-ID: Subject: Re: FreeBSD 10.1 can't "make -j5 buildworld" over NFS? From: J David To: Rick Macklem Cc: "freebsd-fs@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2015 15:49:48 -0000 On Wed, Apr 15, 2015 at 10:18 AM, Rick Macklem wrote: > Well, the NFS client is almost identical in the two systems. (A couple > of NFSv4 specific changes and a removal of a redundant check for creation > of a hard link across mount points are the only ones I can see.) > > As such, I'd suspect userland differences. There is a different "make" > in 10 (which I don't think is in 9.3?), so this would be a good starting > point. That may be, but this problem only occurs over NFS. It does not happen with local UFS or ZFS. So perhaps the new make is exercising the NFS client differently than the old one, revealing the problem. > Btw, "stale NFS file handle" means that the file has been deleted on the > server. Yes it does. And the make always dies during cleandir, during which things are being aggressively deleted. It does seem like that's the *only* stage that has problems. I.e. if "make cleanworld" is run before "make -j5 buildworld" then the parallel build will succeed. Hopefully that means it will be relatively easy to narrow down / reproduce the problem behavior. However, in my experience, stale NFS file handles usually occur when one client deletes things out from under another client (and/or after a server reboot, which is not the case here). In this case, this is the only client that can even mount the relevant partition as read-write, much less writing to it. It's like the 10.1 client is caching that stuff exists even after it removes it, leading to errors from the server when it tries to access them again. It's pretty unusual (again, in my experience) for a single client to trip over *itself* when deleting things. Thanks! From owner-freebsd-fs@FreeBSD.ORG Thu Apr 16 16:53:21 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4CE2155 for ; Thu, 16 Apr 2015 16:53:21 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8B90F8B6 for ; Thu, 16 Apr 2015 16:53:21 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3GGrLTZ017084 for ; Thu, 16 Apr 2015 16:53:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199189] SWAP on ZFS can crash server Date: Thu, 16 Apr 2015 16:53:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: john@jnielsen.net X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2015 16:53:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199189 John Nielsen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |john@jnielsen.net --- Comment #5 from John Nielsen --- Using the recommended (AFAIK) settings for a ZFS swap volume (below) combined with nowak's v_free sysctl recommendation allows me to run your test script successfully (meaning the system doesn't hang and the script is killed). zfs create -V -o org.freebsd:swap=on -o checksum=off -o compression=off -o dedup=off -o sync=disabled -o primarycache=none / That said, I'm not sure what (if any) action this ticket should spur. Is there specific documentation you (OP) would like to see updated? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 16 17:30:13 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE3D9836 for ; Thu, 16 Apr 2015 17:30:13 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D4FD0C63 for ; Thu, 16 Apr 2015 17:30:13 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3GHUD23080955 for ; Thu, 16 Apr 2015 17:30:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199189] SWAP on ZFS can crash server Date: Thu, 16 Apr 2015 17:30:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: john@jnielsen.net X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2015 17:30:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199189 --- Comment #6 from John Nielsen --- FWIW, on my test VM with 3GB RAM and a 2GB swap volume (with ZFS properties as described in my previous comment) the test script hangs the system with the default settings: vm.v_free_min: 4833 vm.v_free_target: 16218 vm.v_free_reserved: 1038 vm.v_free_severe: 2935 but not with these (just bumping up v_free_min and v_free_severe): vm.v_free_min: 8192 vm.v_free_target: 16218 vm.v_free_reserved: 1038 vm.v_free_severe: 7168 On this system the magic number for v_free_severe seems to be between 5120 (which hangs) and 7168 (which doesn't). I have added a note about vm.v_free_severe to https://wiki.freebsd.org/RootOnZFS#ZFS_Swap_Volume, which is where I got the recommended swap volume settings from in the first place. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 16 21:47:19 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8FB67EFA for ; Thu, 16 Apr 2015 21:47:19 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 558311B63 for ; Thu, 16 Apr 2015 21:47:18 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CmBADzLDBV/95baINXBoQ6BYMQwneHUgKCDBMBAQEBAQEBfYQhAQEEI1EFGxgCAg0ZAlkGE4YVghWzG5VsAQEBAQYBAQEBAQEcgSGKCIQxCA80B4JogUUFnFGGII1GIoQLIjGBAkJ/AQEB X-IronPort-AV: E=Sophos;i="5.11,590,1422939600"; d="scan'208";a="206039745" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 16 Apr 2015 17:47:08 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 6A2E0B3F43; Thu, 16 Apr 2015 17:47:08 -0400 (EDT) Date: Thu, 16 Apr 2015 17:47:08 -0400 (EDT) From: Rick Macklem To: J David Cc: freebsd-fs@freebsd.org Message-ID: <379019615.20563078.1429220828421.JavaMail.root@uoguelph.ca> In-Reply-To: Subject: Re: FreeBSD 10.1 can't "make -j5 buildworld" over NFS? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2015 21:47:19 -0000 J David wrote: > On Wed, Apr 15, 2015 at 10:18 AM, Rick Macklem > wrote: > > Well, the NFS client is almost identical in the two systems. (A > > couple > > of NFSv4 specific changes and a removal of a redundant check for > > creation > > of a hard link across mount points are the only ones I can see.) > > > > As such, I'd suspect userland differences. There is a different > > "make" > > in 10 (which I don't think is in 9.3?), so this would be a good > > starting > > point. > > That may be, but this problem only occurs over NFS. It does not > happen with local UFS or ZFS. So perhaps the new make is exercising > the NFS client differently than the old one, revealing the problem. > > > Btw, "stale NFS file handle" means that the file has been deleted > > on the > > server. > > Yes it does. And the make always dies during cleandir, during which > things are being aggressively deleted. > > It does seem like that's the *only* stage that has problems. I.e. if > "make cleanworld" is run before "make -j5 buildworld" then the > parallel build will succeed. Hopefully that means it will be > relatively easy to narrow down / reproduce the problem behavior. > > However, in my experience, stale NFS file handles usually occur when > one client deletes things out from under another client (and/or after > a server reboot, which is not the case here). In this case, this is > the only client that can even mount the relevant partition as > read-write, much less writing to it. It's like the 10.1 client is > caching that stuff exists even after it removes it, leading to errors > from the server when it tries to access them again. It's pretty > unusual (again, in my experience) for a single client to trip over > *itself* when deleting things. > > Thanks! > First, I will point out that the NFS protocol is not POSIX compliant and, as such, there will be always cases where apps. that work on POSIX compliant file systems don't work on NFS. When the NFS Remove RPC is done, a file is removed. (NFS does not know if the file is open and does not maintain POSIX opens on files.) A "trick" used by the NFS client to approximate POSIX is called "silly rename". When the client sees that a file is open by another process on the machine, an unlink(2) becomes "rename file to .nfsXXX and then do a Remove RPC on it when the open count goes to 0". This normally avoids "stale NFS file handle" within a single client. This "trick" is not "race free" when done between multiple clients, but for a single client I am not aware of a problem with it. However, the FreeBSD client does this, so I doubt this is the problem. It may be something as simple as make expecting ENOENT for a remove and instead gets ESTALE from the NFS when the file has already been deleted. rick From owner-freebsd-fs@FreeBSD.ORG Fri Apr 17 21:11:54 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 39423F1A for ; Fri, 17 Apr 2015 21:11:54 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2270CE82 for ; Fri, 17 Apr 2015 21:11:54 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3HLBsD9088761 for ; Fri, 17 Apr 2015 21:11:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199309] Kernel panic "binsfree: free buffer onto another queue???" extracting tar to ext2fs partition. Date: Fri, 17 Apr 2015 21:11:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pfg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pfg@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2015 21:11:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199309 Pedro F. Giffuni changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-fs@FreeBSD.org |pfg@FreeBSD.org CC| |pfg@FreeBSD.org --- Comment #1 from Pedro F. Giffuni --- Hello; I assume you are using ext3. I think that this is yet another bug report related to dir_index implementation. As a workaround disable the dir_index extension using tune2fs utility. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Fri Apr 17 21:13:11 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3B394F95 for ; Fri, 17 Apr 2015 21:13:11 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 259B6E93 for ; Fri, 17 Apr 2015 21:13:11 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3HLDBs5048171 for ; Fri, 17 Apr 2015 21:13:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 191895] [ext2fs] [panic] ext2_dirbad: /mnt: bad dir ino 32787 at offset 6136: mangled entry Date: Fri, 17 Apr 2015 21:13:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pfg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pfg@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2015 21:13:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191895 Pedro F. Giffuni changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-fs@FreeBSD.org |pfg@FreeBSD.org --- Comment #7 from Pedro F. Giffuni --- Grab PR: I got tired of dir_index issues and will be removing the feature altogether. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Fri Apr 17 21:14:10 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8C0E820E for ; Fri, 17 Apr 2015 21:14:10 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F84AE9A for ; Fri, 17 Apr 2015 21:14:10 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3HLEAxL081119 for ; Fri, 17 Apr 2015 21:14:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 198731] Generated ext2/ext3 filesystem is reported to have corrupted directory inodes Date: Fri, 17 Apr 2015 21:14:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pfg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pfg@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2015 21:14:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198731 Pedro F. Giffuni changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-fs@FreeBSD.org |pfg@FreeBSD.org --- Comment #7 from Pedro F. Giffuni --- Grab the issue. I will fix this (somewhat brutally). -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Sat Apr 18 14:25:38 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80EF5B0C for ; Sat, 18 Apr 2015 14:25:38 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6B6703C6 for ; Sat, 18 Apr 2015 14:25:38 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3IEPc8U025339 for ; Sat, 18 Apr 2015 14:25:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Sat, 18 Apr 2015 14:25:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: drsmithy@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2015 14:25:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 --- Comment #7 from Chris Smith --- I've retrieved all my data from the pool. Does anyone want a dump of any data before I nuke it and recreate ? I will wait 24 hours. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Sat Apr 18 16:04:20 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 98A2335C for ; Sat, 18 Apr 2015 16:04:20 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 82D3AEE0 for ; Sat, 18 Apr 2015 16:04:20 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3IG4KQv026128 for ; Sat, 18 Apr 2015 16:04:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Sat, 18 Apr 2015 16:04:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2015 16:04:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 --- Comment #8 from Steven Hartland --- As with any upgrade, where the on disk state is the cause of the issue, its not going clear if the issue occurred due to old code which has already been fixed. Given this I'm not sure how helpful a dump would be tbh. Even so what size are we talking about? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Sat Apr 18 18:06:43 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83ADC469 for ; Sat, 18 Apr 2015 18:06:43 +0000 (UTC) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CF90D67 for ; Sat, 18 Apr 2015 18:06:43 +0000 (UTC) Received: by igblo3 with SMTP id lo3so33492822igb.1 for ; Sat, 18 Apr 2015 11:06:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=O4svhdx0Rolgff4FdAaJVpxCb+ZocwDnQ9hJnQiSawE=; b=zUPpkHmoP5XaVuWG8qJQSOb8o+yN2WlRqe5zMQm6kmFcFrNpUn8+yWpZqZhaNo3CeR KB5f/fb0idOe+GH2jwrC4PCNLPNWr8ynutqczSKWrMho13rvRv4M3VAV662cU59Vmjm6 E/aZsN+rKshbNsuoXa+kd8arOYGb1uwbFEPN4pQHK0OSfzpc5vz1f4uNzOypaev0CAlc oLMmvcT/ndJVYEQIe2zroTC5O1OFqCuBCjlObWekkTzMHKFeeUpExNck+XrtbEuSjtgw ORUSv3JAUbgkysN+TBkYshppGeqSj0sp2+ZnBN1iseKdT9SZPmY+a3PrU4Mr13g39Eqv Rohg== MIME-Version: 1.0 X-Received: by 10.107.46.39 with SMTP id i39mr4088784ioo.8.1429380402757; Sat, 18 Apr 2015 11:06:42 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.36.67.2 with HTTP; Sat, 18 Apr 2015 11:06:42 -0700 (PDT) In-Reply-To: <379019615.20563078.1429220828421.JavaMail.root@uoguelph.ca> References: <379019615.20563078.1429220828421.JavaMail.root@uoguelph.ca> Date: Sat, 18 Apr 2015 14:06:42 -0400 X-Google-Sender-Auth: 9kEfyc6y2f-yqya1vfd7jh5sAFw Message-ID: Subject: Re: FreeBSD 10.1 can't "make -j5 buildworld" over NFS? From: J David To: Rick Macklem , "freebsd-fs@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2015 18:06:43 -0000 On Thu, Apr 16, 2015 at 5:47 PM, Rick Macklem wrote: > First, I will point out that the NFS protocol is not POSIX compliant and, > as such, there will be always cases where apps. that work on POSIX compliant > file systems don't work on NFS. Aha. It seems I was misled by this working correctly for years (decades?) and by it being documented in the handbook as the right way to do things. But as building the OS from source is simply too bizarre of an edge case to expect it to work reliably over NFS, I will not pursue this issue any further. Thanks! From owner-freebsd-fs@FreeBSD.ORG Sat Apr 18 22:07:37 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AEA6D219 for ; Sat, 18 Apr 2015 22:07:37 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 99AF196A for ; Sat, 18 Apr 2015 22:07:37 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3IM7b0U048659 for ; Sat, 18 Apr 2015 22:07:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Date: Sat, 18 Apr 2015 22:07:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: drsmithy@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2015 22:07:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 --- Comment #9 from Chris Smith --- (In reply to Steven Hartland from comment #8) The pool itself is about 15T (~10T of actual data). I thought there may be some way for you to pull out the metadata that's causing the panic. Happy to do that if it can help. Otherwise I'll just nuke and recreate. :) -- You are receiving this mail because: You are the assignee for the bug.