Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Joel Parthemore <joel@parthemores.com>
To: Yu Kuai <yukuai1@huaweicloud.com>, Roman Mamedov <rm@romanrm.net>
Cc: linux-raid@vger.kernel.org, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: request for help on IMSM-metadata RAID-5 array
Date: Fri, 29 Sep 2023 21:44:09 +0200	[thread overview]
Message-ID: <9c67d4b6-9b7d-467c-827a-729f62348d54@parthemores.com> (raw)
In-Reply-To: <86dd0750-d060-eada-dc16-03a783c3bd1d@huaweicloud.com>

[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]

Den 2023-09-26 kl. 03:10, skrev Yu Kuai:


>>> It'll be much helper for developers to collect kernel stack for all 
>>> stuck thread(and it'll be much better to use add2line).
>>
>>
>> Presuming I can re-create the problem, let me know what I should do 
>> to collect that information for you. I'm very much a newbie in that 
>> area.
>
> You can use following cmd:
>
> for pid in `ps -elf | grep " D " | awk '{print $4}'`; do ps $pid; cat 
> /proc/$pid/stack; done
>
> Thanks,
> Kuai


for pid in `ps -elf | grep " D " | awk '{print $4}'`; do ps $pid; cat 
/proc/$pid/stack; done
   PID TTY      STAT   TIME COMMAND
  4017 tty1     D+     0:00 e2fsck /dev/md126
[<0>] md_write_start+0x191/0x310
[<0>] raid5_make_request+0x90/0x1230 [raid456]
[<0>] md_handle_request+0x129/0x210
[<0>] __submit_bio+0x7f/0x110
[<0>] submit_bio_noacct_nocheck+0x150/0x360
[<0>] __block_write_full_folio+0x1d8/0x3f0
[<0>] writepage_cb+0x11/0x70
[<0>] write_cache_pages+0x13a/0x390
[<0>] do_writepages+0x15b/0x1e0
[<0>] filemap_fdatawrite_wbc+0x5a/0x80
[<0>] __filemap_fdatawrite_range+0x53/0x80
[<0>] filemap_write_and_wait_range+0x3a/0xa0
[<0>] blkdev_put+0x116/0x1c0
[<0>] blkdev_release+0x22/0x30
[<0>] __fput+0xe5/0x290
[<0>] task_work_run+0x51/0x80
[<0>] exit_to_user_mode_prepare+0x132/0x140
[<0>] syscall_exit_to_user_mode+0x1d/0x50
[<0>] do_syscall_64+0x46/0x90
[<0>] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
   PID TTY      STAT   TIME COMMAND
cat: /proc/5266/stack: Filen eller katalogen finns inte


-- 
---------------------------------------------------------------
- Joel Parthemore - philosopher - academic proofreader --------
- English teacher - technology instructor - editor ------------
- "We are all in the gutter, but some of us are looking at the-
- "stars." - Oscar Wilde --------------------------------------
---------------------------------------------------------------


[-- Attachment #2: S/MIME-kryptografisk signatur --]
[-- Type: application/pkcs7-signature, Size: 4005 bytes --]

  reply	other threads:[~2023-09-29 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 10:54 request for help on IMSM-metadata RAID-5 array Joel Parthemore
2023-09-23 11:24 ` Roman Mamedov
2023-09-23 15:18   ` Joel Parthemore
2023-09-23 15:35     ` Roman Mamedov
2023-09-23 15:45       ` Joel Parthemore
2023-09-23 18:49       ` Joel Parthemore
2023-09-25  1:43         ` Yu Kuai
2023-09-25 15:57           ` Joel Parthemore
2023-09-26  1:10             ` Yu Kuai
2023-09-29 19:44               ` Joel Parthemore [this message]
     [not found]                 ` <a0b8a693-5d9c-d354-5afc-4500b78a983e@huaweicloud.com>
2023-10-05  7:28                   ` Joel Parthemore
2023-09-25  9:44 ` Mariusz Tkaczyk
2023-09-25 15:52   ` Joel Parthemore
2023-09-25 16:43     ` Mariusz Tkaczyk

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=9c67d4b6-9b7d-467c-827a-729f62348d54@parthemores.com \
    --to=joel@parthemores.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.net \
    --cc=yukuai1@huaweicloud.com \
    --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