public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Oops on 2.5.1-pre6 doing mkreiserfs on loop device
Date: Fri, 7 Dec 2001 12:36:50 -0500	[thread overview]
Message-ID: <20011207123650.A118@earthlink.net> (raw)
In-Reply-To: <20011206233759.A173@earthlink.net> <20011207144836.GF12017@suse.de> <20011207145431.GI12017@suse.de> <20011207150058.GJ12017@suse.de> <20011207114046.A152@earthlink.net> <20011207164431.GA27629@suse.de>
In-Reply-To: <20011207164431.GA27629@suse.de>; from axboe@suse.de on Fri, Dec 07, 2001 at 05:44:31PM +0100

On Fri, Dec 07, 2001 at 05:44:31PM +0100, Jens Axboe wrote:
> > I got a very similar oops during mkreiserfs /dev/loop0 on this
> > HIGHMEM machine.
> 
> loop can't be trusted yet. btw, updated patch on kernel.org,
> /pub/linux/kernel/people/axboe/patches/v2.5/2.5.1-pre6

It's a lot better with bio-pre6-2. :) No more oops.  mkreiserfs,
mount, cpio into the loop filesystem work now.  sync will hang on 
/dev/loop0 though.

It's amazing what you get done in one day.
-- 
Randy Hron


  reply	other threads:[~2001-12-07 17:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07  4:37 Oops on 2.5.1-pre6 doing mkreiserfs on loop device rwhron
2001-12-07 14:48 ` Jens Axboe
2001-12-07 14:54   ` Jens Axboe
2001-12-07 15:00     ` Jens Axboe
2001-12-07 16:40       ` rwhron
2001-12-07 16:44         ` Jens Axboe
2001-12-07 17:36           ` rwhron [this message]
2001-12-09  8:07           ` rwhron
2001-12-09  8:57             ` 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=20011207123650.A118@earthlink.net \
    --to=rwhron@earthlink.net \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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