It looks like this was fixed some time ago.
** Changed in: util-linux (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/313385
Title:
losetup 32bit offset
So, I think the issue I've been having *may* be related.
I store a bunch of junk on an LVM and I needed to expand that a bit. So
I created a virtual disk using dd and losetup to expand my LVM.
Everything seems fine, but after some case that I'm having a hard time
identifying, I cease to be able
Ohh yeah, and I'm on AMD64 8.10
--
losetup 32bit offset limit, hangs on retry, remains defunct
https://bugs.launchpad.net/bugs/313385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
your logs seem to indicate that there is a problem with samba (keywords
cifs, smbd). how do you use samba in respect to the lvm device?
i also don't really understand why you need to use a virtual disk to
expand a LVM (but i probably won't be able to help you anyway..).
what commands did you
There are other keywords, like one of those backtraces comes out of an
instance of rm.
My LVM was full and I had another drive that was already doing something
else. I used dd to make a file that I'm using an extra storage space on
the LVM.
losetup is what connects that file to the file system
** Summary changed:
- losetup 32bit offset limit, hang, remaining defunct
+ losetup 32bit offset limit, hangs on retry, remains defunct
** Description changed:
Binary package hint: util-linux
i made a dd image of my laptop drive and try to work with it (mount,
resizing etc).
#
** Description changed:
Binary package hint: util-linux
i made a dd image of my laptop drive and try to work with it (mount,
resizing etc).
# losetup -a
/dev/loop0: [fe01]:29253634 (/image.dd)
# fdisk -lu /dev/loop0
Disk /dev/loop0: 60.0 GB, 60011642880 bytes
240
