06:14:23 <blue-cat> If i want `zpool labelclear`, how do i define the device for this?
06:34:16 <jclulow> blue-cat: You could start with "zpool import" (as root), which should find any ZFS pools that _could_ be imported and print them.  You can also look at the output of "diskinfo", which should list disks that the system can see.
06:36:28 <blue-cat> zpool import says rpool ONLINE c1d0 OLPINE
06:36:54 <blue-cat> *in config:
06:39:49 <blue-cat> but i still don't understand what im supposed to specify as a device.
06:42:21 <blue-cat> `zpool labelclear -f c1d0` failed to clear label for /dev/dsk/c1d0s0
06:42:45 <blue-cat> why doesn't it work
08:08:30 <blue-cat> https://0x0.st/Xf-k.txt
08:11:47 <blue-cat> why is that?
09:24:41 <blue-cat> Does someone know?
13:04:01 <gitomat> [illumos-gate] 16663 pmap heap overflow if new LWP appears -- Andy Fiddaman <illumos⊙fn>
17:24:28 <sommerfeld> blue-cat: try 'zpool labelclear /dev/rdsk/c1d0s0'.   
17:27:07 <sommerfeld> in addition to the "zpool import" thing mentioned above, you can check for the presence of a ZFS label in a partition with "zdb -l"
17:28:13 <sommerfeld> try something like 'zdb -l /dev/rdsk/c1d0s0'
17:29:36 <jclulow> The fact that it's listing as "rpool" suggests you're booted from that pool
17:29:46 <jclulow> I think?
17:30:05 <jclulow> Oh I suppose it would say ONLINE in the import output just because it's not DEGRADED/FAULTED
17:30:20 <andyf> It might be that the device is not c1d0 in whatever is currently booted
17:31:19 <andyf> or, more likely, it's not a whole disk pool, so the pool might be on s1
18:17:20 <blue-cat> sommerfeld: # zpool labelclear -f /dev/rdsk/c1d0s0    returns: failed to clear label for /dev/rdsk/c1d0s0
18:20:00 <blue-cat> `# zdb -l /dev/dsk/c1d0` returns failed to unpack label 0 failed to unpack label 1 failed to unpack label 2 failed to unpack label 3
18:20:50 <blue-cat> same for `# zdb -l /dev/dsk/c1d0s0`
18:21:56 <blue-cat> sad
20:18:02 <tsoome> how many disks and pools you have? if you have just 2 disks and 2 pools (one rpool used for current OS instance), then check which disk is used for rpool and labelclear the other disk (get name from output of format or iostat -n or diskinfo)
20:31:19 <gitomat> [illumos-gate] 16610 headers, symbol-tests should know about c17, POSIX 2024 -- Robert Mustacchi <rm⊙fo>
20:31:19 <gitomat> [illumos-gate] 16624 Want support for FD_CLOFORK and friends -- Robert Mustacchi <rm⊙fo>
20:31:19 <gitomat> [illumos-gate] 14237 Want support for pthread_cond_clockwait() and friends -- Robert Mustacchi <rm⊙fo>
20:31:19 <gitomat> [illumos-gate] 16635 want SO_PROTOCOL socket option support -- Robert Mustacchi <rm⊙fo>
20:31:19 <gitomat> [illumos-gate] 16636 want ptsname_r -- Robert Mustacchi <rm⊙fo>
20:37:29 <richlowe> rmustacc: nice
20:38:43 <rmustacc> It's a start at least. More to come when I get some more time.
20:39:52 <blue-cat> tsoome: im from usb. and i cant labelclear
20:40:49 <blue-cat> i sent a link with the output and few messages
20:45:51 <blue-cat> it was about failed for some unknown reason
20:49:47 <tsoome> yes, I understand that you do get errors from labelclear. btw, what do you get from zdb -l /dev/dsk/c1d0s1 (assuming there is c1d0)?
21:10:32 <blue-cat> outputs some text, not failed
21:15:46 <tsoome> there are your labels then.
21:17:44 <tsoome> in short, labelclear has bug. it would be nice if you can report the problem https://www.illumos.org/issues
21:34:06 <blue-cat> tsoome supposedly it should work with the s1 omitted
21:34:22 <tsoome> exactly.
21:34:48 <blue-cat> I also don't understand why the import doesn't show s1
21:35:44 <tsoome> because the pool is created on "whole" device, in which case the slice name is omitted.
21:36:25 <blue-cat> im not sure about that honestly
21:36:26 <tsoome> with zdb -l, you can see the whole disk flag is 1 and you can also see the full disk name with slice included
21:37:13 <blue-cat> zdb -l failed labels for whole disk as i mentioned before
21:37:42 <tsoome> yes, thats why I did ask output from zdb -l /dev/dsk/c1d0s1
21:38:06 <blue-cat> i also found some information https://coda.io/@ff0/home-lab-data-vault/clearing-old-zfs-labels-22
21:38:26 <tsoome> also, if you check the partition table on that disk, you would see ESP (EFI System Partition) on s0
21:38:54 <blue-cat> yeah
21:39:09 <blue-cat> they're talking about the lack of wipefs in link i shared
21:40:27 <blue-cat> even though yesterday and the day before yesterday, people here told me otherwise.
21:45:43 <tsoome> why call it wipefs, if it wont touch data in partition? and why you need wipefs, if you have dd:P (https://man7.org/linux/man-pages/man8/wipefs.8.html)
21:51:14 <blue-cat> wipefs is wipefs not dd
21:51:42 <blue-cat> i dont mean lack
21:51:46 <blue-cat> wrong word
21:53:10 <blue-cat> i dont know english good