All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Litherland <josh@temp123.org>
To: linux-raid@vger.kernel.org
Subject: Superblock checksum problems
Date: Sat, 02 Sep 2006 18:36:50 -0400	[thread overview]
Message-ID: <1157236610.8070.7.camel@localhost> (raw)


Attempting to build a new raid5 md array across 4 hard drives.  At the
exact moment that the drive finishes rebuilding, the superblock checksum
changes to an invalid value.  During the rebuild, mdadm -E for the 4
drives shows:

       Checksum : 70c0863a - correct
       Checksum : 70c0864c - correct
       Checksum : 70c0865e - correct
       Checksum : 70c08670 - correct

The instant it finishes:

       Checksum : 70c0bc47 - expected 70c0bc27
       Checksum : 70c0bc59 - expected 70c0bc39
       Checksum : 70c0bc6b - expected 70c0bc4b
       Checksum : 70c0bc7d - expected 70c0bc5d

Kernel is 2.6.17.11.

Controller is 4-port silicon image:

0000:00:08.0 RAID bus controller: Silicon Image, Inc. SiI 3114
[SATALink/SATARaid] Serial ATA Controller (rev 02)

Drives are seagate 250G sata ST3250824AS

-- 
Josh Litherland (josh@temp123.org)



-- 
VGER BF report: U 0.669701

             reply	other threads:[~2006-09-02 22:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-02 22:36 Josh Litherland [this message]
2006-09-04  5:12 ` Superblock checksum problems Neil Brown
2006-09-04 16:00   ` Josh Litherland
2006-09-04 20:55     ` Josh Litherland
2006-09-04 21:13       ` Josh Litherland
2006-09-04 21:35         ` Neil Brown
2006-09-04 21:46           ` Josh Litherland
2006-09-04 23:11             ` Josh Litherland
2006-09-04 23:17               ` Neil Brown
2006-09-04 23:43               ` Henrik Holst
2006-09-06  7:07                 ` Mario 'BitKoenig' Holbe
2006-09-06 13:26               ` Josh Litherland
2006-09-07 20:40                 ` Josh Litherland
2006-09-04 21:54           ` Josh Litherland

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=1157236610.8070.7.camel@localhost \
    --to=josh@temp123.org \
    --cc=linux-raid@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.