Is it possible to destroy a pool by ID? I created two pools with the same name, and want to destroy one of them -neel
On Wed, Sep 27, 2006 at 09:53:32AM -0700, Neelakanth Nadgir wrote:> Is it possible to destroy a pool by ID? I created two pools with the > same name, and want to destroy one of themHow do you manage to do that? This should be impossible, and is a bug in ZFS somewhere. The internal AVL tree is keyed off of the pool name, so something must be very screwed up - I''m surprised the machine hasn''t panicked. Can you run ''::spa -ve'' from ''mdb -k'' on this machine? You can try to export both pools one by one, and then import back the one you want. Not sure how it will work, since you are in undefined bug territory here... - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
Neel,> Is it possible to destroy a pool by ID? I created two pools with the > same name, and want to destroy one of themCould you please cut and paste (ie. not re-type) the output from the command "zpool list | col -b", and post it here please? Thanks... Sean.
Sorry, But i was able to dd zero''s to the devices "zpool status" gave for the incorrect zpool, and made it disappear. There are two possible cases that could have made this happen 1. When I first created the zpool (zpool create zfsdata ...) I control-c''d the command. I ran it to completion the next time around. 2. Some of the disks I used, were part of a zpool of the same name, but on a different system. I created a zpool containing those disks and some new disks I am not sure if I can reproduce what I saw. -neel> On Wed, Sep 27, 2006 at 09:53:32AM -0700, Neelakanth Nadgir wrote: > > Is it possible to destroy a pool by ID? I created two pools with the > > same name, and want to destroy one of them > > How do you manage to do that? This should be impossible, and is a bug > in ZFS somewhere. The internal AVL tree is keyed off of the pool name, > so something must be very screwed up - I''m surprised the machine hasn''t > panicked. Can you run ''::spa -ve'' from ''mdb -k'' on this machine? > > You can try to export both pools one by one, and then import back the > one you want. Not sure how it will work, since you are in undefined bug > territory here... > > - Eric > > -- > Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
> On Wed, Sep 27, 2006 at 09:53:32AM -0700, Neelakanth Nadgir wrote: > > Is it possible to destroy a pool by ID? I created two pools with the > > same name, and want to destroy one of them > > How do you manage to do that? This should be impossible, and is a bug > in ZFS somewhere. The internal AVL tree is keyed off of the pool name, > so something must be very screwed up - I''m surprised the machine hasn''t > panicked. Can you run ''::spa -ve'' from ''mdb -k'' on this machine?Is this only a concern with *imported* pools? I was assuming Neelakath was trying to destroy exported pools (or at least one of them was exported). I hope ZFS won''t get too worried about them if I do this an they''re not both imported (thinking about moving LUNs over from a test system that had been using the same pool name). -- Darren Dunham ddunham at taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
I was trying to import the pool, but got an error that there wee 2 pools with the same name (in exported state) and I had to import by "id". Thus I wanted to destroy the other pool -neel Sometime ago, Darren Dunham said:> > On Wed, Sep 27, 2006 at 09:53:32AM -0700, Neelakanth Nadgir wrote: > > > Is it possible to destroy a pool by ID? I created two pools with the > > > same name, and want to destroy one of them > > > > How do you manage to do that? This should be impossible, and is a bug > > in ZFS somewhere. The internal AVL tree is keyed off of the pool name, > > so something must be very screwed up - I''m surprised the machine hasn''t > > panicked. Can you run ''::spa -ve'' from ''mdb -k'' on this machine? > > Is this only a concern with *imported* pools? I was assuming Neelakath > was trying to destroy exported pools (or at least one of them was > exported). > > I hope ZFS won''t get too worried about them if I do this an they''re not > both imported (thinking about moving LUNs over from a test system that > had been using the same pool name). >
On Wed, Sep 27, 2006 at 02:12:48PM -0700, Darren Dunham wrote:> > Is this only a concern with *imported* pools? I was assuming Neelakath > was trying to destroy exported pools (or at least one of them was > exported).Yes, that is correct.> I hope ZFS won''t get too worried about them if I do this an they''re not > both imported (thinking about moving LUNs over from a test system that > had been using the same pool name).Yes, that is correct. ''zpool import'' will display both pools, and allow you to selectively import one of them by GUID rather than name. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock