Turns out zfs mount -a will pick up the file system.
Fun question is why the OS can't mount the disk by itself.
gnome-mount is what puts up the "Can't access the disk"
and whines to stdout (/dev/null in this case) about:
> ** (gnome-mount:1050): WARNING **: Mount failed for
> /org/freedesktop/Hal
Indeed, after rebooting we see the following. You'll have to trust me that
/ehome and /ehome/v1 are the relevant ZFS filesystems. If it makes any
different, this file system had been previously mounted. My memory is
suggesting that zpool import works in this situation whenever the FS
hasn't been pr
Currently on SNV92 + some BFUs but this has bene going on for quite a while.
If I boot my system without a USB drive plugged in and then plug it in,
rmformat sees it but ZFS seems not to. If I reboot the system, ZFS
will have no problem with using the disk.
> # zpool import
> # rmformat
> Lookin
