From owner-freebsd-rc@freebsd.org  Thu Sep 24 21:12:01 2015
Return-Path: <owner-freebsd-rc@freebsd.org>
Delivered-To: freebsd-rc@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68A9DA07A73;
 Thu, 24 Sep 2015 21:12:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (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 2237B1761;
 Thu, 24 Sep 2015 21:12:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1ZfDo0-0007jb-2j; Fri, 25 Sep 2015 00:11:52 +0300
Date: Fri, 25 Sep 2015 00:11:51 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Cc: "Andrey V. Elsukov" <bu7cher@yandex.ru>,
 FreeBSD Current <freebsd-current@FreeBSD.org>,
 freebsd-rc@FreeBSD.org, Andriy Gapon <avg@FreeBSD.org>, cem@FreeBSD.org
Subject: Re: dumpdev in loader.conf vs rc.d/dumpon
Message-ID: <20150924211151.GT21849@zxy.spb.ru>
References: <5602B922.20703@FreeBSD.org>
 <CAG6CVpVvStV1pUi8WEBS0T5PaHxFk_HxGi8ch-LXU_DiheyTGw@mail.gmail.com>
 <5602CDBC.7080906@FreeBSD.org>
 <CAG6CVpXfBj_-cLj-8EMuAzgk6Ktmh_46e6zBBkZHMBxYW7=Cqg@mail.gmail.com>
 <5602DA17.7060501@FreeBSD.org> <5603B415.2090405@yandex.ru>
 <20150924111850.GA3158@zxy.spb.ru>
 <20150924205800.GA1475@garage.freebsd.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150924205800.GA1475@garage.freebsd.pl>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-rc@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Discussion related to /etc/rc.d design and implementation."
 <freebsd-rc.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-rc>,
 <mailto:freebsd-rc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-rc/>
List-Post: <mailto:freebsd-rc@freebsd.org>
List-Help: <mailto:freebsd-rc-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
 <mailto:freebsd-rc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2015 21:12:01 -0000

On Thu, Sep 24, 2015 at 10:58:00PM +0200, Pawel Jakub Dawidek wrote:

> On Thu, Sep 24, 2015 at 02:18:50PM +0300, Slawa Olhovchenkov wrote:
> > On Thu, Sep 24, 2015 at 11:28:05AM +0300, Andrey V. Elsukov wrote:
> > 
> > > On 23.09.2015 19:57, Andriy Gapon wrote:
> > > > I do not have a strong opinion.  Either option, rc.d/dumpon change or geom_dev
> > > > change, is fine with me.
> > > 
> > > I added the ability to set dumpdev via loader. But I wasn't aware that
> > > it was used in rc.d script.
> > > 
> > > If you have set dumpdev kenv, it will be already enabled in the time
> > > when rc.d/dumpon  will be run. So, I think it is useless to try to
> > > enable dumpdev again. I prefer remove this old code from rc.d script.
> > 
> > rc.d script can redirect dump to device, not available at boot time,
> > iSCSI disk, for examle.
> 
> No. Dump device is very special. It runs in an environment when kernel
> already paniced, there are no interrupt, so there is no networking.
> Storage controllers have special methods to handle dumping kernel memory
> - it doesn't go through GEOM, it cannot go through GEOM as the scheduler
> doesn't work too.

Can be ZFS VOL act as dump device?