On Thu, Jun 01, 2017 at 01:01:49PM -0700, Paul B. Henson wrote:
> > From: Geoff Nordli
> > Sent: Tuesday, May 30, 2017 7:57 PM
> >
> > Right, it will not boot after upgrading to the new loader; even if the
> > 4K disks are not part of the rpool.
>
> Yikes 8-/, I'm glad I hadn't got around to
> From: Geoff Nordli
> Sent: Tuesday, May 30, 2017 7:57 PM
>
> Right, it will not boot after upgrading to the new loader; even if the
> 4K disks are not part of the rpool.
Yikes 8-/, I'm glad I hadn't got around to updating; my data pool consists
of 13 WD Red 3TB drives which are 4K native. I'm
On Thu, 1 Jun 2017, Artem Penner wrote:
are *zfs intent log* data will be striped across all disk in pool without
redundancy? If hard drive fail and this cause kernel panic, can I lose my
data?
You will not lose data if sufficient hard drives are working properly.
That is the purpose of zfs
are *zfs intent log* data will be striped across all disk in pool without
redundancy? If hard drive fail and this cause kernel panic, can I lose my
data?
чт, 1 июн. 2017 г. в 17:45, Rafael Pardinas :
> By default, ZFS stores the ZIL in the pool with all the data, so yes.
>
> On
On Thu, 1 Jun 2017, qutic development wrote:
; Hi Theo,
;
; that is a word!
;
; > I was hoping not to be the first, but I will attempt to lead by example.
I'll pledge my time to do required security package publications on 014 and
022. As security issues with packages in core arise, I will