"WRITE ERROR on recording, disk full?"

[ymeknassi]

Dears, I'm using Openvix on Vu+ Solo 2, with external network HDD using ntfs and I'm getting same errors. Any idea? I don't want to get back to BH, I didn't have this issue before

Moderator EDIT:
Posts moved from this thread.
http://www.world-of-satellite.com/showthread.php?21029-quot-WRITE-ERROR-on-recording-disk-full-quot-messages-now-and-then

[ymeknassi]

Dears, I'm using Openvix on Vu+ Solo 2, with external network HDD using ntfs and I'm getting same errors. Any idea? I don't want to get back to BH, I didn't have this issue before
Dears, have started from fresh installationonce again. I'm using cifs mount using autofs. Network drive not mounted as HDD but it's target location for recording. No tspanel. Any ideas?

Sent from my E5823 using Tapatalk

[ymeknassi]

Dears, have started from fresh installationonce again. I'm using cifs mount using autofs. Network drive not mounted as HDD but it's target location for recording. No tspanel. Any ideas?

Sent from my E5823 using Tapatalk
One last update, I have redone a fresh install. Removed all mount points except the network drive that I use now as HDD using autofs cifs mount. No plugin I installed manually except mediaplayer2 and subssupport. Still, the issue is there. Any help please?

Sent from my E5823 using Tapatalk

[abu baniaz]

Vix image does not have ntfs drivers in base image. You have to install them first if you want to use a hdd in ntfs file system.

If you are using a network mount, you must have write permissions.

[ymeknassi]

Vix image does not have ntfs drivers in base image. You have to install them first if you want to use a hdd in ntfs file system.

If you are using a network mount, you must have write permissions.
Hi,

I actually use cifs nerwork mount. The recording actually starts but stops after a random time wity disk full error. I'm connected directly to the network drive using ethernet cable. And it stops after a random amount of time or size recorded. Any idea?


Sent from my E5823 using Tapatalk

[birdman]

And it stops after a random amount of time or size recorded. Any idea?Quotas set on the CIFS file server?

[ymeknassi]

Quotas set on the CIFS file server?
It's a LaCie cloudbox and there are no such options on it. On Top, I am.able to manually start another record which also behave the same after some time...

Sent from my E5823 using Tapatalk

[ymeknassi]

http://images.tapatalk-cdn.com/15/11/26/738e543dc95f052a8e343a296417794f.jpg

Not really random after all. Look at the recordings I have made. First and second ones are from blackhole (no issue recording behaved as expected). The next ones are all from openvix. Look at the first 7 ones. Exactly same size. I'm back to bh today to make checks. Checking also using openatv

Sent from my E5823 using Tapatalk

[birdman]

First and second ones are from blackhole (no issue recording behaved as expected). The next ones are all from openvix. Look at the first 7 ones. Exactly same size. Which look suspiciously like and issue around 32-bit integer file sizes (2**31/19024 is 2097152).

[ymeknassi]

I agree it's suspicious. I'm trying again using blackhole. Had same issue with openatv. I'll confirm in a while if it's an image issue or something else after all

Sent from my E5823 using Tapatalk

[ymeknassi]

Hey guys. I confirm it's an image related issue so far. Installed back blackhole and can do indefinite recording (I tries up to 24Gb). Back to Openvix now, I have the same issue again. Note the issue also occured on OpenATV. I'm doing last tries using different mount options. But I think it does't work on all OE-alliance based images... that's unfortunate! vix team, can you investigate on it? Need any logs?

[abu baniaz]

Debug logs would be great. Thanks.

[birdman]

Hey guys. I confirm it's an image related issue so far.Which is a little odd. Clearly OpenVix can handle files larger than this, and it shouldn't be concerned as to the type of file-system which is being used to store a recording.
So that would leave the problem with the kernel cifs module - which i'd expect to be the same for the different images (as it's part of the kernel).

[abu baniaz]

......So that would leave the problem with the kernel cifs module - which i'd expect to be the same for the different images (as it's part of the kernel).

Not always the same and changes as and when provided by manufacturer. Hopefully OP can confirm kernel versions.

[ymeknassi]

Not always the same and changes as and when provided by manufacturer. Hopefully OP can confirm kernel versions.
I'm building the log... Will post in a while

Sent from my E5823 using Tapatalk

[ymeknassi]

Here is the log guys. What think?
45962

Thank you

