There is a new version of the avoidTrashing-patch available: http://vdr.unetz.com/download/patches/vdr-avoidTrashing-0.2.1-plain-1.3.31.d...
Changes since 0.2.0: - better handling of jump backs in a stream - temporarily disabled active read ahead of this patch (back to normal kernel read ahead currently)
Ralf
Ralf Müller wrote:
There is a new version of the avoidTrashing-patch available: http://vdr.unetz.com/download/patches/vdr-avoidTrashing-0.2.1-plain-1.3.31.d...
Changes since 0.2.0:
- better handling of jump backs in a stream
- temporarily disabled active read ahead of this patch (back to normal
kernel read ahead currently)
Are there "trashing" patches for streamdev (0.3.3-pre3-geni) and the burn plugins?
Best Regards.
Hi Ralf,
with this patch i get the syslog is flooded with the following messages when recording or cutting flush buffer: 41 (10491272 bytes, 146888709-157379981) the bytes from/to differ and also the number of bytes. What does the messages mean, are that error messages an my recordings cutted recordings damaged?
cheers Gerald
Am Sonntag, 28. August 2005 18:24 schrieb Ralf Müller:
There is a new version of the avoidTrashing-patch available: http://vdr.unetz.com/download/patches/vdr-avoidTrashing-0.2.1-plain-1.3.31. diff.gz
Changes since 0.2.0:
- better handling of jump backs in a stream
- temporarily disabled active read ahead of this patch (back to normal
kernel read ahead currently)
Ralf
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Montag 29 August 2005 22:35, Gerald Raaf wrote:
with this patch i get the syslog is flooded with the following messages when recording or cutting flush buffer: 41 (10491272 bytes, 146888709-157379981) the bytes from/to differ and also the number of bytes.
You use a relatively high log level ... anyway I have disabled this message. A new version is available here:
http://vdr.unetz.com/download/patches/vdr-avoidTrashing-0.2.2-plain-1.3.31. diff.gz
What does the messages mean, are that error messages an my recordings cutted recordings damaged?
It is not an error message and no damage should have been done. It just tells you which region of which file handle has been flushed to disk. For you it's just noise but nothing you have to worry about.
Regards Ralf
-
C.Y.M -
Gerald Raaf -
Ralf Müller