From: J Sloan <jjs@mirai.cx>
To: Jim Murray <jjm@jjm.com>
Cc: jeff@CYTE.COM, linux-kernel@vger.kernel.org
Subject: Re: 2.4.2 seems to break loopback and/or mount
Date: Thu, 22 Feb 2001 19:47:55 -0800 [thread overview]
Message-ID: <3A95DD6B.58771190@mirai.cx> (raw)
In-Reply-To: <Pine.LNX.4.30.0102222215190.8939-100000@light.jjm.com>
Red Hat 7.x running nicely on a number of machines
here w/ no problem, with all apologies to the Red Hat
bashers -
The real problem is loopback is broken, and the
fix still needs to be merged.
In the meantime, Jens Axboe's loop patches will
make it work -
ftp://ftp.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.2-pre4/
jjs
Murray wrote:
> On Thu, 22 Feb 2001 jeff@CYTE.COM wrote:
>
> Compiling with kgcc compiler from RedHat 7.0 breaks loopback in the
> way you describe on 2.4.2-prex kernels and I suspect also in the real 2.4.2.
>
> Jim
>
> > Please CC me on replies. I just joined the list and don't want
> > to miss any replies.
> >
> > I have been running 2.4.1-pre10 for quite some time with no
> > problems. I just upgraded to 2.4.2 and everything seem to work
> > fine until I did... (as root or course)
> >
> > mount -t iso9660 -o loop,ro mycdimage.iso /mnt/cdrom
> >
> > at which point the mount process hung in an uninterruptable sleep.
> > after that I can no longer successfully issue any other mount
> > commands, including non-loopback mounts. I can mount/unmount
> > regular partitions before mounting anything via loopback.
> >
> > Any ideas as to what is wrong?
> > The only thing I can think of is that my modutils is v2.3.19
> > but I doubt that is doing it as the loop module and other modules
> > are loaded fine.
> >
> > If anybody has an idea as to what I broke please let me know.
> > I will upgrade modutils tomorrow and see if the problem goes
> > away while I wait for a possibly more accurate response.
> >
> > Thank you,
> >
> > Jeff Wiegley
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> --
> Jim Murray jjm@jjm.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-23 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 1:22 2.4.2 seems to break loopback and/or mount jeff
2001-02-23 3:04 ` Mohammad A. Haque
2001-02-23 3:19 ` Jim Murray
2001-02-23 3:47 ` J Sloan [this message]
2001-02-23 3:51 ` Mohammad A. Haque
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=3A95DD6B.58771190@mirai.cx \
--to=jjs@mirai.cx \
--cc=jeff@CYTE.COM \
--cc=jjm@jjm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.