public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: qkholland@my-deja.com
Cc: linux-kernel@vger.kernel.org, Mark Bratcher <mbratche@rochester.rr.com>
Subject: Re: Kernel 2.4.0 loop device still hangs
Date: Fri, 26 Jan 2001 11:28:11 +0100	[thread overview]
Message-ID: <20010126112811.E12520@suse.de> (raw)
In-Reply-To: <fa.hl5rjsv.1b78u0u@ifi.uio.no> <200101260634.AAA02715@x57.deja.com>
In-Reply-To: <200101260634.AAA02715@x57.deja.com>; from qkholland@my-deja.com on Fri, Jan 26, 2001 at 06:34:52AM +0000

On Fri, Jan 26 2001, qkholland@my-deja.com wrote:
>   Mark Bratcher <mbratche@rochester.rr.com> wrote:
> > I saw a post dated last fall 2000 sometime about the
> > loop device hanging when copying large amounts of data
> > to a file mounted as, say, ext2fs.
> 
> I've recently reported a similar problem and told by
> Jens Axboe at SUSE that it is still there, and appears
> to be generic (not hardware nor kernel configuration
> specific) problem.

Yes, and please try:

*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.1-pre10/loop-3

and see if you can reproduce.

-- 
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
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/

  reply	other threads:[~2001-01-26 10:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.hl5rjsv.1b78u0u@ifi.uio.no>
2001-01-26  6:34 ` Kernel 2.4.0 loop device still hangs qkholland
2001-01-26 10:28   ` Jens Axboe [this message]
2001-01-28 13:01 Andreas Franck
2001-01-28 19:43 ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2001-01-26  3:29 Mark Bratcher
2001-01-27 15:27 ` Mark Bratcher
2001-01-28  2:43   ` Jens Axboe
2001-01-28  2:50     ` Mark Bratcher
2001-01-28 12:10     ` Mircea Damian

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=20010126112811.E12520@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbratche@rochester.rr.com \
    --cc=qkholland@my-deja.com \
    /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