linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: <linux-btrfs@vger.kernel.org>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
	Roman Mamedov <rm@romanrm.net>, Hugo Mills <hugo@carfax.org.uk>
Subject: Re: Uncorrectable errors after rebooting with Magic Sysrq Keys
Date: Sat, 30 Apr 2016 15:11:58 +0200	[thread overview]
Message-ID: <b0bceaf1-b5a2-47b4-8f8b-a06af171cfbc@linuxsystems.it> (raw)
In-Reply-To: <e359750f-9fbe-46d5-b16e-adc83539722b@linuxsystems.it>

Finally my external drive arrived and I've been able to make a backup and 
try btrfs check --repair.
Unfortunately btrfs check --repair got stuck in an infinite loop like this 
one (https://www.spinics.net/lists/linux-btrfs/msg54146.html) and after 
several hours of looping and several Gigabytes of logs I had to kill it, 
which gave me a completely fucked fs.
I still have backup images, so I can restore the old state and try again 
with updated tools (I used latest btrfs-progs 4.5.1, but I also tried 
4.4.1).
For those who didn't read the whole thread I can mount the fs, but it hangs 
while trying to read certain files and sometimes it remounts read-only. I'm 
pretty sure the culprit was a bug in 4.6-rc because problems started 
roughly after upgrading. Disk (an SSD) is fine. The fs is on top of 
dm-crypt and I always mounted it with 
"rw,relatime,ssd,space_cache,discard,compress=lzo,autodefrag".

You can find the whole logs here: 
https://drive.google.com/open?id=0Bwe9Wtc-5xF1Z2YwN1Y4U0ROSUU

01_scrub is the scrub output
02_check is the btrfs check output (14MB)
03_repair_short is the btrfs check --repair output truncated to 14MB

I hope someone will be able to help me recover my data, otherwise I will 
have to backup just the most important files and reinstall the whole system 
from scratch. Mounting the fs and doing a backup with cp -a wasn't a viable 
solution because it got stuck after several GBs.

Niccolò

P.S.
I changed my spf/dkim/dmarc settings, this email should no longer go into 
the spam folder, if it does please let me know. Thanks.

      reply	other threads:[~2016-04-30 13:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  8:21 Uncorrectable errors after rebooting with Magic Sysrq Keys Niccolò Belli
2016-04-15  9:30 ` Qu Wenruo
2016-04-15 15:42   ` Niccolò Belli
2016-04-15 15:45     ` Hugo Mills
2016-04-15 17:28       ` Niccolò Belli
2016-04-15 16:58     ` Roman Mamedov
2016-04-16 10:25       ` Niccolò Belli
2016-04-30 13:11         ` Niccolò Belli [this message]

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=b0bceaf1-b5a2-47b4-8f8b-a06af171cfbc@linuxsystems.it \
    --to=darkbasic@linuxsystems.it \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.com \
    --cc=rm@romanrm.net \
    /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).