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.

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

Resolve Issue 851: Fix problem with UUIDs on Fedora by using mkfs to … #854

Merged
merged 1 commit into from Jun 1, 2016

Conversation

exedor
Copy link
Contributor

@exedor exedor commented May 30, 2016

…set them instead of tune2fs.

I'm still not entirely sure why this the case, but there must be a bug in the filesystem utilities or maybe filesystem changes are cached and not committed to disk before initrd is created. For some reason when mkfs and tune2fs are used separately to retain the original filesystem UUIDs the initrd created at the end of the restore remembers and retains the original incorrect and temporary UUIDs generated by the call to mkfs...at least it does on Fedora Core 21 and maybe later resulting in a failure to boot after restore due to dracut failing to locate the filesystem with the incorrect UUIDs. This pull request avoids the use of temporary UUIDs by having mkfs use the original UUIDs directly when they are present. I've tested it and it does in fact fix the issue in a way that should not break other platforms.

@gdha gdha added the enhancement Adaptions and new features label Jun 1, 2016
@gdha gdha self-assigned this Jun 1, 2016
@gdha gdha added this to the Rear v1.19 milestone Jun 1, 2016
@gdha gdha merged commit adcc2de into rear:master Jun 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adaptions and new features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants