Empty files when writing to samba share

[aimaim]

Hi there,

I'm running NextPVR on Pi OS. Recording to a local usb thumb drive works, yet recording to my NAS' smb-share doesn't.

The folder 'Manual Recordings' as well as a ts- and a ts.map-file are created on the smb-share, yet the files have 0 bytes.
(I started the test recording for the attached log at 20:34:
  logs.zip (Size: 101.56 KB / Downloads: 2) )
(When I switch user to nextpvr in the pi's shell, writing to the share mounted to '/home/nextpvr/shares/nas/' works flawlessly.)

When I try and play the running recording from the webif it doesn't work, since there hasn't been anything recorded. But trying to play the non existant recording somehow triggers it to actually start recording.
(20:37 in the log)

Then I cancelled the recording. (20:38 in the log)

Excerpt from the pi's '/etc/fstab':

Code:

#for nextpvr
/dev/sda1      /home/nextpvr/shares/flashdrive    exfat noauto,x-systemd.automount,x-systemd.idle-timeout=60,defaults,users,uid=nextpvr,gid=video 0 0
//192.168.187.143/stuff /home/nextpvr/shares/nas cifs noauto,defaults,username=***,password=***,uid=nextpvr,gid=video,x-systemd.automount,x-systemd.requires=network-online.ta>

Excerpt from the pi's shell:

Code:

nextpvr@raspberrypi:~$ cd /home/nextpvr/
nextpvr@raspberrypi:~$ ls -lt
drwxr-xr-x 4 nextpvr nextpvr 4096  5. Jul 18:56 shares
nextpvr@raspberrypi:~$ ls -lt shares/
drwxr-xr-x 3 nextpvr video 131072  5. Jul 22:58 flashdrive
drwxr-xr-x 2 nextpvr video      0 25. Jun 07:35 nas
nextpvr@raspberrypi:~$ ls -lt shares/nas/downloads/
drwxr-xr-x 2 nextpvr video      0  5. Jul 22:11 'Manual Recordings'
nextpvr@raspberrypi:~$ ls -lt shares/nas/downloads/Manual\ Recordings/
-rwxr-xr-x 1 nextpvr video        0  5. Jul 22:38 'DE - SKY SPORT 1 4K_20220705_22342334.xml'
-rwxr-xr-x 1 nextpvr video 40036820  5. Jul 22:11 'DE - SKY SPORT 1 4K_20220705_22342334.ts'

Please disregard
  nrecord.zip (Size: 31.01 KB / Downloads: 1) . Somehow I couldn't successfully delete it. It does not contain the entire test case.

[mvallevand]

First mounting shares in /home seems like you are asking for trouble with permission conflicts.

For the deb installer I have never tested for users who decide to create /home/nextpvr

I don't understand the noauto option you are using which will force you to mount the drive manually something you normally don't do with a PVR.

You specify a uid=nextpvr in fstab but does your server even support that uid?

Check dmesg for mount issues

Run getfacl on each folder

getfacl /home/nextpvr -R

Martin

[aimaim]

Why would mounting shares in /home/... be a problem? Works for my tvheadend recording directory exactly like that.
I'm in bed already. Tomorrow I'll try and use /media/... But I'd be suprised if that made a difference.

The noauto option in combination with x-systemd.automount causes the share to be mounted, when it is accessed for the first time, instead of on boot. This is just a precaution to have the system boot without problems, should the share ever not be available.

The option 'uid=nextpvr' is client side. The user does not need to exist on the server side. The user on the server side is determined by the login given.

I'll try your other suggestions tomorrow, yet I don't think there's a mounting or permission issue. After all manually writing to the share as nextpvr does work.

[mvallevand]

I didn't see using /home was a problem, just bad form and you must create things appropriately.

As I said this is not a NextPVR problem but good luck tomorrow. It now sure sounds like it is related to your automount choices.

Martin