EXT3-fs error after LUKS encryption set up
Hi all,
I had a correctly working system for somewhat more than one year, with 4
disks, 5 partitions in mdadm RAID-1 (sda+sdb: /boot, /, swap, /home;
sdc+sdd: /var).
Three days ago I have updated to LUKS encrypted partitions, by marking as
failing the sdb partitions of RAID arrays, creating the new partition
layout on sdb (just the sizes were what I have modified, no hw has been
changed), creating new RAID arrays with missing devices (for later addition
of the remaining partitions), creating the LUKS encryption over md's,
creating the filesystems, rsyncing /boot, / and /home.
After I have booted everything seemed okay, but some hours later I have got
strange EXT3-fs errors (like below), so I thought I made something wrong. I
have rebooted with the old root partition in single mode, fsck'd the new
root and it has found a lot of errors - I have repaired them. Next time the
boot from the new root partition was impossible. At this time I have
recreated the EXT3 fs (with default settings), and rsynced the contents
again (with -xav parameters), then unmounted, fsck'd, everything was okay.
I have rebooted, and the system seemed okay for a few hours, when I got the
EXT3-fs error messages again (see below). I have no other error messages,
so I think this is not hardware-related nor mdadm-related and even not
LUKS-related.
I am completely puzzled as I can't find any reason why is it not working
now.
I have used kernel 2.6.18-6 for a while, then 2.6.28.3, and after the issue
came for the first time, I have updated to 2.6.29.1 (I thought this bug(?)
may be kernel/module related).
I have pasted some logs and configs that may be needed.
Had anybody the same problem? Has any body any idea about this? I would be
very happy if someone could help me...
Thank you for your help in advance,
Gabor Heja
--- kern.log ---
Apr 18 00:11:45 zaphod kernel: journal_bmap: journal block not found at
offset 30732 on dm-0
Apr 18 00:11:45 zaphod kernel: Aborting journal on device dm-0.
Apr 18 00:11:46 zaphod kernel: ext3_abort called.
Apr 18 00:11:46 zaphod kernel: EXT3-fs error (device dm-0):
ext3_journal_start_sb: Detected aborted journal
Apr 18 00:11:46 zaphod kernel: Remounting filesystem read-only
Apr 18 06:25:41 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #16323: rec_len %% 4 != 0 -
offset=0, inode=448592521, rec_len=57635, name_len=80
Apr 18 06:25:41 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207709: rec_len %% 4 != 0
- offset=0, inode=498065228, rec_len=27001, name_len=188
Apr 18 06:25:41 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #16387: directory entry
across blocks - offset=0, inode=1580238972, rec_len=30636, name_len=27
Apr 18 06:25:41 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207681: rec_len %% 4 != 0
- offset=0, inode=4285218298, rec_len=42839, name_len=160
Apr 18 06:25:41 zaphod kernel: init_special_inode: bogus i_mode (116400)
[...]
Apr 18 06:25:43 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #16321: rec_len %% 4 != 0 -
offset=0, inode=2154176260, rec_len=31926, name_len=60
Apr 18 06:25:43 zaphod kernel: init_special_inode: bogus i_mode (76400)
Apr 18 06:25:43 zaphod kernel: init_special_inode: bogus i_mode (136731)
Apr 18 06:25:43 zaphod kernel: init_special_inode: bogus i_mode (37004)
Apr 18 06:25:43 zaphod kernel: init_special_inode: bogus i_mode (54713)
[...]
Apr 18 06:25:44 zaphod kernel: EXT3-fs warning (device dm-0): dx_probe:
Unrecognised inode hash code 236
Apr 18 06:25:44 zaphod kernel: EXT3-fs warning (device dm-0): dx_probe:
Corrupt dir inode 1207682, running e2fsck is recommended.
Apr 18 06:25:44 zaphod kernel: EXT3-fs error (device dm-0): ext3_readdir:
bad entry in directory #1207682: rec_len %% 4 != 0 - offset=0,
inode=306242936, rec_len=26027, name_len=215
Apr 18 06:25:44 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #16327: rec_len %% 4 != 0 -
offset=0, inode=895120187, rec_len=14550, name_len=99
Apr 18 06:25:44 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #16325: rec_len %% 4 != 0 -
offset=4096, inode=1701286484, rec_len=29967, name_len=221
Apr 18 06:25:44 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #16325: rec_len %% 4 != 0 -
offset=8192, inode=3317017796, rec_len=7450, name_len=2
Apr 18 06:25:44 zaphod kernel: init_special_inode: bogus i_mode (3400)
Apr 18 06:25:44 zaphod kernel: init_special_inode: bogus i_mode (157263)
Apr 18 06:25:44 zaphod kernel: init_special_inode: bogus i_mode (165677)
[...]
Apr 18 06:25:44 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207684: rec_len %% 4 != 0
- offset=0, inode=2000554412, rec_len=35286, name_len=116
Apr 18 06:25:45 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207705: rec_len %% 4 != 0
- offset=0, inode=1843201093, rec_len=62154, name_len=34
Apr 18 06:25:45 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207704: rec_len %% 4 != 0
- offset=0, inode=3976465125, rec_len=9718, name_len=176
Apr 18 06:25:45 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207700: rec_len %% 4 != 0
- offset=0, inode=3406998369, rec_len=54651, name_len=252
Apr 18 06:25:45 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207701: directory entry
across blocks - offset=0, inode=119066520, rec_len=42016, name_len=232
Apr 18 06:25:45 zaphod kernel: init_special_inode: bogus i_mode (164)
Apr 18 06:25:45 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207695: directory entry
across blocks - offset=0, inode=2569094070, rec_len=53236, name_len=41
Apr 18 06:25:45 zaphod kernel: EXT3-fs error (device dm-0):
htree_dirblock_to_tree: bad entry in directory #1207687: rec_len %% 4 != 0
- offset=0, inode=1571285659, rec_len=33829, name_len=18
--- /etc/fstab (just the important lines) ---
proc /proc proc defaults 0 0
/dev/mapper/md5_crypt / ext3 defaults,errors=remount-ro 0 1
/dev/md4 /boot ext3 defaults,rw 0 2
/dev/md3 /var ext3 defaults 0 2
/dev/mapper/md6_crypt none swap sw 0 0
--- /proc/mdstat ---
Personalities : [raid1]
md3 : active raid1 sdd1[0] sdc1[1]
488383936 blocks [2/2] [UU]
md6 : active raid1 sdb3[0] sda3[1]
3911744 blocks [2/2] [UU]
md7 : active raid1 sdb4[0] sda4[1]
142094848 blocks [2/2] [UU]
md5 : active raid1 sdb2[0] sda2[1]
9775488 blocks [2/2] [UU]
md4 : active raid1 sdb1[0] sda1[1]
505920 blocks [2/2] [UU]
unused devices: <none>
--- fdisk -l (md's ignored) ---
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 63 506016 fd Linux raid
autodetect
/dev/sda2 64 1280 9775552+ fd Linux raid
autodetect
/dev/sda3 1281 1767 3911827+ fd Linux raid
autodetect
/dev/sda4 1768 19457 142094925 fd Linux raid
autodetect
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 63 506016 fd Linux raid
autodetect
/dev/sdb2 64 1280 9775552+ fd Linux raid
autodetect
/dev/sdb3 1281 1767 3911827+ fd Linux raid
autodetect
/dev/sdb4 1768 19457 142094925 fd Linux raid
autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 60801 488384001 fd Linux raid
autodetect
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 1 60801 488384001 fd Linux raid
autodetect
Reply to: