I have old pool skeletons with vdevs that no longer exist. Can't import them,
can't destroy them, can't even rename them to something obvious like junk1.
What do I do to clean up?
--
This message posted from opensolaris.org
___
zfs-discuss mailing
Hi Chris,
Yes, this is a known problem and a CR is filed.
I haven't tried these in a while, but consider one of the following
workarounds below.
#1 is most drastic and make sure you've got the right device name. No
sanity checking is done by the dd command.
Other experts can comment on a
On Sun, 21 Jun 2009 13:56:52 +1000 (EST)
Andre van Eyssen an...@purplecow.org wrote:
On Sat, 20 Jun 2009, Cindy Swearingen wrote:
I wish we had a zpool destroy option like this:
# zpool destroy -really_dead tank2
Cindy,
The moment we implemented such a thing, there would be a rash
Over the course of multiple OpenSolaris installs , I first created a
pool called "tank" and then, later and resusing some of the same
drives, I created another pool called tank. I can `zpool export tank`,
but when I `zpool import tank`, I get:
bash-3.2# zpool import tank
cannot import
Hi Kent,
This is what I do in similar situations:
1. Import the pool to be destroyed by using the ID. In your case,
like this:
# zpool import 3280066346390919920
If tank already exists you can also rename it:
# zpool import 3280066346390919920 tank2
Then destroy it:
# zpool destroy tank2
I
On Sat, 20 Jun 2009, Cindy Swearingen wrote:
I wish we had a zpool destroy option like this:
# zpool destroy -really_dead tank2
Cindy,
The moment we implemented such a thing, there would be a rash of requests
saying:
a) I just destroyed my pool with -really_dead - how can I get my data
