Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

interesting note on fsck and journalled filesystems



> The reason to use a journalling file system has more to
> do with crash recovery time than with integrity. IMHO, most Unix/Linux
> file systems run without any significant problems for years.

Crash recovery has been more of an issue at our shop than most, because we use 
Unix/Linux in factory equipment.  People are turning the power off all the 
time without doing a shutdown.  Journalling filesystems have been a big plus.  
It's such a hassle to try to get a non-computer type to punch in 
"fsck -y /dev/sd0a", or something like it.  I could never understand the 
current reason for requiring a user to type in an fsck command anyway (not 
just limited to Linux, Solaris does it, too).  I knew one graduate student 
when I was in school that would actually repair inodes and recover files, but
I've meet no one else since then that would know what to do.




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org