You are right. I'm using e2compression latest patch (for 2.1.130
I think it was 0.4.16). Howevere home was not compressed :((
(when it started reporting file system contains errors check forced
on every boot I have decided to do mke2fs on it again). I have
closley examined my syslog file and also posted what was problem
that might caused mess (either was problem with ide cable or for some
other reason disk did LBA/CSH translation). I also don't get why
does e2compression causes problems that e2fsck can't repair :((
>It probably would have been better to use an alternative superblock
>(e2fsck -b 8193), but depending on how badly your filesystem was
>corrupted, it might not have made a difference, since some of the
>evidence you provided at makes it appear that part of your inode table
>may have gotten smashed as well.
That is true. e2fsck -b8193 couldn't restore anything :~~~((((
>happened, but it might not. The main lesson I would take away from all
>of this is that any responsible sysadmin should always be doing
>frequent, reliable backups of any data files that he/she really cares
>about and can't easily reconstruct.
Fortunately this machine has only 100 users, only my friends, and it
is running development kernel... On machine with 2000 or more users I
certanly wouldn't run 2.1.xx kernels :)
Best regards,
Goran Gajic
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/