From: "First Name Last Name" <qkholland@my-deja.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.0-pre10 Hard lockup writing to fs on loop devices
Date: Wed, 24 Jan 2001 16:02:04 -0800 [thread overview]
Message-ID: <200101250002.QAA13445@mail3.bigmailbox.com> (raw)
I am seeing hard lockup without OOPS when I write
60-40MB into a filesystem created on a regular file via
loop device, and the problem is quite reproducible.
Is anybody else suffering from a similar problem?
# mount | grep export/scratch
/dev/hda9 on /export/scratch type ext2 (rw)
# dd if=/dev/zero of=/export/scratch/F bs=1M count=420
# echo yes | mke2fs /export/scratch/F
# mount -o loop /export/scratch/F /mnt
# tar cf - . | ( cd /mnt && tar xfp - )
------------------------------------------------------------
--== Sent via Deja.com ==--
http://www.deja.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-25 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 0:02 First Name Last Name [this message]
2001-01-25 0:13 ` 2.4.0-pre10 Hard lockup writing to fs on loop devices Jens Axboe
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=200101250002.QAA13445@mail3.bigmailbox.com \
--to=qkholland@my-deja.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