From: Benjamin Valentin <benpicco@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: One disc of 3-disc btrfs-raid5 failed - files only partially readable
Date: Sun, 14 Feb 2016 08:40:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20160214T072657-687@post.gmane.org> (raw)
In-Reply-To: CAPmG0jaRphE4jWi4aGUk_tV2OYyddVUXjwcNtuN+A97PTWtYVA@mail.gmail.com
Henk Slager <eye1tm <at> gmail.com> writes:
> You could use 1-time mount option clear_cache, then mount normally and
> cache will be rebuild automatically (but also corrected if you don't
> clear it)
This didn't help, gave me
[ 316.111596] BTRFS info (device sda): force clearing of disk cache
[ 316.111605] BTRFS info (device sda): disk space caching is enabled
[ 316.111608] BTRFS: has skinny extents
[ 316.227354] BTRFS info (device sda): bdev /dev/sda errs: wr 180547340,
rd 592949011, flush 4967, corrupt 582096433, gen
26993
and still
[ 498.552298] BTRFS warning (device sda): csum failed ino 171545 off
2269560832 csum 2566472073 expected csum 874509527
[ 498.552325] BTRFS warning (device sda): csum failed ino 171545 off
2269564928 csum 2566472073 expected csum 2434927850
> > Do you think there is still a chance to recover those files?
>
> You can use btrfs restore to get files off a damaged fs.
This however does work - thank you!
Now since I'm a bit short on disc space, can I remove the disc that
previously disappeared (and thus doesn't have all the
data) from the RAID, format it and run btrfs rescue on the degraded array,
saving the rescued data to the now free disc?
next prev parent reply other threads:[~2016-02-14 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 17:28 One disc of 3-disc btrfs-raid5 failed - files only partially readable Benjamin Valentin
2016-02-09 19:35 ` Henk Slager
2016-02-14 8:40 ` Benjamin Valentin [this message]
2016-02-14 11:21 ` Henk Slager
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=loom.20160214T072657-687@post.gmane.org \
--to=benpicco@googlemail.com \
--cc=linux-btrfs@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).