RE: mdadm 3.1.1: level change won't start

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



	I never received a response on this one either.  Can anyone guess
why one of my systems would suddenly start claiming it doesn't recognize the
superblock versions?  The two systems are highly similar.

> > >> Three questions -
> > >>
> > >> 1. What does the stuff about "metadata format 1.10 unknown" mean?
> > >> Notice the "super 1.1" vs. "metadata 1.01" vs. "metadata format 1.10"
> > >> disrepancy between mdsat, --detail and --grow output.
> > >>
> > >> 2. Am I doing something wrong? :)
> > >>
> > >> 3. How can I get more info about what is causing the failure to
> > >> initialize the growth?
> > >>
> > >> Thanks!
> > >>
> > >> -- Kristleifur
> > >>
> > >>
> > >> (P.s., I'm cc-ing this directly to Neil Brown as the maintainer of
> > >> mdadm. I hope that isn't rude of me.)
> > >> --
> > >
> > >
> > > I thought there were three metadata variants for 1.x: 1.0 1.1 and 1.2
> > >  Maybe the extra 1 or 0 at the end refers to a reshape in progress?
> > >
> >
> > Thanks for the reply. FWIW, I intended the array to have metadata
> > format 1.1 when I created it. I've noticed these "1.01" messages
> > before, so I believe it's not due to the reshape. However, I'm
> > thinking the funny metadata might be interfering with the reshape
> > somehow.
> 
> 	I'm getting the same thing on one of my systems and not on the
> other:
> 
> RAID-Server:/etc/rcS.d# mdadm -V
> mdadm - v2.6.7.2 - 14th November 2008
> RAID-Server:/etc/rcS.d# mdadm --detail --scan
> ARRAY /dev/md0 level=raid6 num-devices=10 metadata=01.02 spares=1
> name=RAID-Server:0 UUID=5ff10d73:a096195f:7a646bba:a68986ca
> 
> Backup:/etc/initramfs-tools# mdadm -V
> mdadm - v2.6.7.2 - 14th November 2008
> Backup:/etc/initramfs-tools# mdadm --detail --scan
> mdadm: metadata format 01.02 unknown, ignored.
> mdadm: metadata format 01.02 unknown, ignored.
> mdadm: metadata format 01.02 unknown, ignored.
> mdadm: metadata format 01.00 unknown, ignored.
> ARRAY /dev/md0 level=raid5 num-devices=8 metadata=01.02 name='Backup':0
> UUID=940ae4e4:04057ffc:5e92d2fb:63e3efb7
> ARRAY /dev/md3 level=raid1 num-devices=2 metadata=01.02 spares=1
> name='Backup':3 UUID=3615c4a2:33786b6d:b13863d9:458cd054
> ARRAY /dev/md2 level=raid1 num-devices=2 metadata=01.02 spares=1
> name='Backup':2 UUID=d45ff663:9e53774c:6fcf9968:21692025
> ARRAY /dev/md1 level=raid1 num-devices=2 metadata=01.00 name='Backup':1
> UUID=d6a2c60b:7345e957:05aefe0b:f8d1527f
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux