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 |
> If that file system is messed up, running fsck with the -y option could > cause a lot of data to be lost. Even when the file system is corrupted, > you might be able to copy off the data. Do you know of any good references on how to do that, to look for potentially lost data? > For the most part, you could use that option, but it would slow down > booting (as Derek pointed out), and for the most part, you can use it with > confidence. If there's only one disk, and only one partition on the disk (which is how I typically set up our systems), there wouldn't be any slowdown. And the slowdown would only occur when fsck executes. If the system has been properly shut down, it almost never executes. > It is simply when there is a serious problem, you might want > a human to take a look at it. Again, just how does one do that? - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |