All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David L. Parsley" <parsley@roanoke.edu>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Hans-Peter Jansen <hpj@urpla.net>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	Neil Brown <neilb@cse.unsw.edu.au>,
	linux-kernel@vger.kernel.org,
	Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: [BUG] symlink problem with knfsd and reiserfs
Date: Tue, 15 Jan 2002 13:01:15 -0500	[thread overview]
Message-ID: <3C446E6B.1020709@roanoke.edu> (raw)
In-Reply-To: <20020115115019.89B55143B@shrek.lisa.de>	<E16QVf3-0002NG-00@charged.uio.no>	<15428.23828.941425.774587@laputa.namesys.com>	<20020115163208.785831435@shrek.lisa.de> <15428.27801.724105.557093@laputa.namesys.com>

Nikita,

To be clear: if I upgrade the kernel on my nfs server to 2.4.latest and 
mount -o conv my reiserfs partition, that will almost certain fix my 
knfsd problem with a very small likelihood of generation problems?

regards,
	David
-- 
David L. Parsley
Network Administrator, Roanoke College
"If I have seen further it is by standing on ye shoulders of Giants."
--Isaac Newton


  reply	other threads:[~2002-01-15 18:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 11:50 [BUG] symlink problem with knfsd and reiserfs Hans-Peter Jansen
2002-01-15 12:06 ` Trond Myklebust
2002-01-15 14:07   ` Nikita Danilov
2002-01-15 13:40     ` Trond Myklebust
2002-01-15 15:27       ` Nikita Danilov
2002-01-15 15:38         ` Trond Myklebust
2002-01-15 16:47           ` Nikita Danilov
2002-01-15 16:31             ` Hans-Peter Jansen
2002-01-15 17:53               ` Nikita Danilov
2002-01-15 18:01                 ` David L. Parsley [this message]
2002-01-15 19:30                   ` Nikita Danilov
2002-01-15 18:14                 ` Hans-Peter Jansen
2002-01-15 19:25                   ` Nikita Danilov
2002-01-15 15:32     ` Hans-Peter Jansen
2002-01-15 13:40 ` David L. Parsley

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=3C446E6B.1020709@roanoke.edu \
    --to=parsley@roanoke.edu \
    --cc=Nikita@Namesys.COM \
    --cc=Reiserfs-List@Namesys.COM \
    --cc=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=trond.myklebust@fys.uio.no \
    /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.