Jump to content


Photo

Write error on recording, something to do with NFS settings?

DUO

  • Please log in to reply
16 replies to this topic

#1 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 9 September 2012 - 08:01

What will cause this issue?

Using now OpenPli 3.0 based image.

If i but timers they can record for a while but after a while i maybe get popup which says "WRITE ERROR on recording, disk full?" and it stops
recording, samething when using record now.
There have never been this kind of issue when using eg. BH image. Recording will go to correct place at /hdd/movie

root@vuduo:~# df
Filesystem		   1K-blocks	  Used Available Use% Mounted on
ubi0:rootfs			 104708	 61476	 43232  59% /
devtmpfs				 69072		 4	 69068   0% /dev
tmpfs					   64		 0	    64   0% /media
/dev/sda1			   976984	  8104    968880   1% /media/usb
tmpfs				    69188	   168	 69020   0% /var/volatile
192.168.1.6:/mnt/video/dream/
					 7324175520 6245064160 1079111360  85% /media/net/nas

fixed up 1344f7c26 to 5afd90 (offset 0)
[TIMER] record event 5
[TIMER] record event 8
WRITE ERROR on recording, disk full?
RemovePopup, id = DiskFullMessage
AddPopup, id = DiskFullMessage
ERROR reading PES (fd=49) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 49(8)
[SoftcamManager] CCcam.2.2.1 already running
[SoftcamManager] Telnet info not allowed, can not check if frozen
job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
[EPGC] start caching events(1347097501)
[EPGC] abort non avail schedule reading
[EPGC] abort non avail schedule other reading
[EPGC] abort non avail netmed schedule reading
[EPGC] abort non avail netmed schedule other reading
[EPGC] abort non avail FreeSat schedule_other reading
[EPGC] abort non avail viasat reading
[EPGC] nownext finished(1347097512)
[EPGC] stop caching events(1347097512)
[EPGC] next update in 60 min

root@vuduo:~# cat /etc/fstab
rootfs			   /				    auto	   defaults			  1  1
proc				 /proc			    proc	   defaults			  0  0
devpts			   /dev/pts			 devpts	 mode=0620,gid=5	   0  0
usbdevfs			 /proc/bus/usb	    usbdevfs   noauto			    0  0
tmpfs			    /var/volatile	    tmpfs	  defaults			  0  0
usbfs			    /proc/bus/usb	    usbfs	  defaults			  0  0
UUID=60AF-4D53  /media/usb	  vfat    defaults	    0 0
192.168.1.6:/mnt/video/dream /media/net/nas	 nfs	 nfsvers=3,proto=tcp,rsize=32768,wsize=32768,timeo=14,fg,soft,intr	 0 0
UUID=98E7-0D66  /media/usb	  vfat    defaults	    0 0


Removed USB stick and changed fstab settings without help, still getting same error.

root@vuduo:~# cat /etc/fstab
rootfs			   /				    auto	   defaults			  1  1
proc				 /proc			    proc	   defaults			  0  0
devpts			   /dev/pts			 devpts	 mode=0620,gid=5	   0  0
usbdevfs			 /proc/bus/usb	    usbdevfs   noauto			    0  0
tmpfs			    /var/volatile	    tmpfs	  defaults			  0  0
usbfs			    /proc/bus/usb	    usbfs	  defaults			  0  0
UUID=60AF-4D53  /media/usb	  vfat    defaults	    0 0
192.168.1.6:/mnt/video/dream /media/net/nas nfs rw,soft,async,nolock 0 0

root@vuduo:~# cat /proc/mounts
rootfs / rootfs rw 0 0
ubi0:rootfs / ubifs rw,sync,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=69072k,nr_inodes=17268,mode=755 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /media tmpfs rw,relatime,size=64k 0 0
tmpfs /var/volatile tmpfs rw,relatime 0 0
usbfs /proc/bus/usb usbfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
192.168.1.6:/mnt/video/dream/ /media/net/nas nfs rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,soft,nolock,proto=tcp,port=65535,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.1.6 0 0


Re: Write error on recording, something to do with NFS settings? #2 blzr

  • PLi® Core member
  • 2,269 posts

+118
Excellent

Posted 9 September 2012 - 09:03

...There have never been this kind of issue when using eg. BH image. Recording will go to correct place at /hdd/movie

and that's exactly what is going on in this case also,
but since you have no hdd /?/ in your box, recording is writen to flash, so... ;)

you'd like to record on NFS share on a remote computer?
if so, you have to set 'use as hdd replacement = yes' in the mount manager for this nfs mount...
rgds
True sarcasm doesn't need green font...

Re: Write error on recording, something to do with NFS settings? #3 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 9 September 2012 - 09:09


...There have never been this kind of issue when using eg. BH image. Recording will go to correct place at /hdd/movie

and that's exactly what is going on in this case also,
but since you have no hdd /?/ in your box, recording is writen to flash, so... ;)

you'd like to record on NFS share on a remote computer?
if so, you have to set 'use as hdd replacement = yes' in the mount manager for this nfs mount...
rgds


Issue is not this simple :)
NFS is set as HDD replacement and all recordings are going to my NAS, continuing my 5 year recordings. It can record 5min, 10min or an hour and after unsuccesful recording i can make new one, which will again can save 5min, 30min etc

Re: Write error on recording, something to do with NFS settings? #4 MiLo

  • PLi® Core member
  • 14,045 posts

+298
Excellent

Posted 9 September 2012 - 19:33

REplace the NFS mount options:

nfsvers=3,proto=tcp,rsize=32768,wsize=32768,timeo=14,fg,soft,intr
Just make it:

rw,async,soft

and nothing else. Let the box negotiate with your NAS for the best options, instead of using parameters that were deemed good by a random person about 25 kernel versions ago.
Real musicians never die - they just decompose

Re: Write error on recording, something to do with NFS settings? #5 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 9 September 2012 - 19:55

REplace the NFS mount options:

nfsvers=3,proto=tcp,rsize=32768,wsize=32768,timeo=14,fg,soft,intr
Just make it:

rw,async,soft

and nothing else. Let the box negotiate with your NAS for the best options, instead of using parameters that were deemed good by a random person about 25 kernel versions ago.


Are those rw,async,soft default on mount manager when creating mount by manual with remote control? If yes, then first settings was with those. I think NFS was not the problem i tested also with CIFS and same issue was there. Now im using BH again without a problems. I have to test openpli based again later.

Re: Write error on recording, something to do with NFS settings? #6 MiLo

  • PLi® Core member
  • 14,045 posts

+298
Excellent

Posted 9 September 2012 - 19:59

Instead of recording, you could try copying large files around as a test (e.g. from a usb stick to the share. Or "dd if=/dev/zero of=/media/hdd/testfile bs=188K" if you dare). After all, the problem appears to be that you cannot reliably write to the remote disk.
Real musicians never die - they just decompose

Re: Write error on recording, something to do with NFS settings? #7 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 10 September 2012 - 10:11

Yes thanks. I will do some tests. This will be mine reference, benchmarked with BH.

Test filesize 64MB

Current:
Results for write throughput:
67.108 Mbit/s with udp,async,wsize=16384
59.652 Mbit/s with udp,async,wsize=8192
59.652 Mbit/s with udp,async,wsize=32768
59.652 Mbit/s with tcp,async,wsize=32768
53.687 Mbit/s with tcp,async,wsize=8192
53.687 Mbit/s with tcp,async,wsize=4096
53.687 Mbit/s with tcp,async,wsize=16384
44.739 Mbit/s with udp,async,wsize=4096

Results for read throughput:
89.478 Mbit/s with udp,async,rsize=8192
89.478 Mbit/s with udp,async,rsize=4096
89.478 Mbit/s with udp,async,rsize=32768
89.478 Mbit/s with udp,async,rsize=16384
89.478 Mbit/s with tcp,async,rsize=8192
89.478 Mbit/s with tcp,async,rsize=4096
89.478 Mbit/s with tcp,async,rsize=32768
89.478 Mbit/s with tcp,async,rsize=16384