[abu baniaz]

Can you post what the kernel versions in the images you have tried please.
Menu > Information > About

[ymeknassi]

Open Vix is : 3.13.5. I used Blackhole 3.0.1 today for the recording, I think it's same kernel

[abu baniaz]

Please confirm it. Both images allow you to backub and restore, so hopefully will not be an issue for you.There is an entry on line 1050 of your log about disk being full. One of the coders will have a look at it later.

P.S
I will be moving your posts to their own thread.

[ymeknassi]

Ok, thank you

Sent from my E5823 using Tapatalk

[bbbuk]

I don't think it would be a kernel issue (3.13.5 is current kernel for solo2 btw) and both Vix/ATV and BH use this version of kernel.

Could it be ntfs you use to write to the network drive. Maybe different ntfs versions in use with BH 3.0.1 and OpenVix/OpenATV or even a issue with ntfs and OE-A core images?

[ymeknassi]

It's same kernel used in both. I confirm

Sent from my E5823 using Tapatalk

[birdman]

Not always the same and changes as and when provided by manufacturer. I'd be surprised if the cifs support in any kernel version suddenly failed to handle Large Files (> 2**31 bytes) - it's not a configurable option.

FWIW - I've just set up Samba on a system near my box, added a cifs mount on the box and copied a recording over it.

On my MBTwin

root@mbtwin:/media/autofs/SMBtest# cp /media/hdd/movie/Films/20150623\ 2057\ -\ Film4\ -\ Transformers_\ Revenge\ of\ the___.ts .
root@mbtwin:/media/autofs/SMBtest# md5sum /media/hdd/movie/Films/20150623\ 2057\ -\ Film4\ -\ Transformers_\ Revenge\ of\ the___.ts
c5c10eb531262b4652dafe2d32b61b73 /media/hdd/movie/Films/20150623 2057 - Film4 - Transformers_ Revenge of the___.ts

On the Samba system:

plug-root:/extra/SMBtest# ls -l
total 3902876
-rw-r--r-- 1 myapps myapps 3996540096 Nov 30 01:04 20150623 2057 - Film4 - Transformers_ Revenge of the___.ts
plug-root:/extra/SMBtest# md5sum 20150623\ 2057\ -\ Film4\ -\ Transformers_\ Revenge\ of\ the___.ts
c5c10eb531262b4652dafe2d32b61b73 20150623 2057 - Film4 - Transformers_ Revenge of the___.ts


so that can handle Large Files OK.

[birdman]

Could it be ntfs you use to write to the network drive. Maybe different ntfs versions in use with BH 3.0.1 and OpenVix/OpenATV or even a issue with ntfs and OE-A core images?ntfs isn't a network file-system protocol - it's only used to write to directly-connected storage.

A network drive would use cifs or NFS.

[birdman]

Here is the log guys. What think?
45962

Thank youIt seems to be complaining about an Interrupted System Call. Always a bit of a pain, and this is in asynchronous I/O code....


http://www.python4science.eu/aio.html seems to offer some comments on this: the aio_suspend section specifically mentions the issue and offers this as a way around it:


Or, let a signal interrupt aio_suspend and just call aio_error for each element of the list you pass to aio_suspend when it returns to see what, if anything, happened, and reissue the aio_suspend (perhaps in a loop) if nothing did.



Mind you, this may not be anything to do with it - it's difficult to think why this would only occur for cifs mount around the 2GB barrier.

[birdman]

There is a difference in the demux.cpp code between OpenVix and BlackHole.

OpenVix uses more buffers on systems with 1024MB of RAM - which (according to a rare comment) includes the Vusolo2 and vuduo2.

