Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I ran a script to snapshot all logical volumes from KVM guests and backup. But /var/log/messages reported these errors:

Jun 02 09:57:08 server lvm[24245]: Monitoring snapshot vg2-guest741_snapshot_vol
Jun 02 09:57:12 server kernel: EXT4-fs warning (device loop0): ext4_orphan_get: bad orphan inode 28540!  e2fsck was run?
Jun 02 09:57:12 server kernel: ext4_test_bit(bit=3771, block=148) = 0
Jun 02 09:57:12 server kernel: inode=(null)
Jun 02 09:57:12 server kernel: EXT4-fs (loop0): 1 orphan inode deleted
Jun 02 09:57:12 server kernel: EXT4-fs (loop0): recovery complete
Jun 02 09:57:12 server kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: 
Jun 02 09:57:56 server lvm[24245]: No longer monitoring snapshot vg2-guest741_snapshot_vol
Jun 02 09:58:08 server lvm[24245]: Monitoring snapshot vg2-guest159_snapshot_vol
Jun 02 09:58:12 server kernel: EXT4-fs warning (device loop0): ext4_orphan_get: bad orphan inode 93114!  e2fsck was run?
Jun 02 09:58:12 server kernel: ext4_test_bit(bit=1113, block=117) = 0
Jun 02 09:58:12 server kernel: inode=(null)
Jun 02 09:58:12 server kernel: EXT4-fs (loop0): recovery complete
Jun 02 09:58:12 server kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: 
Jun 02 09:58:56 server lvm[24245]: No longer monitoring snapshot vg2-guest159_snapshot_vol
Jun 02 09:59:08 server lvm[24245]: Monitoring snapshot vg2-guest5_snapshot_vol
Jun 02 09:59:12 server kernel: EXT4-fs (loop0): recovery complete
Jun 02 09:59:12 server kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: 
Jun 02 09:59:50 server lvm[24245]: No longer monitoring snapshot vg2-guest5_snapshot_vol
Jun 02 10:00:03 server lvm[24245]: Monitoring snapshot vg2-guest12_snapshot_vol
Jun 02 10:00:06 server kernel: EXT4-fs warning (device loop0): ext4_orphan_get: bad orphan inode 21310!  e2fsck was run?
Jun 02 10:00:06 server kernel: ext4_test_bit(bit=5605, block=147) = 0
Jun 02 10:00:06 server kernel: inode=(null)
Jun 02 10:00:06 server kernel: EXT4-fs (loop0): recovery complete
Jun 02 10:00:06 server kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: 
Jun 02 10:00:51 server lvm[24245]: No longer monitoring snapshot vg2-guest12_snapshot_vol
Jun 02 10:01:03 server lvm[24245]: Monitoring snapshot vg2-guest333_snapshot_vol
Jun 02 10:01:07 server kernel: EXT4-fs warning (device loop0): ext4_orphan_get: bad orphan inode 93118!  e2fsck was run?
Jun 02 10:01:07 server kernel: ext4_test_bit(bit=8157, block=118) = 0
Jun 02 10:01:07 server kernel: inode=(null)
Jun 02 10:01:07 server kernel: EXT4-fs (loop0): recovery complete
Jun 02 10:01:07 server kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: 
Jun 02 10:01:55 server lvm[24245]: No longer monitoring snapshot vg2-guest333_snapshot_vol

I tried running guestfish and fsck on one of the guests, the status code returned '0x4'. Is there a way to fix these bad inodes?

share|improve this question

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.