Found it, this UI could really use some work
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63
How do i change tags?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63 characters
To manage notifications about this bug go to:
I can't seem to be able to change the state of the bug myself to
'tested' in any way. Everything's grayed out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with
I verified the bugs months ago, however i'm not familiar with how this
process here works and nobody reacted to my question.
The package works, please integrate it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not sure how the process here works, is this enough or do i need to
change some status somewhere?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths
Not sure how the process here works, is this enough or do i need to
change some status somewhere?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d
Tested the above scenario on vivid, appears to work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63 characters
To manage notifications
Tested the above scenario on vivid, appears to work
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63 characters
Thank you Mathieu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63 characters
To manage notifications about
Thank you Mathieu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63 characters
To manage notifications about this bug go to:
Looks like the upstream people don't seem to be very responsive to handle this
case. Is there any way to kick it forward?
Also, could ubuntu still fix this properly while redhat sits on it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Looks like the upstream people don't seem to be very responsive to handle this
case. Is there any way to kick it forward?
Also, could ubuntu still fix this properly while redhat sits on it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks Risto!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63 characters
To manage notifications about this bug go to:
Thanks Risto!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63 characters
To manage notifications about this
is the lo_name which gets stored in the loop_info structure actually
required to be an actual file path or is it enough to be an arbitrary
string identifier?
If it doesn't have to be a file path, could it be for instance a sha1
hash of the provided path? That fits into 40 chars and is relatively
is the lo_name which gets stored in the loop_info structure actually
required to be an actual file path or is it enough to be an arbitrary
string identifier?
If it doesn't have to be a file path, could it be for instance a sha1
hash of the provided path? That fits into 40 chars and is relatively
If i understand correctly, the fix is to compare only the first 63 chars
of the path.
With kpartx the precise file path matters in resolving the correct loop
device, the suggested solution has the following consequence:
Assuming all loop devices are available, these commands succeed and
mount
If i understand correctly, the fix is to compare only the first 63 chars
of the path.
With kpartx the precise file path matters in resolving the correct loop
device, the suggested solution has the following consequence:
Assuming all loop devices are available, these commands succeed and
mount
Public bug reported:
$ apt-show-versions multipath-tools
multipath-tools:amd64/vivid 0.4.9-3ubuntu12 uptodate
Reproduce:
Mount an image from a path longer than 63 chars succeeds:
$ sudo kpartx -av
asfd1asdf2asdf3asdf4asdf5asdf6asfd7asdf8asdf9asf10asdf11asdf12asdf13/disk.img
add map loop0p1
Public bug reported:
$ apt-show-versions multipath-tools
multipath-tools:amd64/vivid 0.4.9-3ubuntu12 uptodate
Reproduce:
Mount an image from a path longer than 63 chars succeeds:
$ sudo kpartx -av
asfd1asdf2asdf3asdf4asdf5asdf6asfd7asdf8asdf9asf10asdf11asdf12asdf13/disk.img
add map loop0p1
20 matches
Mail list logo
