All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Huber <florian.huber@mnet-online.de>
To: linux-kernel@vger.kernel.org
Cc: jfs-discussion@www-124.ibm.com
Subject: md raid + jfs + jfs_fsck
Date: Tue, 27 Jan 2004 20:15:33 +0100	[thread overview]
Message-ID: <1075230933.11207.84.camel@suprafluid> (raw)

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

Hello MLs,
today I switched from no-raid to linux kernel software raid 1 on a jfs
and a ext3 partition. Both are working fine, but jfs_fsck reports an
error on the jfs md device (md2 <-- hda3+hdc3):

Superblock is corrupt and cannot be repaired 
since both primary and secondary copies are corrupt. 

Did I miss something? jfs_fsck runs without any error on hda3 and hdc3,
but fails on md2.

I'm using the 2.6.2-rc2 kernel with raid autodetection.

TIA
	Florian


-- 
Florian Huber

Key ID: D9D50EA2
Fingerprint: 0241 C329 E355 9B94 8D34 F637 4EB9 1B1D D9D5 0EA2

BOFH Excuse #413:
Cow-tippers tipped a cow onto the server.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-01-27 19:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 19:15 Florian Huber [this message]
2004-01-27 19:28 ` [Jfs-discussion] md raid + jfs + jfs_fsck Dave Kleikamp
2004-01-27 19:39   ` Florian Huber
2004-01-27 19:52     ` Florian Huber
2004-01-27 20:43     ` Dave Kleikamp
2004-01-27 20:53       ` Christoph Hellwig
2004-01-27 21:19         ` Florian Huber
2004-01-27 21:22           ` Christoph Hellwig
2004-01-27 23:39             ` Neil Brown
2004-01-27 21:47         ` Gene Heskett
2004-01-28  2:47         ` Theodore Ts'o
2004-01-28  9:24         ` venom
2004-01-28  9:38           ` Christoph Hellwig
2004-01-28 16:29             ` venom
2004-01-28 10:54           ` Jakob Oestergaard
2004-01-29 22:52           ` Helge Hafting

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=1075230933.11207.84.camel@suprafluid \
    --to=florian.huber@mnet-online.de \
    --cc=jfs-discussion@www-124.ibm.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 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.