![]() Should be close to the best of both worlds. I think my next array is going to be a little more bleeding edge and use btrfs. It also doesn't allow online capacity expansion, like mdadm. I'm not nearly as familiar with ZFS as I am with mdadm, so it makes me a little nervous. That led me to ZFS and data checksums, which are completely awesome. Unfortunately, I also had a drive dying slowly with lots of bad sectors silently corrupting data for months. ![]() You can stop and restart the array with another -assume-clean and another guess at order until the file system is valid without problem. You just have to get the order of the drives right when you pass in the devices else the file system is corrupt. ![]() Calling madam -assume-clean was the ticket. I just had to convince madam they weren't half spares. Since the array wasn't just degraded, it was down, there were no changes made. The worst that happened to me is when I had drives split between multiple SATA controller cards, and one of the controller cards flaked out and dropped half the drives in my RAID 5 array all at once. Having to stop an array that wasn't quite there before forcing it to show up probably would have taken me awhile to figure out, too. It would never have crossed my mind to look for a Windows tool to access them. I never had any doubt that if the NAS itself failed, but not the drives, that I could just plug them into another machine and have access to everything. I was explicit about RAID 5 because I had manually run arrays in mdadm for a while and noticed that's all it was when I logged into a shell on the NAS.
0 Comments
Leave a Reply. |