I'm just about to start using ZFS in a RAIDZ configuration for a home file
server (mostly holding backups), and I wasn't clear on what happens if data
corruption is detected while resilvering. For example: let's say I'm using
RAIDZ1 and a drive fails. I pull it and put in a new one. While res
I'm planning on running FreeBSD in VirtualBox (with a Linux host) and giving it
raw disk access to four drives, which I plan to configure as a raidz2 volume.
On top of that, I'm considering using encryption. I understand that ZFS
doesn't
yet natively support encryption, so my idea was to set e
on 11/07/2010 15:54 Andriy Gapon said the following:
>on 11/07/2010 14:21 Roy Sigurd Karlsbakk said the following:
>>
>> I'm planning on running FreeBSD in VirtualBox (with a Linux host)
>> and giving it raw disk access to four drives, which I plan to
>> configure as a raidz2 volume.
Nikola M wrote:
>Freddie Cash wrote:
>> You definitely want to do the ZFS bits from within FreeBSD.
>Why not using ZFS in OpenSolaris? At least it has most stable/tested
>implementation and also the newest one if needed?
I'd love to use OpenSolaris for exactly those reasons, but I'm wary of using
Garrett wrote:
>I don't know about ramifications (though I suspect that a broadening
>error scope would decrease ZFS' ability to isolate and work around
>problematic regions on the media), but one thing I do know. If you use
>FreeBSD disk encryption below ZFS, then you won't be able able to import
I'm currently planning on running FreeBSD with ZFS, but I wanted to
double-check
how much memory I'd need for it to be stable. The ZFS wiki currently says you
can go as low as 1 GB, but recommends 2 GB; however, elsewhere I've seen
someone
claim that you need at least 4 GB. Does anyone here
Garrett D'Amore wrote:
>On Fri, 2010-07-16 at 10:24 -0700, Michael Johnson wrote:
>> I'm currently planning on running FreeBSD with ZFS, but I wanted to
>>double-check
>> how much memory I'd need for it to be stable. The ZFS wiki currently says
>you
>
