DefaultDirectoryChoice spread not working

[Lanhydrock]

Running version 5.1.0.201216 of NextPVR on Linux Mint 20.1
2 recording directories setup via WebGUI.

/var/opt/nextpvr/config.xml includes

Code:

<RecordingDirectory>/media/psf/NextPVR/</RecordingDirectory>
<ExtraRecordingDirectories>NextPVRext256GB~/media/psf/NextPVRext256GB/~</ExtraRecordingDirectories>
<RecordingDirectoryTranslation>d:\temp~\\someserver\someshare</RecordingDirectoryTranslation>
<LiveTVBufferDirectory>/media/psf/NextPVRext256GB/</LiveTVBufferDirectory>

<DefaultDirectoryChoice>spread</DefaultDirectoryChoice>

Still, spreading doesn't work.

We open the TVGuide and select any program. 
We click on Record Once without specifying any advanced options.

Although /media/psf/NextPVRext256GB has 256GB of free space and /media/psf/NextPVR only 100GB, the system records to the default directory on /media/psf/NextPVR.

We select /media/psf/NextPVRext256GB in the advanced options and it does record to the other location.

Is spreading working for anybody, please? Are we missing something? - Thanks a lot.

[EDIT]

With Extended Logging set to on we even get:

Code:

2021-03-13 15:54:09.242 [DEBUG][6] Checking disk space for: /media/psf/NextPVRext256GB/
2021-03-13 15:54:09.242 [DEBUG][15] Available Space:
2021-03-13 15:54:09.242 [DEBUG][15] (Default) - 499963174912/98969874432
2021-03-13 15:54:09.242 [DEBUG][15] (NextPVRext256GB) - 249849593856/249711009792
2021-03-13 15:54:09.242 [DEBUG][15] [{"name":"Default","total":499963174912,"free":98969874432},{"name":"NextPVRext256GB","total":249849593856,"free":249711009792}]

and

Code:

2021-03-13 15:54:30.822 [DEBUG][9] DefaultDirectoryChoiceext: spread

Strangely, with Extended Logging set to off, the log reads:

Code:

2021-03-13 15:56:30.522 [DEBUG][9] DefaultDirectoryChoice: spread

Note the missing ext in DefaultDirectoryChoice.

[mvallevand]

Since it works on Windows I suspect it is a linux limitation that sub needs to look at.

Martin

[sub]

This logic was limited to Windows because it relied on a Windows apis to get the available disk space on different types of volumes. I've implemented the equivalent logic for Linux in the next build.

[Lanhydrock]

Thank you very much for implementing the feature for Linux/Mac in v5.1.1.210329. 

We cleaned up a lot of space when we first run into the issue in March, so somehow couldn't/didn't follow-up very closely. Apologies, sub... -

Last week we moved NextPVR to a new computer and are of the impression that it (sometimes?) still doesn't work as we expect it to:

Now running version 5.2.2.211017 of NextPVR on Ubuntu Server 20.04.3 LTS.
2 recording directories setup via WebGUI.

/var/opt/nextpvr/config.xml includes

Code:

<RecordingDirectory>/media/nextpvr/</RecordingDirectory>

Code:

<ExtraRecordingDirectories>usbext-256gb~/media/usbext/256gb/nextpvr/~</ExtraRecordingDirectories>

Code:

<DefaultDirectoryChoice>spread</DefaultDirectoryChoice>

We searched for a text in the WebGUI where we knew that something could be found that was live at that time: (BBC2) "do in the shadows".

We selected the first entry in the list of episodes and selected RECORD ONCE, more specifically didn't change anything in ADVANCED for example.

The log states: 

Code:

2021-11-02 23:04:40.301 [DEBUG][6] Checking disk space for: /media/nextpvr/
2021-11-02 23:04:40.307 [DEBUG][4] Got request [10.10.10.251]: /service (session.valid)
2021-11-02 23:04:40.308 [DEBUG][13] Checking disk space for: /media/usbext/256gb/nextpvr/
2021-11-02 23:04:40.308 [DEBUG][6] Available Space:
2021-11-02 23:04:40.308 [DEBUG][6] (Default) - 421682126848/126408105984
2021-11-02 23:04:40.308 [DEBUG][6] (usbext-256gb) - 245058273280/232475635712
2021-11-02 23:04:40.308 [DEBUG][6] [{"name":"Default","total":421682126848,"free":126408105984},{"name":"usbext-256gb","total":245058273280,"free":232475635712}]

Still, NextPVR choses the Default directory, not the one which (in relation and absolute) has the most free space available.

Code:

2021-11-02 23:05:34.290 [DEBUG][9] DefaultDirectoryChoice: spread
2021-11-02 23:05:34.291 [DEBUG][9] Preferred filename is 'What.We.Do.in.the.Shadows.S03E01.The.Prisoner'
2021-11-02 23:05:34.295 [DEBUG][9] allocating recording target filename: /media/nextpvr/What We Do in the Shadows/Season 03/What.We.Do.in.the.Shadows.S03E01.The.Prisoner.ts
2021-11-02 23:05:34.295 [DEBUG][9] About to start recording (1226 on 24): /media/nextpvr/What We Do in the Shadows/Season 03/What.We.Do.in.the.Shadows.S03E01.The.Prisoner.ts...
2021-11-02 23:05:34.295 [DEBUG][9] (Recording is due to be stopped at 11/2/2021 11:30 PM)
2021-11-02 23:05:34.299 [DEBUG][9] RTSP input source starting
2021-11-02 23:05:34.304 [DEBUG][9] Creating writer: /media/nextpvr/What We Do in the Shadows/Season 03/What.We.Do.in.the.Shadows.S03E01.The.Prisoner.ts
2021-11-02 23:05:34.306 [DEBUG][9] Created Mutex: Global\NPVR-mutex-b3dc3a3ebd393c0f3dbc666e7ed1b862
2021-11-02 23:05:34.307 [DEBUG][9] Created map: /media/nextpvr/What We Do in the Shadows/Season 03/What.We.Do.in.the.Shadows.S03E01.The.Prisoner.ts.map
2021-11-02 23:05:34.312 [DEBUG][9] StartStream [/media/nextpvr/What We Do in the Shadows/Season 03/What.We.Do.in.the.Shadows.S03E01.The.Prisoner.ts] allocated handle: 1
2021-11-02 23:05:34.312 [DEBUG][9] Started recording (1226:1:/media/nextpvr/What We Do in the Shadows/Season 03/What.We.Do.in.the.Shadows.S03E01.The.Prisoner.ts)

Thanks a lot for checking why that is...

[mvallevand]

I wouldn't expect any difference

/media = /media

On the startup page http:/10.10.10.5:8866/index.html they likely show the same available storage

Martin

[Lanhydrock]

Thank you for your time, Martin.

The startup page lists the same values as the log:

Code:

2021-11-02 23:04:40.308 [DEBUG][6] Available Space:
2021-11-02 23:04:40.308 [DEBUG][6] (Default) - 421682126848/126408105984
2021-11-02 23:04:40.308 [DEBUG][6] (usbext-256gb) - 245058273280/232475635712

We followed your advice and changed the location of the Linux mount from /media/usbext/256gb to /media2/usbext/256gb; still NextPVR records to the default directory.

[mvallevand]

Sorry I must have searched in someone elses logs. Sub will need to investigate I know there are folder nuances on linux (ie archiving) that are being looked at fort the next release.

Martin

[sub]

I can see why that happened. Fixed for the next build.