BLU Discuss list archive

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

best practices using LVM and e2fsck

Subject: best practices using LVM and e2fsck
From: blu-Z8efaSeK1ezqlBn2x/YWAg at public.gmane.org (Edward Ned Harvey)
Date: Thu, 1 Jul 2010 09:47:47 -0400
In-reply-to: <4C2BC1E0.1030700-5a1Jt6qxUNc@public.gmane.org>
References: <10B70046B6BA4EEABFE45C40142FA2E0@dnanet.mit.edu> <001601cb172b$5d83ea70$188bbf50$@com> <20100629213222.GM7359@dragontoe.org> <000e01cb1872$4a545410$defcfc30$@com> <EEBBF0238C7146B6855CCE5CC9568715@dnanet.mit.edu> <20100630173628.GE2447@collab.or8.net> <4C2BC1E0.1030700@vl.com>

> 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.

Follow-Ups:
- best practices using LVM and e2fsck
  - From: mkomarinski-GqRSzq0LZOzYtjvyW6yDsg at public.gmane.org (Mark Komarinski)
- best practices using LVM and e2fsck
  - From: jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org (Jarod Wilson)

Prev by Date: multipath alias not being created.
Next by Date: best practices using LVM and e2fsck
Previous by thread: multipath alias not being created.
Next by thread: best practices using LVM and e2fsck
Index(es):
- Date
- Thread


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

Boston Linux & Unix / webmaster@blu.org