Hi. On Tue, Dec 29, 2020 at 07:58:50AM +0100, Thomas A. Anderson wrote: > I have been "using" mdadm to run software raid1 (stripping) on a file > server i have been running.
RAID1 is mirroring. Stripping is RAID0. RAID1 provides redundancy. RAID0 does not. > It is only now that I wonder if I am even using RAID1 properly? In > other words, now that I try to access data on these two original > drives on another system, I am unable to. I assume it's possible > (albeit doesn't seem intuitively simple -- at least for me), makes me > wonder if it's enen supposed to be used like this. It's possible for RAID1, it's impossible for RAID0. Which brings me to the question - cat /proc/mdstat . What does it show for you? > So, I ask a more precise question: Is mdadm designed to be used on other > system, and simply access data? As long as you have all the drives, any mdadm array should be able to assemble and provide you the access to its contents on that other system. If you do not have all the drives but have RAID that provides redundancy it's usually possible to convince mdadm to assemble a degraded array and therefore access its contents. > Maybe I just need two drives, and just do a cron job to rysnc to backup > once a week or something. RAID is not a substitute for a backup. Backup is not a substitute for mirroring. One does not exclude another, so use both. Reco
