From: Andreas Dilger <adilger@clusterfs.com>
To: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: ext3 and SPEC SFS Run rules.
Date: Wed, 28 Jul 2004 17:00:16 -0400 [thread overview]
Message-ID: <20040728210016.GA1439@schnapps.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.44.0407261016580.32233-100000@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
On Jul 26, 2004 10:18 +0100, Tigran Aivazian wrote:
> I think the important part of rule 1. saying "server adheres to the
> protocol" is this bit from rfc1813:
>
> The following data modifying procedures are
> synchronous: WRITE (with stable flag set to FILE_SYNC), CREATE,
> MKDIR, SYMLINK, MKNOD, REMOVE, RMDIR, RENAME, LINK, and COMMIT.
>
> E.g. if a client had a successful SYMLINK and the server crashed, the
> client is not going to discover on the next reboot (of the server) that
> the symlink is somehow disappeared...
Just an FYI - if you are running a heavy sync load like a sync NFS
server you may want to consider running a large external journal for
performance. This means your journal data writes are always sequential
and to a different disk than the main filesystem.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-28 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 18:49 Tigran Aivazian
2004-07-26 7:03 ` Andrew Morton
2004-07-26 9:12 ` Tigran Aivazian
2004-07-26 9:18 ` Tigran Aivazian
2004-07-28 21:00 ` Andreas Dilger [this message]
2004-07-26 19:57 ` Theodore Ts'o
2004-07-26 20:01 ` Andrew Morton
2004-07-26 23:00 ` Neil Brown
2004-07-26 23:45 ` Brian Pawlowski
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=20040728210016.GA1439@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@aivazian.fsnet.co.uk \
/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
all inboxes | Powered by JetHome®