Description of problem: Something is wrong with my pool. But if I try to run "zpool status -x" it hangs. Version-Release number of selected component (if applicable): zfs-fuse-0.6.9-6.20100709git.fc13.i686 How reproducible: Always (for me) Steps to Reproduce: 1. service zfs start 2. service zfs status 3. zpool status -x Actual results: [root@fedora ~]# service zfs-fuse status zfs-fuse (pid 28812) is running... pool: test state: UNAVAIL status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and online it using 'zpool online'. see: http://www.sun.com/msg/ZFS-8000-3C scrub: none requested config: NAME STATE READ WRITE CKSUM test UNAVAIL 0 0 0 insufficient replicas mapper/test UNAVAIL 0 0 0 cannot open [root@fedora ~]# zpool status -x Then it hangs. Expected results: No hang. Additional info: kernel-PAE-2.6.34.7-56.fc13.i686 fuse-2.8.4-1.fc13.i686 Workaround: strace -f *both* the zpool command *and* the zfs-fuse daemon. (!!!) Or possibly it just stopped hanging by itself and strace had nothing to do with it.
Well, /dev/mapper/test does not exist. But still, it should not hang.
I can't get the workaround to work now.
I tried "yum downgrade zfs-fuse" but (leaving aside problems with yum hanging while trying to stop zfs-fuse) zfs-fuse-0.6.0-6.fc13.i686 didn't see my pool at all. It said there were no pools.
Now I was wondering, why does the initscript succeed at determining the status, when it just calls zpool status? Well, it turns out: zpool status hangs, but /usr/bin/zpool status doesn't hang! And, surprise surprise, I have an old version of zfs-fuse installed in /usr/local/. Sorry.