Jakub Kruszona-Zawadzki
Jakub Kruszona-Zawadzki
STRICT is a "creation mode" - not "keep mode", so STRICT does not apply to labels defined in KEEP. As I remember I wrote you long answer with explanation -...
I didn't forget about it. I have some nice ideas how to improve this - but as for now I have to release 3.0.107 due to other issues, so this...
It looks rather strange. I will add more syslog messages to background data writer and we will see why it is exiting. One reason might be exiting after unsuccessful memory...
Sending the same logs will not make any difference. Still you are probably the only person in the whole world with such problem. We cannot reproduce it. Our MFS never...
I don't think that those messages are related - but since we still don't know what causes this I can't be sure. BTW. Did @oxide94 send you packages?
Just checked my FreeBSD and I don't see the problem: ``` # ./test.sh 0 1st ls: ./temp.tmp 2nd ls: ls: ./temp.tmp: No such file or directory Line 1 of test...
Just to clarify. Deleted and open files are preserved in this case. The thing is that sometimes it could be a problem with accessing them due to 'getattr' done by...
Ad. 2 - The problem is on MFS side truncate returns OK, but with incorrect attributes - fixing
Hmm. With default settings we were able to saturate 100Gb (using libmfsio and many threads of course). The readaheadleng is actually multiplied by a factor that is increased when subsequent...
I don't think that network latency is so important when we are reading huge sequential files - low latency is rather needed for reading small files or reading one file...