From: "Roy Murphy" <murphy@panix.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [POT] Which journalised filesystem uses Linus Torvalds ?
Date: Wed, 3 Oct 2001 11:21:16 -0500 [thread overview]
Message-ID: <3bbb2cec.6d.0@panix.com> (raw)
'Twas brillig when Sebastien Cabaniols scrobe:
>With the availability of XFS,JFS,ext3 and ReiserFS I am a
>little lost and I don't know which one I should use for entreprise
>class servers.
Well, the Linus Torvalds filesystem (ltfs for short) is a highly developed,
version control filesystem, but it still has a few shortcomings.
When saving a file to ltfs, it sometimes suggests that you should do it a different
way. The ltfs is very particular about how things should be done.
Often, when saving a file, it is dropped without any notification. Experienced
users of the ltfs follow the mantra "submit early and submit often". They repeatedly
resave their files hoping that one of them will be accepted into a "version"
that does get saved to disk.
Several forks of the ltfs (i.e the Alan Cox filesystem -- acfs and the Anread
Arcangeli filesystem -- aafs) are a little better about saving files, but each
of them has its own idea about which files are worthy of being saved.
While these advanced filesystems hold great promise for the future, they should
probably not be used in a production server due to these failings. In fact,
one user of the acfs, Telsa Cox, reports that the acfs often dosn't work at
all before noon local time.
YMMV.
next reply other threads:[~2001-10-03 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 16:21 Roy Murphy [this message]
2001-10-03 22:31 ` [OT] Re: Which journalised filesystem uses Linus Torvalds ? Matt Bernstein
2001-10-04 7:54 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 12:00 [POT] " sebastien.cabaniols
2001-10-03 14:33 ` Dave Cinege
2001-10-03 14:48 ` Sean Hunter
2001-10-03 16:54 ` Fabbione
2001-10-03 17:52 ` Bernd Eckenfels
2001-10-03 18:01 ` Luigi Genoni
2001-10-04 5:42 ` Andrew Ip
2001-10-04 7:32 ` Constantin Loizides
2001-10-04 16:30 ` Nathan Straz
2001-10-04 17:21 ` Hristo Grigorov
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=3bbb2cec.6d.0@panix.com \
--to=murphy@panix.com \
--cc=linux-kernel@vger.kernel.org \
/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