From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "loop device recursion avoidance" patch causes difficulties
Date: Wed, 18 May 2005 17:27:17 -0400 [thread overview]
Message-ID: <428BB335.9060204@tmr.com> (raw)
In-Reply-To: <73e1f59805051704216bc4c78f@mail.gmail.com>
Luboš Doležel wrote:
> Hello,
>
> I've created a bugreport at http://bugme.osdl.org/show_bug.cgi?id=4472
> and I was advised to write to this list.
>
> A patch called "loop device recursion avoidance" which appeared in
> 2.6.11 kernel has complicated ISO image mounting from another mounted
> media.
>
> Example:
>
> # mount /mnt/dvd
> # mount -o loop /mnt/dvd/file.iso /somedir
>
> The mount command produces this error: "ioctl: LOOP_SET_FD: Invalid argument".
>
> This operation maybe is a kind of recursion but I think that recursion
> should be limited - not disabled.
> Now I have to copy the ISO image to my hdd before mounting. I used to
> put CD backups on DVDs; now it's more complicated to use.
Far worse than complicated, it just doesn't work... I'm glad you found
this before I did, I have loads of similar things, created when a number
of small system were decomissioned and each partition was written raw
as a file. Like:
machineA/part1
machineA/part2
machineB/part1
and similar. These were all 525MB drives, but the data is moderately
critical. I've been successful mounting with all older kernel, except
the SysVR4 images, which have a filesystem Linux can't handle (from
Dell's brief adventure with SysVR4). Now it appears that I will have to
copy the data to a drive to use it, which is a minor pain since the
process is in scripts.
Another case of fixing a problem without completely understanding it, I
fear. At least one machine had a partition with floppy images, I hope
they weren't loop mounting them, although it's likely they just burn a
fresh floppy when needed (boot disks for control PCs).
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2005-05-18 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 11:21 "loop device recursion avoidance" patch causes difficulties Luboš Doležel
2005-05-18 21:04 ` Andrew Morton
2005-05-19 11:16 ` Luboš Doležel
2005-05-18 21:27 ` Bill Davidsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=428BB335.9060204@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox