bugGNU GRUB - Bugs: bug #26720, Multiple metadata areas created...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #26720: Multiple metadata areas created for large LVM volumes are not supported

Submitter:  Andrew Oakley <adoakley>
Submitted:  Tue 02 Jun 2009 01:59:57 AM UTC
   
 
Category:  Disk & Partition Severity:  Major
Priority:  5 - Normal Item Group:  None
Status:  Fixed Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Closed Release:  None
Release:  svn trunk Reproducibility:  Every Time
Planned Release:  None

Tue 04 Aug 2009 07:57:30 AM UTC, comment #2: 

Fixed in r2457.

Felix Zielcke <fzielcke>
Group Member
Thu 11 Jun 2009 09:11:12 PM UTC, comment #1: 

Can you try removing this check and run grub-fsprobe? If it works I think we can remove this check

Vladimir Serbinenko <phcoder>
Group administrator
Tue 02 Jun 2009 01:59:57 AM UTC, original submission:  

GRUB fails (silently) when scanning LVM volumes that have multiple metadata areas (which is the default for "large" volumes).  GRUB checks that there is only a single metadata area, and rejects the volumes with multiple copies.  It is possible that simply removing the check is the right thing to do. 

You can set the number of LVM metadata areas using the --metadatacopies argument to pvcreate.  It looks like 0 metadata copies would also break GRUB, but that is less likely to happen (it's never the default). 

The offending code is at grub2/disk/lvm.c:276 revision 2238.

Andrew Oakley <adoakley>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by fzielcke (Posted a comment)
  • -email is unavailable- added by phcoder (Posted a comment)
  • -email is unavailable- added by adoakley (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-08-04 fzielcke Open/ClosedOpen Closed
        StatusNone Fixed

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code