Did you erase the *whole* disk? (label and both start and end of disk?) Otherwise I’m out of ideas — the only thing it could know about at that point would be the WWN or some such, but I don’t see why it would care unless you actually do have a pool configuration that still references it.
On Fri, Apr 1, 2016 at 12:44 PM, Gabriele Bulfon <[email protected]> wrote: > The proptotype machine is safe, I can play with it as much as I like, > until I find a good solution for the target machine. > > I did the "dd if=/dev/zero of=/dev/....", did the fdisk remove/create > partition...no way :( > Only if I change the disk phisically in between the volume2jbod, the it > will work. > > How can this be? Any other way to let it think it's another disk and > forget about the replacing one? > > > ---------------------------------------------------------------------------------------- > *Sonicle S.r.l. *: http://www.sonicle.com > *Music: *http://www.gabrielebulfon.com > *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon > > ------------------------------ > > > *Da:* Garrett D'Amore <[email protected]> > *A:* [email protected] > *Cc:* Aldo Fornoni <[email protected]> > *Data:* 1 aprile 2016 18.07.28 CEST > *Oggetto:* Re: [discuss] converting adpatec volume to jbod cannot replace > > > If you have a backup, you can try destroying the label on the disk > you’re adding. I think its likely that zpool is seeing the ZFS label > or other data on the drive and trying to be paranoid to prevent you from > clobbering useful data on the drive. dd from /dev/zero to the drive can > clear that up (but again, make sure you have a backup in case something > goes wrong!) > > On Fri, Apr 1, 2016 at 11:47 AM, Gabriele Bulfon <[email protected]> > wrote: > >> Hi, >> I'm trying to convert a raidz pool that has 3 vdev incorrectly configured >> as volumes instead of jbods. >> One by one I would like to: >> - offline the vdev on the pool >> - through arcconf remove the volume, initialize and create it as jbod >> - zpool replace the old vdev with the new vdev >> >> Everytime I get to the last point, zfs cannot use the target device as >> busy, or "part of active ZFS pool data". >> No "-f" solve the problem. >> >> I'm using a prototype machine before using the destination one. >> If I destroy the pool and recreate through "-f" correctly. >> >> Looks like because the replaced disk is actually the same, but with a >> different vdev, something goes wrong. >> >> Any idea? >> >> Gabriele >> >> >> ---------------------------------------------------------------------------------------- >> *Sonicle S.r.l. *: http://www.sonicle.com >> *Music: *http://www.gabrielebulfon.com >> *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon >> > > *illumos-discuss* | Archives > <https://www.listbox.com/member/archive/182180/=now> > <https://www.listbox.com/member/archive/rss/182180/22003744-9012f59c> | > Modify > <https://www.listbox.com/member/?&;> > Your Subscription <http://www.listbox.com> > ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
