All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paweł Sikora" <pluto@agmk.net>
To: linux-nfs@vger.kernel.org
Subject: nondeterministic exportfs? /home/users (ext4) does not support NFS export.
Date: Tue, 14 Dec 2010 19:14:54 +0100	[thread overview]
Message-ID: <201012141914.55076.pluto@agmk.net> (raw)

Hi,

i have a new machine with fresh linux distro (2.6.36.2 kernel, nfs-1.2.3)
and the configured export doesn't work sometimes.

following md1, md2 partitions are mounted and configured for exporting:

Filesystem            Size  Used Avail Use% Mounted on
/dev/md0              7.6G  1.4G  5.8G  19% /
/dev/md1              1.9T   42G  1.9T   3% /home/atest
/dev/md2              798G  116G  682G  15% /home/users

# /etc/rc.d/init.d/nfs status
Configured NFS exports:
/home/atest     *(rw,async,no_subtree_check,no_root_squash,insecure_locks)
/home/users     *(rw,sync,no_wdelay,no_subtree_check,no_root_squash,insecure_locks)

Active NFS exports:
/home/atest     <world>(rw,async,wdelay,no_root_squash,no_subtree_check,insecure_locks)
/home/users     <world>(rw,no_root_squash,no_subtree_check,insecure_locks)

rpc.mountd (pid 3195) is running...
nfsd (pid 3213 3212 3211 3210 3209 3208 3207 3206) is running...

# exportfs -v
/home/atest     <world>(rw,async,wdelay,no_root_squash,no_subtree_check,insecure_locks)
/home/users     <world>(rw,no_root_squash,no_subtree_check,insecure_locks)

but the /home/users doesn't work and (bad workaround) re-export is needed.

# exportfs -rv
exporting *:/home/users
exportfs: /home/users does not support NFS export
exporting *:/home/atest

# exportfs -rv
exporting *:/home/users
exporting *:/home/atest

/home/atest works fine, /home/users has weird problems.

what's wrong with this /home/users @ ext4 ?
thanks for any hints.

BR,
Pawel.

                 reply	other threads:[~2010-12-14 18:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201012141914.55076.pluto@agmk.net \
    --to=pluto@agmk.net \
    --cc=linux-nfs@vger.kernel.org \
    /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.