From: "David E. Weekly" <dweekly@legato.com>
To: <linux-kernel@vger.kernel.org>
Subject: "mount -o loop" lockup issue
Date: Mon, 26 Mar 2001 17:56:19 -0800 [thread overview]
Message-ID: <019501c0b661$1de195a0$5c044589@legato.com> (raw)
On Linux 2.4.2, running a "mount -o loop" on a file properly created with
"dd if=/dev/zero of=/path/to/my/file.img count=1024" seems to decide to
freeze up my shell (not my system). An strace showed the lockup happening at
the actual system "mount()" call, which never returns.
Since mount() is in glibc, it might be relevant to note that I'm running
Mandrake's glibc 2.1.3-16mdk. I compiled the kernel with a gcc of 2.95.3
[1991030] (although oddly enough this binary seems to have come with the
gcc-2.95.2 RPM and installed itself as /usr/bin/gcc-2.95.2) and binutils
2.10.0.24-4mdk.
I'm very sorry to post to this list, but several people independantly told
me that there was a loopback mountpoint deadlocking issue with 2.4.2 and
that I should check here. Of course, this could be a completely retarded
system configuration issue, in which case please shut me up and I'll go away
quietly. But if it is an issue with a known resolution I'd love to hear it -
I wasn't able to find resolution on the web or with several rather
knowledgeable people.
-david weekly [dweekly@legato.com]
next reply other threads:[~2001-03-27 1:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 1:56 David E. Weekly [this message]
2001-03-27 3:31 ` Jason Madden
2001-03-27 3:50 ` David Konerding
2001-03-27 4:19 ` Alan Cox
2001-03-27 8:32 ` David Konerding
2001-03-27 13:24 ` Mohammad A. Haque
2001-03-27 18:51 ` J Sloan
2001-03-27 19:33 ` Alexander Viro
2001-03-27 5:30 ` Rik van Riel
2001-03-27 8:13 ` David Konerding
2001-03-27 12:31 ` Rik van Riel
2001-03-27 13:51 ` Kernel QA James Lewis Nance
2001-03-27 18:02 ` Shawn Starr
2001-03-27 16:25 ` "mount -o loop" lockup issue Alan Cox
2001-03-27 22:09 ` Kernel QA Alexander Valys
2001-03-27 3:50 ` "mount -o loop" lockup issue Mohammad A. Haque
2001-03-27 3:59 ` William Stearns
2001-03-27 19:25 Joerg Pommnitz
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='019501c0b661$1de195a0$5c044589@legato.com' \
--to=dweekly@legato.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
all inboxes | Powered by JetHome®