Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#37154 - [util-linux] losetup does not accept offsets, that isn't 512*n byte
Attached to Project:
Arch Linux
Opened by Dikiy (dikiy) - Monday, 30 September 2013, 23:52 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 01 October 2013, 14:51 GMT
Opened by Dikiy (dikiy) - Monday, 30 September 2013, 23:52 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 01 October 2013, 14:51 GMT
|
DetailsDescription:
When I try to mount an image with a 32-byte offset mount -o loop,offset=32 test.iso /var/tmp/mount_dir I got mount: test.iso: failed to setup loop device: Numerical result out of range or with losetup: losetup: test.iso: failed to set up loop device, offset is not 512-byte aligned. Additional info: util-linux 2.32.2-1 Steps to reproduce: sudo mount -o loop,offset=32 test.iso mount_dir or losetup -o 32 /dev/loop0 test.iso But util-linux 2.20 seems to work. |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 01 October 2013, 14:51 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed upstream for 2.24
Tuesday, 01 October 2013, 14:51 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed upstream for 2.24
Comment by Karel Zak (kzak) -
Tuesday, 01 October 2013, 13:58 GMT
This is bug in extra check that we have in losetup code to detect non-synced loop devices. Fixed by upstream commit a7d5202b5e49b7e33336818e00d240b8badddbb7.