From: kclair <kclair@gmail.com>
To: Jim Paris <jim@jtan.com>, linux-raid@vger.kernel.org
Subject: Re: adding a disk smaller than the array size
Date: Thu, 14 Oct 2004 16:29:09 -0400 [thread overview]
Message-ID: <dff3752704101413296326ff89@mail.gmail.com> (raw)
In-Reply-To: <20041013224643.GA9601@jim.sh>
On Wed, 13 Oct 2004 18:46:43 -0400, Jim Paris <jim@jtan.com> wrote:
> > And failing everything, you could (maybe) clone the array-disk to the empty
> > smaller one, run fsck to fix the partition size (but I'm not totally sure it
> > does, so that remains doubtful), reverse the roles of the two disks and then
> > add the -now free- larger disk to the array. But that would be a last resort.
> > I cannot vouch for how md copes with the few missing sectors, and neither how
> > the filesystem reacts, so you'd better not try that without good testing.
>
> Or just do this same thing at the filesystem level.
>
> Right now you have md0 with one missing disk. Use your new disk to
> create md1 with one missing disk. Create filesystem on md1, and copy
> files with e.g. tar, rsync, etc. Then get rid of md0 and add that
> drive to md1.
>
> -jim
>
Thanks for all the info and the suggestions. The key factor here was
that I could not just build an array with one disk containing the data
and one unformatted disk and hope they would sync up. I followed
Jim's advice successfully ... except that mdadm reports that the new
array is State: dirty.
But at least the data is accessible once again!
Kristina
prev parent reply other threads:[~2004-10-14 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 20:30 adding a disk smaller than the array size kclair
2004-10-13 20:54 ` maarten
2004-10-13 21:06 ` kclair
2004-10-13 22:08 ` maarten
2004-10-13 22:46 ` Jim Paris
2004-10-14 20:29 ` kclair [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=dff3752704101413296326ff89@mail.gmail.com \
--to=kclair@gmail.com \
--cc=jim@jtan.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).