From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: strange corruptions found during btrfs check
Date: Mon, 06 Jul 2015 20:40:23 +0200 [thread overview]
Message-ID: <1436208023.7124.6.camel@scientia.net> (raw)
In-Reply-To: <1435853528.6153.3.camel@scientia.net>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
After removing some of the snapshots that were received, the errors at
btrfs check went away.
Is there some list of features in btrfs which are considered stable?
Cause I though send/receive and the subvolumes would be, but apparently
this doesn't seem to be the case :-/
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-07-06 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 16:12 strange corruptions found during btrfs check Christoph Anton Mitterer
2015-07-06 18:40 ` Christoph Anton Mitterer [this message]
2015-07-07 0:47 ` Duncan
2015-07-07 1:03 ` Christoph Anton Mitterer
2015-07-07 2:08 ` Duncan
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=1436208023.7124.6.camel@scientia.net \
--to=calestyo@scientia.net \
--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).