From: Samuel Flory <sflory@valinux.com>
To: Josh Durham <jmd@aoe.vt.edu>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] NFS and reiserfs
Date: Mon, 05 Feb 2001 11:52:51 -0800 [thread overview]
Message-ID: <3A7F0492.AD31A2FC@valinux.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102051410440.22045-100000@hermes.aoe.vt.edu>
I had some intial issues with my v3 mounts, but it appears that it was
related to hitting the ulimit on a make -j 16. (It's nice to work for a
hardware company, and have access to an 8-way.) In case since upping my
ulimit on the client kernel builds seem to work just with a server power
off in the middle.
I generally run everything v2, and don't have the issue of non-linux
clients. So I'm not sure how much help I can be. I seem to remember
someone (you?) talking about v3 issues with SGI boxes under 2.4 on the
nfs list. I didn't much pay much attention as it wasn't an issue I
could help with.
http://sourceforge.net/mail/?group_id=14
Josh Durham wrote:
>
> Any problems with NFSv3? I had tons of issues, but NFSv2 seems to work
> just fine. It was with SGI clients.
>
> - Josh
>
> On Mon, 5 Feb 2001, Samuel Flory wrote:
>
> > Dirk Mueller wrote:
> > >
> > > On Mon, 05 Feb 2001, Grahame Jordan wrote:
> > >
> > > > Should I convert all of my NFS filesystems to ext2 or is there another
> > > > option?
> > >
> > > If you use kernel 2.4.x: there are patches for NFS support.
> > >
> >
> > You can also try the rpms below. They seem to work for me, but your
> > results may vary. If you really want to be able to gracefully recover
> > you need to force sync on all of your exports.
> >
> > http://ftp.valinux.com/pub/people/flory/2.4.1/
> >
> >
> > The patch is here:
> > ftp://ftp.namesys.com/pub/reiserfs-for-2.4/linux-2.4.0-reiserfs-3.6.25-nfs.diff
> >
> >
--
Solving people's computer problems always
requires more hardware be given to you.
(The Second Rule of Hardware Acquisition)
Samuel J. Flory <sam@valinux.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-05 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A7E40D1.DBCC16E9@cpgen.cpg.com.au>
2001-02-05 11:48 ` [reiserfs-list] NFS and reiserfs Dirk Mueller
2001-02-05 19:06 ` Samuel Flory
2001-02-05 19:11 ` Josh Durham
2001-02-05 19:52 ` Samuel Flory [this message]
2001-02-06 0:56 ` Paul Jakma
2001-02-07 2:48 ` Neil Brown
2001-02-07 3:00 ` Paul Jakma
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=3A7F0492.AD31A2FC@valinux.com \
--to=sflory@valinux.com \
--cc=jmd@aoe.vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox