From: Mike Fedyk <mfedyk@matchmail.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Hans Reiser <reiser@namesys.com>,
Bernd Eckenfels <ecki@lina.inka.de>,
linux-kernel@vger.kernel.org
Subject: Re: [POT] Which journalised filesystem ? (fwd)
Date: Fri, 5 Oct 2001 16:22:26 -0700 [thread overview]
Message-ID: <20011005162226.A797@mikef-linux.matchmail.com> (raw)
In-Reply-To: <706340000.1002116485@gullevek.piwi.intern> <E15oqKN-00058k-00@calista.inka.de> <20011005113146.B3587@redhat.com> <3BBD8E82.592130A7@namesys.com> <20011005122536.C2293@redhat.com>
In-Reply-To: <20011005122536.C2293@redhat.com>
On Fri, Oct 05, 2001 at 12:25:36PM +0100, Stephen C. Tweedie wrote:
> Hi,
>
> On Fri, Oct 05, 2001 at 02:42:10PM +0400, Hans Reiser wrote:
>
> > > Should be fine with ext3 and XFS. It's not a journaling problem as
> > > much as NFS assuming a particular property of the filesystem.
>
> > Err, I meant it is stable from all reports for recent kernels:-/.... excuse me.
>
> Yes, and it's also worth noting that this same NFS assumption will
> break exports of _all_ filesystems which don't have simple static
> inum/filehandle capabilities. Reiserfs should work just fine now but
> the same NFS problem is still present if you do other things such as
> trying to re-export a SMB mount as NFS.
>
Yes, this issue has been reported many times on the samba mailing lists...
Are there any network filesystems on linux that have the "static
inum/filehandle capabilities"?
prev parent reply other threads:[~2001-10-05 23:22 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
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 [this message]
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=20011005162226.A797@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=sct@redhat.com \
/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.