After doing a little reading on ext3, I decided it would be nice to try it out with my 8.1 root partition (saving /home for later when I'm sure it works!). I didn't originally install with ext3, so I did a tunefs -j /dev/hda6 (my root partition), and modified fstab to ext3 instead of ext2 for this partition. "mount" even lists the partition as ext3.
Well, the kids were playing on the computer and turned the power off while loading a page in Netscape! Excellent, I thought, a good chance to see how well ext3 works! So when I booted-up the machine again, I was a little surprised to find my root partition being totally fsck from start to finish! No only that, but I was unfortunate enough to have sustained damage that caused entries in lost+found (first time in 3 years of Linux use, and numerous switch-offs!). I was expecting to see some different response from fsck... perhaps something to tell me it was replaying steps in the journal or something! Am I missing something? I saw (after the event, of course) in the Red Hat whitepaper for ext3 that you're supposed to run mkinitrd to recreate the initial ramdisk, if you're using ext3 on your root partition. Does this apply with Mandrake too (I kinda thought this would be compiled right into the kernel?). Many Thanks for any help! Scottie btw, how does one handle lost+found entries? If it's anything like MS Scandisk used to be, I'd have a quick look through the generated files, see if it looked useful (9 times out of 10 I'd have little idea what the data was), then delete the files.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