Test script:

#!/bin/sh
# IP of your NFS server
serverip=192.168.1.6
# exported directory on your NFS server
exportdir=/mnt/video/dream
# mount point on dbox
dboxmountpoint="/mnt"
# filesize to transfer in MBytes.
# At least 8 MByte. Good values are 32 or 64 MByte.
# Try 128 to be more accurate (takes much longer!)
filesize=64
# block sizes to test in KBytes, possible values are 1 2 4 8 16 32.
# values have to be separated with spaces. See examples below.
# blocksizelist="4 8 32"
# blocksizelist="16"
blocksizelist="4 8 16 32"
# wether to enable synchronous reading, writing. Possible values are "yes"
# or no. Normally synchronous reading or writing should be slower than
# asynchronous, so to save some time most people would say "no" here.
enablesynctests="no"


##################################################################
########			 don't edit below this line		   ########
##################################################################

bs=8192
count=`expr $filesize \* 1048576 / $bs`
wlist=""
rlist=""
synctests="async"
if [ $enablesynctests = "yes" ]; then
  synctests="sync "$synctests
fi

echo
echo "Measuring NFS throughput..."
for factor in $blocksizelist
do
  for protocol in udp tcp
  do
    for synchronized in $synctests
    do
	   size=`expr $factor \* 1024`
	   bitcount=`expr $bs \* $count \* 8`
	   umount $dboxmountpoint 2>/dev/null
	   mount -t nfs -o rw,soft,$protocol,nolock,$synchronized,rsize=$size,wsize=$size,rsize=$size $serverip:$exportdir $dboxmo											    untpoint
	   echo "Mount options: "$protocol", "$synchronized", wsize="$size
	   echo "writing "$filesize" MBytes..."
	   a=`date +%s`
	   dd if=/dev/zero of=$dboxmountpoint/test bs=$bs count=$count 2>/dev/null;
	   if [ $? = "0" ]
	   then
		 z=`date +%s`
		 duration=`expr $z - $a`
		 throughput=`expr $bitcount / $duration`
    echo "Success after "$duration" seconds"
	   else
		 throughput="Failure"
    echo "Failure"
	   fi
	   wlist=$wlist$throughput" with "$protocol","$synchronized",wsize="$size"\n"

	   echo "Mount options: "$protocol", "$synchronized", rsize="$size
	   echo "reading "$filesize" MBytes..."
	   a=`date +%s`
	   dd of=/dev/null if=$dboxmountpoint/test bs=$bs count=$count 2>/dev/null;
	   if [ $? = "0" ]
	   then
		 z=`date +%s`
		 duration=`expr $z - $a`
		 throughput=`expr $bitcount / $duration`
    echo "Success after "$duration" seconds"
	   else
		 throughput="Failure"
    echo "Failure"
	   fi
	   rlist=$rlist$throughput" with "$protocol","$synchronized",rsize="$size"\n"
	   echo
    done
  done
done

echo "Results for write throughput:"
echo -e $wlist | sort -nr | sed 's/^\([0-9]*\)\([0-9]\{3\}\)\([0-9]\{3\}\(.*\)\)/\1.\2 Mbit\/s\4/g'

echo "Results for read throughput:"
echo -e $rlist | sort -nr | sed 's/^\([0-9]*\)\([0-9]\{3\}\)\([0-9]\{3\}\(.*\)\)/\1.\2 Mbit\/s\4/g'


Edited by rassi, 10 September 2012 - 10:13.


Re: Write error on recording, something to do with NFS settings? #8 MiLo

  • PLi® Core member
  • 14,045 posts

+298
Excellent

Posted 10 September 2012 - 13:13

