Date: Mon, 15 Mar 2004 04:41:25 +0100
From: Marc Lehmann <pcg@schmorp.de>
To: jpearson@oasissystems.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange ext3 corruption problem on 2.6.x
Message-ID: <20040315034125.GA5295@schmorp.de>
Mail-Followup-To: jpearson@oasissystems.com.au,
	linux-kernel@vger.kernel.org
References: <20040314222929.GA23106@mark>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040314222929.GA23106@mark>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1336
Lines: 27

On Mon, Mar 15, 2004 at 08:59:29AM +1030, jpearson@oasissystems.com.au wrote:
> 'r/o' by the RAID layer, presumably unbeknownst to VFS; are you
> *sure* that your array is still up and 'good' when you get this
> message?

As I said, there are no other messages, so if there is a problem (cabling,
disk-i/o etc.), then the kernel doesn't know it either (usually the kernel
it quite loud in this condition).

The array also comes up clean and synced. And the reiserfs partition on
the same lv doesn't have any problems (wether this means that reiserfs
doesn't suffer from this bug or wether reiserfs is just unable to detect
it is, of course, a different question).

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg@goof.com      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/