Recordings Stop at 2GB

[zed]

I'm having a problem with recordings being truncated at a specific length. They all stop at the same file length...2147483647 bytes...2GB. Nextpvr shows them as recording past that size but the files don't get any longer. When played back, when it reaches the end of the file the playback jumps back to the beginning and restarts. Anything shorter works fine. Looks to me like there's a 2.0 GB limit set somewhere but I can't find where.

I'm running version 5.0.1.200211 on a Raspberry Pi 4 running Ubuntu 19.04 server and recording onto an external USB 3.0 hard drive formatted as ext4 but the issue was also there on the previous nextpvr version(s).

Probably something dumb but I can't see what it is. Any suggestions will be appreciated.

[sub]

I'm not aware of any NextPVR issue that could cause this. I would have guessed you were using some FAT filesystem, and it was the max file size.

Maybe try a command like the following to see if you can create a 8GB file on that disk

Code:

dd if=/dev/zero of=/path/file.txt count=8096 bs=1048576

[zed]

Thanks for the reply, sub.

Creating an 8GB file on the recordings disk works just fine.

I spent a lot of time today googling and trying a lot of things including updating the OS, all to no avail. At this point I don't know what else to do.

I wonder if it's some weird interaction between ubuntu, dotnet, raspberry pi hardware, and maybe the drivers for the WinTV tuner?

[sub]

What tuner are you using?

[sub]

Is the linux distribution a 64bit or 32bit version?

https://stackoverflow.com/questions/7307...write-in-c

[zed]

Tuner is the Hauppauge WinTV-dualHD TV Tuner.

Hmmm....it appears that it's running 32 bit OS.

$ getconf LONG_BIT
32

I guess that might have something to do with it...

I thought it was the 64 bit version but apparently not. The Pi 4 is supposed to be able to run 64 bit Linux and I thought that that was what I installed (Ubuntu 19.10)...I'll have to check into that.

Thanks for the pointers...

[sub]

From what I've read, it is related to this, but I'm going to have to fix it in my arm32 version of the DeviceHostLinux code. It's not a big change, but I wasn't aware this was an issue with Linux.

[sub]

I haven't tried it, but this updated DeviceHostLinux should do the job. If you are able to confirm it for me, that’d be great. Replace your existing file of the same name in ./DeviceHost/arm32

[zed]

Sub...



Good news & bad news...




I replaced the file and I was able to record past 2GB.




However, I'm seeing failures where something errors and the system unmounts the external drive that holds the recordings.




I'll attach a couple sets of logs. The first set (in logs) I started a recording. It ran for a a while and then the failure occurred.




In the logs2 set I was able to record a > 2GB file and then scheduled a couple more recordings but when I came back to check on it, it had unmounted the drive, not sure at what point it happened.




I think the first set is cleaner...I did a server restart then started a recording and the problem happened right away.




I included the syslog also in case that would be helpful.




Let me know if you need anything more from me that would be helpful.




Thanks for following up on this so quickly.

[sub]

However, I'm seeing failures where something errors and the system unmounts the external drive that holds the recordings.

Hmm, that doesn't sound like the sort of thing an application should be able to cause.