linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Jon@eHardcastle.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Is this likely to cause me problems?
Date: Tue, 21 Sep 2010 22:15:17 +0100	[thread overview]
Message-ID: <4C992065.9000107@anonymous.org.uk> (raw)
In-Reply-To: <965992.31969.qm@web51304.mail.re2.yahoo.com>

On 21/09/2010 21:33, Jon Hardcastle wrote:
> I am finally replacing an old and now failed drive with a new one.
>
> I normally create a partition the size of the entire disk and add that but whilst checking the sizes marry up i noticed that is an odity...
>
> Below is an fdisk dump of all the drives in my RAID6 array
>
> sdc---
> /dev/sdc1            2048  1953525167   976761560   fd  Linux raid autodetect
> ---
> Seems to be different to sda say which is also '1TB'
>
> sda---
> /dev/sda1              63  1953520064   976760001   fd  Linux raid autodetect
> ---
>
> Now i read somewhere that the sizes flucuate but as some core value remains the same can anyone confirm if this is the case?
>
> I am reluctant to add to my array until i know for sure...

Looks like you've used a different partition tool on the new disc than 
you used on the old ones - old ones started the first partition at the 
beginning of cylinder 1, new ones like to start partitions at 1MB so 
they're aligned on 4K sector boundaries and SSDs' erase group boundaries 
etc. You could duplicate the original partition table like this:

sfdisk -d /dev/older-disc | sfdisk /dev/new-disc

But it wouldn't cause you any problems, because the new partition is 
bigger than the old one, despite starting a couple of thousand sectors 
later. This in itself is odd - how did you come to not use the last 
chunk of your original discs?

Cheers,

John.


  reply	other threads:[~2010-09-21 21:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 20:33 Is this likely to cause me problems? Jon Hardcastle
2010-09-21 21:15 ` John Robinson [this message]
2010-09-21 21:18   ` Jon Hardcastle
2010-09-21 22:34     ` John Robinson
2010-09-22  6:42   ` Jon Hardcastle
2010-09-22 11:25     ` John Robinson
2010-09-22 14:38       ` Jon Hardcastle
2010-09-23 13:14         ` John Robinson
     [not found] <94202.62107.qm@web51304.mail.re2.yahoo.com>
2010-09-22  9:09 ` Tim Small

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=4C992065.9000107@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=Jon@eHardcastle.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).