From: Giuseppe Della Bianca <bepi@adria.it>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive
Date: Sun, 27 Nov 2016 19:18:38 +0100 [thread overview]
Message-ID: <1606562.nMLPFcA8R6@exnet.gdb.it> (raw)
In-Reply-To: <CAJCQCtRpppbJb4a_zEdRFi7Fbxnhg5VkLktHuLMW2Z0H-cOkDg@mail.gmail.com>
I have reinstalled from scratch my system (for remote receiving of the
snapshot).
Now it uses the 4.8.8-100.fc23.x86_64 kernel, and now I have a separate
partition for '''possible dangerous''' test.
I do not remember the exact sequence that caused the corruption of the file
system, but now it worked without problem.
If I have problems again, I will update the btrfs-tools and I will try to fix.
P.S The silent and unrecoverable corruption are not entirely friendly ( :) ).
Thank you for answer.
Gdb
> I haven't seen this with 4.7.10. I suggest running 'btrfs check'
> (without repair) using a recent btrfs-progs. You can find 4.8.3 in
> koji, just download the appropriate rpm, and 'dnf update *rpm'
>
> As for kernel, Fedora 23 has 4.8.8 in updates (stable) and 4.8.10 is
> in updates-testing, I suggest moving to one of those.
>
>
> Chris Murphy
next prev parent reply other threads:[~2016-11-27 18:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 12:09 [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive bepi
2016-11-26 14:56 ` Giuseppe Della Bianca
2016-11-26 18:56 ` Chris Murphy
2016-11-27 18:18 ` Giuseppe Della Bianca [this message]
2016-12-04 18:11 ` Giuseppe Della Bianca
2016-12-18 19:59 ` Giuseppe Della Bianca
2016-12-18 20:12 ` Chris Murphy
2016-12-18 21:36 ` Xin Zhou
2016-12-19 12:46 ` bepi
2016-12-19 13:04 ` bepi
2016-12-19 18:55 ` Giuseppe Della Bianca
2016-12-20 17:43 ` Xin Zhou
2016-12-21 12:27 ` bepi
2016-12-21 21:09 ` Chris Murphy
2016-12-21 21:11 ` Chris Murphy
2016-12-21 22:14 ` Xin Zhou
2016-12-23 7:28 ` Giuseppe Della Bianca
2016-12-23 16:53 ` Xin Zhou
2016-12-23 17:48 ` bepi
2016-12-23 18:35 ` Xin Zhou
2016-12-24 12:16 ` Giuseppe Della Bianca
2016-12-24 20:15 ` Xin Zhou
2016-12-25 22:57 ` Duncan
2016-12-26 2:36 ` Xin Zhou
2016-12-26 3:52 ` Duncan
2016-12-27 3:20 ` Xin Zhou
2016-12-26 11:04 ` Giuseppe Della Bianca
2016-12-26 17:41 ` Xin Zhou
2016-12-24 12:47 ` Giuseppe Della Bianca
2017-08-19 14:56 ` Giuseppe Della Bianca
2016-12-23 7:16 ` Giuseppe Della Bianca
2016-12-27 9:29 ` Giuseppe Della Bianca
2016-12-26 11:24 ` Giuseppe Della Bianca
2016-12-19 4:53 ` Qu Wenruo
2016-12-19 12:54 ` bepi
-- strict thread matches above, loose matches on Subject: below --
2016-11-22 13:19 bepi
[not found] <CAJCQCtRmmMc3QwhFAkGqFPLc1_C4VpZCei_cevncUJduTJmg@mail.gmail.com>
2016-12-18 20:39 ` Giuseppe Della Bianca
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=1606562.nMLPFcA8R6@exnet.gdb.it \
--to=bepi@adria.it \
--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).