I meant running that as a "duration" test, i.e. keep writing until you get an error. The speed isn't interesting in this case, the problem is that it "stops".
Real musicians never die - they just decompose

Re: Write error on recording, something to do with NFS settings? #9 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 10 September 2012 - 14:41

Oh, ok :)

Re: Write error on recording, something to do with NFS settings? #10 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 24 November 2012 - 08:10

Back to this. I was using 2.5 month again another than OpenPli bases image without an problem.

Current NFS mount options

root@vuduo:~# cat /proc/mounts
rootfs / rootfs rw 0 0
ubi0:rootfs / ubifs rw,sync,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=69072k,nr_inodes=17268,mode=755 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /media tmpfs rw,relatime,size=64k 0 0
/dev/sda1 /media/usb vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /var/volatile tmpfs rw,relatime 0 0
usbfs /proc/bus/usb usbfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
192.168.1.6:/mnt/video/dream/ /media/hdd nfs rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,nolock,proto=tcp,port=65535,timeo=14,retrans=3,sec=sys,local_lock=all,addr=192.168.1.6 0 0


First DD test. No problem.

root@vuduo:~# dd if=/dev/zero of=/media/hdd/testfile bs=188K
^C
root@vuduo:~# ls /media/hdd/testfile -l
-rw-r--r--    1 nobody   nogroup  5998096384 Nov 23 22:10 /media/hdd/testfile

[TIMER] activating state 1
begin_date:  20121123 2100
service_name:  Discovery (F)
name: Mafian parhaat
description:  Mafia's Greatest Hits. Salaisiin FBI:n tietoihin perustuva sarja paljastaa totuuden mafian pahamaineisimmista tappajista ja heidän taustoistaan.
[RecordTimer] media is not mounted: /media/hdd/movie
[TIMER] backoff: retry in 5 seconds
[RecordTimer] media is not mounted: /media/hdd/movie
[TIMER] failed to find mount to check for free space.
RemovePopup, id = DiskFullMessage
AddPopup, id = DiskFullMessage
getFPWasTimerWakeup: False

Second dd test is running at the moment.

21GB now written without an issue.

root@vuduo:~# ls /media/hdd/testfile -l
-rw-r--r--    1 nobody   nogroup  20935041024 Nov 24 09:10 /media/hdd/testfile


Re: Write error on recording, something to do with NFS settings? #11 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 24 November 2012 - 08:50

 
root@vuduo:~# ls /media/hdd/testfile -l
-rw-r--r--    1 nobody   nogroup  45010227200 Nov 24 09:49 /media/hdd/testfile


I will stop this test now.

Test will stop now :)

Re: Write error on recording, something to do with NFS settings? #12 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 25 November 2012 - 16:21

And some more logs from just happened Disk full error, if anyone figure what can be the issue?
I was watching recorded show and then new timer record started and "Disk Full" popup came.


