[lustre-discuss] mkfs.lustre for ZFS draid

Cameron Harr harr1 at llnl.gov
Thu Feb 6 08:01:39 PST 2025


Like Laura, we do one draid pool and one OST per OSS node. Having 
multiple redundancy groups in the draid doesn't give you multiple block 
devices; it's still a single pool and device. You could create multiple 
pools, but then you are perhaps defeating some of the reasons to use draid.

On 2/6/25 06:40, Laura Hild wrote:
>> But how can I address them when running mkfs.lustre, if I still want to get 7 OSTs out of it?
> When we started using draid, we went from having six ten-disk OSTs per OSS to one sixty-disk OST per OSS.  I'm unsure why one would want seven OSTs on a single pool, being that if the pool becomes degraded all the OSTs would with it.  It would be as if you made a pool with seven raidz2 vdevs and created seven datasets.  The datasets do not correspond to individual vdevs, but rather all of the datasets use all of the vdevs.
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> https://urldefense.us/v3/__http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org__;!!G2kpM7uM-TzIFchu!xgZIVKZ7i1qH333bOgoPKfN-RxtYeTFzbP612qRqzzBCPiDbfdyPU3sUrBfPM4yhQMwV8xt9zA$


More information about the lustre-discuss mailing list