[opensuse] oS 13.2: losetup not working - permission denied?
I know I've used loopback mounts on openSUSE before, but today they aren't working for me. As an example: === + ls -l /mnt-ewf/ewf1 -r--r--r-- 1 root root 1000555581440 Dec 3 16:33 /mnt-ewf/ewf1 + sudo /usr/sbin/losetup /dev/loop0 /mnt-ewf/ewf1 -o 209735680 root's password: losetup: /mnt-ewf/ewf1: failed to set up loop device: Permission denied === I have the loop module loaded:
sudo /sbin/lsmod | grep loop loop 28312 0
I tried "modprobe loop" just in case, but it doesn't help. What am I forgetting? Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Dec 3, 2014 at 4:36 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
I know I've used loopback mounts on openSUSE before, but today they aren't working for me.
As an example:
=== + ls -l /mnt-ewf/ewf1 -r--r--r-- 1 root root 1000555581440 Dec 3 16:33 /mnt-ewf/ewf1 + sudo /usr/sbin/losetup /dev/loop0 /mnt-ewf/ewf1 -o 209735680 root's password: losetup: /mnt-ewf/ewf1: failed to set up loop device: Permission denied ===
I have the loop module loaded:
sudo /sbin/lsmod | grep loop loop 28312 0
I tried "modprobe loop" just in case, but it doesn't help.
What am I forgetting?
Thanks Greg -- Greg Freemyer
This just gets stranger. I've found that if use a true file to loopback mount from, then all is good. Instead I'm using a virtual block device to mount. In past versions of openSUSE I could do that and it worked fine. [to be more explicit I'm using ewfmount to leverage the fuse kernel subsystem to create a single non-segmented, non-compressed dd image from a segmented / compressed image. I've done this many times before but with 13.1 and older.] With opensuse 13.2, it is failing. I'm wondering if something in the kernel changed. I have no idea how to troubleshoot this. Thoughts? Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Greg Freemyer wrote:
On Wed, Dec 3, 2014 at 4:36 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
I know I've used loopback mounts on openSUSE before, but today they aren't working for me.
As an example:
=== + ls -l /mnt-ewf/ewf1 -r--r--r-- 1 root root 1000555581440 Dec 3 16:33 /mnt-ewf/ewf1 + sudo /usr/sbin/losetup /dev/loop0 /mnt-ewf/ewf1 -o 209735680 root's password: losetup: /mnt-ewf/ewf1: failed to set up loop device: Permission denied
a guess: maybe you need losetup -r because the file is read-only even to root? if that doesn't help... strace and/or ltrace and find the call that is failing...? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I On December 4, 2014 8:19:44 PM EST, Linda Walsh <suse@tlinx.org> wrote:
Greg Freemyer wrote:
On Wed, Dec 3, 2014 at 4:36 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
I know I've used loopback mounts on openSUSE before, but today they aren't working for me.
As an example:
=== + ls -l /mnt-ewf/ewf1 -r--r--r-- 1 root root 1000555581440 Dec 3 16:33 /mnt-ewf/ewf1 + sudo /usr/sbin/losetup /dev/loop0 /mnt-ewf/ewf1 -o 209735680 root's password: losetup: /mnt-ewf/ewf1: failed to set up loop device: Permission denied
a guess: maybe you need losetup -r because the file is read-only even to root?
if that doesn't help... strace and/or ltrace and find the call that is failing...?
Day late and a dollar short. By default a filesystem created by a normal user has zero access by root, not even read only. You have to first create a /etc/fuse.conf and set a config option then pass an extra arg to fusemount to give root access. I find it against the Linux tradition, but it is what it is. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Greg Freemyer -
Linda Walsh