9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] making better use of ext2fs?
Date: Mon, 14 May 2001 19:10:31 +0100	[thread overview]
Message-ID: <20010514181358.130FF199F2@mail.cse.psu.edu> (raw)

>>Am I confused or is the problem with data corruption on unclean
>>shutdown with kfs the same as with ext2, namely that there aren't
>>synchronous metadata updates?

disk/kfs updates most metadata synchronously (look
for localfs and Bimm), which
might be why some people complain about its performance.
the file server kernel is (just) slightly more relaxed about it.

that reduces the scrambling, but doesn't ensure that
the data blocks from the last file you wrote have been
written out, hence the need to sync.



             reply	other threads:[~2001-05-14 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14 18:10 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-14 17:17 Jonathan Sergent
2001-05-14 12:25 forsyth
2001-05-14 10:36 Aharon Robbins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010514181358.130FF199F2@mail.cse.psu.edu \
    --to=forsyth@caldo.demon.co.uk \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).