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 | Linux Links | Bling | About BLU

BLU Discuss list archive


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

best practices using LVM and e2fsck



> From: discuss-bounces-mNDKBlG2WHs at public.gmane.org [mailto:discuss-bounces-mNDKBlG2WHs at public.gmane.org] On
> Behalf Of Stephen Goldman
> 
>     I am afraid if I "need" to reboot- which I don't for see and e2fsck
> kicks off it will take a long time to bring up the server.
> 
>     Is it a good idea to plan service outages to run -e2fsck on the
> mounts beforehand. What do others do ?

This might not be helpful.  I'm replying to the question "what do others
do."  I never use large filesystems (large numbers of files/directories) on
linux.  I do all of this on solaris/opensolaris with ZFS.  The ability to
scrub a filesystem while it's mounted and in use seems like such a brainless
obvious feature.

Whenever my linux systems do fsck themselves, I just let it run.  Since my
filesystems are not huge, they don't take too long.







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