All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Ed Tomlinson <tomlins@CAM.ORG>, reiserfs-list@namesys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] [BUG] opps in 2.4.11-pre2 + prempt patch
Date: Thu, 04 Oct 2001 09:12:27 -0400	[thread overview]
Message-ID: <213850000.1002201147@tiny> (raw)
In-Reply-To: <20011003230330.508E91104F@oscar.casa.dyndns.org>
In-Reply-To: <20011003230330.508E91104F@oscar.casa.dyndns.org>



On Wednesday, October 03, 2001 07:03:29 PM -0400 Ed Tomlinson
<tomlins@CAM.ORG> wrote:

> Hi,
> 
> Does this point at anything?  This happened running dbench with
> 2.4.11-pre2 working on a reiserfs on an LVM (1.01-rc2) volume.  The
> prempt patch is also applied.

I suspect it is a bad interaction with the prempt patch.  I'm using
reiserfs on pre2 without problems here.  It could be lvm-rc2, but I doubt
it.

-chris


  reply	other threads:[~2001-10-04 13:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 23:03 [BUG] opps in 2.4.11-pre2 + prempt patch Ed Tomlinson
2001-10-04 13:12 ` Chris Mason [this message]
     [not found] ` <20011008012906.D790A11069@oscar.casa.dyndns.org>
     [not found]   ` <77260000.1002507094@tiny>
2001-10-08 15:53     ` [linux-lvm] [OOPS] full snapshot (with test vfs locking patch for reiserfs snapshots in 11-pre) Ed Tomlinson
2001-10-08 16:54       ` [linux-lvm] " Chris Mason
2001-10-08 17:05         ` Ed Tomlinson
2001-10-08 17:40           ` Chris Mason
2001-10-08 19:51           ` Chris Mason
2001-10-09  1:57             ` Ed Tomlinson
2001-10-09  2:29               ` Chris Mason
2001-10-09 11:42                 ` Ed Tomlinson
2001-10-10 21:28                 ` Ed Tomlinson
2001-10-10 23:21                   ` Chris Mason
2001-10-11  0:37                     ` Ed Tomlinson
2001-10-11  1:27                       ` Chris Mason

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=213850000.1002201147@tiny \
    --to=mason@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@namesys.com \
    --cc=tomlins@CAM.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.