From: Roman Mamedov <rm@romanrm.net>
To: Neko-san <nekoNexus@proton.me>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [Help?] "errors" found in fs roots
Date: Mon, 2 May 2022 22:22:10 +0500 [thread overview]
Message-ID: <20220502222210.6893657f@nvm> (raw)
In-Reply-To: <6mLGKEfkxtWN7Z-dUziEgizAdclo0RftcmcYG74zaXY1F0hgqeknrqKc5CGo0IjliM7_2BAp515jR3X1OJ5GzqTG8-QWOPDe56goD2dSZm8=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
On Mon, 02 May 2022 16:51:09 +0000
Neko-san <nekoNexus@proton.me> wrote:
> Is no one willing to help with this?
"here's a cloud link"
It could be most people thought it was too much of a barrier to entry to just
"take a look". I have downloaded your files and attaching them to this E-Mail
now. Let's see if it goes through -- raw files didn't, but in gzip it's not
anything huge after all.
Thanks
--
With respect,
Roman
[-- Attachment #2: btrfs-check.log.gz --]
[-- Type: application/gzip, Size: 214684 bytes --]
[-- Attachment #3: dmesg.log.gz --]
[-- Type: application/gzip, Size: 25372 bytes --]
next prev parent reply other threads:[~2022-05-02 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 6:19 [Help?] "errors" found in fs roots Neko-san
2022-05-02 16:51 ` Neko-san
2022-05-02 17:22 ` Roman Mamedov [this message]
2022-05-03 10:31 ` Roman Mamedov
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=20220502222210.6893657f@nvm \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nekoNexus@proton.me \
/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