public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Mathew Spencer <Matthew.Spencer@eu.sony.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: blk_congestion_wait() with linux-2.5.68]
Date: Thu, 22 May 2003 17:18:56 +0200	[thread overview]
Message-ID: <20030522151856.GJ812@suse.de> (raw)
In-Reply-To: <1053617008.8679.280.camel@jeckle>

On Thu, May 22 2003, Mathew Spencer wrote:
> I have been using 2.4.19 successfully for a while now with an PCI IDE
> disk drive with no problems whatsoever.  I recently upgraded to 2.5.68
> (so that I could use the most recent ieee1394 drivers) and also to start
> experimenting with the new version of the kernel and since then I am
> having problems formatting the hard disk.
> 
> When I run mke2fs, it manages to write out the first 12 or 13 blocks
> successfully, but then the code gets stuck continually calling
> blk_congestion_wait() from balance_dirty_pages().
> 
> This is the only time that I see this problem.  If the disk is already
> formatted, then mounting/reading/writing to the disk happens without any
> problems at all.
> 
> Is anyone out there aware of this problem?

Any messages in dmesg? It sounds like io to the drive stops completely,
and that is why you see mke2fs being stuck in blk_congestion_wait
(mke2fs eats most of the requests, the queue gets marked congested). If
io isn't progressing, then the queue won't have the congestion flag
cleared again.

You need to give a lot more hardware details, see REPORTING-BUGS

-- 
Jens Axboe


      reply	other threads:[~2003-05-22 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 15:23 [Fwd: blk_congestion_wait() with linux-2.5.68] Mathew Spencer
2003-05-22 15:18 ` Jens Axboe [this message]

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=20030522151856.GJ812@suse.de \
    --to=axboe@suse.de \
    --cc=Matthew.Spencer@eu.sony.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