Hi!
I got a 11 TB NFS storage here to store my recordings, but VDR (1.6.0) states when trying to record "no diskspace available".
Does anybody know how to fix this.
Regards
Marco
Hi!
I'm no C++ programmer but can read the code so I will try to add some output.
Regards
Marco
Klaus Schmidinger schrieb:
Hi!
Some more log output
Aug 12 10:10:40 rec-ism-1 vdr: [12960] ERROR: /video: Value too large for defined data type Aug 12 10:10:40 rec-ism-1 last message repeated 181 times Aug 12 10:10:40 rec-ism-1 vdr: [12960] ...no old recording found, giving up Aug 12 10:10:40 rec-ism-1 vdr: [12960] ERROR: /video: Value too large for defined data type Aug 12 10:10:40 rec-ism-1 vdr: [12960] not enough disk space to start recording timer 1 (1 1009-1014 'Premier League') Aug 12 10:10:40 rec-ism-1 vdr: [12960] warning: Not enough disk space to start recording!
df output: 192.168.120.151:/share/data 11534325760 644983296 10889342464 6% /mnt/data
Regards
Marco
PS: Adding more logging output seems to be harder than I thought yesterday, will try further.
Klaus Schmidinger schrieb:
Hi!
Seems that
if (statfs(Directory, &statFs) == 0)
returns false.
I changed
struct statfs64 statFs; if (statfs64(Directory, &statFs) == 0) {
This works. Recordings are now stored. Is there a better fix for that.
Regards
Marco
Marco Göbenich schrieb:
Hi!
Tried to use
DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE as added in vdr-1.7.4 make.config.template, but this causes other warnings/errors:
recording.c: In constructor ‘cIndexFile::cIndexFile(const char*, bool)’: recording.c:1207: warning: format ‘%ld’ expects type ‘long int’, but argument 3 has type ‘__off64_t’ ... tools.c: In member function ‘ssize_t cUnbufferedFile::Write(const void*, size_t)’: tools.c:1592: error: no matching function for call to ‘min(off_t&, long int)’ tools.c:1611: error: no matching function for call to ‘min(long long int, long unsigned int)’ make: *** [tools.o] Error 1
Regards
Marco
Marco Göbenich schrieb:
Hi!
I have two storage systems here, one has some data ~ 2 TB stored at the storage and one that is empty and that produces this error on the recording machine.
192.168.254.21:/share/tmpvideo 12732465152 11426749952 1305715200 90% /mnt/tmpvideo
The other system is only reachable per VPN and I have only access at office tomorrow, but the most significant change would be the bigger free space value.
Regards
Marco
Thomas Netousek schrieb: