From: chainofflowers <chainofflowers@neuromante.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Access Beyond End of Device & Input/Output Errors
Date: Mon, 18 Jan 2021 22:07:18 +0100 [thread overview]
Message-ID: <83f3d990-dc07-8070-aa07-303a6b8507be@neuromante.net> (raw)
In-Reply-To: <09596ccd-56b4-d55e-ad06-26d5c84b9ab6@gmx.com>
Thanks, I put everything in place... I am now waiting for the next
occurrence...
> The best way to debug such problem is to recompile the kernel adding
> some debug outputs.
> (Maybe it can be done with bpftrace, but not yet familiar with that)
>
> If you're able to recompile the kenerl (using abs + makepkg for Arch
> based kernel), please try the following diff.
>
> This will add extra debugging to show where the offending length
> happens, either extent discard or unallocated space discard.
> And from that output we can continue our investigation.
>
> Thanks,
> Qu
next prev parent reply other threads:[~2021-01-18 21:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 23:38 Access Beyond End of Device & Input/Output Errors chainofflowers
2021-01-18 0:11 ` Qu Wenruo
2021-01-18 21:07 ` chainofflowers [this message]
2021-01-21 23:55 ` chainofflowers
2021-01-22 0:49 ` Qu Wenruo
2021-02-08 21:05 ` chainofflowers
2021-02-20 11:26 ` chainofflowers
2021-02-20 11:42 ` Qu Wenruo
2021-02-20 11:46 ` Forza
2021-02-20 12:07 ` chainofflowers
2021-02-20 12:13 ` Qu Wenruo
2021-04-23 23:36 ` chainofflowers
2021-04-24 0:25 ` Qu Wenruo
2021-04-24 14:13 ` chainofflowers
2021-04-24 22:56 ` Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2020-08-01 6:51 Justin Brown
2020-08-01 6:58 ` Qu Wenruo
2020-08-01 7:02 ` Qu Wenruo
[not found] ` <CAKZK7uzmg19NDjGPPAxXKu7LJ-7ZdHu2cad22csj_chr2qxMJg@mail.gmail.com>
2020-08-01 9:31 ` Qu Wenruo
2020-08-01 11:56 ` Justin Brown
2020-08-01 23:30 ` Qu Wenruo
2020-09-06 1:42 ` Justin Brown
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=83f3d990-dc07-8070-aa07-303a6b8507be@neuromante.net \
--to=chainofflowers@neuromante.net \
--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).