Hi, today i encountered a strange problem: VDR stopped in the middle of a recording and /var/log/messages says something about disk full (?) In fact i have 2 Harddisks and both have around 20 GB free (see df below, /video0 is located in root) So here is the log file, i have marked the strange things with *** in front! As you can see the drivers also crashed later on (i had to reboot the machine), but i'm not sure if this was caused by the first problem... Jul 16 15:40:34 linux -- MARK -- Jul 16 15:57:00 linux vdr[657]: timer 1 start Jul 16 15:57:00 linux vdr[657]: switching to channel 6 Jul 16 15:57:00 linux vdr[657]: record /video0/Star_Trek_-_Das_n�chste_Jahrhundert Jul 16 15:57:00 linux vdr[657]: creating directory /video0/Star_Trek_-_Das_n�chste Jul 16 15:57:00 linux vdr[657]: creating directory /video0/Star_Trek_-_Das_n�chste Jul 16 15:57:00 linux vdr[657]: recording to '/video0/Star_Trek_-_Das_n�chste_Jahr Jul 16 15:57:00 linux vdr[3931]: output thread started (pid=3931) Jul 16 15:57:00 linux vdr[3932]: input thread started (pid=3932) ***Jul 16 15:58:41 linux vdr[3931]: low disk space (0 MB, limit is 512 MB) ***Jul 16 15:58:41 linux vdr[3931]: recording to '/video0/Star_Tr' Jul 16 15:59:00 linux /USR/SBIN/CRON[3938]: (root) CMD ( rm -f /var/spool/cron/las Jul 16 16:20:34 linux -- MARK -- ***Jul 16 16:34:53 linux vdr[3931]: ERROR: max number of files (255) exceeded Jul 16 16:34:53 linux vdr[3931]: output thread ended (pid=3931) Jul 16 16:34:53 linux vdr[3932]: input thread ended (pid=3932) Jul 16 16:59:00 linux /USR/SBIN/CRON[4091]: (root) CMD ( rm -f /var/spool/cron/las Jul 16 17:05:01 linux vdr[657]: buffer stats: 49040 (4%) used Jul 16 17:05:01 linux vdr[657]: timer 1 stop Jul 16 17:05:01 linux vdr[657]: deleting timer 1 Jul 16 17:20:34 linux -- MARK -- Jul 16 17:40:34 linux -- MARK -- Jul 16 17:59:00 linux /USR/SBIN/CRON[4215]: (root) CMD ( rm -f /var/spool/cron/las Jul 16 18:20:34 linux -- MARK -- Jul 16 18:40:34 linux -- MARK -- Jul 16 18:59:00 linux /USR/SBIN/CRON[4338]: (root) CMD ( rm -f /var/spool/cron/las Jul 16 19:20:34 linux -- MARK -- Jul 16 19:40:34 linux -- MARK -- Jul 16 19:40:43 linux vdr[657]: switching to channel 5 Jul 16 19:40:56 linux vdr[657]: switching to channel 5 ***Jul 16 19:40:56 linux vdr[657]: ERROR: channel 5 not sync'ed! Jul 16 19:40:56 linux vdr[657]: retrying Jul 16 19:40:58 linux vdr[657]: ERROR: timeout while tuning *** Jul 16 19:40:58 linux vdr[657]: ERROR: channel 5 not sync'ed! Jul 16 19:40:58 linux vdr[657]: retrying df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda3 32341888 9998396 20700448 33% / /dev/hda1 23300 5309 16788 25% /boot /dev/hdc1 24205416 3185400 20770108 14% /video1 shmfs 227220 0 227220 0% /dev/shm Any idea about that ? Is it a bug ? Could it be that vdr interprets something wrong if both video0 and video1 have exactly the same amount of free space ? Maybe you could comment on this, Klaus ? Martin. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
