I've had a sid/unstable system with four raid1 / mdadm partitions running
for about 4 years now...
Recently, upon boot-up, three of those four partitions come up as
"auto-read-only" in /proc/mdstat
for example:
md3 : active (auto-read-only) raid1 sda4[0] sdb4[1]
        280631360 blocks [2/2] [UU]

this device DOESN'T appear in /dev/md3

however:
md2 : active raid1 sda3[0] sdb3[1]
        9767424 blocks [2/2] [UU]

isn't auto-read-only, and does appear as /dev/md2...

I'd like to reset the "auto-read-only" on /dev/md3, but /dev/md3 doesn't
exist.  Sometimes I've seen it show up as /dev/.tmp.md3,
but it isn't consistent...

where does it go?

-Derek

Reply via email to