Skip to content

Conversation

@jkirk
Copy link
Contributor

@jkirk jkirk commented Jul 25, 2018

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.

@jkirk jkirk requested a review from mika July 25, 2018 16:07
Copy link
Member

@mika mika left a 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 :(

jkirk added a commit to jkirk/grml-debootstrap that referenced this pull request Jul 25, 2018
This was detected by spellsheck via Travis CI.

Also do not match the first partition only to be able to install any
other (single digit) partition in the future (as pointed out by @mika in
PR grml#112).
@jkirk
Copy link
Contributor Author

jkirk commented Jul 25, 2018

This time you got the code update before I was able to comment.. :)

Copy link
Contributor Author

@jkirk jkirk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review done.

Copy link
Contributor Author

@jkirk jkirk left a 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... :)

@jkirk jkirk force-pushed the jkirk/kpartxworkaround branch from 4173daa to 77e7d77 Compare July 27, 2018 14:12
jkirk added a commit to jkirk/grml-debootstrap that referenced this pull request Jul 27, 2018
This was detected by spellsheck via Travis CI.

Also do not match the first partition only to be able to install any
other (single digit) partition in the future (as pointed out by @mika in
PR grml#112).
@jkirk
Copy link
Contributor Author

jkirk commented Jul 31, 2018

After talking to @mika, I will squash my last commit.

@jkirk jkirk force-pushed the jkirk/kpartxworkaround branch from 77e7d77 to 8a6b0ea Compare August 8, 2018 11:02
@jkirk
Copy link
Contributor Author

jkirk commented Aug 8, 2018

Rebased to current master and squashed the (now missing) commit, see: #112 (review)

@mika
Copy link
Member

mika commented Aug 9, 2018

Did you forget to squash d80bc92 + 8a6b0ea? Then I'm happy to do a git merge --no-ff origin/pr/112 :)

@jkirk jkirk force-pushed the jkirk/kpartxworkaround branch from 8a6b0ea to 1166e53 Compare August 18, 2018 21:59
@jkirk
Copy link
Contributor Author

jkirk commented Aug 18, 2018

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.

@jkirk jkirk force-pushed the jkirk/kpartxworkaround branch from 1166e53 to a421110 Compare November 14, 2018 15:40
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.
@jkirk jkirk force-pushed the jkirk/kpartxworkaround branch from a421110 to 33d0e7f Compare November 14, 2018 16:38
@mika mika merged commit 33d0e7f into grml:master Nov 14, 2018
@mika
Copy link
Member

mika commented Nov 14, 2018

Thanks :)

@jkirk jkirk deleted the jkirk/kpartxworkaround branch December 3, 2021 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants