On Tue, 8 Jun 2010 12:37:38 +0200
martin f krafft wrote:
> also sprach Martin Michlmayr [2010.06.08.1124 +0200]:
> > > It would be safer to use
> > >mdadm -As
> > > to ensure all arrays are assembled, then
> > >mdadm -Ds
> > > to create mdadm.conf
> > >
> > > ... but why do you even wan
also sprach Martin Michlmayr [2010.06.08.1124 +0200]:
> > It would be safer to use
> >mdadm -As
> > to ensure all arrays are assembled, then
> >mdadm -Ds
> > to create mdadm.conf
> >
> > ... but why do you even want to create mdadm.conf ???
>
> I'll let madduck answer this.
I have not y
* Neil Brown [2010-06-08 08:57]:
> > When I run:
> > mdadm --examine --scan --config=partitions
> > I get:
> > ARRAY /dev/md/0 metadata=1.2 UUID=afb5fddc:1e5a383b:246bf8de:7f52a209
> > name=debian:0
> > i.e. the /dev/md/0 form. (Also note that that the UUID in the map
> > file is differe
On Mon, 7 Jun 2010 16:25:47 +0100
Martin Michlmayr wrote:
> * martin f krafft [2010-05-26 10:31]:
> > also sprach Neil Brown [2010.05.26.1016 +0200]:
> > > The most likely explanation for this is that /var/run/mdadm/map existed
> > > and
> > > contained and entry for 'md0' declaring that it co
So I briefly booted into the last stable release of Debian to see why
it works. The difference here is that mdadm shows /dev/mdX device
names by default (there was no map file in /var/run):
/var/run # mdadm --examine --scan --config=partitions
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=01
5 matches
Mail list logo
