Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#500 closed defect (fixed)

SW RAID1, lilo, mdadm and new metadata format

Reported by: petr.balas Owned by: bruno
Priority: normal Milestone: 3.0.2
Component: mondo Version:
Severity: normal Keywords: lilo, raid, raid1, mdadm, metadata


boot partition on SW RAID1, lilo used as bootmanager. After restore lilo failed to run. Problem is with metadata version of newly created RAID. mdadm prefers to create RAIDs with new metadata format but lilo is compatible only with metadata format 0.90. mdadm needs to be run with "-e 0.90" switch to force it to create old metadata format. At least on boot partition.

Change History (4)

comment:1 Changed 6 years ago by bruno

  • Status changed from new to assigned

Lots of commonality with #473 no ?

What woul be your answer to the question asked there ?

comment:2 Changed 6 years ago by petr.balas

I'm more than happy with forcing 0.90 metadata everywhere :-). And this is quick and dirty solution but it works.

The correct long term solution is remember metadata format at backup time and restore with this format.

mdadm version above 3.1 supports old metadata format (at least my 3.1.4 version in Debian stable does). I beliewe nobody plans to remove its support. Only change is selection of default format.

MDADMVER - I don't think it's usable. I can switch to console at correct moment, stop RAID array, recreate it with metadata 0.90, switch back and continue with restoration of all data. If you want to do this type of workaround do it so it's can be specified at backup time.

comment:3 Changed 5 years ago by bruno

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed with rev [2928].

You're right that a better solution is to support the metadata format and store it. That's work for version 4.x of MondoRescue ;-)

Last edited 5 years ago by bruno (previous) (diff)

comment:4 Changed 5 years ago by bruno

  • Milestone changed from 3.0.0 to 3.0.2

metadata are now restored as they were originally with rev [2991]. Will be in 3.0.2.

Note: See TracTickets for help on using tickets.