{"action":"created","issue":{"url":"https://api.github.com/repos/sahlberg/libnfs/issues/257","repository_url":"https://api.github.com/repos/sahlberg/libnfs","labels_url":"https://api.github.com/repos/sahlberg/libnfs/issues/257/labels{/name}","comments_url":"https://api.github.com/repos/sahlberg/libnfs/issues/257/comments","events_url":"https://api.github.com/repos/sahlberg/libnfs/issues/257/events","html_url":"https://github.com/sahlberg/libnfs/issues/257","id":329113129,"node_id":"MDU6SXNzdWUzMjkxMTMxMjk=","number":257,"title":"[kodi] New files inaccessible until reboot - Overzealous file/directory caching?","user":{"login":"aphirst","id":1735556,"node_id":"MDQ6VXNlcjE3MzU1NTY=","avatar_url":"https://avatars3.githubusercontent.com/u/1735556?v=4","gravatar_id":"","url":"https://api.github.com/users/aphirst","html_url":"https://github.com/aphirst","followers_url":"https://api.github.com/users/aphirst/followers","following_url":"https://api.github.com/users/aphirst/following{/other_user}","gists_url":"https://api.github.com/users/aphirst/gists{/gist_id}","starred_url":"https://api.github.com/users/aphirst/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aphirst/subscriptions","organizations_url":"https://api.github.com/users/aphirst/orgs","repos_url":"https://api.github.com/users/aphirst/repos","events_url":"https://api.github.com/users/aphirst/events{/privacy}","received_events_url":"https://api.github.com/users/aphirst/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-06-04T15:47:04Z","updated_at":"2018-06-18T04:30:45Z","closed_at":null,"author_association":"NONE","body":"I recently made a post on the Kodi forums about a bug I've been experiencing with files I host on my NFS server.\r\n\r\n[Kodi Forums - Newly added files in previously-accessed directories inaccessible until reboot](https://forum.kodi.tv/showthread.php?tid=332282)\r\n\r\n> I have Kodi+Libreelec on an ODROID-C2, I have my NFS server and my Kodi Database on an ODROID-XU4 (running Arch Linux ARM), and I have another Kodi instance (also set up to use the database) on my laptop. I use the laptop Kodi instance to do my rescanning and database related stuff. All devices are running Kodi 17.\r\n>\r\n>Steps to reproduce:\r\n>1. On the ODROID-C2, play a random episode from [current season] of [show] (optionally: immediately stop playback), and keep the menu in the [current season]'s listing\r\n>2. add [new episode] to [current season]'s folder of [show] on the NFS storage (via the laptop, or some other machine on the LAN)\r\n>3. on the laptop, open Kodi and run \"Update Library\"\r\n>4. on the ODROID-C2, go \"back\" from the [current season] view to the list of seasons, then back into [current season]\r\n>5. attempt to \"play\" the newly added episode entry\r\n>6. receive \"This file is no longer available\" error, despite the file definitely actually being present on the server (if you press \"i\", on my skin at least, the correct full path for the file is displayed)\r\n\r\nKodi uses libnfs for its NFS support. As I detail in the thread, my suspicion is that libnfs is caching the files it sees in a given folder on the first access it makes, but then refuses to ever update the entries in that cache, even when new files have been added to the folder, and when the Kodi database now contains entries pointing to these new files.\r\n\r\nI was suggested to open a bug here on the libnfs tracker.\r\n\r\nIf there's any further info I can provide, please do not hesitate to ask."},"comment":{"url":"https://api.github.com/repos/sahlberg/libnfs/issues/comments/397939318","html_url":"https://github.com/sahlberg/libnfs/issues/257#issuecomment-397939318","issue_url":"https://api.github.com/repos/sahlberg/libnfs/issues/257","id":397939318,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NzkzOTMxOA==","user":{"login":"sahlberg","id":494992,"node_id":"MDQ6VXNlcjQ5NDk5Mg==","avatar_url":"https://avatars3.githubusercontent.com/u/494992?v=4","gravatar_id":"","url":"https://api.github.com/users/sahlberg","html_url":"https://github.com/sahlberg","followers_url":"https://api.github.com/users/sahlberg/followers","following_url":"https://api.github.com/users/sahlberg/following{/other_user}","gists_url":"https://api.github.com/users/sahlberg/gists{/gist_id}","starred_url":"https://api.github.com/users/sahlberg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sahlberg/subscriptions","organizations_url":"https://api.github.com/users/sahlberg/orgs","repos_url":"https://api.github.com/users/sahlberg/repos","events_url":"https://api.github.com/users/sahlberg/events{/privacy}","received_events_url":"https://api.github.com/users/sahlberg/received_events","type":"User","site_admin":false},"created_at":"2018-06-18T04:30:45Z","updated_at":"2018-06-18T04:30:45Z","author_association":"OWNER","body":"UUID=386cb49b-6b69-41bd-ab8c-111af6cb0fd1 /mnt/Odin xfs defaults,nofail,relatime 0 2\r\n-snip-\r\n/mnt/Odin /srv/nfs/Odin none bind,nofail 0 2\r\n\r\nYou are accessing the files via /srv/nfs/Odin which is a bind mount.  That should not make any difference but could you see if this effect also show up if you access via the real mountpoint  /mnt/Odin  ?\r\n"}}
{"actor":{"display_login":"sahlberg"}}