![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Jerry Feldman wrote: > Recovering the root file system is a bit different from other file > systems. When fsck runs during the boot process, the root file system > is mounted read-only and the other file systems are not mounted. It is > ok to do a full recovery on a file system that is not mounted, but not > root. The reiser fsck utility will not allow you to do a complete > repair on root unless you boot from recovery. Ext2 and ext3 do allow a > repair of the root file system when your system is running, but that > file system MUST be mounted read-only. If you try to repair a mounted > file system that is mounted as read-write, the system will write the > in-memory data back onto that file system, and then you are screwed. Yup, That is what happened to me. And since then I use the rescue disk. I had forgotten the reason why. You reminded me I need to update my rescue disk to the current release. > The best practice is to boot from a recovery disk and perform the > repair while the root file system is unmounted. (This is true with all > Linux and Unix systems). You can then mount that file system from the > recovery disk and check it out. > (Make sure that your recovery disk contains the proper file system and > utilities at the same rev. of what your system is running. > Thanks, Jim Kelly-Rand
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |