Disk space is a recurring issue

[Schtele Bunzorz]

Which client? As I posted the web player takes double the space and that space is the same drive as the data directory not the recording.

Martin

Also, I appreciate your assistance. I know you have contributed much to this community. I'm not ignorant of your contributions.

[mvallevand]

If you are going to localhost you are using the web client so double the space and account for browser cache too. Five files is correct, a map file and up to 4 files. I think you you will find 1080i ATSC is more than 600MB a half hour but your 1 minute.

If a client crashes perhaps because of disk full conditions the cleanup is when the server restarts. Free up more space if you want a better experience.

Martin

[gEd]

Yes, I should have more space available.  But when I don't, I have these issues.
yep. I work with a number of enterprise-grade software products (used by some of the largest companies in the world) that don't play nice when they are unable to write to disk (similar to what can happen when that are unable to allocate memory).

I know not everyone is made of money but storage has never been so cheap. Personally, I'd rather Sub (the developer) spent his time on other things (including the work he has to do to put food on the table when not working on this project).

Put food on the table.  But the same product is sold commercially, so I kind of think I am helping Sub by posting feedback and being willing to offer further feedback.  I mean, I can't just say this is broke fix it.  I have the perfect environment for gathering more information.

The service should not have to be restarted.  I think we can all agree on that.  If I get a disk space alert and swap out a disk, should the service have crashed?

For Sub's commercial version of nextpvr (of which I know absolutely nothing) then perhaps he (and whatever partner he is working with) would need to properly handle a zero free disk scenario in whatever turnkey systems are being sold with embedded nextpvr. It's up to Sub to decide if that something he needs to spend time on.

However I would suggest that this use case is not within the scope of the home users of this forum for whom that problem can easily be resolved by buying 500GB of SSD storage for $30.

[sub]

On the commercial front, we've had a few very small deals over the years, which help subsidise the project, but nothing with any serious money (and nothing in a few years). At the end of the day, I have to work a full time job, and NextPVR is just a hobby I work on in my spare time.

"Live TV is already a ring buffer "

I have no evidence of that. It records to a single file until disk space is exhausted, then hangs. When I F5/refresh, disk space by the previous session is cleared. Live TV continues, with no other issue than having had a full disk. I will ask you to explain your answer in more detail.

As the guys have pointed out, it does use a ring buffer, so doesn't consume endless disk when watching live tv. It's a system based on time, not available disk space. It uses a rolling set of four files, deleting the oldest as it creates the newest file.

Yes, it would be nice if it didn't crash if you ran out of disk space, but I focused on what I considered priority, and unfortunately this is never made it to the top of the priority list. Maybe someday it'll find time to focus on this aspect. For now you'll just need to try to have enough disk space available.

[Schtele Bunzorz]

[quote pid="601542" dateline="1749854290"]
However I would suggest that this use case is not within the scope of the home users of this forum for whom that problem can easily be resolved by buying 500GB of SSD storage for $30.
[/quote]

I would argue that it is still a software issue, if I manage to fill up 500GB and it fails.  It's just not a quality product if it fails, without warning, on writing the files it needs to replay.

To hang the service, which must be restarted, is an utter failure.  Leaving the NextPVR backend status still displaying "recording" something that ended more than 24 hours ago is beyond failure.

Sub has weighed in, but I felt it necessary to reply to this statement in particular.

[Schtele Bunzorz]

Data is written to:
C:\Users\Public\NPVR-data\web\temp\[Channel] 93b7321aa98e4430a60101928a6e60eb17.ts)

I do not want that to happen.
1) Is this documented?
2) Other than changing the Public profile location, how do I change or disable that?

I have a pre-configured SSD with the system disk (C having a limited amount of space. It was probably good when I bought it.

But, I do not want temp writes on my SSD. That's why I have a Live-Buffer established elsewhere. I did not expect these writes to be done at all, let alone have them accumulate.

Any feedback?

[sub]

Data is written to:
C:\Users\Public\NPVR-data\web\temp\[Channel] 93b7321aa98e4430a60101928a6e60eb17.ts)

I do not want that to happen.
1) Is this documented?
2) Other than changing the Public profile location, how do I change or disable that?

I have a pre-configured SSD with the system disk (C having a limited amount of space. It was probably good when I bought it.

But, I do not want temp writes on my SSD. That's why I have a Live-Buffer established elsewhere. I did not expect these writes to be done at all, let alone have them accumulate.

Any feedback?

These HLS streaming files are only written to this directory if you're watching in the web app. If you use a client that does native streaming, then those web\temp\ files are not created.

[mvallevand]

It isn't well documented, documentation is a user responsibility feel free to amend the wiki. You can create a junction on the web folder fo another drive.

Martin