From: "John Stoffel" <john@stoffel.org>
To: Liam Zeng <zqwliam@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [bug] Hi, need your help about raid1 causing kernel panic!
Date: Thu, 5 Jan 2023 20:01:55 -0500 [thread overview]
Message-ID: <25527.29443.610761.668848@quad.stoffel.home> (raw)
In-Reply-To: <CAMmbgcZADtyYp0xsu7qtiXL7hNZNex-OumCf+QFj81ZF9ZfYsw@mail.gmail.com>
>>>>> "Liam" == Liam Zeng <zqwliam@gmail.com> writes:
> Hope you kindly forgive my troubles. I have worked with a bug for
> several days, and I really need your help, even a kind
> encouragement.
You need to provide more details. What is your disk setup, what is
your OS base, etc.
> here's some informations
> kernel version: 5.10.107
Is this is a vendor kernel or your own self-compiled one? And if so,
can you move to the latest 6.x kernel instead?
> cpu arch: arm64
> the system install on /dev/md9, which make up of raid1 of two disks;
More details on this setup. Type of disks, their connectivity to the
system, etc.
> the bug: every time I transfer files (50G file, using samba or ftp),
> the system will break down.
Does it break if you copy the file on the system? Do you have enough
disk space to copy a 10g file from one directory to another on the
same RAID1 setup?
Which filesystem are you using?
> I have not modified any code of md.
Good to know.
> And the attachment is the log.
Sorry, I'm not going to bother decoding it. Just attach it as plain
text instead please.
> I would appreciate any reply!
> [DELETED ATTACHMENT kernel_panic_log, Untyped binary data]
prev parent reply other threads:[~2023-01-06 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 1:28 [bug] Hi, need your help about raid1 causing kernel panic! Liam Zeng
2023-01-06 1:01 ` John Stoffel [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=25527.29443.610761.668848@quad.stoffel.home \
--to=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--cc=zqwliam@gmail.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