I pulled down the latest boot image, burned a new USB key, and rebooted the
system with it, so unfortunately I don't have the output available for
posting now (scrolled back out of my terminal's buffer), but it was
something to the effect of "cannot remove device X: operation not supported
on this type of pool".
But it's now a moot point, because after rebooting I was able to do the
remove:
root@smart01 /zones/scratch/backup # zpool status zones
pool: zones
state: ONLINE
scan: scrub repaired 0 in 7h16m with 0 errors on Fri Jan 19 04:41:43 2018
config:
NAME STATE READ WRITE CKSUM
zones ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c1t26d0 ONLINE 0 0 0
c1t23d0 ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
c1t27d0 ONLINE 0 0 0
c1t28d0 ONLINE 0 0 0
mirror-2 ONLINE 0 0 0
c1t29d0 ONLINE 0 0 0
c1t30d0 ONLINE 0 0 0
logs
mirror-3 ONLINE 0 0 0
c1t25d0p0 ONLINE 0 0 0
c1t31d0p0 ONLINE 0 0 0
errors: No known data errors
root@smart01 /zones/scratch/backup # zpool remove zones mirror-3
root@smart01 /zones/scratch/backup # zpool status zones
pool: zones
state: ONLINE
scan: scrub repaired 0 in 7h16m with 0 errors on Fri Jan 19 04:41:43 2018
config:
NAME STATE READ WRITE CKSUM
zones ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c1t26d0 ONLINE 0 0 0
c1t23d0 ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
c1t27d0 ONLINE 0 0 0
c1t28d0 ONLINE 0 0 0
mirror-2 ONLINE 0 0 0
c1t29d0 ONLINE 0 0 0
c1t30d0 ONLINE 0 0 0
errors: No known data errors
And using "s0" instead of "p0" to specify the partition to use for the
ZIL mirror solved the other issue:
root@smart01 /zones/scratch/backup # zpool add -f zones log mirror
c1t25d0s0 c1t31d0s0
root@smart01 /zones/scratch/backup # zpool status
pool: zones
state: ONLINE
scan: scrub repaired 0 in 7h16m with 0 errors on Fri Jan 19 04:41:43 2018
config:
NAME STATE READ WRITE CKSUM
zones ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c1t26d0 ONLINE 0 0 0
c1t23d0 ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
c1t27d0 ONLINE 0 0 0
c1t28d0 ONLINE 0 0 0
mirror-2 ONLINE 0 0 0
c1t29d0 ONLINE 0 0 0
c1t30d0 ONLINE 0 0 0
logs
mirror-3 ONLINE 0 0 0
c1t25d0s0 ONLINE 0 0 0
c1t31d0s0 ONLINE 0 0 0
errors: No known data errors
root@smart01 /zones/scratch/backup # zpool add zones cache c1t25d0s2
root@smart01 /zones/scratch/backup # zpool add zones cache c1t31d0s3
root@smart01 /zones/scratch/backup # zpool status zones
pool: zones
state: ONLINE
scan: scrub repaired 0 in 7h16m with 0 errors on Fri Jan 19 04:41:43 2018
config:
NAME STATE READ WRITE CKSUM
zones ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c1t26d0 ONLINE 0 0 0
c1t23d0 ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
c1t27d0 ONLINE 0 0 0
c1t28d0 ONLINE 0 0 0
mirror-2 ONLINE 0 0 0
c1t29d0 ONLINE 0 0 0
c1t30d0 ONLINE 0 0 0
logs
mirror-3 ONLINE 0 0 0
c1t25d0s0 ONLINE 0 0 0
c1t31d0s0 ONLINE 0 0 0
cache
c1t25d0s2 ONLINE 0 0 0
c1t31d0s3 ONLINE 0 0 0
errors: No known data errors
root@smart01 /zones/scratch/backup # zpool iostat -v zones
capacity operations bandwidth
pool alloc free read write read write
------------- ----- ----- ----- ----- ----- -----
zones 1.93T 497G 55 102 2.44M 2.53M
mirror 148G 1.49G 11 24 211K 391K
c1t26d0 - - 3 12 185K 392K
c1t23d0 - - 3 12 185K 392K
mirror 459G 4.61G 15 32 730K 693K
c1t27d0 - - 6 15 576K 693K
c1t28d0 - - 6 15 576K 693K
mirror 1.33T 491G 28 45 1.53M 1.47M
c1t29d0 - - 14 23 1.34M 1.47M
c1t30d0 - - 14 23 1.34M 1.47M
logs - - - - - -
mirror 2.00M 1.98G 0 11 0 133K
c1t25d0s0 - - 0 11 120 149K
c1t31d0s0 - - 0 11 120 149K
cache - - - - - -
c1t25d0s2 398M 106G 0 145 4.52K 13.3M
c1t31d0s3 29.2M 51.0G 0 40 18.0K 3.88M
------------- ----- ----- ----- ----- ----- -----
root@smart01 /zones/scratch/backup #
So all is right with the world again. But I'm still left with one
question: why on Earth is *parted* not included as part of the SmartOS
hypervisor image? The old Solaris format command is spectacularly
user-unfriendly and always has been. I can't imagine that parted requires
so much additional space that it couldn't be included. Was there any
particular rationale to not put a better and more user-friendly
partitioning tool into the OS that runs at the top level and manages the
hardware?
I really don't want to come across as overly critical; this has been my
first time working with SmartOS and up until this current problem, things
have gone very well and I've been extremely impressed. I've successfully
migrated 2 KVM systems using older versions of Linux to this machine and so
far they are working great; I've also reimplemented a couple of Linux KVM
systems running more recent (Ubuntu 16.04) distros as LX branded zones and
they've performed flawlessly so far. This is really nice tech and I'm
looking forward to getting more comfortable with it.
Many thanks for your assistance!
best,
Jim
On Thu, Jan 18, 2018 at 10:47 PM, Jussi Sallinen <[email protected]> wrote:
> On 19/01/2018 8.16, Jim Wiggs wrote:
>
> Folks,
>>
>> Why can I not remove the ZIL from my zones pool? Please tell me this
>> is not a "feature"...
>>
>> I'm trying to accomplish something that is ridiculously easy with ZFS
>> on Linux, and ridiculously difficult in SmartOS:
>>
>> 1. Partition my two SSDs to have two partitions each: one 2GB
>> partition for ZIL and one partition with all the remaining space for L2ARC
>> 2. Set a mirror of the 2GB partitions on the two SSDs as the ZIL
>> 3. Add the remaining space on the two drives as L2ARC space
>>
>> I could do this in about 90 seconds on a Linux box: parted for step 1,
>> "zpool add zones log mirror ssd1p1 ssd2p1" for step 2, and "zpool add zones
>> cache ssd1p2" + "zpool add zones cache ssd2p2" for step 3.
>>
>> I've spent the last three hours trying to do it on my SmartOS box, and
>> now I'm stuck with a zones zpool that's using the full space on both drives
>> for ZIL with nothing left over for cache. And what's worse, there's
>> apparently no way to undo this without destroying the zpool and starting
>> over, which I absolutely cannot afford to do at this point.
>>
>> Any suggestions that anyone can make would be *very* welcome!
>>
>
> Hi,
>
> Output of zpool status would be useful and command that you've tried to
> remove the mirrored ZIL with.
> This is what zpool(1m) says about removing ZFS Intent Log:
>
> "Log devices can be added, replaced, attached, detached, and imported and
> exported as part of the larger pool. Mirrored log devices can be removed
> by specifying the top-level mirror for the log."
>
> ie. zpool remove tank mirror-1
>
> --
> -Jussi Sallinen
> [email protected]
> https://jus.si/
>
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
