Hi Cindy,
> I don't think the force import of a degraded pool would cause the pool
> to be faulted. In general, the I/O error is caused when ZFS can't access the
> underlying devices. In this case, your non-standard devices names
> might have caused that message.
as I wrote in my first mail, zpo
Hi Christian,
Yes, with non-standard disks you will need to provide the path to zpool
import.
I don't think the force import of a degraded pool would cause the pool
to be faulted. In general, the I/O error is caused when ZFS can't access
the underlying devices. In this case, your non-standard d
Hi Cindy,
> Can you provide the commands you used to create this pool?
I don't have them anymore, no. But they were pretty much like what you wrote
below.
> Are the pool devices actually files? If so, I don't see how you
> have a pool device that starts without a leading slash. I tried
> to creat
Hi Hans-Christian,
Can you provide the commands you used to create this pool?
Are the pool devices actually files? If so, I don't see how you
have a pool device that starts without a leading slash. I tried
to create one and it failed. See the example below.
By default, zpool import looks in the
Hi,
I've been playing around with zfs for a few days now, and now ended up with a
faulted raidz (4 disks) with 3 disks still marked as online.
Lets start with the output of zpool import:
pool: tank-1
id: 15108774693087697468
state: FAULTED
status: One or more devices contains corrupted da
