"WRITE ERROR on recording, disk full?"

[birdman]

zipped
Attachment 46821

This line might mean something (although it is almost 4 mins earlier, the I/O is asynchronous). Need to check whether the other logs show the same (EDIT - no they don't...):

< 27430.899961> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 90(16)

And 90 file-descriptors sounds like a lot of open files - but possibly not....

[rassi]

This line might mean something (although it is almost 4 mins earlier, the I/O is asynchronous). Need to check whether the other logs show the same (EDIT - no they don't...):

< 27430.899961> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 90(16)

And 90 file-descriptors sounds like a lot of open files - but possibly not....

For me that line wont say anything
I´ll try to see do I still have full logs from earlier issues, when posted only partials.

[ymeknassi]

I'm actuammu using a network hdd. Lacie cloudbox. It's very limited in term of flexibility: I cannot change filesystem or share type or anything. My only option is windows samba share. I'll never buy this brand again BTW. I'm an open source lover :-)
I dont' have any simultaneous recordings or double processing running during the recording. Also, I tried blackhole is the only image where the issue doesn't occur. It happens is openvix, openpli and openatv exatcly the same way: at the same file size

Sent from my E5823 using Tapatalk

[rassi]

Now i´ve completely changed whole infra and issue still on.
NFS server changed, switches changed, Enigma2 box changed and still OpenViX/OpenPli variant causes Disk full error.
Vu+ DUO with Blackhole never had issues. Currently using LX3 with gbit. Newest logs attached.


Enigma2-2016-03-01_14-18-19.zip

[birdman]

Newest logs attached.


Enigma2-2016-03-01_14-18-19.zip

That one is different. It looks like the network writing was too slow and it ran out of local buffers to put the recording data in.

[rassi]

That one is different. It looks like the network writing was too slow and it ran out of local buffers to put the recording data in.

Thanks. Yes it seem that NFS performce is currently VERY poor on my gbit network from Xpeed LX3. Now i need to figure, why
It´s been MUCH faster, almost what you just can throw over the gbit ethernet.
No issues transfer from other HW to the same servers.

root@xpeedlx3:~# dd if=/dev/zero of=/media/tmp/testfile2 bs=512k count=1000
1000+0 records in
1000+0 records out
524288000 bytes (500.0MB) copied, 53.080058 seconds, 9.4MB/s

root@xpeedlx3:/# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 4
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: ags
        Wake-on: d
        SecureOn password: 00:00:00:00:00:00
        Link detected: yes

Mount:

192.168.1.2:/mnt/tallenteet on /media/hdd type nfs (rw,relatime,vers=3,rsize=16384,wsize=16384,namlen=255,soft,nolock,proto=tcp,timeo=14,retrans=2,sec=sys,mountaddr=192.168.1.2,mountvers=3,mountproto=tcp,local_lock=all,addr=192.168.1.2)

fstab.
async is set, but it seem to not using it.. trying it to two different server, first ZFS RAIDZ and second RAID5. Both running Ubuntu.

192.168.1.2:/mnt/tallenteet     /media/hdd      nfs     _netdev,rw,nolock,tcp,async,nfsvers=3,rsize=16384,wsize=16384,timeo=14,soft     0 0
192.168.1.6:/mnt/video     /media/tmp      nfs     _netdev,rw,nolock,tcp,async,nfsvers=3,rsize=32768,wsize=32768,timeo=14,soft      0 0

exports are equal on both servers. except path.

/mnt/tallenteet 192.168.1.0/24(rw,no_root_squash,no_subtree_check,async)

[rassi]

Back on track. Bad connector on network. Now need to wait new "Write errors"

root@xpeedlx3:~# dd if=/dev/zero of=/media/hdd/testfile2231 bs=512k count=1000
1000+0 records in
1000+0 records out
524288000 bytes (500.0MB) copied, 10.616792 seconds, 47.1MB/s