Greetings All,
I can't believe it didn't figure this out sooner. First of all, a big thank
you to everyone who gave me advice and suggestions, especially Richard. The
problem was with the -d switch. When importing a pool if you specify -d and
a path it ONLY looks there. So if I run:
# z
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Andrew Kener
>
> According to 'zpool upgrade' my pool versions are are 22. All pools
> were upgraded several months ago, including the one in question. Here
> is what I get when I try to impo
According to 'zpool upgrade' my pool versions are are 22. All pools were
upgraded several months ago, including the one in question. Here is what I get
when I try to import:
fileserver ~ # zpool import 9013303135438223804
cannot import 'tank': pool may be in use from other system, it was last
erm. using a file on another pool (your zpool) for the SLOG is NOT a good
idea. Use an SSD or two (a mirror) or let ZFS deal with the ZIL on the drives.
roy
Hello All,
I've recently run into an issue I can't seem to resolve. I have been running a
zpool populated with two RAID-Z1
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Andrew Kener
>
> the OS hard drive crashed [and log device]
Here's what I know: In zpool >= 19, if you import this, it will prompt you
to confirm the loss of the log device, and then it will
Hello All,
I've recently run into an issue I can't seem to resolve. I have been
running a zpool populated with two RAID-Z1 VDEVs and a file on the
(separate) OS drive for the ZIL:
raidz1-0 ONLINE
c12t0d0 ONLINE
c12t1d0 ONLINE
c12t2d0 ONLINE
c12t3d0 ONLINE
raidz1-
