From owner-freebsd-fs@freebsd.org Sun Jan 1 21:00:43 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12D2AC9B53B for ; Sun, 1 Jan 2017 21:00:43 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) 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 06E6E178D for ; Sun, 1 Jan 2017 21:00:43 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v01L01vK030015 for ; Sun, 1 Jan 2017 21:00:42 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201701012100.v01L01vK030015@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 Date: Sun, 01 Jan 2017 21:00:42 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2017 21:00:43 -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 ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 203419 | solaris assert: (dn->dn_phys->dn_nlevels == 0 && Open | 211491 | System hangs after "Uptime" on reboot with ZFS 7 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Sun Jan 1 21:09:05 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC18DC9BB7F for ; Sun, 1 Jan 2017 21:09:05 +0000 (UTC) (envelope-from julien@perdition.city) Received: from relay-b01.edpnet.be (relay-b01.edpnet.be [212.71.1.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "edpnet.email", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59BC41FBB for ; Sun, 1 Jan 2017 21:09:05 +0000 (UTC) (envelope-from julien@perdition.city) X-ASG-Debug-ID: 1483304932-0a7ff54cf0a2e5c0001-dE2xID Received: from mordor.lan ([213.219.148.14]) by relay-b01.edpnet.be with ESMTP id lJWDV5dC6qStqvMS (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 01 Jan 2017 22:08:53 +0100 (CET) X-Barracuda-Envelope-From: julien@perdition.city X-Barracuda-Effective-Source-IP: UNKNOWN[213.219.148.14] X-Barracuda-Apparent-Source-IP: 213.219.148.14 Date: Sun, 1 Jan 2017 22:08:52 +0100 From: Julien Cigar To: Rick Macklem Cc: "freebsd-fs@FreeBSD.org" Subject: Re: nfsuserd + jails mbufs leak ? Message-ID: <20170101210852.GT15696@mordor.lan> X-ASG-Orig-Subj: Re: nfsuserd + jails mbufs leak ? References: <20161231143932.GS15696@mordor.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TJ9V72hR/LoebVea" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-Barracuda-Connect: UNKNOWN[213.219.148.14] X-Barracuda-Start-Time: 1483304932 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://212.71.1.221:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 2130 X-Virus-Scanned: by bsmtpd at edpnet.be X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.5000 1.0000 0.0000 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.35500 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2017 21:09:05 -0000 --TJ9V72hR/LoebVea Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 31, 2016 at 10:01:17PM +0000, Rick Macklem wrote: > Julien Cigar wrote: > >I just upgraded a bunch of machines from 10.0 to 10.3. Those machines > >have a lot of jails with NFS shares (mounted on the HOST), for example: > [stuff snipped] > >On the hosts since I upgraded to 10.3 I'm seeing tons of: > >Dec 31 14:29:33 duvel nfsuserd:[675]: req from ip=3D0xc0a80a21 port=3D618 > > > >It is not clear to me yet why I'm getting this, but from what I > >understand it's because requests are not coming from 127.0.0.1 but from > >the jail ip (192.168.10.x in my case).. Parallel to this I'm observing a > >constant increase of mbufs usage so that at some point in time I'm > >getting an exhaustion of mbufs: > Yes, nfsuserd only accepts upcalls from 127.0.0.1 (about the only time a > reserved port# actually means anything). > As such, it doesn't work when you have jails. > I came up with a patch that switched nfsuserd to using AF_LOCAL, but the > person testing this at the time had hangs, so I never committed it to hea= d, etc. > (I don't know what the mbuf leak is, but since it is busted and useless, = I don't > think fixing the leak is necessary.;-) >=20 > Your choices are: > 1 - As you mentioned, don't run nfsuserd. If you are using FreeBSD and/or= Linux > clients, this should work once you set vfs.nfsd.enablestringtouid (o= r whatever > it is called) to 1. > 2 - I had a patch that added an option to nfsuserd that allowed specifica= tion of > a different ip address (unfortunately, I don't have this old patch h= andy, but > might be able to find it at the end of this week. Email if you want = me to find it.) >=20 > rick Thank you for those enlightenments :) I just turned off nfsuserd and everything works as expected..! Perhaps this should be mentionned in the BUGS section in nfsuserd(8) (?) Julien --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --TJ9V72hR/LoebVea Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE7vn2l0to0nV7EWolsrs3EKIEI8AFAlhpb+EACgkQsrs3EKIE I8AuaRAArjSxd4V5ucoKqlvtqzQyzGZiC9OOwU7irGuVrTbkSEd1f82itlzQtYTo Jt35xW0Eorssh9kWw5BzBoHgtpeNAOz1AYcrDx99LeTBXwSYxUvMJuV7YGKse7y2 egM4+ZVU5l2FG71dFCxnFG8ZavKZMH808I7THSVe3CIDBvXQd+yJCqg3lGpXACXi jT1OCkzRpNYjTRv4OCdmoxNIUAInX9YP8Cd3BDWZiB3OR3zGavnFqAxzdbjPom+H OfMETKxE9TPgw5fRvQAGO4D6TiCZhuLUxdkbYM9rCX5yqoO4f0DW47ewVbZYiR20 6hWq+oiXYnQuC2rok8+ZbrU1tV6ATFSmsEZjk8HSqpp8bSdMFjrvyAQa+bkYnqtg P2oSOOfDCSVqc76CXIgbMoXls76/TI9DCh76d6DhL/UvuSfw5xmhGIV/7KJkTh+4 VHdMALXriGyO/NcpmRAUiou5w8pWE2gZGW8wNYrtsm9VSNTKHwUxwp66+wvtz6VH x1ZRwpWxaOS1ohZkD30pnPZTv7/c54l7nxXu1nk5EJEIQvUfVl8ybC5wyIqKS1fd b0MNaS12psd4w53eTYOOWpJsUnX+W5BFIUyO4xO/9OgIRTDPsdOnxgh47YXONyYV JWpPRh0CgBkcdmLFrorfOGFRtnU6gA+/f/BZJsKu8QXKf5vYDGY= =/LPX -----END PGP SIGNATURE----- --TJ9V72hR/LoebVea-- From owner-freebsd-fs@freebsd.org Wed Jan 4 15:22:41 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2CEDC9F579 for ; Wed, 4 Jan 2017 15:22:41 +0000 (UTC) (envelope-from la5lbtyi@aon.at) Received: from smtpout-fallback.aon.at (smtpout-fallback.aon.at [195.3.96.120]) (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 3A6A51785 for ; Wed, 4 Jan 2017 15:22:40 +0000 (UTC) (envelope-from la5lbtyi@aon.at) Received: (qmail 5669 invoked from network); 4 Jan 2017 15:15:58 -0000 Received: from unknown (HELO smtpout.aon.at) ([172.18.1.205]) (envelope-sender ) by fallback43.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 4 Jan 2017 15:15:58 -0000 X-A1Mail-Track-Id: 1483542958:5668:fallback43:172.18.1.205:1 Received: (qmail 13405 invoked from network); 4 Jan 2017 15:15:50 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on WARSBL604.highway.telekom.at X-Spam-Level: Received: from 80-123-58-253.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([80.123.58.253]) (envelope-sender ) by smarthub77.res.a1.net (qmail-ldap-1.03) with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP for ; 4 Jan 2017 15:15:50 -0000 X-A1Mail-Track-Id: 1483542950:13392:smarthub77:80.123.58.253:1 Received: from mizar.xyzzy (mizar.xyzzy [192.168.1.19]) by gandalf.xyzzy (8.15.2/8.15.2) with ESMTP id v04FFnpn016572 for ; Wed, 4 Jan 2017 16:15:50 +0100 (CET) (envelope-from la5lbtyi@aon.at) To: freebsd-fs@freebsd.org From: Martin Birgmeier Subject: Native ZFS encryption Organization: MBi at home Message-ID: <3e0b2644-9739-5341-0295-c746275588ec@aon.at> Date: Wed, 4 Jan 2017 16:15:49 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 15:22:41 -0000 Tom Caputi is working on Native ZFS encryption for Linux: https://github.com/zfsonlinux/zfs/pull/4329 What are the plans/what is the status for incorporating this into FreeBSD? -- Martin From owner-freebsd-fs@freebsd.org Wed Jan 4 17:35:07 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B522C9F9E6 for ; Wed, 4 Jan 2017 17:35:07 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wj0-x231.google.com (mail-wj0-x231.google.com [IPv6:2a00:1450:400c:c01::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 92EC6160A for ; Wed, 4 Jan 2017 17:35:06 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wj0-x231.google.com with SMTP id tq7so237776970wjb.0 for ; Wed, 04 Jan 2017 09:35:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=PWKdMWUU5OHzBYKtuz/zv36onGvo3OrmIieuKJFke1U=; b=vkJV2jdYoxi2O0XiBvDaW/gUQJ6zS2g2UH4L2MmULJeGzQW2OcdEMLB3OtUd0Ymtat Xh5Qg9G4D3EfmC8TTPrFmqZWVj7fA9sB5752hJScxeVJF6s+zrDETeaq7hC2a5RNaF/i yJE/uAOp7Nxqm8H+iJwXbYy07cFOgELH7ZCrIkbSnd4UdfhalXCCRHB79FKESTWJJuL8 JAka0c8nxAyXurzqfag0PPyCh13Z7y4dnU3oenoRIFMPU0+W993Zuqa7Sq5kM+DeZpck M0jfXTfvWtnSEl/OW3N7Y4TamiaJdgvtucJv7nBrwQOwfsVfSus/5E4Ob6Y45GIwrKZO 0i+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=PWKdMWUU5OHzBYKtuz/zv36onGvo3OrmIieuKJFke1U=; b=WPggQWHHQYQ6q2uNvvkyqQ3xdrz/VXEeyKTqYosSqpeTuaRBCT4zEu0lDIHLUkGcYD RBSrms/Z4aLghrPiG4w/DTDoLI890FBIg1ECCDt5YcNT9aG9dfLhjEbsLLan2/AWk5nP 3C+jJbeaEvC1rg6tXV+Htac2NH7KkOg+LR8kpaVC86JbLivxw+7Q6+tzTwdUx4pNe/OS GOlHHgQQ2SvosNwwY9yaDJ7QDTTbr5MOauBoeNrX7saBKkzZY2FIFHufYTEPIlZMTPsa Y0a0ekWgJIgNnkurg8V0jBvJuXV6r677OYRVX90gF+7bZgzxAL78Ghta01inGIdi1peS kFBg== X-Gm-Message-State: AIkVDXKldNkl3d/fCF4z5naTJ+2uKGzH1wSOMHdQfmhtQYhNzY+Q3QalAbFVWzU2uN8zJBwV X-Received: by 10.195.30.165 with SMTP id kf5mr57136587wjd.41.1483551304148; Wed, 04 Jan 2017 09:35:04 -0800 (PST) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id w197sm95926764wmd.11.2017.01.04.09.35.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2017 09:35:03 -0800 (PST) Subject: Re: Native ZFS encryption To: freebsd-fs@freebsd.org References: <3e0b2644-9739-5341-0295-c746275588ec@aon.at> From: Steven Hartland Message-ID: <0bf3fd08-1803-e15b-cadf-755d1c0af325@multiplay.co.uk> Date: Wed, 4 Jan 2017 17:32:57 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <3e0b2644-9739-5341-0295-c746275588ec@aon.at> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 17:35:07 -0000 Typically once its merged upstream (openzfs) after then it will get pulled in. Status of that request is currently conflicting: https://github.com/openzfs/openzfs/pull/124 On 04/01/2017 15:15, Martin Birgmeier wrote: > Tom Caputi is working on Native ZFS encryption for Linux: > https://github.com/zfsonlinux/zfs/pull/4329 > > What are the plans/what is the status for incorporating this into FreeBSD? > > -- Martin > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://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 Jan 4 18:15:31 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71468C9FAFC for ; Wed, 4 Jan 2017 18:15:31 +0000 (UTC) (envelope-from arthur_ramsey@mediture.com) Received: from zimbra.mediture.com (zimbra.mediture.com [198.181.114.30]) (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 374281AD2 for ; Wed, 4 Jan 2017 18:15:30 +0000 (UTC) (envelope-from arthur_ramsey@mediture.com) Received: from zimbra.mediture.com (localhost [127.0.0.1]) by mail01.mediture.dom (Postfix) with ESMTPS id 1F7761E2724 for ; Wed, 4 Jan 2017 12:15:24 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mail01.mediture.dom (Postfix) with ESMTP id 1404D1E26A2 for ; Wed, 4 Jan 2017 12:15:24 -0600 (CST) X-Amavis-Modified: Mail body modified (using disclaimer) - mail01.mediture.dom Received: from zimbra.mediture.com ([127.0.0.1]) by localhost (mail01.mediture.dom [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id N45QmPOdrtJQ for ; Wed, 4 Jan 2017 12:15:23 -0600 (CST) Received: from [192.168.223.92] (74-94-83-121-Minnesota.hfc.comcastbusiness.net [74.94.83.121]) by mail01.mediture.dom (Postfix) with ESMTPSA id DD3981E24DD for ; Wed, 4 Jan 2017 12:15:20 -0600 (CST) From: Arthur Ramsey Subject: Unable to import degraded zpool To: freebsd-fs@freebsd.org Message-ID: <5e87711e-83e8-b813-2224-a3c7d00d6ad0@mediture.com> Date: Wed, 4 Jan 2017 12:13:48 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:15:31 -0000 Hello, I had 2 pools on Nexenta 4. One pool caused Nexenta to boot loop, so I decided to install FreeNAS 9.10.2. No idea why it starting acting up: no changes were made nor was a scrub started. I've previously migrated pools from Nexenta 4 to FreeNAS 9.3 without issue. FreeNAS reported one of the pools reported as corrupted though all disks were online, which is the pool that was causing the boot loop I think. I recreated that pool since the data was more easily replaceable. I had another pool that reported as online, but it failed to import with a missing disk error and dmesg had errors about incompatible mediasize. One disk was shown with the blkdev name (daXXpX) in the zfs import output and zdb -l revealed what I thought was a label for an old pool, so I did a zpool labelclear on it; however, it still failed to import with the same error and as expected now reported as degraded. I then tried FreeNAS 9.3.1 and got the same missing disk error, but nothing interesting in dmesg: http://pastebin.com/w0VBcCfy, http://pastebin.com/NH0uyULV. No combination of -f, -F, -n, -N, -X, -T or -o readonly=on will import the pool on FreeNAS 9.3.1, FreeNAS 9.10.2, OpenIndiana Hipster or Ubuntu 16.04.1. On FreeNAS, I had vfs.zfs.recover=1 and vfs.zfs.debug=1. A memory test passed on the machine and the recreated pool seemed to work OK, but I tried moving the pool's disks to a known good machine running FreeNAS 9.3 and I had the same result. # zpool import pool: xensr id: 17993649064102742628 state: DEGRADED status: The pool was last accessed by another system. action: The pool can be imported despite missing or damaged devices. The fault tolerance of the pool may be compromised if imported. see: http://illumos.org/msg/ZFS-8000-EY config: xensr DEGRADED mirror-0 DEGRADED gptid/f3ececf5-a319-9266-b870-bc3259f24b68 ONLINE 5862692444503195050 UNAVAIL cannot open mirror-1 ONLINE mfisyspd6p1 ONLINE gptid/7cbacbcb-30f8-b5cd-a569-c92eea865edd ONLINE mirror-3 ONLINE mfisyspd5p1 ONLINE mfisyspd4p1 ONLINE mirror-4 ONLINE mfisyspd3p1 ONLINE mfisyspd1p1 ONLINE cache 12574043822818177481 spares 11626098521560667599 logs mirror-2 ONLINE mfisyspd8p1 ONLINE mfisyspd7p1 ONLINE # zpool import -f xensr cannot import 'xensr': one or more devices is currently unavailable Could it be a bug with importing non-exported degraded pools or unreported corruption? I tried the FreeNAS IRC channel and got some assistance, but no solution. I cannot get logged into their forums. The OpenZFS advises to use platform specific mailing lists. I decided to try this mailing list. Thanks, Arthur This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at privacyofficer@mediture.com. From owner-freebsd-fs@freebsd.org Wed Jan 4 18:30:39 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 930EDC9FF11 for ; Wed, 4 Jan 2017 18:30:39 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 52265136C for ; Wed, 4 Jan 2017 18:30:39 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qt0-x22a.google.com with SMTP id k15so259606235qtg.3 for ; Wed, 04 Jan 2017 10:30:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=ZgFC3vypBkIpmn9YMOJJGWNn0ZXKju8CDq4Y+Gm+WhM=; b=turOiP5hNPuvOHwszeb+wN7w0Heg9VDJFZwUGCX35+z2jF/BSfGRlI+hbqHryV2MQx kTNr4qjXkN+5gmGZbErVOoGBO7ki1HdMlYTf2h/8p0Ll0LBJ/NAr99pFXlaflyPLiNAA SKVyh27G0Vi1NZwdodPsqOYHrzB4TFtWPQCiQA+BN1MzCjY1QhV1y0UJtIi/8STh+A8C giFzFq07hfA08O3oE5sMz7EU09V1KPJn2NCbnIBYWVkQSFU/vliziult0WuFOo/cE7jT Qy/33eTBgwka4ATE7qDdqDxvqqnHabjO2tk/WxT4B8GMjA1i1KfxiDRo6zIO7cCMwp8w iA5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ZgFC3vypBkIpmn9YMOJJGWNn0ZXKju8CDq4Y+Gm+WhM=; b=h0xRNJWnAxpC9Cuz3T2cjrs60LrMvn7apsH/6TE3HDvjrBZzaeFP+zaG13utu4qFTt tSvxdPbYjF7j0dGRozqmxyvtxGgRqGf32QMvDrifCLn0Bqo0f4LzfFBCwrQ7Diix0FEL UBJgLq9PJS4KZ5T8jbRN26zMAs64HwAEWKgWUYxYiBbGUM+ftITI53hFwqpUmRx1gKza E/X/SKL3zLMQ0rgWtLnArHl7JkpU4X7/xgdN3eVwPg8RWerMGNHIrojEfVAi0o4Vb+zg sw5vxrejL4BulT+4zII46yRwhqjRqkjvKHhqvHYLMXGIMoS3tEDzMSY2d48CU4927HY/ O6jw== X-Gm-Message-State: AIkVDXIpowskuYMFMJF1czYu241Ho1x58saN3wxpkG1wcbxgNUrEIJPZjL8GArHE4SAQbHTpUdOz4BJ/xjfGZw== X-Received: by 10.200.37.178 with SMTP id e47mr70745808qte.7.1483554638224; Wed, 04 Jan 2017 10:30:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.165.161 with HTTP; Wed, 4 Jan 2017 10:30:37 -0800 (PST) From: Freddie Cash Date: Wed, 4 Jan 2017 10:30:37 -0800 Message-ID: Subject: Check status of background destroy To: FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:30:39 -0000 Is there a way to check the progress of a background destroy process? I did a very bad thing in the middle of December. "zfs destroy -r poolname/dataset", where there's approx 40 TB of data in that dataset, spread across about 400 snapshots, sitting on a dedupe-enabled pool. :( (Usually, I delete individual snapshots, but thought I would try a recursive destroy instead.) Needless to say, the 128 GB of RAM in the box, with 128 GB of L2ARC on SSD, is not enough to hold the DDT, and the box deadlocks after about 8 hours of disk churning. Once Wired memory goes above 120 GB, the system is unresponsive to everything, including pings. During that 8 hour period, the pool is usable; I can read and write data to the pool, I can create and destroy snapshots, and I can receive snapshots from other systems. But the background destroy continues to run after every boot, continues to churn through RAM, and locks everything up after about 8 hours. This has been going on for several weeks now. Is there any way to check the progress of the background destroy to see how much longer this will continue, how much data has been freed, how much of the DDT has been updated, etc? "zfs list" shows very little change in free space. Or am I just going to have to live with resetting the box every 8-10 hours for the next few weeks? Unfortunately, adding more RAM to the box isn't an option right now. :( -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@freebsd.org Wed Jan 4 18:43:12 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37556C9E5AA for ; Wed, 4 Jan 2017 18:43:12 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-wj0-x22b.google.com (mail-wj0-x22b.google.com [IPv6:2a00:1450:400c:c01::22b]) (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 C24AB1D7A for ; Wed, 4 Jan 2017 18:43:11 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mail-wj0-x22b.google.com with SMTP id ew7so3796979wjc.3 for ; Wed, 04 Jan 2017 10:43:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CsSubHtYWGIP0D5HMKFKLFu743WfFn+UagvrNGnovZc=; b=GTp5cuXD+qlm2fzcs2SMUnpIrfPf5KK+Zma5BRW/ZzQDkiyATKtS2m3ZTGJG6keQP5 dGKd5iTi/ZlmKy/DbBIwCJR1Gnx/u3YE/5kr0iBkDgo0QXNT+dtlgUpF5zYe3xRB5lD1 m39cActPATTzXxQ7FtLDPAnYlTfZSUezjqIT5BxIzGgpqWq/Oi/K4qk98g9mYX5ezdWH 9OKWNh+x/w/hpSaHalXWeOgDWzH62E5o2kiGo4SpZ4ZCNn5PkUdEdrzYAWMmoRb4u6Dg FLfctyn+PZ7/S39V3Py0VhQKo54qPrP2YC9W/UdhI4F319ISUFn+FjRs39bGTHZY5az+ C7og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CsSubHtYWGIP0D5HMKFKLFu743WfFn+UagvrNGnovZc=; b=dHQzoAeGvf7vLpaNnvqS2T3WPiMzYqthKUCy8WqWKEQ0aJEFzEHx7EpyqgQAsKW3S/ Qalm2CRfloGyEmxcLJ92WSaXttPwOeHpZ1vNIOZOtyFvR2UFkdpPXzoxHMvN2EcFHlRM DOLY6LU99BNMbszqqis1i2Le/StS8AAlBBqXHqMvDac65SI9bevcO4ThrLEXJpmtvjXn 71Q36pBFES1Ldsy3eYHbfT3GRSJLHtSKhnvr1HKAqOq60bxmvHD1abQ6fSPOjrAvZ+ze DhrN6yoQPqHKPiNwucWU1gaxR3X7jRIj9bnFD28hafA8zeGXcDEZ5r+Snh17c+duqr76 Z2fw== X-Gm-Message-State: AIkVDXJMuRRKFxSb7cmtQcPFLmPZlnzYo3XdOiKhzkax3vFSlaebYU+dMBKiXSrL1Zrl026lkyDDDuYAXaJglQ== X-Received: by 10.194.20.34 with SMTP id k2mr58910638wje.9.1483555390128; Wed, 04 Jan 2017 10:43:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.74.100 with HTTP; Wed, 4 Jan 2017 10:43:09 -0800 (PST) In-Reply-To: References: From: Xin LI Date: Wed, 4 Jan 2017 10:43:09 -0800 Message-ID: Subject: Re: Check status of background destroy To: Freddie Cash Cc: FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:43:12 -0000 Try setting vfs.zfs.free_max_blocks to 100000 (this is an arbitrary number, can be larger, limits maximum blocks being freed per txg; see https://svnweb.freebsd.org/base?view=revision&revision=271532 for details). You can inspect the progress with DTrace by looking at zfs-dbgmsg. On Wed, Jan 4, 2017 at 10:30 AM, Freddie Cash wrote: > Is there a way to check the progress of a background destroy process? > > I did a very bad thing in the middle of December. "zfs destroy -r > poolname/dataset", where there's approx 40 TB of data in that dataset, > spread across about 400 snapshots, sitting on a dedupe-enabled pool. :( > (Usually, I delete individual snapshots, but thought I would try a > recursive destroy instead.) > > Needless to say, the 128 GB of RAM in the box, with 128 GB of L2ARC on SSD, > is not enough to hold the DDT, and the box deadlocks after about 8 hours of > disk churning. Once Wired memory goes above 120 GB, the system is > unresponsive to everything, including pings. > > During that 8 hour period, the pool is usable; I can read and write data to > the pool, I can create and destroy snapshots, and I can receive snapshots > from other systems. But the background destroy continues to run after > every boot, continues to churn through RAM, and locks everything up after > about 8 hours. > > This has been going on for several weeks now. > > Is there any way to check the progress of the background destroy to see how > much longer this will continue, how much data has been freed, how much of > the DDT has been updated, etc? "zfs list" shows very little change in free > space. > > Or am I just going to have to live with resetting the box every 8-10 hours > for the next few weeks? Unfortunately, adding more RAM to the box isn't an > option right now. :( > > -- > Freddie Cash > fjwcash@gmail.com > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://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 Jan 4 18:48:29 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8394CC9E6FC for ; Wed, 4 Jan 2017 18:48:29 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 3E9AE1F54 for ; Wed, 4 Jan 2017 18:48:29 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qk0-x233.google.com with SMTP id u25so404682378qki.2 for ; Wed, 04 Jan 2017 10:48:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yC205P3STjBcf03FnH8/EZLcAeApkd9s9C+fdkLg7yo=; b=XhVeJRGem8rdKExmMSiOtzpPUfxmq4V1YrQ1ot6RAPvl3zautacfNOZMTIbOm850h4 g5+1CJsBpPKbVqf4VaCxjOrHSkYHNR5Um5OrYDLYf1XC7jkOG5fTwdXTB+7qMXdvlhbK ANUH6t2eAUzCpgs6Ky6rxKf2bnakFCX05wHN1R0DajFEV57KTsLZ1+KNZVbNDPvn2SH5 KWCAVtUSsI0L9eQhkuUzscEQwevpzSD0glcEBzi+pCf2fWLJAj5NMYO0M2oRc4uaCjUx WGV6cMKQlxpO+9M6s5NxBW2MQxH878bKJsWYn9rXJcZHroAyns/29G05JOguMDWsnFAy Jwsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yC205P3STjBcf03FnH8/EZLcAeApkd9s9C+fdkLg7yo=; b=Mao+dvNpqqk/Zia1yPuScwzVLaYh/NIbR7+qcL+aZQagBYmBH+gqeZ20kD/fH1Mh3T 6dWd/cNcg+WTVlgdUm7rIDKAKNLc8tgqbt6IZLDNW/0SZnNnr9h09mLspD4hCjpukL6E gituej6mR56sLxVpd1e0wAZlRwiul7ZXvwO1LXqn920k/53rovZrLwPfJTQfE5jGhdfU OuJm8LNh1rYgdjYdxLOVoPibSY8iOOYI5EYWY7/HIEg0vYQIWbGFWfL9s/tmTSPXJl4A i+x/EhwNtbTDJ1AfWUrUSjPbFN3Gsv435YDVxuzLtKGw38VRFhVqqwrVJ7XeNHwFIDFz 2jKg== X-Gm-Message-State: AIkVDXJCg6I0RAbrxsEHtrQQDeA0AuyAqoeuy0q93HnNlPQH9zLRytHQ3n2U2WgICUdk9VYrAvEXV7tlcf169w== X-Received: by 10.55.183.197 with SMTP id h188mr72862934qkf.107.1483555708417; Wed, 04 Jan 2017 10:48:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.165.161 with HTTP; Wed, 4 Jan 2017 10:48:28 -0800 (PST) In-Reply-To: References: From: Freddie Cash Date: Wed, 4 Jan 2017 10:48:28 -0800 Message-ID: Subject: Re: Check status of background destroy To: FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:48:29 -0000 On Wed, Jan 4, 2017 at 10:43 AM, Xin LI wrote: > Try setting vfs.zfs.free_max_blocks to 100000 (this is an arbitrary > number, can be larger, limits maximum blocks being freed per txg; see > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D271532 for > details). > > You can inspect the progress with DTrace by looking at zfs-dbgmsg. > =E2=80=8BForgot to mention, this server is running 64-bit FreeBSD 9.3-p5.= =E2=80=8B That sysctl OID doesn't exist. =E2=80=8BFrom the sounds of the comments on that revision, this would proba= ble be a useful feature to have. I'll have to see about upgrading this system (there's a separate pool for the OS), I guess. Which FreeBSD version(s) include that feature? Would 10.3 be okay, or would I have to go all the way to 11.0? Hrm, maybe I'll play with an updated mfsBSD USB stick instead, and see if things work better with that, first. Thanks for the info!! --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@freebsd.org Wed Jan 4 18:51:02 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70508C9E7D4 for ; Wed, 4 Jan 2017 18:51:02 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 4227A1163 for ; Wed, 4 Jan 2017 18:51:02 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: by mail-io0-x229.google.com with SMTP id d9so460951513ioe.0 for ; Wed, 04 Jan 2017 10:51:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kateley-com.20150623.gappssmtp.com; s=20150623; h=reply-to:subject:references:to:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=YNnHk1+PpRqRAqdZ2xiZAnkelnfYgTFdzcqD6u9Cy8U=; b=NJMNbDWkib7yI/seLD/+XWq5BEvoRc6KdIXC2c2RFoiAKYbDjw7KMhSP7HxniXYYLc jr5TqlfABCrW3YOMB1FYdyvkCc2iCruq/NRpBrfWCiCGgJNP+s0OT7P3c3dpAl/IT8EK lDy/Xj4OWBfz62TVbNQhmjrIrEA4jFHS+TmruwCOpwSlAQPIaLvJ5Va3n9ElsaChMloY gqsSTpMIYpS+1kEFdOjq6WJ7V+XKdw9qQMvcUjtiYwbA2rOj+JnOFewNIpsZNKZSsQI0 VQtiimnXMbEtNaoDrY3TJjM/wLMVTu7A9yaKeUxP1oMEp0bVvqAiqZTZriZEndUsHxH3 vNHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=YNnHk1+PpRqRAqdZ2xiZAnkelnfYgTFdzcqD6u9Cy8U=; b=fIOmbI9ESHP7pXQS1y3hoacE3CCKleYcRcosjCJpW16zM/7OSrj3HcYyg4fJv9CH3Z lZhM2jYosi9A2Qm9zaIYU3cEO9AboPdbUnAGVKv7ND1rATiP5q2ym3eKlecsV0ZTslK2 prTCVWLxnvpbNWEg7ZcpNwTC31oatASpWoE1NUvOixhN1ev8vO2NP0AbP4MIuz4gEwlQ qGI1Md5nMS1NWFqTJcH83lLDXiSBoqfrwuYELls9WgltvwAuVFYFj9oTp8ybfUqXGbDR yd8IRyAuqrBBoHLR2Qk/rdsxUWGkJdT4hKDG5Cruqg0/6NYuKQNs4/E/EXeFAtyjoLAs gn1g== X-Gm-Message-State: AIkVDXJoX/h8Ty2kOf9rctAfJbbDUWGxe7QhD5Ol5XlDHiA/1uh5AYb/vag2nsdf1FGstw== X-Received: by 10.107.159.68 with SMTP id i65mr55730972ioe.153.1483555861205; Wed, 04 Jan 2017 10:51:01 -0800 (PST) Received: from Kateleyco-iMac.local (c-75-72-30-128.hsd1.mn.comcast.net. [75.72.30.128]) by smtp.googlemail.com with ESMTPSA id y134sm18922575iod.16.2017.01.04.10.51.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2017 10:51:00 -0800 (PST) Reply-To: linda@kateley.com Subject: Re: Unable to import degraded zpool References: <5e87711e-83e8-b813-2224-a3c7d00d6ad0@mediture.com> To: freebsd-fs@freebsd.org From: Linda Kateley Organization: Kateley Company Message-ID: <420baa88-c405-cb2d-a4e0-8bd6042b0020@kateley.com> Date: Wed, 4 Jan 2017 12:51:00 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <5e87711e-83e8-b813-2224-a3c7d00d6ad0@mediture.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:51:02 -0000 I would have tried omnios for this.. much closer to nexenta. If you can import the pool, sometimes I can just run zpool online on the UNAVAIL drive and have it pop in.. Linda On 1/4/17 12:13 PM, Arthur Ramsey wrote: > Hello, > > I had 2 pools on Nexenta 4. One pool caused Nexenta to boot loop, so > I decided to install FreeNAS 9.10.2. No idea why it starting acting > up: no changes were made nor was a scrub started. I've previously > migrated pools from Nexenta 4 to FreeNAS 9.3 without issue. FreeNAS > reported one of the pools reported as corrupted though all disks were > online, which is the pool that was causing the boot loop I think. I > recreated that pool since the data was more easily replaceable. I had > another pool that reported as online, but it failed to import with a > missing disk error and dmesg had errors about incompatible mediasize. > One disk was shown with the blkdev name (daXXpX) in the zfs import > output and zdb -l revealed what I thought was a label for an old pool, > so I did a zpool labelclear on it; however, it still failed to import > with the same error and as expected now reported as degraded. I then > tried FreeNAS 9.3.1 and got the same missing disk error, but nothing > interesting in dmesg: http://pastebin.com/w0VBcCfy, > http://pastebin.com/NH0uyULV. No combination of -f, -F, -n, -N, -X, > -T or -o readonly=on will import the pool on FreeNAS 9.3.1, FreeNAS > 9.10.2, OpenIndiana Hipster or Ubuntu 16.04.1. On FreeNAS, I had > vfs.zfs.recover=1 and vfs.zfs.debug=1. A memory test passed on the > machine and the recreated pool seemed to work OK, but I tried moving > the pool's disks to a known good machine running FreeNAS 9.3 and I had > the same result. > > # zpool import > pool: xensr > id: 17993649064102742628 > state: DEGRADED > status: The pool was last accessed by another system. > action: The pool can be imported despite missing or damaged devices. > The > fault tolerance of the pool may be compromised if imported. > see: http://illumos.org/msg/ZFS-8000-EY > config: > > xensr DEGRADED > mirror-0 DEGRADED > gptid/f3ececf5-a319-9266-b870-bc3259f24b68 ONLINE > 5862692444503195050 UNAVAIL cannot > open > mirror-1 ONLINE > mfisyspd6p1 ONLINE > gptid/7cbacbcb-30f8-b5cd-a569-c92eea865edd ONLINE > mirror-3 ONLINE > mfisyspd5p1 ONLINE > mfisyspd4p1 ONLINE > mirror-4 ONLINE > mfisyspd3p1 ONLINE > mfisyspd1p1 ONLINE > cache > 12574043822818177481 > spares > 11626098521560667599 > logs > mirror-2 ONLINE > mfisyspd8p1 ONLINE > mfisyspd7p1 ONLINE > > # zpool import -f xensr > cannot import 'xensr': one or more devices is currently unavailable > > Could it be a bug with importing non-exported degraded pools or > unreported corruption? I tried the FreeNAS IRC channel and got some > assistance, but no solution. I cannot get logged into their forums. > The OpenZFS advises to use platform specific mailing lists. I decided > to try this mailing list. > > > Thanks, > Arthur > > This e-mail and any attachments may contain CONFIDENTIAL information, > including PROTECTED HEALTH INFORMATION. If you are not the intended > recipient, any use or disclosure of this information is STRICTLY > PROHIBITED; you are requested to delete this e-mail and any > attachments, notify the sender immediately, and notify the Mediture > Privacy Officer at privacyofficer@mediture.com. > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://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 Jan 4 18:51:45 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67416C9E837 for ; Wed, 4 Jan 2017 18:51:45 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 337601282 for ; Wed, 4 Jan 2017 18:51:45 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.88 (FreeBSD)) (envelope-from ) id 1cOqf0-0006VD-JQ; Wed, 04 Jan 2017 18:51:42 +0000 Date: Wed, 4 Jan 2017 18:51:42 +0000 From: Gary Palmer To: Freddie Cash Cc: FreeBSD Filesystems Subject: Re: Check status of background destroy Message-ID: <20170104185142.GB95857@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:51:45 -0000 On Wed, Jan 04, 2017 at 10:48:28AM -0800, Freddie Cash wrote: > On Wed, Jan 4, 2017 at 10:43 AM, Xin LI wrote: > > > Try setting vfs.zfs.free_max_blocks to 100000 (this is an arbitrary > > number, can be larger, limits maximum blocks being freed per txg; see > > https://svnweb.freebsd.org/base?view=revision&revision=271532 for > > details). > > > > You can inspect the progress with DTrace by looking at zfs-dbgmsg. > > > > ???Forgot to mention, this server is running 64-bit FreeBSD 9.3-p5.??? That > sysctl OID doesn't exist. > > ???From the sounds of the comments on that revision, this would probable be a > useful feature to have. > > I'll have to see about upgrading this system (there's a separate pool for > the OS), I guess. > > Which FreeBSD version(s) include that feature? Would 10.3 be okay, or > would I have to go all the way to 11.0? The sysctl is in 10.3 $ uname -r 10.3-RELEASE-p15 $ sysctl -d vfs.zfs.free_max_blocks vfs.zfs.free_max_blocks: Maximum number of blocks to free in one TXG $ sysctl vfs.zfs.free_max_blocks vfs.zfs.free_max_blocks: 18446744073709551615 $ Regards, Gary From owner-freebsd-fs@freebsd.org Wed Jan 4 18:57:40 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F366EC9ED3A for ; Wed, 4 Jan 2017 18:57:40 +0000 (UTC) (envelope-from arthur_ramsey@mediture.com) Received: from zimbra.mediture.com (zimbra.mediture.com [198.181.114.30]) (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 D202A1A29 for ; Wed, 4 Jan 2017 18:57:40 +0000 (UTC) (envelope-from arthur_ramsey@mediture.com) Received: from zimbra.mediture.com (localhost [127.0.0.1]) by mail01.mediture.dom (Postfix) with ESMTPS id 67DD81E24DD; Wed, 4 Jan 2017 12:57:39 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mail01.mediture.dom (Postfix) with ESMTP id 5C9381E2370; Wed, 4 Jan 2017 12:57:39 -0600 (CST) X-Amavis-Modified: Mail body modified (using disclaimer) - mail01.mediture.dom Received: from zimbra.mediture.com ([127.0.0.1]) by localhost (mail01.mediture.dom [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id kUd65S-CWvea; Wed, 4 Jan 2017 12:57:39 -0600 (CST) Received: from [192.168.223.92] (74-94-83-121-Minnesota.hfc.comcastbusiness.net [74.94.83.121]) by mail01.mediture.dom (Postfix) with ESMTPSA id 26B171E1AD9; Wed, 4 Jan 2017 12:57:39 -0600 (CST) Subject: Re: Unable to import degraded zpool To: linda@kateley.com, freebsd-fs@freebsd.org References: <5e87711e-83e8-b813-2224-a3c7d00d6ad0@mediture.com> <420baa88-c405-cb2d-a4e0-8bd6042b0020@kateley.com> From: Arthur Ramsey Message-ID: Date: Wed, 4 Jan 2017 12:57:33 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <420baa88-c405-cb2d-a4e0-8bd6042b0020@kateley.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:57:41 -0000 Open Indiana, Omnios and Nexenta use the same kernel and ZFS implementation? I tried the latest version of Nexenta too with no luck. I'll give it a try barring any better ideas though. Thanks for the tip, Arthur On 01/04/2017 12:51 PM, Linda Kateley wrote: > I would have tried omnios for this.. much closer to nexenta. > > If you can import the pool, sometimes I can just run zpool online on > the UNAVAIL drive and have it pop in.. > > Linda > > > On 1/4/17 12:13 PM, Arthur Ramsey wrote: >> Hello, >> >> I had 2 pools on Nexenta 4. One pool caused Nexenta to boot loop, so >> I decided to install FreeNAS 9.10.2. No idea why it starting acting >> up: no changes were made nor was a scrub started. I've previously >> migrated pools from Nexenta 4 to FreeNAS 9.3 without issue. FreeNAS >> reported one of the pools reported as corrupted though all disks were >> online, which is the pool that was causing the boot loop I think. I >> recreated that pool since the data was more easily replaceable. I >> had another pool that reported as online, but it failed to import >> with a missing disk error and dmesg had errors about incompatible >> mediasize. One disk was shown with the blkdev name (daXXpX) in the >> zfs import output and zdb -l revealed what I thought was a label for >> an old pool, so I did a zpool labelclear on it; however, it still >> failed to import with the same error and as expected now reported as >> degraded. I then tried FreeNAS 9.3.1 and got the same missing disk >> error, but nothing interesting in dmesg: >> http://pastebin.com/w0VBcCfy, http://pastebin.com/NH0uyULV. No >> combination of -f, -F, -n, -N, -X, -T or -o readonly=on will import >> the pool on FreeNAS 9.3.1, FreeNAS 9.10.2, OpenIndiana Hipster or >> Ubuntu 16.04.1. On FreeNAS, I had vfs.zfs.recover=1 and >> vfs.zfs.debug=1. A memory test passed on the machine and the >> recreated pool seemed to work OK, but I tried moving the pool's disks >> to a known good machine running FreeNAS 9.3 and I had the same result. >> >> # zpool import >> pool: xensr >> id: 17993649064102742628 >> state: DEGRADED >> status: The pool was last accessed by another system. >> action: The pool can be imported despite missing or damaged >> devices. The >> fault tolerance of the pool may be compromised if imported. >> see: http://illumos.org/msg/ZFS-8000-EY >> config: >> >> xensr DEGRADED >> mirror-0 DEGRADED >> gptid/f3ececf5-a319-9266-b870-bc3259f24b68 ONLINE >> 5862692444503195050 UNAVAIL >> cannot open >> mirror-1 ONLINE >> mfisyspd6p1 ONLINE >> gptid/7cbacbcb-30f8-b5cd-a569-c92eea865edd ONLINE >> mirror-3 ONLINE >> mfisyspd5p1 ONLINE >> mfisyspd4p1 ONLINE >> mirror-4 ONLINE >> mfisyspd3p1 ONLINE >> mfisyspd1p1 ONLINE >> cache >> 12574043822818177481 >> spares >> 11626098521560667599 >> logs >> mirror-2 ONLINE >> mfisyspd8p1 ONLINE >> mfisyspd7p1 ONLINE >> >> # zpool import -f xensr >> cannot import 'xensr': one or more devices is currently unavailable >> >> Could it be a bug with importing non-exported degraded pools or >> unreported corruption? I tried the FreeNAS IRC channel and got some >> assistance, but no solution. I cannot get logged into their forums. >> The OpenZFS advises to use platform specific mailing lists. I >> decided to try this mailing list. >> >> >> Thanks, >> Arthur >> >> This e-mail and any attachments may contain CONFIDENTIAL information, >> including PROTECTED HEALTH INFORMATION. If you are not the intended >> recipient, any use or disclosure of this information is STRICTLY >> PROHIBITED; you are requested to delete this e-mail and any >> attachments, notify the sender immediately, and notify the Mediture >> Privacy Officer at privacyofficer@mediture.com. >> >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at privacyofficer@mediture.com. From owner-freebsd-fs@freebsd.org Thu Jan 5 13:10:44 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99DB4CA08C7 for ; Thu, 5 Jan 2017 13:10:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 801001102 for ; Thu, 5 Jan 2017 13:10:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v05DAfjt036840 for ; Thu, 5 Jan 2017 13:10:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207464] Panic when destroying ZFS snapshot Date: Thu, 05 Jan 2017 13:10:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: drs-freebsd@sieborger.nom.za X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: mfc-stable9+ mfc-stable10+ X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 13:10:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207464 David Sieb=C3=B6rger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drs-freebsd@sieborger.nom.z | |a --- Comment #31 from David Sieb=C3=B6rger --- This bug still affects 10.3-RELEASE and it's being triggered on a number of= our machines during backups. Any chance of merging the fix to that branch in an errata notification? FreeBSD XXXXXX 10.3-RELEASE-p11 FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:49:24 UTC 2016=20=20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 panic: vputx: negative ref cnt 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 condition= s. 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: vputx: negative ref cnt cpuid =3D 3 KDB: stack backtrace: #0 0xffffffff8098e3e0 at kdb_backtrace+0x60 #1 0xffffffff809510b6 at vpanic+0x126 #2 0xffffffff80950f83 at panic+0x43 #3 0xffffffff809f78e5 at vputx+0x2d5 #4 0xffffffff809f1139 at dounmount+0x689 #5 0xffffffff81a6dfe4 at zfs_unmount_snap+0x114 #6 0xffffffff81a71301 at zfs_ioc_destroy_snaps+0xc1 #7 0xffffffff81a6fd64 at zfsdev_ioctl+0x664 #8 0xffffffff80835dc9 at devfs_ioctl_f+0x139 #9 0xffffffff809a8c85 at kern_ioctl+0x255 #10 0xffffffff809a8980 at sys_ioctl+0x140 #11 0xffffffff80d5695f at amd64_syscall+0x40f #12 0xffffffff80d3bbbb at Xfast_syscall+0xfb Uptime: 7m17s Dumping 419 out of 3995 MB:..4%..12%..23%..31%..42%..54%..61%..73%..81%..92% Reading symbols from /boot/kernel/zfs.ko.symbols...done. Loaded symbols for /boot/kernel/zfs.ko.symbols Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /boot/kernel/opensolaris.ko.symbols Reading symbols from /boot/kernel/ums.ko.symbols...done. Loaded symbols for /boot/kernel/ums.ko.symbols Reading symbols from /boot/kernel/pflog.ko.symbols...done. Loaded symbols for /boot/kernel/pflog.ko.symbols Reading symbols from /boot/kernel/pf.ko.symbols...done. Loaded symbols for /boot/kernel/pf.ko.symbols #0 doadump (textdump=3D) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=3D) at pcpu.h:219 #1 0xffffffff80950d12 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:486 #2 0xffffffff809510f5 in vpanic (fmt=3D, ap=3D) at /usr/src/sys/kern/kern_shutdown.c:889 #3 0xffffffff80950f83 in panic (fmt=3D0x0) at /usr/src/sys/kern/kern_shutdown.c:818 #4 0xffffffff809f78e5 in vputx (vp=3D, func=3D) at /usr/src/sys/kern/vfs_subr.c:2348 #5 0xffffffff809f1139 in dounmount (mp=3D0xfffff800052da660, flags=3D, td=3D) at /usr/src/sys/kern/vfs_mount.c:1359 #6 0xffffffff81a6dfe4 in zfs_unmount_snap (snapname=3D) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/z= fs_ioctl.c:3485 #7 0xffffffff81a71301 in zfs_ioc_destroy_snaps ( poolname=3D0xfffffe003b89b000 "hippo", innvl=3D, outnvl=3D0xfffff80092925060) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/z= fs_ioctl.c:3558 #8 0xffffffff81a6fd64 in zfsdev_ioctl (dev=3D, zcmd=3D, arg=3D, flag=3D, td=3D) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/z= fs_ioctl.c:6278 #9 0xffffffff80835dc9 in devfs_ioctl_f (fp=3D0xfffff8001c036230, com=3D3222821411, data=3D0xfffffe011b427a20, cred=3D, td=3D0xfffff80005b3a960) at /usr/src/sys/fs/devfs/devfs_vnops.c:786 #10 0xffffffff809a8c85 in kern_ioctl (td=3D0xfffff80005b3a960, fd=3D, com=3D0) at file.h:321 #11 0xffffffff809a8980 in sys_ioctl (td=3D0xfffff80005b3a960, uap=3D0xfffffe011b427b80) at /usr/src/sys/kern/sys_generic.c:718 #12 0xffffffff80d5695f in amd64_syscall (td=3D0xfffff80005b3a960, traced=3D= 0) at subr_syscall.c:141 #13 0xffffffff80d3bbbb in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:396 #14 0x0000000801a05f3a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 5 13:36:44 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29F4BCA0822 for ; Thu, 5 Jan 2017 13:36:44 +0000 (UTC) (envelope-from admin@x199.save85off.com) Received: from x199.save85off.com (x199.save85off.com [43.240.238.199]) by mx1.freebsd.org (Postfix) with ESMTP id CE8BD1509 for ; Thu, 5 Jan 2017 13:36:43 +0000 (UTC) (envelope-from admin@x199.save85off.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=save85off; d=x199.save85off.com; h=MIME-Version:From:To:Date:Subject:Content-Type:Content-Transfer-Encoding; i=admin@x199.save85off.com; bh=RnpOt9fU2mOWdx5Xayou/BLZBbQ=; b=V4uviIc1ZqhjT83ikJBOBrMmBGEQ6uijpLQBGxgAjPJNeIZxFhBRISCb267CWHQRKl+AlbX6rFNk adAy4Yd/pLRSOM5uAbg3oiR9IMVGRW8ND/vjOoHVFzz5MrGi0QaZP3q7y5Rdt3JIM1ydOTfGXKR0 6FL6NcoDsY5I/EyTUDo= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=save85off; d=x199.save85off.com; b=hBPjt/ob07Tten4B+at6lDmyOe8yBQnqmg8e4P2Izyl1lLurQbw3/wiD2kUbfzFGGehpZjUb2Znl gpwEQ7wyEBlVqjG8B7LEGgERTB5/Qr/sW/Lwfy6uIiOWgNm6278wxvtNS0Nj7DpqHxFd2RY9TKrZ cd2zE0acLzB+nV1TTjo=; From: "Michael Kors Discount" To: freebsd-fs@freebsd.org Date: 5 Jan 2017 21:26:44 +0800 Subject: The Best Deal You'll Find on Cyber Monday win 192$ MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 13:36:44 -0000 From owner-freebsd-fs@freebsd.org Thu Jan 5 13:51:16 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3597ACA1991 for ; Thu, 5 Jan 2017 13:51:16 +0000 (UTC) (envelope-from dgeo@centrale-marseille.fr) Received: from mel0.ec-m.fr (melout.ec-m.fr [147.94.19.37]) (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 EF17114CB for ; Thu, 5 Jan 2017 13:51:15 +0000 (UTC) (envelope-from dgeo@centrale-marseille.fr) Subject: Re: Recommended HBA for ZFS, contemporary DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=centrale-marseille.fr; s=smtp0; t=1483624273; bh=Y/m2VZn9OHmekEaMwkIdbaNGRTOjtUd1GtxUsGub/vk=; h=Subject:To:References:From:Date:In-Reply-To; b=n+ouCi4u9DCliEab5S21lIniLN8oY1LcjAki3yB5O88JxvIjIHchdkyFqp1dyz314 C+MNUFkA5HRO0NgbGO/RCl8GZJimjE9pEx+ibV8rC42o/Mq8Xe/UrAHyg3bweEZCZz elrwDZGCQ1piw0GYF9qSkEOL4HR9hCQRpybbN3newqJmO06weGx+E6i5Eru2gN3z2e Wkwz5RQ/9t+fsXkUh8QdukY5MnMBm2RZcXUICMAtC0IqjhnzGQQTZv8cP3Vs8rOwSz AxqEinlbT2RykBmlVVrx06TtYyB/lyAN3OtdcIcN9p/xXOVEVJoc7mXA/x3+6iOd3G Uv0cSkQO2vdTg== To: freebsd-fs@freebsd.org References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> <61997358-1660-20d1-1067-df4dc01ede7f@centrale-marseille.fr> From: geoffroy desvernay Message-ID: <7b9ddf9e-913c-7c6e-a6c0-e3a43a1595ed@centrale-marseille.fr> Date: Thu, 5 Jan 2017 14:51:12 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 13:51:16 -0000 On 10/19/2016 18:40, Ben RUBSON wrote: > >> On 19 Oct 2016, at 17:19, geoffroy desvernay wrote: >> >> On 10/19/2016 09:20, Ben RUBSON wrote: >>> Thank you Rich. >>> >>> I saw that the LSI 3008 can be put in IT mode, as with the well known 2008. >>> Firmware & drivers seem to be well maintained, with a P13 release last month. >>> 2 good points. >>> >>> However I did not found much much user feedback on it, nor recommandations. >>> There should be no surprise compared to the 2008, but we never know... >>> >> Well, I just received one, and it seems complicated for the moment (or I >> missed something important): > > Some of your drives seems to be not correctly detected. > What "sas3ircu 0 display" returns ? > Does "geom disk list" correctly shows your disks ? > > Firmware seems quite old too. Does it suits the driver version ? > > Ben > Thank you Ben and sorry, I missed your response :( I found the solution (on scsi@) - see http://marc.info/?l=freebsd-scsi&m=148362244824907&w=2 The sas3008 controller(s) I used were OK, the problem was solved by low-level-formatting the drives to disable a 'type 2 protection' (don't ask me more on this I wouldn't be able to explain ;) Now I have two sas3008 (IT mode) working, and two 'dell H330' in 'HBA mode' (that seems to be sas3008 chips as well) in production, and never had problems with them ;) -- *geoffroy desvernay* C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille From owner-freebsd-fs@freebsd.org Fri Jan 6 15:52:36 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9764CA21AF for ; Fri, 6 Jan 2017 15:52:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 992221626 for ; Fri, 6 Jan 2017 15:52:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v06FqSbt004694 for ; Fri, 6 Jan 2017 15:52:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204764] Filesystem deadlock, process in vodead state Date: Fri, 06 Jan 2017 15:52:28 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rs@bytecamp.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2017 15:52:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204764 Robert Schulze changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed Resolution|--- |FIXED --- Comment #34 from Robert Schulze --- Since the problem has been fixed, I think this PR can be closed now. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Jan 6 17:03:39 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D560CA2537 for ; Fri, 6 Jan 2017 17:03:39 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 186971F4F for ; Fri, 6 Jan 2017 17:03:39 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qk0-x233.google.com with SMTP id a20so81260202qkc.1 for ; Fri, 06 Jan 2017 09:03:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DDIuRldAxHGCaXFuakSZdydtuohkYoMBc++jDijEMgE=; b=vGv/TpCsNl7tDDGLAxQgz+uid6bxPb8CKWFHQASE6Q3/Hf7BlYZLyrw+Bt+dcw8JeP mfM02wVnc6LKidAFyXmD5G/83QkKMn8+00f5mrVgc6HYhjD1D/oZPS/huDRNQ6XEIAx/ VojaVAUwjNBAZn3f59t/sxxpBlSQX7CRlDNkjx0CIig1ZLxOBzz9T3OG06IP6NTeGREg Tlyhh7/Qp8Sm4+Khpfk4s2qNNVlFAqLD2jbHIL/0c5J0IgGDHHvL7oPq4bbgFGYid9tS zqMMptr3iqrcuZNex3Gq0p+UuMSp5fZdJqxs9iVEt1spNHO1dMUPt53GCJFJ2ADFeQ3b L6NQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DDIuRldAxHGCaXFuakSZdydtuohkYoMBc++jDijEMgE=; b=SY9SxVHdoSolfZPL6PVSDwQjuXrevXW86rWfqc640EsF5sozY4jXCDgpuJB9zB6wHi IukspwUYdzuNd+tZRLcFz7NWPmy8kj89VB7Ro1mMdAykZEFbD+CyAxTSK0FK7JiS06tH 0p+H3z7oErhRO4UxqIeiyn3aZf9wjSW1MpMsEl+VlEORTZQeEuXbXczAYsoKPtIwf5ro Kxwar9vK7zybKMXC5wY0bo0JjqFXBRnjBFYeOnKs0/XToW1JPHffClNwOlFSoklJ0ivM q1gC+V2ilfaejERyb7xyQZ889WkLJoAdT+X8aurkmINrGpRqg526YQXF5iUS9JqYQOIC iGbw== X-Gm-Message-State: AIkVDXKOJIkqp4qbtL6AS/0IFw2TyUqH+Bm72EFi6e4kwSeBnfIQ80ww7eo3ODDERH/cF4MceCQ2wA37l+cyfQ== X-Received: by 10.55.112.65 with SMTP id l62mr87155886qkc.76.1483722218124; Fri, 06 Jan 2017 09:03:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.165.161 with HTTP; Fri, 6 Jan 2017 09:03:37 -0800 (PST) In-Reply-To: References: From: Freddie Cash Date: Fri, 6 Jan 2017 09:03:37 -0800 Message-ID: Subject: Re: Check status of background destroy To: Xin LI Cc: FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2017 17:03:39 -0000 On Wed, Jan 4, 2017 at 10:43 AM, Xin LI wrote: > Try setting vfs.zfs.free_max_blocks to 100000 (this is an arbitrary > number, can be larger, limits maximum blocks being freed per txg; see > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D271532 for > details). > > You can inspect the progress with DTrace by looking at zfs-dbgmsg. > =E2=80=8BThis is looking promising. Booting off an 11.0-based mfsBSD didn't work (locked up after "Trying to mount root from /dev/md0"). Booting off a 10.3-based mfsBSD worked. Set that sysctl, then imported the pool without issues. The box has now been running for just over 24 hours. ARC is sitting at 93 GB, with Wired at 116 GB. Previously, the ARC would only be around 10 GB with Wired over 120 GB. "zpool iostat" shows lots of reads and writes happening to the pool. And the Avail space is slowly ticking upwards. Now just need to wait and see how long it takes to free up all 40 TB of referenced space. :) Thanks for the info! --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@freebsd.org Fri Jan 6 22:40:15 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D658CA2A4C for ; Fri, 6 Jan 2017 22:40:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 3D0821724 for ; Fri, 6 Jan 2017 22:40:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v06MeEbm037850 for ; Fri, 6 Jan 2017 22:40:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 215797] fs/fuse : allow_other & allow_root not restricted to root Date: Fri, 06 Jan 2017 22:40:15 +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: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2017 22:40:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215797 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org Keywords| |patch --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Jan 7 09:52:51 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13EC9C9FDFF for ; Sat, 7 Jan 2017 09:52:51 +0000 (UTC) (envelope-from brscvs@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 9E4C315F6 for ; Sat, 7 Jan 2017 09:52:50 +0000 (UTC) (envelope-from brscvs@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id c85so51133107wmi.1 for ; Sat, 07 Jan 2017 01:52:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=CZIN5KO9oQfjsMninpsGO8QusFuY3RKoKQMonucmyDg=; b=rUgvUQ2ZWyNBVkwh6awMDpehd0JAiETlpJ99IZCM1ZfD1ysU2t1xH9B0E+Y61UanUV Yp6nRtNZrEoz4LS9U7c8vOq/sr1+NnlyZ5ZR4AF67Sb63RYhEQZJP8cqfZxRP3+kvQ8D XgFXEigRY4VHs12AeoXmM0/g8S7AdfcpCflIRQi6ktYEHz3tx2B4o1pEkpcTOevpCVLy nzxwNy7chfSIAOVCHR6eNv1g1bI+gTpvfWoD2mMHZUXr4fAAZJqitLrgKvz9Et5hGcpq TssTjZl/i5t7IfSxzlqmQK81Hgc/QKxsjTJgrQuhS7geu5/seiuqoWxACE05WqHG0BIz kVNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=CZIN5KO9oQfjsMninpsGO8QusFuY3RKoKQMonucmyDg=; b=TKaITgc5Qv/ZCeLB6UTa6ZPYHHBf7gBxT3QCsKYjWcbsW+bTlPwS/Xgtp26euCnYmG zGwyGH+DfwUpSjfTrBy5Br/UCcodpDktrDfshj+Czcm/lipuypMchrijv+qOdpWx0Gw3 k/An7qwAmucETcfolflgLVqapwx9V/n3ZObNA4sf4rR0v4bFA+cEZLo62fmXSrItwjYs XN1U9cnlgo+15oF/gJMLKXtcc11nqd1QH8aHVtzTsBddU4zG5ZDWlZQu6AJXV6rM3oHI zgvxRUfQplIlKr0BVKQ2j7B2UTKAec9yVGGT604DsUp6x4gHYnIlLwYd+9bIShnUDYZW YHZg== X-Gm-Message-State: AIkVDXJgv2ECgDARAEafPAzxe/Mb75dtWzJAJO5NzRL1EEymLBh2TAm/4Aqap/6xGUlyhA== X-Received: by 10.28.23.137 with SMTP id 131mr951432wmx.121.1483782768907; Sat, 07 Jan 2017 01:52:48 -0800 (PST) Received: from [192.168.1.42] ([78.167.14.181]) by smtp.gmail.com with ESMTPSA id y3sm82894912wjy.34.2017.01.07.01.52.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Jan 2017 01:52:48 -0800 (PST) To: FreeBSD Filesystems From: "baris.cavus" Subject: Mountd process stuck in D( TASK_UNINTERRUPTIBLE) state - Freebsd 10.3 stable Message-ID: <1bf6c468-4b51-2c65-3aff-6687782811f3@gmail.com> Date: Sat, 7 Jan 2017 12:52:47 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2017 09:52:51 -0000 I created a zfs volume ,edited the exports file and reloaded mountd service. Then mountd process stuck in D(TASK_UNINTERRUPTIBLE) state, What could be the reason for this? Thanks, Baris From owner-freebsd-fs@freebsd.org Sat Jan 7 12:12:12 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A6C0CA2FA0 for ; Sat, 7 Jan 2017 12:12:12 +0000 (UTC) (envelope-from cp_public@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B53FB1F7A for ; Sat, 7 Jan 2017 12:12:11 +0000 (UTC) (envelope-from cp_public@gmx.de) Received: from [192.191.1.201] ([37.201.141.123]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MV6PJ-1byYVE3pFd-00YTp0 for ; Sat, 07 Jan 2017 13:12:05 +0100 To: freebsd-fs@freebsd.org From: Christoph Pomaska Subject: Stupidly destroyed a ZFS pool by recreating with the same name Message-ID: <4d186184-c118-84db-4a53-d027eaa32d89@gmx.de> Date: Sat, 7 Jan 2017 13:12:05 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:V/U06QEb2ZOnyDmt79EY6GkUCpUyX0sWyJpDDHmUPUY0Y36zD3v E1JiXdGsNSQ6VI0mxHY8OsYNF7/X/bSKxOIXQe1rAjc8I7z5Ib4MxGTeqC5SPxQT6IzAUbc 1UljSCkpKQQ9IC7OO9ujR5dSs6f0w8rHTI1rUe/QrXYl8r847qi2HGtHx/aNPBtZMZoE4ap VLqh30kG2SUvKtpkSLhGw== X-UI-Out-Filterresults: notjunk:1;V01:K0:pST0At9Qz6g=:1l2j7TnkxiFwpqpWP6+9tH pitXLOoqg6ufvULEj9RLQ3RTAnKj4j54oN1VjM/Ue395+VYlxha2zsPexNOpZWQUhDBGsHKoX cwuKDifJIThB47fQcrzurZ+dyAFvcA9myF6PYAgZHWuMgPq21yqrxEqs+WCWVl/3kwymcmv7Q K9+IbsybDDFp3VasVAVXnHIOvjTupXPuwaM/ZReMeQcnKvtQPVQuyfvKnCQqSkYZ+AvU/Gpcg VhJZMefupHtzQVPm413ssdLm/hCvtqXmRT1unp2+3eE4w1OCya11R2ojlHncdDFjQIw9ei+qU oLZqDA8XJ5MBIRPDGUiH93ITGVpBudiw0f68yh/lLAYQenXoB2U7lehFMI8G2G74mV1UG6lbi w8BekEKqZYsneXiK1zbhWA8YaNBS7PqNwmf1GS3EaaoDjEu5yAuiXlpEqKdu2heMnlCrJScpd r2e0dE6Zo71HA0MgzkdH0wwCSmTmOtz4XigGxz2hXXPae7J22+1XDaa7X2Xt8s14drG0SiEpo OqMUdKGj5wnlKxCHdHjDl/sDVHRO1AFSnu2Qw4hGLET39PS//CCIR8i8xOjaeqdRd50hBiexA fW/yqYlroPbw4VUv/XD3rFBcRLRwu4XqDtWxg1jMcEZkmVsevu73afc7J32EOlEBY6vx22gKS D9oKsYMTi02wuxPG+ElEmZlIDvgt3OvM6DdPIGBSCIN3PHr2Ceupe1ucBhzB3RtnH2PYjtJlp qTL8QqW6PZtVnddfQrEsN6RB/zrriovnB2BS8YySEzi5jw6+Ax1f081jPcbTwCIbzCGRtOyYs qjf556vFyLK6bz90lc2UdDHkdT2xmrgYULQFtXwbpdhDvlkLrP2dwu5OZf00a/Mi1J0GYjIVD yNxpuOWABUlTTNyInasESaiK8MmqLGFptLyjvTiONTVb8gy7VhheCHebV4maxZgyziS2bF2Us urQGeC6ypx//0KudeDjeBZcerB5B+aBKXsdHZCCEi3jRMMsIQcykwaVwKEZZLDpz8yhG3aSnI S1PSc3CK9k98+8C1eTbCfrE= X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2017 12:12:12 -0000 Hello dear freebsd-fs-community, this is my first contact within a mailing list, so I hope I got everything right... I not-so-recently set up a ZFS data pool on my Arch Linux setup, either for experimenting and also because I think that the concept is a pretty cool thing. Well, as you can read in the subject title, I recently accidentally recreated the ZFS pool that died, because I switched some drives out, instead of importing it (as not stupidly enough, I did it with the option -f, that's why it didn't ask me anything though). So, is there ANY way to get the original pool or at least ANYTHING back? Best regards Christoph From owner-freebsd-fs@freebsd.org Sat Jan 7 12:29:32 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FF72CA37E9 for ; Sat, 7 Jan 2017 12:29:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4AC3A1A58; Sat, 7 Jan 2017 12:29:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:a523:9283:113:736a]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 707E8721; Sat, 7 Jan 2017 15:29:31 +0300 (MSK) Date: Sat, 7 Jan 2017 15:29:33 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1551133578.20170107152925@serebryakov.spb.ru> To: Andriy Gapon , freebsd-fs Subject: Re: ZFS L2ARC checksum errors after compression In-Reply-To: <5695c647-9250-703d-35d8-8b125dbcd61b@FreeBSD.org> References: <921575537.20161029143626@serebryakov.spb.ru> <3dae7691-fcd1-b3b9-445c-b81d6f0cdc52@FreeBSD.org> <3bd7cb79-ec5a-3b7c-0642-24a7b1f001e6@FreeBSD.org> <5826F293.7020408@FreeBSD.org> <5695c647-9250-703d-35d8-8b125dbcd61b@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="----------0A41C0208029F663C" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2017 12:29:32 -0000 ------------0A41C0208029F663C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: base64 SGVsbG8gQW5kcml5LA0KDQpTYXR1cmRheSwgTm92ZW1iZXIgMTIsIDIwMTYsIDI6NTY6MDUg UE0sIHlvdSB3cm90ZToNCg0KPj4+IGJlY2F1c2Ugb2YgdGhlIGNvbmZ1c2luZyB2YXJpYWJs ZSBuYW1lcyBJIG1hZGUgYSBtaXN0YWtlIGluIHRoZSBwYXRjaCB0aGF0IEkNCj4+PiBvZmZl cmVkIHlvdS4gIENvdWxkIHlvdSBwbGVhc2UgdHJ5IGEgbmV3IHNsaWdodCBkaWZmZXJlbnQg cGF0Y2g/DQo+Pj4gQWxzbywgSSB0aGluayB0aGF0IHRoZXJlIGNvdWxkIGJlIGFub3RoZXIg cHJvYmxlbSBpbiBhZGRpdGlvbiB0byB0aGUgb25lIHRoYXQgSQ0KPj4+IHNlZS4gIEJ1dCBJ IGFtIHF1aXRlIGJ1c3kgYXQgdGhlIG1vbWVudCwgbm8gdGltZSB0byBpbnZlc3RpZ2F0ZS4g IE1heWJlIG9uIHRoZQ0KPj4+IHdlZWtlbmQgb3Igc29tZSB0aW1lIG5leHQgd2Vlay4NCj4+ IA0KPj4gIE5vcGUuIFNlY29uZCB2ZXJzaW9uIG9mIHBhdGNoIGRvZXNuJ3QgaGVscCBlaXRo ZXIuIFN0aWxsIHVucmVhbGlzdGljDQo+PiBoaWdoIGNvbXByZXNzaW9uIHJhdGlvIChBTExP Qy9TSVpFLCBzbGlnaHRseSBsZXNzIHRoYW4gMiBvbiBtb3N0bHkNCj4+IHVuY29tcHJlc3Nl YWJsZSBkYXRhKSwgMTYuMEUgb2YgRlJFRSBzaW5jZSBBTExPQyBiZWNvbWVzIGdyZWF0ZXIg dGhhbg0KPj4gU0laRSBhbmQgbG90IG9mIGNoZWNrc3VtIGVycm9ycyBzaW5jZSB0aGUgc2Ft ZSBtb21lbnQuDQoNCj4gSSBzZWUuDQo+IENvdWxkIHlvdSBwbGVhc2Ugc2VuZCBtZSBmdWxs IG91dHB1dCBvZiB0aGUgZm9sbG93aW5nIGNvbW1hbmRzPw0KPiB6cG9vbCBzdGF0dXMgLXYN Cj4genBvb2wgbGlzdCAtdg0KPiB6ZGIgLUNDICRwb29sDQogQW55IG5ld3Mgb24gdGhpcyBp c3N1ZT8gU2hvdWxkIEkgZmlsZSBmb3JtYWwgUFI/DQoNCg0KLS0gDQpCZXN0IHJlZ2FyZHMs DQogTGV2ICAgICAgICAgICAgICAgICAgICAgICAgICAgIG1haWx0bzpsZXZARnJlZUJTRC5v cmc= ------------0A41C0208029F663C Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJYcN8tXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePMzoP/2mZ4N811S+frwGDVGeI9EgD /V82+o2CLgRLrXPHKhdvfYQYbLdyr+bbpG6UPOju/fWfJbztdjjDNv/H2zfL9wy6 NgEZqTLLbHc1WHefHQMx3uQhUtxrroSj0I11VHA4aSagc7L4UQmXBTB/ns9Yp3a4 ycYSxuIWhavuR9j9Ip5xD3MKYQ61dL62Vo9oYAqb1XrhaTEK9z7zhvO7DqlvJQ9u n/Ghu8ayPmFtJgNo64xYVO47OdjGatDEgy2VZF44wZvGTXf8gapOsjaHxjWeLAKB kGC4a3rbAafCVcH5X85oiovOSEWnswbKfTX7mk9pbP2YHUT4n/x+k4mV+J5lOat8 TxE/yMXuxxlDbemXvyPF3yjFNmkj01cKkcdCh7sciY7mz/46J79nN9aqXcqQqK70 CcxfkWDXiX4bEeKhxdWd+8I8armk/MWLTEJoxm3qAN+rQJSBznmsDuJCLv3mlkN/ pIQnAbQ3B/0GNSim+xwkUbxUvVDAmf8D9mvo8wihLS1rnfLxjHsYZEWG+03KYX+p efXOYr0VfzpHO84ULW+Ql3uQd7OXnKAa0Kk6GP59tJyUrQWnL0roelD89Jb9sWQK 1MzJ67PtClbaOeZd2ormV7oiZ9EoaNlm9kPtuciCsbW3wFGIjjRrEnhZMy7IIQok ATU3xRZ0GdwfdDXJU2hB =SxHp -----END PGP MESSAGE----- ------------0A41C0208029F663C--