From: "János Tóth F." <toth.f.janos@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs/RAID5 became unmountable after SATA cable fault
Date: Thu, 22 Oct 2015 03:18:52 +0200 [thread overview]
Message-ID: <56283981.294fb40a.5301a.5630@mx.google.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1119 bytes --]
I tried that after every possible combinations of RO mount failed. I used it in the past for an USB attached drive where an USB-SATA adapter had some issues (I plugged it into a standard USB2 port even though it expected USB3 power current, so a high-current or several standard USB2 ports should have been used to prevent it from emergency shutdown during file copy). It worked flawlessly then but in this case it threw the same errors as "btrsf check". It couldn't even find and list alternative roots. Every tools seemed to give up really fast and easy, sometimes with segfaults and tracing messages in the kernel log.On Oct 21, 2015 22:26, Chris Murphy <lists@colorremedies.com> wrote:
>
> https://btrfs.wiki.kernel.org/index.php/Restore
>
> This should still be possible with even a degraded/unmounted raid5. It
> is a bit tedious to figure out how to use it but if you've got some
> things you want off the volume, it's not so difficult to prevent
> trying it.
>
>
> Chris Murphy
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±ý»k~ÏâØ^nr¡ö¦zË\x1aëh¨èÚ&£ûàz¿äz¹Þú+Ê+zf£¢·h§~Ûiÿÿïêÿêçz_è®\x0fæj:+v¨þ)ߣøm
next reply other threads:[~2015-10-22 1:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 1:18 János Tóth F. [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-23 13:20 Btrfs/RAID5 became unmountable after SATA cable fault Janos Toth F.
[not found] <g7loe3red3ksp64hmb0vsbs2.1445476794489@email.android.com>
2015-11-04 18:01 ` Janos Toth F.
2015-11-04 18:45 ` Austin S Hemmelgarn
2015-11-05 4:06 ` Duncan
2015-11-05 12:30 ` Austin S Hemmelgarn
2015-11-06 3:19 ` Zoiled
2015-11-06 9:03 ` Janos Toth F.
2015-11-06 10:23 ` Patrik Lundquist
2015-10-19 8:39 Janos Toth F.
2015-10-20 14:59 ` Duncan
2015-10-21 16:09 ` Janos Toth F.
2015-10-21 16:44 ` ronnie sahlberg
2015-10-21 17:42 ` ronnie sahlberg
2015-10-21 18:40 ` Janos Toth F.
2015-10-21 17:46 ` Janos Toth F.
2015-10-21 20:26 ` Chris Murphy
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=56283981.294fb40a.5301a.5630@mx.google.com \
--to=toth.f.janos@gmail.com \
--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).