it appears that if I let the system continue booting, the remaining /dev/md*s do get populated, which makes me suspicious of my /etc/rc*.d/ ordering...
On Wed, Aug 26, 2009 at 12:03 PM, martin f krafft <madd...@debian.org>wrote: > also sprach Derek Bosch <smi...@gmail.com> [2009.08.26.2020 +0200]: > > 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, > > File a bug, please. > > I doubt this has to do with auto-read-only, which is just a symptom > because the filesystem probably doesn't get mounted, hence the array > is not written and thus stays auto-read-only. The real issue is why > the node doesn't get renamed like it should. > > -- > .''`. martin f. krafft <madd...@d.o> Related projects: > : :' : proud Debian developer http://debiansystem.info > `. `'` > http://people.debian.org/~madduck<http://people.debian.org/%7Emadduck> > http://vcs-pkg.org > `- Debian - when you have better things to do than fixing systems > > all software projects are done by iterative prototyping. > some companies call their prototypes "releases", that's all. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEAREDAAYFAkqVhwgACgkQIgvIgzMMSnXD8gCfcxX2nCpOmjSJ8SftUZXPAZwV > E7wAoIfIHwCFShsF1hWb0958Naof0eV9 > =HGNp > -----END PGP SIGNATURE----- > >
