ZFS pool disappeared in zfs-fuse after system freeze

116 views
Skip to first unread message

Timo Holle

unread,
Apr 3, 2009, 4:05:47 PM4/3/09
to zfs-fuse
Hello all,

I have created a zpool with RAID-Z spanning three whole disks using
the OpenSolaris 2008.11 LiveCD.
I know that there are known issues when using raw disks with zfs-fuse
in Linux, but I had no problems at first accessing the pool from an
Ubuntu 8.10 Live-CD using the zfs-fuse packages for Ubuntu Intrepid by
Filip Brcic [ https://launchpad.net/~brcha/+archive/ppa -> zfs-fuse -
0.5.1-1ubuntu5 ].

While copying an immense amount of small files from an XFS filesystem
to an ZFS filesystem in the pool (using Nautilus as root), the system
froze and I did a reset. After that, the zpool disappeared under
Linux. In OpenSolaris it is still perfectly usable an a scrub reports
that there were no errors.

Here are the outputs of several zpool-commands on Linux:

------------------------------------------------------------------------------------------------------
ubuntu@ubuntu:~$ sudo zpool import timo
cannot import 'timo': pool may be in use from other system, it was
last accessed by opensolaris (hostid: 0x866da7) on Thu Jan 1 00:00:00
1970
use '-f' to import anyway

------------------------------------------------------------------------------------------------------

ubuntu@ubuntu:~$ sudo zpool import -f timo
cannot import 'timo': no such pool or dataset

------------------------------------------------------------------------------------------------------

ubuntu@ubuntu:/dev/disk/by-id$ sudo zpool import -d /dev/disk/by-id
pool: timo
id: 8476649544359099174
state: UNAVAIL
status: One or more devices are missing from the system.
action: The pool cannot be imported. Attach the missing
devices and try again.
see: http://www.sun.com/msg/ZFS-8000-3C
config:


timo
UNAVAIL insufficient replicas

raidz1
UNAVAIL insufficient replicas
dsk/
c6d0s0 UNAVAIL
cannot open
disk/by-id/scsi-1ATA_WDC_WD10EADS-00L5B1_WD-WCAU46136696-
part1 ONLINE
dsk/c8d0s0

------------------------------------------------------------------------------------------------------

In OpenSolaris "zpool" shows a pool "timo" consisting of the three
devices c6d0, c6d1 and c8d0.

Does anybody have an idea how to get it working under Linux again (I
hope so, because it definitely worked until the system freeze and
reset) or how to get further (debugging) information from zfs-fuse?

Thank you in advance!
Timo

Fajar A. Nugraha

unread,
Apr 6, 2009, 8:43:33 AM4/6/09
to zfs-...@googlegroups.com
On Sat, Apr 4, 2009 at 3:05 AM, Timo Holle <timo....@googlemail.com> wrote:
> ubuntu@ubuntu:/dev/disk/by-id$ sudo zpool import -d /dev/disk/by-id
>  pool: timo
>    id: 8476649544359099174
>  state: UNAVAIL
> status: One or more devices are missing from the system.
> action: The pool cannot be imported. Attach the missing
>    devices and try again.
>   see: http://www.sun.com/msg/ZFS-8000-3C
> config:
>
>
> timo
> UNAVAIL  insufficient replicas
>
> raidz1
> UNAVAIL  insufficient replicas
>        dsk/
> c6d0s0                                                      UNAVAIL
> cannot open
>        disk/by-id/scsi-1ATA_WDC_WD10EADS-00L5B1_WD-WCAU46136696-
> part1  ONLINE
>        dsk/c8d0s0

This is weird, as it shows dsk/c6d0s0 and dsk/c8d0s0 inside ubuntu.
You might want to try:
- boot using opensolaris, export the pool cleanly
- boot ubuntu, but do not start zfs-fuse yet
- look at dmesg, make sure it detects solaris' slice, note its
partiton (e.g. sdb2)
- delete /etc/zfs/zpool.cache on ubuntu
- try "zpool import" (without -d).

Good luck.

Regards,

Fajar

Timo Holle

unread,
Apr 6, 2009, 2:17:47 PM4/6/09
to zfs-fuse
Hello Fajar and thank you four your hints.


> You might want to try:
> - boot using opensolaris, export the pool cleanly
> - boot ubuntu, but do not start zfs-fuse yet
> - look at dmesg, make sure it detects solaris' slice, note its
> partiton (e.g. sdb2)
> - delete /etc/zfs/zpool.cache on ubuntu
> - try "zpool import" (without -d).

After not getting it to work, I now decided do backup my data and
create a new pool.
I think I messed things up during the system freeze described in my
first post.

Also I will stick very closely to the recommendations (use partitions,
not entire disks), though it worked at the beginning with entire
disks.

Regards,
Timo
Reply all
Reply to author
Forward
0 new messages