From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] making better use of ext2fs?
Date: Mon, 14 May 2001 13:25:44 +0100 [thread overview]
Message-ID: <20010514122438.46975199E3@mail.cse.psu.edu> (raw)
>>One thing I've noticed is that people report kfs sometimes gets flaky
>>when used in a stand-alone configuration.
apart from not sync'ing on shutdown, i suspect many of the problems people had with
kfs were mainly caused by bugs elsewhere in the kernel (eg, the ones that
caused trouble when pages were paged out).
perhaps kfs deserves a bad name for other reasons, but i don't think this
is one of them. it's worth noting that if disk/kfs is buggy, it's quite
serious, because the main file server uses similar code.
i've been running various versions of kfs on my thinkpads for
more than five years.
next reply other threads:[~2001-05-14 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 12:25 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-14 18:10 forsyth
2001-05-14 17:17 Jonathan Sergent
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=20010514122438.46975199E3@mail.cse.psu.edu \
--to=forsyth@vitanuova.com \
--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).