not sure where to post bugs and not even sure the title is correct since I have no clue what's going on.
I'm using Mint 16 with the latests stable updates. From there, I checked another partition (the boot partition of a LMDE deployment).
Both Mint 16 and LMDE are on the same LVM2. LMDE uses distro/lmde_boot, distro/lmde_root, and distro/lmde_home, all being ext4 filesystems.
What I did:
Code: Select all
fsck.ext4 -Dft -C 0 /dev/distro/lmde_boot
mount /dev/distro/lmde_boot /mnt
e4defrag -c /dev/distro/lmde_boot
e4defrag /dev/distro/lmde_bootI compared the files with a backup just to realize the kernel files have been altered.
Actually, the original LMDE's kernel, initrd, and System.map have been modified. For my own kernel, only its initramfs and System.map have been modified (the kernel itself is still the same).
So out of 6 files, 5 have been modified to death. Unfortunately, I can't check the other files on that lmde_boot partition. Its grub.cfg seems intact.
After that, I tried to fsck that partition again but everything looks normal.
I have no idea what broke those files. Is it e4defrag or fsck.ext4? Or maybe something else happened?
LMDE booted perfectly right before that bug occurred. I was using LMDE when I rebooted to Mint in order to check the filesystems. Then I immediately rebooted to LMDE. So basically, appart from issuing those e4defrag and fsck commands, I haven't done anything. I made sure I never ran fsck on a mounted filesystem.
As far as I remember, e4defrag shown fragmentation on the kernel files. I can't remember if my own kernel (the one that has not been altered) was fragmented. My guess is that the fragmented files got corrupted by e4defrag but I can't verify it.
I'm not worried about those corrupted files, I do have a backup. I'm a bit more worried about the other partitions (I hope lmde_root didn't suffer from the same issue).
Should I fill in a bug report and how to do it?
...