linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Radu Rendec <radu.rendec@ines.ro>
To: Neil Brown <neilb@suse.de>
Cc: Dan Williams <dan.j.williams@intel.com>, linux-raid@vger.kernel.org
Subject: Re: Raid 1, new disk can't be added after replacing faulty disk
Date: Tue, 08 Jan 2008 12:24:22 +0200	[thread overview]
Message-ID: <1199787862.3202.35.camel@localhost.localdomain> (raw)
In-Reply-To: <18306.64884.866266.620787@notabene.brown>

On Tue, 2008-01-08 at 15:35 +1100, Neil Brown wrote:
> On Monday January 7, dan.j.williams@intel.com wrote:
> > Looks like you are running into the issue described here:
> > http://marc.info/?l=linux-raid&m=119892098129022&w=2

Dan, thanks for your quick reply. It's exactly the same issue: the array
was created with mdadm 2.5.6.

> I cannot easily reproduce this.  I suspect it is sensitive to the
> exact size of the devices involved.

I reproduced this with 3 different device sizes: 518160384 bytes,
4005711360 bytes and 155021851648 bytes. Is it possible that I hit the
"wrong" size every time? Maybe it's related to the disk geometry
(because all partitions lay on exact cylinder boundaries, and thus all
partitions sizes are multiples of the same cylinder size).

> Please test this patch and see if it fixes the problem.
> If not, please tell me the exact sizes of the partition being used
> (e.g. cat /proc/partitions) and I will try harder to reproduce it.

I'll test the patch and get back to you soon.

Thanks,

Radu Rendec



  reply	other threads:[~2008-01-08 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 13:44 Raid 1, new disk can't be added after replacing faulty disk Radu Rendec
2008-01-07 19:11 ` Dan Williams
2008-01-08  4:35   ` Neil Brown
2008-01-08 10:24     ` Radu Rendec [this message]
2008-01-08 10:38     ` Radu Rendec
2009-01-15 19:10     ` rcoverby

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=1199787862.3202.35.camel@localhost.localdomain \
    --to=radu.rendec@ines.ro \
    --cc=dan.j.williams@intel.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).