http://qa.mandrakesoft.com/show_bug.cgi?id=4862
------- Additional Comments From [EMAIL PROTECTED] 2003-24-08 00:28 ------- Danny, it seems much better on 9.2b2 than on 9.1, I had an automatic reboot (instead of seeing the REBOOT LINUX message) on my new 9.2b2 install, and I can't get it to do the old bad behaviour by hard resets, with root on ext3. The ext3 root partition it's journal recovered now before init even starts. Also, if left alone during boot after an unclean shutdown, it does the right thing, and the user doesn't come back to a "Do you want to run fsck?"-type question. With bootsplash in silent mode by default, the user probably won't see any tempting prompts anyway ;-). Even if fsck is run by the user, it's now after a successful journal recovery, so shouldn't result in corruption of files. Or are you seeing worse behaviour on cooker? (I couldn't find any changelog claiming credit for this apparent improvement, so maybe I haven't been testing enough, maybe I should hard reset while installing packages, running rsync, playing music, and compiling a kernel?). -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Many people are tempted to press "Y" after an unclean shutdown so that (according to message) filesystem gets checked. But for ext3 this runs fsck, which has a big chance of destroying files (somehow, it seems that it destroys more on ext3 than on ext2). please: - remove the message altogether from rc.sysinit for journalling fs (an expert can still do it manually, if for some reason it is wanted) - make the check sound like a bad idea. d.
