From: Genes Lists <lists@sapience.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: song@kernel.org, yukuai3@huawei.com, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, linux@leemhuis.info
Subject: Re: md-raid 6.11.8 page fault oops
Date: Wed, 20 Nov 2024 06:04:25 -0500 [thread overview]
Message-ID: <9ad77de15c483d31ba10b4b7bcf65a9e133f63ae.camel@sapience.com> (raw)
In-Reply-To: <Zz23Z3RK/AHSXY1I@li-bb2b2a4c-3307-11b2-a85c-8fa5c3a69313.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 498 bytes --]
On Wed, 2024-11-20 at 15:48 +0530, Ojaswin Mujoo wrote:
>
> Got it, I'm still not sure what might be causing this oops. Would you
> happen to a have a reproducer that I can play around with on my
> system?
>
> Regards,
> ojaswin
>
Sorry, unfortunately I do not have a reproducer otherwise I could
bisect. This system has an rsync backup of about 5 TB twice a day
(receives data over net and writes to local raid disks) - and it
happened during one of them.
gene
--
Gene
[-- Attachment #1.2: Type: text/html, Size: 1134 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-11-20 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 12:12 Genes Lists
2024-11-15 17:55 ` Song Liu
2024-11-16 3:34 ` Yu Kuai
2024-11-16 12:01 ` Genes Lists
2024-11-18 10:34 ` Mikulas Patocka
2024-11-19 11:49 ` Yu Kuai
2024-11-17 17:23 ` Genes Lists
2024-11-18 1:14 ` Yu Kuai
2024-11-20 11:48 ` md-raid 6.11.8 page fault oops - *bad memory* please ignore Genes Lists
2024-11-19 11:34 ` md-raid 6.11.8 page fault oops Ojaswin Mujoo
2024-11-19 13:31 ` Genes Lists
2024-11-20 10:18 ` Ojaswin Mujoo
2024-11-20 11:04 ` Genes Lists [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=9ad77de15c483d31ba10b4b7bcf65a9e133f63ae.camel@sapience.com \
--to=lists@sapience.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=ojaswin@linux.ibm.com \
--cc=song@kernel.org \
--cc=tytso@mit.edu \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®