From: "Stephen C. Tweedie" <sct@redhat.com>
To: Bernd Eckenfels <ecki@lina.inka.de>
Cc: linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: [POT] Which journalised filesystem ? (fwd)
Date: Fri, 5 Oct 2001 11:31:46 +0100 [thread overview]
Message-ID: <20011005113146.B3587@redhat.com> (raw)
In-Reply-To: <706340000.1002116485@gullevek.piwi.intern> <E15oqKN-00058k-00@calista.inka.de>
In-Reply-To: <E15oqKN-00058k-00@calista.inka.de>; from ecki@lina.inka.de on Wed, Oct 03, 2001 at 08:01:03PM +0200
Hi,
On Wed, Oct 03, 2001 at 08:01:03PM +0200, Bernd Eckenfels wrote:
>
> Do you had NFS Problems or do you had filesystem problems?
>
> Because NFS interaction with Journaled Filesystems is/was an issue with
> those recent kernels, as far as i understand.
Should be fine with ext3 and XFS. It's not a journaling problem as
much as NFS assuming a particular property of the filesystem.
Resierfs had a particular difficulty with NFS, mainly because the NFS
spec assumes that every file can be looked up by a 64-bit cookie which
doesn't change over reboots, and that's a hard invariant to deal with
when you've only got 32-bit inode numbers in the kernel and when your
filesystem is tree-structured so that the file metadata on disk can
move about. The VFS has been extended a bit in more recent kernels to
allow Reiserfs to give NFS the hints it needs to get the file handles
right.
Cheers,
Stephen
next prev parent reply other threads:[~2001-10-05 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 13:41 [POT] Which journalised filesystem ? (fwd) Clemens Schwaighofer
2001-10-03 18:01 ` Bernd Eckenfels
2001-10-04 10:42 ` Clemens Schwaighofer
2001-10-05 10:48 ` Hans Reiser
2001-10-05 10:31 ` Stephen C. Tweedie [this message]
2001-10-05 10:41 ` Hans Reiser
2001-10-05 10:42 ` Hans Reiser
2001-10-05 11:25 ` Stephen C. Tweedie
2001-10-05 23:22 ` Mike Fedyk
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=20011005113146.B3587@redhat.com \
--to=sct@redhat.com \
--cc=ecki@lina.inka.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.