on 2020/02/12 18:54, Jan Kara wrote:
Hello!
On Tue 11-02-20 16:14:35, Yang Xu wrote:
Since xfstests support rename2, this case(generic/269) reports filesystem
inconsistent problem with ext4 on my system(4.18.0-32.el8.x86_64).
I don't remember seeing this in my testing... It might be specific to that
RHEL kernel.
Agree.
When I test generic/269(ext4) on 5.6.0-rc1 kernel, it hangs.
----------------------------------------------
dmesg as below:
76.506753] run fstests generic/269 at 2020-02-11 05:53:44
[ 76.955667] EXT4-fs (sdc): mounted filesystem with ordered data mode.
Opts: acl, user_xattr
[ 100.912511] device virbr0-nic left promiscuous mode
[ 100.912520] virbr0: port 1(virbr0-nic) entered disabled state
[ 246.801561] INFO: task dd:17284 blocked for more than 122 seconds.
[ 246.801564] Not tainted 5.6.0-rc1 #41
[ 246.801565] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this mes sage.
[ 246.801566] dd D 0 17284 16931 0x00000080
[ 246.801568] Call Trace:
[ 246.801584] ? __schedule+0x251/0x690
[ 246.801586] schedule+0x40/0xb0
[ 246.801588] wb_wait_for_completion+0x52/0x80
[ 246.801591] ? finish_wait+0x80/0x80
[ 246.801592] __writeback_inodes_sb_nr+0xaa/0xd0
[ 246.801593] try_to_writeback_inodes_sb+0x3c/0x50
Interesting. Does the hang resolve eventually or the machine is hung
permanently? If the hang is permanent, can you do:
echo w >/proc/sysrq-trigger
and send us the stacktraces from dmesg? Thanks!
Yes. the hang is permanent, log as below:
[ 959.451423] fsstress D 0 20094 20033 0x00000080
[ 959.451424] Call Trace:
[ 959.451425] ? __schedule+0x251/0x690
[ 959.451426] schedule+0x40/0xb0
[ 959.451428] schedule_preempt_disabled+0xa/0x10
[ 959.451429] __mutex_lock.isra.8+0x2b5/0x4a0
[ 959.451430] ? __check_object_size+0x162/0x173
[ 959.451431] lock_rename+0x28/0xb0
[ 959.451433] do_renameat2+0x2a9/0x530
[ 959.451434] __x64_sys_renameat2+0x20/0x30
[ 959.451436] do_syscall_64+0x55/0x1b0
[ 959.451436] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 959.453023] dd D 0 21645 19793 0x00004080
[ 959.453024] Call Trace:
[ 959.453026] ? __schedule+0x251/0x690
[ 959.453027] ? __wake_up_common_lock+0x87/0xc0
[ 959.453028] schedule+0x40/0xb0
[ 959.453030] jbd2_log_wait_commit+0xac/0x120 [jbd2]
[ 959.453032] ? finish_wait+0x80/0x80
[ 959.453034] jbd2_log_do_checkpoint+0x383/0x3f0 [jbd2]
[ 959.453036] __jbd2_log_wait_for_space+0x66/0x190 [jbd2]
[ 959.453038] add_transaction_credits+0x27d/0x290 [jbd2]
[ 959.453040] ? blk_mq_make_request+0x289/0x5d0
[ 959.453042] start_this_handle+0x10a/0x510 [jbd2]
[ 959.453043] ? _cond_resched+0x15/0x30
[ 959.453045] jbd2__journal_start+0xea/0x1f0 [jbd2]
[ 959.453051] ? ext4_writepages+0x518/0xd90 [ext4]
[ 959.453057] __ext4_journal_start_sb+0x6e/0x130 [ext4]
[ 959.453063] ext4_writepages+0x518/0xd90 [ext4]
[ 959.453065] ? do_writepages+0x41/0xd0
[ 959.453070] ? ext4_mark_inode_dirty+0x1f0/0x1f0 [ext4]
[ 959.453072] do_writepages+0x41/0xd0
[ 959.453073] ? iomap_write_begin+0x4c0/0x4c0
[ 959.453188] ? xfs_iunlock+0xf3/0x100 [xfs]
[ 959.453189] __filemap_fdatawrite_range+0xcb/0x100
[ 959.453191] ? __raw_spin_unlock+0x5/0x10
[ 959.453198] ext4_release_file+0x6c/0xa0 [ext4]
[ 959.453200] __fput+0xbe/0x250
[ 959.453201] task_work_run+0x84/0xa0
[ 959.453203] exit_to_usermode_loop+0xc8/0xd0
[ 959.453204] do_syscall_64+0x1a5/0x1b0
[ 959.453205] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 959.453206] RIP: 0033:0x7f368a22f1a8
Best Regards
Yang Xu
Honza
[ 246.801609] ext4_nonda_switch+0x7b/0x80 [ext4]
[ 246.801618] ext4_da_write_begin+0x6f/0x480 [ext4]
[ 246.801621] generic_perform_write+0xf4/0x1b0
[ 246.801628] ext4_buffered_write_iter+0x8d/0x120 [ext4]
[ 246.801634] ext4_file_write_iter+0x6e/0x700 [ext4]
[ 246.801636] new_sync_write+0x12d/0x1d0
[ 246.801638] vfs_write+0xa5/0x1a0
[ 246.801640] ksys_write+0x59/0xd0
[ 246.801643] do_syscall_64+0x55/0x1b0
[ 246.801645] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 246.801646] RIP: 0033:0x7fe9ec947b28
[ 246.801650] Code: Bad RIP value.
----------------------------------------------
Does anyone also meet this problem?
Best Regards
Yang Xu
