Why server went to unresponsive state showing filesystem in frozen state ?

Solution Unverified - Updated -

Issue

  • Server went to unresponsive state showing following traces :
PID: 12377  TASK: ffff8109b616d0c0  CPU: 16  COMMAND: "logmon"
 #0 [ffff8111d4c57c18] schedule at ffffffff80062fa0
 #1 [ffff8111d4c57cf0] __generic_file_aio_write_nolock at ffffffff800164fc
 #2 [ffff8111d4c57d90] generic_file_aio_write at ffffffff80021e10
 #3 [ffff8111d4c57de0] ext3_file_write at ffffffff8804c372 [ext3]
 #4 [ffff8111d4c57e00] do_sync_write at ffffffff800183d1
 #5 [ffff8111d4c57f10] vfs_write at ffffffff80016b4e
 #6 [ffff8111d4c57f40] sys_write at ffffffff80017417
 #7 [ffff8111d4c57f80] system_call at ffffffff8005d116
    RIP: 0000003889cc72db  RSP: 00007fffaef0d758  RFLAGS: 00010202
    RAX: 0000000000000001  RBX: ffffffff8005d116  RCX: ffffffffffffffe0
    RDX: 000000000000004d  RSI: 00002ac193935000  RDI: 0000000000000005
    RBP: 000000000000004d   R8: 00002ac19394c040   R9: 00000000ffffffff
    R10: 20676e696b636568  R11: 0000000000000206  R12: 00000000186f5fb0
    R13: 00002ac193935000  R14: 000000000000004d  R15: 00000001006a0960
    ORIG_RAX: 0000000000000001  CS: 0033  SS: 002b

Environment

  • Red Hat Enterprise Linux 5.9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.