From: Phil Turmel <philip@turmel.org>
To: Dragon <Sunghost@gmx.de>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: SRaid with 13 Disks crashed
Date: Fri, 10 Jun 2011 10:49:29 -0400 [thread overview]
Message-ID: <4DF22EF9.1030507@turmel.org> (raw)
In-Reply-To: <20110610144429.298520@gmx.net>
On 06/10/2011 10:44 AM, Dragon wrote:
> "fsck automatically calls fsck.ext4 when it sees an ext4 filesystem. 15.4% Notcontiguous == 15.4 fragmented. No lost data."
> -> ok, puh
>
> Now that you have a good filesystem, mounting it and taking a backup would be a good idea. Or at least retrieve any files that are very important to you.
> -> ups
>
> NO! You must use "mdadm --grow". Yes, "--grow" also does "shrink". Your fsck shows that the ext4 filesystem is still sized for the original 12-disk setup, so you don't have to shrink the filesystem. You do have to shrink the raid:
>
> ->mount was successfull and i can see all of my data ;) im so happy, but have still no possibility to make a backup
Yay! :) and Oooo! :(
> Step 1a: Tell mdadm the final size you are aiming for. MD will emulate this while you test that the new size works:
> mdadm /dev/md0 --grow --array-size=16116523456k
> -> shows
> mdadm /dev/md0 --grow --array-size=16116523456k
> mdadm: invalid array size: 16116523456k
>
> might be: 16896000k better? 1500*1024*11
No, it must be "Used Device Size" * 11 = 16116523456. Try it without the 'k'.
Phil
next parent reply other threads:[~2011-06-10 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110610144429.298520@gmx.net>
2011-06-10 14:49 ` Phil Turmel [this message]
2011-06-10 13:06 (unknown) Dragon
2011-06-10 14:01 ` SRaid with 13 Disks crashed Phil Turmel
-- strict thread matches above, loose matches on Subject: below --
2011-06-10 7:52 Dragon
2011-06-10 11:48 ` Phil Turmel
2011-06-08 20:02 Dragon
2011-06-08 20:32 ` Phil Turmel
2011-06-08 14:24 (unknown) Dragon
2011-06-08 14:39 ` SRaid with 13 Disks crashed Phil Turmel
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=4DF22EF9.1030507@turmel.org \
--to=philip@turmel.org \
--cc=Sunghost@gmx.de \
--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 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.