linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Beck <mail@pierre-beck.de>
To: freeone3000 <freeone3000@gmail.com>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Data Offset
Date: Wed, 13 Jun 2012 11:46:35 +0200	[thread overview]
Message-ID: <4FD86179.1080209@pierre-beck.de> (raw)
In-Reply-To: <CAFhY2CgxkjH6JvJzvQt9XT0oawntK7YoTFqnXQJGzvqthD8XpQ@mail.gmail.com>

You specified same offset for all drives, which is wrong. Your initial 
drive setup had differing offsets - look at the examines.

In summary, we have this information:

Drive 0: offset 2048
Drive 1: offset 2048
Drive 2: offset 2048
Drive 3: offset 1024
Drive 4: -dead-

The order was also wrong. The unpartitioned drive was active device 2. 
The /dev/sdX ordering information we got is like

Drive 0: ?
Drive 1: ?
Drive 2: /dev/sde
Drive 3: ?
Drive 4: missing

That makes 3 variables. You can trial-and-error the order of drive 0, 1, 
3 but make sure the offset of drive 3 is always 1024. You'd shift 
characters only. My first try would be:

/dev/sdc3:2048s /dev/sdb3:2048s /dev/sde:2048s /dev/sdd3:1024s missing


My second try would be:

/dev/sdb3:2048s /dev/sdc3:2048s /dev/sde:2048s /dev/sdd3:1024s missing

... and so on.

And DON'T run fsck early. Try mounting read-only, take a look at your 
data. Something bigger than chunksize, like a movie file, checksum some 
iso or smth. It should be intact. THEN run fsck. fsck cannot expect raid 
stripe reordering and worst case may cause damage (not that I heard of 
it happen, but inspecting data first is safe).

Good luck,

Pierre Beck


Am 13.06.2012 08:57, schrieb freeone3000:
>   /dev/sdc3:2048s /dev/sdb3:2048s /dev/sdd3:2048s /dev/sde:2048s


  parent reply	other threads:[~2012-06-13  9:46 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
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 [this message]
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=4FD86179.1080209@pierre-beck.de \
    --to=mail@pierre-beck.de \
    --cc=freeone3000@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).