2016-02-11, 06:46
I was using SMB previously but scanning for new videos pegged the CPU on the NAS and took forever. NFS was much faster. Looks like I might have to switch back to SMB unfortunately as I have no clue why this is happening.
2016-03-05, 07:12
Using `nfstrace` I found the following:
So the files that show up as "0 B" in kodi have `name attributes: void name handle: void`. I'm not sure why that is happening.
I think that I may have found part of the answer. It may be related to "inode64". Directories with inode values > 64bits don't seem to be exported properly.
Code:
file id: 2429 name: Music name attributes: type: DIR mode: OWNER_READ OWNER_WRITE OWNER_EXEC GROUP_READ GROUP_WRITE GROUP_EXEC OTHER_READ OTHER_EXEC nlink: 8 uid: 1000 gid: 1000 size: 96 used: 4096 rdev: specdata1: 0 specdata2: 0 fsid: 0 fileid: 2429 atime: seconds: 1454459047 nseconds: 426231589 mtime: seconds: 1419893363 nseconds: 159754539 ctime: seconds: 1419893363 nseconds: 159754539 name handle: handle: 01000181000000007d090000000000001d0b7c64 cookie: 30
file id: 56908316928 name: Old TV Shows name attributes: void name handle: void cookie: 36
file id: 25772617057 name: Pictures name attributes: void name handle: void cookie: 39So the files that show up as "0 B" in kodi have `name attributes: void name handle: void`. I'm not sure why that is happening.
I think that I may have found part of the answer. It may be related to "inode64". Directories with inode values > 64bits don't seem to be exported properly.
2016-03-05, 12:27
its possible libnfs doesn't support 64bit inodes. Can you open an issue at https://github.com/sahlberg/libnfs
edit: is this running on a 32bit kodi build? e.g. android?
edit: is this running on a 32bit kodi build? e.g. android?
2016-03-05, 12:47
This is on an android build running on Fire TV 1. I'm not sure if it's running as 32-bit or 64-bit. It also showed up on Kodi running on 32-bit Linux.
I did end up finding out what happened. In Ubuntu 14.04 and newer, the XFS file system began to default to using the "inode64" mount option. That's why all new directories I created after my upgrade showed up incorrectly.
Given the "nfstrace" information posted above, I feel like the problem is not with Kodi but with the NFS server on linux with a 32-bit kernel. It seems that any directories with an inode number > 32bit limit don't return any attributes, as shown above.
However, I do find it odd that the NFS client in OS X was able to see those directories, so perhaps it is a client issue.
I solved this issue by remounting the filesystem with "inode32" and writing a script to find all my directories with large inodes and recreating them.
I did end up finding out what happened. In Ubuntu 14.04 and newer, the XFS file system began to default to using the "inode64" mount option. That's why all new directories I created after my upgrade showed up incorrectly.
Given the "nfstrace" information posted above, I feel like the problem is not with Kodi but with the NFS server on linux with a 32-bit kernel. It seems that any directories with an inode number > 32bit limit don't return any attributes, as shown above.
However, I do find it odd that the NFS client in OS X was able to see those directories, so perhaps it is a client issue.
I solved this issue by remounting the filesystem with "inode32" and writing a script to find all my directories with large inodes and recreating them.
2016-03-05, 18:29
please post an issue to the link wsnipex provided anyway - ggod finding for sure!
