Corporate Raid ZFS and FreeBSD root ZFS

For many years, we have been running ZFS on a single hardware RAID on dell poweredge. I know most people are against this, but ZFS’s snapshot/cloning, compression and flexible partitioning do us A good service is provided. Whenever the drive dies, dispatch a Dell technician (the server is in another state), he will confirm that the drive has an amber light, and then replace it.

Now we To take advantage of ZFS’s L2ARC/ZIL cache, we are seriously considering running ZFS on bare disks. The current dell RAID controllers (PERC H730/H330) do support pass-through. My remaining questions are:

>If the drive fails from ZFS, does it show an amber light on the front panel? This is important because the dispatched Dell technician may need to confirm that the drive is indeed faulty. Otherwise we may encounter Dell problems.
>Is anyone running ZFS on FreeBSD root? Is it in production quality? Any known issues?

You can use the LSI MegaCLI utility to control PERC H730 and H330, because both cards are Dell PERC marked LSI card.

Excellent articles and tutorials on how to do this at https://calomel.org/megacli_lsi_commands.html

I know that zfsonlinux has A ZFS Event Daemon (ZED) that you can use to cause specific events to occur on certain events (for example, when the drive dies, use MegaCLI to turn on the amber light of a specific slot).

IIRC, FreeBSD has a ZFSd that can do similar things, but I’m not an expert in FreeBSD so you can’t point out more information other than saying that the FreeBSD forum is full of useful suggestions and helpful people.

I suspect that the most difficult part of doing this is figuring out what the MegaCLI “slot” number of a given drive is, because ZFS only knows the device node/name, and there is no specific LSI or PERC information. If the device node name matches the card and The slot number is directly related, it may be a trivial conversion…otherwise, it may be very difficult.

Even if you have to manually use MegaCLI to turn on the amber light of the case when the drive fails to meet Dell technology The program expects that you can still better provide ZFS raw drives instead of overwriting ZFS on top of the hardware raid-by doing this you lose most of the important functions of ZFS, which are the most important functions (e.g., error detection and data Correction).

For years, we have been running ZFS on a single hardware RAID on dell poweredge. I know most people are against this, but ZFS is a snapshot/clone , Compression and flexible partitioning provide us with a good service. Whenever the drive dies, send a Dell technician (the server is in another state), he will confirm that the drive has an amber light, and then replace it.

p>

Now we want to take advantage of ZFS’s L2ARC/ZIL cache, and we are seriously considering running ZFS on bare disks. The current dell RAID controllers (PERC H730/H330) do support pass-through. My remaining questions are:

>If the drive fails from ZFS, does it show an amber light on the front panel? This is important because the dispatched Dell technician may need to confirm that the drive is indeed faulty. Otherwise we may encounter Dell problems.
>Is anyone running ZFS on FreeBSD root? Is it in production quality? Any known issues?

You can use the LSI MegaCLI utility to control PERC H730 and H330, because these two cards are LSI cards marked by Dell PERC.

Excellent articles and tutorials on how to do this at https://calomel.org/megacli_lsi_commands.html

I know that zfsonlinux has a ZFS Event Daemon (ZED), you can use It is used to cause specific events to occur on certain events (for example, when the drive dies, use MegaCLI to turn on the amber light of a specific slot).

IIRC, FreeBSD has a ZFSd that can do similar things, But I’m not an expert on FreeBSD so you can’t point out more information other than saying that the FreeBSD forum is full of useful suggestions and helpful people.

I suspect that the most difficult part of doing this is figuring it out What is the MegaCLI “slot” number of a given drive, because ZFS only knows the device node/name, and there is no specific LSI or PERC information. If the device node name is directly related to the card and slot number, it may be a trivial one Conversion… Otherwise, it may be very difficult.

Even if you have to manually use MegaCLI to turn on the amber light of the case when the drive fails to meet the expectations of the Dell technology program, you can still better provide ZFS The original drive instead of overwriting ZFS on top of the hardware raid-by doing this you lose most of the important functions of ZFS, which are the most important functions (for example, error detection and data correction).

< p>

Leave a Comment

Your email address will not be published.