(Well, that's what the comments say - the actual code seem to do this for >400MB - the "if (megabytes > 400)" being a clue).

[edogg]

I have a similar problem in that recordings that are set to record for 1 hour stop with disk write error disk full ? . There I'd plenty of space left on the drive . 3.02.24

Sent from my Blade S6 using Tapatalk

[abu baniaz]

@ymeknassi
Did you try with installing the ntfs-3g drivers in the plugin menu? If not, please try doing that.

Thanks.

[birdman]

@ymeknassi
Did you try with installing the ntfs-3g drivers in the plugin menu? If not, please try doing that.

Thanks.He's using a CIFS network mount (see #5). NTFS (on the Enigma2 box) isn't involved.

[birdman]

I have a similar problem in that recordings that are set to record for 1 hour stop with disk write error disk full ? . There I'd plenty of space left on the drive . 3.02.24 Is that using a locally attached disk or a network drive?

And do you have a debug log for it?

[edogg]

A local USB drive sorry I had only just installed it and had not set debug logs

Sent from my Blade S6 using Tapatalk

[ymeknassi]

Installed ntfs-3g and nothing changed. I think it's not relevant as I'm using network cifd

Sent from my E5823 using Tapatalk

[ymeknassi]

Dears, any other ideas?

Sent from my E5823 using Tapatalk

[IAmATeaf]

I thought ntfs-3g no longer worked with the latest versions of VIX?

[birdman]

A local USB drive sorry I had only just installed it and had not set debug logsWhich is different to ymeknassi, who is using a Network Drive.
A pity about the debug log absence, as that would have shown whether the EINTR (Interruprted system call) was common.
If it were I wonder what else you have in common, as no-one else seems to be seeing this.

[ymeknassi]

Guys are you looking for someone with sme issue to get log and understand? Is there any way I can help with this myself? Or maybe this doesn't make sense as I'll be using same hardware anyway...

Sent from my E5823 using Tapatalk

[imish]

having the same issue

Miracle Box running the latest version - 3.2.032
Kernel - 3.14.2
Network Drive

[birdman]

having the same issue

Miracle Box running the latest version - 3.2.032
Kernel - 3.14.2
Network DriveDo you have a debug log?
Does it always happen (i.e. is it reproducible)?

[birdman]

FWIW, I can happily write to a Samba share (provided by a Samba daemon on a Linux box) and produce files >2GB (3671986176 bytes in the .ts before I stopped it).
So it's nothing generic to OpenVix.

[rassi]

This has started again for me, currently using LX3
It was better with ATV

Something from the logs below.



[TIMER] activating state 2
[TIMER] start recording
< 94513.941543> [eDVBServiceRecord] Recording to /media/hdd/movie/20160103 0857 - Nelonen Nappula - Lego Legends Of Chima.ts...
< 94513.943849> [eDVBServiceRecord] start recording...
< 94513.943932> [eDVBServiceRecord] RECORD: have 1 video stream(s) (061e), and 1 audio stream(s) (0d1f), and the pcr pid is 061e, and the text pid is ffffffff
< 94513.944142> [eDVBServiceRecord] ADD PID: 0000
< 94513.944187> [eDVBServiceRecord] ADD PID: 02c5
< 94513.944227> [eDVBServiceRecord] ADD PID: 061e
< 94513.944266> [eDVBServiceRecord] ADD PID: 0d1f
< 94513.946253> [setIoPrio] realtime level 7 ok
< 94513.946333> [eFilePushThreadRecorder] THREAD START
< 94546.000554> [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call
< 94546.000680> [eFilePushThreadRecorder] WRITE ERROR, aborting thread: Interrupted system call
< 94546.000742> [eDVBRecordFileThread] waiting for aio to complete
< 94546.000773> [eDVBRecordFileThread] Waiting for I/O to complete
< 94546.001200> [eDVBServiceRecord] record write error
< 94546.001295> [eDVBServiceRecord] stop recording!
< 94546.001750> [eDVBRecordFileThread] buffer usage histogram (40 buffers of 188 kB)
< 94546.001850> [eDVBRecordFileThread] 1: 56
< 94546.001886> [eDVBRecordFileThread] 2: 1
< 94546.001916> [eDVBRecordFileThread] 3: 1
< 94546.001949> [eDVBRecordFileThread] 4: 1
< 94546.001976> [eDVBRecordFileThread] 5: 1
< 94546.002058> [eFilePushThreadRecorder] stopping thread.
< 94546.010774> [eFilePushThreadRecorder] THREAD STOP
< 94546.054270> [eDVBTSTools] setSource loading streaminfo for /media/hdd/movie/20160103 0857 - Nelonen Nappula - Lego Legends Of Chima.ts
WRITE ERROR on recording, disk full?
RemovePopup, id = DiskFullMessage
AddPopup, id = DiskFullMessage
[SKIN] processing screen MessageBoxSimple:
[SKIN] Attribute not implemented: itemHeight value: 40
< 94546.787988> [ePNG] couldn't open /usr/share/enigma2/skin_default/myNOVUM_FHD2_Black/buttons/FocusBar.png
[SKIN] Error: {myNOVUM_FHD2_Black/skin.xml}: pixmap file /usr/share/enigma2/skin_default/myNOVUM_FHD2_Black/buttons/FocusBar.png not found!. Please contact the skin's author!
< 94546.795747> [gAccel] alloc failed

< 94546.795812> [gSurface] ERROR: accelAlloc failed
< 94546.819710> [gAccel] alloc failed

< 94546.819774> [gSurface] ERROR: accelAlloc failed
[SKIN] processing screen MessageBoxSimple_summary:
< 94704.681717> [eDVBServiceRecord] pcr of eit change: 7215b76
< 94704.681801> [eDVBServiceRecord] now running: Lego Legends of Chima (1440 seconds)
< 94704.682315> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 94704.682440> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 94704.683499> [eDVBServiceRecord] now running: Lego Legends of Chima (1440 seconds)
< 94704.683883> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 94704.683997> [eDVBSectionReader] DMX_SET_FILTER pid=18
[SoftcamManager] oscam already running
[SoftcamManager] Checking if oscam is frozen
< 94752.978333> [eConsoleAppContainer] Starting /bin/sh
< 94753.217619> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 90(16)
[SoftcamManager] oscam is responding like it should
job Components.Task.Job name=Softcam-tarkistus #tasks=1 completed with [] in None
[TIMER] activating state 3
[TIMER] stop recording
< 94813.919662> [eDVBServiceRecord] stop recording!
< 94813.922295> [eFilePushThreadRecorder] stopping thread.
< 94813.922565> [eDVBRecordFileThread] waiting for aio to complete
< 94813.922631> [eDVBRecordFileThread] buffer usage histogram (40 buffers of 188 kB)
< 94813.922662> [eDVBRecordFileThread] 1: 2360
< 94814.100376> [eFilePushThreadRecorder] THREAD STOP
< 94814.110793> [eDVBTSTools] setSource loading streaminfo for /media/hdd/movie/20160103 0838 - Nelonen Nappula - Transformers Rescue Bots.ts
< 94814.115844> [eDVBServiceRecord] fixed up 7215b76 to 7107 (offset 0)
[Trashcan] Recording in progress 1
< 94814.125254> [eDVBCAService] free slot 0 demux 1 for service 1:0:16:1B98:48:46:E080000:0:0:0:
< 94814.125327> [eDVBCAService] don't build/send the same CA PMT twice
[TIMER] record time changed, start prepare is now: Sun Jan 10 08:37:40 2016
< 95002.192813> [eDVBServicePlay] timeshift
< 95002.194499> [eDVBDemux] open demux /dev/dvb/adapter0/demux0





145044.222040> [eFilePushThread] wait for driver eof timeout
<145044.482040> [eFilePushThread] wait for driver eof timeout
<145044.633897> [eFilePushThreadRecorder] Warning: All write buffers busy
<145044.634047> [eDVBRecordFileThread] Waiting for I/O to complete
<145044.741066> [eFilePushThreadRecorder] Warning: All write buffers busy
<145044.741218> [eDVBRecordFileThread] Waiting for I/O to complete
<145044.742059> [eFilePushThread] wait for driver eof timeout
<145045.002042> [eFilePushThread] wait for driver eof timeout
<145045.262048> [eFilePushThread] wait for driver eof timeout
<145045.522216> [eFilePushThread] wait for driver eof timeout
<145045.633425> [eFilePushThreadRecorder] OVERFLOW while recording
<145045.740337> [eFilePushThreadRecorder] OVERFLOW while recording
<145045.752603> [eFilePushThreadRecorder] Warning: All write buffers busy
<145045.752699> [eDVBRecordFileThread] Waiting for I/O to complete
<145045.782323> [eFilePushThread] wait for driver eof timeout
<145045.903455> [eFilePushThreadRecorder] Warning: All write buffers busy
<145045.903543> [eDVBRecordFileThread] Waiting for I/O to complete
<145046.043043> [eFilePushThread] wait for driver eof timeout
<145046.303034> [eFilePushThread] wait for driver eof timeout
<145046.340825> [eFilePushThreadRecorder] Warning: All write buffers busy
<145046.340918> [eDVBRecordFileThread] Waiting for I/O to complete
<145046.433394> [eFilePushThreadRecorder] OVERFLOW while recording
<145046.544577> [eFilePushThreadRecorder] Warning: All write buffers busy
<145046.544662> [eDVBRecordFileThread] Waiting for I/O to complete
<145046.563034> [eFilePushThread] wait for driver eof timeout
<145046.823037> [eFilePushThread] wait for driver eof timeout
<145047.083035> [eFilePushThread] wait for driver eof timeout
<145047.140332> [eFilePushThreadRecorder] OVERFLOW while recording
<145047.233466> [eFilePushThreadRecorder] OVERFLOW while recording
<145047.315623> [eFilePushThreadRecorder] Warning: All write buffers busy
<145047.315712> [eDVBRecordFileThread] Waiting for I/O to complete
<145047.343045> [eFilePushThread] wait for driver eof timeout
<145047.345698> [eFilePushThreadRecorder] Warning: All write buffers busy
<145047.345785> [eDVBRecordFileThread] Waiting for I/O to complete
<145047.604037> [eFilePushThread] wait for driver eof timeout
<145047.833877> [eFilePushThreadRecorder] Warning: All write buffers busy
<145047.833974> [eDVBRecordFileThread] Waiting for I/O to complete
<145047.864044> [eFilePushThread] wait for driver eof timeout
<145048.115286> [eFilePushThread] wait for driver eof timeout
<145048.140848> [eFilePushThreadRecorder] Warning: All write buffers busy
<145048.140932> [eDVBRecordFileThread] Waiting for I/O to complete
<145048.375053> [eFilePushThread] wait for driver eof timeout
<145048.635293> [eFilePushThread] wait for driver eof timeout
<145048.833399> [eFilePushThreadRecorder] OVERFLOW while recording
<145048.896050> [eFilePushThread] wait for driver eof timeout
<145048.940378> [eFilePushThreadRecorder] OVERFLOW while recording
<145048.945640> [eFilePushThreadRecorder] Warning: All write buffers busy
<145048.945758> [eDVBRecordFileThread] Waiting for I/O to complete
<145049.115488> [eFilePushThreadRecorder] Warning: All write buffers busy
<145049.115577> [eDVBRecordFileThread] Waiting for I/O to complete
<145049.156041> [eFilePushThread] wait for driver eof timeout
<145049.416056> [eFilePushThread] wait for driver eof timeout
<145049.633439> [eFilePushThreadRecorder] OVERFLOW while recording
<145049.676046> [eFilePushThread] wait for driver eof timeout
<145049.741273> [eFilePushThreadRecorder] Warning: All write buffers busy
<145049.741380> [eDVBRecordFileThread] Waiting for I/O to complete
<145049.745642> [eFilePushThreadRecorder] Warning: All write buffers busy
<145049.745743> [eDVBRecordFileThread] Waiting for I/O to complete
<145049.936048> [eFilePushThread] wait for driver eof timeout
<145050.196048> [eFilePushThread] wait for driver eof timeout
<145050.340371> [eFilePushThreadRecorder] OVERFLOW while recording
<145050.433369> [eFilePushThreadRecorder] OVERFLOW while recording
<145050.456033> [eFilePushThread] wait for driver eof timeout
<145050.518510> [eFilePushThreadRecorder] Warning: All write buffers busy
<145050.518597> [eDVBRecordFileThread] Waiting for I/O to complete
<145050.548759> [eFilePushThreadRecorder] Warning: All write buffers busy
<145050.548898> [eDVBRecordFileThread] Waiting for I/O to complete
<145050.716038> [eFilePushThread] wait for driver eof timeout
<145050.976041> [eFilePushThread] wait for driver eof timeout
<145051.233605> [eFilePushThreadRecorder] OVERFLOW while recording
<145051.236093> [eFilePushThread] wait for driver eof timeout
<145051.340777> [eFilePushThreadRecorder] Warning: All write buffers busy
<145051.340883> [eDVBRecordFileThread] Waiting for I/O to complete
<145051.348525> [eFilePushThreadRecorder] Warning: All write buffers busy
<145051.348620> [eDVBRecordFileThread] Waiting for I/O to complete
<145051.496036> [eFilePushThread] wait for driver eof timeout
<145051.756041> [eFilePushThread] wait for driver eof timeout
<145052.016039> [eFilePushThread] wait for driver eof timeout
<145052.033452> [eFilePushThreadRecorder] OVERFLOW while recording
<145052.140343> [eFilePushThreadRecorder] OVERFLOW while recording
<145052.148778> [eFilePushThreadRecorder] Warning: All write buffers busy
<145052.148883> [eDVBRecordFileThread] Waiting for I/O to complete
<145052.276036> [eFilePushThread] wait for driver eof timeout
<145052.318465> [eFilePushThreadRecorder] Warning: All write buffers busy
<145052.318554> [eDVBRecordFileThread] Waiting for I/O to complete
<145052.536042> [eFilePushThread] wait for driver eof timeout
<145052.796038> [eFilePushThread] wait for driver eof timeout
<145052.833379> [eFilePushThreadRecorder] OVERFLOW while recording
<145052.948615> [eFilePushThreadRecorder] Warning: All write buffers busy
<145052.948711> [eDVBRecordFileThread] Waiting for I/O to complete
<145053.056043> [eFilePushThread] wait for driver eof timeout
<145053.140917> [eFilePushThreadRecorder] Warning: All write buffers busy
<145053.141057> [eDVBRecordFileThread] Waiting for I/O to complete
<145053.316038> [eFilePushThread] wait for driver eof timeout
<145053.576033> [eFilePushThread] wait for driver eof timeout
<145053.633551> [eFilePushThreadRecorder] OVERFLOW while recording
<145053.740351> [eFilePushThreadRecorder] OVERFLOW while recording
<145053.748763> [eFilePushThreadRecorder] Warning: All write buffers busy
<145053.748859> [eDVBRecordFileThread] Waiting for I/O to complete
<145053.836058> [eFilePushThread] wait for driver eof timeout
<145053.918516> [eFilePushThreadRecorder] Warning: All write buffers busy
<145053.918602> [eDVBRecordFileThread] Waiting for I/O to complete
<145054.096040> [eFilePushThread] wait for driver eof timeout
<145054.356037> [eFilePushThread] wait for driver eof timeout
<145054.616041> [eFilePushThread] wait for driver eof timeout
<145054.633386> [eFilePushThreadRecorder] OVERFLOW while recording
<145054.740982> [eFilePushThreadRecorder] Warning: All write buffers busy
<145054.741127> [eDVBRecordFileThread] Waiting for I/O to complete
<145054.748646> [eFilePushThreadRecorder] Warning: All write buffers busy
<145054.748732> [eDVBRecordFileThread] Waiting for I/O to complete
<145054.876071> [eFilePushThread] wait for driver eof timeout
<145055.136038> [eFilePushThread] wait for driver eof timeout
<145055.233954> [eFilePushThreadRecorder] Warning: All write buffers busy
<145055.234104> [eDVBRecordFileThread] Waiting for I/O to complete
<145055.396043> [eFilePushThread] wait for driver eof timeout
<145055.540352> [eFilePushThreadRecorder] OVERFLOW while recording
<145055.656038> [eFilePushThread] wait for driver eof timeout
<145055.718470> [eFilePushThreadRecorder] Warning: All write buffers busy
<145055.718560> [eDVBRecordFileThread] Waiting for I/O to complete
<145055.916039> [eFilePushThread] wait for driver eof timeout
<145056.176036> [eFilePushThread] wait for driver eof timeout
<145056.233383> [eFilePushThreadRecorder] OVERFLOW while recording
<145056.341147> [eFilePushThreadRecorder] Warning: All write buffers busy
<145056.341234> [eDVBRecordFileThread] Waiting for I/O to complete
<145056.351595> [eFilePushThreadRecorder] Warning: All write buffers busy
<145056.351684> [eDVBRecordFileThread] Waiting for I/O to complete
<145056.436038> [eFilePushThread] wait for driver eof timeout
<145056.696039> [eFilePushThread] wait for driver eof timeout
<145056.956042> [eFilePushThread] wait for driver eof timeout
<145057.033601> [eFilePushThreadRecorder] OVERFLOW while recording
<145057.140320> [eFilePushThreadRecorder] OVERFLOW while recording
<145057.151673> [eFilePushThreadRecorder] Warning: All write buffers busy
<145057.151758> [eDVBRecordFileThread] Waiting for I/O to complete
<145057.216036> [eFilePushThread] wait for driver eof timeout
<145057.311430> [eFilePushThreadRecorder] Warning: All write buffers busy
<145057.311526> [eDVBRecordFileThread] Waiting for I/O to complete
<145057.476040> [eFilePushThread] wait for driver eof timeout
<145057.736041> [eFilePushThread] wait for driver eof timeout
<145057.996040> [eFilePushThread] wait for driver eof timeout
<145058.033369> [eFilePushThreadRecorder] OVERFLOW while recording
<145058.140880> [eFilePushThreadRecorder] Warning: All write buffers busy
<145058.140989> [eDVBRecordFileThread] Waiting for I/O to complete
<145058.151721> [eFilePushThreadRecorder] Warning: All write buffers busy
<145058.151840> [eDVBRecordFileThread] Waiting for I/O to complete
<145058.256051> [eFilePushThread] wait for driver eof timeout
<145058.516039> [eFilePushThread] wait for driver eof timeout
<145058.740348> [eFilePushThreadRecorder] OVERFLOW while recording
<145058.776054> [eFilePushThread] wait for driver eof timeout
<145058.902539> [eFilePushThreadRecorder] Warning: All write buffers busy
<145058.902628> [eDVBRecordFileThread] Waiting for I/O to complete
<145059.033648> [eFilePushThreadRecorder] OVERFLOW while recording
<145059.036090> [eFilePushThread] wait for driver eof timeout
<145059.152557> [eFilePushThreadRecorder] Warning: All write buffers busy
<145059.152648> [eDVBRecordFileThread] Waiting for I/O to complete
<145059.296042> [eFilePushThread] wait for driver eof timeout
<145059.556038> [eFilePushThread] wait for driver eof timeout
<145059.634828> [eFilePushThreadRecorder] Warning: All write buffers busy
<145059.634937> [eDVBRecordFileThread] Waiting for I/O to complete
<145059.740753> [eFilePushThreadRecorder] Warning: All write buffers busy
<145059.740836> [eDVBRecordFileThread] Waiting for I/O to complete
<145059.816037> [eFilePushThread] wait for driver eof timeout
<145060.076039> [eFilePushThread] wait for driver eof timeout
<145060.336039> [eFilePushThread] wait for driver eof timeout
<145060.596038> [eFilePushThread] wait for driver eof timeout
<145060.634378> [eFilePushThreadRecorder] OVERFLOW while recording
<145060.740320> [eFilePushThreadRecorder] OVERFLOW while recording
<145060.753523> [eFilePushThreadRecorder] Warning: All write buffers busy
<145060.753610> [eDVBRecordFileThread] Waiting for I/O to complete
<145060.856042> [eFilePushThread] wait for driver eof timeout
<145060.913523> [eFilePushThreadRecorder] Warning: All write buffers busy
<145060.913613> [eDVBRecordFileThread] Waiting for I/O to complete
<145061.116043> [eFilePushThread] wait for driver eof timeout
<145061.376040> [eFilePushThread] wait for driver eof timeout
<145061.540834> [eFilePushThreadRecorder] Warning: All write buffers busy
<145061.540947> [eDVBRecordFileThread] Waiting for I/O to complete
<145061.636059> [eFilePushThread] wait for driver eof timeout
<145061.834365> [eFilePushThreadRecorder] OVERFLOW while recording
<145061.896338> [eFilePushThread] wait for driver eof timeout
<145061.946642> [eFilePushThreadRecorder] Warning: All write buffers busy
<145061.946729> [eDVBRecordFileThread] Waiting for I/O to complete
<145062.156301> [eFilePushThread] wait for driver eof timeout
<145062.417052> [eFilePushThread] wait for driver eof timeout

[birdman]

This has started again for me, currently using LX3
It was better with ATV

Something from the logs below.

The first one shows an Interrupted System call, as seen previously (see #16 and #25). However, it is different in that it has happened quite soon after the recording started. You seem to have had two concurrent recordings on the go (consecutive episodes?) and the other one kept going, which at least seems to answer the question of whether the disk really was full.

The second excerpt is different. Not sure how it relates to anything else going on (why not upload the while log?). It looks like what I would expect to happen if the disk subsystem were to stop/be slow handling write requests? (although the EOVERFLOW itself appears to be a result of not reading sufficiently quickly from the tuner data).

Are you writing to a network share here, or a local/usb disk?
Do you have timeshift on and, if so, where is that writing?

[birdman]

Well, I can reproduce (forcibly) the "Interrupted System call" messages in a way that might explain the log in #16.
It is highly unlikely to explain the first part of #40.

What I did was to run (temporarily) enigma2 with a limit on the size of an output file of 40000 (which is 20MB on my box) and start a recording. The result was:
< 831.328208> [eDVBRecordFileThread] poll: aio_return returned failure: Interrupted system call
< 831.328680> [eFilePushThreadRecorder] WRITE ERROR, aborting thread: Interrupted system call
< 831.328967> [eDVBServiceRecord] record write error
< 831.329136> [eDVBServiceRecord] stop recording!
< 831.329989> [eDVBRecordFileThread] waiting for aio to complete
< 831.330578> [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call
< 831.330726> [eDVBRecordFileThread] buffer usage histogram (20 buffers of 188 kB)
< 831.330958> [eDVBRecordFileThread] 0: 3
< 831.331360> [eDVBRecordFileThread] 1: 105
< 831.335321> [eFilePushThreadRecorder] stopping thread.
< 831.363607> [eFilePushThreadRecorder] THREAD STOP
< 831.368150> [eDVBTSTools] setSource loading streaminfo for /media/hdd/movie/20160103 1757 - BBC TWO - The Great History Quiz_ The Tudors.ts
< 831.369766> [eDVBServiceRecord] fixed up 1a84ca942 to bc92 (offset 0)
WRITE ERROR on recording, disk full?
RemovePopup, id = DiskFullMessage
AddPopup, id = DiskFullMessage
[SKIN] processing screen MessageBoxSimple:
[SKIN] processing screen MessageBoxSimple_summary:
One interesting(?) thing was that after this had happened the timer was still showing as active (recording) in the timer list.

Anyway, back to ymeknassi (http://www.world-of-satellite.com/member.php?85413-ymeknassi)'s problem. You'll need to logjn to the system, run "ps -ef" and look for the pid (second column) of the /usr/bin/enigma2 process (not the enigma2.sh one), then "cd /proc/<<pid>>" for that number followed by "cat limits". The second limit (Max file size) should be unlimited for both the Soft and Hard limit. Is it?

[ymeknassi]

Hi guys, I was quite busy the last days and didn't follow up on this. Anyway back from BlackHole where recording is working correctly; I installed now open vix 3.2 . Same issue is still happening. I also checked as per your recommendation and both limits are Unlimited



Well, I can reproduce (forcibly) the "Interrupted System call" messages in a way that might explain the log in #16.
It is highly unlikely to explain the first part of #40.

What I did was to run (temporarily) enigma2 with a limit on the size of an output file of 40000 (which is 20MB on my box) and start a recording. The result was:
One interesting(?) thing was that after this had happened the timer was still showing as active (recording) in the timer list.

Anyway, back to ymeknassi (http://www.world-of-satellite.com/member.php?85413-ymeknassi)'s problem. You'll need to logjn to the system, run "ps -ef" and look for the pid (second column) of the /usr/bin/enigma2 process (not the enigma2.sh one), then "cd /proc/<<pid>>" for that number followed by "cat limits". The second limit (Max file size) should be unlimited for both the Soft and Hard limit. Is it?

[Photovoltaic]

If you're running Samba on a Linux system..why not just ditch Samba and use NFS instead? I use an NFS Mounted 16TB Filesystem as my "Hard Drive Replacement" mount and record all content to it. (OpenViX, Xtrend ET10000)

[rassi]

The first one shows an Interrupted System call, as seen previously (see #16 and #25). However, it is different in that it has happened quite soon after the recording started. You seem to have had two concurrent recordings on the go (consecutive episodes?) and the other one kept going, which at least seems to answer the question of whether the disk really was full.

The second excerpt is different. Not sure how it relates to anything else going on (why not upload the while log?). It looks like what I would expect to happen if the disk subsystem were to stop/be slow handling write requests? (although the EOVERFLOW itself appears to be a result of not reading sufficiently quickly from the tuner data).

Are you writing to a network share here, or a local/usb disk?
Do you have timeshift on and, if so, where is that writing?

HDD (NFS mount) is not full, there is always something like 3-7TB free. It seem that it dont matter do i have just SD or SD+HD+HD recording going on :(
Attached log from today. There is one [RecordTimer] WRITE ERROR on recording, disk full?

zipped
46821



If you're running Samba on a Linux system..why not just ditch Samba and use NFS instead?

It do not make any difference. Ok at least in my case. Using NFS.

[birdman]

zipped
46821This 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.


47061

[birdman]

Newest logs attached.


47061That 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=t cp,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