On 2/10/22 16:44, Tomas Kuchta wrote:
On Thu, Feb 10, 2022, 18:55 Rich Shepard <rshep...@appl-ecosys.com> wrote:
On Thu, 10 Feb 2022, Bill Barry wrote:
I don't know how far into setting this up, but you might want to
consider a ZFS mirror instead of the mdadm raid1.
Bill,
The 'create' function's been running about 2 hours so far. Now that I've
dug
deep into mdadm (having to redo the array several times due to hdd
failures)
I'm comfortable using it.
It could be a little easier to manage.
Once I get it set up again and it's accepting input from my dirvish
backups,
rather than stuffing / to its gills, I don't expect to need to manage it
unless one of the new WD Red NAS disks fails.
Thanks for the suggestion, though. I had gotten away from deep dives into
hardware and software over the past few years and I don't mind getting back
to it and learning new things.
.
You should start using UUIDs rather than /dev/sd* especially when having
the disks hanging outside the actual PC. .... of course they can randomly
change letters causing things to go south.
I would expect that this would be clear after long mailing list sagas of
similar trouble with John's Mediasonic, or whatever the actual disk holding
contraption....
-T
+1
Using UUIDs should prevent much of this grief. For example, here's a
line from mdadm.conf on one my my machines:
ARRAY /dev/md0 level=raid1 num-devices=2
uuid=77c98cce:1768e666:b78530e9:957e7034
IIRC, mdraid will scan the superblocks of the disks looking for this
UUID. Any matching UUIDs will be made part of the array.
*NOTE:* the UUID shown here is the mdraid UUID, which should not be
confused with the UUID of the filesystem residing on /dev/md0, or any
other possible UUID that might be found in the system.
galen
--
Galen Seitz
gal...@seitzassoc.com
