-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/11 02:55, Edward Ned Harvey wrote:
>> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
>> boun...@opensolaris.org] On Behalf Of Carsten John
>>
>> Now I'm wondering about the best option to replace the HDD with the SSD:
>
> What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/11 02:55, Edward Ned Harvey wrote:
>> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
>> boun...@opensolaris.org] On Behalf Of Carsten John
>>
>> Now I'm wondering about the best option to replace the HDD with the SSD:
>
> What
bin65MpxTCk5V.bin
Description: PGP/MIME version identification
encrypted.asc
Description: OpenPGP encrypted message
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Carsten John
>
> Now I'm wondering about the best option to replace the HDD with the SSD:
What version of zpool are you running? If it's >= 19, then you could
actually survive a complete ZIL
I'd guess removing the SLOG altogether might be the safest, so for this
configuration logs mirror-7 ONLINE 0 0 0 c2t22d0 ONLINE 0 0 0 c2t23d0 ONLINE 0
0 0 just `zpool remove zwimming mirror-7`, run `cfgadm -a` to find the full
device path, do `cfgadm -c unconfigure devpath`, replace the drive, r
I think that the least disruptive way would be to detach the HDD from the ZIL
mirror and offline it, remove and replace with an SSD, and then attach the
SSD to the ZIL to make it a mirror again.
Note that this would create a window of possible ZIL failure (and you had
such a window already when
