> 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
> 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 /dev/dsk directory so
> you would need to include the -d /dir option to look in an
> alternative directory.
The pool devices are real devices. The naming scheme might be a bit… different,
Importing the pool did work with these names.
> I'm curious how you faulted the device because when I fault
> a device in a similar raidz1 configuration, my pool is only
> degraded. See below. Your pool is corrupted at a higher level.
> In general, RAID-Z redundancy works like this:
> raidz can withstand 1 device failure
> raidz2 can withstand 2 device failures
> raidz3 can withstand 3 device failures
Thats what I understood, and thats the reason for my mail to this list.
No important data is lost, as I was just playing around with raidz.
But I really want to know what happend.
After thinking about what I did, one thing came to my mind.
Might exporting a degraded pool cause this issue?
zfs-discuss mailing list