Pool not correctly destroyed

This forum is to find answers to problems you may be having with ZEVO Community Edition.

Moderators: jhartley, MSR734, nola

Pool not correctly destroyed

Post by Fredje_B » Tue Oct 30, 2012 11:45 am

I have a pool that was made of 2 disks. I destroy the pool and remove one of the two disks. Now, I see that the deleted pool is still visible in the disk Tools (or with a commando diskutil list).

The problem is that I can not use the disk that is linked to this deleted pool. Diskutil eraseVolime, diskutil eraseDisk all are finishing with the errors :
Started erase on disk3
Unmounting disk
Error: -69877: Couldn't open device

I can't also delete this pool again as zpool doesn't see it anymore (zpool list). And trying to recreate it gives me the same errors as when I try to delete the disk.


The log gives this when the machine is starting :
29/10/12 18:10:38,000 kernel: ZFSLabelScheme:probe: label 'Test', vdev 13375918736068257648

But there is no "ZFSLabelScheme:Start" commando afterwards. This is, according to me, the evidence that this deleted pool is still referenced in the pool table of ZFS, or am I wrong?

Is there any way to delete this entry in the config file of ZFS?
Fredje_B Offline


 
Posts: 7
Joined: Sun Sep 16, 2012 6:06 am

Re: Pool not correctly destroyed

Post by grahamperrin » Tue Oct 30, 2012 2:04 pm

Off-topic from installation of ZEVO

In some ways this reminds me of a topic in the general discussion area:


If you remove both disks, restart the operating system, then connect just one of the two disks, can you use that disk for a new pool?

Which OS?
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: Pool not correctly destroyed

Post by Fredje_B » Wed Oct 31, 2012 8:13 am

Just the same when i took the drive off and back on...I put back the second drive and the pool was visible again. I had no problem to destroy it again...is now in order.

I don't really good understand how ZFS will handle a hardware failure of one or more drive in a pool...if the (non raidz) pool is not accessible anymore and the drive are 'locked', how can you create a new pool with the still running drives?
Fredje_B Offline


 
Posts: 7
Joined: Sun Sep 16, 2012 6:06 am

Re: Pool not correctly destroyed

Post by grahamperrin » Wed Oct 31, 2012 4:39 pm

I should expect superuser privileges with option -f to give the force required for destruction of a pool that is UNAVAIL

Comparison: zpool freezing - The FreeBSD Forums (2010-05-05)
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: Pool not correctly destroyed

Post by Fredje_B » Fri Nov 02, 2012 7:49 am

I did use the superuser en -f option but as zpool don't see the pool anymore, it gives just an error : "No pool with xxxx finded"...
Fredje_B Offline


 
Posts: 7
Joined: Sun Sep 16, 2012 6:06 am

Re: Pool not correctly destroyed

Post by grahamperrin » Sat Nov 24, 2012 7:01 am

If the problem is reproducible, maybe run the following command before and during the routine:

Code: Select all
diskutil activity
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom


Return to Troubleshooting

Who is online

Users browsing this forum: bileyqrkq, ilovezfs and 0 guests

cron