linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: deleting mdadm array?
Date: Thu, 25 Oct 2007 10:06:19 +0200	[thread overview]
Message-ID: <20071025100619.3b3810be@absurd> (raw)

Hello,

I just created a new array /dev/md1 like this:

mdadm --create --verbose /dev/md1 --chunk=64 --level=raid5 \
   --metadata=1.1  --bitmap=internal \
   --raid-devices=3 /dev/hdc2 /dev/sda2 missing


But later I changed my mind, and I wanted to use chunk 128. Do I need
to delete this array somehow first, or can I just create an array
again (overwriting the current one)?

-- 
Janek Kozicki                                                         |

             reply	other threads:[~2007-10-25  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25  8:06 Janek Kozicki [this message]
2007-10-25  8:17 ` deleting mdadm array? Neil Brown
2007-10-25  9:55 ` David Greaves
2007-10-25 10:12   ` Neil Brown
2007-10-25 13:36   ` Janek Kozicki

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=20071025100619.3b3810be@absurd \
    --to=janek_listy@wp.pl \
    --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).