All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Anders Widman <andewid@tnonline.net>
Cc: reiserfs-list@namesys.com
Subject: Re: ReiserFS and NFS?
Date: Wed, 4 Sep 2002 10:10:12 +0400	[thread overview]
Message-ID: <20020904101012.A10223@namesys.com> (raw)
In-Reply-To: <18030661062.20020903175652@tnonline.net>

Hello!

On Tue, Sep 03, 2002 at 05:56:52PM +0200, Anders Widman wrote:
> 
>    I am trying to use ReiserFS with NFS to work nicely, but I ran into
>    troubles  exporting root (/). I am getting the following error when
>    a   client   tries  to  connect  to  the  root  export  (I am using
>    ReiserFS on root filesystem):
>       rpc.mountd: getfh failed: Operation not permitted
>    After  browsing around different mailing lists and read suggestions
>    about Kernel and NFS utils I found that someone said that there was
>    needed patches to use ReiserFS with NFS?

Hmmm.
What kernel are you using? What nfs server?
2.4.19 with stock knfsd:
angband:~ # cat /etc/exports
/ (ro)

bowl:~# mount angband:/ /mnt/testfs -t nfs
bowl:~# ls /mnt/testfs/
.   bin   cdrecorder  dev  floppy  lib    mnt  proc    root  testfs0  tmp  var
..  boot  cdrom       etc  home    media  opt  rescue  sbin  testfs1  usr

Changing config:
angband:~ # cat /etc/exports
/ (rw,no_root_squash,insecure)
angband:~ # exportfs -a
exportfs: No host name given with / (rw,no_root_squash,insecure), suggest *(rw,no_root_squash,insecure) to avoid warning

bowl:~# ls /mnt/testfs/
.    boot        dev     home   mnt   rescue  testfile  tmp
..   cdrecorder  etc     lib    opt   root    testfs0   usr
bin  cdrom       floppy  media  proc  sbin    testfs1   var

Everything works ok.

But now (/rescue is another mount point):
bowl:~# mount angband:/rescue /mnt/testfs -t nfs

Sep  4 10:06:17 angband rpc.mountd: authenticated mount request from 212.16.7.82:916 for /rescue (/)
Sep  4 10:06:17 angband rpc.mountd: getfh failed: Operation not permitted

>    Right now my exports file looks like this:
>          /usr/src/       192.168.0.100(rw,no_root_squash,insecure)
>          /               192.168.0.100(rw,no_root_squash,insecure)

>    Is this something someone might know how to fix?

What if you allow anyone to connect (use * instead of address?)
Look into logs on on nfs server side for more clues, enable debug.

Basically I do not think yo are experiencing reiserfs problem, but it rather
looks like nfs server configuration problem.

I hope you have not forgot to to 'exportfs -a' after changing /etc/exports.

Bye,
    Oleg

  reply	other threads:[~2002-09-04  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 15:56 ReiserFS and NFS? Anders Widman
2002-09-04  6:10 ` Oleg Drokin [this message]
2002-09-04 21:23   ` Anders Widman

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=20020904101012.A10223@namesys.com \
    --to=green@namesys.com \
    --cc=andewid@tnonline.net \
    --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 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.