linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ram Ramesh <rramesh2400@gmail.com>
To: NeilBrown <neilb@suse.com>, Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Why can't I re-add my drive after partition shrink?
Date: Mon, 17 Jul 2017 00:15:47 -0500	[thread overview]
Message-ID: <8d3e1264-2f0a-6ee9-52b5-edddc1e6f185@gmail.com> (raw)
In-Reply-To: <87pod0ypmh.fsf@notabene.neil.brown.name>

On 07/16/2017 05:37 PM, NeilBrown wrote:
> On Fri, Jul 14 2017, Ram Ramesh wrote:
>
>> On 07/13/2017 08:35 PM, NeilBrown wrote:
>>> <snip
>>> Please report output of "mdadm --examine" on both a device that is active
>>> in the array, and the device that you are trying to add.
>>> Also "mdadm --examine-bitmap" of a device that is active in the array.
>>>
>>> NeilBrown
>>>
>>>> I researched as much as I could on the net and came up with nothing
>>>> except some one saying that mdadm keeps something at the end of the disk
>>>> regardless of what it says about "Used Dev Size." Is it possible to move
>>>> this info so that I could re-add?
>>>>
>>>> Ramesh
>>>>
>>>> --
>>>> 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
>> Neil,
>>
>>     Since the problem, I did not want to leave my md in degraded state.
>> So, I added my drive back and paid the penalty for rebuilding. I have
>> other disks that need to be resized and *can get you want*. Please let
>> me know if that is what you meant. If  you wanted the current info after
>> successfully rebuilding the array after a regular add, it is below.
> I only requested the information because it might help fix, or explain,
> your difficulty.  If you don't currently have a difficulty, then I don't
> need to look at any details.
>
> Thanks,
> NeilBrown

Thanks for your time. Yes, I still have the problem as I need to shrink 
other 5 disks in the array and I like to re-add rather than add and 
rebuild each time.

The host with the array is currently busy, and I will get this info 
tomorrow  when I attempt the process on my next hard drive.

Ramesh


  reply	other threads:[~2017-07-17  5:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 23:17 Why can't I re-add my drive after partition shrink? Ram Ramesh
2017-07-13 23:37 ` Anthony Youngman
2017-07-14  1:35 ` NeilBrown
2017-07-15  0:17   ` Ram Ramesh
2017-07-16 22:37     ` NeilBrown
2017-07-17  5:15       ` Ram Ramesh [this message]
2017-07-19 20:55         ` Ram Ramesh
2017-07-19 23:14           ` NeilBrown
2017-07-20  0:39             ` Ram Ramesh
2017-07-20 10:23               ` Wols Lists

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=8d3e1264-2f0a-6ee9-52b5-edddc1e6f185@gmail.com \
    --to=rramesh2400@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.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).