--
To post to this group, send email to zfs-...@googlegroups.com
To visit our Web site, click on http://zfs-fuse.net/
For the record: there have been bugs with disappearing datasets going
from 0.5* to 0.6*. Starting with 0.6.1 (nicknamed "critical" in some
packages) these problems should no longer occur.
Also, it makes complete sense that you might have a pool with mixed
filesystem versions. It is technically possible to have filesystems of
unsupported versions inside a pool of 'older' versions[1]. In that case,
the following theory might apply: zfs-fuse is compatible enough to
import the pool (pool version is low enough) but it doesn't yet support
the filesystem version.
In any case, try to explicitely 'zfs mount tank/my/unmounted/fs' and see
what the output is.
In all cases, it is recommended to upgrade to 0.6.9. It should support
up to pool version 23 (from the top of my head) and that should be on
par with a Solaris nv134 at least.
If you were using an even more recent version of OpenSolaris [2] you
might _have_ to resort to an unstable build with Emmanuels ongoing synch
work with upstream. I believe it supports pool version 25 now. Beware
this is dev grade so use with backups!
Here is the link for our repo:
http://zfs-fuse.net/releases/0.6.9 (contains link to maint snapshots)
gitweb, official maint:
http://gitweb.zfs-fuse.net/?p=official;a=shortlog;h=refs/heads/maint
gitweb, emmanuels dev branch:
http://gitweb.zfs-fuse.net/?p=emmanuel;a=shortlog;h=refs/heads/master
[1] the most playsible way in which such a situation may arise is when
receiving filesystems into a pool using zfs send/receive
[2] not yet published via genunix.org
So maybe /I/ was the moron here, but you see how naively I might have just happily done the apt-get install zfs-fuse, seen most of my filesystems are there, migrate the data and destroy the zpool, and realize the damage I've done only later.
IMPORTANT NOTICE
That
this release has been superseded by 0.6.9. The initial release of this
version included a potentially dangerous problem with larger pools that
would 'hide' filesystems. Such issues could lead to data loss if
unnoticed, which is why it absolutely recommended to upgrade to the
0.6.9 release from this website, if at all possible.