public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Kagan <Roman.Kagan@itep.ru>
To: linux-kernel@vger.kernel.org
Cc: "T.Raykoff" <traykoff@snet.net>
Subject: Re: 2.4.18 IDE channels block each other under load?
Date: Tue, 30 Jul 2002 21:27:07 +0400	[thread overview]
Message-ID: <20020730172707.GE30271@panda.itep.ru> (raw)

 Hi,

I'm by no means an expert in this, just a guess:

On Tue, Jul 30, 2002 at 05:09:22PM +0000, T.Raykoff wrote:
> This lockup only happens under write load.  Heavy reads don't cause the 
> prob.  Hmmmm.
> 
> Not sure that it really is memory thrashing.  The box is unloaded and 
> really has about 1GB free, to use for buffer as it sees fit.  No I/O to 
> the swap file going on, cause there is no mounted swap.
> 
> Check this out:
> 
> dd if=/dev/zero of=/dev/hda bs=1024
> 
> then:
> 
> fdisk /dev/hdc
> 
> "q"
> 
> fdisk blocks in the close() call.... for well over 15 minutes!
> 
> As soon as dd ends cause /dev/hda is at EOF, fisk::close() returns in a 
> moment.

When you quit from fdisk it does a sync() right after the close().  I
suspect that fdisk gets stuck in that sync() rather than close().  (You
said strace reported close() as the last syscall - it's the last one
completed.)  The write on one of the channels doesn't let sync() return.

To make sure I'd try to check (e.g. with /proc/<pid>/fd) if fdisk still
has /dev/hdc open during the dd.

  Cheers,
  	Roman.

             reply	other threads:[~2002-07-30 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 17:27 Roman Kagan [this message]
     [not found] <Pine.LNX.4.33.0207221750210.22553-100000@coffee.psychology.mcmaster.ca>
2002-07-22 23:04 ` 2.4.18 IDE channels block each other under load? T.Raykoff
2002-07-30 16:18   ` Bill Davidsen
     [not found] <fa.e5te67v.1s3m1qr@ifi.uio.no>
2002-07-22 20:08 ` Aniket Malatpure
2002-07-22 21:09   ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-06-21 14:03 Taavo Raykoff
2002-06-21 14:17 ` Roy Sigurd Karlsbakk
2002-06-21 15:14   ` T.Raykoff

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=20020730172707.GE30271@panda.itep.ru \
    --to=roman.kagan@itep.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=traykoff@snet.net \
    /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