Re: generic/269 hangs on lastest upstream kernel

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]



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.

> 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!

								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
> 
> 
-- 
Jan Kara <jack@xxxxxxxx>
SUSE Labs, CR



[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux