On Friday, March 23, 2018, 1:27:25 PM PDT, Jussi Sallinen <[email protected]>
wrote:
On 22/03/2018 8.07, LastQuark wrote:
Here's the output of zpool history:
--- start ---History for 'zones':2018-03-21.19:26:30 zpool create -f zones
c2t0d0 log c3t1d02018-03-21.19:26:35 zfs set atime=off zones2018-03-21.19:26:36
zfs create -V 1378mb -o checksum=noparity zones/dump2018-03-21.19:26:38 zfs
create zones/config2018-03-21.19:26:38 zfs set mountpoint=legacy
zones/config2018-03-21.19:26:39 zfs create -o mountpoint=legacy
zones/usbkey2018-03-21.19:26:39 zfs create -o quota=10g -o
mountpoint=/zones/global/cores -o compression=gzip
zones/cores2018-03-21.19:26:39 zfs create -o mountpoint=legacy
zones/opt2018-03-21.19:26:40 zfs create zones/var2018-03-21.19:26:40 zfs set
mountpoint=legacy zones/var2018-03-21.19:26:41 zfs create -V 32741mb
zones/swap2018-03-21.19:28:44 zpool import -f zones2018-03-21.19:28:44 zpool
set feature@extensible_dataset=enabled zones2018-03-21.19:28:45 zfs set
checksum=noparity zones/dump2018-03-21.19:28:45 zpool set
feature@multi_vdev_crash_dump=enabled zones2018-03-21.19:28:46 zfs destroy -r
zones/cores2018-03-21.19:28:46 zfs create -o compression=gzip -o
mountpoint=none zones/cores2018-03-21.19:28:52 zfs create -o quota=10g -o
mountpoint=/zones/global/cores zones/cores/global2018-03-21.19:29:12 zfs create
-o compression=lzjb -o mountpoint=/zones/archive
zones/archive2018-03-22.05:20:28 zpool import -f zones2018-03-22.05:20:28 zpool
set feature@extensible_dataset=enabled zones2018-03-22.05:20:29 zfs set
checksum=noparity zones/dump2018-03-22.05:20:29 zpool set
feature@multi_vdev_crash_dump=enabled zones--- end ---
Also, if I may add, installed a more later version of Smartos USB and I am
still getting errors. I hope I didn't lose the original zones. I still have
the other mirrored drive to try.
Hi,
According to the zpool history you never had mirrored zones pool, the 'zones'
pool was created on 2018-03-21 with a single disk (c2t0d0) and a log device
(c3t1d0).
Unfortunately ZFS Log Device (for ZIL, ZFS Intent Log) is not a mirrored copy
of the contents of the 'zones' data disk (c2t0d0).
Do you mean you have a disk which is not currently connected to the host, ie.
your previous installation which suffered a hardware failure?
Ps. Here's few links regarding ZFS Log Device & ZIL:
https://www.ixsystems.com/blog/o-slog-not-slog-best-configure-zfs-intent-log/
http://www.freenas.org/blog/zfs-zil-and-slog-demystified/
-Jussi
Hi Jussi,
After the crash, I took one of the mirrored drive out and installed a fresh
single disk (c2t0d0). I went through the Smartos install process this time
installing the zones to c2t0d0 while c3t1d0 drive is still attached. I believe
this process created the log device (c3t1d0) and overrides the content of the
original zones. From the looks of it, this copy of the zones in c3t1d0 is
already screwed. I have one more shot at it on the other mirrored drive.
What is the correct process of retrieving the zones in the original mirrored
drive and copying them over to the new zones in a new drive? I do not seem to
find good documentation on it particularly related to Smartos.
Thanks for looking into this by the way and for the links.
Rgds.
| smartos-discuss | Archives | Modify Your Subscription | |
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
