From: David Liontooth <lionteeth-tj7FKCIresWsTnJN9+BGXg@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: No write access with recent versions of nfs-utils in Debian
Date: Sun, 30 Nov 2008 14:13:49 -0800 [thread overview]
Message-ID: <4933101D.9000308@cogweb.net> (raw)
This appears to be a Debian-specific issue, so I'm just looking for a
pointer from someone who may know about it.
I installed Debian sid on a new machine back in July, including the
current nfs-common and nfs-kernel-server. NFS mounts were successful,
but did not allow write -- I lost some serious data on one occasion
before I noticed the problem. mount and nfs-utils were upgraded several
times since, and never gave the requested write access. I've been
assuming the problem was firewall-related and lived with it.
On the other machines in the group, NFS writes worked fine. I banged my
head against the wall for a while today, after finally finding time to
look into the problem, and discovered a completely different version of
nfs-utils was running on the new machine. After a painful downgrade
things work fine again.
Here's the verbose output of the version that didn't work, nfs-common
1:1.1.3-2:
mount -vvv /mnt/cortona1
mount: fstab path: "/etc/fstab"
mount: lock path: "/etc/mtab~"
mount: temp path: "/etc/mtab.tmp"
mount: spec: "cortona:/tv1"
mount: node: "/mnt/cortona1"
mount: types: "nfs"
mount: opts: "noauto,user,exec,rw,rsize=16k,wsize=16k,hard,intr"
mount: external mount: argv[0] = "/sbin/mount.nfs"
mount: external mount: argv[1] = "cortona:/tv1"
mount: external mount: argv[2] = "/mnt/cortona1"
mount: external mount: argv[3] = "-v"
mount: external mount: argv[4] = "-o"
mount: external mount: argv[5] =
"rw,nosuid,nodev,noauto,user,rsize=16k,wsize=16k,hard,intr"
mount.nfs: trying xxx.xxx.xxx.178 prog 100003 vers 3 prot TCP port 2049
mount.nfs: trying xxx.xxx.xxx.178 prog 100005 vers 3 prot UDP port 32774
cortona:/tv1 on /mnt/cortona1 type nfs
(noauto,user,exec,rw,rsize=16k,wsize=16k,hard,intr)
tna@roma$ cd /mnt/cortona1
tna@roma:/mnt/cortona1$ touch one
touch: cannot touch `one': Permission denied
Downgrading to 1:1.1.0-5 restored proper write access. Is this a
familiar-looking problem to someone?
Dave
next reply other threads:[~2008-11-30 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 22:13 David Liontooth [this message]
[not found] ` <4933101D.9000308-tj7FKCIresWsTnJN9+BGXg@public.gmane.org>
2008-11-30 23:18 ` No write access with recent versions of nfs-utils in Debian Steinar H. Gunderson
[not found] ` <20081130231819.GA15303-6Z/AllhyZU4@public.gmane.org>
2008-12-01 6:53 ` David Liontooth
[not found] ` <49338A03.4040000-tj7FKCIresWsTnJN9+BGXg@public.gmane.org>
2008-12-01 8:55 ` Steinar H. Gunderson
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=4933101D.9000308@cogweb.net \
--to=lionteeth-tj7fkcireswstnjn9+bgxg@public.gmane.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox