• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

ZFS (bsd) cross controller reboot

M

madrebel

Gawd
Joined
Sep 23, 2011
Messages
724
I'm hoping someone has run into this problem.

i'm using 2 aoc-sat2-mv8 controllers with 15 identical hitachi ultrastar 750GB drives running 8.2-STABLE zfs 5/28 for the pools.

the problem is if i create a raid6 vdev across these controllers the system instantly reboots if i try writing to the vdev. if i create a mirror across the controllers, i can run a DD type file creation for a minute or so then the system crashes.

i can create a cross controller raid0 with all 15 drives and it works fine.

i can create raidz2 vdevs on each controller and these work fine. if i use the exact same drives that just worked fine in a nested raidz2 (raid60) again, instant crash.

i have a similar setup in another server using WD RE4 1TB drives working fine cross controllers, same aoc-sat2-mv8 controller type and that works great.

any ideas how i can track down the cause of this?
 
ZFS does not support nested raidz(?). It only supports raidz1, raidz2, raidz3 and mirror. Nothing else. You can not use combinations of those.
 
yes it does. you can even nest a completely different raidz level. it would be stupid, but you can do it.
 
I like how misunderstanding and misinformation is spoiling a thread.. NOT.

First, whether ZFS supports nesting different RAID levels, e.g. mirror of raidz is not even a question since that's not what the OP did. I don't know why it's brought up.

Second, ZFS in fact does NOT support nested vdevs. All you could do is RAID 10, 50, 60 etc. by adding vdevs to a pool, so the OP followup was wrong as well.

What the OP did is pretty normal stuff and crashes are certainly not normal. I don't knopw why it crashes, it just bothers me that people just skim posts and write completely irrelevant stuff.
 
Last edited:
Sounds like either a problem with one of the drives on one of the controllers or a problem with the controller itself.

I think there is a command you can run to see read/write errors logged for each drive which don't necessarily boot the drive from the array.

Hopefully somebody can tell you the command to run.....
 
To be fair, tcm, the OP DID use the word nested, although I think he meant concatenated vdevs.
 
look, if i add a raidz2 to an existing raidz2 array for all intents that is nesting/raid60.
 
I agree, TCM. "Nesting" means to put something inside something else. Not after or in addition to.
 
I am unimpressed. Because some guy with a blog apparently doesn't understand the definition of the word 'nested', the definition is what it is.
 
http://en.wikipedia.org/wiki/Nested_RAID_levels

There are two examples on that page that ZFS does not support and both of them have raid3 in them. everything else on that page is supported in zfs.

pick nits all you want on the wording, its nesting. call it striping across parity sets if you want idfc.

*edit* make that 3 ... i don't think zfs has a raid100 equivalent. Although you might be able to do this if you create a r10 pool on another machine, export it, then import it to an existing identical raid10 that ... might work but idk.
 
danswartz said:
I am unimpressed. Because some guy with a blog apparently doesn't understand the definition of the word 'nested', the definition is what it is.
Click to expand...
True.

ZFS does not support nested raid. You can not create a bunch of mirrors, and then create a raidz2 of all the mirrors. You can not create a raid, consisting of smaller raid. You can not put a vdev, inside another vdev.

But, you can add another vdev to a zpool But that is expanding the zpool. You are not putting a vdev inside another vdev. You are putting them, side by side.

Please dont confuse people using the word "nested" because ZFS does not support nested raid configurations.



EDIT: In case you dont believe us:
http://en.wikipedia.org/wiki/Zfs#Limitations
"Vdevs cannot be nested, so a mirror or RAID-Z top-level vdev can only contain files or disks. Mirrors of mirrors (or other combinations) are not allowed."
 
Unfortunately, it appears some sites misuse the word 'nested' in connection with RAID levels, so I understand how the confusion arose.
 
You must log in or register to reply here.
Back
Top