Re: clear old pools remains from active vdevs

On 26/04/2018 18:14, Alan Somers wrote: > On Thu, Apr 26, 2018 at 8:37 AM, Eugene Grosbein > wrote: > > 26.04.2018 14:50, Andriy Gapon wrote: > > > You can try to use zdb -l to find the stale labels. > > And then zpool labelclear to

Re: clear old pools remains from active vdevs

On 26/04/2018 17:37, Eugene Grosbein wrote: > 26.04.2018 14:50, Andriy Gapon wrote: > >> You can try to use zdb -l to find the stale labels. >> And then zpool labelclear to clear them. > > Our "zpool labelclear" implementation destroys everything (literally). > Have you really tried it? > I

Re: clear old pools remains from active vdevs

On Thu, Apr 26, 2018 at 8:37 AM, Eugene Grosbein wrote: > 26.04.2018 14:50, Andriy Gapon wrote: > > > You can try to use zdb -l to find the stale labels. > > And then zpool labelclear to clear them. > > Our "zpool labelclear" implementation destroys everything (literally). >

Re: clear old pools remains from active vdevs

26.04.2018 14:50, Andriy Gapon wrote: > You can try to use zdb -l to find the stale labels. > And then zpool labelclear to clear them. Our "zpool labelclear" implementation destroys everything (literally). Have you really tried it? ___

Re: clear old pools remains from active vdevs

On 26/04/2018 10:28, Eugene M. Zheganin wrote: > Hello, > > > I have some active vdev disk members that used to be in pool that clearly have > not beed destroyed properly, so I'm seeing in a "zpool import" output > something > like > > > # zpool import >    pool: zroot > id:

clear old pools remains from active vdevs

Hello, I have some active vdev disk members that used to be in pool that clearly have not beed destroyed properly, so I'm seeing in a "zpool import" output something like # zpool import pool: zroot id: 14767697319309030904 state: UNAVAIL status: The pool was last accessed by