From owner-freebsd-hackers Wed May 12 8:48:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id EF63E15179 for ; Wed, 12 May 1999 08:48:48 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id RAA06857; Wed, 12 May 1999 17:48:26 +0200 (CEST) Date: Wed, 12 May 1999 17:47:43 +0200 From: Stefan Bethke To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Metablock caching & negative block # Message-ID: <819360.3135520063@d225.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhihui Zhang wrote: > By the way, all other metablocks seem to be delay-written. In other = words, > they are not written synchronously. What happens if the system crashes > before their updates go to disk. I read in the mailinglist that FreeBSD > metadata I/O are conservative. Can anyone describe this a little bit = for > me. AFAIK, the non-static information in the superblock and others can easily be reconstructed by fsck (the information is gathered anyway). Stefan -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message