On Mon, 24 Feb 2020 at 18:59, Rocky Hotas <rockyho...@firemail.cc> wrote: > > Hi! > I was also trying to learn ZFS and still have some doubts. Thanks for > the suggestions in this whole thread. A couple of questions: > > On feb 21 13:40, David Brownlee wrote: > > [...] > > > - If you make a zfs filesystem on a disklabel partition (eg wd0f) and > > the disk moves zfs does not seem to be able to find it again. > > Do you mean if the disk is removed from the system and then plugged > there again? > > > zfs best practice is to use raw devices, so this shouldn't be an issue > > for most people > > For example, assume that you would like to create a new pool called > `newpool' using disk /dev/wd0. > By `using the raw device', are you meaning `zpool create newpool rwd0'?
My two pools: ... xci # zpool history tank | grep zpool\ create 2019-07-28.13:17:24 zpool create tank /dev/wd2d xci # zpool history pail | grep zpool\ create 2019-08-09.19:45:49 zpool create -f pail wd1 ... I never specify the raw device; as you see, it works both for the sheer name - wd1 - or whole disk partition - /dev/wd2d, both cover whole disks. I haven't used zfs pool backed by a disklabel slice yet, which was the warning above. On the other hand, the latest root-on-zfs VM I setup for testing has its pool on a gpt partition - /dev/dk2: dkctl wd0 listwedges /dev/rwd0: 6 wedges: dk3: FILLER, 30 blocks at 34, type: ffs dk0: d6dd2b31-4705-4a83-a239-f80a44bcfa66, 262144 blocks at 64, type: msdos dk4: F1LLER, 64 blocks at 262208, type: ffs dk1: boot, 4194304 blocks at 262272, type: ffs dk2: zfsroot, 58720256 blocks at 4456576, type: ffs dk5: SWAP2, 3931999 blocks at 63176832, type: ffs However, within the system itself I can't see the create history, as it was created outside it and only imported once populated: zpool history rpool History for 'rpool': 2020-02-22.16:03:34 zfs set mountpoint=legacy rpool/ROOT 2020-02-22.16:09:17 zpool import -f rpool 2020-02-22.17:11:06 zpool import -f -N rpool .... > > Rocky -- ----
