![]() ![]() Inode 2228934 was part of the orphaned inode list. Inode 2228932 was part of the orphaned inode list. Inode 2228902 was part of the orphaned inode list. Inode 268043 was part of the orphaned inode list. Inode 267835 was part of the orphaned inode list. Inode 267749 was part of the orphaned inode list. Inode 267659 was part of the orphaned inode list. Inode 267539 was part of the orphaned inode list. Inode 266732 was part of the orphaned inode list. Inode 266589 was part of the orphaned inode list. Inodes that were part of a corrupted orphan linked list found. Pass 1: Checking inodes, blocks, and sizes (Repair filesystem) 1 # fsck.ext4 /dev/mapper/V^GolGroup-lv^G_root ![]() (Repair filesystem) 1 # fsck^G.e^Gxt^G4^G *** Dropping you to a shell the system will rebootīash: cannot set terminal process group (-1): Inappropriate ioctl for device *** An error occurred during the file system check. dev/mapper/VolGroup-lv_root: UNEXPECTED INCONSISTENCY RUN fsck MANUALLY. dev/mapper/VolGroup-lv_root: Inodes that were part of a corrupted orphan linked list found. dev/mapper/VolGroup-lv_root contains a file system with errors, check forced. fsck.ext4 -a /dev/mapper/VolGroup-lv_root Then I rebooted the test box, this time it dropped me in a repair sulogin: ![]() I'm using ext4 as my rhel6 test box, but I'm seeing a error while I'm testing xfs via loop device:įirst I got a error in the running rhel6 kernel:ĮXT4-fs error (device dm-0) in ext4_reserve_inode_write: Journal has abortedĮXT4-fs error (device dm-0): ext4_journal_start_sb: Detected aborted journalĮXT4-fs (dm-0): Remounting filesystem read-onlyĮXT4-fs error (device dm-0): ext4_find_entry: reading directory #264071 offset 0ĮXT4-fs error (device dm-0): ext4_find_entry: reading directory #1180633 offset 0 Copying from email for tracking this problem: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |