As mentioned in the linked forum discussion... After emerging baselayout-1.8.6.5 (marked as ~x86), it appears that the filesystem journal becomes corrupted. Personally I have had problems with both XFS and ReiserFs, and another user has had problems with ext3. Reproducible: Always Steps to Reproduce: 1. Emerge baselayout-1.8.6.5 2. After successful emerge, reboot machine Actual Results: For ReiserFS (which I have the best recollection of): reiserfsck reports problems with the journal, booting of the system is halted. I was able to drop into Single User mode at this point to correct the issue. Expected Results: System should have come up correctly, and proceeded to the login screen Was able to recreate the journal for ReiserFS and upon subsequent reboots have not had any problems. To the best of my memory I was unable to get into single user mode to repair my XFS partitions when it occured (they were done as two seperate installs, one all Reiser, one all XFS), so I had to reboot with the livecd.
I have upgraded to the mentioned version of baselayout without any problems. My system is running on XFS. May be this is reiserfs specific? Sounds very stange.
i find it extremely hard to believe that it corrupts ALL journals for all journaling file systems...
I run ext3, no problem. Find me anything that differs from 1.8.6.4 that could cause this, and then after testing it outside baselayout, and if able to verify, reopen. This is bogus.
