From: Florian Huber <florian.huber@mnet-online.de>
To: JFS-Discussion <jfs-discussion@oss.software.ibm.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>, shaggy@austin.ibm.com
Subject: Re: [Jfs-discussion] md raid + jfs + jfs_fsck
Date: Tue, 27 Jan 2004 20:39:55 +0100 [thread overview]
Message-ID: <1075232395.11203.94.camel@suprafluid> (raw)
In-Reply-To: <1075231718.21763.28.camel@shaggy.austin.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Tue, 2004-01-27 at 20:28, Dave Kleikamp wrote:
> I wonder if JFS is having trouble getting the partition size. Can you
> run jfs_fsck with the -v flag to see what part of the superblock it
> doesn't like?
The current device is: /dev/md2
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Incorrect jlog length detected in the superblock (P).
Incorrect jlog length detected in the superblock (S).
Superblock is corrupt and cannot be repaired
since both primary and secondary copies are corrupt.
--
Florian Huber
Key ID: D9D50EA2
Fingerprint: 0241 C329 E355 9B94 8D34 F637 4EB9 1B1D D9D5 0EA2
BOFH Excuse #147:
Party-bug in the Aloha protocol.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-27 19:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 19:15 md raid + jfs + jfs_fsck Florian Huber
2004-01-27 19:28 ` [Jfs-discussion] " Dave Kleikamp
2004-01-27 19:39 ` Florian Huber [this message]
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=1075232395.11203.94.camel@suprafluid \
--to=florian.huber@mnet-online.de \
--cc=jfs-discussion@oss.software.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.ibm.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