Article ID: 118130, created on Oct 23, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0

Symptoms

A hardware node crashed.

The following messages can be found in /var/log/messages log:

    <2>[7643798.068322] EXT4-fs error (device ploop31376p1): htree_dirblock_to_tree: bad entry in directory #2: inode out of bounds - block=8865offset=148(148), inode=1048577, rec_len=16, name_len=5
    <2>[7643798.456609] EXT4-fs error (device ploop31376p1): htree_dirblock_to_tree: bad entry in directory #2: inode out of bounds - block=8865offset=148(148), inode=1048577, rec_len=16, name_len=5
    <2>[7643798.469990] EXT4-fs error (device ploop31376p1): htree_dirblock_to_tree: bad entry in directory #2: inode out of bounds - block=8865offset=148(148), inode=1048577, rec_len=16, name_len=5
    <2>[7643798.935819] EXT4-fs error (device ploop31376p1): htree_dirblock_to_tree: bad entry in directory #2: inode out of bounds - block=8865offset=148(148), inode=1048577, rec_len=16, name_len=5
    <2>[7643798.943359] EXT4-fs error (device ploop31376p1): htree_dirblock_to_tree: bad entry in directory #2: inode out of bounds - block=8865offset=148(148), inode=1048577, rec_len=16, name_len=5
    <3>[7643820.372226] Buffer I/O error on device ploop31779p1, logical block 0
    <4>[7643820.372316] lost page write due to I/O error on ploop31779p1
    <2>[7643855.293692] EXT4-fs error (device ploop31376p1): htree_dirblock_to_tree: bad entry in directory #2: inode out of bounds - block=8865offset=148(148), inode=1048577, rec_len=16, name_len=5
    <4>[7643855.293974] ------------[ cut here ]------------
    <2>[7643855.294056] kernel BUG at fs/buffer.c:3112!
    <4>[7643855.294137] invalid opcode: 0000 [#1] SMP
    ...
    <4>[7643855.298502] Call Trace:
    <4>[7643855.298583]  [<ffffffff811de233>] __sync_dirty_buffer+0x53/0xf0
    <4>[7643855.298668]  [<ffffffff811de2e3>] sync_dirty_buffer+0x13/0x20
    <4>[7643855.298767]  [<ffffffffa009d278>] ext4_commit_super+0x158/0x1e0 [ext4]
    <4>[7643855.298855]  [<ffffffffa009d9d2>] ext4_handle_error+0x72/0xd0 [ext4]
    <4>[7643855.298944]  [<ffffffffa009ddc2>] __ext4_error+0x82/0x90 [ext4]
    <4>[7643855.299028]  [<ffffffff8118e98f>] ? __kmalloc+0x22f/0x270
    <4>[7643855.299113]  [<ffffffffa007e27d>] ext4_check_dir_entry+0xbd/0x100 [ext4]
    <4>[7643855.299202]  [<ffffffffa008e240>] htree_dirblock_to_tree+0xc0/0x190 [ext4]
    <4>[7643855.299291]  [<ffffffffa008ec58>] ext4_htree_fill_tree+0xa8/0x260 [ext4]
    <4>[7643855.299379]  [<ffffffff81165ad6>] ? handle_mm_fault+0x236/0x320
    <4>[7643855.301106]  [<ffffffff811a23c4>] ? nameidata_to_filp+0x54/0x70
    <4>[7643855.301193]  [<ffffffffa007e3ee>] ext4_readdir+0x12e/0x780 [ext4]
    <4>[7643855.301277]  [<ffffffff811bad50>] ? filldir+0x0/0xe0
    <4>[7643855.301360]  [<ffffffff811ab0d4>] ? cp_new_stat+0xe4/0x100
    <4>[7643855.301445]  [<ffffffff811bafb8>] vfs_readdir+0xa8/0xd0
    <4>[7643855.301525]  [<ffffffff811bad50>] ? filldir+0x0/0xe0
    <4>[7643855.301605]  [<ffffffff811bb149>] sys_getdents+0x89/0xf0
    <4>[7643855.301693]  [<ffffffff8100b102>] system_call_fastpath+0x16/0x1b

Cause

The problem is recognized as a product bug PSBM-23065.

The crash occurs during the operation of cloning a ploop-based container.

Resolution

The fix will be included in one of the future releases of Parallels Cloud Server, however additional information is needed from a complete kernel dump. Should you have configured crashdumps and have the dump file, please provide the dump to Parallels Support.

It is highly advised to perform a file system check on the container that was being cloned before the crash.

Search Words

bad entry in directory

kernel BUG at fs/buffer.c:3112!

htree_dirblock_to_tree

inode out of bounds

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF