linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: freeone3000 <freeone3000@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Data Offset
Date: Mon, 4 Jun 2012 13:35:26 +1000	[thread overview]
Message-ID: <20120604133526.6da3bf10@notabene.brown> (raw)
In-Reply-To: <CAFhY2Cjwep5mZkYCfRn4UYmQpSyHU13dSCB8HF8F9wG8Rzx9Aw@mail.gmail.com>

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

On Fri, 1 Jun 2012 19:48:41 -0500 freeone3000 <freeone3000@gmail.com> wrote:

> Sorry.
> 
> /dev/sde fell out of the array, so I replaced the physical drive with
> what is now /dev/sdf. udev may have relabelled the drive - smartctl
> states that the drive that is now /dev/sde works fine.
> /dev/sdf is a new drive. /dev/sdf has a single, whole-disk partition
> with type marked as raid. It is physically larger than the others.
> 
> /dev/sdf1 doesn't have a mdadm superblock. /dev/sdf seems to, so I
> gave output of that device instead of /dev/sdf1, despite the
> partition. Whole-drive RAID is fine, if it gets it working.
> 
> What I'm attempting to do is rebuild the RAID from the data from the
> other four drives, and bring the RAID back up without losing any of
> the data. /dev/sdb3, /dev/sdc3, /dev/sdd3, and what is now /dev/sde3
> should be used to rebuild the array, with /dev/sdf as a new drive. If
> I can get the array back up with all my data and all five drives in
> use, I'll be very happy.

You appear to have 3 devices that are happy:
  sdc3 is device 0   data-offset 2048
  sdb3 is device 1   data-offset 2048
  sdd3 is device 3   data-offset 1024

nothing claims to be device 2 or 4.

sde3 looks like it was last in the array on 23rd May, a little over
a week before your report.  Could that have been when "sde fell out of the
array" ??
Is it possible that you replaced the wrong device?
Or is it possible the the array was degraded when sde "fell out" resulting
in data loss?

I need more precise history to understand what happened, as I cannot suggest
a fixed until I have that understanding.

When did the array fail?
How certain are you that you replaced the correct device?
Can you examine the drive that you removed and see what it says?
Are you certain that the array wasn't already degraded?

NeilBrown



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-06-04  3:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 23:22 Data Offset freeone3000
2012-06-01 23:52 ` NeilBrown
2012-06-02  0:48   ` freeone3000
2012-06-04  3:35     ` NeilBrown [this message]
2012-06-04 18:26       ` Pierre Beck
2012-06-04 22:57         ` NeilBrown
2012-06-05  5:26           ` freeone3000
2012-06-05  5:44             ` NeilBrown
     [not found]               ` <CAFhY2CiDTMRSV2wFCMhT9ZstUkHkJS7E0p7SP-ssfqwaquo+0w@mail.gmail.com>
     [not found]                 ` <20120610074531.65eaed81@notabene.brown>
     [not found]                   ` <CAFhY2CgxkjH6JvJzvQt9XT0oawntK7YoTFqnXQJGzvqthD8XpQ@mail.gmail.com>
2012-06-13  9:46                     ` Pierre Beck
2012-06-13 12:49                       ` Phil Turmel
2012-06-13 17:56                         ` Pierre Beck
2012-06-13 18:11                           ` Phil Turmel
2012-06-13 18:22                             ` Pierre Beck
2012-06-13 18:49                               ` Piergiorgio Sartor
2012-06-20  3:56                                 ` freeone3000
2012-06-20 14:09                                   ` Pierre Beck
2012-06-25  6:25                                   ` NeilBrown
2014-02-24 11:22           ` wiebittewas
2014-02-24 21:38             ` NeilBrown
  -- strict thread matches above, loose matches on Subject: below --
2014-05-15 14:11 Data offset Patrik Horník
2014-05-15 22:07 ` NeilBrown
2014-05-16  0:41   ` Patrik Horník
2012-05-10 17:42 Data Offset Piergiorgio Sartor
2012-05-24  5:20 ` NeilBrown

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=20120604133526.6da3bf10@notabene.brown \
    --to=neilb@suse.de \
    --cc=freeone3000@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).