3 ms·
> One thing that I would add is avoid mdadm like the plague. Its tricky, poorly documented and requires a whole bunch of other crap tools to make it work. Do y
by derefr 6y ago
> One thing that I would add is avoid mdadm like the plague. Its tricky, poorly documented and requires a whole bunch of other crap tools to make it work.
Do you feel that Linux MDRAID is a bad technology, or just a bad UX? I.e., are MDRAID-based appliances (like many NASes)—where all the sharp edges have been smoothed away—still bad in some fundamental way?
- joana035 6y agomdadm is just fine. YMMV depending on the distro you are using and your knowledge/know-how about storage. I recommend to try it out with loop devices, play around and build your own opinion about it.
- KaiserPro 6y agoOh no, its a fine technology, its just useless documentation and to make it really work you need LVM, which is just horrific to deal with. I should say that I've worked proffeshionally with ZFS, mdamd/pv/lvm gluster(ugh) lustre(ok) clustered xfs and GPFS. Along with a bunch of appliances. mdadm/pv/lvm is about the bottom three. After gluster and ceph.
- core-questions 6y agoI find LVM2 to be easy to work with, but the weird marriage between MD and LVM confuses me, so I just use "hardware" raid beneath LVM. (For server OS installs that I can recreate trivially, and not for actual data, which lives on a proper SAN because I value my employment)
- joana035 6y agoHow come mdadm needs lvm? Do you mean device mapper?
- KaiserPro 6y agoI don't mind device mapper, for what I used it for, multipath scsi. mdadm doesn't need lvm. But if you want snapshots, or to have flexible partitions (anything like the flexibility of zfs) you need lvm. Also for the longest time redhat used to force lvm on you by default. I assume this was to help with "flexibility" In practice, on virtual machines, or anything back with decent storage, I'd remove the partition table and just run on the block device directly.