linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: whollygoat@letterboxes.org
To: debian-user@lists.debian.org, linux-raid@vger.kernel.org
Cc: John Robinson <john.robinson@anonymous.org.uk>
Subject: Re: Alex Samad Re: RAID5 (mdadm) array hosed after grow operation
Date: Mon, 12 Jan 2009 19:46:08 -0800	[thread overview]
Message-ID: <1231818368.32510.1294443075@webmail.messagingengine.com> (raw)
In-Reply-To: <49672AE4.2060602@anonymous.org.uk>


On Fri, 09 Jan 2009 10:45:56 +0000, "John Robinson"
<john.robinson@anonymous.org.uk> said:
> On 09/01/2009 02:41, whollygoat@letterboxes.org wrote:
> > But anyway, I don't think that is going to matter.  The issue I am
> > trying to 
> > solve is how to de-activate the bitmap. It was suggested on the
> > linux-raid 
> > list that my problem may have been caused by running the grow op on an
> > active 
> > bitmap and I can't see from "man mdadm" how to de-activate the bit map.
> 
> man mdadm tells me:
> [...]
> -b, --bitmap=
>      Specify a file to store a write-intent bitmap in. The file should 
> not exist unless --force is also given. The same file should be provided 
> when assembling the array. If the word internal is given, then the 
> bitmap is stored with the metadata on the array, and so is replicated on 
> all devices. If the word none is given with --grow mode, then any bitmap 
> that is present is removed.
> 
> So I imagine you'd want to
>    # mdadm --grow /dev/mdX --bitmap=none
> to de-activate the bitmap.

The question that came to mind when I read that in the docs,
was how to recreate the bitmap on an already created array
after nuking it with "none".

I guess I also had doubts because the reply I had a few iterations
back didn't say that I shouldn't have performed the grow operation
on an existant bitmap, but an active one, and I wasn't prepared to
make the leap from active/inactive to existant/non-existant.

But, this has all become moot anyway.  When I put the original, smaller
drives back in, hoping to do the grow op overagain, I was faced with a
similar problem assembling the array, so I'm guessing the problem
caused by something other than the grow.  I put the larger drives in,
zeroed them, and am in the process of recreating the array and
file systems to be populated from backups.

Thanks for the input.

goat
-- 
  
  whollygoat@letterboxes.org

-- 
http://www.fastmail.fm - Faster than the air-speed velocity of an
                          unladen european swallow


      reply	other threads:[~2009-01-13  3:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1231144738.2997.1293010001@webmail.messagingengine.com>
2009-01-05 14:13 ` RAID5 (mdadm) array hosed after grow operation Justin Piszcz
2009-01-05 22:17   ` Neil Brown
2009-01-06  8:45     ` whollygoat
2009-01-08  4:19     ` whollygoat
     [not found]       ` <20090108101218.GI25654@samad.com.au>
2009-01-09  2:41         ` Alex Samad " whollygoat
2009-01-09 10:45           ` John Robinson
2009-01-13  3:46             ` whollygoat [this message]

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=1231818368.32510.1294443075@webmail.messagingengine.com \
    --to=whollygoat@letterboxes.org \
    --cc=debian-user@lists.debian.org \
    --cc=john.robinson@anonymous.org.uk \
    --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).