Con­fig­ur­ing ZFS

OpenSource For You - - OPENGURUS LET’S TRY -

As men­tioned ear­lier, our in­stal­la­tion has just one hard drive. Let’s sup­pose that we need to add six more hard drives to our sys­tem.

Now, let us as­sume that we have fin­ished adding the six hard drives. But since none of them is par­ti­tioned, they are cur­rently un­us­able.

This is where the ben­e­fits of ZFS come in, free­ing us from the bur­den of cre­at­ing par­ti­tions (although we have the lib­erty of cre­at­ing these, if we want to).

Let’s now cre­ate a stor­age pool us­ing two of our hard drives: three drives and uses strip­ing to di­vide data across all the hard drives, with ad­di­tional par­ity data di­vided across all disks. If one of the hard drives dies, you won’t lose any of your data. RAID 5 of­fers data re­dun­dancy with a lower stor­age cost than RAID 1). RAID Z voids the ‘write hole’ by us­ing copy-on-write. If a sin­gle disk in your pool dies, sim­ply re­place that disk, and ZFS will au­to­mat­i­cally re­build the data based on par­ity in­for­ma­tion from the other disks. To lose all the in­for­ma­tion in your stor­age pool, two disks would have to die. To make things even more re­dun­dant, you can use RAID 6 (RAID-Z2 in the case of ZFS) and have dou­ble par­ity.

To achieve the above, run the fol­low­ing com­mand:

Newspapers in English

Newspapers from India

© PressReader. All rights reserved.