From: Chris Mason <chris.mason@oracle.com>
To: Gustavo Sverzut Barbieri <barbieri@gmail.com>
Cc: Alexandre Oliva <oliva@lsd.ic.unicamp.br>, linux-btrfs@vger.kernel.org
Subject: Re: corrupted btrfs after suspend2ram uncorrectable with scrub
Date: Tue, 8 Nov 2011 12:20:43 -0500 [thread overview]
Message-ID: <20111108172043.GH4954@shiny> (raw)
In-Reply-To: <CANkykrCfvFH_fg+5vJVkoWgcPuFp6euzVxZPTRDf=U+qrYUipA@mail.gmail.com>
On Tue, Nov 08, 2011 at 03:08:41PM -0200, Gustavo Sverzut Barbieri wrot=
e:
> On Tue, Nov 1, 2011 at 9:20 PM, Gustavo Sverzut Barbieri
> <barbieri@gmail.com> wrote:
> > On Tue, Nov 1, 2011 at 7:57 PM, Alexandre Oliva <oliva@lsd.ic.unica=
mp.br> wrote:
> >> Hi, Gustavo,
> >>
> >> On Nov =A01, 2011, Gustavo Sverzut Barbieri <barbieri@gmail.com> w=
rote:
> >>
> >>> =A0 btrfs csum failed ino 2957021 extent 85041815552 csum 6673106=
79
> >>> wanted 0 mirror 0
> >>
> >>> Is there any way to recover it? =A0:-S
> >>
> >> Did you try mounting without data checksums?
> >
> > Just tried to mount with -o nodatasum, no luck. Is that enough?
>=20
> Ideas? Should I give up and consider data lost? :-(
We actually check the crcs even when mounted with nodatasum. Can you
give the restore tool a shot from my current btrfs-progs git repo? If
it can read it we can find a way to get the files off.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-08 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 18:38 corrupted btrfs after suspend2ram uncorrectable with scrub Gustavo Sverzut Barbieri
2011-11-01 21:57 ` Alexandre Oliva
2011-11-01 23:20 ` Gustavo Sverzut Barbieri
2011-11-08 17:08 ` Gustavo Sverzut Barbieri
2011-11-08 17:20 ` Chris Mason [this message]
2011-11-09 14:19 ` Gustavo Sverzut Barbieri
2011-11-09 14:27 ` Chris Mason
2011-11-09 14:29 ` Gustavo Sverzut Barbieri
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=20111108172043.GH4954@shiny \
--to=chris.mason@oracle.com \
--cc=barbieri@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=oliva@lsd.ic.unicamp.br \
/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