Hi Steve,
On Wed, Aug 17, 2011 at 12:28 PM, Steve Langasek <
steve.langa...@canonical.com> wrote:
> > BTW, this is likely a 64-bit problem, as that number is -2, right? Maybe
> > it's an exceptionally bad programming error. I guess I won't see this
> > problem on i386.
>
> Incorrect.
>
>
Have yo
On Wed, Aug 17, 2011 at 06:51:31AM -, exa wrote:
> This bug persists in Ubuntu 11.04 on amd64. The nfsv4 is absolutely not
> working, can anybody tell me why this terrible code is the default?
It's not "terrible code". NFSv4 works perfectly well if configured.
> Please remove this non-functi
BTW, this is likely a 64-bit problem, as that number is -2, right? Maybe
it's an exceptionally bad programming error. I guess I won't see this
problem on i386.
So, maybe there is a serious 64-bit bug, in this case, why is the nfs-
user-server package removed from the distribution, why are the choi
This bug persists in Ubuntu 11.04 on amd64. The nfsv4 is absolutely not
working, can anybody tell me why this terrible code is the default?
Please remove this non-functional kernel server thing from the
distribution, it doesn't work as it ought to. If nfsv4 isn't working,
then what's the point of t
I only accidentally found this bug using Ubuntu 11.04 pre-installed
daily build 20110409 for ARM on a Pandaboard. All my 10.10 i386 machines
work fine, but now that I checked, they're actually not fine, so it was
just luck that it didn't cause me any trouble. Setting NEED_IDMAPD=yes
fixes the probl
im getting the same issue
previously server was 10.04, and clients 10.10.
after upgrade of server to 10.10, both had uid/gid problems.
I have fixed it on one client machine 10.10 by setting the client mount options
to include ...nfsvers=3
but on another client 10.10 machine, both patched yest
We are also affected.
I have worked around the automounter problem by using auto.net and
editing the opt variable to contain "-vers=3"
-- Karsten
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662711
Hi out there,
As there is no activity here, I leave my (working) hack in place. Just
posting to help others with the same problem.
Picked up /sbin/mount.nfs from Ubuntu 10.04 installation. This defaults
to nfs3 with works around the (I suppose) server side bug with nfs4.
Have fun,
Klaus
--
Y
We have the problem, that the nfs-server is externally hosted and NFS
entries are published via automounter maps.
Running now 10.10 on an NFS client we have the situation:
* mount uses NFS4 per default
* autmounter maps don't give something like vers=3
=> nfs stuff is mounted nobody/nogroup
The
This morning, I had a working NFS set-up on an 10.04 server with 10.10
clients. After upgrading the server to 10.10, I had this problem as
well. Setting NEED_STATD=no and NEED_IDMAPD=yes on BOTH ends fixes it,
indeed. Thanks a lot for the info!
And... yes! I would have appreciated a default config
@Perry:
Thanks, from your suggestion I made the changes to /etc/default/nfs-
common and started idmapd, and the problem was resolved.
@Tiemen:
Thanks for the link, but even the wiki authors seem confused about this
issue...
So, now it seems clear that it is a default configuration problem rath
I believe this is documented already here:
https://help.ubuntu.com/community/NFSv4Howto
--
NFS user/group mapping not working in 10.10
https://bugs.launchpad.net/bugs/662711
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Not a bug it seems, but needs documentation or something somewhere.
10.10 enables NFSv4 and I was able to fix it by enabling nfs idmap on
both server and client.
On my solaris server, I edited /etc/default/nfs and set NFSMAPID_DOMAIN
to my server's name (domain name, whatever), then did svcadm re
same problem here, client 10.10 and server 10.10 gives me UID and GID
4294967294. UID and GID are correct on the server but not on the client.
It works however if i connect an ubuntu 10.04 client to the 10.10
server. So it seems to be a client issue. The solution im using is
autofs for all my user
Solaris servers, ubuntu 10.10 clients. This used to work fine.
Exact same problem as the one above:
"However now the client is always displaying 4294967294 for the UID and GID but
- and here is the strange bit - if I create a file on the client it shows up on
the server with the correct user and
For what it's worth, I resolved the same (?) problem involving a Solaris
ZFS server and Ubuntu 10.10 nfs client by using nfs mount option vers=3.
--
NFS user/group mapping not working in 10.10
https://bugs.launchpad.net/bugs/662711
You received this bug notification because you are a member of Ub
I can confirm this bug for our mixed environment (Solaris servers using
zfs, and Ubuntu clients). It does seriously affect us, since the
behaviour of file creation is quite erratic (as far as I can see).
Additional observations:
1. No problems with older Solaris servers running NFS3 and NFS2 - see
--
NFS user/group mapping not working in 10.10
https://bugs.launchpad.net/bugs/662711
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
18 matches
Mail list logo
