From: Michael Tokarev <mjt@tls.msk.ru>
To: Marco Scoffier <marco@metm.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: old raid0run
Date: Sun, 11 Feb 2007 09:59:29 +0300 [thread overview]
Message-ID: <45CEBED1.6000702@tls.msk.ru> (raw)
In-Reply-To: <pan.2007.02.11.06.33.05.974944@metm.org>
Marco Scoffier wrote:
> Hello all,
>
> I have an old raid0 with no superblocks.
>
> I have just upgraded the machine with this raid and mdadm is incapable of
> mounting it. Unfortunately raidtools will no longer compile*. So I am a
> bit stuck as I would like to save the data on this raid0.
>
> Can I create a new raid0 using mdadm ?
>
> mdadm -C -n 2 -c 128 -l 0 /dev/md0 /dev/hde1 /dev/hdg1
Well, mdadm is able to assemble it. It's called 'build' (--build) --
mdadm --build -n 2 -c 128 -l 0 /dev/md0 /dev/hde1 /dev/hdg1
> or should I build a new raid0 and then upgrade that to a raid0 with
> superblocks (how would I do that?)
I think the best option is to convert it to raid0-with-superblocks.
For that, I'd go this route:
- build the array as above
- fsck the filesystem on it
- resize the filesystem to be, say, 1Mb smaller
- stop the array
- create new array as you've shown above with -C
- and finally resize the filesystem to utilize all available space
Or something like that, anyway.
Sure, backing up data and restoring it after creating the array is
safer.
> Thanks for any pointers,
>
> As there are no super-blocks mdadm is
> giving very little information:
>
> mdadm -E /dev/hde1
> mdadm: No md superblock detected on /dev/hde1.
Well, it's expectable. -E = show superblock contents.
> mdadm -As /dev/md0
> mdadm: /dev/hde1 has no superblock - assembly aborted
Assembly needs devices with superblocks. Try -B.
/mjt
next prev parent reply other threads:[~2007-02-11 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 6:33 old raid0run Marco Scoffier
2007-02-11 6:59 ` Michael Tokarev [this message]
2007-02-11 7:45 ` Marco Scoffier
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=45CEBED1.6000702@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-raid@vger.kernel.org \
--cc=marco@metm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.