Sign in to your account. There's an issue here somewhere with lbnfs and Windows Frodo Details: Server Win 7 64 bit running Hanewin nfs server 1. Wireshark trace is full of: 51 0. I don't see other NFS errors as such, but I don't really know what I am looking for in the surrounding frames.
It's most noticeable when running a 'clean library' - basically it fails to find pretty much all files and dumps the whole library.
I was not able to reproduce the errors consistently with a mockup small library, so I am sorry these are large. The text was updated successfully, but these errors were encountered:.
I should add Memphiz had me try libnfs 1. Sorry, something went wrong. I had a look at the big trace but can not see anything obviously wrong. Here we see that the content of this directory consists of :.
So I can not really seen anything wrong from the NFS side. Only errors that I see in the trace are NOENT and seem to be the application trying to access a file that does not exist. On Sun, Jan 19, at AM, adebree notifications github. On Tue, Jan 21, at AM, ronnie sahlberg ronniesahlberg gmail. I am surprised that's happening given the library would contain clear info about the files? Early in the xbmc log it says. I think it goes wrong in the check for directory existence - lines in the xbmc.
Here it is basically 'stat'ting the folders, and immediately after this is does a mass delete from the mysql database. I weirdly can't seem to find the corresponding 'exists' calls for just the parent dirs in the wireshark. Maybe it's using the references from way back early when it mounts the share?? Memphiz - does that give any clues at all? No it doesn't - Video Scanning is Magic for me. Beside that i didn't See any nfs errors in that log yesterday can't look again - Only on the phone atm.
There aren't any nfs errors as such in the xbmc log - but the nfs calls behind it seem to be at issue. I suppose it not impossible it's not nfs at all, but a more general library update issue with frodo Memphiz - same issue. Actually, I'd say worse.
The entire library is dropped, except things I have as. So it seems the stat is actually even worse :. The remaining. I'll repeat what I posted in the forum for anyone following along: A thought occurred to me. Does windows cache DLLs? I just tried installng Gotham nightly from 29th Jan, copying the libnfs. I then rebooted and tried with libnfs-master that you linked to above - boom, whole lot dropped again. Put back So: libnfs 1. Manually reverting to libnfs 1. I know the first Gotham beta is sort of imminent - is there anything I can do to help with this somehow - any testing or tracing?
I understand you may simply not have time of course. Just if there is anything I can do, I would :. It appears to be the stat process not finding directories that then causes the mass delete from the library.
When setting up a testbed environment on just one machine, I have not been able to trigger the problem consistently indeed I have only seen it once. So - I am wondering if there are possible timeout issues at play here? Thus the difference in results between the testbed one machine and the wireless connection used on my laptop.
Note that Frodo I had a look at the commits between 1. The testbed is of course a much simpler environment basically, vastly less files but same general structure - than my working environment, so it may well be some other issue, just an idea. But, from what I can read on google, stat is pretty hairy on windows and it appears that there are huge numbers of different varients on windows.
The problem appears to be that libnfs and xbmc are compiled with a different view of what exactly 'struct stat' is and the ABI between them thus becomes broken As I said, I do not have access to windows compilers so I can not test much. What I can do however is provide new functions to libnfs which provides a special stat structure where everything is 64 bit clean. This should provide a stable ABI for the new 'special stat' function but with the drawback that any applications that use it, like xbmc, will have to manually copy the fields one by one from the 'special stat' structure that libnfs exposes onto the, whatever, weird, stat structure that the build uses.
Providing this 'special, everything is 64bit, no matter what' ABI is the only thing I can do. The cachemembuffersize is set to the default 5MB so you will still need to update that after pasting it in. After you have updated the advancedsettings. When streaming videos over the network my XBMC log would frequently throw an error saying:.
As it turns out my biggest performance problem was an issue with drivers. The drivers that were ultimately causing issues with my setup were the LAN drivers. I was using the drivers recommended by ASRock, my motherboard manufacturer, when in reality I should have turned to the manufacturer of the network card… Realtek. I jumped over to the Realtek site only to see that the network drivers ASRock were dishing out on their site were over a year old.
The XBMC forums might be a better location to reach out though since many of the developers are also active in the forums. Hotkeys to change subtitles font size. Subtitles font size setting only works for some videos. Kodi not recovering properly from lid close. Segfault when hitting a specific scene with HEVC vaapi decode enabled.
Videos Enter Hyperspeed after Buffer Empties. Dolby Vision files are not recognized if embed in a mkv container. DVD Menu not highlighted. Kodi DVB subtitles position. Speeded up audio playback after boot.
0コメント