From owner-freebsd-fs@FreeBSD.ORG Sun Nov 2 14:16:08 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 EA627F2E;
Sun, 2 Nov 2014 14:16:08 +0000 (UTC)
Received: from wonkity.com (wonkity.com [67.158.26.137])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "wonkity.com", Issuer "wonkity.com" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 81EB5A4D;
Sun, 2 Nov 2014 14:16:08 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
by wonkity.com (8.14.9/8.14.9) with ESMTP id sA2EG066008767
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
Sun, 2 Nov 2014 07:16:00 -0700 (MST)
(envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id sA2EFx5f008764;
Sun, 2 Nov 2014 07:16:00 -0700 (MST)
(envelope-from wblock@wonkity.com)
Date: Sun, 2 Nov 2014 07:15:59 -0700 (MST)
From: Warren Block <wblock@wonkity.com>
To: John <freebsd-lists@potato.growveg.org>
Subject: Re: gptboot: invalid backup GPT header
In-Reply-To: <20141101224426.GA69717@potato.growveg.org>
Message-ID: <alpine.BSF.2.11.1411020653130.97570@wonkity.com>
References: <20141101224426.GA69717@potato.growveg.org>
User-Agent: Alpine 2.11 (BSF 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
(wonkity.com [127.0.0.1]); Sun, 02 Nov 2014 07:16:00 -0700 (MST)
Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Nov 2014 14:16:09 -0000
On Sat, 1 Nov 2014, John wrote:
> Hello lists,
>
> Not sure if this is a hardware problem or a filesystem problem, so have
> cc'd to freebsd-fs@
>
> The "problem" is on newly-installed freebsd 10.1 RC3. I say "problem" in
> inverted commas because it's not stopping it from booting and the server
> seems to run allright, I'm wondering if it's anything to worry about. As
> well as seeing gptboot: invalid backup GPT header *before* beastie
> starts, I see the following in dmesg:
>
> GEOM: mfid1: corrupt or invalid GPT detected.
> GEOM: mfid1: GPT rejected -- may not be recoverable.
>
> There are 4 disks installed - mfid0,1,2 & 3. mfid0 is a regular ufs gpt
> based disk. mfid1,2 and 3 together form a zfs raidz array. A thread on
> https://forums.freenas.org/index.php?threads/gpt-table-is-corrupt-or-invalid-error-on-bootup.12171/
> describes a similar problem - the thing is though the "erroring" disk is
> not a GPT disk, and the one in the example was.
>
> # gpart list mfid1
> gpart: No such geom: mfid1.
My guess is that mfid1 was used as a GPT disk before it was used for
ZFS. Installing ZFS to the whole disk leaves an unused and apparently
unwritten section at the end, so the backup GPT is still present in the
last few blocks (usually 33 blocks, but not always). That is the
"invalid backup GPT header".
Clearing the last blocks will remove the warning, at least if the
assumption is correct. ZFS is not supposed to be using the last portion
of the disk(*) to make replacing disks of slightly different sizes
easier. Still, I would back up either the whole array, the whole disk,
or at least the last 33 blocks of mfid1 first.
*: I don't know exactly how much of the last part of the disk is not
used by ZFS, do not recall an exact number being posted, and have not
gone spelunking through the code for it.
From owner-freebsd-fs@FreeBSD.ORG Sun Nov 2 21:00:07 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 B23527B9
for <freebsd-fs@FreeBSD.org>; Sun, 2 Nov 2014 21:00:07 +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 7562B347
for <freebsd-fs@FreeBSD.org>; Sun, 2 Nov 2014 21:00:07 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA2L07sL014354
for <freebsd-fs@FreeBSD.org>; Sun, 2 Nov 2014 21:00:07 GMT
(envelope-from bugzilla-noreply@FreeBSD.org)
Message-Id: <201411022100.sA2L07sL014354@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, 02 Nov 2014 21:00:07 +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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Nov 2014 21:00:07 -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
----------------+-----------+-------------------------------------------------
Needs MFC | 136470 | [nfs] Cannot mount / in read-only, over NFS
Needs MFC | 139651 | [nfs] mount(8): read-only remount of NFS volume
Needs MFC | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non
3 problems total for which you should take action.
From owner-freebsd-fs@FreeBSD.ORG Mon Nov 3 01:44:00 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 C705AC98;
Mon, 3 Nov 2014 01:44:00 +0000 (UTC)
Received: from potato.growveg.org (potato.growveg.org [62.49.247.163])
(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 86A38EB;
Mon, 3 Nov 2014 01:44:00 +0000 (UTC)
Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD))
(envelope-from <john@potato.growveg.org>)
id 1Xl6gI-000OSf-1H; Mon, 03 Nov 2014 01:43:42 +0000
Date: Mon, 3 Nov 2014 01:43:41 +0000
From: John <freebsd-lists@potato.growveg.org>
To: freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org
Subject: Re: gptboot: invalid backup GPT header
Message-ID: <20141103014341.GA91255@potato.growveg.org>
Mail-Followup-To: freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org
References: <20141101224426.GA69717@potato.growveg.org>
<alpine.BSF.2.11.1411020653130.97570@wonkity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.11.1411020653130.97570@wonkity.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: John <john@potato.growveg.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: john@potato.growveg.org
X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2014 01:44:00 -0000
On Sun, Nov 02, 2014 at 07:15:59AM -0700, Warren Block wrote:
> Clearing the last blocks will remove the warning, at least if the
> assumption is correct. ZFS is not supposed to be using the last
> portion of the disk(*) to make replacing disks of slightly different
> sizes easier. Still, I would back up either the whole array, the
> whole disk, or at least the last 33 blocks of mfid1 first.
Thanks for replying. So, in short - is my data on the array in any
danger, or is this just a cosmetic issue?
[I think the reason it happened is that during the install process,
where the installer asks you to choose partitions, I removed
*everything* from mfid1,2 & 3 as I knew zfs likes to deal with the raw
disk. I don't want to have to blat the system again though, unless
absolutely necessary].
--
John
From owner-freebsd-fs@FreeBSD.ORG Mon Nov 3 04:46:36 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 D75128C7;
Mon, 3 Nov 2014 04:46:36 +0000 (UTC)
Received: from wonkity.com (wonkity.com [67.158.26.137])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "wonkity.com", Issuer "wonkity.com" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 89164365;
Mon, 3 Nov 2014 04:46:36 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
by wonkity.com (8.14.9/8.14.9) with ESMTP id sA34PbKH024525
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
Sun, 2 Nov 2014 21:25:38 -0700 (MST)
(envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id sA34Pbum024495;
Sun, 2 Nov 2014 21:25:37 -0700 (MST)
(envelope-from wblock@wonkity.com)
Date: Sun, 2 Nov 2014 21:25:37 -0700 (MST)
From: Warren Block <wblock@wonkity.com>
To: John <freebsd-lists@potato.growveg.org>
Subject: Re: gptboot: invalid backup GPT header
In-Reply-To: <20141103014341.GA91255@potato.growveg.org>
Message-ID: <alpine.BSF.2.11.1411022120180.22743@wonkity.com>
References: <20141101224426.GA69717@potato.growveg.org>
<alpine.BSF.2.11.1411020653130.97570@wonkity.com>
<20141103014341.GA91255@potato.growveg.org>
User-Agent: Alpine 2.11 (BSF 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
(wonkity.com [127.0.0.1]); Sun, 02 Nov 2014 21:25:38 -0700 (MST)
Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2014 04:46:36 -0000
On Mon, 3 Nov 2014, John wrote:
> On Sun, Nov 02, 2014 at 07:15:59AM -0700, Warren Block wrote:
>> Clearing the last blocks will remove the warning, at least if the
>> assumption is correct. ZFS is not supposed to be using the last
>> portion of the disk(*) to make replacing disks of slightly different
>> sizes easier. Still, I would back up either the whole array, the
>> whole disk, or at least the last 33 blocks of mfid1 first.
>
> Thanks for replying. So, in short - is my data on the array in any
> danger, or is this just a cosmetic issue?
If the guess is correct, it's just cosmetic. Unless someone panics at
the warning and tries to repair it.
From owner-freebsd-fs@FreeBSD.ORG Mon Nov 3 08:00:10 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 846DF550
for <freebsd-fs@FreeBSD.org>; Mon, 3 Nov 2014 08:00: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 722CC95C
for <freebsd-fs@FreeBSD.org>; Mon, 3 Nov 2014 08:00: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 sA380AOo009435
for <freebsd-fs@FreeBSD.org>; Mon, 3 Nov 2014 08:00:10 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Message-Id: <201411030800.sA380AOo009435@kenobi.freebsd.org>
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [FreeBSD Bugzilla] Commit Needs MFC
MIME-Version: 1.0
X-Bugzilla-Type: whine
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
Date: Mon, 03 Nov 2014 08:00:10 +0000
Content-Type: text/plain
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2014 08:00:10 -0000
Hi,
You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed.
In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days.
This reminder is only sent on Mondays. Please file a bug about concerns you may have.
This search was scheduled by eadler@FreeBSD.org.
(3 bugs)
Bug 136470:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=136470
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-fs@FreeBSD.org
Status: Needs MFC
Resolution:
Summary: [nfs] Cannot mount / in read-only, over NFS
Bug 139651:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=139651
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-fs@FreeBSD.org
Status: Needs MFC
Resolution:
Summary: [nfs] mount(8): read-only remount of NFS volume does not work
Bug 144447:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144447
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-fs@FreeBSD.org
Status: Needs MFC
Resolution:
Summary: [zfs] sharenfs fsunshare() & fsshare_main() non functional
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 05:31:28 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 8604B138
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 05:31:28 +0000 (UTC)
Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "smtp.new-ukraine.org",
Issuer "smtp.new-ukraine.org" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 2C88B147
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 05:31:26 +0000 (UTC)
Received: on behalf of honored client by smtp.new-ukraine.org with ESMTP id
sA45TS0m079141
for <freebsd-fs@FreeBSD.org> on Tue, 4 Nov 2014 07:29:29 +0200 (EET)
Message-ID: <20141104072923.79140@smtp.new-ukraine.org>
Date: Tue, 04 Nov 2014 07:29:23 +0200
From: "Zeus Panchenko" <zeus@ibs.dn.ua>
To: <freebsd-fs@FreeBSD.org>
cc:
Subject: why no automount for one zfs?
Organization: I.B.S. LLC
Reply-To: "Zeus Panchenko" <zeus@ibs.dn.ua>
X-Attribution: zeus
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN
cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F
eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N
ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw
15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5
lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG
ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq
zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe
riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M
1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a
mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs
SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6
7tXQAAAAASUVORK5CYII=
X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
X-NewUkraine-Agent: mailfromd (7.99.92)
X-NewUkraine-URL: http://www.ibs.dn.ua/smtp.html
X-NewUkraine-VirStat: NO
X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures,
ScanHTML, ScanPDF
X-NewUkraine-SpamStat: NO
X-NewUkraine-SpamScore: -1.600 of 3.500
X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 05:31:28 -0000
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi all,
some times after installation I decided to dedicate separate ZFS with
mountpoint in my homedir for storage needs
but each reboot I have to mount it by hands with:
zfs unmount zroot_z-hp/storage && zfs mount zroot_z-hp/storage
after reboot this very fs is listed as mounted but the mount directory
for it, is empty ... after umount/mount everything appears on it's
expected place ...
please help me to understand why it does not automount after reboot?
> uname -a
FreeBSD 10.0-STABLE #0 r261303 amd64
partial output of
> zfs get all zroot_z-hp/storage
NAME PROPERTY VALUE SOURCE
zroot_z-hp/storage type filesystem -
zroot_z-hp/storage mounted yes -
zroot_z-hp/storage mountpoint /home/zeus/storage local
zroot_z-hp/storage sharenfs off default
zroot_z-hp/storage checksum fletcher4 inherited =
from zroot_z-hp
zroot_z-hp/storage compression off default
zroot_z-hp/storage atime off inherited =
from zroot_z-hp
zroot_z-hp/storage devices on default
zroot_z-hp/storage exec on default
zroot_z-hp/storage setuid on default
zroot_z-hp/storage readonly off default
zroot_z-hp/storage jailed off default
zroot_z-hp/storage snapdir hidden default
zroot_z-hp/storage aclmode discard default
zroot_z-hp/storage aclinherit restricted default
zroot_z-hp/storage canmount on default
zroot_z-hp/storage xattr off temporary
zroot_z-hp/storage copies 1 default
zroot_z-hp/storage version 5 -
=2D --=20
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlRYZDMACgkQr3jpPg/3oyozlACgrQfGK/7Ch9CQMRqJ0T4/+/Qr
kkMAoKNYOTZdlxdQPxUe8Y9hfg7XJg0v
=3DS86e
=2D----END PGP SIGNATURE-----
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 06:06:50 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 C2BB48F8
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 06:06:50 +0000 (UTC)
Received: from mail.slu.se (tmgext2-1.slu.se [77.235.224.51])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 57FC26A6
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 06:06:49 +0000 (UTC)
Received: from Exchange2-2.slu.se (130.238.96.155) by Tmg2-1.slu.se
(130.238.96.151) with Microsoft SMTP Server (TLS) id 14.3.210.2; Tue, 4 Nov
2014 07:06:40 +0100
Received: from Exchange2-1.slu.se ([130.238.96.154]) by exchange2-2
([130.238.96.155]) with mapi id 14.03.0210.002; Tue, 4 Nov 2014 07:06:40
+0100
From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= <Karli.Sjoberg@slu.se>
To: "zeus@ibs.dn.ua" <zeus@ibs.dn.ua>
Subject: Re: why no automount for one zfs?
Thread-Topic: why no automount for one zfs?
Thread-Index: AQHP9/V/D2nTSkFDkEqe7tQVOHCq2A==
Date: Tue, 4 Nov 2014 06:06:40 +0000
Message-ID: <5F9E965F5A80BC468BE5F40576769F099DF85BC1@exchange2-1>
References: <20141104072923.79140@smtp.new-ukraine.org>
In-Reply-To: <20141104072923.79140@smtp.new-ukraine.org>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [77.235.228.32]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "freebsd-fs@FreeBSD.org" <freebsd-fs@FreeBSD.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 06:06:50 -0000
T24gVHVlLCAyMDE0LTExLTA0IGF0IDA3OjI5ICswMjAwLCBaZXVzIFBhbmNoZW5rbyB3cm90ZToK
PiAtLS0tLUJFR0lOIFBHUCBTSUdORUQgTUVTU0FHRS0tLS0tCj4gSGFzaDogU0hBMQo+IAo+IGhp
IGFsbCwKPiAKPiBzb21lIHRpbWVzIGFmdGVyIGluc3RhbGxhdGlvbiBJIGRlY2lkZWQgdG8gZGVk
aWNhdGUgc2VwYXJhdGUgWkZTIHdpdGgKPiBtb3VudHBvaW50IGluIG15IGhvbWVkaXIgZm9yIHN0
b3JhZ2UgbmVlZHMKPiAKPiBidXQgZWFjaCByZWJvb3QgSSBoYXZlIHRvIG1vdW50IGl0IGJ5IGhh
bmRzIHdpdGg6Cj4gCj4gemZzIHVubW91bnQgenJvb3Rfei1ocC9zdG9yYWdlICYmIHpmcyBtb3Vu
dCB6cm9vdF96LWhwL3N0b3JhZ2UKPiAKPiBhZnRlciByZWJvb3QgdGhpcyB2ZXJ5IGZzIGlzIGxp
c3RlZCBhcyBtb3VudGVkIGJ1dCB0aGUgbW91bnQgZGlyZWN0b3J5Cj4gZm9yIGl0LCBpcyBlbXB0
eSAuLi4gYWZ0ZXIgdW1vdW50L21vdW50IGV2ZXJ5dGhpbmcgYXBwZWFycyBvbiBpdCdzCj4gZXhw
ZWN0ZWQgcGxhY2UgLi4uCj4gCj4gcGxlYXNlIGhlbHAgbWUgdG8gdW5kZXJzdGFuZCB3aHkgaXQg
ZG9lcyBub3QgYXV0b21vdW50IGFmdGVyIHJlYm9vdD8KClRvIGhhdmUgWkZTIGZpbGVzeXN0ZW1z
IG1vdW50ZWQgYXQgYm9vdCwgZmlyc3Qgb2YgYWxsLCAiY2FubW91bnQiIG11c3QKYmUgb24gKGNo
ZWNrKSBhbmQgdGhlbiB5b3UgaGF2ZSBuZWVkIHRvIGhhdmU6Cnpmc19lbmFibGU9IllFUyIKaW4g
InJjLmNvbmYiLiBUaGVuIHRoZXJlwrRzIGFsc28gdGhlIHF1ZXN0aW9uIGhvdyB0aGUgcGFyZW50
IGZpbGVzeXN0ZW1zCiIvaG9tZS96ZXVzIiBhbmQgIi9ob21lIiBhcmUgbW91bnRlZD8gQXJlIHRo
ZXkgYWxzbyBaRlM/CgovSwoKPiAKPiA+IHVuYW1lIC1hCj4gRnJlZUJTRCAxMC4wLVNUQUJMRSAj
MCByMjYxMzAzIGFtZDY0Cj4gCj4gcGFydGlhbCBvdXRwdXQgb2YKPiA+IHpmcyBnZXQgYWxsIHpy
b290X3otaHAvc3RvcmFnZQo+IE5BTUUgICAgICAgICAgICAgICAgUFJPUEVSVFkgICAgICAgICAg
ICAgIFZBTFVFICAgICAgICAgICAgICAgICAgU09VUkNFCj4genJvb3Rfei1ocC9zdG9yYWdlICB0
eXBlICAgICAgICAgICAgICAgICAgZmlsZXN5c3RlbSAgICAgICAgICAgICAtCj4genJvb3Rfei1o
cC9zdG9yYWdlICBtb3VudGVkICAgICAgICAgICAgICAgeWVzICAgICAgICAgICAgICAgICAgICAt
Cj4genJvb3Rfei1ocC9zdG9yYWdlICBtb3VudHBvaW50ICAgICAgICAgICAgL2hvbWUvemV1cy9z
dG9yYWdlICAgICBsb2NhbAo+IHpyb290X3otaHAvc3RvcmFnZSAgc2hhcmVuZnMgICAgICAgICAg
ICAgIG9mZiAgICAgICAgICAgICAgICAgICAgZGVmYXVsdAo+IHpyb290X3otaHAvc3RvcmFnZSAg
Y2hlY2tzdW0gICAgICAgICAgICAgIGZsZXRjaGVyNCAgICAgICAgICAgICAgaW5oZXJpdGVkIGZy
b20genJvb3Rfei1ocAo+IHpyb290X3otaHAvc3RvcmFnZSAgY29tcHJlc3Npb24gICAgICAgICAg
IG9mZiAgICAgICAgICAgICAgICAgICAgZGVmYXVsdAo+IHpyb290X3otaHAvc3RvcmFnZSAgYXRp
bWUgICAgICAgICAgICAgICAgIG9mZiAgICAgICAgICAgICAgICAgICAgaW5oZXJpdGVkIGZyb20g
enJvb3Rfei1ocAo+IHpyb290X3otaHAvc3RvcmFnZSAgZGV2aWNlcyAgICAgICAgICAgICAgIG9u
ICAgICAgICAgICAgICAgICAgICAgZGVmYXVsdAo+IHpyb290X3otaHAvc3RvcmFnZSAgZXhlYyAg
ICAgICAgICAgICAgICAgIG9uICAgICAgICAgICAgICAgICAgICAgZGVmYXVsdAo+IHpyb290X3ot
aHAvc3RvcmFnZSAgc2V0dWlkICAgICAgICAgICAgICAgIG9uICAgICAgICAgICAgICAgICAgICAg
ZGVmYXVsdAo+IHpyb290X3otaHAvc3RvcmFnZSAgcmVhZG9ubHkgICAgICAgICAgICAgIG9mZiAg
ICAgICAgICAgICAgICAgICAgZGVmYXVsdAo+IHpyb290X3otaHAvc3RvcmFnZSAgamFpbGVkICAg
ICAgICAgICAgICAgIG9mZiAgICAgICAgICAgICAgICAgICAgZGVmYXVsdAo+IHpyb290X3otaHAv
c3RvcmFnZSAgc25hcGRpciAgICAgICAgICAgICAgIGhpZGRlbiAgICAgICAgICAgICAgICAgZGVm
YXVsdAo+IHpyb290X3otaHAvc3RvcmFnZSAgYWNsbW9kZSAgICAgICAgICAgICAgIGRpc2NhcmQg
ICAgICAgICAgICAgICAgZGVmYXVsdAo+IHpyb290X3otaHAvc3RvcmFnZSAgYWNsaW5oZXJpdCAg
ICAgICAgICAgIHJlc3RyaWN0ZWQgICAgICAgICAgICAgZGVmYXVsdAo+IHpyb290X3otaHAvc3Rv
cmFnZSAgY2FubW91bnQgICAgICAgICAgICAgIG9uICAgICAgICAgICAgICAgICAgICAgZGVmYXVs
dAo+IHpyb290X3otaHAvc3RvcmFnZSAgeGF0dHIgICAgICAgICAgICAgICAgIG9mZiAgICAgICAg
ICAgICAgICAgICAgdGVtcG9yYXJ5Cj4genJvb3Rfei1ocC9zdG9yYWdlICBjb3BpZXMgICAgICAg
ICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAgICBkZWZhdWx0Cj4genJvb3Rfei1ocC9zdG9y
YWdlICB2ZXJzaW9uICAgICAgICAgICAgICAgNSAgICAgICAgICAgICAgICAgICAgICAtCj4gCj4g
LSAtLSAKPiBaZXVzIFYuIFBhbmNoZW5rbwkJCQlqaWQ6emV1c0BpbS5pYnMuZG4udWEKPiBJVCBE
cHQuLCBJLkIuUy4gTExDCQkJCQkgIEdNVCsyIChFRVQpCj4gLS0tLS1CRUdJTiBQR1AgU0lHTkFU
VVJFLS0tLS0KPiBWZXJzaW9uOiBHbnVQRyB2MQo+IAo+IGlFWUVBUkVDQUFZRkFsUllaRE1BQ2dr
UXIzanBQZy8zb3lvemxBQ2dyUWZHSy83Q2g5Q1FNUnFKMFQ0LysvUXIKPiBra01Bb0tOWU9UWmRs
eGRRUHhVZThZOWhmZzdYSmcwdgo+ID1TODZlCj4gLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0t
Cj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBmcmVl
YnNkLWZzQGZyZWVic2Qub3JnIG1haWxpbmcgbGlzdAo+IGh0dHA6Ly9saXN0cy5mcmVlYnNkLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtZnMKPiBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkg
bWFpbCB0byAiZnJlZWJzZC1mcy11bnN1YnNjcmliZUBmcmVlYnNkLm9yZyIKCgoKLS0gCgpNZWQg
VsOkbmxpZ2EgSMOkbHNuaW5nYXIKCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KS2FybGkgU2rDtmJl
cmcKU3dlZGlzaCBVbml2ZXJzaXR5IG9mIEFncmljdWx0dXJhbCBTY2llbmNlcyBCb3ggNzA3OSAo
VmlzaXRpbmcgQWRkcmVzcwpLcm9uw6VzdsOkZ2VuIDgpClMtNzUwIDA3IFVwcHNhbGEsIFN3ZWRl
bgpQaG9uZTogICs0Ni0oMCkxOC02NyAxNSA2NgprYXJsaS5zam9iZXJnQHNsdS5zZQo=
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 06:51:31 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 899BDE2E
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 06:51:31 +0000 (UTC)
Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "smtp.new-ukraine.org",
Issuer "smtp.new-ukraine.org" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 0E843AC2
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 06:51:30 +0000 (UTC)
Received: on behalf of honored client by smtp.new-ukraine.org with ESMTP id
sA46pOqS081578 on Tue, 4 Nov 2014 08:51:24 +0200 (EET)
Message-ID: <20141104085120.81576@smtp.new-ukraine.org>
Date: Tue, 04 Nov 2014 08:51:20 +0200
From: "Zeus Panchenko" <zeus@ibs.dn.ua>
To: "=?us-ascii?Q?=3D=3Futf-8=3FB=3FS2FybGkgU2rDtmJlcmc=3D=3F=3D?="
<Karli.Sjoberg@slu.se>
Subject: Re: why no automount for one zfs?
In-reply-to: Your message of Tue, 4 Nov 2014 06:06:40 +0000
<5F9E965F5A80BC468BE5F40576769F099DF85BC1@exchange2-1>
References: <20141104072923.79140@smtp.new-ukraine.org>
<5F9E965F5A80BC468BE5F40576769F099DF85BC1@exchange2-1>
Organization: I.B.S. LLC
Reply-To: "Zeus Panchenko" <zeus@ibs.dn.ua>
X-Attribution: zeus
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN
cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F
eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N
ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw
15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5
lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG
ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq
zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe
riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M
1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a
mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs
SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6
7tXQAAAAASUVORK5CYII=
X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha1; protocol="application/pgp-signature"
X-NewUkraine-Agent: mailfromd (7.99.92)
X-NewUkraine-URL: http://www.ibs.dn.ua/smtp.html
X-NewUkraine-VirStat: NO
X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures,
ScanHTML, ScanPDF
X-NewUkraine-SpamStat: NO
X-NewUkraine-SpamScore: -1.600 of 3.500
X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS
Cc: "freebsd-fs@FreeBSD.org" <freebsd-fs@FreeBSD.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 06:51:31 -0000
--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Karli Sj=C3=B6berg <Karli.Sjoberg@slu.se> wrote:
> On Tue, 2014-11-04 at 07:29 +0200, Zeus Panchenko wrote:
> To have ZFS filesystems mounted at boot, first of all, "canmount" must
> be on (check) and then you have need to have:
thanks, yes it is (and it is mentioned in `zfs get all' output in my
initial post)
> zfs_enable=3D"YES"
> in "rc.conf". Then there=C2=B4s also the question how the parent filesyst=
ems
> "/home/zeus" and "/home" are mounted? Are they also ZFS?
my case is root-on-zfs, one pool and no other fs except ZFS
all other fs (ZFS) are mounted correctly
=2D-=20
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
--=-=-=
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlRYd2cACgkQr3jpPg/3oypKXQCg7NgekXt4erT9iD4WfT5xnmrm
FcMAnRzBMLv1H+5dJgKeS4hm2u89XMu8
=RAkG
-----END PGP SIGNATURE-----
--=-=-=--
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 07:01:40 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 E7B62C5
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 07:01:40 +0000 (UTC)
Received: from mail.slu.se (tmgext2-2.slu.se [77.235.224.52])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 77CEDBC9
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 07:01:39 +0000 (UTC)
Received: from Exchange2-2.slu.se (130.238.96.155) by Tmg2-2.slu.se
(130.238.96.152) with Microsoft SMTP Server (TLS) id 14.3.210.2; Tue, 4 Nov
2014 08:00:25 +0100
Received: from Exchange2-1.slu.se ([130.238.96.154]) by exchange2-2
([130.238.96.155]) with mapi id 14.03.0210.002; Tue, 4 Nov 2014 08:00:24
+0100
From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= <Karli.Sjoberg@slu.se>
To: "zeus@ibs.dn.ua" <zeus@ibs.dn.ua>
Subject: Re: why no automount for one zfs?
Thread-Topic: why no automount for one zfs?
Thread-Index: AQHP9/0BI64rLjUBoEqQLg97D+mvgA==
Date: Tue, 4 Nov 2014 07:00:24 +0000
Message-ID: <5F9E965F5A80BC468BE5F40576769F099DF85D61@exchange2-1>
References: <20141104072923.79140@smtp.new-ukraine.org>
<5F9E965F5A80BC468BE5F40576769F099DF85BC1@exchange2-1>
<20141104085120.81576@smtp.new-ukraine.org>
In-Reply-To: <20141104085120.81576@smtp.new-ukraine.org>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [77.235.228.32]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "freebsd-fs@FreeBSD.org" <freebsd-fs@FreeBSD.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 07:01:41 -0000
T24gVHVlLCAyMDE0LTExLTA0IGF0IDA4OjUxICswMjAwLCBaZXVzIFBhbmNoZW5rbyB3cm90ZToK
PiBLYXJsaSBTasO2YmVyZyA8S2FybGkuU2pvYmVyZ0BzbHUuc2U+IHdyb3RlOgo+IAo+ID4gT24g
VHVlLCAyMDE0LTExLTA0IGF0IDA3OjI5ICswMjAwLCBaZXVzIFBhbmNoZW5rbyB3cm90ZToKPiA+
IFRvIGhhdmUgWkZTIGZpbGVzeXN0ZW1zIG1vdW50ZWQgYXQgYm9vdCwgZmlyc3Qgb2YgYWxsLCAi
Y2FubW91bnQiIG11c3QKPiA+IGJlIG9uIChjaGVjaykgYW5kIHRoZW4geW91IGhhdmUgbmVlZCB0
byBoYXZlOgo+IAo+IHRoYW5rcywgeWVzIGl0IGlzIChhbmQgaXQgaXMgbWVudGlvbmVkIGluIGB6
ZnMgZ2V0IGFsbCcgb3V0cHV0IGluIG15Cj4gaW5pdGlhbCBwb3N0KQoKSW5kZWVkLCBoZW5jZSB0
aGV5IHByZXZpb3VzICJjaGVjayIgY29tbWVudCBvbiBteSBwYXJ0OikKCj4gCj4gPiB6ZnNfZW5h
YmxlPSJZRVMiCj4gPiBpbiAicmMuY29uZiIuIFRoZW4gdGhlcmXCtHMgYWxzbyB0aGUgcXVlc3Rp
b24gaG93IHRoZSBwYXJlbnQgZmlsZXN5c3RlbXMKPiA+ICIvaG9tZS96ZXVzIiBhbmQgIi9ob21l
IiBhcmUgbW91bnRlZD8gQXJlIHRoZXkgYWxzbyBaRlM/Cj4gCj4gbXkgY2FzZSBpcyByb290LW9u
LXpmcywgb25lIHBvb2wgYW5kIG5vIG90aGVyIGZzIGV4Y2VwdCBaRlMKPiAKPiBhbGwgb3RoZXIg
ZnMgKFpGUykgYXJlIG1vdW50ZWQgY29ycmVjdGx5Cj4gCgpBbmQsIGp1c3QgdG8gYmUgc3VyZSwg
dGhleSBhcmUgYWxsIG1vdW50ZWQgYXV0b21hdGljYWxseSB0aGUgc2FtZSB3YXk/Ckxpa2UgaWYg
eW91IG1heWJlIGhhdmUgc29tZSBmaWxlc3lzdGVtcyBtb3VudGVkIGF1dG9tYXRpY2FsbHkgYW5k
IHNvbWUKdGhyb3VnaCBmc3RhYiBhcyAiY2FubW91bnQ9bm9hdXRvIiwgb3Igc3R1ZmYgbGlrZSB0
aGF0PwoKCi0tIAoKTWVkIFbDpG5saWdhIEjDpGxzbmluZ2FyCgotLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tCkthcmxpIFNqw7ZiZXJnClN3ZWRpc2ggVW5pdmVyc2l0eSBvZiBBZ3JpY3VsdHVyYWwgU2Np
ZW5jZXMgQm94IDcwNzkgKFZpc2l0aW5nIEFkZHJlc3MKS3JvbsOlc3bDpGdlbiA4KQpTLTc1MCAw
NyBVcHBzYWxhLCBTd2VkZW4KUGhvbmU6ICArNDYtKDApMTgtNjcgMTUgNjYKa2FybGkuc2pvYmVy
Z0BzbHUuc2UK
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 07:52:25 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 8FC7CEAB
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 07:52:25 +0000 (UTC)
Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "smtp.new-ukraine.org",
Issuer "smtp.new-ukraine.org" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 1102FFE1
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 07:52:23 +0000 (UTC)
Received: on behalf of honored client by smtp.new-ukraine.org with ESMTP id
sA47qJEV085360 on Tue, 4 Nov 2014 09:52:19 +0200 (EET)
Message-ID: <20141104095214.85358@smtp.new-ukraine.org>
Date: Tue, 04 Nov 2014 09:52:14 +0200
From: "Zeus Panchenko" <zeus@ibs.dn.ua>
To: "=?us-ascii?Q?=3D=3Futf-8=3FB=3FS2FybGkgU2rDtmJlcmc=3D=3F=3D?="
<Karli.Sjoberg@slu.se>
Subject: Re: why no automount for one zfs?
In-reply-to: Your message of Tue, 4 Nov 2014 07:00:24 +0000
<5F9E965F5A80BC468BE5F40576769F099DF85D61@exchange2-1>
References: <20141104072923.79140@smtp.new-ukraine.org>
<5F9E965F5A80BC468BE5F40576769F099DF85BC1@exchange2-1>
<20141104085120.81576@smtp.new-ukraine.org>
<5F9E965F5A80BC468BE5F40576769F099DF85D61@exchange2-1>
Organization: I.B.S. LLC
Reply-To: "Zeus Panchenko" <zeus@ibs.dn.ua>
X-Attribution: zeus
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN
cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F
eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N
ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw
15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5
lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG
ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq
zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe
riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M
1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a
mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs
SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6
7tXQAAAAASUVORK5CYII=
X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-NewUkraine-Agent: mailfromd (7.99.92)
X-NewUkraine-URL: http://www.ibs.dn.ua/smtp.html
X-NewUkraine-VirStat: NO
X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures,
ScanHTML, ScanPDF
X-NewUkraine-SpamStat: NO
X-NewUkraine-SpamScore: -1.600 of 3.500
X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS
Cc: "freebsd-fs@FreeBSD.org" <freebsd-fs@FreeBSD.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 07:52:25 -0000
Karli Sj=C3=B6berg <Karli.Sjoberg@slu.se> wrote:
> And, just to be sure, they are all mounted automatically the same way?
> Like if you maybe have some filesystems mounted automatically and some
> through fstab as "canmount=3Dnoauto", or stuff like that?
yes, all my fs-es are automatically mounted except this one ...
it is nothing in my /etc/fstab except swap
may it relate to the mountpoint? it is the "second level", not the root
but dir inside other fs
--=20
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 08:10:02 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 51E8F360
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 08:10:02 +0000 (UTC)
Received: from mail.slu.se (tmgext2-3.slu.se [77.235.224.53])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id ADC6C1D0
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 08:10:00 +0000 (UTC)
Received: from Exchange2-3.slu.se (130.238.96.156) by Tmg2-3.slu.se
(130.238.96.153) with Microsoft SMTP Server (TLS) id 14.3.210.2; Tue, 4 Nov
2014 09:08:47 +0100
Received: from Exchange2-1.slu.se ([130.238.96.154]) by exchange2-3
([130.238.96.156]) with mapi id 14.03.0210.002; Tue, 4 Nov 2014 09:08:47
+0100
From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= <Karli.Sjoberg@slu.se>
To: "zeus@ibs.dn.ua" <zeus@ibs.dn.ua>
Subject: Re: why no automount for one zfs?
Thread-Topic: why no automount for one zfs?
Thread-Index: AQHP+AaOA1C+h4sjmU2f9qm+vz3+wg==
Date: Tue, 4 Nov 2014 08:08:46 +0000
Message-ID: <5F9E965F5A80BC468BE5F40576769F099DF85FB1@exchange2-1>
References: <20141104072923.79140@smtp.new-ukraine.org>
<5F9E965F5A80BC468BE5F40576769F099DF85BC1@exchange2-1>
<20141104085120.81576@smtp.new-ukraine.org>
<5F9E965F5A80BC468BE5F40576769F099DF85D61@exchange2-1>
<20141104095214.85358@smtp.new-ukraine.org>
In-Reply-To: <20141104095214.85358@smtp.new-ukraine.org>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [77.235.228.32]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "freebsd-fs@FreeBSD.org" <freebsd-fs@FreeBSD.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 08:10:02 -0000
T24gVHVlLCAyMDE0LTExLTA0IGF0IDA5OjUyICswMjAwLCBaZXVzIFBhbmNoZW5rbyB3cm90ZToK
PiBLYXJsaSBTasO2YmVyZyA8S2FybGkuU2pvYmVyZ0BzbHUuc2U+IHdyb3RlOgo+ID4gQW5kLCBq
dXN0IHRvIGJlIHN1cmUsIHRoZXkgYXJlIGFsbCBtb3VudGVkIGF1dG9tYXRpY2FsbHkgdGhlIHNh
bWUgd2F5Pwo+ID4gTGlrZSBpZiB5b3UgbWF5YmUgaGF2ZSBzb21lIGZpbGVzeXN0ZW1zIG1vdW50
ZWQgYXV0b21hdGljYWxseSBhbmQgc29tZQo+ID4gdGhyb3VnaCBmc3RhYiBhcyAiY2FubW91bnQ9
bm9hdXRvIiwgb3Igc3R1ZmYgbGlrZSB0aGF0Pwo+IAo+IHllcywgYWxsIG15IGZzLWVzIGFyZSBh
dXRvbWF0aWNhbGx5IG1vdW50ZWQgZXhjZXB0IHRoaXMgb25lIC4uLgo+IGl0IGlzIG5vdGhpbmcg
aW4gbXkgL2V0Yy9mc3RhYiBleGNlcHQgc3dhcAo+IAo+IG1heSBpdCByZWxhdGUgdG8gdGhlIG1v
dW50cG9pbnQ/IGl0IGlzIHRoZSAic2Vjb25kIGxldmVsIiwgbm90IHRoZSByb290Cj4gYnV0IGRp
ciBpbnNpZGUgb3RoZXIgZnMKPiAKPiAtLSAKPiBaZXVzIFYuIFBhbmNoZW5rbwkJCQlqaWQ6emV1
c0BpbS5pYnMuZG4udWEKPiBJVCBEcHQuLCBJLkIuUy4gTExDCQkJCQkgIEdNVCsyIChFRVQpCgpO
byBpZGVhLCBvdXIgc3RvcmFnZSBzZXJ2ZXJzIGhhdmUgZmlsZXN5c3RlbXMgdGhhdCBhcmUgImRl
ZXBlciIgdGhhbgp0aGF0IGJ1dCB3ZSBzZXQgImNhbm1vdW50PW5vYXV0byIgYW5kIG1vdW50IHRo
cm91Z2ggZnN0YWIsIHNvIEkgZG9uwrR0Cmtub3cuIEhhdmUgc2VlbiBmb2xrIHJ1biBqYWlscyB0
aGF0IHN0cmV0Y2ggZmFyICJkZWVwZXIiIHRoYW4gd2hhdCB5b3UKaGF2ZSBpc3N1ZXMgc28gc2hv
dWxkbsK0dCBiZSBhIHByb2JsZW0uCgpJIHdhcyBtb3JlIG1ha2luZyBzdXJlIGV2ZXJ5dGhpbmcg
d2FzIGFzIGl0IHNob3VsZCBmb3IgYXV0byBtb3VudGluZyBaRlMKdG8gd29yayBjb3JyZWN0bHks
IHdoaWNoIHNlZW1zIHRvIGJlIHRoZSBjYXNlLgoKTWF5YmUgeW91IHNob3VsZCBhY3RpdmF0ZSB2
ZXJib3NlIGxvZ2dpbmcgZHVyaW5nIGJvb3QgdG8gYmUgYWJsZSB0byBzZWUKbW9yZSBjbGVhcmx5
IHdoYXQgKGFuZCB3aGF0IGRvZXNuwrR0KSBoYXBwZW4ocyk/CgpodHRwOi8vbGlzdHMuZnJlZWJz
ZC5vcmcvcGlwZXJtYWlsL2ZyZWVic2QtcXVlc3Rpb25zLzIwMDQtQXVndXN0LzA1NDk4MS5odG1s
CgoKCi0tIAoKTWVkIFbDpG5saWdhIEjDpGxzbmluZ2FyCgotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
CkthcmxpIFNqw7ZiZXJnClN3ZWRpc2ggVW5pdmVyc2l0eSBvZiBBZ3JpY3VsdHVyYWwgU2NpZW5j
ZXMgQm94IDcwNzkgKFZpc2l0aW5nIEFkZHJlc3MKS3JvbsOlc3bDpGdlbiA4KQpTLTc1MCAwNyBV
cHBzYWxhLCBTd2VkZW4KUGhvbmU6ICArNDYtKDApMTgtNjcgMTUgNjYKa2FybGkuc2pvYmVyZ0Bz
bHUuc2UK
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 08:23:20 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 2672B6B4
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 08:23:20 +0000 (UTC)
Received: from squishy.elizium.za.net (squishy.elizium.za.net [80.68.90.178])
by mx1.freebsd.org (Postfix) with ESMTP id E4A1D382
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 08:23:19 +0000 (UTC)
Received: from sludge.elizium.za.net (sludge.elizium.za.net [196.41.137.247])
by squishy.elizium.za.net (Postfix) with ESMTPSA id 85262300E2;
Tue, 4 Nov 2014 10:14:49 +0200 (SAST)
Date: Tue, 4 Nov 2014 10:19:24 +0200
From: Hugo Lombard <hal@elizium.za.net>
To: Zeus Panchenko <zeus@ibs.dn.ua>
Subject: Re: why no automount for one zfs?
Message-ID: <20141104081924.GY9223@sludge.elizium.za.net>
References: <20141104072923.79140@smtp.new-ukraine.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20141104072923.79140@smtp.new-ukraine.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: freebsd-fs@FreeBSD.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 08:23:20 -0000
On Tue, Nov 04, 2014 at 07:29:23AM +0200, Zeus Panchenko wrote:
>
> after reboot this very fs is listed as mounted but the mount directory
> for it, is empty ... after umount/mount everything appears on it's
> expected place ...
>
Could you perhaps show the output of "mount" before and after?
--
Hugo Lombard
.___.
(o,o)
/) )
---"-"---
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 09:09:44 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 2FDBF4E1
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 09:09:44 +0000 (UTC)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id B98E6D1A
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 09:09:43 +0000 (UTC)
Received: by mail-wg0-f46.google.com with SMTP id x13so13029760wgg.33
for <freebsd-fs@freebsd.org>; Tue, 04 Nov 2014 01:09:41 -0800 (PST)
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=eVAtRFp9FGDKZXqoOMbVXc8E6fVAjx6cAmWa8Y3Am3s=;
b=MUvPC/08juiNKj3nDpblaNmL2U/cFdmebNCsHjEJpd+fvMJKGRq7mHUcan7eZnpMvb
mCA8QDvkvVC0l0PfRX4POtxSXzP8pgcnKQkg0vYBM2RTXFDJpktIiam0e+cp/z0bS8cf
KO7NMNOUxl2NcKnGLjQY4lc+Vv9Aq3Ik2KUk0LswW4VnSbaGcIyHVGqi+iAe4BxuM85Z
doXkYFCswkbbUAEkOGZYv7uLIAWBJp7ygcgZOBK//+jN++/kfP6KQ34KwooHy9HMPQC7
sQceU9l7mxPqaR1zV2ahC7dsN3b7nHKarLdZ+L+/WJJ9NxmrpbUMT8cwblF6tb2b4xha
fyYg==
X-Gm-Message-State: ALoCoQkqDjG1XpIJ1MweG3CGvPW+lVtJvxbKMhQvYLGa6vDbIvMJh245cE/yDCzURc+fUUT+I/+A
X-Received: by 10.180.19.234 with SMTP id i10mr23048949wie.28.1415092181363;
Tue, 04 Nov 2014 01:09:41 -0800 (PST)
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 ci9sm288203wid.24.2014.11.04.01.09.40
for <freebsd-fs@freebsd.org>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Tue, 04 Nov 2014 01:09:40 -0800 (PST)
Message-ID: <54589780.7020303@multiplay.co.uk>
Date: Tue, 04 Nov 2014 09:08:16 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: freebsd-fs@freebsd.org
Subject: Re: why no automount for one zfs?
References: <20141104072923.79140@smtp.new-ukraine.org>
In-Reply-To: <20141104072923.79140@smtp.new-ukraine.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 09:09:44 -0000
Missing zfs_enable="YES" in /etc/rc.conf?
On 04/11/2014 05:29, Zeus Panchenko wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> hi all,
>
> some times after installation I decided to dedicate separate ZFS with
> mountpoint in my homedir for storage needs
>
> but each reboot I have to mount it by hands with:
>
> zfs unmount zroot_z-hp/storage && zfs mount zroot_z-hp/storage
>
> after reboot this very fs is listed as mounted but the mount directory
> for it, is empty ... after umount/mount everything appears on it's
> expected place ...
>
> please help me to understand why it does not automount after reboot?
>
>> uname -a
> FreeBSD 10.0-STABLE #0 r261303 amd64
>
> partial output of
>> zfs get all zroot_z-hp/storage
> NAME PROPERTY VALUE SOURCE
> zroot_z-hp/storage type filesystem -
> zroot_z-hp/storage mounted yes -
> zroot_z-hp/storage mountpoint /home/zeus/storage local
> zroot_z-hp/storage sharenfs off default
> zroot_z-hp/storage checksum fletcher4 inherited from zroot_z-hp
> zroot_z-hp/storage compression off default
> zroot_z-hp/storage atime off inherited from zroot_z-hp
> zroot_z-hp/storage devices on default
> zroot_z-hp/storage exec on default
> zroot_z-hp/storage setuid on default
> zroot_z-hp/storage readonly off default
> zroot_z-hp/storage jailed off default
> zroot_z-hp/storage snapdir hidden default
> zroot_z-hp/storage aclmode discard default
> zroot_z-hp/storage aclinherit restricted default
> zroot_z-hp/storage canmount on default
> zroot_z-hp/storage xattr off temporary
> zroot_z-hp/storage copies 1 default
> zroot_z-hp/storage version 5 -
>
> - --
> Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
> IT Dpt., I.B.S. LLC GMT+2 (EET)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iEYEARECAAYFAlRYZDMACgkQr3jpPg/3oyozlACgrQfGK/7Ch9CQMRqJ0T4/+/Qr
> kkMAoKNYOTZdlxdQPxUe8Y9hfg7XJg0v
> =S86e
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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 Tue Nov 4 09:17:16 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 918E573F
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 09:17:16 +0000 (UTC)
Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "smtp.new-ukraine.org",
Issuer "smtp.new-ukraine.org" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 1B78DDF1
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 09:17:15 +0000 (UTC)
Received: on behalf of honored client by smtp.new-ukraine.org with ESMTP id
sA49H9x1091941 on Tue, 4 Nov 2014 11:17:10 +0200 (EET)
Message-ID: <20141104111704.91939@smtp.new-ukraine.org>
Date: Tue, 04 Nov 2014 11:17:04 +0200
From: "Zeus Panchenko" <zeus@ibs.dn.ua>
To: "Steven Hartland" <killing@multiplay.co.uk>
Subject: Re: why no automount for one zfs?
In-reply-to: Your message of Tue,
04 Nov 2014 09:08:16 +0000 <54589780.7020303@multiplay.co.uk>
References: <20141104072923.79140@smtp.new-ukraine.org>
<54589780.7020303@multiplay.co.uk>
Organization: I.B.S. LLC
Reply-To: "Zeus Panchenko" <zeus@ibs.dn.ua>
X-Attribution: zeus
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN
cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F
eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N
ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw
15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5
lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG
ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq
zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe
riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M
1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a
mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs
SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6
7tXQAAAAASUVORK5CYII=
X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1
X-NewUkraine-Agent: mailfromd (7.99.92)
X-NewUkraine-URL: http://www.ibs.dn.ua/smtp.html
X-NewUkraine-VirStat: NO
X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures,
ScanHTML, ScanPDF
X-NewUkraine-SpamStat: NO
X-NewUkraine-SpamScore: -1.600 of 3.500
X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 09:17:16 -0000
Steven Hartland <killing@multiplay.co.uk> wrote:
> Missing zfs_enable="YES" in /etc/rc.conf?
no, it is on it's place (I run root-on-zfs)
--
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 09:31:54 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 98240CB8
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 09:31:54 +0000 (UTC)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com
[209.85.212.178])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 2BCB5FB6
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 09:31:53 +0000 (UTC)
Received: by mail-wi0-f178.google.com with SMTP id q5so8695543wiv.5
for <freebsd-fs@freebsd.org>; Tue, 04 Nov 2014 01:31:51 -0800 (PST)
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
:cc:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=GZjl112RVidZ4cqYoigkvEFuVGQf9EpJZXOAmHacs5M=;
b=Wa89bqlQb/zWDau9UNO2WLwASpQFKHuWc1bwuf2PEmEc4j8lfUwtWHAMW/HgVSYkug
x5P/kaFiM8wWZJLk6Y1nIVn3qP5qOHf0ZaslLAdBilSbpqOgGIYvaHAZK1hL1J7FoZ4R
urc9MSTt04UE4Pv/sQUmHSozBuPjIeoAjwGfW4olFmB53snPBZd7anR2ScaWouJ9rYP8
EWloHlUpQ+bnxeHSf9EiXSK1S9Dm49mnigyJDk/OnRw8yDdS4r7Z8rld6oHJIe//4t9/
mt1Na4vNgb6V+qwEdPrR9HSDv1PhAMTECOG2bX/bMFI8j+DgNvPILr+0tY+Og7PemJP6
Th8g==
X-Gm-Message-State: ALoCoQl6gnY9QCuV1qGaH0zKx4Q/5N5bdRtpgZeHVc7EA63g6fK4ubyXwL2GHJB2sMsDiKpnWmpt
X-Received: by 10.180.36.205 with SMTP id s13mr22003984wij.11.1415093511559;
Tue, 04 Nov 2014 01:31:51 -0800 (PST)
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 j8sm11602328wib.10.2014.11.04.01.31.50
for <multiple recipients>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Tue, 04 Nov 2014 01:31:50 -0800 (PST)
Message-ID: <54589CB2.5090105@multiplay.co.uk>
Date: Tue, 04 Nov 2014 09:30:26 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Zeus Panchenko <zeus@ibs.dn.ua>
Subject: Re: why no automount for one zfs?
References: <20141104072923.79140@smtp.new-ukraine.org>
<54589780.7020303@multiplay.co.uk>
<20141104111704.91939@smtp.new-ukraine.org>
In-Reply-To: <20141104111704.91939@smtp.new-ukraine.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 09:31:54 -0000
On 04/11/2014 09:17, Zeus Panchenko wrote:
> Steven Hartland <killing@multiplay.co.uk> wrote:
>> Missing zfs_enable="YES" in /etc/rc.conf?
> no, it is on it's place (I run root-on-zfs)
>
Add it, it will fix you mounting issue.
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 09:45:51 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 19FBAE2
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 09:45:51 +0000 (UTC)
Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "smtp.new-ukraine.org",
Issuer "smtp.new-ukraine.org" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 76C9E18A
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 09:45:49 +0000 (UTC)
Received: on behalf of honored client by smtp.new-ukraine.org with ESMTP id
sA49jjY4094098 on Tue, 4 Nov 2014 11:45:45 +0200 (EET)
Message-ID: <20141104114540.94096@smtp.new-ukraine.org>
Date: Tue, 04 Nov 2014 11:45:40 +0200
From: "Zeus Panchenko" <zeus@ibs.dn.ua>
To: "Steven Hartland" <killing@multiplay.co.uk>
Subject: Re: why no automount for one zfs?
In-reply-to: Your message of Tue,
04 Nov 2014 09:30:26 +0000 <54589CB2.5090105@multiplay.co.uk>
References: <20141104072923.79140@smtp.new-ukraine.org>
<54589780.7020303@multiplay.co.uk>
<20141104111704.91939@smtp.new-ukraine.org>
<54589CB2.5090105@multiplay.co.uk>
Organization: I.B.S. LLC
Reply-To: "Zeus Panchenko" <zeus@ibs.dn.ua>
X-Attribution: zeus
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN
cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F
eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N
ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw
15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5
lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG
ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq
zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe
riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M
1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a
mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs
SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6
7tXQAAAAASUVORK5CYII=
X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha1; protocol="application/pgp-signature"
X-NewUkraine-Agent: mailfromd (7.99.92)
X-NewUkraine-URL: http://www.ibs.dn.ua/smtp.html
X-NewUkraine-VirStat: NO
X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures,
ScanHTML, ScanPDF
X-NewUkraine-SpamStat: NO
X-NewUkraine-SpamScore: -1.600 of 3.500
X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 09:45:51 -0000
--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Steven Hartland <killing@multiplay.co.uk> wrote:
> On 04/11/2014 09:17, Zeus Panchenko wrote:
> > Steven Hartland <killing@multiplay.co.uk> wrote:
> >> Missing zfs_enable=3D"YES" in /etc/rc.conf?
> > no, it is on it's place (I run root-on-zfs)
> >
> Add it,
the option *is* in /etc/rc.conf, otherwise I couldn't boot since I run
root-on-zfs
> cat /etc/rc.conf
=2D--[ quotation start ]-------------------------------------------
#-*- conf -*-
#
zfs_enable=3D"YES"
...
=2D--[ quotation end ]-------------------------------------------
> it will fix you mounting issue.
the problem exists only for this single fs, all other fs are automounted
correctly
=2D-=20
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
--=-=-=
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlRYoEMACgkQr3jpPg/3oyrpCwCfYMcNcIB4v+4UwmGPF1tnswvP
kOcAoPqole8v1UKnwSMT0frQkuwRTRJI
=n/c9
-----END PGP SIGNATURE-----
--=-=-=--
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 10:15:59 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 A506EAA6
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 10:15:59 +0000 (UTC)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com
[209.85.212.179])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 39B606E6
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 10:15:58 +0000 (UTC)
Received: by mail-wi0-f179.google.com with SMTP id h11so8787255wiw.12
for <freebsd-fs@freebsd.org>; Tue, 04 Nov 2014 02:15:49 -0800 (PST)
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
:cc:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=OPaVR3/q8nHX5YatCKjWahibgQH3BGUtafjrQ1Stxy4=;
b=AL06d1mtWSTi6PDEreT0mIyjXS6gkXihzqmAigP9w904WbN4D7kHdKZjl83rwQSFCD
otYrLIxpmqJo4kInd0JgTy1XtHtDJDrUVoUE/kAGmzAKlk0rubu1P50GzYoXuCb27ZLI
KYUr+uDvufeIQWzQTXNyFNBDaDTxOlA0eR0Yy0h1683AvBa33z8GGpvdLxnUqNm3NGZA
3KgYVyP+wKaCxHedllaNllPCzjX2wbr5M/Ju6hzAer2ycOuaUeK9QCCYPXzco3sAG5EC
F4two3qbPBSDjUgYkwRsYoRcumyNJo9xqPoBXk05FF3ROYMjzSLl/MK5/1rp8jyKm9jA
aWvg==
X-Gm-Message-State: ALoCoQmTFyBj1o1o6mL+v/s7N9OizrekbXkx5Zkb5CCNGYMsbFq7G3cAeZ4SavEHi+m1GgnB2Uzl
X-Received: by 10.180.107.1 with SMTP id gy1mr22699614wib.8.1415096149798;
Tue, 04 Nov 2014 02:15:49 -0800 (PST)
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 a8sm446556wiz.21.2014.11.04.02.15.48
for <multiple recipients>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Tue, 04 Nov 2014 02:15:49 -0800 (PST)
Message-ID: <5458A700.1000700@multiplay.co.uk>
Date: Tue, 04 Nov 2014 10:14:24 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Zeus Panchenko <zeus@ibs.dn.ua>
Subject: Re: why no automount for one zfs?
References: <20141104072923.79140@smtp.new-ukraine.org>
<54589780.7020303@multiplay.co.uk>
<20141104111704.91939@smtp.new-ukraine.org>
<54589CB2.5090105@multiplay.co.uk>
<20141104114540.94096@smtp.new-ukraine.org>
In-Reply-To: <20141104114540.94096@smtp.new-ukraine.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 10:15:59 -0000
On 04/11/2014 09:45, Zeus Panchenko wrote:
> Steven Hartland <killing@multiplay.co.uk> wrote:
>
>> On 04/11/2014 09:17, Zeus Panchenko wrote:
>>> Steven Hartland <killing@multiplay.co.uk> wrote:
>>>> Missing zfs_enable="YES" in /etc/rc.conf?
>>> no, it is on it's place (I run root-on-zfs)
>>>
>> Add it,
> the option *is* in /etc/rc.conf, otherwise I couldn't boot since I run
> root-on-zfs
>
>> cat /etc/rc.conf
> ---[ quotation start ]-------------------------------------------
> #-*- conf -*-
> #
> zfs_enable="YES"
> ...
> ---[ quotation end ]-------------------------------------------
>
>
>> it will fix you mounting issue.
> the problem exists only for this single fs, all other fs are automounted
> correctly
Sorry lost in translation a bit there ;-)
So when you boot and its missing the one volume what happens when you run:
zfs mount -a
Does that mount the missing volume?
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 10:36:03 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 72573471
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 10:36:03 +0000 (UTC)
Received: from smtp-outbound.userve.net (smtp-outbound.userve.net
[217.196.1.22])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "*.userve.net",
Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id F3CA5943
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 10:36:02 +0000 (UTC)
Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2])
by smtp-outbound.userve.net (8.14.7/8.14.7) with ESMTP id sA4AQKYU011585
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Tue, 4 Nov 2014 10:26:20 GMT
(envelope-from matt.churchyard@userve.net)
Received: from SERVER.ad.usd-group.com (192.168.0.1) by
SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id
15.0.516.32; Tue, 4 Nov 2014 10:26:20 +0000
Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by
SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id
15.00.0516.029; Tue, 4 Nov 2014 10:26:20 +0000
From: Matt Churchyard <matt.churchyard@userve.net>
To: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject: RE: why no automount for one zfs?
Thread-Topic: why no automount for one zfs?
Thread-Index: AQHP9/CkHtLge5shq0aIgpTMgNTLnpxQLdsAgAACtFSAAAN9AIAABHJsgAAJfSA=
Date: Tue, 4 Nov 2014 10:26:19 +0000
Message-ID: <5449152a2e174a81ae59cb36e7a9de7c@SERVER.ad.usd-group.com>
References: <20141104072923.79140@smtp.new-ukraine.org>
<54589780.7020303@multiplay.co.uk>
<20141104111704.91939@smtp.new-ukraine.org>
<54589CB2.5090105@multiplay.co.uk>
<20141104114540.94096@smtp.new-ukraine.org>
In-Reply-To: <20141104114540.94096@smtp.new-ukraine.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.0.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 10:36:03 -0000
>Steven Hartland <killing@multiplay.co.uk> wrote:
>> On 04/11/2014 09:17, Zeus Panchenko wrote:
>> > Steven Hartland <killing@multiplay.co.uk> wrote:
>> >> Missing zfs_enable=3D"YES" in /etc/rc.conf?
>> > no, it is on it's place (I run root-on-zfs)
>> >
>> Add it,
>the option *is* in /etc/rc.conf, otherwise I couldn't boot since I run roo=
t-on-zfs
Just to be clear, the root filesystem is mounted slightly earlier in the bo=
ot process, regardless of rc.conf settings. (Obviously the root filesystem =
has to be mounted before the system can read what you've got in /etc/rc.con=
f)
However, if you don't have zfs_enable=3D"YES" in /etc/rc.conf, no *other* Z=
FS filesystems will be mounted. This is a very common problem that catches =
quite a few people out, which is why you were asked to confirm.
>> cat /etc/rc.conf
>---[ quotation start ]-------------------------------------------
>#-*- conf -*-
>#
>zfs_enable=3D"YES"
>...
>---[ quotation end ]-------------------------------------------
>> it will fix you mounting issue.
>the problem exists only for this single fs, all other fs are automounted c=
orrectly
At the moment I'd look at the possibility of another ZFS dataset getting mo=
unted over the top.
Regards,
Matt
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 14:42:10 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 58F8B480
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 14:42:10 +0000 (UTC)
Received: from mail-yh0-x22e.google.com (mail-yh0-x22e.google.com
[IPv6:2607:f8b0:4002:c01::22e])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 1194FCC8
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 14:42:10 +0000 (UTC)
Received: by mail-yh0-f46.google.com with SMTP id c41so2530916yho.5
for <freebsd-fs@freebsd.org>; Tue, 04 Nov 2014 06:42:09 -0800 (PST)
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=8ikZRST7nuPm4rJvo5qglgMHXqxfpk6Mk3ANyQ9ujrU=;
b=tokidzvOSMpoUZdTMNFc/r1vd4ZXH8lx19PWkVc4OmnUfIxsi+FJrwq8Gq/UDFkgIW
XfcQUiANXY6B6hA1u1C/QLJB59Fr83f5HwqmqLKzg/QqnlxaYzRz2trWGOtB5EJxhNUZ
XGekNNoAZFLAmNzROvhfrGl+raxCkIrfJfdsXPGvvJL9z6kbZkKZfSJ0jz/sFlwtl4Hp
1Oikqvvwwx4GXIrbpVEMFAB6XNiyT7sVhJd1kRVi8Ebog0V9UefuOILF/kmbSWu1yBFO
zOaqVQFoKIm6qSkc5sFoVyIIrg9O3z0IgudPxLqQg7pwQXL8W6t9rTLjqtyS306KVDCG
heGg==
MIME-Version: 1.0
X-Received: by 10.236.230.40 with SMTP id i38mr34954294yhq.34.1415112129281;
Tue, 04 Nov 2014 06:42:09 -0800 (PST)
Received: by 10.170.156.139 with HTTP; Tue, 4 Nov 2014 06:42:09 -0800 (PST)
In-Reply-To: <5449152a2e174a81ae59cb36e7a9de7c@SERVER.ad.usd-group.com>
References: <20141104072923.79140@smtp.new-ukraine.org>
<54589780.7020303@multiplay.co.uk>
<20141104111704.91939@smtp.new-ukraine.org>
<54589CB2.5090105@multiplay.co.uk>
<20141104114540.94096@smtp.new-ukraine.org>
<5449152a2e174a81ae59cb36e7a9de7c@SERVER.ad.usd-group.com>
Date: Tue, 4 Nov 2014 14:42:09 +0000
Message-ID: <CALfReye=KShy_xNoRTOpE2zjXfZp6qw-nFVnPYysRzrFCR8_bA@mail.gmail.com>
Subject: Re: why no automount for one zfs?
From: krad <kraduk@gmail.com>
To: Matt Churchyard <matt.churchyard@userve.net>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 14:42:10 -0000
i 2nd that, a zfs list output wouldnt go amiss either
On 4 November 2014 10:26, Matt Churchyard <matt.churchyard@userve.net>
wrote:
> >Steven Hartland <killing@multiplay.co.uk> wrote:
>
> >> On 04/11/2014 09:17, Zeus Panchenko wrote:
> >> > Steven Hartland <killing@multiplay.co.uk> wrote:
> >> >> Missing zfs_enable="YES" in /etc/rc.conf?
> >> > no, it is on it's place (I run root-on-zfs)
> >> >
> >> Add it,
>
> >the option *is* in /etc/rc.conf, otherwise I couldn't boot since I run
> root-on-zfs
>
> Just to be clear, the root filesystem is mounted slightly earlier in the
> boot process, regardless of rc.conf settings. (Obviously the root
> filesystem has to be mounted before the system can read what you've got in
> /etc/rc.conf)
>
> However, if you don't have zfs_enable="YES" in /etc/rc.conf, no *other*
> ZFS filesystems will be mounted. This is a very common problem that catches
> quite a few people out, which is why you were asked to confirm.
>
> >> cat /etc/rc.conf
> >---[ quotation start ]-------------------------------------------
> >#-*- conf -*-
> >#
> >zfs_enable="YES"
> >...
> >---[ quotation end ]-------------------------------------------
>
>
> >> it will fix you mounting issue.
>
> >the problem exists only for this single fs, all other fs are automounted
> correctly
>
> At the moment I'd look at the possibility of another ZFS dataset getting
> mounted over the top.
>
> Regards,
> Matt
> _______________________________________________
> freebsd-fs@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
>
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 22:12:40 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 5BEE342C
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 22:12:40 +0000 (UTC)
Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "smtp.new-ukraine.org",
Issuer "smtp.new-ukraine.org" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id D9460862
for <freebsd-fs@FreeBSD.org>; Tue, 4 Nov 2014 22:12:38 +0000 (UTC)
Received: on behalf of honored client by smtp.new-ukraine.org with ESMTP id
sA4MCJ1G031616 on Wed, 5 Nov 2014 00:12:25 +0200 (EET)
Message-ID: <20141105001214.31614@smtp.new-ukraine.org>
Date: Wed, 05 Nov 2014 00:12:14 -2200
From: "Zeus Panchenko" <zeus@ibs.dn.ua>
To: "Hugo Lombard" <hal@elizium.za.net>
Subject: Re: why no automount for one zfs?
In-reply-to: Your message of Tue, 4 Nov 2014 10:19:24 +0200
<20141104081924.GY9223@sludge.elizium.za.net>
References: <20141104072923.79140@smtp.new-ukraine.org>
<20141104081924.GY9223@sludge.elizium.za.net>
Organization: I.B.S. LLC
Reply-To: "Zeus Panchenko" <zeus@ibs.dn.ua>
X-Attribution: zeus
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN
cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F
eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N
ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw
15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5
lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG
ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq
zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe
riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M
1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a
mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs
SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6
7tXQAAAAASUVORK5CYII=
X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha1; protocol="application/pgp-signature"
X-NewUkraine-Agent: mailfromd (7.99.92)
X-NewUkraine-URL: http://www.ibs.dn.ua/smtp.html
X-NewUkraine-VirStat: NO
X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures,
ScanHTML, ScanPDF
X-NewUkraine-SpamStat: NO
X-NewUkraine-SpamScore: -1.000 of 3.500
X-NewUkraine-SpamKeys: AWL, BAYES_00, BUG6152_INVALID_DATE_TZ_ABSURD,
INVALID_DATE_TZ_ABSURD, NO_RECEIVED, NO_RELAYS
Cc: freebsd-fs@FreeBSD.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 22:12:40 -0000
--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Hugo Lombard <hal@elizium.za.net> wrote:
> On Tue, Nov 04, 2014 at 07:29:23AM +0200, Zeus Panchenko wrote:
> >=20
> > after reboot this very fs is listed as mounted but the mount directory
> > for it, is empty ... after umount/mount everything appears on it's
> > expected place ...
> >=20
>=20
> Could you perhaps show the output of "mount" before and after?
>=20
here it is
1. before umount/mount
1.1. zfs list
NAME USED AVAIL REFER MOUNTPOINT
zroot_z-hp 27.9G 81.4G 144K none
zroot_z-hp/ROOT 8.42G 81.4G 144K none
zroot_z-hp/ROOT/default 8.42G 81.4G 8.42G /
zroot_z-hp/storage 8.52G 81.4G 8.52G /home/zeus/storage
zroot_z-hp/tmp 291M 81.4G 291M /tmp
zroot_z-hp/usr 9.35G 81.4G 144K /usr
zroot_z-hp/usr/home 5.27G 81.4G 2.43G /usr/home
zroot_z-hp/usr/ports 3.00G 81.4G 1.80G /usr/ports
zroot_z-hp/usr/src 1.08G 81.4G 1.08G /usr/src
zroot_z-hp/var 1.15G 81.4G 1017M /var
zroot_z-hp/var/crash 148K 81.4G 148K /var/crash
zroot_z-hp/var/log 5.99M 81.4G 5.99M /var/log
zroot_z-hp/var/tmp 153M 81.4G 153M /var/tmp
zroot_z-hp/ROOT/default on / (zfs, local, noatime, nfsv4acls)
1.2. df -h
devfs on /dev (devfs, local, multilabel)
zroot_z-hp/storage on /usr/home/zeus/storage (zfs, local, noatime, nfsv4acl=
s)
zroot_z-hp/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
zroot_z-hp/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)
zroot_z-hp/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls)
zroot_z-hp/usr/src on /usr/src (zfs, local, noatime, noexec, nosuid, nfsv4a=
cls)
zroot_z-hp/var on /var (zfs, local, noatime, nfsv4acls)
zroot_z-hp/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nf=
sv4acls)
zroot_z-hp/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4a=
cls)
zroot_z-hp/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
1.3. ls -al /home/zeus/storage
total 41
drwxr-xr-x 2 root staff 2 Jul 20 21:37 .
drwxr-xr-x 48 zeus staff 118 Nov 4 21:02 ..
2. after umount/mount
2.1. zfs list
NAME USED AVAIL REFER MOUNTPOINT
zroot_z-hp 27.9G 81.4G 144K none
zroot_z-hp/ROOT 8.42G 81.4G 144K none
zroot_z-hp/ROOT/default 8.42G 81.4G 8.42G /
zroot_z-hp/storage 8.52G 81.4G 8.52G /home/zeus/storage
zroot_z-hp/tmp 291M 81.4G 291M /tmp
zroot_z-hp/usr 9.35G 81.4G 144K /usr
zroot_z-hp/usr/home 5.27G 81.4G 2.43G /usr/home
zroot_z-hp/usr/ports 3.00G 81.4G 1.80G /usr/ports
zroot_z-hp/usr/src 1.08G 81.4G 1.08G /usr/src
zroot_z-hp/var 1.15G 81.4G 1017M /var
zroot_z-hp/var/crash 148K 81.4G 148K /var/crash
zroot_z-hp/var/log 5.99M 81.4G 5.99M /var/log
zroot_z-hp/var/tmp 153M 81.4G 153M /var/tmp
zroot_z-hp/ROOT/default on / (zfs, local, noatime, nfsv4acls)
2.2. df -h
devfs on /dev (devfs, local, multilabel)
zroot_z-hp/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
zroot_z-hp/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)
zroot_z-hp/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls)
zroot_z-hp/usr/src on /usr/src (zfs, local, noatime, noexec, nosuid, nfsv4a=
cls)
zroot_z-hp/var on /var (zfs, local, noatime, nfsv4acls)
zroot_z-hp/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nf=
sv4acls)
zroot_z-hp/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4a=
cls)
zroot_z-hp/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
zroot_z-hp/storage on /usr/home/zeus/storage (zfs, local, noatime, nfsv4acl=
s)
=2D-=20
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
--=-=-=
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlRZTz4ACgkQr3jpPg/3oyoAiQCgkO/6PuBXmVOETlCqUXYc+It5
rWoAoIhqw+Lk/VPQ/5OwbHJuMMAYgIAb
=IDrV
-----END PGP SIGNATURE-----
--=-=-=--
From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 23:32:22 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 86D4E689
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 23:32:22 +0000 (UTC)
Received: from mail-lb0-f179.google.com (mail-lb0-f179.google.com
[209.85.217.179])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id C86A61CD
for <freebsd-fs@freebsd.org>; Tue, 4 Nov 2014 23:32:21 +0000 (UTC)
Received: by mail-lb0-f179.google.com with SMTP id l4so5359909lbv.10
for <freebsd-fs@freebsd.org>; Tue, 04 Nov 2014 15:32:18 -0800 (PST)
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:from:date
:message-id:subject:to:cc:content-type;
bh=yB9qMFi59CDFfu8yP4IA8dL4YwP6lwwWaHI5pe8TcQE=;
b=fsHi23zx5mQscMvgdEkNS+/0O8Z7JLY6ntd0B+2b3jP50UVvEaxl518IK3MZL0rPmI
mjt4uaNfCdRsIlje/jsmdxyUBls3OH/IS60jEoz0IvS//ZEtW6HA+Ol+6LrXh/oIufK0
46ZhrJgX4sSre7OjalfbhCyfSZIgB1dDWrG++CJwtDcV+QeIWI3QfNUtYGJ9FaHDA8Qs
hNZmQz2WEKXzHbYGNTtshrOilDqp0qypuylJT9tZFBr8kkxTWcvPkkevRd0Gf+PUrsEV
kdkMWJIBo57fwFPfdtVDa7HAUrRNn78Lfq/X4FT1dh8MIlp8Sf7+V53Vz2/PoZeJZrcC
ErFQ==
X-Gm-Message-State: ALoCoQmJUbTylYKov52Dnvn+yTyCNKj74popVypdDs6gJOdN5OlcrhC3kZPSgdZgywokLe5v9c2J
X-Received: by 10.152.5.129 with SMTP id s1mr64193751las.59.1415143938804;
Tue, 04 Nov 2014 15:32:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.9.214 with HTTP; Tue, 4 Nov 2014 15:31:48 -0800 (PST)
In-Reply-To: <20141105001214.31614@smtp.new-ukraine.org>
References: <20141104072923.79140@smtp.new-ukraine.org>
<20141104081924.GY9223@sludge.elizium.za.net>
<20141105001214.31614@smtp.new-ukraine.org>
From: Steven Hartland <killing@multiplay.co.uk>
Date: Tue, 4 Nov 2014 23:31:48 +0000
Message-ID: <CAHEMsqZ-MYp_oNL4E=_PifdXo9O=RdYrhU5RL4bpc_=L0rUCmQ@mail.gmail.com>
Subject: Re: why no automount for one zfs?
To: Zeus Panchenko <zeus@ibs.dn.ua>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 23:32:22 -0000
So it is mounting it, its just being shadowed by the usr mount point as
/home is typically a symlink to /usr/home.
Change your mount point to /usr/home/zeus/storage from /home/zeus/storage
and you should be good.
On 5 November 2014 22:12, Zeus Panchenko <zeus@ibs.dn.ua> wrote:
> Hugo Lombard <hal@elizium.za.net> wrote:
>
> > On Tue, Nov 04, 2014 at 07:29:23AM +0200, Zeus Panchenko wrote:
> > >
> > > after reboot this very fs is listed as mounted but the mount directory
> > > for it, is empty ... after umount/mount everything appears on it's
> > > expected place ...
> > >
> >
> > Could you perhaps show the output of "mount" before and after?
> >
>
> here it is
>
> 1. before umount/mount
> 1.1. zfs list
> NAME USED AVAIL REFER MOUNTPOINT
> zroot_z-hp 27.9G 81.4G 144K none
> zroot_z-hp/ROOT 8.42G 81.4G 144K none
> zroot_z-hp/ROOT/default 8.42G 81.4G 8.42G /
> zroot_z-hp/storage 8.52G 81.4G 8.52G /home/zeus/storage
> zroot_z-hp/tmp 291M 81.4G 291M /tmp
> zroot_z-hp/usr 9.35G 81.4G 144K /usr
> zroot_z-hp/usr/home 5.27G 81.4G 2.43G /usr/home
> zroot_z-hp/usr/ports 3.00G 81.4G 1.80G /usr/ports
> zroot_z-hp/usr/src 1.08G 81.4G 1.08G /usr/src
> zroot_z-hp/var 1.15G 81.4G 1017M /var
> zroot_z-hp/var/crash 148K 81.4G 148K /var/crash
> zroot_z-hp/var/log 5.99M 81.4G 5.99M /var/log
> zroot_z-hp/var/tmp 153M 81.4G 153M /var/tmp
> zroot_z-hp/ROOT/default on / (zfs, local, noatime, nfsv4acls)
>
> 1.2. df -h
> devfs on /dev (devfs, local, multilabel)
> zroot_z-hp/storage on /usr/home/zeus/storage (zfs, local, noatime,
> nfsv4acls)
> zroot_z-hp/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
> zroot_z-hp/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)
> zroot_z-hp/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls)
> zroot_z-hp/usr/src on /usr/src (zfs, local, noatime, noexec, nosuid,
> nfsv4acls)
> zroot_z-hp/var on /var (zfs, local, noatime, nfsv4acls)
> zroot_z-hp/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid,
> nfsv4acls)
> zroot_z-hp/var/log on /var/log (zfs, local, noatime, noexec, nosuid,
> nfsv4acls)
> zroot_z-hp/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
>
> 1.3. ls -al /home/zeus/storage
> total 41
> drwxr-xr-x 2 root staff 2 Jul 20 21:37 .
> drwxr-xr-x 48 zeus staff 118 Nov 4 21:02 ..
>
> 2. after umount/mount
> 2.1. zfs list
> NAME USED AVAIL REFER MOUNTPOINT
> zroot_z-hp 27.9G 81.4G 144K none
> zroot_z-hp/ROOT 8.42G 81.4G 144K none
> zroot_z-hp/ROOT/default 8.42G 81.4G 8.42G /
> zroot_z-hp/storage 8.52G 81.4G 8.52G /home/zeus/storage
> zroot_z-hp/tmp 291M 81.4G 291M /tmp
> zroot_z-hp/usr 9.35G 81.4G 144K /usr
> zroot_z-hp/usr/home 5.27G 81.4G 2.43G /usr/home
> zroot_z-hp/usr/ports 3.00G 81.4G 1.80G /usr/ports
> zroot_z-hp/usr/src 1.08G 81.4G 1.08G /usr/src
> zroot_z-hp/var 1.15G 81.4G 1017M /var
> zroot_z-hp/var/crash 148K 81.4G 148K /var/crash
> zroot_z-hp/var/log 5.99M 81.4G 5.99M /var/log
> zroot_z-hp/var/tmp 153M 81.4G 153M /var/tmp
> zroot_z-hp/ROOT/default on / (zfs, local, noatime, nfsv4acls)
>
> 2.2. df -h
> devfs on /dev (devfs, local, multilabel)
> zroot_z-hp/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
> zroot_z-hp/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)
> zroot_z-hp/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls)
> zroot_z-hp/usr/src on /usr/src (zfs, local, noatime, noexec, nosuid,
> nfsv4acls)
> zroot_z-hp/var on /var (zfs, local, noatime, nfsv4acls)
> zroot_z-hp/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid,
> nfsv4acls)
> zroot_z-hp/var/log on /var/log (zfs, local, noatime, noexec, nosuid,
> nfsv4acls)
> zroot_z-hp/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
> zroot_z-hp/storage on /usr/home/zeus/storage (zfs, local, noatime,
> nfsv4acls)
>
>
> --
> Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
> IT Dpt., I.B.S. LLC GMT+2 (EET)
>
From owner-freebsd-fs@FreeBSD.ORG Wed Nov 5 08:26:28 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 490379CB
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 08:26:28 +0000 (UTC)
Received: from mail-yk0-x22f.google.com (mail-yk0-x22f.google.com
[IPv6:2607:f8b0:4002:c07::22f])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 0196A27B
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 08:26:28 +0000 (UTC)
Received: by mail-yk0-f175.google.com with SMTP id q9so107940ykb.6
for <freebsd-fs@freebsd.org>; Wed, 05 Nov 2014 00:26:27 -0800 (PST)
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=9ISG+kXUWAA77Fjje3Zb6lYRWPKq1JCxbjGBIhOCkAo=;
b=v479HBkP9YopyOFP9H3IqLWeTFcpf8PVg+IO8TLPulqmL10fPs6HKmpYfTDKP91MxM
tfyd3DyBS3YHcQBi8Ytkh0ddLra6o9vhRVGDFYdi3y4pw/4xj41bOQfVIA0CvPZGz8j0
nE7ul1kXbrdTUdD6lFlf0mJhB0sfe1XrwyfzQC7IXOFsSXynXGFLvkSpXlAdRpAebFId
9hndwayBssAYpY/uqWKCk0Sh2MAvIbGQE7hh4FT6JrjjVIshZp2Kk8vOWTws9ZjR0ulE
aa4Th20xyYLn6Smt0RzUJjzIIVWKbMXQzrLhurSuKQqdJX+enjvGpAw3YVtvoKGEz/v5
+Q+Q==
MIME-Version: 1.0
X-Received: by 10.236.63.70 with SMTP id z46mr2186724yhc.187.1415175987143;
Wed, 05 Nov 2014 00:26:27 -0800 (PST)
Received: by 10.170.156.139 with HTTP; Wed, 5 Nov 2014 00:26:27 -0800 (PST)
In-Reply-To: <CAHEMsqZ-MYp_oNL4E=_PifdXo9O=RdYrhU5RL4bpc_=L0rUCmQ@mail.gmail.com>
References: <20141104072923.79140@smtp.new-ukraine.org>
<20141104081924.GY9223@sludge.elizium.za.net>
<20141105001214.31614@smtp.new-ukraine.org>
<CAHEMsqZ-MYp_oNL4E=_PifdXo9O=RdYrhU5RL4bpc_=L0rUCmQ@mail.gmail.com>
Date: Wed, 5 Nov 2014 08:26:27 +0000
Message-ID: <CALfReyfTCPqBDbxhY6sE807k1REwqq+=v+yGPUr9+s48oUAWfg@mail.gmail.com>
Subject: Re: why no automount for one zfs?
From: krad <kraduk@gmail.com>
To: Steven Hartland <killing@multiplay.co.uk>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: FreeBSD FS <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 08:26:28 -0000
Basically its getting mounted 1st then zroot_z-hp/usr/home is getting
mounted ontop of it and hiding it.
You should consider putting zroot_z-hp/storage under the usr/home hierarchy
as it will protect you to some degree from this scenario
On 4 November 2014 23:31, Steven Hartland <killing@multiplay.co.uk> wrote:
> So it is mounting it, its just being shadowed by the usr mount point as
> /home is typically a symlink to /usr/home.
>
> Change your mount point to /usr/home/zeus/storage from /home/zeus/storage
> and you should be good.
>
> On 5 November 2014 22:12, Zeus Panchenko <zeus@ibs.dn.ua> wrote:
>
> > Hugo Lombard <hal@elizium.za.net> wrote:
> >
> > > On Tue, Nov 04, 2014 at 07:29:23AM +0200, Zeus Panchenko wrote:
> > > >
> > > > after reboot this very fs is listed as mounted but the mount
> directory
> > > > for it, is empty ... after umount/mount everything appears on it's
> > > > expected place ...
> > > >
> > >
> > > Could you perhaps show the output of "mount" before and after?
> > >
> >
> > here it is
> >
> > 1. before umount/mount
> > 1.1. zfs list
> > NAME USED AVAIL REFER MOUNTPOINT
> > zroot_z-hp 27.9G 81.4G 144K none
> > zroot_z-hp/ROOT 8.42G 81.4G 144K none
> > zroot_z-hp/ROOT/default 8.42G 81.4G 8.42G /
> > zroot_z-hp/storage 8.52G 81.4G 8.52G /home/zeus/storage
> > zroot_z-hp/tmp 291M 81.4G 291M /tmp
> > zroot_z-hp/usr 9.35G 81.4G 144K /usr
> > zroot_z-hp/usr/home 5.27G 81.4G 2.43G /usr/home
> > zroot_z-hp/usr/ports 3.00G 81.4G 1.80G /usr/ports
> > zroot_z-hp/usr/src 1.08G 81.4G 1.08G /usr/src
> > zroot_z-hp/var 1.15G 81.4G 1017M /var
> > zroot_z-hp/var/crash 148K 81.4G 148K /var/crash
> > zroot_z-hp/var/log 5.99M 81.4G 5.99M /var/log
> > zroot_z-hp/var/tmp 153M 81.4G 153M /var/tmp
> > zroot_z-hp/ROOT/default on / (zfs, local, noatime, nfsv4acls)
> >
> > 1.2. df -h
> > devfs on /dev (devfs, local, multilabel)
> > zroot_z-hp/storage on /usr/home/zeus/storage (zfs, local, noatime,
> > nfsv4acls)
> > zroot_z-hp/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
> > zroot_z-hp/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)
> > zroot_z-hp/usr/ports on /usr/ports (zfs, local, noatime, nosuid,
> nfsv4acls)
> > zroot_z-hp/usr/src on /usr/src (zfs, local, noatime, noexec, nosuid,
> > nfsv4acls)
> > zroot_z-hp/var on /var (zfs, local, noatime, nfsv4acls)
> > zroot_z-hp/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid,
> > nfsv4acls)
> > zroot_z-hp/var/log on /var/log (zfs, local, noatime, noexec, nosuid,
> > nfsv4acls)
> > zroot_z-hp/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
> >
> > 1.3. ls -al /home/zeus/storage
> > total 41
> > drwxr-xr-x 2 root staff 2 Jul 20 21:37 .
> > drwxr-xr-x 48 zeus staff 118 Nov 4 21:02 ..
> >
> > 2. after umount/mount
> > 2.1. zfs list
> > NAME USED AVAIL REFER MOUNTPOINT
> > zroot_z-hp 27.9G 81.4G 144K none
> > zroot_z-hp/ROOT 8.42G 81.4G 144K none
> > zroot_z-hp/ROOT/default 8.42G 81.4G 8.42G /
> > zroot_z-hp/storage 8.52G 81.4G 8.52G /home/zeus/storage
> > zroot_z-hp/tmp 291M 81.4G 291M /tmp
> > zroot_z-hp/usr 9.35G 81.4G 144K /usr
> > zroot_z-hp/usr/home 5.27G 81.4G 2.43G /usr/home
> > zroot_z-hp/usr/ports 3.00G 81.4G 1.80G /usr/ports
> > zroot_z-hp/usr/src 1.08G 81.4G 1.08G /usr/src
> > zroot_z-hp/var 1.15G 81.4G 1017M /var
> > zroot_z-hp/var/crash 148K 81.4G 148K /var/crash
> > zroot_z-hp/var/log 5.99M 81.4G 5.99M /var/log
> > zroot_z-hp/var/tmp 153M 81.4G 153M /var/tmp
> > zroot_z-hp/ROOT/default on / (zfs, local, noatime, nfsv4acls)
> >
> > 2.2. df -h
> > devfs on /dev (devfs, local, multilabel)
> > zroot_z-hp/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
> > zroot_z-hp/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)
> > zroot_z-hp/usr/ports on /usr/ports (zfs, local, noatime, nosuid,
> nfsv4acls)
> > zroot_z-hp/usr/src on /usr/src (zfs, local, noatime, noexec, nosuid,
> > nfsv4acls)
> > zroot_z-hp/var on /var (zfs, local, noatime, nfsv4acls)
> > zroot_z-hp/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid,
> > nfsv4acls)
> > zroot_z-hp/var/log on /var/log (zfs, local, noatime, noexec, nosuid,
> > nfsv4acls)
> > zroot_z-hp/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
> > zroot_z-hp/storage on /usr/home/zeus/storage (zfs, local, noatime,
> > nfsv4acls)
> >
> >
> > --
> > Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
> > IT Dpt., I.B.S. LLC GMT+2 (EET)
> >
> _______________________________________________
> 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 Nov 5 08:44:53 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 DBD38C91
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 08:44:52 +0000 (UTC)
Received: from mail.slu.se (tmgext2-3.slu.se [77.235.224.53])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id ADA0F68D
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 08:44:50 +0000 (UTC)
Received: from Exchange2-3.slu.se (130.238.96.156) by Tmg2-3.slu.se
(130.238.96.153) with Microsoft SMTP Server (TLS) id 14.3.210.2; Wed, 5 Nov
2014 09:44:42 +0100
Received: from Exchange2-1.slu.se ([130.238.96.154]) by exchange2-3
([130.238.96.156]) with mapi id 14.03.0210.002; Wed, 5 Nov 2014 09:44:41
+0100
From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= <Karli.Sjoberg@slu.se>
To: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject: Differences in memory handling on systems with/out cache drives
Thread-Topic: Differences in memory handling on systems with/out cache drives
Thread-Index: Ac/41L0Gnp83ctyFT9W1UAOKlNmesA==
Date: Wed, 5 Nov 2014 08:44:40 +0000
Message-ID: <5F9E965F5A80BC468BE5F40576769F099DF87F57@exchange2-1>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [77.235.228.32]
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 08:44:53 -0000
SGV5IGFsbCEKClN0aWxsIGludmVzdGlnYXRpbmcgdGhlIGludGVybWl0dGVudCBsb2NrdXBzIHdl
IGFyZSBleHBlcmllbmNpbmcgb24gb3VyCnN0b3JhZ2Ugc3lzdGVtcyBhbmQgaGF2ZSBzdGFydGVk
IHRvIGNvbXBhcmUgbWVtb3J5IGdyYXBocyBmcm9tIG91cgpHcmFwaGl0ZSBtb25pdG9yaW5nIHN5
c3RlbS4gV2hhdMK0cyBpbnRlcmVzdGluZyBhYm91dCB0d28gb2Ygb3VyIHN5c3RlbXMKaXMgdGhh
dCB0aGV5IGJvdGggaGF2ZSB0aGUgc2FtZSBhbW91bnQgb2YgUkFNOyAzMiBHQi4gQnV0IG9uIG9u
ZSBvZgp0aGVtLCBJIGhhdmUgInpwb29sIHJlbW92ZSInZCB0aGUgY2FjaGUgZHJpdmVzIGZyb20g
dGhlIHBvb2wgYW5kIGhhdmUKYmVlbiBhYmxlIHRvIHN0dWR5IGhvdyBkaWZmZXJlbnQgdGhlaXIg
bWVtb3J5IGdyYXBocyBub3cgbG9vayBsaWtlLgoKQWxzbyB3b3J0aCBub3RpbmcgaXMgdGhhdCB0
aGUgY2FjaGUtbGVzcyBzeXN0ZW0gbmVhcmx5IGhhdmVuwrR0IHN3YXBwZWQKYXQgYWxsICgxMTEy
Sykgc2luY2UgdGhlIGxhc3Qgc3RhbGwgMjAgZGF5cyBhZ28sIHdoaWxlIHRoZSBvdGhlciBzeXN0
ZW0KaGFzIHN3YXBwZWQgNzggTUIgZHVyaW5nIGl0wrRzIDQ4IGRheXMgb2YgdXB0aW1lLgoKScK0
dmUgYXR0YWNoZWQgYm90aCBzY3JlZW5zaG90cyBmcm9tIHRoZSB0d28gc3lzdGVtcywgd2l0aC0g
YW5kIHdpdGhvdXQKY2FjaGUgZHJpdmVzLCBkaXNwbGF5aW5nIGEgcGVyaW9kIG9mIDEyIGhvdXJz
LgoKV2hhdMK0cyBtb3N0IG5vdGFibGUgYXJlIHRoZSBjaGFyYWN0ZXJpc3RpYyBjdXRzIHRoYXQg
aGFwcGVuIG9uIHRoZQpjYWNoZS1sZXNzIHN5c3RlbSB3aGVuIFpGUyBnb2VzIGluIGFuZCBldmlj
dHMgYmxvY2tzIGZyb20gQVJDIHRoYXQgc2hvd3MKYXMgYSBkZWNyZWFzZSBpbiAid2lyZWQiIGFu
ZCBpbmNyZWFzZSBpbiAiZnJlZSIsIHRoYXQganVzdCBkb2VzbsK0dApoYXBwZW4vbG9va3MgZGlm
ZmVyZW50IGluIHRoZSBzeXN0ZW0gd2l0aCBjYWNoZSBkcml2ZSBjb25maWd1cmVkIGluIHRoZQpw
b29sLgoKV2hhdMK0cyB5b3VyIHRha2Ugb24gdGhpcz8gQXJlIHdlIGhpdHRpbmcgYnVnOiAxODc1
OTQgcGVyaGFwcz8gSG93IGNhbiB3ZQprbm93PwoKCi0tIAoKTWVkIFbDpG5saWdhIEjDpGxzbmlu
Z2FyCgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCkthcmxpIFNqw7ZiZXJnClN3ZWRpc2ggVW5pdmVy
c2l0eSBvZiBBZ3JpY3VsdHVyYWwgU2NpZW5jZXMgQm94IDcwNzkgKFZpc2l0aW5nIEFkZHJlc3MK
S3JvbsOlc3bDpGdlbiA4KQpTLTc1MCAwNyBVcHBzYWxhLCBTd2VkZW4KUGhvbmU6ICArNDYtKDAp
MTgtNjcgMTUgNjYKa2FybGkuc2pvYmVyZ0BzbHUuc2UK
From owner-freebsd-fs@FreeBSD.ORG Wed Nov 5 08:53:53 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 3E681ECE
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 08:53:53 +0000 (UTC)
Received: from mail.slu.se (tmgext2-1.slu.se [77.235.224.51])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 98C8B7D6
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 08:53:52 +0000 (UTC)
Received: from Exchange2-3.slu.se (130.238.96.156) by Tmg2-1.slu.se
(130.238.96.151) with Microsoft SMTP Server (TLS) id 14.3.210.2; Wed, 5 Nov
2014 09:53:43 +0100
Received: from Exchange2-1.slu.se ([130.238.96.154]) by exchange2-3
([130.238.96.156]) with mapi id 14.03.0210.002; Wed, 5 Nov 2014 09:53:43
+0100
From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= <Karli.Sjoberg@slu.se>
To: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject: Re: Differences in memory handling on systems with/out cache drives
Thread-Topic: Differences in memory handling on systems with/out cache drives
Thread-Index: AQHP+NYAYcHKJ/GmaECo9Rzajby0aA==
Date: Wed, 5 Nov 2014 08:53:42 +0000
Message-ID: <5F9E965F5A80BC468BE5F40576769F099DF87FBB@exchange2-1>
References: <5F9E965F5A80BC468BE5F40576769F099DF87F57@exchange2-1>
In-Reply-To: <5F9E965F5A80BC468BE5F40576769F099DF87F57@exchange2-1>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [77.235.228.32]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 08:53:53 -0000
T24gV2VkLCAyMDE0LTExLTA1IGF0IDA4OjQ0ICswMDAwLCBLYXJsaSBTasO2YmVyZyB3cm90ZToK
PiBIZXkgYWxsIQo+IAo+IFN0aWxsIGludmVzdGlnYXRpbmcgdGhlIGludGVybWl0dGVudCBsb2Nr
dXBzIHdlIGFyZSBleHBlcmllbmNpbmcgb24gb3VyCj4gc3RvcmFnZSBzeXN0ZW1zIGFuZCBoYXZl
IHN0YXJ0ZWQgdG8gY29tcGFyZSBtZW1vcnkgZ3JhcGhzIGZyb20gb3VyCj4gR3JhcGhpdGUgbW9u
aXRvcmluZyBzeXN0ZW0uIFdoYXTCtHMgaW50ZXJlc3RpbmcgYWJvdXQgdHdvIG9mIG91ciBzeXN0
ZW1zCj4gaXMgdGhhdCB0aGV5IGJvdGggaGF2ZSB0aGUgc2FtZSBhbW91bnQgb2YgUkFNOyAzMiBH
Qi4gQnV0IG9uIG9uZSBvZgo+IHRoZW0sIEkgaGF2ZSAienBvb2wgcmVtb3ZlIidkIHRoZSBjYWNo
ZSBkcml2ZXMgZnJvbSB0aGUgcG9vbCBhbmQgaGF2ZQo+IGJlZW4gYWJsZSB0byBzdHVkeSBob3cg
ZGlmZmVyZW50IHRoZWlyIG1lbW9yeSBncmFwaHMgbm93IGxvb2sgbGlrZS4KPiAKPiBBbHNvIHdv
cnRoIG5vdGluZyBpcyB0aGF0IHRoZSBjYWNoZS1sZXNzIHN5c3RlbSBuZWFybHkgaGF2ZW7CtHQg
c3dhcHBlZAo+IGF0IGFsbCAoMTExMkspIHNpbmNlIHRoZSBsYXN0IHN0YWxsIDIwIGRheXMgYWdv
LCB3aGlsZSB0aGUgb3RoZXIgc3lzdGVtCj4gaGFzIHN3YXBwZWQgNzggTUIgZHVyaW5nIGl0wrRz
IDQ4IGRheXMgb2YgdXB0aW1lLgo+IAo+IEnCtHZlIGF0dGFjaGVkIGJvdGggc2NyZWVuc2hvdHMg
ZnJvbSB0aGUgdHdvIHN5c3RlbXMsIHdpdGgtIGFuZCB3aXRob3V0Cj4gY2FjaGUgZHJpdmVzLCBk
aXNwbGF5aW5nIGEgcGVyaW9kIG9mIDEyIGhvdXJzLgo+IAo+IFdoYXTCtHMgbW9zdCBub3RhYmxl
IGFyZSB0aGUgY2hhcmFjdGVyaXN0aWMgY3V0cyB0aGF0IGhhcHBlbiBvbiB0aGUKPiBjYWNoZS1s
ZXNzIHN5c3RlbSB3aGVuIFpGUyBnb2VzIGluIGFuZCBldmljdHMgYmxvY2tzIGZyb20gQVJDIHRo
YXQgc2hvd3MKPiBhcyBhIGRlY3JlYXNlIGluICJ3aXJlZCIgYW5kIGluY3JlYXNlIGluICJmcmVl
IiwgdGhhdCBqdXN0IGRvZXNuwrR0Cj4gaGFwcGVuL2xvb2tzIGRpZmZlcmVudCBpbiB0aGUgc3lz
dGVtIHdpdGggY2FjaGUgZHJpdmUgY29uZmlndXJlZCBpbiB0aGUKPiBwb29sLgo+IAo+IFdoYXTC
tHMgeW91ciB0YWtlIG9uIHRoaXM/IEFyZSB3ZSBoaXR0aW5nIGJ1ZzogMTg3NTk0IHBlcmhhcHM/
IEhvdyBjYW4gd2UKPiBrbm93Pwo+IAo+IAo+IC0tIAo+IAo+IE1lZCBWw6RubGlnYSBIw6Rsc25p
bmdhcgo+IAo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBLYXJsaSBTasO2YmVyZwo+IFN3ZWRp
c2ggVW5pdmVyc2l0eSBvZiBBZ3JpY3VsdHVyYWwgU2NpZW5jZXMgQm94IDcwNzkgKFZpc2l0aW5n
IEFkZHJlc3MKPiBLcm9uw6VzdsOkZ2VuIDgpCj4gUy03NTAgMDcgVXBwc2FsYSwgU3dlZGVuCj4g
UGhvbmU6ICArNDYtKDApMTgtNjcgMTUgNjYKPiBrYXJsaS5zam9iZXJnQHNsdS5zZQo+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gZnJlZWJzZC1mc0Bm
cmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QKPiBodHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1h
bi9saXN0aW5mby9mcmVlYnNkLWZzCj4gVG8gdW5zdWJzY3JpYmUsIHNlbmQgYW55IG1haWwgdG8g
ImZyZWVic2QtZnMtdW5zdWJzY3JpYmVAZnJlZWJzZC5vcmciCgpEYW1uaXQsIHRoZSBpbWFnZXMg
YXR0YWNoZWQgZGlzYXBwZWFyZWQsIGhlcmUgYXJlIHdlYmxpbmtzIGZvciB0aGVtCmluc3RlYWQ6
Cgp3aXRoLWwyYXJjOiAgICBodHRwOi8vaS5pbWd1ci5jb20vb3VORk92Yy5wbmcKCndpdGhvdXQt
bDJhcmM6IGh0dHA6Ly9pLmltZ3VyLmNvbS8wcEJreU9TLnBuZwoKU29ycnkgYWJvdXQgdGhhdC4K
CgotLSAKCk1lZCBWw6RubGlnYSBIw6Rsc25pbmdhcgoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpL
YXJsaSBTasO2YmVyZwpTd2VkaXNoIFVuaXZlcnNpdHkgb2YgQWdyaWN1bHR1cmFsIFNjaWVuY2Vz
IEJveCA3MDc5IChWaXNpdGluZyBBZGRyZXNzCktyb27DpXN2w6RnZW4gOCkKUy03NTAgMDcgVXBw
c2FsYSwgU3dlZGVuClBob25lOiAgKzQ2LSgwKTE4LTY3IDE1IDY2CmthcmxpLnNqb2JlcmdAc2x1
LnNlCg==
From owner-freebsd-fs@FreeBSD.ORG Wed Nov 5 10:23:07 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 EBD38C0A
for <freebsd-fs@FreeBSD.org>; Wed, 5 Nov 2014 10:23:07 +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 D297B160
for <freebsd-fs@FreeBSD.org>; Wed, 5 Nov 2014 10:23:07 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA5AN7jn051644
for <freebsd-fs@FreeBSD.org>; Wed, 5 Nov 2014 10:23:07 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 161968] [zfs] [hang] renaming snapshot with -r including a zvol
snapshot causes total ZFS freeze/lockup
Date: Wed, 05 Nov 2014 10:23:08 +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: 8.2-STABLE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: FreeBSD@ShaneWare.Biz
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-161968-3630-WNx8jMcdD5@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-161968-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-161968-3630@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 10:23:08 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161968
FreeBSD@ShaneWare.Biz changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |FreeBSD@ShaneWare.Biz
--- Comment #10 from FreeBSD@ShaneWare.Biz ---
I am unable to reproduce this on 10.1RC4
--
You are receiving this mail because:
You are the assignee for the bug.
From owner-freebsd-fs@FreeBSD.ORG Wed Nov 5 10:26:19 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 3E847CCE
for <freebsd-fs@FreeBSD.org>; Wed, 5 Nov 2014 10:26:19 +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 25DB9188
for <freebsd-fs@FreeBSD.org>; Wed, 5 Nov 2014 10:26:19 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA5AQJLJ053315
for <freebsd-fs@FreeBSD.org>; Wed, 5 Nov 2014 10:26:19 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 161968] [zfs] [hang] renaming snapshot with -r including a zvol
snapshot causes total ZFS freeze/lockup
Date: Wed, 05 Nov 2014 10:26: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: 8.2-STABLE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: smh@FreeBSD.org
X-Bugzilla-Status: Issue Resolved
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-161968-3630-31ekAnJq8c@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-161968-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-161968-3630@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 10:26:19 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161968
Steven Hartland <smh@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|In Discussion |Issue Resolved
CC| |smh@FreeBSD.org
Resolution|--- |FIXED
--- Comment #11 from Steven Hartland <smh@FreeBSD.org> ---
Thanks for the confirmation.
For the record this was fixed by r273162.
--
You are receiving this mail because:
You are the assignee for the bug.
From owner-freebsd-fs@FreeBSD.ORG Wed Nov 5 11:12:17 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 107C1624
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 11:12:17 +0000 (UTC)
Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "smtp.new-ukraine.org",
Issuer "smtp.new-ukraine.org" (not verified))
by mx1.freebsd.org (Postfix) with ESMTPS id 878858D8
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 11:12:15 +0000 (UTC)
Received: on behalf of honored client by smtp.new-ukraine.org with ESMTP id
sA5BBuZi067320 on Wed, 5 Nov 2014 13:11:57 +0200 (EET)
Message-ID: <20141105131151.67318@smtp.new-ukraine.org>
Date: Wed, 05 Nov 2014 13:11:51 +0200
From: "Zeus Panchenko" <zeus@ibs.dn.ua>
To: "Steven Hartland" <killing@multiplay.co.uk>
Subject: Re: why no automount for one zfs?
In-reply-to: Your message of Tue, 4 Nov 2014 23:31:48 +0000
<CAHEMsqZ-MYp_oNL4E=_PifdXo9O=RdYrhU5RL4bpc_=L0rUCmQ@mail.gmail.com>
References: <20141104072923.79140@smtp.new-ukraine.org>
<20141104081924.GY9223@sludge.elizium.za.net>
<20141105001214.31614@smtp.new-ukraine.org>
<CAHEMsqZ-MYp_oNL4E=_PifdXo9O=RdYrhU5RL4bpc_=L0rUCmQ@mail.gmail.com>
Organization: I.B.S. LLC
Reply-To: "Zeus Panchenko" <zeus@ibs.dn.ua>
X-Attribution: zeus
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN
cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F
eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N
ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw
15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5
lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG
ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq
zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe
riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M
1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a
mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs
SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6
7tXQAAAAASUVORK5CYII=
X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha1; protocol="application/pgp-signature"
X-NewUkraine-Agent: mailfromd (7.99.92)
X-NewUkraine-URL: http://www.ibs.dn.ua/smtp.html
X-NewUkraine-VirStat: NO
X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures,
ScanHTML, ScanPDF
X-NewUkraine-SpamStat: NO
X-NewUkraine-SpamScore: -1.600 of 3.500
X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 11:12:17 -0000
--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Steven Hartland <killing@multiplay.co.uk> wrote:
> So it is mounting it, its just being shadowed by the usr mount point
> as /home is typically a symlink to /usr/home.
yes, it works! thank you much
what did I miss concerning the shadowing? where is it descibed, please?
=2D-=20
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
--=-=-=
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlRaBfcACgkQr3jpPg/3oypQCQCggKlrq9VgQ0D+9w0/BXa0lxPZ
z68AoMvrbV0dbrzxgaqo8UPcD4npV6Xb
=7sPM
-----END PGP SIGNATURE-----
--=-=-=--
From owner-freebsd-fs@FreeBSD.ORG Wed Nov 5 11:16:28 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 8BB0777C
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 11:16:28 +0000 (UTC)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 1E9A9909
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 11:16:27 +0000 (UTC)
Received: by mail-wg0-f50.google.com with SMTP id z12so624429wgg.23
for <freebsd-fs@freebsd.org>; Wed, 05 Nov 2014 03:16:26 -0800 (PST)
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
:cc:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=i6ErZ+7QrTZniJ3FuW3sbTOJd16Ip7ryxXBIBCuY9A4=;
b=gcNO5oeXQ5X+Pwao8lkdenfdpXhvvzB4PNN1QZRwHJ4JFXjcIs5EvZ7n7vEJ+KZmLc
eBZDSObPB75PMgBwYXhwUnv58F/77+8EbyQzI6nJkqovbju1en9qMdBzPCPwNJwilQB5
qHDdkv4yVeaCWgO9JJ3cAlXYbEHfkhw96zavZPVGBUy7CTQOVX1Gg3F0pG/854pt7PfU
ZwaIYtgyanL+tyUNB32lKVOfpelfcBd9eiDU9clIm2vqowT4N7Ys8xFl1FapGDvUK5/3
abbYPlT1+HLOuAcFFnMHKeffD1pJlPmvDCOeSWk5LXID9MkvQ4IYiV1jTZOXJPZAg/W+
If+w==
X-Gm-Message-State: ALoCoQkzF0ci7c/TbWmduawhcyYQHXfANTFDZ6Odn3g65khlYo4e6snYZ52N6QywuGyv95bgtZ0y
X-Received: by 10.194.133.229 with SMTP id pf5mr65048672wjb.73.1415186186109;
Wed, 05 Nov 2014 03:16:26 -0800 (PST)
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 ci9sm4184324wid.24.2014.11.05.03.16.24
for <multiple recipients>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 05 Nov 2014 03:16:25 -0800 (PST)
Message-ID: <545A06B5.7010208@multiplay.co.uk>
Date: Wed, 05 Nov 2014 11:15:01 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Zeus Panchenko <zeus@ibs.dn.ua>
Subject: Re: why no automount for one zfs?
References: <20141104072923.79140@smtp.new-ukraine.org>
<20141104081924.GY9223@sludge.elizium.za.net>
<20141105001214.31614@smtp.new-ukraine.org>
<CAHEMsqZ-MYp_oNL4E=_PifdXo9O=RdYrhU5RL4bpc_=L0rUCmQ@mail.gmail.com>
<20141105131151.67318@smtp.new-ukraine.org>
In-Reply-To: <20141105131151.67318@smtp.new-ukraine.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 11:16:28 -0000
On 05/11/2014 11:11, Zeus Panchenko wrote:
> Steven Hartland <killing@multiplay.co.uk> wrote:
>
>> So it is mounting it, its just being shadowed by the usr mount point
>> as /home is typically a symlink to /usr/home.
> yes, it works! thank you much
>
> what did I miss concerning the shadowing? where is it descibed, please?
>
Because your mounting under a different location (via a symlink), when
ZFS mounts the volumes it doesn't spot that there is a dependency there.
This results in /usr being mounted after the volume under /home which is
a symlink to /usr/home hence the volume /usr shadows / hides the one
mounted under /usr/home which was mounted first.
Regards
Steve
From owner-freebsd-fs@FreeBSD.ORG Wed Nov 5 15:41:54 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 5A0AFBB5
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 15:41:54 +0000 (UTC)
Received: from mta1-filtered.netlife.no (mail.netlife.no [62.92.26.226])
by mx1.freebsd.org (Postfix) with ESMTP id 13FC1D32
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 15:41:53 +0000 (UTC)
Received: from amavis.netlife.no (unknown [10.115.1.11])
by mta1-filtered.netlife.no (Postfix) with ESMTP id 1057D1C9573
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 16:36:12 +0100 (CET)
X-Virus-Scanned: amavisd-new at netlife.no
Received: from mta1-submission.netlife.no ([62.92.26.226])
by amavis.netlife.no (amavis.netlife.no [10.115.1.11]) (amavisd-new,
port 10026) with ESMTP id siOdQLDlZaof for <freebsd-fs@freebsd.org>;
Wed, 5 Nov 2014 16:36:11 +0100 (CET)
Received: from [10.0.0.41] (unknown [195.1.220.218])
(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
(No client certificate requested)
(Authenticated sender: erik@tefre.com)
by mta1-submission.netlife.no (Postfix) with ESMTPSA id D80EA1C956F
for <freebsd-fs@freebsd.org>; Wed, 5 Nov 2014 16:36:11 +0100 (CET)
Message-ID: <545A43EB.7070603@tefre.com>
Date: Wed, 05 Nov 2014 16:36:11 +0100
From: Erik Stian Tefre <erik@tefre.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: freebsd-fs@freebsd.org
Subject: Re: Differences in memory handling on systems with/out cache drives
References: <5F9E965F5A80BC468BE5F40576769F099DF87F57@exchange2-1>
<5F9E965F5A80BC468BE5F40576769F099DF87FBB@exchange2-1>
In-Reply-To: <5F9E965F5A80BC468BE5F40576769F099DF87FBB@exchange2-1>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 15:41:54 -0000
On 05. nov. 2014 09:53, Karli Sjöberg wrote:
> On Wed, 2014-11-05 at 08:44 +0000, Karli Sjöberg wrote:
>> Hey all!
>>
>> Still investigating the intermittent lockups we are experiencing on our
>> storage systems and have started to compare memory graphs from our
>> Graphite monitoring system. What´s interesting about two of our systems
>> is that they both have the same amount of RAM; 32 GB. But on one of
>> them, I have "zpool remove"'d the cache drives from the pool and have
>> been able to study how different their memory graphs now look like.
>>
>> Also worth noting is that the cache-less system nearly haven´t swapped
>> at all (1112K) since the last stall 20 days ago, while the other system
>> has swapped 78 MB during it´s 48 days of uptime.
>>
>> I´ve attached both screenshots from the two systems, with- and without
>> cache drives, displaying a period of 12 hours.
>>
>> What´s most notable are the characteristic cuts that happen on the
>> cache-less system when ZFS goes in and evicts blocks from ARC that shows
>> as a decrease in "wired" and increase in "free", that just doesn´t
>> happen/looks different in the system with cache drive configured in the
>> pool.
>>
>> What´s your take on this? Are we hitting bug: 187594 perhaps? How can we
>> know?
Take a look at the recent thread on freebsd-stable@, subject "ARC size
limit". Possibly related issues have been patched in stable/10, the
mailing list thread includes a patch for releng/10.1.
--
Erik
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 11:01:43 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 04FD4EBC
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 11:01:43 +0000 (UTC)
Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com
[195.16.150.151])
(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 49598BFE
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 11:01:42 +0000 (UTC)
Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11])
by proxypop03.sare.net (Postfix) with ESMTPSA id 1513D9DCDE6
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 12:01:32 +0100 (CET)
From: Borja Marcos <borjam@sarenet.es>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
Date: Thu, 6 Nov 2014 12:01:27 +0100
Message-Id: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
To: "freebsd-fs@FreeBSD.org Filesystems" <freebsd-fs@freebsd.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 11:01:43 -0000
Hi,
I have noticed that ZIL creation _ignores_ the vfs.zfs.min_auto_ashift =
variable. ZIL and cache on SSDs should use
this variable in order to apply the optimum sector size on SSDs or =
so-called advanced format drives.
The system is:
root@splunk:/ # uname -a
FreeBSD splunk 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #12: Tue Nov 4 =
11:22:48 CET 2014 root@splunk:/usr/obj/usr/src/sys/SPLUNK10 amd64
Example:
# sysctl vfs.zfs.min_auto_ashift=3D12
# zpool status //// Just a common mirror with two hard disks
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 =
2014
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada0p3 ONLINE 0 0 0
ada2p3 ONLINE 0 0 0
errors: No known data errors
# zpool add rpool log ada1
# zpool status
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 =
2014
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada0p3 ONLINE 0 0 0
ada2p3 ONLINE 0 0 0
logs
ada1 ONLINE 0 0 0
errors: No known data errors
///// There it is, but
# zdb | more
version: 5000
name: 'rpool'
state: 0
txg: 11738986
pool_guid: 18110845055860026534
hostid: 316898903
hostname: 'splunk'
vdev_children: 2
vdev_tree:
type: 'root'
id: 0
guid: 18110845055860026534
children[0]:
type: 'mirror'
id: 0
guid: 10858793804082837265
metaslab_array: 30
metaslab_shift: 32
ashift: 12
asize: 482922987520
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 10490056043151312448
path: '/dev/ada0p3'
phys_path: '/dev/ada0p3'
whole_disk: 1
DTL: 331
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 2441255496794840851
path: '/dev/ada2p3'
phys_path: '/dev/ada2p3'
whole_disk: 1
DTL: 252
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 3564614139316480036
path: '/dev/ada1'
id: 1
guid: 2441255496794840851
path: '/dev/ada2p3'
phys_path: '/dev/ada2p3'
whole_disk: 1
DTL: 252
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 3564614139316480036
path: '/dev/ada1'
phys_path: '/dev/ada1'
whole_disk: 1
metaslab_array: 0
metaslab_shift: 0
ashift: 9 =
<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =
WRONG, SHOULDN'T IT BE 12??
asize: 40015757312
is_log: 1
create_txg: 11738986
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
If, however, I do the gnop trick,
# gnop create -S 4K ada1
# zpool add rpool log ada1.nop
# zpool status
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 =
2014
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada0p3 ONLINE 0 0 0
ada2p3 ONLINE 0 0 0
logs
ada1.nop ONLINE 0 0 0
errors: No known data errors
this time our mirror has the ashift we wanted, 12.=20
children[1]:
type: 'disk'
id: 1
guid: 6487094506120463221
path: '/dev/ada1.nop'
phys_path: '/dev/ada1.nop'
whole_disk: 1
metaslab_array: 0
metaslab_shift: 0
ashift: 12
asize: 40015757312
is_log: 1
create_txg: 11739034
The disks I am playing with are:
# camcontrol devlist
<ST3500418AS CC38> at scbus0 target 0 lun 0 (ada0,pass0)
<INTEL SSDSA2CT040G3 4PC10362> at scbus1 target 0 lun 0 (ada1,pass1)
<ST500DM002-1BC142 JC4B> at scbus2 target 0 lun 0 (ada2,pass2)
<INTEL SSDSA2CT040G3 4PC10362> at scbus3 target 0 lun 0 (ada3,pass3)
And yes, I know the two hard disks have different sector sizes but I =
created the pool with an ashift of 12.
Borja.
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 13:03:50 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 C07EDEDC
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:03:50 +0000 (UTC)
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com
[209.85.212.182])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 56F0FBE5
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:03:49 +0000 (UTC)
Received: by mail-wi0-f182.google.com with SMTP id d1so1406955wiv.9
for <freebsd-fs@freebsd.org>; Thu, 06 Nov 2014 05:03:42 -0800 (PST)
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=5gY53iFYlj4nYgkUsi3fsYsH83OCtYLEEpBZjO9fxbk=;
b=aqKhWRtwxzlUPzrhac3QjVB9TnbJhddkZ8aft0wqgb4wfUtYL1nCyoDVfZh+xwAYWO
NGn1bw5J0m+xDY/FYm6Sf/QdcPfnQdQrbHNL1Jz1Sec4boLyzKxWYYNuaqkCkxsqdFP5
+To1MrlxfVx/WDAAEMR12/bH5+20xntVMxQY10+OYwKLGcFPsSmIUSkW/FnKzeKJNAII
tePELZeYJ3IayjRkJ5GDbZBznkazNLgbEaIw6WTCQ02COkzJeIVDJvAO9HVwr7QuEkme
pYHauZrezKoBk28J5a51ceaebMRN5x7vxI6x9JAptwaHsuom6z35TkjyaGLuuJm/GIxj
VRDQ==
X-Gm-Message-State: ALoCoQmBgd4xVWRiTxQuoYYVWr/0yYh9qmHI5lSGCep7jZk2tvVxDt2hGjS/xcWnZBMPLS/IVZi2
X-Received: by 10.194.184.140 with SMTP id eu12mr5242536wjc.47.1415279022017;
Thu, 06 Nov 2014 05:03:42 -0800 (PST)
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 ht9sm19460236wib.8.2014.11.06.05.03.40
for <freebsd-fs@freebsd.org>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 06 Nov 2014 05:03:41 -0800 (PST)
Message-ID: <545B715A.5060804@multiplay.co.uk>
Date: Thu, 06 Nov 2014 13:02:18 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: freebsd-fs@freebsd.org
Subject: Re: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
In-Reply-To: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 13:03:50 -0000
Your zdb output looks strange you have two children[1] entries are you
sure your pool is not corrupt?
On 06/11/2014 11:01, Borja Marcos wrote:
>
> Hi,
>
> I have noticed that ZIL creation _ignores_ the vfs.zfs.min_auto_ashift variable. ZIL and cache on SSDs should use
> this variable in order to apply the optimum sector size on SSDs or so-called advanced format drives.
>
> The system is:
> root@splunk:/ # uname -a
> FreeBSD splunk 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #12: Tue Nov 4 11:22:48 CET 2014 root@splunk:/usr/obj/usr/src/sys/SPLUNK10 amd64
>
>
>
> Example:
>
> # sysctl vfs.zfs.min_auto_ashift=12
>
> # zpool status //// Just a common mirror with two hard disks
> pool: rpool
> state: ONLINE
> scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
> config:
>
> NAME STATE READ WRITE CKSUM
> rpool ONLINE 0 0 0
> mirror-0 ONLINE 0 0 0
> ada0p3 ONLINE 0 0 0
> ada2p3 ONLINE 0 0 0
>
> errors: No known data errors
>
>
> # zpool add rpool log ada1
>
> # zpool status
> pool: rpool
> state: ONLINE
> scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
> config:
>
> NAME STATE READ WRITE CKSUM
> rpool ONLINE 0 0 0
> mirror-0 ONLINE 0 0 0
> ada0p3 ONLINE 0 0 0
> ada2p3 ONLINE 0 0 0
> logs
> ada1 ONLINE 0 0 0
>
> errors: No known data errors
>
>
> ///// There it is, but
>
> # zdb | more
> version: 5000
> name: 'rpool'
> state: 0
> txg: 11738986
> pool_guid: 18110845055860026534
> hostid: 316898903
> hostname: 'splunk'
> vdev_children: 2
> vdev_tree:
> type: 'root'
> id: 0
> guid: 18110845055860026534
> children[0]:
> type: 'mirror'
> id: 0
> guid: 10858793804082837265
> metaslab_array: 30
> metaslab_shift: 32
> ashift: 12
> asize: 482922987520
> is_log: 0
> create_txg: 4
> children[0]:
> type: 'disk'
> id: 0
> guid: 10490056043151312448
> path: '/dev/ada0p3'
> phys_path: '/dev/ada0p3'
> whole_disk: 1
> DTL: 331
> create_txg: 4
> children[1]:
> type: 'disk'
> id: 1
> guid: 2441255496794840851
> path: '/dev/ada2p3'
> phys_path: '/dev/ada2p3'
> whole_disk: 1
> DTL: 252
> create_txg: 4
> children[1]:
> type: 'disk'
> id: 1
> guid: 3564614139316480036
> path: '/dev/ada1'
> id: 1
> guid: 2441255496794840851
> path: '/dev/ada2p3'
> phys_path: '/dev/ada2p3'
> whole_disk: 1
> DTL: 252
> create_txg: 4
> children[1]:
> type: 'disk'
> id: 1
> guid: 3564614139316480036
> path: '/dev/ada1'
> phys_path: '/dev/ada1'
> whole_disk: 1
> metaslab_array: 0
> metaslab_shift: 0
> ashift: 9 <======================= WRONG, SHOULDN'T IT BE 12??
> asize: 40015757312
> is_log: 1
> create_txg: 11738986
> features_for_read:
> com.delphix:hole_birth
> com.delphix:embedded_data
>
>
>
> If, however, I do the gnop trick,
>
> # gnop create -S 4K ada1
> # zpool add rpool log ada1.nop
> # zpool status
>
> pool: rpool
> state: ONLINE
> scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
> config:
>
> NAME STATE READ WRITE CKSUM
> rpool ONLINE 0 0 0
> mirror-0 ONLINE 0 0 0
> ada0p3 ONLINE 0 0 0
> ada2p3 ONLINE 0 0 0
> logs
> ada1.nop ONLINE 0 0 0
>
> errors: No known data errors
>
>
> this time our mirror has the ashift we wanted, 12.
>
> children[1]:
> type: 'disk'
> id: 1
> guid: 6487094506120463221
> path: '/dev/ada1.nop'
> phys_path: '/dev/ada1.nop'
> whole_disk: 1
> metaslab_array: 0
> metaslab_shift: 0
> ashift: 12
> asize: 40015757312
> is_log: 1
> create_txg: 11739034
>
>
>
> The disks I am playing with are:
>
> # camcontrol devlist
> <ST3500418AS CC38> at scbus0 target 0 lun 0 (ada0,pass0)
> <INTEL SSDSA2CT040G3 4PC10362> at scbus1 target 0 lun 0 (ada1,pass1)
> <ST500DM002-1BC142 JC4B> at scbus2 target 0 lun 0 (ada2,pass2)
> <INTEL SSDSA2CT040G3 4PC10362> at scbus3 target 0 lun 0 (ada3,pass3)
>
>
> And yes, I know the two hard disks have different sector sizes but I created the pool with an ashift of 12.
>
>
>
>
>
>
> Borja.
>
>
>
> _______________________________________________
> 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 Thu Nov 6 13:11:15 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 2635A2FD
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:11:15 +0000 (UTC)
Received: from mx2.paymentallianceintl.com (mx2.paymentallianceintl.com
[216.26.158.171])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(Client CN "mx2.paymentallianceintl.com",
Issuer "Go Daddy Secure Certification Authority" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id D04EEC3B
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:11:14 +0000 (UTC)
Received: from PAIMAIL.pai.local (paimail.pai.local [10.10.0.153])
by mx2.paymentallianceintl.com (8.14.5/8.13.8) with ESMTP id sA6DB6UV025969
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Thu, 6 Nov 2014 08:11:06 -0500 (EST)
(envelope-from mikej@paymentallianceintl.com)
Received: from PAICAS.pai.local (10.10.0.154) by PAIMAIL.pai.local
(10.10.0.153) with Microsoft SMTP Server (TLS) id 8.3.348.2; Thu, 6 Nov 2014
08:11:05 -0500
Received: from PAIMAIL.pai.local ([::1]) by PAICAS.pai.local ([::1]) with
mapi; Thu, 6 Nov 2014 08:11:06 -0500
From: Michael Jung <mikej@paymentallianceintl.com>
To: Borja Marcos <borjam@sarenet.es>, "freebsd-fs@FreeBSD.org Filesystems"
<freebsd-fs@freebsd.org>
Date: Thu, 6 Nov 2014 08:11:57 -0500
Subject: RE: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
Thread-Topic: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
Thread-Index: Ac/5sRQItqdiev8jQZih3ZjmegdNlgAEQbKA
Message-ID: <9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
In-Reply-To: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 13:11:15 -0000
What does smartctl -a /dev/ada1 show?
I see other posts via google showing that the SSDSA2CT040G3 has 512 byte ph=
ysical sectors (ashift 9)
=20
--mikej
=3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D
Device Model: INTEL SSDSA2CT040G3
Serial Number: CVPR140301GV040AGN
LU WWN Device Id: 5 001517 9596e4f5f
Firmware Version: 4PC10362
User Capacity: 40,020,664,320 bytes [40.0 GB]
Sector Size: 512 bytes logical/physical <--------------
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Sun May 13 14:36:47 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
-----Original Message-----
From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] On=
Behalf Of Borja Marcos
Sent: Thursday, November 06, 2014 6:01 AM
To: freebsd-fs@FreeBSD.org Filesystems
Subject: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
Hi,
I have noticed that ZIL creation _ignores_ the vfs.zfs.min_auto_ashift vari=
able. ZIL and cache on SSDs should use this variable in order to apply the =
optimum sector size on SSDs or so-called advanced format drives.
The system is:
root@splunk:/ # uname -a
FreeBSD splunk 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #12: Tue Nov 4 11:2=
2:48 CET 2014 root@splunk:/usr/obj/usr/src/sys/SPLUNK10 amd64
Example:
# sysctl vfs.zfs.min_auto_ashift=3D12
# zpool status //// Just a common mirror with two hard disks
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada0p3 ONLINE 0 0 0
ada2p3 ONLINE 0 0 0
errors: No known data errors
# zpool add rpool log ada1
# zpool status
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada0p3 ONLINE 0 0 0
ada2p3 ONLINE 0 0 0
logs
ada1 ONLINE 0 0 0
errors: No known data errors
///// There it is, but
# zdb | more
version: 5000
name: 'rpool'
state: 0
txg: 11738986
pool_guid: 18110845055860026534
hostid: 316898903
hostname: 'splunk'
vdev_children: 2
vdev_tree:
type: 'root'
id: 0
guid: 18110845055860026534
children[0]:
type: 'mirror'
id: 0
guid: 10858793804082837265
metaslab_array: 30
metaslab_shift: 32
ashift: 12
asize: 482922987520
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 10490056043151312448
path: '/dev/ada0p3'
phys_path: '/dev/ada0p3'
whole_disk: 1
DTL: 331
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 2441255496794840851
path: '/dev/ada2p3'
phys_path: '/dev/ada2p3'
whole_disk: 1
DTL: 252
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 3564614139316480036
path: '/dev/ada1'
id: 1
guid: 2441255496794840851
path: '/dev/ada2p3'
phys_path: '/dev/ada2p3'
whole_disk: 1
DTL: 252
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 3564614139316480036
path: '/dev/ada1'
phys_path: '/dev/ada1'
whole_disk: 1
metaslab_array: 0
metaslab_shift: 0
ashift: 9 <=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WRONG, SHOULDN'T IT =
BE 12??
asize: 40015757312
is_log: 1
create_txg: 11738986
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
If, however, I do the gnop trick,
# gnop create -S 4K ada1
# zpool add rpool log ada1.nop
# zpool status
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada0p3 ONLINE 0 0 0
ada2p3 ONLINE 0 0 0
logs
ada1.nop ONLINE 0 0 0
errors: No known data errors
this time our mirror has the ashift we wanted, 12.=20
children[1]:
type: 'disk'
id: 1
guid: 6487094506120463221
path: '/dev/ada1.nop'
phys_path: '/dev/ada1.nop'
whole_disk: 1
metaslab_array: 0
metaslab_shift: 0
ashift: 12
asize: 40015757312
is_log: 1
create_txg: 11739034
The disks I am playing with are:
# camcontrol devlist
<ST3500418AS CC38> at scbus0 target 0 lun 0 (ada0,pass0)
<INTEL SSDSA2CT040G3 4PC10362> at scbus1 target 0 lun 0 (ada1,pass1)
<ST500DM002-1BC142 JC4B> at scbus2 target 0 lun 0 (ada2,pass2)
<INTEL SSDSA2CT040G3 4PC10362> at scbus3 target 0 lun 0 (ada3,pass3)
And yes, I know the two hard disks have different sector sizes but I create=
d the pool with an ashift of 12.
Borja.
_______________________________________________
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"
=0A=
GoPai.com | Facebook.com/PaymentAlliance
=20
CONFIDENTIALITY NOTE: This message is intended only for the use
of the individual or entity to whom it is addressed and may=20
contain information that is privileged, confidential, and=20
exempt from disclosure under applicable law. If the reader=20
of this message is not the intended recipient, you are hereby=20
notified that any dissemination, distribution or copying=20
of this communication is strictly prohibited. If you have=20
received this transmission in error, please notify us by=20
telephone at (502) 212-4001 or notify us at PAI , Dept. 99,=20
6060 Dutchmans Lane, Suite 320, Louisville, KY 40205
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 13:27:38 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 CC03EA56
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:27:38 +0000 (UTC)
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
[209.85.212.174])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 64889DFE
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:27:38 +0000 (UTC)
Received: by mail-wi0-f174.google.com with SMTP id d1so1479061wiv.1
for <freebsd-fs@freebsd.org>; Thu, 06 Nov 2014 05:27:31 -0800 (PST)
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=0sG9UlPfaVdkX9oYjQvJxx9vhBN/pcAth3E3eE/Mc7E=;
b=UGDR9rX08pVImIBOeM+WgVwtpC747IrTda3Sn4dgGeMFy/50I+DVqSjaqp2vSKxMam
nsedKL++2JVJqjAS0XUo080Uluh/QDtUEuGJegMAL+vdAG9vhS5VznobE8s9I5+p/Q2l
jv0kSl5BvMtWXJAg9VR5LsPlsV+B/IFkHDn/OHCNueNn0Bs9W2by+Yj6Sa/1pBopuzFf
FbyB9+GeDNeorJJw+mECKc2CVRDZnoa0Plqmu92QxXv059vFS7jTe4x7eSab4b/fBd0o
2PrxQxARwUKP9CZRY/loCdXMwKMfm7UZFwwDEo60Y/wuDs3RbUiWF3WttnSYf//F7BqO
x4IQ==
X-Gm-Message-State: ALoCoQnrj/zNOxbf2nxAu5LIuVW62alc7DTdYA/3TmN42jmhlWZVhwZCBzR4jepeZBSmn26R/UZT
X-Received: by 10.181.13.20 with SMTP id eu20mr40530546wid.36.1415280451083;
Thu, 06 Nov 2014 05:27:31 -0800 (PST)
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 q2sm3386558wik.20.2014.11.06.05.27.29
for <freebsd-fs@freebsd.org>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 06 Nov 2014 05:27:30 -0800 (PST)
Message-ID: <545B76EF.6050709@multiplay.co.uk>
Date: Thu, 06 Nov 2014 13:26:07 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: freebsd-fs@freebsd.org
Subject: Re: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
In-Reply-To: <9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 13:27:38 -0000
That's not relevant as min when set should override the drives params
On 06/11/2014 13:11, Michael Jung wrote:
> What does smartctl -a /dev/ada1 show?
>
> I see other posts via google showing that the SSDSA2CT040G3 has 512 byte physical sectors (ashift 9)
>
> --mikej
>
> === START OF INFORMATION SECTION ===
> Device Model: INTEL SSDSA2CT040G3
> Serial Number: CVPR140301GV040AGN
> LU WWN Device Id: 5 001517 9596e4f5f
> Firmware Version: 4PC10362
> User Capacity: 40,020,664,320 bytes [40.0 GB]
> Sector Size: 512 bytes logical/physical <--------------
> Device is: Not in smartctl database [for details use: -P showall]
> ATA Version is: 8
> ATA Standard is: ATA-8-ACS revision 4
> Local Time is: Sun May 13 14:36:47 2012 CEST
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> -----Original Message-----
> From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] On Behalf Of Borja Marcos
> Sent: Thursday, November 06, 2014 6:01 AM
> To: freebsd-fs@FreeBSD.org Filesystems
> Subject: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
>
>
>
> Hi,
>
> I have noticed that ZIL creation _ignores_ the vfs.zfs.min_auto_ashift variable. ZIL and cache on SSDs should use this variable in order to apply the optimum sector size on SSDs or so-called advanced format drives.
>
> The system is:
> root@splunk:/ # uname -a
> FreeBSD splunk 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #12: Tue Nov 4 11:22:48 CET 2014 root@splunk:/usr/obj/usr/src/sys/SPLUNK10 amd64
>
>
>
> Example:
>
> # sysctl vfs.zfs.min_auto_ashift=12
>
> # zpool status //// Just a common mirror with two hard disks
> pool: rpool
> state: ONLINE
> scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
> config:
>
> NAME STATE READ WRITE CKSUM
> rpool ONLINE 0 0 0
> mirror-0 ONLINE 0 0 0
> ada0p3 ONLINE 0 0 0
> ada2p3 ONLINE 0 0 0
>
> errors: No known data errors
>
>
> # zpool add rpool log ada1
>
> # zpool status
> pool: rpool
> state: ONLINE
> scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
> config:
>
> NAME STATE READ WRITE CKSUM
> rpool ONLINE 0 0 0
> mirror-0 ONLINE 0 0 0
> ada0p3 ONLINE 0 0 0
> ada2p3 ONLINE 0 0 0
> logs
> ada1 ONLINE 0 0 0
>
> errors: No known data errors
>
>
> ///// There it is, but
>
> # zdb | more
> version: 5000
> name: 'rpool'
> state: 0
> txg: 11738986
> pool_guid: 18110845055860026534
> hostid: 316898903
> hostname: 'splunk'
> vdev_children: 2
> vdev_tree:
> type: 'root'
> id: 0
> guid: 18110845055860026534
> children[0]:
> type: 'mirror'
> id: 0
> guid: 10858793804082837265
> metaslab_array: 30
> metaslab_shift: 32
> ashift: 12
> asize: 482922987520
> is_log: 0
> create_txg: 4
> children[0]:
> type: 'disk'
> id: 0
> guid: 10490056043151312448
> path: '/dev/ada0p3'
> phys_path: '/dev/ada0p3'
> whole_disk: 1
> DTL: 331
> create_txg: 4
> children[1]:
> type: 'disk'
> id: 1
> guid: 2441255496794840851
> path: '/dev/ada2p3'
> phys_path: '/dev/ada2p3'
> whole_disk: 1
> DTL: 252
> create_txg: 4
> children[1]:
> type: 'disk'
> id: 1
> guid: 3564614139316480036
> path: '/dev/ada1'
> id: 1
> guid: 2441255496794840851
> path: '/dev/ada2p3'
> phys_path: '/dev/ada2p3'
> whole_disk: 1
> DTL: 252
> create_txg: 4
> children[1]:
> type: 'disk'
> id: 1
> guid: 3564614139316480036
> path: '/dev/ada1'
> phys_path: '/dev/ada1'
> whole_disk: 1
> metaslab_array: 0
> metaslab_shift: 0
> ashift: 9 <======================= WRONG, SHOULDN'T IT BE 12??
> asize: 40015757312
> is_log: 1
> create_txg: 11738986
> features_for_read:
> com.delphix:hole_birth
> com.delphix:embedded_data
>
>
>
> If, however, I do the gnop trick,
>
> # gnop create -S 4K ada1
> # zpool add rpool log ada1.nop
> # zpool status
>
> pool: rpool
> state: ONLINE
> scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 2014
> config:
>
> NAME STATE READ WRITE CKSUM
> rpool ONLINE 0 0 0
> mirror-0 ONLINE 0 0 0
> ada0p3 ONLINE 0 0 0
> ada2p3 ONLINE 0 0 0
> logs
> ada1.nop ONLINE 0 0 0
>
> errors: No known data errors
>
>
> this time our mirror has the ashift we wanted, 12.
>
> children[1]:
> type: 'disk'
> id: 1
> guid: 6487094506120463221
> path: '/dev/ada1.nop'
> phys_path: '/dev/ada1.nop'
> whole_disk: 1
> metaslab_array: 0
> metaslab_shift: 0
> ashift: 12
> asize: 40015757312
> is_log: 1
> create_txg: 11739034
>
>
>
> The disks I am playing with are:
>
> # camcontrol devlist
> <ST3500418AS CC38> at scbus0 target 0 lun 0 (ada0,pass0)
> <INTEL SSDSA2CT040G3 4PC10362> at scbus1 target 0 lun 0 (ada1,pass1)
> <ST500DM002-1BC142 JC4B> at scbus2 target 0 lun 0 (ada2,pass2)
> <INTEL SSDSA2CT040G3 4PC10362> at scbus3 target 0 lun 0 (ada3,pass3)
>
>
> And yes, I know the two hard disks have different sector sizes but I created the pool with an ashift of 12.
>
>
>
>
>
>
> Borja.
>
>
>
> _______________________________________________
> 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"
>
>
> GoPai.com | Facebook.com/PaymentAlliance
>
>
> CONFIDENTIALITY NOTE: This message is intended only for the use
> of the individual or entity to whom it is addressed and may
> contain information that is privileged, confidential, and
> exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby
> notified that any dissemination, distribution or copying
> of this communication is strictly prohibited. If you have
> received this transmission in error, please notify us by
> telephone at (502) 212-4001 or notify us at PAI , Dept. 99,
> 6060 Dutchmans Lane, Suite 320, Louisville, KY 40205
>
>
>
>
> _______________________________________________
> 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 Thu Nov 6 13:49:42 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 5CD4DD9C
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:49:42 +0000 (UTC)
Received: from cu01176a.smtpx.saremail.com (cu1176c.smtpx.saremail.com
[195.16.148.151])
(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 D0A2C81
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:49:40 +0000 (UTC)
Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11])
by proxypop02.sare.net (Postfix) with ESMTPSA id 57BB89DCD70;
Thu, 6 Nov 2014 14:41:06 +0100 (CET)
Subject: Re: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <545B715A.5060804@multiplay.co.uk>
Date: Thu, 6 Nov 2014 14:41:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E3EE484-9735-4BBD-9FB9-D52CC62C761A@sarenet.es>
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<545B715A.5060804@multiplay.co.uk>
To: Steven Hartland <killing@multiplay.co.uk>
X-Mailer: Apple Mail (2.1283)
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 13:49:42 -0000
On Nov 6, 2014, at 2:02 PM, Steven Hartland wrote:
> Your zdb output looks strange you have two children[1] entries are you =
sure your pool is not corrupt?
As far as I know, it's working fine, no need to summon the guardian of =
the lost children ;)
The extra "children" is the log device. I have verified it in a =
completely virgin (pun intended) system and indeed the log device
appears as a new "children" branch.
Let's see. This is the output without log or anything. Just a mirror.
# zpool status
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 5h55m with 0 errors on Wed Oct 29 23:26:03 =
2014
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada0p3 ONLINE 0 0 0
ada2p3 ONLINE 0 0 0
errors: No known data errors
#=20
# zdb|more
rpool:
version: 5000
name: 'rpool'
state: 0
txg: 11739617
pool_guid: 18110845055860026534
hostid: 316898903
hostname: 'splunk'
vdev_children: 1
vdev_tree:
type: 'root'
id: 0
guid: 18110845055860026534
children[0]:
type: 'mirror'
id: 0
guid: 10858793804082837265
metaslab_array: 30
metaslab_shift: 32
ashift: 12
asize: 482922987520
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 10490056043151312448
path: '/dev/ada0p3'
phys_path: '/dev/ada0p3'
whole_disk: 1
DTL: 331
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 2441255496794840851
path: '/dev/ada2p3'
phys_path: '/dev/ada2p3'
whole_disk: 1
DTL: 252
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
If I add a zil,
zdb|more
rpool:
version: 5000
name: 'rpool'
state: 0
txg: 11741324
pool_guid: 18110845055860026534
hostid: 316898903
hostname: 'splunk'
vdev_children: 2
vdev_tree:
type: 'root'
id: 0
guid: 18110845055860026534
children[0]:
type: 'mirror'
id: 0
guid: 10858793804082837265
metaslab_array: 30
metaslab_shift: 32
ashift: 12
asize: 482922987520
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 10490056043151312448
path: '/dev/ada0p3'
phys_path: '/dev/ada0p3'
whole_disk: 1
DTL: 331
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 2441255496794840851
path: '/dev/ada2p3'
phys_path: '/dev/ada2p3'
whole_disk: 1
DTL: 252
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 16071425471468142310
path: '/dev/ada1'
phys_path: '/dev/ada1'
whole_disk: 1
metaslab_array: 0
metaslab_shift: 0
ashift: 9
asize: 40015757312
is_log: 1
create_txg: 11741324
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 13:57:11 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 5D30CF90
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:57:11 +0000 (UTC)
Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com
[195.16.151.151])
(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 18D9519C
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 13:57:10 +0000 (UTC)
Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11])
by proxypop04.sare.net (Postfix) with ESMTPSA id D14C59DF033;
Thu, 6 Nov 2014 14:48:29 +0100 (CET)
Subject: Re: ZFS bug: Creating ZIL ignores vfs.zfs.min_auto_ashift
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
Date: Thu, 6 Nov 2014 14:48:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <49868BFD-A96A-4B60-B337-6BAD611BDCAA@sarenet.es>
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
To: Michael Jung <mikej@paymentallianceintl.com>
X-Mailer: Apple Mail (2.1283)
Cc: "freebsd-fs@FreeBSD.org Filesystems" <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 13:57:11 -0000
On Nov 6, 2014, at 2:11 PM, Michael Jung wrote:
> What does smartctl -a /dev/ada1 show?
>=20
> I see other posts via google showing that the SSDSA2CT040G3 has 512 =
byte physical sectors (ashift 9)
Different issue and I just stumbled upon it when testing this. The =
quirk provided for the SSD 320 drives,
{
/*
* Intel 320 Series SSDs
* 4k optimised & trim only works in 4k requests + 4k =
aligned
*/
{ T_DIRECT, SIP_MEDIA_FIXED, "*", "INTEL SSDSA2CW*", "*" =
},
/*quirks*/ADA_Q_4K
},
{
/*
* Intel 330 Series SSDs
* 4k optimised & trim only works in 4k requests + 4k =
aligned
*/
{ T_DIRECT, SIP_MEDIA_FIXED, "*", "INTEL SSDSC2CT*", "*" =
},
/*quirks*/ADA_Q_4K
},
doesn't match mine, hence they are not properly recognized.
Anyway, as Steve says, it's irrelevant. If I change the min_auto_ashift =
variable to 12 it should set the ashift to 12
regardless of the quirk detection.
I'll send the updated quirk to -scsi, but that's a different matter.
Borja.
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 14:58:52 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 CE857DE5
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 14:58:52 +0000 (UTC)
Received: from cu01176a.smtpx.saremail.com (cu1176c.smtpx.saremail.com
[195.16.148.151])
(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 670FBA30
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 14:58:51 +0000 (UTC)
Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11])
by proxypop02.sare.net (Postfix) with ESMTPSA id B0E989DC7F9;
Thu, 6 Nov 2014 15:58:47 +0100 (CET)
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift,
should be ZIL sets improper ashift with AHCI controllers
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <545B76EF.6050709@multiplay.co.uk>
Date: Thu, 6 Nov 2014 15:58:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
To: Steven Hartland <killing@multiplay.co.uk>
X-Mailer: Apple Mail (2.1283)
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 14:58:53 -0000
On Nov 6, 2014, at 2:26 PM, Steven Hartland wrote:
> That's not relevant as min when set should override the drives params
There is more to this than it seems, I just found more funny stuff.=20
MY CONCLUSION IS: when creating a ZIL device, it behaves differently =
depending on the disk controller. It works with SAS,
and it doesn't work with AHCI.
When using an AHCI controller, ZIL ignores *both* the 4K block quirk and =
the min_auto_ashift variables. Ashift is fixed to 9. It only
uses a different ashift when using a "nop" device. For example, I have =
tried with a 4 KB gnop device and this time it used the correct ashift, =
12.
When using a SAS controller, ZIL works perfectly with both.
Seems quite odd to me. I am not running exactly the same version on both =
machines (the one with AHCI controllers is running -STABLE
from three days ago) and the one with the SAS controller is running =
10.1-RC4. But the results should be the same.
I've added the relevant quirk to ata_da.c and the SSD is now
properly "quirked":
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <INTEL SSDSA2CT040G3 4PC10362> ATA-8 SATA 2.x device
ada1: Serial Number PEPR408501DV040AGN
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=3D0x1<4K>
But still something is wrong:
EXAMPLE ONE: AHCI controller, min_auto_ashift with the default value of =
9.
The log child, has the wrong ashift, 9, regardless of the 4K quirk.
children[1]:
type: 'disk'
id: 1
guid: 2447450905312007897
path: '/dev/ada1'
phys_path: '/dev/ada1'
whole_disk: 1
metaslab_array: 0
metaslab_shift: 0
ashift: 9
asize: 40015757312
is_log: 1
create_txg: 11741519
EXAMPLE 2: AHCI controller, raise min_auto_ashift to 12
# sysctl vfs.zfs.min_auto_ashift=3D12
vfs.zfs.min_auto_ashift: 9 -> 12
# zpool add rpool log ada1
And our log child still has the wrong ashift.
children[1]:
type: 'disk'
id: 1
guid: 17598938711972588792
path: '/dev/ada1'
phys_path: '/dev/ada1'
whole_disk: 1
metaslab_array: 0
metaslab_shift: 0
ashift: 9
asize: 40015757312
is_log: 1
create_txg: 11741560
EXAMPLE 3: Doing the same as example one, but using a SAS controller =
(mps).
I haven't changed the min_auto_ashift.
da3: <ATA Samsung SSD 840 BB0Q> Fixed Direct Access SCSI-6 device=20
da3: Serial Number S1D9NEADA08568E =20
da3: 600.000MB/s transfers
da3: Command Queueing enabled
da3: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da3: quirks=3D0x8<4K>
da1: <ATA Samsung SSD 840 BB0Q> Fixed Direct Access SCSI-6 device=20
da1: Serial Number S1D9NEADA08549F =20
da1: 600.000MB/s transfers
da1: Command Queueing enabled
da1: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da1: quirks=3D0x8<4K>
da2: <ATA Samsung SSD 840 BB0Q> Fixed Direct Access SCSI-6 device=20
da2: Serial Number S1D9NEADA08548T =20
da2: 600.000MB/s transfers
da2: Command Queueing enabled
da2: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da2: quirks=3D0x8<4K>
Now, we create a pool. I did this in two steps in order to reproduce my =
AHCI more accurately.
# zpool create sample mirror da2 da3
and add a log device
# zpool add sample log da1
And our log device uses the ashift...
children[1]:
type: 'disk'
id: 1
guid: 1327562712929751294
path: '/dev/da1'
phys_path: '/dev/da1'
whole_disk: 1
metaslab_array: 38
metaslab_shift: 33
ashift: 12 <=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D BINGO! 12!!
asize: 1000199946240
is_log: 1
create_txg: 7
EXAMPLE 4: Same hardware as before, but I have compiled a "dequirked" =
kernel. The Samsung 840 SSD is now
detected with 512 byte sectors.
# sysctl vfs.zfs.min_auto_ashift=3D12
# zpool create sample da2 da3
# zpool add sample log da1
# zdb
sample:
version: 5000
name: 'sample'
state: 0
txg: 10
pool_guid: 10244789911221894670
hostid: 1065071139
hostname: 'elibm'
vdev_children: 3
vdev_tree:
type: 'root'
id: 0
guid: 10244789911221894670
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 147759032286414284
path: '/dev/da2'
phys_path: '/dev/da2'
whole_disk: 1
metaslab_array: 37
metaslab_shift: 33
ashift: 12
asize: 1000199946240
is_log: 0
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 2632519121370708463
path: '/dev/da3'
phys_path: '/dev/da3'
whole_disk: 1
metaslab_array: 34
metaslab_shift: 33
ashift: 12
asize: 1000199946240
is_log: 0
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 10136980984141171426
path: '/dev/da1'
phys_path: '/dev/da1'
whole_disk: 1
metaslab_array: 39
metaslab_shift: 33
ashift: 12 =
<=3D=3D=3D=3D=3D=3D=3D=3D=3D 12, ashift for the log device
asize: 1000199946240
is_log: 1
create_txg: 8
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
root@elibm:~ #=20
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 20:26:25 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 EC202F43
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 20:26:25 +0000 (UTC)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com
[209.85.212.170])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 79D9C2BF
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 20:26:24 +0000 (UTC)
Received: by mail-wi0-f170.google.com with SMTP id r20so2570977wiv.3
for <freebsd-fs@freebsd.org>; Thu, 06 Nov 2014 12:26:17 -0800 (PST)
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
:cc:subject:references:in-reply-to:content-type;
bh=wpucUzsn8/2qLRv00HCe9zp3DV2xRVdnDZ0LIakz92c=;
b=ZJynnGEmLPj5ZjUchk8ApoDNlERAQHopD26L2ybt7CugXkZbAVzoxALdkRlYY2pUPe
mBc/+wiwsjERzVNhRxsJ0myBRwUFVTFJzMJo1J9l+9HM3m4ZB4WvSjoK5CbP++3QTQK6
XlKrQWW+ZYyHCQgCI8t/LLuzheqkvU4+1A8xuOltENpeC15UdZia6rYP6ODeeyqSMkVx
YVfWSSCU7FQihjKQP3Kam05IQFtcTqpjJ+O1n8aZbuUG7XchmasnpXtJPdJrI9HORYVm
SlUEEbMQ1hjEexWRSKcQQq/GGUqm+4WqtBnRy3L1ZlL3XaocVsdij31Jq2WzwP2emuHT
dP1Q==
X-Gm-Message-State: ALoCoQnEUxRHsM1Sz0t+HsOj3wtzE9PTSy+f/HGiPHgNXst4A+w5LnlpsfvCtqw0PZxNtG7C6SDi
X-Received: by 10.194.110.161 with SMTP id ib1mr9675733wjb.78.1415305577505;
Thu, 06 Nov 2014 12:26:17 -0800 (PST)
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 l10sm20823973wif.20.2014.11.06.12.26.16
for <multiple recipients>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 06 Nov 2014 12:26:16 -0800 (PST)
Message-ID: <545BD916.5020609@multiplay.co.uk>
Date: Thu, 06 Nov 2014 20:24:54 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Borja Marcos <borjam@sarenet.es>
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift, should
be ZIL sets improper ashift with AHCI controllers
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
<21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
In-Reply-To: <21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
Content-Type: multipart/mixed; boundary="------------040906050104080702050904"
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 20:26:26 -0000
This is a multi-part message in MIME format.
--------------040906050104080702050904
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Something very strange going on.
I have a boot pool (tank) and if I add ada1p3 (512b disk with
min_auto_ashift = 12) to it as a log device zdb reports its ashift as 9.
If I add the same device to another test pool (tpool) on the same
machine it gets ashift 12.
The attached dtrace script traces the calls and shows that
vdev_ashift_optimize is correctly called and that the ashift of the vdev
in both cases should be 12 according to the final vdev_config_generate call.
More debugging required
On 06/11/2014 14:58, Borja Marcos wrote:
> On Nov 6, 2014, at 2:26 PM, Steven Hartland wrote:
>
>> That's not relevant as min when set should override the drives params
> There is more to this than it seems, I just found more funny stuff.
>
> MY CONCLUSION IS: when creating a ZIL device, it behaves differently depending on the disk controller. It works with SAS,
> and it doesn't work with AHCI.
>
> When using an AHCI controller, ZIL ignores *both* the 4K block quirk and the min_auto_ashift variables. Ashift is fixed to 9. It only
> uses a different ashift when using a "nop" device. For example, I have tried with a 4 KB gnop device and this time it used the correct ashift, 12.
>
> When using a SAS controller, ZIL works perfectly with both.
>
> Seems quite odd to me. I am not running exactly the same version on both machines (the one with AHCI controllers is running -STABLE
> from three days ago) and the one with the SAS controller is running 10.1-RC4. But the results should be the same.
>
>
>
>
>
> I've added the relevant quirk to ata_da.c and the SSD is now
> properly "quirked":
>
> ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
> ada1: <INTEL SSDSA2CT040G3 4PC10362> ATA-8 SATA 2.x device
> ada1: Serial Number PEPR408501DV040AGN
> ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada1: Command Queueing enabled
> ada1: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C)
> ada1: quirks=0x1<4K>
>
>
> But still something is wrong:
>
> EXAMPLE ONE: AHCI controller, min_auto_ashift with the default value of 9.
>
> The log child, has the wrong ashift, 9, regardless of the 4K quirk.
>
> children[1]:
> type: 'disk'
> id: 1
> guid: 2447450905312007897
> path: '/dev/ada1'
> phys_path: '/dev/ada1'
> whole_disk: 1
> metaslab_array: 0
> metaslab_shift: 0
> ashift: 9
> asize: 40015757312
> is_log: 1
> create_txg: 11741519
>
>
> EXAMPLE 2: AHCI controller, raise min_auto_ashift to 12
>
> # sysctl vfs.zfs.min_auto_ashift=12
> vfs.zfs.min_auto_ashift: 9 -> 12
>
> # zpool add rpool log ada1
>
> And our log child still has the wrong ashift.
>
> children[1]:
> type: 'disk'
> id: 1
> guid: 17598938711972588792
> path: '/dev/ada1'
> phys_path: '/dev/ada1'
> whole_disk: 1
> metaslab_array: 0
> metaslab_shift: 0
> ashift: 9
> asize: 40015757312
> is_log: 1
> create_txg: 11741560
>
>
>
> EXAMPLE 3: Doing the same as example one, but using a SAS controller (mps).
> I haven't changed the min_auto_ashift.
>
> da3: <ATA Samsung SSD 840 BB0Q> Fixed Direct Access SCSI-6 device
> da3: Serial Number S1D9NEADA08568E
> da3: 600.000MB/s transfers
> da3: Command Queueing enabled
> da3: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
> da3: quirks=0x8<4K>
> da1: <ATA Samsung SSD 840 BB0Q> Fixed Direct Access SCSI-6 device
> da1: Serial Number S1D9NEADA08549F
> da1: 600.000MB/s transfers
> da1: Command Queueing enabled
> da1: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
> da1: quirks=0x8<4K>
> da2: <ATA Samsung SSD 840 BB0Q> Fixed Direct Access SCSI-6 device
> da2: Serial Number S1D9NEADA08548T
> da2: 600.000MB/s transfers
> da2: Command Queueing enabled
> da2: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
> da2: quirks=0x8<4K>
>
>
> Now, we create a pool. I did this in two steps in order to reproduce my AHCI more accurately.
>
> # zpool create sample mirror da2 da3
>
> and add a log device
>
> # zpool add sample log da1
>
> And our log device uses the ashift...
>
> children[1]:
> type: 'disk'
> id: 1
> guid: 1327562712929751294
> path: '/dev/da1'
> phys_path: '/dev/da1'
> whole_disk: 1
> metaslab_array: 38
> metaslab_shift: 33
> ashift: 12 <=============== BINGO! 12!!
> asize: 1000199946240
> is_log: 1
> create_txg: 7
>
>
> EXAMPLE 4: Same hardware as before, but I have compiled a "dequirked" kernel. The Samsung 840 SSD is now
> detected with 512 byte sectors.
>
> # sysctl vfs.zfs.min_auto_ashift=12
>
> # zpool create sample da2 da3
>
> # zpool add sample log da1
>
> # zdb
>
> sample:
> version: 5000
> name: 'sample'
> state: 0
> txg: 10
> pool_guid: 10244789911221894670
> hostid: 1065071139
> hostname: 'elibm'
> vdev_children: 3
> vdev_tree:
> type: 'root'
> id: 0
> guid: 10244789911221894670
> create_txg: 4
> children[0]:
> type: 'disk'
> id: 0
> guid: 147759032286414284
> path: '/dev/da2'
> phys_path: '/dev/da2'
> whole_disk: 1
> metaslab_array: 37
> metaslab_shift: 33
> ashift: 12
> asize: 1000199946240
> is_log: 0
> create_txg: 4
> children[1]:
> type: 'disk'
> id: 1
> guid: 2632519121370708463
> path: '/dev/da3'
> phys_path: '/dev/da3'
> whole_disk: 1
> metaslab_array: 34
> metaslab_shift: 33
> ashift: 12
> asize: 1000199946240
> is_log: 0
> create_txg: 4
> children[2]:
> type: 'disk'
> id: 2
> guid: 10136980984141171426
> path: '/dev/da1'
> phys_path: '/dev/da1'
> whole_disk: 1
> metaslab_array: 39
> metaslab_shift: 33
> ashift: 12 <========= 12, ashift for the log device
> asize: 1000199946240
> is_log: 1
> create_txg: 8
> features_for_read:
> com.delphix:hole_birth
> com.delphix:embedded_data
> root@elibm:~ #
>
--------------040906050104080702050904
Content-Type: text/plain; charset=windows-1252;
name="ashift.d"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="ashift.d"
#!/usr/sbin/dtrace -s
fbt::vdev_ashift_optimize:entry {
vd = (vdev_t *)arg0;
printf("vdev: %s, ashift: %d, physical_ashift: %d, top: %d, min: %d",
vd->vdev_path ? stringof(vd->vdev_path) : "n/a",
vd->vdev_ashift,
vd->vdev_physical_ashift,
vd == vd->vdev_top,
`zfs_min_auto_ashift
);
}
fbt::vdev_config_generate:entry {
vd = (vdev_t *)arg1;
printf("vdev: %s, ashift: %d, physical_ashift: %d, top: %d, min: %d",
vd->vdev_path ? stringof(vd->vdev_path) : "n/a",
vd->vdev_ashift,
vd->vdev_physical_ashift,
vd == vd->vdev_top,
`zfs_min_auto_ashift
);
}
fbt::vdev_ashift_optimize:return {
printf("%x", arg0);
}
--------------040906050104080702050904--
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 20:40:30 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 F2E7218C
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 20:40:30 +0000 (UTC)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 8680E679
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 20:40:29 +0000 (UTC)
Received: by mail-wg0-f46.google.com with SMTP id x13so2176751wgg.33
for <freebsd-fs@freebsd.org>; Thu, 06 Nov 2014 12:40:28 -0800 (PST)
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
:cc:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=WU4wqs8WdUvXdl3XKheeVpiuhCyAJ/k27URRCC9MSUs=;
b=MFDw9OKDL2SAIbuCHQTqDMUpIBsVjU9kswyS1e2hdNbT/IG9Am9a/fBPJ69FY6o3SH
VhVnPTSTgSS8QZhwCS9+dRzfmaLO7674JmKDT/R1ywO0vtGrHVNWe7y9lMWV5FCJ2tub
omugN/ZQR6GMqtnMwh7HW9A3OStkLsrNXFx+6T7EvJq6LQWlmZzGzngvFsxQgTjxT4bj
CtlJ+Ohmy6JnZeHzjc0I7lFKvUKELyr0t7UUeT7/xeoVpHu6lrmQ/CwfJAHE8OrX2ttL
M51OeBIzwxfo+fS8e6wQRgP3EGxW00CA8+9OCZZO4yKxOTCobA0cZdvno9OqaxEkq6lc
mbUA==
X-Gm-Message-State: ALoCoQn5cSVUJs+dJH/Govz1Xw6uz4zsE+/FRJ66zyDbf6ktgrLhsjEfXbELh3OCzb1BI2+qPeOW
X-Received: by 10.194.89.161 with SMTP id bp1mr9685650wjb.114.1415306428078;
Thu, 06 Nov 2014 12:40:28 -0800 (PST)
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 bj7sm9160872wjc.33.2014.11.06.12.40.26
for <multiple recipients>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 06 Nov 2014 12:40:27 -0800 (PST)
Message-ID: <545BDC69.9030903@multiplay.co.uk>
Date: Thu, 06 Nov 2014 20:39:05 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Borja Marcos <borjam@sarenet.es>
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift, should
be ZIL sets improper ashift with AHCI controllers
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
<21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
In-Reply-To: <21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 20:40:31 -0000
What does the following report for you when zdb on its own reports an
incorrect ashift of 9?
zdb -l /dev/<your log device> | grep ashift
Here that reports the correct ashift, so I'm thinking that zdb on its
own might be incorrectly reporting the ashift for some reason.
Regards
Steve
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 21:12:21 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 952F7CE7
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 21:12:21 +0000 (UTC)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 28B35A8C
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 21:12:20 +0000 (UTC)
Received: by mail-wg0-f46.google.com with SMTP id x13so2235136wgg.33
for <freebsd-fs@freebsd.org>; Thu, 06 Nov 2014 13:12:19 -0800 (PST)
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
:cc:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=5ayiX6WcR8Mx7gCVjfP9RfRUsCt+F8qT2VY4PmVNgz0=;
b=MUmw9jQXLLr7bx6a1qwV5pZp5q/d8Uo9V8jv9fzKRI4gxtB/CYVCFOfFQQhzpq0DAT
mw+bdbRy1R0IOViUibW4v3z4xPeGBOHTDlR58wwIUwhC7n+41xVh1GUtDVTUCGZV6sHN
SpKZm0c6KDe1ZlU4Zez+DqhcI1+o8RKhtiq24wV2LkBrQxP+KuG8Psf/qIxldlmr6Tkk
WNPjB2cc09DXj3BCgs4x2jFvclJk8UCCmn6DpODGnLbCDrsitr0tMfi/6KeLGQIkkD/2
x/SVY1iPE8AMzyUnRi6cRVK9lp56eREoPlWh1ki3SEndzFlDYZYSUFilkhCMDTbN+oz/
JffQ==
X-Gm-Message-State: ALoCoQm3jUnRqXDIslNqLcaURpKIYzZEYN/Lh8aEH2bgzMDWAGSze8+4jY1gmRjQvYtV7kg0zeDe
X-Received: by 10.194.79.201 with SMTP id l9mr9505309wjx.59.1415308339432;
Thu, 06 Nov 2014 13:12:19 -0800 (PST)
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 gw6sm9747768wib.8.2014.11.06.13.12.18
for <multiple recipients>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 06 Nov 2014 13:12:18 -0800 (PST)
Message-ID: <545BE3E0.4030203@multiplay.co.uk>
Date: Thu, 06 Nov 2014 21:10:56 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Borja Marcos <borjam@sarenet.es>
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift, should
be ZIL sets improper ashift with AHCI controllers
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
<21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
In-Reply-To: <21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 21:12:21 -0000
On 06/11/2014 14:58, Borja Marcos wrote:
> On Nov 6, 2014, at 2:26 PM, Steven Hartland wrote:
>
>> That's not relevant as min when set should override the drives params
> There is more to this than it seems, I just found more funny stuff.
>
> MY CONCLUSION IS: when creating a ZIL device, it behaves differently depending on the disk controller. It works with SAS,
> and it doesn't work with AHCI.
>
Ok narrowed down the issue, looks like cache file generation is where
the issue is, possibly a race condition.
If you run the following then rerun your zdb I suspect you'll get the
right results (ashift: 12)
zpool set cachefile='' <pool>
Alternatively you can run the following to display real pool config vs
that which is in the cache file:
zdb -C <pool>
Regards
Steve
From owner-freebsd-fs@FreeBSD.ORG Thu Nov 6 21:51:09 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 C9696964
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 21:51:09 +0000 (UTC)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com
[IPv6:2a00:1450:4010:c04::232])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 46580F4E
for <freebsd-fs@freebsd.org>; Thu, 6 Nov 2014 21:51:09 +0000 (UTC)
Received: by mail-lb0-f178.google.com with SMTP id f15so1845629lbj.23
for <freebsd-fs@freebsd.org>; Thu, 06 Nov 2014 13:51:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphix.com; s=google;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=aMCir4NGzxDciaxwqv0HKsKd7hoPEUb+CFseq1GAKCA=;
b=IYJau1/TwSftMlGM/ttzx5YNN8+/2vUSla1IHv/QSMObg/mQ1HKobFtYJGCdgE4jn/
vFT/+hg5222RNV+BXTrT+mDyS5pMR+chYU475la5jeo5qKN6Dn+W7oYxkum468fkj0N7
m7c0TejIg+CKeTzwvrKD+FQdZIEGPW2ynJfk8=
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
:content-type;
bh=aMCir4NGzxDciaxwqv0HKsKd7hoPEUb+CFseq1GAKCA=;
b=IEXac4pryhymiYZi3kJauV96b6ByEkoVEGRkC0lbUlbdKG8f4+pf+l317mhjBxt4H6
9mTUdVanZFB5jwclC8yveYQjHfHNuE5YBjwd4JZv20YZrbghEgYb28DK4WDrcZZIY5md
briDAv8XMUtNd1B+GA8qo5LOPXRO8m12ZqS6Vafbt1ra/zJdAyuih33NzBNOSu/PJkAS
ivyOd02M+/V7WVl9ztfLxbz7m8c1hDyNgAJglzYm+4rHVK1Mu7whjnSfDOeiI/WG6R0h
getJTlzaPrJaE4Ryl5tluzsAVdEhiz2XbCpT1yjWZTDmzvlb10rjBUbnwzVlnaKDCUr7
5Iuw==
X-Gm-Message-State: ALoCoQncMr4CEqzzxVwF8AVeMevOHx5AXB/QFRC6a96vG5OHwwueQbgcf+MzffAAo0U/vZ0ddmke
MIME-Version: 1.0
X-Received: by 10.152.4.229 with SMTP id n5mr4985378lan.1.1415310667317; Thu,
06 Nov 2014 13:51:07 -0800 (PST)
Received: by 10.25.155.77 with HTTP; Thu, 6 Nov 2014 13:51:07 -0800 (PST)
Date: Thu, 6 Nov 2014 13:51:07 -0800
Message-ID: <CAJjvXiEvo7n2pZGoEmjdSgcn0UdNsE2us5N65pB0zLC4V_+RNg@mail.gmail.com>
Subject: webcast: OpenZFS Developer Summit on Monday
From: Matthew Ahrens <mahrens@delphix.com>
To: developer <developer@open-zfs.org>, illumos-zfs <zfs@lists.illumos.org>,
freebsd-fs <freebsd-fs@freebsd.org>,
zfs-discuss <zfs-discuss@zfsonlinux.org>,
"admin@open-zfs.org" <admin@open-zfs.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 21:51:10 -0000
The 2nd annual OpenZFS Developer Summit will be held next Monday and
Tuesday! I'm looking forward to seeing many of you there. For those who
can't make it, there will be a live webcast of Monday's presentations,
starting at 9:30AM PST.
We have a huge variety of short talks, with more than 20 speakers and most
talks being 15 minutes or less. Tune in for everything from high-level
overviews, to deep dives into upcoming features, and practical explanations
of how OpenZFS is used in products.
The webcast, schedule, and all info is available on the webpage:
http://www.open-zfs.org/wiki/OpenZFS_Developer_Summit_2014
--matt
p.s. If you miss the webcast, we'll post slides and recorded video later in
the week -- check the website or developer@open-zfs.org; I won't spam all
these lists again :-)
From owner-freebsd-fs@FreeBSD.ORG Fri Nov 7 07:31:08 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 0E1CE4E6
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 07:31:08 +0000 (UTC)
Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com
[195.16.151.151])
(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 BD52566D
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 07:31:07 +0000 (UTC)
Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11])
by proxypop04.sare.net (Postfix) with ESMTPSA id C22169DF17A;
Fri, 7 Nov 2014 08:31:03 +0100 (CET)
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift,
should be ZIL sets improper ashift with AHCI controllers
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <545BE3E0.4030203@multiplay.co.uk>
Date: Fri, 7 Nov 2014 08:31:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <757B9039-8DF0-4E6A-A036-82A2143D7F45@sarenet.es>
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
<21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
<545BE3E0.4030203@multiplay.co.uk>
To: Steven Hartland <killing@multiplay.co.uk>
X-Mailer: Apple Mail (2.1283)
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 07:31:08 -0000
On Nov 6, 2014, at 10:10 PM, Steven Hartland wrote:
> On 06/11/2014 14:58, Borja Marcos wrote:
> Ok narrowed down the issue, looks like cache file generation is where =
the issue is, possibly a race condition.
Hmm and you mentioned a boot pool and a not boot pool. Certainly, that's =
another difference :/ I wrongly blamed the
controlled difference because I directly suspected the quirks mechanism.
> If you run the following then rerun your zdb I suspect you'll get the =
right results (ashift: 12)
> zpool set cachefile=3D'' <pool>
>=20
> Alternatively you can run the following to display real pool config vs =
that which is in the cache file:
> zdb -C <pool>
Let's see
# zpool add rpool log ada1
# zdb|fgrep ashift
ashift: 12
ashift: 9
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <INTEL SSDSA2CT040G3 4PC10362> ATA-8 SATA 2.x device
ada1: Serial Number PEPR408501DV040AGN
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=3D0x1<4K>
And now,
# zdb -C rpool|fgrep ashift
ashift: 12
ashift: 12
You are right!
This time I had not altered min_auto_ashift but I had added a quirk to =
ata_da.c. So it
correctly used the quirk sector size to adjust ashift.=20
Seems the bug should be "improper cache file generation for a pool used =
for boot". I'll
see if I can run some more tests.
Thanks!
Borja.
From owner-freebsd-fs@FreeBSD.ORG Fri Nov 7 08:20:31 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 0D81DB0F
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 08:20:31 +0000 (UTC)
Received: from mail.slu.se (tmgext2-1.slu.se [77.235.224.51])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 96E0FB9C
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 08:20:29 +0000 (UTC)
Received: from Exchange2-2.slu.se (130.238.96.155) by Tmg2-1.slu.se
(130.238.96.151) with Microsoft SMTP Server (TLS) id 14.3.210.2; Fri, 7 Nov
2014 09:20:21 +0100
Received: from Exchange2-1.slu.se ([130.238.96.154]) by exchange2-2
([130.238.96.155]) with mapi id 14.03.0210.002; Fri, 7 Nov 2014 09:20:21
+0100
From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= <Karli.Sjoberg@slu.se>
To: "erik@tefre.com" <erik@tefre.com>
Subject: Re: Differences in memory handling on systems with/out cache drives
Thread-Topic: Differences in memory handling on systems with/out cache drives
Thread-Index: AQHP+mOrL1Ns2O6BG0+LXpqkrsQqEw==
Date: Fri, 7 Nov 2014 08:20:20 +0000
Message-ID: <5F9E965F5A80BC468BE5F40576769F099DF8DDCD@exchange2-1>
References: <5F9E965F5A80BC468BE5F40576769F099DF87F57@exchange2-1>
<5F9E965F5A80BC468BE5F40576769F099DF87FBB@exchange2-1>
<545A43EB.7070603@tefre.com>
In-Reply-To: <545A43EB.7070603@tefre.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [77.235.228.32]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>,
"karl@fs.denninger.net" <karl@fs.denninger.net>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 08:20:31 -0000
T24gV2VkLCAyMDE0LTExLTA1IGF0IDE2OjM2ICswMTAwLCBFcmlrIFN0aWFuIFRlZnJlIHdyb3Rl
Ogo+IE9uIDA1LiBub3YuIDIwMTQgMDk6NTMsIEthcmxpIFNqw7ZiZXJnIHdyb3RlOgo+ID4gT24g
V2VkLCAyMDE0LTExLTA1IGF0IDA4OjQ0ICswMDAwLCBLYXJsaSBTasO2YmVyZyB3cm90ZToKPiA+
PiBIZXkgYWxsIQo+ID4+Cj4gPj4gU3RpbGwgaW52ZXN0aWdhdGluZyB0aGUgaW50ZXJtaXR0ZW50
IGxvY2t1cHMgd2UgYXJlIGV4cGVyaWVuY2luZyBvbiBvdXIKPiA+PiBzdG9yYWdlIHN5c3RlbXMg
YW5kIGhhdmUgc3RhcnRlZCB0byBjb21wYXJlIG1lbW9yeSBncmFwaHMgZnJvbSBvdXIKPiA+PiBH
cmFwaGl0ZSBtb25pdG9yaW5nIHN5c3RlbS4gV2hhdMK0cyBpbnRlcmVzdGluZyBhYm91dCB0d28g
b2Ygb3VyIHN5c3RlbXMKPiA+PiBpcyB0aGF0IHRoZXkgYm90aCBoYXZlIHRoZSBzYW1lIGFtb3Vu
dCBvZiBSQU07IDMyIEdCLiBCdXQgb24gb25lIG9mCj4gPj4gdGhlbSwgSSBoYXZlICJ6cG9vbCBy
ZW1vdmUiJ2QgdGhlIGNhY2hlIGRyaXZlcyBmcm9tIHRoZSBwb29sIGFuZCBoYXZlCj4gPj4gYmVl
biBhYmxlIHRvIHN0dWR5IGhvdyBkaWZmZXJlbnQgdGhlaXIgbWVtb3J5IGdyYXBocyBub3cgbG9v
ayBsaWtlLgo+ID4+Cj4gPj4gQWxzbyB3b3J0aCBub3RpbmcgaXMgdGhhdCB0aGUgY2FjaGUtbGVz
cyBzeXN0ZW0gbmVhcmx5IGhhdmVuwrR0IHN3YXBwZWQKPiA+PiBhdCBhbGwgKDExMTJLKSBzaW5j
ZSB0aGUgbGFzdCBzdGFsbCAyMCBkYXlzIGFnbywgd2hpbGUgdGhlIG90aGVyIHN5c3RlbQo+ID4+
IGhhcyBzd2FwcGVkIDc4IE1CIGR1cmluZyBpdMK0cyA0OCBkYXlzIG9mIHVwdGltZS4KPiA+Pgo+
ID4+IEnCtHZlIGF0dGFjaGVkIGJvdGggc2NyZWVuc2hvdHMgZnJvbSB0aGUgdHdvIHN5c3RlbXMs
IHdpdGgtIGFuZCB3aXRob3V0Cj4gPj4gY2FjaGUgZHJpdmVzLCBkaXNwbGF5aW5nIGEgcGVyaW9k
IG9mIDEyIGhvdXJzLgo+ID4+Cj4gPj4gV2hhdMK0cyBtb3N0IG5vdGFibGUgYXJlIHRoZSBjaGFy
YWN0ZXJpc3RpYyBjdXRzIHRoYXQgaGFwcGVuIG9uIHRoZQo+ID4+IGNhY2hlLWxlc3Mgc3lzdGVt
IHdoZW4gWkZTIGdvZXMgaW4gYW5kIGV2aWN0cyBibG9ja3MgZnJvbSBBUkMgdGhhdCBzaG93cwo+
ID4+IGFzIGEgZGVjcmVhc2UgaW4gIndpcmVkIiBhbmQgaW5jcmVhc2UgaW4gImZyZWUiLCB0aGF0
IGp1c3QgZG9lc27CtHQKPiA+PiBoYXBwZW4vbG9va3MgZGlmZmVyZW50IGluIHRoZSBzeXN0ZW0g
d2l0aCBjYWNoZSBkcml2ZSBjb25maWd1cmVkIGluIHRoZQo+ID4+IHBvb2wuCj4gPj4KPiA+PiBX
aGF0wrRzIHlvdXIgdGFrZSBvbiB0aGlzPyBBcmUgd2UgaGl0dGluZyBidWc6IDE4NzU5NCBwZXJo
YXBzPyBIb3cgY2FuIHdlCj4gPj4ga25vdz8KPiBUYWtlIGEgbG9vayBhdCB0aGUgcmVjZW50IHRo
cmVhZCBvbiBmcmVlYnNkLXN0YWJsZUAsIHN1YmplY3QgIkFSQyBzaXplIAo+IGxpbWl0Ii4gUG9z
c2libHkgcmVsYXRlZCBpc3N1ZXMgaGF2ZSBiZWVuIHBhdGNoZWQgaW4gc3RhYmxlLzEwLCB0aGUg
Cj4gbWFpbGluZyBsaXN0IHRocmVhZCBpbmNsdWRlcyBhIHBhdGNoIGZvciByZWxlbmcvMTAuMS4K
ClRoYW5rcyEgSSBsb29rZWQgYXQgaXQgYW5kIHNhdyB0aGF0IHRoYXTCtHMgb25lIHRoYXTCtHMg
Z29pbmcgdG8gYmUgdXNlZApmb3IgMTAuMVsxXSBhbmQgdGhlIHBhdGNoIHJlZmVycmVkIHRvIGlz
IHRoZSBzYW1lIGFzIHRoZSBvbmUgZGV2ZWxvcGVkCmZvciBidWcgMTg3NTk0WzJdLCB3aGljaCBz
dGlsbCBoYXMgc3RhdHVzICJJbiBEaXNjdXNzaW9uIi4gVGhlIHBhdGNoCnJlYWxseSBzaG91bGQg
YmUgdmVyaWZpZWQgYnkgT1AgdGhlcmUgYmVmb3JlIGlzc3VlIGlzIF9yZWFsbHlfIGRlY2xhcmVk
CnJlc29sdmVkLgoKQEthcmwKRG8geW91IGhhdmUgYW55IGNoYW5jZSBvZiB2ZXJpZnlpbmcgdGhp
cywgYXMgeW91IHdlcmUgdGhlIG9uZSB0aGF0IGZpcnN0CnJlcG9ydGVkIGFib3V0IGl0PyBJIHdv
dWxkIHBlcnNvbmFsbHkgZmVlbCBzbyBtdWNoIGJldHRlciBrbm93aW5nIHdlIGNhbgpmaW5hbGx5
IHJpZCBvdXJzZWx2ZXMgb2YgdGhpcyBtZW5hY2UgaW4gMTAuMTopCgpbMV06aHR0cHM6Ly9saXN0
cy5mcmVlYnNkLm9yZy9waXBlcm1haWwvZnJlZWJzZC1zdGFibGUvMjAxNC1Ob3ZlbWJlci8wODA4
OTQuaHRtbApbMl06aHR0cHM6Ly9idWdzLmZyZWVic2Qub3JnL2J1Z3ppbGxhL3Nob3dfYnVnLmNn
aT9pZD0xODc1OTQjYzE4OQoKCi0tIAoKTWVkIFbDpG5saWdhIEjDpGxzbmluZ2FyCgotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tCkthcmxpIFNqw7ZiZXJnClN3ZWRpc2ggVW5pdmVyc2l0eSBvZiBBZ3Jp
Y3VsdHVyYWwgU2NpZW5jZXMgQm94IDcwNzkgKFZpc2l0aW5nIEFkZHJlc3MKS3JvbsOlc3bDpGdl
biA4KQpTLTc1MCAwNyBVcHBzYWxhLCBTd2VkZW4KUGhvbmU6ICArNDYtKDApMTgtNjcgMTUgNjYK
a2FybGkuc2pvYmVyZ0BzbHUuc2UK
From owner-freebsd-fs@FreeBSD.ORG Fri Nov 7 09:31:33 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 EB5DBC50
for <freebsd-fs@FreeBSD.org>; Fri, 7 Nov 2014 09:31:33 +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 D21E437A
for <freebsd-fs@FreeBSD.org>; Fri, 7 Nov 2014 09:31:33 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA79VXVk019987
for <freebsd-fs@FreeBSD.org>; Fri, 7 Nov 2014 09:31:33 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 61503] [smbfs] mount_smbfs does not work as non-root
Date: Fri, 07 Nov 2014 09:31:33 +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: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: mazhe@alkumuna.eu
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-61503-3630-MSUYX22mnu@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-61503-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-61503-3630@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 09:31:34 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=61503
Matthieu Volat <mazhe@alkumuna.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mazhe@alkumuna.eu
--- Comment #2 from Matthieu Volat <mazhe@alkumuna.eu> ---
Wow, fumbling on a 10 year old bug, did ever somebody proposed a fix for that
problem?
--
You are receiving this mail because:
You are the assignee for the bug.
From owner-freebsd-fs@FreeBSD.ORG Fri Nov 7 09:48:16 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 97EAE202
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 09:48:16 +0000 (UTC)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com
[209.85.212.170])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 272D46AB
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 09:48:15 +0000 (UTC)
Received: by mail-wi0-f170.google.com with SMTP id r20so3799397wiv.1
for <freebsd-fs@freebsd.org>; Fri, 07 Nov 2014 01:48:13 -0800 (PST)
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
:cc:subject:references:in-reply-to:content-type;
bh=nMYsiNmyvMmvdwYxBmrBB726xP5+jfw4aK55eywcgxA=;
b=IqNjCF5YTjcNWCt2jwGbKR/F5dmzy7rWswLHeC+GaHT1xg7YDedZO7M7/TdXk0POOw
Ew3fbkulV/b0nyrdE0Vvp7sPlTJ67E8tOWI8ciS9LgxS9GGAZjCabAOFV4dTC+QtRySr
Ii3lltPnad/1j0mpJ0LoJQk9BO14OFhOUb/H5I9yTGTnAjBggoYAvdyV9M5CiBLWzQhT
mMKLsqBe13ednwMBVgjcNwVOtyBWb9z0S+7VbiC2xEoR7SQ2Lj3W5NF0U74qWq3ZPgQg
/vlhWxv2GJdq7roXJOCXcsN927Z1sL/KtK1SR5l1wfrxwjVHVrR3w1hWKCsQwEm+iwkr
bmjQ==
X-Gm-Message-State: ALoCoQksde3dPXjCo1I0UASkTO9tLsbt08t59081zValPaFS7bBT6WY968yd1Gx0HwAeAIuzFgg9
X-Received: by 10.180.187.44 with SMTP id fp12mr3402714wic.72.1415353693266;
Fri, 07 Nov 2014 01:48:13 -0800 (PST)
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 hu3sm11103379wjb.17.2014.11.07.01.48.12
for <multiple recipients>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 07 Nov 2014 01:48:12 -0800 (PST)
Message-ID: <545C9552.30207@multiplay.co.uk>
Date: Fri, 07 Nov 2014 09:48:02 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Borja Marcos <borjam@sarenet.es>
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift, should
be ZIL sets improper ashift with AHCI controllers
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
<21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
<545BE3E0.4030203@multiplay.co.uk>
<757B9039-8DF0-4E6A-A036-82A2143D7F45@sarenet.es>
In-Reply-To: <757B9039-8DF0-4E6A-A036-82A2143D7F45@sarenet.es>
Content-Type: multipart/mixed; boundary="------------040004010503080103060804"
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 09:48:16 -0000
This is a multi-part message in MIME format.
--------------040004010503080103060804
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
On 07/11/2014 07:31, Borja Marcos wrote:
> snip...
>
> You are right!
>
> This time I had not altered min_auto_ashift but I had added a quirk to ata_da.c. So it
> correctly used the quirk sector size to adjust ashift.
>
> Seems the bug should be "improper cache file generation for a pool used for boot". I'll
> see if I can run some more tests.
>
I believe the attached is the correct fix, but I've asked upstream as
this test was explicitly added ages ago.
Regards
Steve
--------------040004010503080103060804
Content-Type: text/plain; charset=windows-1252;
name="zpool-cache.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="zpool-cache.patch"
Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_config.c
===================================================================
--- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_config.c (revision 274189)
+++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_config.c (working copy)
@@ -536,8 +536,7 @@ spa_config_update(spa_t *spa, int what)
/*
* Update the global config cache to reflect the new mosconfig.
*/
- if (!spa->spa_is_root)
- spa_config_sync(spa, B_FALSE, what != SPA_CONFIG_UPDATE_POOL);
+ spa_config_sync(spa, B_FALSE, what != SPA_CONFIG_UPDATE_POOL);
if (what == SPA_CONFIG_UPDATE_POOL)
spa_config_update(spa, SPA_CONFIG_UPDATE_VDEVS);
--------------040004010503080103060804--
From owner-freebsd-fs@FreeBSD.ORG Fri Nov 7 12:01:22 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 CA0B43C6
for <freebsd-fs@FreeBSD.org>; Fri, 7 Nov 2014 12:01:22 +0000 (UTC)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
by mx1.freebsd.org (Postfix) with ESMTP id 1DEB583D
for <freebsd-fs@FreeBSD.org>; Fri, 7 Nov 2014 12:01:21 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
[212.40.38.100])
by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA25642;
Fri, 07 Nov 2014 14:03:13 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
id 1XmiEB-000Cab-9I; Fri, 07 Nov 2014 14:01:19 +0200
Message-ID: <545CB43E.6040901@FreeBSD.org>
Date: Fri, 07 Nov 2014 13:59:58 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Steven Hartland <killing@multiplay.co.uk>, Borja Marcos <borjam@sarenet.es>
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift, should
be ZIL sets improper ashift with AHCI controllers
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
<21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
<545BE3E0.4030203@multiplay.co.uk>
<757B9039-8DF0-4E6A-A036-82A2143D7F45@sarenet.es>
<545C9552.30207@multiplay.co.uk>
In-Reply-To: <545C9552.30207@multiplay.co.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@FreeBSD.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 12:01:22 -0000
On 07/11/2014 11:48, Steven Hartland wrote:
>
> On 07/11/2014 07:31, Borja Marcos wrote:
>> snip...
>>
>> You are right!
>>
>> This time I had not altered min_auto_ashift but I had added a quirk to
>> ata_da.c. So it
>> correctly used the quirk sector size to adjust ashift.
>>
>> Seems the bug should be "improper cache file generation for a pool used for
>> boot". I'll
>> see if I can run some more tests.
>>
> I believe the attached is the correct fix, but I've asked upstream as this test
> was explicitly added ages ago.
It could be that this problem is of no interest / relevance to the illumos
upstream as they have more restrictions on how a root pool can be configured. I
am not sure if they allow slog devices for root pools.
--
Andriy Gapon
From owner-freebsd-fs@FreeBSD.ORG Fri Nov 7 13:31:20 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 B3279F56
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 13:31:20 +0000 (UTC)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com
[209.85.212.179])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 3F79C382
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 13:31:19 +0000 (UTC)
Received: by mail-wi0-f179.google.com with SMTP id h11so4560216wiw.12
for <freebsd-fs@freebsd.org>; Fri, 07 Nov 2014 05:31:12 -0800 (PST)
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
:cc:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=r7+7dh6eo1UubEJieWcdIzDXuM2oUvyO5FWsWRMDD+8=;
b=K/B7hJmeDvwuwlJSqX8pK8Xxv2ERcIbJRKmu0PXpJ5YP5q5rk5PMyVpqDbdz25rTBr
NF65s21HK3RjHe+JSStUSi9OLq2YbVoPYN7hmI6SEGnLoWimT/HO+iYFYij+UAXm8EjJ
8bh609diryJZLZlazPbv/mmH4tWUDxu48gkTxy3OlNwtOyrDWMiqtFiwBGlxVyHFmFii
OfW+fB1FS5ukBFnAmSimpQ8Cg4e1TZYw5HfXv4mH7d2OsXQIemZAzubAFJ0GRiCyQTIT
ByYrxCM2FC5rjZiufF97cwnTsPbUeMkNbCoQ82gnmmireoQl58QET09tt/ocugr1GObF
fiIQ==
X-Gm-Message-State: ALoCoQmyP7IGexG+URLNZzhb9mJu7y3J4yUZA8BOTBH9hWhB8bLGiFn8OViyR6ND5KjQm1Qlj8W3
X-Received: by 10.180.74.201 with SMTP id w9mr5045775wiv.17.1415367071922;
Fri, 07 Nov 2014 05:31:11 -0800 (PST)
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 dc8sm2076866wib.7.2014.11.07.05.31.09
for <multiple recipients>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 07 Nov 2014 05:31:10 -0800 (PST)
Message-ID: <545CC99B.1010302@multiplay.co.uk>
Date: Fri, 07 Nov 2014 13:31:07 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Andriy Gapon <avg@FreeBSD.org>, Borja Marcos <borjam@sarenet.es>
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift, should
be ZIL sets improper ashift with AHCI controllers
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
<21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
<545BE3E0.4030203@multiplay.co.uk>
<757B9039-8DF0-4E6A-A036-82A2143D7F45@sarenet.es>
<545C9552.30207@multiplay.co.uk> <545CB43E.6040901@FreeBSD.org>
In-Reply-To: <545CB43E.6040901@FreeBSD.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@FreeBSD.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 13:31:20 -0000
On 07/11/2014 11:59, Andriy Gapon wrote:
> On 07/11/2014 11:48, Steven Hartland wrote:
>> On 07/11/2014 07:31, Borja Marcos wrote:
>>> snip...
>>>
>>> You are right!
>>>
>>> This time I had not altered min_auto_ashift but I had added a quirk to
>>> ata_da.c. So it
>>> correctly used the quirk sector size to adjust ashift.
>>>
>>> Seems the bug should be "improper cache file generation for a pool used for
>>> boot". I'll
>>> see if I can run some more tests.
>>>
>> I believe the attached is the correct fix, but I've asked upstream as this test
>> was explicitly added ages ago.
> It could be that this problem is of no interest / relevance to the illumos
> upstream as they have more restrictions on how a root pool can be configured. I
> am not sure if they allow slog devices for root pools.
>
illumos does indeed have the following restrictions for root pools
according to zfs_ioc_vdev_add
* Concatenated devices are not supported
* Intent log device is not supported
So your right but I'm still curious if there are any reasons why we
shouldn't sync the zpool.cache file for the root pool as that seems
independent to this? The only thing I can think of is that it was an
optimisation but this would still break things like a reguid.
Regards
Steve
From owner-freebsd-fs@FreeBSD.ORG Fri Nov 7 13:37:01 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 23BB629E
for <freebsd-fs@FreeBSD.org>; Fri, 7 Nov 2014 13:37:01 +0000 (UTC)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
by mx1.freebsd.org (Postfix) with ESMTP id 6C29A3FA
for <freebsd-fs@FreeBSD.org>; Fri, 7 Nov 2014 13:37:00 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
[212.40.38.100])
by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA27266;
Fri, 07 Nov 2014 15:38:46 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
id 1Xmjie-000CfX-Cg; Fri, 07 Nov 2014 15:36:52 +0200
Message-ID: <545CCABA.6000707@FreeBSD.org>
Date: Fri, 07 Nov 2014 15:35:54 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Steven Hartland <killing@multiplay.co.uk>, Borja Marcos <borjam@sarenet.es>
Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift, should
be ZIL sets improper ashift with AHCI controllers
References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es>
<9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local>
<545B76EF.6050709@multiplay.co.uk>
<21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
<545BE3E0.4030203@multiplay.co.uk>
<757B9039-8DF0-4E6A-A036-82A2143D7F45@sarenet.es>
<545C9552.30207@multiplay.co.uk> <545CB43E.6040901@FreeBSD.org>
<545CC99B.1010302@multiplay.co.uk>
In-Reply-To: <545CC99B.1010302@multiplay.co.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@FreeBSD.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 13:37:01 -0000
On 07/11/2014 15:31, Steven Hartland wrote:
> illumos does indeed have the following restrictions for root pools according to
> zfs_ioc_vdev_add
> * Concatenated devices are not supported
> * Intent log device is not supported
>
> So your right but I'm still curious if there are any reasons why we shouldn't
> sync the zpool.cache file for the root pool as that seems independent to this?
> The only thing I can think of is that it was an optimisation but this would
> still break things like a reguid.
Yeah, I'd like to see an answer as well :)
--
Andriy Gapon
From owner-freebsd-fs@FreeBSD.ORG Fri Nov 7 15:49:15 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 837339B6
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 15:49:15 +0000 (UTC)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com
[IPv6:2607:f8b0:400d:c01::22a])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 41A487CC
for <freebsd-fs@freebsd.org>; Fri, 7 Nov 2014 15:49:14 +0000 (UTC)
Received: by mail-qc0-f170.google.com with SMTP id l6so2720262qcy.15
for <freebsd-fs@freebsd.org>; Fri, 07 Nov 2014 07:49:13 -0800 (PST)
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=lqBe3faFdREnfgL/MJflbF/7JC9G9/QwsD2iLGXQLEQ=;
b=jkSJGEaiD8mjXxevuRxQHMKN8JeYsdM4vbdLwr64MZXBJMiiR86pNOY3BAxlSpXClF
4CJT7Qwf4n5OpUqsz0Awwm9qk9Jx0E8TdQdNFcBcIDl+RoXf9bo0bS5U4bA2apVKWSNY
64ENNFGOt8wCNuJAZ9lQtJdo1SRbW68XVtNok+AbQpR9bpeveji3iIR08fPo8PRLtIlq
BWMX+ANlsg1QPR36LI/+tG9AW9KsjBRW4stEQPZaL9ZVfDTF4c6U6w/Jsb2OQ4tBUZFR
cM74N9YBRqXZT5ggzAZIy2dxS80Zf72IX++0vsWZD9fey9CGnyJJ5hJeGkty9O27TSQg
pmnA==
MIME-Version: 1.0
X-Received: by 10.224.41.142 with SMTP id o14mr8138736qae.100.1415375353144;
Fri, 07 Nov 2014 07:49:13 -0800 (PST)
Received: by 10.140.98.211 with HTTP; Fri, 7 Nov 2014 07:49:13 -0800 (PST)
In-Reply-To: <CAJjvXiEvo7n2pZGoEmjdSgcn0UdNsE2us5N65pB0zLC4V_+RNg@mail.gmail.com>
References: <CAJjvXiEvo7n2pZGoEmjdSgcn0UdNsE2us5N65pB0zLC4V_+RNg@mail.gmail.com>
Date: Fri, 7 Nov 2014 13:49:13 -0200
Message-ID: <CACj=ugQB_8nd7PqtY-ZC7srgsPeE6s8PsFc_ujn4U=5QkGGj0g@mail.gmail.com>
Subject: Re: [zfs-discuss] webcast: OpenZFS Developer Summit on Monday
From: Durval Menezes <durval.menezes@gmail.com>
To: "zfs-discuss@zfsonlinux.org" <zfs-discuss@zfsonlinux.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: developer <developer@open-zfs.org>, freebsd-fs <freebsd-fs@freebsd.org>,
illumos-zfs <zfs@lists.illumos.org>, "admin@open-zfs.org" <admin@open-zfs.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 15:49:15 -0000
Hi Matt,
On Thu, Nov 6, 2014 at 7:51 PM, Matthew Ahrens <mahrens@delphix.com> wrote:
> The 2nd annual OpenZFS Developer Summit will be held next Monday and
> Tuesday! I'm looking forward to seeing many of you there. For those who
> can't make it, there will be a live webcast of Monday's presentations,
> starting at 9:30AM PST.
>
> We have a huge variety of short talks, with more than 20 speakers and most
> talks being 15 minutes or less. Tune in for everything from high-level
> overviews, to deep dives into upcoming features, and practical explanations
> of how OpenZFS is used in products.
>
> The webcast, schedule, and all info is available on the webpage:
>
> http://www.open-zfs.org/wiki/OpenZFS_Developer_Summit_2014
>
Great initiative! Thanks for posting it.
--matt
>
> p.s. If you miss the webcast, we'll post slides and recorded video later
> in the week -- check the website or developer@open-zfs.org; I won't spam
> all these lists again :-)
>
I'm interested in a couple of talks, but probably won't be available at the
time to watch them live. Can you please post here when all talks are
available? One more post surely wouldn't be considered spam :-)
Cheers,
--
Durval.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to zfs-discuss+unsubscribe@zfsonlinux.org.
>
From owner-freebsd-fs@FreeBSD.ORG Sat Nov 8 20:43:49 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 10BD5E96
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 20:43:49 +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 EB772AAA
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 20:43:48 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA8Khmwm064184
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 20:43:48 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 188187] [zfs] [panic] 10-stable: Kernel panic on zpool import:
integer divide fault
Date: Sat, 08 Nov 2014 20:43:48 +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.0-STABLE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: danm@vivocore.com
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-188187-3630-TtihJHnRyl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-188187-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-188187-3630@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Nov 2014 20:43:49 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188187
Dan Milgram <danm@vivocore.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |danm@vivocore.com
--- Comment #3 from Dan Milgram <danm@vivocore.com> ---
I'm seeing the same exact panic error. I'm wondering if there's any workaround
to recover from this, as I can not import the zpool when trying to do so from
LiveCD. Also, running "zdb -e -bcsvL zroot" seg faults.
My system is FreeBSD 10.0 Release on an HP Proliant ML110 G7, with ZFS on root.
The pool consists of 2 mirrored hard drives 500GB.
--
You are receiving this mail because:
You are the assignee for the bug.
From owner-freebsd-fs@FreeBSD.ORG Sat Nov 8 22:05:25 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 EFBB6D3A
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 22:05:25 +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 D69A0200
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 22:05:25 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA8M5P8K051565
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 22:05:25 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 188187] [zfs] [panic] 10-stable: Kernel panic on zpool import:
integer divide fault
Date: Sat, 08 Nov 2014 22:05:25 +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.0-STABLE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: smh@FreeBSD.org
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-188187-3630-TJbnrJzCVJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-188187-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-188187-3630@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Nov 2014 22:05:26 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188187
Steven Hartland <smh@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |smh@FreeBSD.org
--- Comment #4 from Steven Hartland <smh@FreeBSD.org> ---
Can you use kdgb to print out the following with pretty print on:-
1. zio
2. each mirror_child_t entry in mm
--
You are receiving this mail because:
You are the assignee for the bug.
From owner-freebsd-fs@FreeBSD.ORG Sat Nov 8 22:07:06 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 5961AECB
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 22:07:06 +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 3B865228
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 22:07:06 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA8M76NB052087
for <freebsd-fs@FreeBSD.org>; Sat, 8 Nov 2014 22:07:06 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 188187] [zfs] [panic] 10-stable: Kernel panic on zpool import:
integer divide fault
Date: Sat, 08 Nov 2014 22:07:06 +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.0-STABLE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: smh@FreeBSD.org
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-188187-3630-jlQeKnUhSi@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-188187-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-188187-3630@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Nov 2014 22:07:06 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188187
--- Comment #5 from Steven Hartland <smh@FreeBSD.org> ---
(In reply to 6yearold from comment #0)
> I have root on ZFS and using 10-STABLE. Somewhere from March 15 i started to
> get following panic when mounting root:
>
> Fatal trap 18: integer divide fault while in kernel mode
> Fatal trap 18: integer divide fault while in kernel mode
> cpuid = 0; cpuid = 1; apic id = 00
> apic id = 01
> instruction pointer = 0x20:0xffffffff81a7f92d
> instruction pointer = 0x28:0xffffffff81a7f92d
> stack pointer = 0x28:0xfffffe0097a8b100
> stack pointer = 0x28:0xfffffe0097a12ba0
> frame pointer = 0x28:0xfffffe0097a8b120
> frame pointer = 0x28:0xfffffe0097a12bc0
> code segment = base rx0, limit 0xfffff, type 0x1b
> code segment = base rx0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = processor eflags = interrupt enabled,
> interrupt enabled, resume, resume, IOPL = 0
> IOPL = 0
> current process = current process = 0 (system_taskq_1) 1198
> (zpool)
> trap number = 18
> tpanic: integer divide fault
> cpuid = 0
> KDB: stack backtrace:
> #0 0xffffffff80910f30 at kdb_backtrace+0x60
> #1 0xffffffff808d6645 at panic+0x155
> #2 0xffffffff80cc9a9f at trap_fatal+0x38f
> #3 0xffffffff80cc96fc at trap+0x72c
> #4 0xffffffff80cb04f2 at calltrap+0x8
> #5 0xffffffff81a8c4e6 at vdev_mirror_io_start+0x146
> #6 0xffffffff81aa7205 at zio_vdev_io_start+0x185
> #7 0xffffffff81aa4352 at zio_execute+0x162
> #8 0xffffffff81a2f83d at arc_read+0x87d
> #9 0xffffffff81a4917e at traverse_prefetcher+0x13e
> #10 0xffffffff81a48580 at traverse_visitbp+0x270
> #11 0xffffffff81a48749 at traverse_visitbp+0x439
> #12 0xffffffff81a48fa3 at traverse_dnode+0x83
> #13 0xffffffff81a48d45 at traverse_visitbp+0xa35
> #14 0xffffffff81a48749 at traverse_visitbp+0x439
> #15 0xffffffff81a48fa3 at traverse_dnode+0x83
> #16 0xffffffff81a48a0c at traverse_visitbp+0x6fc
> #17 0xffffffff81a482b6 at traverse_prefetch_thread+0x96
>
> I've downloaded latest snapshot of 10-STABLE, booted it and ran
>
> ~ # zpool import -fR /mnt zroot
>
> The error was same.
please provide the output from the kernel dump which includes line numbers.
--
You are receiving this mail because:
You are the assignee for the bug.