linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: wiebittewas <wiebittewas@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Data Offset
Date: Tue, 25 Feb 2014 08:38:40 +1100	[thread overview]
Message-ID: <20140225083840.11cec0f1@notabene.brown> (raw)
In-Reply-To: <530B2B84.3010208@gmail.com>

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

On Mon, 24 Feb 2014 12:22:44 +0100 wiebittewas <wiebittewas@googlemail.com>
wrote:

> Am 05.06.2012 00:57 schrieb "NeilBrown" bzgl. "Re: Data Offset":
> 
> 
> > OK, try:
> > 
> >    git clone -b data_offset git://neil.brown.name/mdadm
> >    cd mdadm
> >    make
> > 
> >    ./mdadm -C /dev/md1 -e 1.2 -l 5 -n 5 --assume-clean -c 512 \ 
> >       /dev/sdc3:2048s /dev/sdb3:2048s ???  /dev/sdd3:1024s ???
> > 
> > The number after ':' after a device name is a data offset.  's' means sectors.
> 
> well, luckily I've found this message and was able to rescue an array
> with two failed disks with only a few damaged files...
> 
> but is there any possibility that this features comes into normal tree,
> so it will be usable in near future from rescue-sticks like grml?

This feature is in mdadm-3.3.

NeilBrown

> 
> > Don't install this mdadm, and don't use it for anything other than
> > re-creating this array.
> 
> or does it interfere with other necessary features?
> 
> I've viewed a diff to standard 3.2.5 and doesn't see real complex
> things, but even a lot of smaller changes.
> 
> at least thanks for your work.
> 
> w.
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


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

  reply	other threads:[~2014-02-24 21:38 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
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 [this message]
  -- 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=20140225083840.11cec0f1@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=wiebittewas@googlemail.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;
as well as URLs for NNTP newsgroup(s).