[EPGImport] autostart (0) occured at 1353856565.63
[AutoTimer] Auto Poll Enabled
[SoftcamManager] AutoStart Enabled
[CI_Assignment] activating ci configs:
[CI_Activate] FOUND 2 CI Slots
[CI_Activate_Config_CI0] no config file found
[CI_Activate_Config_CI0] error parsing xml...
[CI_Activate_Config_CI1] no config file found
[CI_Activate_Config_CI1] error parsing xml...
starting hotplug handler
[TIMER] record time changed, start prepare is now: Sun Nov 25 15:44:40 2012
[Timer] Record RecordTimerEntry(name=Talent Suomi, begin=Sun Nov 25 15:45:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.nelonen.tv" ORDER BY bouquet, justplay=0)
[TIMER] activating state 1
begin_date:  20121125 1545
service_name:  Nelonen
name: Talent Suomi
description:  Finaali II. Tänään esiintyvät tulitaiteilija Jamie Chyay, laulaja Anniina Ahven, kvintetti Con Brio, tanssija Edward Sabo, laulaja Jorma Koponen, voimistelijakaksikko Supertytöt, laulaja Peter Räsänen ja Bollywood-ryhmä DBDC. Tuomareina nähdään Janne Kataja, Maria Sid ja Mikko von Hertzen, ja ohjelman juontavat Lorenz Backman ja Sebastian Rejman. Kotimainen viihdeohjelma. 4. tuotantokausi. (66')
[RecordTimer] media is not mounted: /media/hdd/movie
[TIMER] backoff: retry in 5 seconds
[RecordTimer] media is not mounted: /media/hdd/movie
[TIMER] failed to find mount to check for free space.
RemovePopup, id = DiskFullMessage
AddPopup, id = DiskFullMessage
[TIMER] record time changed, start prepare is now: Sun Nov 25 17:14:40 2012
[Timer] Record RecordTimerEntry(name=Vain elämää, begin=Sun Nov 25 17:15:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.nelonen.tv" ORDER BY bouquet, justplay=0)
[TIMER] activating state 1
begin_date:  20121125 1715
service_name:  Nelonen
name: Vain elämää
description:  Artistien yhteinen viikko huipentuu duettopäivään. Jokainen artisti valitsee duettoparin ja yhden omista hiteistään ja ikimuistoinen päivä voi alkaa. 1. tuotantokausi. (63') Ohjelman tekstitys teksti-tv:n sivulla 333.
[RecordTimer] media is not mounted: /media/hdd/movie
[TIMER] backoff: retry in 5 seconds
[RecordTimer] media is not mounted: /media/hdd/movie
[TIMER] failed to find mount to check for free space.
RemovePopup, id = DiskFullMessage
(found in notifications)
AddPopup, id = DiskFullMessage
[TIMER] record time changed, start prepare is now: Mon Nov 26 06:49:40 2012
[Timer] Record RecordTimerEntry(name=PIKKU KAKKONEN, begin=Mon Nov 26 06:50:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.yle_tv2.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Mon Nov 26 16:58:40 2012
[Timer] Record RecordTimerEntry(name=Pikku Kakkonen, begin=Mon Nov 26 16:59:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.yle_tv2.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Wed Nov 28 19:59:40 2012
[Timer] Record RecordTimerEntry(name=Kuppilat kuntoon, Jyrki Sukula!, begin=Wed Nov 28 20:00:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.nelonen.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Wed Nov 28 20:59:40 2012
[Timer] Record RecordTimerEntry(name=Greyn anatomia, begin=Wed Nov 28 21:00:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.nelonen.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Wed Nov 28 21:59:40 2012
[Timer] Record RecordTimerEntry(name=Hyvät ja huonot uutiset, begin=Wed Nov 28 22:00:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.nelonen.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Fri Nov 30 19:29:40 2012
[Timer] Record RecordTimerEntry(name=Erätulilla, begin=Fri Nov 30 19:30:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.yle_tv2.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Sat Dec  1 07:54:40 2012
[Timer] Record RecordTimerEntry(name=Palomies Sami (S) - Fireman Sam, begin=Sat Dec  1 07:55:00 2012, serviceref=1:0:19:1A94:44:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Thu Nov 22 19:06:01 2012
[Timer] Record RecordTimerEntry(name=Neljän tähden illallinen, begin=Thu Nov 22 19:06:21 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.nelonen.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Thu Nov 22 20:29:40 2012
[Timer] Record RecordTimerEntry(name=Huutokauppa, begin=Thu Nov 22 20:30:00 2012, serviceref=1:0:1:19F:4:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Thu Nov 22 22:59:40 2012
[Timer] Record RecordTimerEntry(name=Pawn Stars, begin=Thu Nov 22 23:00:00 2012, serviceref=1:0:19:106A:29:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Thu Nov 22 23:29:40 2012
[Timer] Record RecordTimerEntry(name=Storage Wars, begin=Thu Nov 22 23:30:00 2012, serviceref=1:0:19:106A:29:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Thu Nov 22 23:59:40 2012
[Timer] Record RecordTimerEntry(name=Ancient Aliens, begin=Fri Nov 23 00:00:00 2012, serviceref=1:0:19:106A:29:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Fri Nov 23 19:59:40 2012
[Timer] Record RecordTimerEntry(name=Huutokauppa, begin=Fri Nov 23 20:00:00 2012, serviceref=1:0:1:19F:4:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Fri Nov 23 20:59:40 2012
[Timer] Record RecordTimerEntry(name=Mafian parhaat, begin=Fri Nov 23 21:00:00 2012, serviceref=1:0:1:19F:4:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Fri Nov 23 20:29:40 2012
[Timer] Record RecordTimerEntry(name=Huutokauppa, begin=Fri Nov 23 20:30:00 2012, serviceref=1:0:1:19F:4:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Fri Nov 23 21:59:40 2012
[Timer] Record RecordTimerEntry(name=Ruudinkäryä, begin=Fri Nov 23 22:00:00 2012, serviceref=1:0:1:19F:4:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Fri Nov 23 22:29:40 2012
[Timer] Record RecordTimerEntry(name=Dino 2, begin=Fri Nov 23 22:30:00 2012, serviceref=1:0:1:CFB:21:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Sat Nov 24 00:59:40 2012
[Timer] Record RecordTimerEntry(name=Mafian parhaat, begin=Sat Nov 24 01:00:00 2012, serviceref=1:0:1:19F:4:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Fri Nov 23 23:59:40 2012
[Timer] Record RecordTimerEntry(name=Kullan sukeltajat, begin=Sat Nov 24 00:00:00 2012, serviceref=1:0:1:19F:4:46:E080000:0:0:0:, justplay=0)
[TIMER] record time changed, start prepare is now: Sat Nov 24 02:24:40 2012
[Timer] Record RecordTimerEntry(name=Pelkokerroin, begin=Sat Nov 24 02:25:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.jim.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Sat Nov 24 01:29:40 2012
[Timer] Record RecordTimerEntry(name=Pelkokerroin, begin=Sat Nov 24 01:30:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.jim.tv" ORDER BY bouquet, justplay=0)
[TIMER] record time changed, start prepare is now: Sat Nov 24 19:29:40 2012
[Timer] Record RecordTimerEntry(name=Talent Suomi, begin=Sat Nov 24 19:30:00 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.nelonen.tv" ORDER BY bouquet, justplay=0)
getFPWasTimerWakeup: False
[ImageManager] AutoStart Enabled
[ImageManager] Backup Schedule Disabled at (now=su 25. marraskuuta 2012 17.16.06)
[BackupManager] AutoStart Enabled
[BackupManager] Backup Schedule Disabled at (now=su 25. marraskuuta 2012 17.16.06)
[EPGImport] autostart (0) occured at 1353856566.6
[EPGImport] WakeUpTime now set to -1 (now=1353856566)
[ePNG] couldn't open /usr/share/enigma2/ico_dvb_s-fs8.png
[ePNG] couldn't open /usr/share/enigma2/ico_dvb_c-fs8.png
[ePNG] couldn't open /usr/share/enigma2/ico_dvb_t-fs8.png
[ePNG] couldn't open /usr/share/enigma2/ico_service_group-fs8.png
RemovePopup, id = ZapError
[Skin] Attribute not implemented: alphatest value: blend


Re: Write error on recording, something to do with NFS settings? #13 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 25 November 2012 - 17:16

And some more info.

NFS mount made with Network Browser, settings we´re
root@vuduo:/etc# nfsstat -m
/media/hdd from 192.168.1.6:/mnt/video/dream/
Flags: rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,nolock,proto=tcp,port=65535,timeo=14,retrans=3,sec=sys,local_lock=all,addr=192.168.1.6


MiLo suggest settings: rw,async,soft
So changed those to fstab.
After reboot

root@vuduo:~# nfsstat -m
/media/hdd from 192.168.1.6:/mnt/video/dream/
 Flags: rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,port=65535,timeo=70,retrans=3,sec=sys,local_lock=none,addr=192.168.1.6

Testing continues.

Edited by rassi, 25 November 2012 - 17:17.


Re: Write error on recording, something to do with NFS settings? #14 MiLo

  • PLi® Core member
  • 14,045 posts

+298
Excellent

Posted 25 November 2012 - 19:57

Something is broken. Just randomly changing settings is not going to fix it. No matter what options you use for mounting, it should just work. It may not work optimal, but it should never break.

Try if you can record to a PC, or another type of NAS, or a USB disk. Try to pinpoint which device is broken, then you can start thinking about fixing something.
Real musicians never die - they just decompose

Re: Write error on recording, something to do with NFS settings? #15 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 25 November 2012 - 20:38

Try if you can record to a PC, or another type of NAS, or a USB disk. Try to pinpoint which device is broken, then you can start thinking about fixing something.


Yeah.

Same thing with SMB mount, but there has never been this kind of issue with other images, which are not OpenPli based. Nothing has changed, no HW, no how mount has done or anything else. Just image which is changed from non-OpenPli to OpenPli. So i just do not get it what can be broken :(
Happy VU+ Duo recordings since 2010

Edited by rassi, 25 November 2012 - 20:41.


Re: Write error on recording, something to do with NFS settings? #16 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 29 November 2012 - 12:59

root@vuduo:~# nfsstat -m
/media/hdd from 192.168.1.6:/mnt/video/dream/
Flags: rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,port=65535,timeo=70,retrans=3,sec=sys,local_lock=none,addr=192.168.1.6

Testing continues.


So far so good, after this change haven´t seen "Disk full write error".

Re: Write error on recording, something to do with NFS settings? #17 rassi

  • Senior Member
  • 91 posts

+1
Neutral

Posted 12 December 2012 - 15:02


root@vuduo:~# nfsstat -m
/media/hdd from 192.168.1.6:/mnt/video/dream/
Flags: rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,port=65535,timeo=70,retrans=3,sec=sys,local_lock=none,addr=192.168.1.6

Testing continues.


So far so good, after this change haven´t seen "Disk full write error".


Ok. Now i have seen it again..

Trying watch one SDTV recording and doing one recording.

[TIMER] record time changed, start prepare is now: Wed Dec 12 15:13:29 2012
[Timer] Record RecordTimerEntry(name=Talent USA, begin=Wed Dec 12 15:13:49 2012, serviceref=1:134:1:0:0:0:0:0:0:0:FROM BOUQUET "alternatives.jim.tv" ORDER BY bouquet, justplay=0)
[TIMER] activating state 1
[RecordTimer] media is not mounted: /media/hdd/movie
[TIMER] backoff: retry in 5 seconds
[RecordTimer] media is not mounted: /media/hdd/movie
[TIMER] failed to find mount to check for free space.
RemovePopup, id = DiskFullMessage
AddPopup, id = DiskFullMessage
[ImageManager] AutoStart Enabled
[ImageManager] Backup Schedule Disabled at (now=ke 12. joulukuuta 2012 15.46.21)
[BackupManager] AutoStart Enabled
[BackupManager] Backup Schedule Disabled at (now=ke 12. joulukuuta 2012 15.46.21)
[EPGImport] autostart (0) occured at 1355319981.16
[EPGImport] WakeUpTime now set to -1 (now=1355319981)
[ePNG] couldn't open /usr/share/enigma2/ico_dvb_s-fs8.png
[ePNG] couldn't open /usr/share/enigma2/ico_dvb_c-fs8.png
[ePNG] couldn't open /usr/share/enigma2/ico_dvb_t-fs8.png
[ePNG] couldn't open /usr/share/enigma2/ico_service_group-fs8.png
RemovePopup, id = ZapError
[Skin] Attribute not implemented: alphatest value: blend


I have raised nfsd count with config on server from 8 to 16
RPCNFSDCOUNT=16



Also tagged with one or more of these keywords: DUO

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users