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]

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 Tom Metro
> 
> I don't recall the ext version being mentioned in this thread. Your
> concern seems to imply v2. Would switching to v3 or v4 be an option,
> which should eliminate the possibility of a long fsck run?

In ext2, you must fsck every time there's an ungraceful dismount.
In ext3/4, you can avoid fsck's after ungraceful dismounts, but still, once
in every ... something like 180 days or 90 reboots or something like that
... It will still fsck during startup.







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