public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Bos <rbos@wizard.ca>
To: linux-kernel@vger.kernel.org
Subject: loopback driver hardlocking machine
Date: Fri, 2 Feb 2001 10:27:29 -0800	[thread overview]
Message-ID: <20010202102729.A364@tech.wizard.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]


Good day;

I have been having consistent trouble with the last several kernels; all the
test[9-12], 2.4.0 (all patched with reiser) and the 2.4.1 kernel (unpatched)
seem to do this for me.  I have devfs enabled as well, but this seems to happen
with or without devfs.  I don't believe it happened when I was running 2.2.18.

bug description and reproducability:

On copying to a loopback-mounted Minix filesystem, my machine seems to hardlock;
it happens after the copy, and seems to happen most often when the disk is
being heavily accessed for other purposes before that.  The loopback filesystem
has resided on both ext2 and reiser filesystems, with no change in frequency of
crashes.  Beyond that it is not reproducible; I have a couple of scripts that
trigger this bug approximately one every five iterations - the machine is 
unable to write any more data to disk, unable to flush buffers, and after 
approximately thirty seconds, seems to hardlock, not accepting any input from
any location (ICMP/IP, mouse, keyboard).

The scripts that trigger this (makeinitrd.sh and makediskimage.sh, which both
utilize mount-copy-unmount; it freezes right after copying all files) are
attached, if that might help.

I did in fact look through the bug-reporting document and the maintainers list,
but did not find anyone who would be specifically concerned with this bug; I
suppose the VFS maintainer might be interested, but I'm not sure if this is
a loopback thing, a Minix thing, a reiserfs thing, a VFS thing, et al, so here
you go.

I am available at this email address for further information about my
configuration.

-- 
Rob Bos - System Administration
Wizard Internet Services - http://www.wizard.ca http://linuxmagic.com
Unix Administration, Website Hosting
Network Services, Programming
--------------------------------------------
(604) 589-0037 Beautiful British Columbia, Canada
--------------------------------------------
Any and all opinions expressed herein are not necessarily
the opinions of Wizard Internet Services.

[-- Attachment #2: makediskimage.sh --]
[-- Type: application/x-sh, Size: 955 bytes --]

[-- Attachment #3: makeinitrd.sh --]
[-- Type: application/x-sh, Size: 857 bytes --]

                 reply	other threads:[~2001-02-02 18:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010202102729.A364@tech.wizard.ca \
    --to=rbos@wizard.ca \
    --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