Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to destroy faulted ZFS pool #41

Closed
wizeman opened this issue Jul 27, 2010 · 1 comment
Closed

Unable to destroy faulted ZFS pool #41

wizeman opened this issue Jul 27, 2010 · 1 comment

Comments

@wizeman
Copy link

wizeman commented Jul 27, 2010

I have this pool cached on my system:

      pool: tankmds1
     state: FAULTED
    status: One or more devices could not be used because the label is missing 
            or invalid.  There are insufficient replicas for the pool to continue
            functioning.
    action: Destroy and re-create the pool from
            a backup source.
       see: http://www.sun.com/msg/ZFS-8000-5E
     scan: none requested
    config:

            NAME             STATE     READ WRITE CKSUM
            tankmds1         FAULTED      0     0     0  corrupted data
              /tmp/img-mds1  UNAVAIL      0     0     0  corrupted data

But I'm unable to destroy it:

    [root@rhel5 zfs]# zpool destroy tankmds1
    cannot destroy 'tankmds1': one or more devices is currently unavailable

Not sure if this is an upstream bug or not, but the destroy is supposed to succeed.

I think the pool was created on top of a file on /tmp, which is still there, but I guess at some point the file was overwritten with zeros. Now when I load the ZFS module, I can't destroy the pool.
As a workaround, I can make the pool disappear by removing /etc/zfs/zpool.cache before loading the ZFS module.

I'm using these commits:

SPL: d0bd694
ZFS: 21191af

This is on RHEL5.5 using a Lustre-patched kernel (linux-2.6.18-164.6.1.el5).
@behlendorf
Copy link
Contributor

This was fixed by commit 0e533b7 when I noticed the same thing. Pull the latest ZFS sources and it should be OK. It was a side effect of the b141 update and the removal of the ZFS_IOC_MINOR_CREATE ioctl. There are still some lingering issue here with snapshots minors due to this I plan to run down before the 0.5.0 tag.

@wrouesnel wrouesnel mentioned this issue Jul 22, 2012
Closed
@dswartz dswartz mentioned this issue Apr 22, 2015
Closed
akatrevorjay added a commit to akatrevorjay/zfs that referenced this issue Dec 16, 2017
@akatrevorjay
# This is a combination of 56 commits.
4ae6a0d 
# This is the 1st commit message:
Merge branch 'master' of https://github.com/zfsonlinux/zfs

* 'master' of https://github.com/zfsonlinux/zfs:
  Enable QAT support in zfs-dkms RPM

# This is the commit message openzfs#2:

Import 0.6.5.7-0ubuntu3

# This is the commit message openzfs#3:

gbp changes

# This is the commit message openzfs#4:

Bump ver

# This is the commit message openzfs#5:

-j9 baby

# This is the commit message openzfs#6:

Up

# This is the commit message openzfs#7:

Yup

# This is the commit message openzfs#8:

Add new module

# This is the commit message openzfs#9:

Up

# This is the commit message openzfs#10:

Up

# This is the commit message openzfs#11:

Bump

# This is the commit message openzfs#12:

Grr

# This is the commit message openzfs#13:

Yay

# This is the commit message openzfs#14:

Yay

# This is the commit message openzfs#15:

Yay

# This is the commit message openzfs#16:

Yay

# This is the commit message openzfs#17:

Yay

# This is the commit message openzfs#18:

Yay

# This is the commit message openzfs#19:

yay

# This is the commit message openzfs#20:

yay

# This is the commit message openzfs#21:

yay

# This is the commit message openzfs#22:

Update ppa script

# This is the commit message openzfs#23:

Update gbp conf with br changes

# This is the commit message openzfs#24:

Update gbp conf with br changes

# This is the commit message openzfs#25:

Bump

# This is the commit message openzfs#26:

No pristine

# This is the commit message openzfs#27:

Bump

# This is the commit message openzfs#28:

Lol whoops

# This is the commit message openzfs#29:

Fix name

# This is the commit message openzfs#30:

Fix name

# This is the commit message openzfs#31:

rebase

# This is the commit message openzfs#32:

Bump

# This is the commit message openzfs#33:

Bump

# This is the commit message openzfs#34:

Bump

# This is the commit message openzfs#35:

Bump

# This is the commit message openzfs#36:

ntrim

# This is the commit message openzfs#37:

Bump

# This is the commit message openzfs#38:

9

# This is the commit message openzfs#39:

Bump

# This is the commit message openzfs#40:

Bump

# This is the commit message openzfs#41:

Bump

# This is the commit message openzfs#42:

Revert "9"

This reverts commit de488f1.

# This is the commit message openzfs#43:

Bump

# This is the commit message openzfs#44:

Account for zconfig.sh being removed

# This is the commit message openzfs#45:

Bump

# This is the commit message openzfs#46:

Add artful

# This is the commit message openzfs#47:

Add in zed.d and zpool.d scripts

# This is the commit message openzfs#48:

Bump

# This is the commit message openzfs#49:

Bump

# This is the commit message openzfs#50:

Bump

# This is the commit message openzfs#51:

Bump

# This is the commit message openzfs#52:

ugh

# This is the commit message openzfs#53:

fix zed upgrade

# This is the commit message openzfs#54:

Bump

# This is the commit message openzfs#55:

conf file zed.d

# This is the commit message #56:

Bump
@jasimmons1973 jasimmons1973 mentioned this issue Apr 23, 2019
Merged
12 tasks
@kocoman1 kocoman1 mentioned this issue Sep 30, 2021
Closed
18 tasks
sdimitro pushed a commit to sdimitro/zfs that referenced this issue Dec 7, 2021
@manoj-joseph
Add a zfs-build github workflow (openzfs#41)
8b3cf9c
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@behlendorf @wizeman