Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Sep 2008 22:43:01 -0400
From:      Vinny <vinny-mail-01+f.questions20080919@palaceofretention.ca>
To:        Questions <questions@freebsd.org>
Subject:   Re: geli and soft-updates
Message-ID:  <48D9A935.70601@palaceofretention.ca>
In-Reply-To: <20080922200239.27da4175@fabiankeil.de>
References:  <48D448A6.2080103@palaceofretention.ca>	<20080920081539.L8554@wojtek.tensor.gdynia.pl>	<48D5A739.4030505@palaceofretention.ca>	<20080922100544.GA10184@nemesis.frida.mouhaha.de> <20080922200239.27da4175@fabiankeil.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Fabian Keil wrote:
> Oliver Peter <lists@peter.de.com> wrote:
> 
>> On Sat, Sep 20, 2008 at 09:45:29PM -0400, Vinny wrote:
>>> ...
[...]

>> I'm using ZFS on geli on my production server with 2 SATA2 disks.
>> Just create and attach the geli devices in /dev and then create
>> a zpool i.e. with 
>>
>>   # zpool create crypt /dev/ad3.eli /dev/ad6.eli
>>
>> Works splendid.

> 
> I'm using ZFS on three geli encrypted slices,
> the only problem I ran into was:
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/117158
> "zpool scrub causes panic if geli vdevs detach on last close"
> 

Thanks for your feedback.  I'm going to give it another try.
I used to run ZFS on top of geli but I had kernel panics.

I changed the providers to normal non-geli disks but still had
panics.  I found out later that the panics were kernel memory related
(kmem_malloc) since ZFS wants a lot.  I increased two of
the kernel memory parameters and haven't seen a panic again.

vm.kmem_size: 512M
vm.kmem_size_max: 512M

I guess I'll have to try the geli disks again now that the
memory has been increased.

Vinny



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48D9A935.70601>