Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

md disk uuid describtion incorrect #39

Closed
pavoldomin opened this issue Mar 29, 2012 · 1 comment
Closed

md disk uuid describtion incorrect #39

pavoldomin opened this issue Mar 29, 2012 · 1 comment
Assignees
@jhoekx
Labels
bug The code does not do what it is meant to do
Milestone
Rear v1.13.0

Comments

@pavoldomin
Copy link
Contributor

On our SUSE Linux Enterprise Server 11, the UUID for md device is incorrectly recoreded in disklayout.conf.
This is because "mdadm --misc --detail" (version v3.0.3) returns more than expected:

# mdadm --misc --detail /dev/md0 | grep UUID
           UUID : 80a392aa:98ef36b7:ebe0bac9:c579498f (local to host XXXXXXXX)

# grep md0 /var/lib/rear/layout/disklayout.conf
raid /dev/md0 level=raid1 raid-devices=2 uuid=80a392aa:98ef36b7:ebe0bac9:c579498f(localtohostXXXXXX) devices=/dev/mapper/3600508b4000ad7f5000070000adf0000_part1,/dev/mapper/3600508b4000ad7f30000a00008820000_part1

The recovery code therefore fails to build md array,
@ghost ghost assigned jhoekx Mar 29, 2012
jhoekx added a commit that referenced this issue Mar 30, 2012
@jhoekx
layout: fix md UUID
b9011f1 
On some systems the UUID line looked like:
UUID : 80a392aa:98ef36b7:ebe0bac9:c579498f (local to host XXXXXXXX)

Fixes issue #39 .
@jhoekx
Copy link
Contributor

jhoekx commented Mar 30, 2012

This should be fixed now. Please reopen if it isn't. Thanks for reporting.

@jhoekx jhoekx closed this as completed Mar 30, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhoekx jhoekx

Labels
bug The code does not do what it is meant to do
Projects
None yet
Milestone
Rear v1.13.0
Development

No branches or pull requests
2 participants
@jhoekx @pavoldomin