-
-
Notifications
You must be signed in to change notification settings - Fork 32
Improve cleanup of loop devices #112
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
Conversation
mika
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also s/devmappings/device mappings/ in commit message
PS: thanks for working on this, I know what horrible yak shavery this is :(
|
This time you got the code update before I was able to comment.. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. Using "%p*" now... :)
4173daa to
77e7d77
Compare
|
After talking to @mika, I will squash my last commit. |
77e7d77 to
8a6b0ea
Compare
|
Rebased to current master and squashed the (now missing) commit, see: #112 (review) |
8a6b0ea to
1166e53
Compare
|
Actually I did not "forget" to squash the commits. I wanted to keep the second one to make it visible that the issue was detected by spellsheck via the cool new Travis CI integration. But anyway, I squashed it now. |
1166e53 to
a421110
Compare
kpartx (sometimes) does not cleanup the loop devices when deleting the partition devmappings. This is a known bug, see Debian Bug #891077. This is change is a possible workaround for that issue. Now aborting grml-debootstrap is possible without leaving unneded loop devices behind.
a421110 to
33d0e7f
Compare
|
Thanks :) |
kpartx (sometimes) does not cleanup the loop devices when deleting the
partition devmappings. This is a known bug, see Debian Bug #891077.
This is change is a possible workaround for that issue.
Now aborting a grml-debootstrap is possible without leaving unneded loop
devices behind.