From owner-freebsd-hackers Mon Jun 8 20:37:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15564 for freebsd-hackers-outgoing; Mon, 8 Jun 1998 20:37:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA15491 for ; Mon, 8 Jun 1998 20:36:59 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) id XAA20916; Mon, 8 Jun 1998 23:35:51 -0400 From: "Allen Smith" Message-Id: <9806082335.ZM20914@beatrice.rutgers.edu> Date: Mon, 8 Jun 1998 23:35:51 -0400 In-Reply-To: Eivind Eklund "Re: Newbie 3 questions." (Jun 8, 2:33pm) References: <199806080349.UAA29145@grebe.Stanford.EDU> <199806080414.XAA01195@dyson.iquest.net> <19980608143347.59513@follo.net> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Eivind Eklund Subject: Re: Newbie 3 questions. Cc: hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jun 8, 2:33pm, Eivind Eklund (possibly) wrote: > ... and (as John well knows) it can be tuned to run an async policy > similar to the one in Linux. Which policy you run is a tradeoff > between the security of synchronous metadata updates (you get the > guarantees that you don't get data crossing over from file to file > during crashes, that directories don't get totally screwed up, etc) vs > speed in massive manipulation of the filesystem (large amounts of > renames, creation of lots of small files, etc). The default policy is > the safest of these. Is async necessary/desirable for an MFS, or is it automatic? From the 4.4BSD book, I know that the 4.4BSD MFS is built just like a FFS, only using pageable memory space instead of filesystem space. Thanks, -Allen P.S. If it isn't automatically async, I might see if I can patch things so that it is. Somebody else doing this would be preferable, however. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message