Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: gerald_clark on May 05, 2015, 04:27:17 PM
-
showmount does not show any mounts. Instead it errors.
showmount --exports vault
clnt_create: RPC: Unknown host
Ping of vault works.
showmount run on a CentOS 6 machine show the exports as expected.
nfs V4 errors
nfs4 mounting an export. Mount succeeds, but an ls -l of any subdirectory of the mount point shows all files and directories have a user and
group of 42949672
"ls -ln" shows user and group of 4294967294
Files created by the Core 6 client show up on the server with the proper user and group, but show on Core as described above.
The directory is exported with no_root_squash and the default no_user_squash.
nfs4 mounts from a CentOS 6 machine show proper user and groups.
-
Do you think this is an nfs bug, something to do with the extension packaging or a tc base bug?
-
I really don't know. I just started using NFS4 on tc to get nfs connections through my firewall.
I tried 6.0 and 5.4 with the same results - odd 'ls -l' output for 'NFS4' and correct output for NFS3.
Since it seems to work except for the user and group i 'ls', I am wondering if it a busybox 'ls' bug. Is there a different user and group id integer size in V4 vs V3?
Without another 'ls' program I cant check that out though.
Showmount not working suggests a busybox problem.
-
there's a "ls" in the coreutils extension, you could maybe try that?
-
coreutils.tcz provides the the standard ls command.
-
With /usr/local/bin/ls ls -l and ls -ln both show user and group as 4294967294.
It is starting to look like an nfs-utils problem.
-
ref blfs svn, is libnfsidmap required?
..or ref http://tinycorelinux.net/5.x/x86_64/tcz/src/nfs-utils/compile_nfs-utils is nfsv4 even enabled?
-
NFS4
mount.nfs4 vault:/var/lib/tftpboot/tcl/core-6.x /mnt/work
mount | grep vault
vault:/var/lib/tftpboot/tcl/core-6.x on /mnt/work type nfs4 rw,relatime,vers=4.0,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.29,local_lock=none,addr=192.168.0.13)
ls -l /mnt/work
total 48
drwxrwxr-x 2 42949672 42949672 4096 May 4 08:24 boot
-rw-rw-r-- 1 42949672 42949672 20704 Apr 21 2012 chain.c32
drwxr-xr-x 3 42949672 42949672 4096 Nov 10 13:06 home
-rwxrwxrwx 1 42949672 42949672 296 Apr 17 14:14 mk-ntfs-3g
drwxrwsr-x 4 42949672 42949672 4096 May 3 07:38 opt
drwxrwxr-x 4 42949672 42949672 4096 Apr 18 01:59 tce
-rw-r--r-- 1 42949672 42949672 120 Apr 18 02:01 tcz.lst
ls -ln /mnt/work
total 48
drwxrwxr-x 2 4294967294 4294967294 4096 May 4 08:24 boot
-rw-rw-r-- 1 4294967294 4294967294 20704 Apr 21 2012 chain.c32
drwxr-xr-x 3 4294967294 4294967294 4096 Nov 10 13:06 home
-rwxrwxrwx 1 4294967294 4294967294 296 Apr 17 14:14 mk-ntfs-3g
drwxrwsr-x 4 4294967294 4294967294 4096 May 3 07:38 opt
drwxrwxr-x 4 4294967294 4294967294 4096 Apr 18 01:59 tce
-rw-r--r-- 1 4294967294 4294967294 120 Apr 18 02:01 tcz.lst
NFS3
mount vault:/var/lib/tftpboot/tcl/core-6.x /mnt/work2
mount | grep work2
vault:/var/lib/tftpboot/tcl/core-6.x on /mnt/work2 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=none,addr=192.168.0.13)
ls -l /mnt/work2
total 48
drwxrwxr-x 2 tc 501 4096 May 4 08:24 boot
-rw-rw-r-- 1 tc staff 20704 Apr 21 2012 chain.c32
drwxr-xr-x 3 root root 4096 Nov 10 13:06 home
-rwxrwxrwx 1 tc staff 296 Apr 17 14:14 mk-ntfs-3g
drwxrwsr-x 4 root staff 4096 May 3 07:38 opt
drwxrwxr-x 4 tc staff 4096 Apr 18 01:59 tce
-rw-r--r-- 1 tc staff 120 Apr 18 02:01 tcz.lst
ls -ln /mnt.work2
total 48
drwxrwxr-x 2 1001 501 4096 May 4 08:24 boot
-rw-rw-r-- 1 1001 50 20704 Apr 21 2012 chain.c32
drwxr-xr-x 3 0 0 4096 Nov 10 13:06 home
-rwxrwxrwx 1 1001 50 296 Apr 17 14:14 mk-ntfs-3g
drwxrwsr-x 4 0 50 4096 May 3 07:38 opt
drwxrwxr-x 4 1001 50 4096 Apr 18 01:59 tce
-rw-r--r-- 1 1001 50 120 Apr 18 02:01 tcz.lst
-
Hi gerald_clark
Don't know if it helps, but Googling linux nfs user group 42949672 turned up this:
http://serverfault.com/questions/98741/files-mounted-over-nfsv4-are-owned-by-4294967294-uids-and-gids-match
-
None of the files referenced in that article exist in /etc or /usr/local/etc in tc
Also, tc has no idmapd program.