From: Robin Hill <robin@robinhill.me.uk>
To: Andris Berzins <pkix@inbox.lv>
Cc: linux-raid@vger.kernel.org
Subject: Re: failed raid re-create changed dev size
Date: Tue, 11 Dec 2012 14:49:49 +0000 [thread overview]
Message-ID: <20121211144949.GB28593@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <1355236515.50c744a3720c1@mail.inbox.lv>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
On Tue Dec 11, 2012 at 04:35:15PM +0200, Andris Berzins wrote:
> Quoting "Robin Hill" <robin@robinhill.me.uk>:
> >
> > You will likely have lost some data though, as the new superblocks will
> > have overwritten part of the data, so make sure you run a fsck
> > afterwards (start with fsck -n though, to make sure the overall array
> > looks okay first).
>
> Is it possible that no data was damaged? It is LUKS partition, i
> mapped it and run "fsck -n" on underlying ext3 partition,
> but fsck returned immediately with status "clean".
>
By default fsck will just check whether the filesystem is marked as
dirty/clean and just skip running if it's clean. You'll need to use "-f"
to force it to run.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-12-11 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 23:37 failed raid re-create changed dev size Andris Berzins
2012-12-11 8:15 ` Mikael Abrahamsson
2012-12-11 9:01 ` Andris Berzins
2012-12-11 9:27 ` Robin Hill
2012-12-11 14:35 ` Andris Berzins
2012-12-11 14:49 ` Robin Hill [this message]
2012-12-12 16:10 ` Andris Berzins
2012-12-13 9:30 ` Robin Hill
2012-12-13 16:13 ` Andris Berzins
2012-12-12 1:04 ` Brad Campbell
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=20121211144949.GB28593@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
--cc=pkix@inbox.lv \
/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).