linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Wiegley <jeffw@csun.edu>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Why would a recreation cause a different number of blocks??
Date: Thu, 24 Apr 2014 22:02:05 -0700	[thread overview]
Message-ID: <5359EC4D.7000308@csun.edu> (raw)
In-Reply-To: <alpine.DEB.2.02.1404250533040.19744@uplift.swm.pp.se>

I'll look into this. I kind of thought about that sort
of thing and I went and installed ubuntu 12.04 which I
thought was what I started this all with but I might
have done it earlier than 12.04 and I might have used
gentoo.

are the mdadm defaults specific to mdadm version or
would ubuntu and gentoo have specified different
defaults in something like an /etc/defaults/ourmdadm.cfg?

If it's mdadm then could I just grab old copies of mdadm
sources and compile them one version after the other and
try each one?

Thanks,

- Jeff

On 4/24/2014 8:34 PM, Mikael Abrahamsson wrote:
> On Thu, 24 Apr 2014, Jeff Wiegley wrote:
>
>> Why did my block counts change? The disk partitions weren't touched
>> or changed at any point. Shouldn't I have gotten the same size?
>
> Defaults in mdadm has changed over time, so data offsets might be
> different. In order to get the exact same data offset you need to use the
> same mdadm version as was originally used, or at least know the values it
> used and use mdadm 3.3 that allows you to specify these data at creation
> time,
>
>> The created device isn't work. There is suppose to be luks encrypted
>> volume there but luksOpen reports there is no luks header. (and there
>> use to be). Would the odd change in size indicate total corruption?
>
> No, the change in size indicates that data offsets are not the same so
> your beginning of volume is now in the wrong place.
>


  reply	other threads:[~2014-04-25  5:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  5:05 Corrupted ext4 filesystem after mdadm manipulation error L.M.J
2014-04-24 17:48 ` L.M.J
     [not found]   ` <CAK_KU4a+Ep7=F=NSbb-hqN6Rvayx4QPWm-M2403OHn5-LVaNZw@mail.gmail.com>
2014-04-24 18:35     ` L.M.J
     [not found]       ` <CAK_KU4Zh-azXEEzW4f1m=boCZDKevqaSHxW0XoAgRdrCbm2PkA@mail.gmail.com>
2014-04-24 19:53         ` L.M.J
     [not found]         ` <CAK_KU4aDDaUSGgcGBwCeO+yE0Qa_pUmMdAHMu7pqO7dqEEC71g@mail.gmail.com>
2014-04-24 19:56           ` L.M.J
2014-04-24 20:31             ` Scott D'Vileskis
2014-04-24 22:25               ` Why would a recreation cause a different number of blocks?? Jeff Wiegley
2014-04-25  3:34                 ` Mikael Abrahamsson
2014-04-25  5:02                   ` Jeff Wiegley [this message]
2014-04-25  6:01                     ` Mikael Abrahamsson
2014-04-25  6:45                       ` Jeff Wiegley
2014-04-25  7:25                         ` Mikael Abrahamsson
2014-04-25  7:05                       ` Jeff Wiegley
     [not found]             ` <CAK_KU4YUejncX9yQk4HM5HE=1-qPPxOibuRauFheo3jaBc8SaQ@mail.gmail.com>
2014-04-25  5:13               ` Corrupted ext4 filesystem after mdadm manipulation error L.M.J
2014-04-25  6:04                 ` Mikael Abrahamsson
2014-04-25 11:43                   ` L. M. J
2014-04-25 13:36                     ` Scott D'Vileskis
2014-04-25 14:43                       ` L.M.J
2014-04-25 18:37                       ` Is disk order relative or are the numbers absolute? Jeff Wiegley

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=5359EC4D.7000308@csun.edu \
    --to=jeffw@csun.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    /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).