# Plantage machine sur mv sur un gros répertoire (Debian 10)

**URL:** <https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503>\
**Category:** Support Debian\
**Tags:** buster, ext2, raid\
**Created:** [Juin 22, 2019, 11:15 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503 "2019-06-22T23:15:36Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![AQkinkin](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/e79b87/32.png) [@AQkinkin](https://www.debian-fr.org/u/AQkinkin)\
**Post date:** [Juin 22, 2019, 11:15 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/1 "2019-06-22T23:15:37Z")

</div>

Bonjour,

Je viens de monter sur mon 3 disques de 500 Go pour faire un nouveau Raid 5.  
Afin de réaliser ce nouveau raid, j’ai déplacé des données d’un des disques vers le Raid existant.  
Il s’agissait du grosse opération, plus de 300 Go.  
Message :

```nohighlight
INFO: task mv:XXXXX blocked for more than 120 seconds.
Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

```

impossible à arrêter la tache (kill -9,-15)  
Arrêt du PC.  
Au redémarrage, passage en mode maintenance, car le raid était désactivé avec 1 disque en moins.

J’ai reconstruit mon Raid puis j’ai fait la copie de fichier répertoire / répertoire.

J’ai créer le Raid. (Ce sont des raids logiciel)

J’ai commencer à déplacer les données de Films d’un autre disque vers mon nouveau Raid. ( Presque 500 Go)  
Même scénario, même message d’erreur.

Donc, la je suis inquiété.

J’ai choisie la Debian 10 car le noyau est 4.19 est que j’ai lu sur internet que pour utiliser un “Rizen 3 2200G”, il fallait une version 4.15 au minimum.

Dans le message d’erreur, ci-desous, je remarque que cela parle de ext4 mais j’utilise des partions ext2.

Avez-vous des conseil à me fournir afin d’avoir un system stable ?  
Passer sur ubuntu 19.04, Kernel 5.0 ?  
Passer sur ubuntu 18.04, Kernel 4.15 ?

Le message d’erreur:

```nohighlight
INFO: task md127_raid5:292 blocked for more than 120 seconds.
Jun 21 22:21:38 mynas kernel: [79509.810300] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:21:38 mynas kernel: [79509.810340] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:21:38 mynas kernel: [79509.810390] md127_raid5 D 0 292 2 0x80000000
Jun 21 22:21:38 mynas kernel: [79509.810394] Call Trace:
Jun 21 22:21:38 mynas kernel: [79509.810407] ? __schedule+0x2a2/0x870
Jun 21 22:21:38 mynas kernel: [79509.810410] schedule+0x28/0x80
Jun 21 22:21:38 mynas kernel: [79509.810422] md_super_wait+0x6e/0xa0 [md_mod]
Jun 21 22:21:38 mynas kernel: [79509.810426] ? finish_wait+0x80/0x80
Jun 21 22:21:38 mynas kernel: [79509.810435] md_update_sb.part.64+0x44c/0x8f0 [md_mod]
Jun 21 22:21:38 mynas kernel: [79509.810444] md_check_recovery+0x148/0x540 [md_mod]
Jun 21 22:21:38 mynas kernel: [79509.810451] raid5d+0x4b/0x5b0 [raid456]
Jun 21 22:21:38 mynas kernel: [79509.810457] ? try_to_del_timer_sync+0x4d/0x80
Jun 21 22:21:38 mynas kernel: [79509.810459] ? del_timer_sync+0x35/0x40
Jun 21 22:21:38 mynas kernel: [79509.810462] ? schedule_timeout+0x173/0x390
Jun 21 22:21:38 mynas kernel: [79509.810466] ? prepare_to_wait_event+0xbb/0x140
Jun 21 22:21:38 mynas kernel: [79509.810473] ? md_rdev_init+0xb0/0xb0 [md_mod]
Jun 21 22:21:38 mynas kernel: [79509.810480] md_thread+0x94/0x150 [md_mod]
Jun 21 22:21:38 mynas kernel: [79509.810483] ? finish_wait+0x80/0x80
Jun 21 22:21:38 mynas kernel: [79509.810486] kthread+0x112/0x130
Jun 21 22:21:38 mynas kernel: [79509.810488] ? kthread_bind+0x30/0x30
Jun 21 22:21:38 mynas kernel: [79509.810491] ret_from_fork+0x22/0x40
Jun 21 22:21:38 mynas kernel: [79509.810511] INFO: task kworker/u32:1:1503 blocked for more than 120 seconds.
Jun 21 22:21:38 mynas kernel: [79509.810552] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:21:38 mynas kernel: [79509.810586] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:21:38 mynas kernel: [79509.810630] kworker/u32:1 D 0 1503 2 0x80000000
Jun 21 22:21:38 mynas kernel: [79509.810638] Workqueue: writeback wb_workfn (flush-9:127)
Jun 21 22:21:38 mynas kernel: [79509.810640] Call Trace:
Jun 21 22:21:38 mynas kernel: [79509.810643] ? __schedule+0x2a2/0x870
Jun 21 22:21:38 mynas kernel: [79509.810645] schedule+0x28/0x80
Jun 21 22:21:38 mynas kernel: [79509.810652] md_write_start+0x14b/0x220 [md_mod]
Jun 21 22:21:38 mynas kernel: [79509.810654] ? finish_wait+0x80/0x80
Jun 21 22:21:38 mynas kernel: [79509.810655] ? finish_wait+0x80/0x80
Jun 21 22:21:38 mynas kernel: [79509.810661] raid5_make_request+0x83/0xb60 [raid456]
Jun 21 22:21:38 mynas kernel: [79509.810665] ? blk_mq_timeout_work+0x120/0x120
Jun 21 22:21:38 mynas kernel: [79509.810668] ? blk_mq_timeout_work+0x120/0x120
Jun 21 22:21:38 mynas kernel: [79509.810669] ? finish_wait+0x80/0x80
Jun 21 22:21:38 mynas kernel: [79509.810671] ? finish_wait+0x80/0x80
Jun 21 22:21:38 mynas kernel: [79509.810678] md_handle_request+0x119/0x190 [md_mod]
Jun 21 22:21:38 mynas kernel: [79509.810686] md_make_request+0x78/0x160 [md_mod]
Jun 21 22:21:38 mynas kernel: [79509.810689] generic_make_request+0x1a4/0x410
Jun 21 22:21:38 mynas kernel: [79509.810693] submit_bio+0x45/0x140
Jun 21 22:21:38 mynas kernel: [79509.810696] ? guard_bio_eod+0x32/0x100
Jun 21 22:21:38 mynas kernel: [79509.810698] submit_bh_wbc+0x163/0x190
Jun 21 22:21:38 mynas kernel: [79509.810700] __block_write_full_page+0x22b/0x440
Jun 21 22:21:38 mynas kernel: [79509.810702] ? touch_buffer+0x60/0x60
Jun 21 22:21:38 mynas kernel: [79509.810704] ? check_disk_change+0x60/0x60
Jun 21 22:21:38 mynas kernel: [79509.810707] __writepage+0x19/0x50
Jun 21 22:21:38 mynas kernel: [79509.810710] write_cache_pages+0x1e1/0x470
Jun 21 22:21:38 mynas kernel: [79509.810712] ? __wb_calc_thresh+0x130/0x130
Jun 21 22:21:38 mynas kernel: [79509.810715] generic_writepages+0x56/0x90
Jun 21 22:21:38 mynas kernel: [79509.810718] do_writepages+0x41/0xd0
Jun 21 22:21:38 mynas kernel: [79509.810720] ? enqueue_entity+0xf6/0x630
Jun 21 22:21:38 mynas kernel: [79509.810723] ? enqueue_task_fair+0x79/0x190
Jun 21 22:21:38 mynas kernel: [79509.810725] __writeback_single_inode+0x3d/0x360
Jun 21 22:21:38 mynas kernel: [79509.810728] ? check_preempt_curr+0x7a/0x90
Jun 21 22:21:38 mynas kernel: [79509.810730] writeback_sb_inodes+0x1e3/0x450
Jun 21 22:21:38 mynas kernel: [79509.810733] __writeback_inodes_wb+0x5d/0xb0
Jun 21 22:21:38 mynas kernel: [79509.810735] wb_writeback+0x25f/0x2f0
Jun 21 22:21:38 mynas kernel: [79509.810738] wb_workfn+0x30d/0x400
Jun 21 22:21:38 mynas kernel: [79509.810742] ? __switch_to+0x15b/0x440
Jun 21 22:21:38 mynas kernel: [79509.810745] process_one_work+0x1a7/0x3a0
Jun 21 22:21:38 mynas kernel: [79509.810748] worker_thread+0x30/0x390
Jun 21 22:21:38 mynas kernel: [79509.810750] ? create_worker+0x1a0/0x1a0
Jun 21 22:21:38 mynas kernel: [79509.810751] kthread+0x112/0x130
Jun 21 22:21:38 mynas kernel: [79509.810753] ? kthread_bind+0x30/0x30
Jun 21 22:21:38 mynas kernel: [79509.810755] ret_from_fork+0x22/0x40
Jun 21 22:21:38 mynas kernel: [79509.810758] INFO: task mv:1506 blocked for more than 120 seconds.
Jun 21 22:21:38 mynas kernel: [79509.810794] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:21:38 mynas kernel: [79509.810828] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:21:38 mynas kernel: [79509.810875] mv D 0 1506 1396 0x00000000
Jun 21 22:21:38 mynas kernel: [79509.810877] Call Trace:
Jun 21 22:21:38 mynas kernel: [79509.810879] ? __schedule+0x2a2/0x870
Jun 21 22:21:38 mynas kernel: [79509.810882] ? __switch_to_asm+0x34/0x70
Jun 21 22:21:38 mynas kernel: [79509.810884] ? __switch_to_asm+0x40/0x70
Jun 21 22:21:38 mynas kernel: [79509.810886] ? bit_wait_timeout+0x90/0x90
Jun 21 22:21:38 mynas kernel: [79509.810887] schedule+0x28/0x80
Jun 21 22:21:38 mynas kernel: [79509.810889] io_schedule+0x12/0x40
Jun 21 22:21:38 mynas kernel: [79509.810892] bit_wait_io+0xd/0x50
Jun 21 22:21:38 mynas kernel: [79509.810894] __wait_on_bit+0x73/0x90
Jun 21 22:21:38 mynas kernel: [79509.810896] out_of_line_wait_on_bit+0x91/0xb0
Jun 21 22:21:38 mynas kernel: [79509.810898] ? init_wait_var_entry+0x40/0x40
Jun 21 22:21:38 mynas kernel: [79509.810916] ext4_wait_block_bitmap+0x64/0xb0 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.810938] ext4_mb_init_cache+0x1be/0x710 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.810959] ext4_mb_init_group+0x191/0x2c0 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.810979] ext4_mb_good_group+0x154/0x170 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.810998] ext4_mb_regular_allocator+0x28d/0x420 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811018] ? ext4_mb_normalize_request.constprop.35+0x290/0x490 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811037] ext4_mb_new_blocks+0x4f6/0xb20 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811039] ? __getblk_gfp+0x2c/0x280
Jun 21 22:21:38 mynas kernel: [79509.811058] ? ext4_get_branch+0xb5/0x130 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811076] ext4_ind_map_blocks+0x52e/0xaa0 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811080] ? __blk_mq_run_hw_queue+0x4e/0xe0
Jun 21 22:21:38 mynas kernel: [79509.811084] ? memcg_kmem_get_cache+0x6b/0x1e0
Jun 21 22:21:38 mynas kernel: [79509.811103] ext4_map_blocks+0x241/0x5c0 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811122] _ext4_get_block+0x8e/0x110 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811140] ext4_block_write_begin+0x14c/0x4c0 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811159] ? _ext4_get_block+0x110/0x110 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811176] ? __ext4_journal_start_sb+0x34/0x120 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811194] ext4_write_begin+0x22a/0x5c0 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811199] generic_perform_write+0xf4/0x1b0
Jun 21 22:21:38 mynas kernel: [79509.811203] ? file_update_time+0xed/0x130
Jun 21 22:21:38 mynas kernel: [79509.811205] __generic_file_write_iter+0xfe/0x1c0
Jun 21 22:21:38 mynas kernel: [79509.811223] ext4_file_write_iter+0xc6/0x400 [ext4]
Jun 21 22:21:38 mynas kernel: [79509.811225] ? page_cache_tree_insert+0xe0/0xe0
Jun 21 22:21:38 mynas kernel: [79509.811228] new_sync_write+0xfb/0x160
Jun 21 22:21:38 mynas kernel: [79509.811231] vfs_write+0xa5/0x1a0
Jun 21 22:21:38 mynas kernel: [79509.811233] ksys_write+0x4f/0xb0
Jun 21 22:21:38 mynas kernel: [79509.811238] do_syscall_64+0x53/0x110
Jun 21 22:21:38 mynas kernel: [79509.811241] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 21 22:21:38 mynas kernel: [79509.811244] RIP: 0033:0x7f9a9678a504
Jun 21 22:21:38 mynas kernel: [79509.811252] Code: Bad RIP value.
Jun 21 22:21:38 mynas kernel: [79509.811253] RSP: 002b:00007ffcbf598d68 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
Jun 21 22:21:38 mynas kernel: [79509.811255] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007f9a9678a504
Jun 21 22:21:38 mynas kernel: [79509.811256] RDX: 0000000000020000 RSI: 0000564ba448a000 RDI: 0000000000000004
Jun 21 22:21:38 mynas kernel: [79509.811257] RBP: 0000564ba448a000 R08: 0000000000020000 R09: 0000000000000000
Jun 21 22:21:38 mynas kernel: [79509.811258] R10: 00007ffcbf598f78 R11: 0000000000000246 R12: 0000564ba448a000
Jun 21 22:21:38 mynas kernel: [79509.811259] R13: 0000000000000004 R14: 0000000000000000 R15: 0000000000020000
Jun 21 22:23:39 mynas kernel: [79630.644871] INFO: task md127_raid5:292 blocked for more than 120 seconds.
Jun 21 22:23:39 mynas kernel: [79630.644927] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:23:39 mynas kernel: [79630.644966] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:23:39 mynas kernel: [79630.645016] md127_raid5 D 0 292 2 0x80000000
Jun 21 22:23:39 mynas kernel: [79630.645020] Call Trace:
Jun 21 22:23:39 mynas kernel: [79630.645033] ? __schedule+0x2a2/0x870
Jun 21 22:23:39 mynas kernel: [79630.645036] schedule+0x28/0x80
Jun 21 22:23:39 mynas kernel: [79630.645048] md_super_wait+0x6e/0xa0 [md_mod]
Jun 21 22:23:39 mynas kernel: [79630.645052] ? finish_wait+0x80/0x80
Jun 21 22:23:39 mynas kernel: [79630.645061] md_update_sb.part.64+0x44c/0x8f0 [md_mod]
Jun 21 22:23:39 mynas kernel: [79630.645070] md_check_recovery+0x148/0x540 [md_mod]
Jun 21 22:23:39 mynas kernel: [79630.645077] raid5d+0x4b/0x5b0 [raid456]
Jun 21 22:23:39 mynas kernel: [79630.645082] ? try_to_del_timer_sync+0x4d/0x80
Jun 21 22:23:39 mynas kernel: [79630.645085] ? del_timer_sync+0x35/0x40
Jun 21 22:23:39 mynas kernel: [79630.645087] ? schedule_timeout+0x173/0x390
Jun 21 22:23:39 mynas kernel: [79630.645091] ? prepare_to_wait_event+0xbb/0x140
Jun 21 22:23:39 mynas kernel: [79630.645097] ? md_rdev_init+0xb0/0xb0 [md_mod]
Jun 21 22:23:39 mynas kernel: [79630.645104] md_thread+0x94/0x150 [md_mod]
Jun 21 22:23:39 mynas kernel: [79630.645106] ? finish_wait+0x80/0x80
Jun 21 22:23:39 mynas kernel: [79630.645109] kthread+0x112/0x130
Jun 21 22:23:39 mynas kernel: [79630.645111] ? kthread_bind+0x30/0x30
Jun 21 22:23:39 mynas kernel: [79630.645114] ret_from_fork+0x22/0x40
Jun 21 22:23:39 mynas kernel: [79630.645133] INFO: task kworker/u32:1:1503 blocked for more than 120 seconds.
Jun 21 22:23:39 mynas kernel: [79630.645173] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:23:39 mynas kernel: [79630.645208] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:23:39 mynas kernel: [79630.645252] kworker/u32:1 D 0 1503 2 0x80000000
Jun 21 22:23:39 mynas kernel: [79630.645260] Workqueue: writeback wb_workfn (flush-9:127)
Jun 21 22:23:39 mynas kernel: [79630.645262] Call Trace:
Jun 21 22:23:39 mynas kernel: [79630.645265] ? __schedule+0x2a2/0x870
Jun 21 22:23:39 mynas kernel: [79630.645267] schedule+0x28/0x80
Jun 21 22:23:39 mynas kernel: [79630.645274] md_write_start+0x14b/0x220 [md_mod]
Jun 21 22:23:39 mynas kernel: [79630.645276] ? finish_wait+0x80/0x80
Jun 21 22:23:39 mynas kernel: [79630.645278] ? finish_wait+0x80/0x80
Jun 21 22:23:39 mynas kernel: [79630.645283] raid5_make_request+0x83/0xb60 [raid456]
Jun 21 22:23:39 mynas kernel: [79630.645288] ? blk_mq_timeout_work+0x120/0x120
Jun 21 22:23:39 mynas kernel: [79630.645290] ? blk_mq_timeout_work+0x120/0x120
Jun 21 22:23:39 mynas kernel: [79630.645291] ? finish_wait+0x80/0x80
Jun 21 22:23:39 mynas kernel: [79630.645293] ? finish_wait+0x80/0x80
Jun 21 22:23:39 mynas kernel: [79630.645300] md_handle_request+0x119/0x190 [md_mod]
Jun 21 22:23:39 mynas kernel: [79630.645308] md_make_request+0x78/0x160 [md_mod]
Jun 21 22:23:39 mynas kernel: [79630.645312] generic_make_request+0x1a4/0x410
Jun 21 22:23:39 mynas kernel: [79630.645315] submit_bio+0x45/0x140
Jun 21 22:23:39 mynas kernel: [79630.645318] ? guard_bio_eod+0x32/0x100
Jun 21 22:23:39 mynas kernel: [79630.645320] submit_bh_wbc+0x163/0x190
Jun 21 22:23:39 mynas kernel: [79630.645322] __block_write_full_page+0x22b/0x440
Jun 21 22:23:39 mynas kernel: [79630.645324] ? touch_buffer+0x60/0x60
Jun 21 22:23:39 mynas kernel: [79630.645326] ? check_disk_change+0x60/0x60
Jun 21 22:23:39 mynas kernel: [79630.645330] __writepage+0x19/0x50
Jun 21 22:23:39 mynas kernel: [79630.645332] write_cache_pages+0x1e1/0x470
Jun 21 22:23:39 mynas kernel: [79630.645334] ? __wb_calc_thresh+0x130/0x130
Jun 21 22:23:39 mynas kernel: [79630.645338] generic_writepages+0x56/0x90
Jun 21 22:23:39 mynas kernel: [79630.645340] do_writepages+0x41/0xd0
Jun 21 22:23:39 mynas kernel: [79630.645343] ? enqueue_entity+0xf6/0x630
Jun 21 22:23:39 mynas kernel: [79630.645345] ? enqueue_task_fair+0x79/0x190
Jun 21 22:23:39 mynas kernel: [79630.645347] __writeback_single_inode+0x3d/0x360
Jun 21 22:23:39 mynas kernel: [79630.645351] ? check_preempt_curr+0x7a/0x90
Jun 21 22:23:39 mynas kernel: [79630.645353] writeback_sb_inodes+0x1e3/0x450
Jun 21 22:23:39 mynas kernel: [79630.645356] __writeback_inodes_wb+0x5d/0xb0
Jun 21 22:23:39 mynas kernel: [79630.645358] wb_writeback+0x25f/0x2f0
Jun 21 22:23:39 mynas kernel: [79630.645361] wb_workfn+0x30d/0x400
Jun 21 22:23:39 mynas kernel: [79630.645364] ? __switch_to+0x15b/0x440
Jun 21 22:23:39 mynas kernel: [79630.645367] process_one_work+0x1a7/0x3a0
Jun 21 22:23:39 mynas kernel: [79630.645370] worker_thread+0x30/0x390
Jun 21 22:23:39 mynas kernel: [79630.645372] ? create_worker+0x1a0/0x1a0
Jun 21 22:23:39 mynas kernel: [79630.645374] kthread+0x112/0x130
Jun 21 22:23:39 mynas kernel: [79630.645375] ? kthread_bind+0x30/0x30
Jun 21 22:23:39 mynas kernel: [79630.645378] ret_from_fork+0x22/0x40
Jun 21 22:23:39 mynas kernel: [79630.645381] INFO: task mv:1506 blocked for more than 120 seconds.
Jun 21 22:23:39 mynas kernel: [79630.645416] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:23:39 mynas kernel: [79630.645450] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:23:39 mynas kernel: [79630.645494] mv D 0 1506 1396 0x00000000
Jun 21 22:23:39 mynas kernel: [79630.645496] Call Trace:
Jun 21 22:23:39 mynas kernel: [79630.645499] ? __schedule+0x2a2/0x870
Jun 21 22:23:39 mynas kernel: [79630.645501] ? __switch_to_asm+0x34/0x70
Jun 21 22:23:39 mynas kernel: [79630.645503] ? __switch_to_asm+0x40/0x70
Jun 21 22:23:39 mynas kernel: [79630.645505] ? bit_wait_timeout+0x90/0x90
Jun 21 22:23:39 mynas kernel: [79630.645506] schedule+0x28/0x80
Jun 21 22:23:39 mynas kernel: [79630.645509] io_schedule+0x12/0x40
Jun 21 22:23:39 mynas kernel: [79630.645511] bit_wait_io+0xd/0x50
Jun 21 22:23:39 mynas kernel: [79630.645513] __wait_on_bit+0x73/0x90
Jun 21 22:23:39 mynas kernel: [79630.645515] out_of_line_wait_on_bit+0x91/0xb0
Jun 21 22:23:39 mynas kernel: [79630.645517] ? init_wait_var_entry+0x40/0x40
Jun 21 22:23:39 mynas kernel: [79630.645535] ext4_wait_block_bitmap+0x64/0xb0 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645557] ext4_mb_init_cache+0x1be/0x710 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645578] ext4_mb_init_group+0x191/0x2c0 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645598] ext4_mb_good_group+0x154/0x170 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645617] ext4_mb_regular_allocator+0x28d/0x420 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645637] ? ext4_mb_normalize_request.constprop.35+0x290/0x490 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645656] ext4_mb_new_blocks+0x4f6/0xb20 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645658] ? __getblk_gfp+0x2c/0x280
Jun 21 22:23:39 mynas kernel: [79630.645676] ? ext4_get_branch+0xb5/0x130 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645694] ext4_ind_map_blocks+0x52e/0xaa0 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645699] ? __blk_mq_run_hw_queue+0x4e/0xe0
Jun 21 22:23:39 mynas kernel: [79630.645702] ? memcg_kmem_get_cache+0x6b/0x1e0
Jun 21 22:23:39 mynas kernel: [79630.645722] ext4_map_blocks+0x241/0x5c0 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645741] _ext4_get_block+0x8e/0x110 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645759] ext4_block_write_begin+0x14c/0x4c0 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645778] ? _ext4_get_block+0x110/0x110 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645794] ? __ext4_journal_start_sb+0x34/0x120 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645813] ext4_write_begin+0x22a/0x5c0 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645817] generic_perform_write+0xf4/0x1b0
Jun 21 22:23:39 mynas kernel: [79630.645821] ? file_update_time+0xed/0x130
Jun 21 22:23:39 mynas kernel: [79630.645823] __generic_file_write_iter+0xfe/0x1c0
Jun 21 22:23:39 mynas kernel: [79630.645841] ext4_file_write_iter+0xc6/0x400 [ext4]
Jun 21 22:23:39 mynas kernel: [79630.645844] ? page_cache_tree_insert+0xe0/0xe0
Jun 21 22:23:39 mynas kernel: [79630.645847] new_sync_write+0xfb/0x160
Jun 21 22:23:39 mynas kernel: [79630.645850] vfs_write+0xa5/0x1a0
Jun 21 22:23:39 mynas kernel: [79630.645852] ksys_write+0x4f/0xb0
Jun 21 22:23:39 mynas kernel: [79630.645856] do_syscall_64+0x53/0x110
Jun 21 22:23:39 mynas kernel: [79630.645859] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 21 22:23:39 mynas kernel: [79630.645862] RIP: 0033:0x7f9a9678a504
Jun 21 22:23:39 mynas kernel: [79630.645870] Code: Bad RIP value.
Jun 21 22:23:39 mynas kernel: [79630.645871] RSP: 002b:00007ffcbf598d68 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
Jun 21 22:23:39 mynas kernel: [79630.645873] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007f9a9678a504
Jun 21 22:23:39 mynas kernel: [79630.645874] RDX: 0000000000020000 RSI: 0000564ba448a000 RDI: 0000000000000004
Jun 21 22:23:39 mynas kernel: [79630.645875] RBP: 0000564ba448a000 R08: 0000000000020000 R09: 0000000000000000
Jun 21 22:23:39 mynas kernel: [79630.645876] R10: 00007ffcbf598f78 R11: 0000000000000246 R12: 0000564ba448a000
Jun 21 22:23:39 mynas kernel: [79630.645877] R13: 0000000000000004 R14: 0000000000000000 R15: 0000000000020000
Jun 21 22:25:40 mynas kernel: [79751.479196] INFO: task md127_raid5:292 blocked for more than 120 seconds.
Jun 21 22:25:40 mynas kernel: [79751.479252] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:25:40 mynas kernel: [79751.479292] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:25:40 mynas kernel: [79751.479342] md127_raid5 D 0 292 2 0x80000000
Jun 21 22:25:40 mynas kernel: [79751.479346] Call Trace:
Jun 21 22:25:40 mynas kernel: [79751.479358] ? __schedule+0x2a2/0x870
Jun 21 22:25:40 mynas kernel: [79751.479362] schedule+0x28/0x80
Jun 21 22:25:40 mynas kernel: [79751.479374] md_super_wait+0x6e/0xa0 [md_mod]
Jun 21 22:25:40 mynas kernel: [79751.479378] ? finish_wait+0x80/0x80
Jun 21 22:25:40 mynas kernel: [79751.479387] md_update_sb.part.64+0x44c/0x8f0 [md_mod]
Jun 21 22:25:40 mynas kernel: [79751.479396] md_check_recovery+0x148/0x540 [md_mod]
Jun 21 22:25:40 mynas kernel: [79751.479404] raid5d+0x4b/0x5b0 [raid456]
Jun 21 22:25:40 mynas kernel: [79751.479409] ? try_to_del_timer_sync+0x4d/0x80
Jun 21 22:25:40 mynas kernel: [79751.479411] ? del_timer_sync+0x35/0x40
Jun 21 22:25:40 mynas kernel: [79751.479414] ? schedule_timeout+0x173/0x390
Jun 21 22:25:40 mynas kernel: [79751.479418] ? prepare_to_wait_event+0xbb/0x140
Jun 21 22:25:40 mynas kernel: [79751.479424] ? md_rdev_init+0xb0/0xb0 [md_mod]
Jun 21 22:25:40 mynas kernel: [79751.479431] md_thread+0x94/0x150 [md_mod]
Jun 21 22:25:40 mynas kernel: [79751.479433] ? finish_wait+0x80/0x80
Jun 21 22:25:40 mynas kernel: [79751.479436] kthread+0x112/0x130
Jun 21 22:25:40 mynas kernel: [79751.479438] ? kthread_bind+0x30/0x30
Jun 21 22:25:40 mynas kernel: [79751.479440] ret_from_fork+0x22/0x40
Jun 21 22:25:40 mynas kernel: [79751.479460] INFO: task kworker/u32:1:1503 blocked for more than 120 seconds.
Jun 21 22:25:40 mynas kernel: [79751.479501] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:25:40 mynas kernel: [79751.479536] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:25:40 mynas kernel: [79751.479579] kworker/u32:1 D 0 1503 2 0x80000000
Jun 21 22:25:40 mynas kernel: [79751.479588] Workqueue: writeback wb_workfn (flush-9:127)
Jun 21 22:25:40 mynas kernel: [79751.479589] Call Trace:
Jun 21 22:25:40 mynas kernel: [79751.479592] ? __schedule+0x2a2/0x870
Jun 21 22:25:40 mynas kernel: [79751.479594] schedule+0x28/0x80
Jun 21 22:25:40 mynas kernel: [79751.479601] md_write_start+0x14b/0x220 [md_mod]
Jun 21 22:25:40 mynas kernel: [79751.479603] ? finish_wait+0x80/0x80
Jun 21 22:25:40 mynas kernel: [79751.479605] ? finish_wait+0x80/0x80
Jun 21 22:25:40 mynas kernel: [79751.479610] raid5_make_request+0x83/0xb60 [raid456]
Jun 21 22:25:40 mynas kernel: [79751.479614] ? blk_mq_timeout_work+0x120/0x120
Jun 21 22:25:40 mynas kernel: [79751.479617] ? blk_mq_timeout_work+0x120/0x120
Jun 21 22:25:40 mynas kernel: [79751.479618] ? finish_wait+0x80/0x80
Jun 21 22:25:40 mynas kernel: [79751.479620] ? finish_wait+0x80/0x80
Jun 21 22:25:40 mynas kernel: [79751.479627] md_handle_request+0x119/0x190 [md_mod]
Jun 21 22:25:40 mynas kernel: [79751.479635] md_make_request+0x78/0x160 [md_mod]
Jun 21 22:25:40 mynas kernel: [79751.479638] generic_make_request+0x1a4/0x410
Jun 21 22:25:40 mynas kernel: [79751.479642] submit_bio+0x45/0x140
Jun 21 22:25:40 mynas kernel: [79751.479645] ? guard_bio_eod+0x32/0x100
Jun 21 22:25:40 mynas kernel: [79751.479647] submit_bh_wbc+0x163/0x190
Jun 21 22:25:40 mynas kernel: [79751.479649] __block_write_full_page+0x22b/0x440
Jun 21 22:25:40 mynas kernel: [79751.479651] ? touch_buffer+0x60/0x60
Jun 21 22:25:40 mynas kernel: [79751.479653] ? check_disk_change+0x60/0x60
Jun 21 22:25:40 mynas kernel: [79751.479657] __writepage+0x19/0x50
Jun 21 22:25:40 mynas kernel: [79751.479659] write_cache_pages+0x1e1/0x470
Jun 21 22:25:40 mynas kernel: [79751.479661] ? __wb_calc_thresh+0x130/0x130
Jun 21 22:25:40 mynas kernel: [79751.479664] generic_writepages+0x56/0x90
Jun 21 22:25:40 mynas kernel: [79751.479667] do_writepages+0x41/0xd0
Jun 21 22:25:40 mynas kernel: [79751.479670] ? enqueue_entity+0xf6/0x630
Jun 21 22:25:40 mynas kernel: [79751.479672] ? enqueue_task_fair+0x79/0x190
Jun 21 22:25:40 mynas kernel: [79751.479674] __writeback_single_inode+0x3d/0x360
Jun 21 22:25:40 mynas kernel: [79751.479677] ? check_preempt_curr+0x7a/0x90
Jun 21 22:25:40 mynas kernel: [79751.479680] writeback_sb_inodes+0x1e3/0x450
Jun 21 22:25:40 mynas kernel: [79751.479683] __writeback_inodes_wb+0x5d/0xb0
Jun 21 22:25:40 mynas kernel: [79751.479685] wb_writeback+0x25f/0x2f0
Jun 21 22:25:40 mynas kernel: [79751.479688] wb_workfn+0x30d/0x400
Jun 21 22:25:40 mynas kernel: [79751.479691] ? __switch_to+0x15b/0x440
Jun 21 22:25:40 mynas kernel: [79751.479694] process_one_work+0x1a7/0x3a0
Jun 21 22:25:40 mynas kernel: [79751.479697] worker_thread+0x30/0x390
Jun 21 22:25:40 mynas kernel: [79751.479699] ? create_worker+0x1a0/0x1a0
Jun 21 22:25:40 mynas kernel: [79751.479701] kthread+0x112/0x130
Jun 21 22:25:40 mynas kernel: [79751.479702] ? kthread_bind+0x30/0x30
Jun 21 22:25:40 mynas kernel: [79751.479705] ret_from_fork+0x22/0x40
Jun 21 22:25:40 mynas kernel: [79751.479708] INFO: task mv:1506 blocked for more than 120 seconds.
Jun 21 22:25:40 mynas kernel: [79751.479743] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:25:40 mynas kernel: [79751.479781] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:25:40 mynas kernel: [79751.479825] mv D 0 1506 1396 0x00000000
Jun 21 22:25:40 mynas kernel: [79751.479827] Call Trace:
Jun 21 22:25:40 mynas kernel: [79751.479830] ? __schedule+0x2a2/0x870
Jun 21 22:25:40 mynas kernel: [79751.479832] ? __switch_to_asm+0x34/0x70
Jun 21 22:25:40 mynas kernel: [79751.479834] ? __switch_to_asm+0x40/0x70
Jun 21 22:25:40 mynas kernel: [79751.479836] ? bit_wait_timeout+0x90/0x90
Jun 21 22:25:40 mynas kernel: [79751.479838] schedule+0x28/0x80
Jun 21 22:25:40 mynas kernel: [79751.479840] io_schedule+0x12/0x40
Jun 21 22:25:40 mynas kernel: [79751.479842] bit_wait_io+0xd/0x50
Jun 21 22:25:40 mynas kernel: [79751.479844] __wait_on_bit+0x73/0x90
Jun 21 22:25:40 mynas kernel: [79751.479846] out_of_line_wait_on_bit+0x91/0xb0
Jun 21 22:25:40 mynas kernel: [79751.479848] ? init_wait_var_entry+0x40/0x40
Jun 21 22:25:40 mynas kernel: [79751.479866] ext4_wait_block_bitmap+0x64/0xb0 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.479888] ext4_mb_init_cache+0x1be/0x710 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.479909] ext4_mb_init_group+0x191/0x2c0 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.479929] ext4_mb_good_group+0x154/0x170 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.479948] ext4_mb_regular_allocator+0x28d/0x420 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.479967] ? ext4_mb_normalize_request.constprop.35+0x290/0x490 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.479986] ext4_mb_new_blocks+0x4f6/0xb20 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.479988] ? __getblk_gfp+0x2c/0x280
Jun 21 22:25:40 mynas kernel: [79751.480007] ? ext4_get_branch+0xb5/0x130 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480025] ext4_ind_map_blocks+0x52e/0xaa0 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480029] ? __blk_mq_run_hw_queue+0x4e/0xe0
Jun 21 22:25:40 mynas kernel: [79751.480033] ? memcg_kmem_get_cache+0x6b/0x1e0
Jun 21 22:25:40 mynas kernel: [79751.480052] ext4_map_blocks+0x241/0x5c0 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480071] _ext4_get_block+0x8e/0x110 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480089] ext4_block_write_begin+0x14c/0x4c0 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480108] ? _ext4_get_block+0x110/0x110 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480124] ? __ext4_journal_start_sb+0x34/0x120 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480143] ext4_write_begin+0x22a/0x5c0 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480148] generic_perform_write+0xf4/0x1b0
Jun 21 22:25:40 mynas kernel: [79751.480151] ? file_update_time+0xed/0x130
Jun 21 22:25:40 mynas kernel: [79751.480154] __generic_file_write_iter+0xfe/0x1c0
Jun 21 22:25:40 mynas kernel: [79751.480172] ext4_file_write_iter+0xc6/0x400 [ext4]
Jun 21 22:25:40 mynas kernel: [79751.480174] ? page_cache_tree_insert+0xe0/0xe0
Jun 21 22:25:40 mynas kernel: [79751.480178] new_sync_write+0xfb/0x160
Jun 21 22:25:40 mynas kernel: [79751.480181] vfs_write+0xa5/0x1a0
Jun 21 22:25:40 mynas kernel: [79751.480183] ksys_write+0x4f/0xb0
Jun 21 22:25:40 mynas kernel: [79751.480187] do_syscall_64+0x53/0x110
Jun 21 22:25:40 mynas kernel: [79751.480191] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 21 22:25:40 mynas kernel: [79751.480194] RIP: 0033:0x7f9a9678a504
Jun 21 22:25:40 mynas kernel: [79751.480202] Code: Bad RIP value.
Jun 21 22:25:40 mynas kernel: [79751.480203] RSP: 002b:00007ffcbf598d68 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
Jun 21 22:25:40 mynas kernel: [79751.480206] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007f9a9678a504
Jun 21 22:25:40 mynas kernel: [79751.480206] RDX: 0000000000020000 RSI: 0000564ba448a000 RDI: 0000000000000004
Jun 21 22:25:40 mynas kernel: [79751.480207] RBP: 0000564ba448a000 R08: 0000000000020000 R09: 0000000000000000
Jun 21 22:25:40 mynas kernel: [79751.480208] R10: 00007ffcbf598f78 R11: 0000000000000246 R12: 0000564ba448a000
Jun 21 22:25:40 mynas kernel: [79751.480209] R13: 0000000000000004 R14: 0000000000000000 R15: 0000000000020000
Jun 21 22:27:40 mynas kernel: [79872.313627] INFO: task md127_raid5:292 blocked for more than 120 seconds.
Jun 21 22:27:40 mynas kernel: [79872.313683] Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-3
Jun 21 22:27:40 mynas kernel: [79872.313722] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 21 22:27:40 mynas kernel: [79872.313772] md127_raid5 D 0 292 2 0x80000000
Jun 21 22:27:40 mynas kernel: [79872.313776] Call Trace:
Jun 21 22:27:40 mynas kernel: [79872.313788] ? __schedule+0x2a2/0x870
Jun 21 22:27:40 mynas kernel: [79872.313792] schedule+0x28/0x80
Jun 21 22:27:40 mynas kernel: [79872.313803] md_super_wait+0x6e/0xa0 [md_mod]
Jun 21 22:27:40 mynas kernel: [79872.313808] ? finish_wait+0x80/0x80
Jun 21 22:27:40 mynas kernel: [79872.313817] md_update_sb.part.64+0x44c/0x8f0 [md_mod]
Jun 21 22:27:40 mynas kernel: [79872.313826] md_check_recovery+0x148/0x540 [md_mod]
Jun 21 22:27:40 mynas kernel: [79872.313834] raid5d+0x4b/0x5b0 [raid456]
Jun 21 22:27:40 mynas kernel: [79872.313839] ? try_to_del_timer_sync+0x4d/0x80
Jun 21 22:27:40 mynas kernel: [79872.313841] ? del_timer_sync+0x35/0x40
Jun 21 22:27:40 mynas kernel: [79872.313844] ? schedule_timeout+0x173/0x390
Jun 21 22:27:40 mynas kernel: [79872.313849] ? prepare_to_wait_event+0xbb/0x140
Jun 21 22:27:40 mynas kernel: [79872.313855] ? md_rdev_init+0xb0/0xb0 [md_mod]
Jun 21 22:27:40 mynas kernel: [79872.313862] md_thread+0x94/0x150 [md_mod]
Jun 21 22:27:40 mynas kernel: [79872.313864] ? finish_wait+0x80/0x80
Jun 21 22:27:40 mynas kernel: [79872.313867] kthread+0x112/0x130
Jun 21 22:27:40 mynas kernel: [79872.313869] ? kthread_bind+0x30/0x30
Jun 21 22:27:40 mynas kernel: [79872.313871] ret_from_fork+0x22/0x40

```

---

<div class="post-metadata">

**Author:** ![anon44391915](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/958977/32.png) [@anon44391915](https://www.debian-fr.org/u/anon44391915)\
**Post date:** [Juin 23, 2019, 12:48 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/2 "2019-06-23T00:48:41Z")

</div>

Bonjour **[AQkinkin](https://www.debian-fr.org/u/AQkinkin)**

> [@AQkinkin](#):
>
> j’utilise des partions ext2.

…des partitions formatées en ext2 ?  
ou plutôt le volume RAID formaté en ext2 pour être précis ?

Je me demande bien pourquoi ? Et si ce n’est pas l’origine de tes soucis…  
Il n’y a aucun problème à utiliser ext4 de nos jours ; c’est ce qui se fait de plus commun.

`hung_task_timeout_secs` est l’indicateur à creuser apparemment.

Sous réserve, je lis que la mémoire vive RAM est concernée :  
« saturation à 40% de la mémoire disponible pour la mise en cache du système de fichiers »

Mais vraiment, c’est pas top ext2 amha.

```plaintext
fdisk -l
cat /proc/mdstat
df -h
free -ht

```

Pour nous informer.

---

<div class="post-metadata">

**Author:** ![AQkinkin](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/e79b87/32.png) [@AQkinkin](https://www.debian-fr.org/u/AQkinkin)\
**Post date:** [Juin 23, 2019, 9:20 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/3 "2019-06-23T09:20:56Z")

</div>

```nohighlight
root@mynas:/var/log# fdisk -l
Disque /dev/sda : 465,8 GiB, 500107862016 octets, 976773168 secteurs
Modèle de disque : HGST HTS725050A7
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0xd1232e88

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sda1 2048 976773167 976771120 465,8G fd RAID Linux autodétecté

Disque /dev/sdb : 1,8 TiB, 2000398934016 octets, 3907029168 secteurs
Modèle de disque : ST2000DM006-2DM1
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x32e561a6

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sdb1 2048 3907029167 3907027120 1,8T fd RAID Linux autodétecté

Disque /dev/md0 : 3,7 TiB, 4000527155200 octets, 7813529600 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 524288 octets / 1048576 octets
Type d'étiquette de disque : gpt
Identifiant de disque : F7993B2E-D03E-4AC5-B064-B65C710826F8

Périphérique Début Fin Secteurs Taille Type
/dev/md0p1 2048 7813529566 7813527519 3,7T Système de fichiers Linux

Disque /dev/sdc : 1,8 TiB, 2000398934016 octets, 3907029168 secteurs
Modèle de disque : ST2000DM008-2FR1
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0xae5aa6e3

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sdc1 2048 3907029167 3907027120 1,8T fd RAID Linux autodétecté

Disque /dev/sdd : 465,8 GiB, 500107862016 octets, 976773168 secteurs
Modèle de disque : HGST HTS725050A7
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0xd1232e88

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sdd1 2048 976773167 976771120 465,8G fd RAID Linux autodétecté

Disque /dev/md127 : 931,3 GiB, 999943045120 octets, 1953013760 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 524288 octets / 1048576 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x6a8cf692

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/md127p1 2048 1953013759 1953011712 931,3G 83 Linux

Disque /dev/sde : 1,8 TiB, 2000398934016 octets, 3907029168 secteurs
Modèle de disque : ST2000DM006-2DM1
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0xb9e3dad4

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sde1 2048 3907029167 3907027120 1,8T fd RAID Linux autodétecté

Disque /dev/sdf : 465,8 GiB, 500107862016 octets, 976773168 secteurs
Modèle de disque : WDC WD5000LPVX-2
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x0951a00b

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sdf1 2048 976773167 976771120 465,8G fd RAID Linux autodétecté

Disque /dev/sdg : 233,8 GiB, 251000193024 octets, 490234752 secteurs
Modèle de disque : Maxtor 6V250F0
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x399145fd

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sdg1 * 2048 1054719 1052672 514M ef EFI (FAT-12/16/32)
/dev/sdg2 7753728 164003839 156250112 74,5G 83 Linux
/dev/sdg3 164003840 490233855 326230016 155,6G 83 Linux
/dev/sdg4 1054720 7753727 6699008 3,2G 82 partition d'échange Linux / Solaris

Les entrées de la table de partitions ne sont pas dans l'ordre du disque.

Disque /dev/sdh : 465,8 GiB, 500107862016 octets, 976773168 secteurs
Modèle de disque : WDC WD5000AZRX-0
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0xbe8444e6

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sdh1 2048 976771071 976769024 465,8G 83 Linux

Disque /dev/sdi : 465,8 GiB, 500107862016 octets, 976773168 secteurs
Modèle de disque : WDC WD5000AADS-6
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0xf5dde74e

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sdi1 2048 976773167 976771120 465,8G 83 Linux

```

```nohighlight
root@mynas:/var/log# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md127 : active raid5 sda1[0] sdf1[3] sdd1[1]
      976506880 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
      bitmap: 0/4 pages [0KB], 65536KB chunk

md0 : active raid5 sde1[2] sdc1[3] sdb1[1]
      3906764800 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
      bitmap: 0/15 pages [0KB], 65536KB chunk

unused devices: <none>

```

```nohighlight
root@mynas:/var/log# df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev 3,4G 0 3,4G 0% /dev
tmpfs 697M 9,0M 688M 2% /run
/dev/sdg2 74G 2,0G 68G 3% /
tmpfs 3,4G 0 3,4G 0% /dev/shm
tmpfs 5,0M 0 5,0M 0% /run/lock
tmpfs 3,4G 0 3,4G 0% /sys/fs/cgroup
/dev/sdg1 513M 9,9M 504M 2% /boot/efi
/dev/sdg3 154G 2,1G 144G 2% /mnt/musics
/dev/md127p1 917G 34G 837G 4% /mnt/medias
tmpfs 697M 0 697M 0% /run/user/0
/dev/md0p1 3,6T 797G 2,7T 23% /mnt/donnees
tmpfs 697M 0 697M 0% /run/user/1000

```

````nohighlight
root@mynas:/var/log# free -th
              total used free shared buff/cache available
Mem: 6,8Gi 284Mi 6,3Gi 9,0Mi 179Mi 6,3Gi
Swap: 3,2Gi 0B 3,2Gi
Total: 9Gi 284Mi 9,5Gi
```text
````

---

<div class="post-metadata">

**Author:** ![anon44391915](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/958977/32.png) [@anon44391915](https://www.debian-fr.org/u/anon44391915)\
**Post date:** [Juin 23, 2019, 9:43 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/4 "2019-06-23T09:43:30Z")

</div>

Merci 🙂

Il y a une chose qui me surprend ;

C’est que les volumes RAID5 /dev/md127 et /dev/md0 soient partitionnés ;  
avec respectivement /dev/md127p1 et /dev/md0p1 qui occupent en l’occurrence  
tout l’espace des volumes.

Pour chaque RAID que j’ai fait, j’ai formaté le volume RAID tel quel :

```nohighlight
# exemple
# sudo mkfs.ext4 /dev/md0

```

Tout autant en utilisant LVM et un volume physique RAID.

```nohighlight
# exemple
# sudo vgcreate VolumeGroupName /dev/md0

```

---

<div class="post-metadata">

**Author:** ![AQkinkin](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/e79b87/32.png) [@AQkinkin](https://www.debian-fr.org/u/AQkinkin)\
**Post date:** [Juin 23, 2019, 10:46 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/5 "2019-06-23T10:46:41Z")

</div>

Je ne savait pas que l’on pouvait faire ce genre de chose.  
c’est un particularité de ext4 ?

Mais le problème n’est pas la.  
Le problème, c’est que, lorsque le processeur est fortement sollicité, des processus sont trop lent et cela plante la synchro entre les processus.

Hypothèse :  
Il me semble qu’au lancement du Ryzen, beaucoup d’article parlé de ce problème. Il fait donc modifier les OS afin que les “core virtuel” ne soit pas vu comme des “core physique”.  
C’est-ce que c’est la bonne piste ?

Je suis désolé mais après 17 ans de fidélité, je viens d’installer xubuntu sur une machine virtuel.

---

<div class="post-metadata">

**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\
**Post date:** [Juin 23, 2019, 11:06 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/6 "2019-06-23T11:06:48Z")

</div>

> [@AQkinkin](#):
>
> Dans le message d’erreur, ci-desous, je remarque que cela parle de ext4 mais j’utilise des partions ext2.

Depuis un bout de temps déjà (ça doit remonter à Jessie ou Wheezy), le pilote ext4 du de Linux gère toutes les versions d’ext\*, et les pilotes ext2 et ext3 ont été retirés.

As-tu une raison particulière d’utiliser ext2 au lieu d’ext4 ?

> [@AQkinkin](#):
>
> Je ne savait pas que l’on pouvait faire ce genre de chose.  
> c’est un particularité de ext4 ?

Tu parles de formater directement un ensemble RAID sans le partitionner ?  
Ça n’a rien à voir avec ext4 (qui se fiche bien d’être dans un périphérique non partitionné ou dans une partition). On a toujours fait comme ça, la possibilité de partitionner un ensemble RAID logiciel n’a été introduite que tardivement. Quand on avait besoin de diviser l’espace d’un ensemble RAID, on utilisait LVM et on continue à le faire car c’est beaucoup plus flexible que des partitions.

Il n’y a pas d’erreurs disques avant les messages du noyau que tu cites ?

---

<div class="post-metadata">

**Author:** ![AQkinkin](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/e79b87/32.png) [@AQkinkin](https://www.debian-fr.org/u/AQkinkin)\
**Post date:** [Juin 23, 2019, 11:18 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/7 "2019-06-23T11:18:46Z")

</div>

Non, pas d’erreur disque.

Mais des erreurs j’ai ça dans le log kernel :

```nohighlight
[drm] amdgpu kernel modesetting enabled.
[drm:amdgpu_pci_probe [amdgpu]] *ERROR* amdgpu requires firmware installed

```

les message s’affiche dans entre les ligne HD-Audio:

```nohighlight
Jun 22 10:55:03 mynas kernel: [57.789475] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:38:00.1/sound/card0/input8
Jun 22 10:55:03 mynas kernel: [57.789571] input: HD-Audio Generic HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:08.1/0000:38:00.1/sound/card0/input9
Jun 22 10:55:03 mynas kernel: [57.790536] input: HD-Audio Generic HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:08.1/0000:38:00.1/sound/card0/input10
Jun 22 10:55:03 mynas kernel: [57.792222] input: HD-Audio Generic HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:08.1/0000:38:00.1/sound/card0/input11
Jun 22 10:55:03 mynas kernel: [57.978536] [drm] amdgpu kernel modesetting enabled.
Jun 22 10:55:03 mynas kernel: [57.978707] [drm:amdgpu_pci_probe [amdgpu]] *ERROR* amdgpu requires firmware installed
Jun 22 10:55:03 mynas kernel: [57.978763] See https://wiki.debian.org/Firmware for information about missing firmware
Jun 22 10:55:03 mynas kernel: [58.040820] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC892: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
Jun 22 10:55:03 mynas kernel: [58.040822] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Jun 22 10:55:03 mynas kernel: [58.040824] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Jun 22 10:55:03 mynas kernel: [58.040825] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0
Jun 22 10:55:03 mynas kernel: [58.040826] snd_hda_codec_realtek hdaudioC1D0: inputs:
Jun 22 10:55:03 mynas kernel: [58.040828] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19
Jun 22 10:55:03 mynas kernel: [58.040829] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18
Jun 22 10:55:03 mynas kernel: [58.040830] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a
Jun 22 10:55:03 mynas kernel: [58.048927] MCE: In-kernel MCE decoding enabled.
Jun 22 10:55:03 mynas kernel: [58.065030] input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:38:00.6/sound/card1/input12

```

---

<div class="post-metadata">

**Author:** ![AQkinkin](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/e79b87/32.png) [@AQkinkin](https://www.debian-fr.org/u/AQkinkin)\
**Post date:** [Juin 23, 2019, 11:27 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/8 "2019-06-23T11:27:13Z")

</div>

Pour répondre à question pourquoi ext2 :

Parce que la journalisation, je ne l’utilise pas.  
Et que mon disque le plus gros est inférieur de 4T donc pourquoi utiliser un systèmes de fichiers qui gère des fichiers de 4T ?

Mais, s’il vous plaie, ce n’est pas de débat.  
Si vous voulez me convaincre que l’ext4 est mieux que l’ext2. Nous pouvons ouvrir un autre sujet.

---

<div class="post-metadata">

**Author:** ![anon44391915](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/958977/32.png) [@anon44391915](https://www.debian-fr.org/u/anon44391915)\
**Post date:** [Juin 23, 2019, 11:33 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/9 "2019-06-23T11:33:55Z")

</div>

as you seem to me to understand English.  
I suggest you read this article

[https://www.blackmoreops.com/2014/09/22/linux-kernel-panic-issue-fix-hung\_task\_timeout\_secs-blocked-120-seconds-problem/](https://www.blackmoreops.com/2014/09/22/linux-kernel-panic-issue-fix-hung_task_timeout_secs-blocked-120-seconds-problem/)

I couldn’t fully understand it.  
I hope it will be useful.

---

<div class="post-metadata">

**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\
**Post date:** [Juin 23, 2019, 2:21 UTC](https://www.debian-fr.org/t/plantage-machine-sur-mv-sur-un-gros-repertoire-debian-10/79503/10 "2019-06-23T14:21:14Z")

</div>

> [@AQkinkin](#):
>
> Pour répondre à question pourquoi ext2 :  
> Parce que la journalisation, je ne l’utilise pas.  
> Et que mon disque le plus gros est inférieur de 4T donc pourquoi utiliser un systèmes de fichiers qui gère des fichiers de 4T ?

Ext4 apporte d’autres améliorations que la journalisation et l’augmentation de la taille maximum des fichiers et systèmes de fichiers. Si tu ne veux vraiment pas de la journalisation, il est possible de la désactiver. Je n’entre pas dans les détails, ce n’est pas le sujet.

Un mot sur le message d’erreur de firmware pour amdgpu : il concerne le pilote pour le GPU AMD/Radeon qui a besoin du paquet firmware-amd-graphics pour gérer optimalement ton GPU. A priori rien à voir avec le problème disque.