From: Hugo Mills <hugo@carfax.org.uk>
To: Christian Wimmer <telefonchris@icloud.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: is this the right place for a question on how to repair a broken btrfs file system?
Date: Thu, 5 Dec 2019 20:24:49 +0000 [thread overview]
Message-ID: <20191205202449.GH4760@savella.carfax.org.uk> (raw)
In-Reply-To: <A01B0EC4-8E96-486B-A182-76B74AD0F97D@icloud.com>
On Thu, Dec 05, 2019 at 05:00:40PM -0300, Christian Wimmer wrote:
> Hi, my name is Chris,
>
> is this the right place for asking on support on how to repair a broken btrfs?
>
> There is no hardware problem, just that the power went out and now I can not mount any more.
What does dmesg say when you try to mount the FS?
> Who is the best specialist that could help here?
>
> Of course I already scanned the WEB some hours and tried all not-destructive commands without success.
"Non-destructive" is a fairly limited of things, and most of the
easily-findable advice on the web about fixing btrfs filesystems is at
best badly misguided, if not actively wrong. :(
Can you also tell us exactly what you ran?
Hugo.
--
Hugo Mills | Is it true that "last known good" on Windows XP
hugo@... carfax.org.uk | boots into CP/M?
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Adrian Bridgett
next prev parent reply other threads:[~2019-12-05 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 20:00 is this the right place for a question on how to repair a broken btrfs file system? Christian Wimmer
2019-12-05 20:24 ` Hugo Mills [this message]
2019-12-05 20:42 ` Christian Wimmer
2019-12-06 0:04 ` Qu Wenruo
2019-12-06 1:32 ` Christian Wimmer
[not found] ` <BD72A51F-A536-428C-9993-91A43C99EE30@icloud.com>
2019-12-06 2:12 ` Qu Wenruo
2019-12-06 2:13 ` Qu Wenruo
[not found] ` <DBA30D34-E186-4359-A8C5-C13C870F1D81@icloud.com>
2019-12-06 3:49 ` Qu Wenruo
2019-12-06 21:28 ` Christian Wimmer
2019-12-05 22:01 ` Christian Wimmer
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=20191205202449.GH4760@savella.carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=telefonchris@icloud.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).