-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hiya list,
Just need some opinions here, and am not looking for a raving flame-war regarding which file system is better etc ;-) ~ Oh and please excuse the long mail, but I need explain my situation clearly to avoid confusion. Last week Friday while I was work I successfully upgraded my home workstation via ssh to the current Xorg 7.0. The wife came home and unintentionally turned Off the main power to the PC instead of On (she thought the PC was off). Since then everything started going really bad on my root partition. KDE needed a few things to be upgraded to fix dependencies which seemed to trigger the following errors. Random KDE components (like kdm) would sometimes start, sometimes not, depending on the reboot. Sometimes in /var/log/messages there were hints to *missing* *.so files in the /usr/kde/3.5/lib folder, yet they did *appear* to be there ~ although when doing a simple `ls` of the lib directory I got (depending on the reboot) between 10 and 30 errors about missing files or directories. It seemed that reiserfs had "catalogued" that files were supposed to be there, but `ls /usr/kde/3.5/lib` could not find them. For the record I am using reiserfs 3.6 (default in vanilla kernel, no patches) ~ not 4.x. The lib dir is also included in /etc/ld.so.conf and ldconfig was run several times to test. After a reboot I would get different errors, and sometimes none when it would just work (Xorg / kde). `revdep-rebuild -p` came up after every reboot with different packages, indicating it detected different missing *.so files after each reboot, mainly in the /usr/kde/3.5/lib. Now I know Linux, and errors like this are not normal in any way. I rebooted with the Gentoo Live-cd and did a few disc scans (fsck) of my root reiserfs partition. Every single time I ran it it would find errors and fix. I did a `--rebuild-tree -S` and for 45 minutes I got error after error after error (thousands), apparently all fixed. Re-running the scan started the whole error-fixing process again. A "badblocks" test showed no error on the partition though. I decided that my reiserfs file tree must have been corrupt, and formatted the root drive (`mkreiserfs /dev/hda3`) and restored a full backup (dar). After a reboot a repreated the scan, to find the same issues again. It seems a format did not clean the file table or something, I don't know. As a last test I formatted the root partition as an ext2 partition, and again restored the backup. No errors, no bad blocks, no problems. What gives? I don't want to use ext2 or ext3, and I have for a couple of years now relied on reiserfs on all my systems, but what could be the problem here? Why did reiserfs seem to mess up like this, and why after formatting it did I get the same errors again? Regards, Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iD8DBQFEu2cgCt0ZF9kLPvYRAqzAAJ9txAJIhhVTnVd1SUwzvfrPHeelWwCfTt5c +X+APrx+dbAjanSBKcYJOIU= =PYzO -----END PGP SIGNATURE----- -- gentoo-user@gentoo.org mailing list
