From: NeilBrown <neilb@suse.de>
To: Gavin Flower <gavinflower@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm: recovering from an aborted reshape op - boot messages
Date: Tue, 15 Feb 2011 13:16:36 +1100 [thread overview]
Message-ID: <20110215131636.3ed62e81@notabene.brown> (raw)
In-Reply-To: <729509.31129.qm@web65105.mail.ac2.yahoo.com>
On Mon, 14 Feb 2011 18:04:01 -0800 (PST) Gavin Flower <gavinflower@yahoo.com>
wrote:
> output from: fsck.ext4 -f -n /dev/md1
>
> e2fsck 1.41.12 (17-May-2010)
> The filesystem size (according to the superblock) is 76799952 blocks
> The physical size of the device is 76799616 blocks
> Either the superblock or the partition table is likely to be corrupt!
> Abort? no
>
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> Block bitmap differences: -9626 -(9728--9752) +(405344--405369)
> Fix? no
>
>
> I suspect that it might be simple to recover. Are you able to advise on this, or should I run further diagnostics, or ask elsewhere.
>
No I am not.
e2fsck has a very good reputation so if it seems to claim that it can fix
things then it almost certainly can.
Did you try asking on ext3-users@redhat.com ??
NeilBrown
prev parent reply other threads:[~2011-02-15 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 22:47 mdadm: recovering from an aborted reshape op - boot messages Gavin Flower
2011-02-14 23:55 ` NeilBrown
2011-02-15 1:11 ` Gavin Flower
2011-02-15 1:41 ` NeilBrown
2011-02-15 2:04 ` Gavin Flower
2011-02-15 2:16 ` NeilBrown [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=20110215131636.3ed62e81@notabene.brown \
--to=neilb@suse.de \
--cc=gavinflower@yahoo.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).