From: Chris Murphy <lists@colorremedies.com>
To: Hendrik Friedel <hendrik@friedels.name>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck does not fix
Date: Sun, 5 Jan 2014 09:55:10 -0700 [thread overview]
Message-ID: <F9C2788F-B057-4C3F-A490-8F8A19C37F97@colorremedies.com> (raw)
In-Reply-To: <52C87B67.1040503@friedels.name>
On Jan 4, 2014, at 2:21 PM, Hendrik Friedel <hendrik@friedels.name> wrote:
> Hi Chris,
>
>
> >> I ran btrfsck on my volume with the repair option. When I re-run it, >>I get the same errors as before.
>>
>> Did you try mounting with -o recovery first?
>> https://btrfs.wiki.kernel.org/index.php/Problem_FAQ
>
> No, I did not.
> In fact, I had visited the FAQ before, and my understanding was, that -o recovery was used/needed when mounting is impossible. This is not the case. In fact, the disk does work without obvious problems.
It mounts without errors? So why then btrfsck/btrfs repair? What precipitated the repair?
If mount option -o recovery is used, dmesg should report 'btrfs: enabling auto recovery' and I think you're right if it's mounting OK then probably recovery isn't applicable. Can you just do a btrfs check <dev> and report the results? Repair can sometimes make problems worse it seems.
Chris Murphy
next prev parent reply other threads:[~2014-01-05 16:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 19:41 btrfsck does not fix Hendrik Friedel
2014-01-03 23:33 ` Chris Murphy
2014-01-04 21:21 ` Hendrik Friedel
2014-01-05 13:36 ` Hendrik Friedel
2014-01-05 16:55 ` Chris Murphy [this message]
2014-01-07 20:38 ` Hendrik Friedel
2014-01-10 23:53 ` Hendrik Friedel
2014-01-11 1:05 ` Chris Murphy
2014-01-12 22:31 ` Hendrik Friedel
2014-01-14 0:40 ` Chris Murphy
2014-01-14 6:03 ` Duncan
2014-01-14 7:49 ` Chris Murphy
2014-01-14 9:30 ` Duncan
2014-01-14 9:38 ` Hugo Mills
2014-01-14 17:17 ` Chris Murphy
2014-01-18 7:20 ` Chris Samuel
2014-01-14 8:16 ` Hugo Mills
2014-01-19 19:37 ` Martin Steigerwald
2014-01-21 20:00 ` Hendrik Friedel
2014-01-21 20:01 ` Hendrik Friedel
2014-02-08 22:01 ` Hendrik Friedel
2014-02-09 0:45 ` Chris Murphy
2014-02-09 8:36 ` Hendrik Friedel
2014-02-11 1:45 ` Chris Murphy
2014-02-11 2:23 ` Chris Murphy
2014-02-16 19:18 ` Hendrik Friedel
2014-02-16 19:54 ` Chris Murphy
2014-02-17 3:20 ` Duncan
2014-02-17 9:41 ` Goswin von Brederlow
2014-02-18 21:55 ` Hendrik Friedel
2014-02-18 22:12 ` Chris Murphy
2014-03-02 18:39 ` Hendrik Friedel
2014-03-03 22:35 ` Chris Murphy
2014-03-04 6:42 ` Hendrik Friedel
2014-03-04 17:02 ` Chris Murphy
2014-03-03 1:09 ` Russell Coker
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=F9C2788F-B057-4C3F-A490-8F8A19C37F97@colorremedies.com \
--to=lists@colorremedies.com \
--cc=hendrik@friedels.name \
--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 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.