All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andrew Lee <andrew@sonysnowie.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs mount problem on vxfs
Date: Wed, 10 Jan 2007 12:47:04 +0000	[thread overview]
Message-ID: <20070110124704.GA3350@infradead.org> (raw)
In-Reply-To: <56800.63.119.254.10.1168372296.squirrel@mail.sonysnowie.com>

On Tue, Jan 09, 2007 at 02:51:36PM -0500, Andrew Lee wrote:
> Hi all,
> 
> I recently upgraded my redhat box to SuSE linux, the kernel version is
> 2.6.5-7.252-bigsmp
> 
> Here is my nfs server version
> 
> yast2-nfs-client-2.9.11-23.2
> yast2-nfs-server-2.9.9-23.2
> 
> I exported 2 directories, one is the /tmp on local reiserfs, and the other
> one is a /emc on vxfs (emc disk). I tried multiple nfs clients, the client
> can mount the /tmp, but none of them can mount the /emc directory, the
> client just hung.

I haven't added support for nfs exporting to the vxfs driver.  To be honest
it's quite old and didn't resource (time and actual  vxfs native systems)
to test it again.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-01-10 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 19:51 nfs mount problem on vxfs Andrew Lee
2007-01-10 12:47 ` Christoph Hellwig [this message]
2007-01-10 16:47   ` Trond Myklebust
2007-01-11  2:12     ` Neil Brown

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=20070110124704.GA3350@infradead.org \
    --to=hch@infradead.org \
    --cc=andrew@sonysnowie.com \
    --cc=nfs@lists.sourceforge.net \
    /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.