From: Mircea Ciocan <mirceac@interplus.ro>
To: Linux-kernel@vger.kernel.org
Subject: LARGE bug with 2.4.1ac10 and loop filesystem
Date: Mon, 12 Feb 2001 23:30:03 +0200 [thread overview]
Message-ID: <3A8855DB.8EEC1170@interplus.ro> (raw)
I think I hit a bug introduced between 2.4.1ac9 and 2.4.1ac10,
and a
really bad one I belive :(.
Bug description:
Distribution: Linux Mandrake 7.2
Machine Dual PIII-950, Asus CUBX-E motheboard, 256MB RAM
Compiler (kgcc -v):Reading specs from
/usr/lib/gcc-lib/i586-mandrake-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux
(egcs-1.1.2 release)
Filesystem "loop" compiled as module, filesystem "iso9660" and
juliet
extension compiled in kernel.
Symptom: When trying to: mount blah.iso /mnt/cdrom -o loop, the
console
hangs, Ctrl-C can not interrupt the command, kill can not kill the
stalled mount process and while rebooting none of the filesystems are
unmounted cleanly ( it squirts messeages like umount2: / is busy,
umount2: /home is busy, etc) and on restart the filesystems are checked
but fortunately no errors are found.
By greping the patch I see that some interlocks were added on
the loop
filesystem but I have no knowledge of the intricate mechanism of the
filesystem to correct the problem :(.
Kernel 2.4.1ac9 works OK from that point of view.
Please advise me how can I help with debugging of that further.
Thank you,
Mircea C.
-
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://vger.kernel.org/lkml/
next reply other threads:[~2001-02-12 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 21:30 Mircea Ciocan [this message]
2001-02-12 21:58 ` Alan Cox
2001-02-12 22:08 ` Mircea Ciocan
2001-02-12 22:20 ` Michael J. Maravillo
2001-02-12 22:28 ` Alan Cox
2001-02-13 0:02 ` Sean
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=3A8855DB.8EEC1170@interplus.ro \
--to=mirceac@interplus.ro \
--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®