Adding to a zpool -- different redundancies and risks

[Norman Gray]

Mike, hello.

On 12 Dec 2019, at 14:14, mike tancsa wrote:

> On 12/12/2019 7:42 AM, Norman Gray wrote:
>>
>>> 1   The 'zpool create ...' command you used to create the existing
>>> pool.
>> I don't have a note of the exact command, but it would have been
>> something like
>>
>>      zpool create pool raidz2 da{0,1,2,3,4,5,6,7,8} raidz2 da9
>> da1{0,1,2,3,4,5,6,7}
>
> would not
>
>     zpool history
>
> show how it was created ?

It would indeed!  How have I missed this command before?

# zpool history pool
History for 'pool':
2017-08-20.15:45:43 zpool create -m /pool pool raidz2 da2 da3 da4 da5 
da6 da7 da8 da9 da10 raidz2 da11 da12 da13 da14 da15 da16 da17 da18 da19
2017-08-20.18:36:39 zfs create pool/lofar
2017-08-25.16:45:28 zfs create pool/norman
2018-02-05.11:00:00 zfs create pool/mcmath
2018-09-07.12:13:27 zfs set compression=on pool/norman
2018-09-07.12:15:06 zfs set compression=on pool/lofar
2018-09-07.12:15:27 zfs set compression=on pool/mcmath
2018-09-07.12:15:32 zfs set compression=on pool
2018-12-03.12:27:43 zfs create pool/crisp
2019-06-24.16:08:09 zfs set quota=56T pool/lofar
2019-10-31.16:22:13 zpool export pool
2019-10-31.17:37:48 zpool import -a
2019-10-31.17:40:46 zpool export pool
2019-10-31.17:41:21 zpool import -d /dev/label -a

(So I wasn't quite right in my guessed 'create' command, but not too far 
off)

Best wishes (and thanks),

Norman


-- 
Norman Gray  :  https://nxg.me.uk
SUPA School of Physics and Astronomy, University of Glasgow, UK