From: Martin Steigerwald <Martin@lichtvoll.de>
To: Hendrik Friedel <hendrik@friedels.name>
Cc: Chris Murphy <lists@colorremedies.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck does not fix
Date: Sun, 19 Jan 2014 20:37:31 +0100 [thread overview]
Message-ID: <6210673.6TYUkLGl6b@merkaba> (raw)
In-Reply-To: <52D317CF.2070007@friedels.name>
Am Sonntag, 12. Januar 2014, 23:31:43 schrieb Hendrik Friedel:
> > It mounts OK with no kernel messages?
>
> Yes. Here I mount the three subvolumes:
Does scrubbing the volume give any errors?
I´d test this. If scrubbing runs through without errors at least your data is
currently safe.
As to the error messages: I do not know how critical those are.
I usually just scrub my filesystems once in a while and would only try btrfs
check on one that fails the scrubbing or has problems mounting or (in some
cases) yields strange messages in dmesg.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2014-01-19 19:37 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
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 [this message]
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=6210673.6TYUkLGl6b@merkaba \
--to=martin@lichtvoll.de \
--cc=hendrik@friedels.name \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).