Recent changes to bugs

#15 cfv fails to detect files with trailing spaces in sfv file

Viper Omega — Mon, 15 Aug 2022 07:11:23 -0000

fix in line 1670:
self.test_file(x.group(1).strip(),unhexlify(x.group(2)))
#self.test_file(x.group(1),unhexlify(x.group(2)))

Future of cfv

lxp — Wed, 13 Mar 2019 22:12:09 -0000

Hello,

cfv is my favorite checksumming tool since nearly a decade. Matthew and all
contributors, I want to thank you for writing this great tool and all effort you
put into it!

I recently installed a Debian buster system and I wanted to do a simple

apt install cfv

However, that did not work, because cfv was removed from Debian buster.

I am writing all this because I think development of cfv has stalled and I want
to change that.

I like the tool and care for it, that's why I have started a repository at
Github [1] for continuing development of cfv.

Anybody is welcome to join me!

Stay tuned for an upcoming 2.0 release of cfv

Best regards,
David Gnedt

[1] https://github.com/cfv-project/cfv

#18 "-q" flag is causing a oom-kill

folti_ — Thu, 12 Jan 2017 05:47:06 -0000

"export CFV_NOMMAP=" exports the variable with a zero length string, whose detection is buggy with thecurrent code (and in shell scripts too), as zero length string is evaluated as False, which is means the value not set. So cfv doesn't care about the value of the variable, only that it have some non-zero string value.

That's why these kind of variables are always set with some variable that's not an empty string.

cksfv don't have this problem, as it doesn't use mmap.

#18 "-q" flag is causing a oom-kill

MisterE2002 — Wed, 11 Jan 2017 22:44:42 -0000

see my reaction below :)

#18 "-q" flag is causing a oom-kill

MisterE2002 — Wed, 11 Jan 2017 22:38:02 -0000

i tried a couple of times. It seems to help. In fact, if i use "export CFV_NOMMAP=0" it works also.
It seems to fail every time if i use "export CFV_NOMMAP="

To be honest, i switch to using "cksfv" instead.
Thanks for your reply.

#18 "-q" flag is causing a oom-kill

folti_ — Wed, 21 Dec 2016 21:56:09 -0000

Hi,

if the problem still persist, could you try to run the errorneous commands with the CFV_NOMMAP=1 environment variable set?

For example:
CFV_NOMMAP=1 cfv -C -q -f /root/tmp.csv "/mnt/vboxsf_share/file"

Problem could be that your VM is limited memory wise, and reading through mmap accidentally consumes too much memory, triggering the OOM killer.

And it doesn't cause a problem without -q, because writing to the terminal inserts small delays in the file reading operation, allowing the kernel to shuffle around the data in the buffers.

"-q" flag is causing a oom-kill

MisterE2002 — Sun, 25 Sep 2016 09:29:58 -0000

Can someone help with debugging this strange problem. The "-q" flag is causing a oom-kill in my debian VM. And the process is terminated with exit code 137.

Situation:
I have a freenas box. This box is exporting a share "/mnt/tank/vboxsf_share"
It is running a jail with Virtualbox. In the VM i am running a Debian instance.
I mount the share with this command.
mount -t vboxsf -o rw vboxsf_share /mnt/vboxsf_share/
So, now i have a loopback to the freenas share (without using the network overhead)

After i switched i noticed the crash of a script of mine. I traced it to the "-q" flag.
If i omit this flag everything is working, but i have have "output" (and i am not sure if it will output exit codes?)
It is reproducable. All other hash calculation programms (cksfv/md5sum/sha1sum) execute normally.

I can not enable verbose logging because this solves the problem :P

It looks like this fix "Work around bug in Python (only manifests with 64-bit Python version >= 2.5) which causes checksums of files > 4GB to be incorrectly calculated (when using mmap, eg, when the progress meter is disabled or not shown."
But this is fixed in version v1.18.2 (https://sourceforge.net/p/cfv/code/415/), and i am using version 1.18.3-2 (official packaged version)

KILLED:
cfv -C -q -f /root/tmp.csv "/mnt/vboxsf_share/file"

NOT KILLED:
cfv -C -f /root/tmp.csv "/mnt/vboxsf_share/file"

KILLED:
cfv -C -tmd5 -q -f /root/tmp.csv "/mnt/vboxsf_share/file"

NOT KILLED:
cfv -C -tmd5 -Q -f /root/tmp.csv "/mnt/vboxsf_share/file"

#17 unable to scan big files

Matthew Mueller — Wed, 13 Feb 2013 08:44:53 -0000

Hi, sorry for slow reply. Could you test whether it works if you set the environment variable CFV_NOMMAP=1 first?

unable to scan big files

lekillerderpg — Fri, 21 Sep 2012 17:43:20 -0000

hi! ^^

xp pro sp3 32 bits / 4go of ram / i5 2500

when i launch a verification with a checksums file (crc32/*.sfv or md5/*.md5 or sha1/*.sha)

i get this messages errors:
-"access blocked" for file equal or bigger than 4gB
-"insufficient space" for file of 1.37gB

with an other verification software i don't have this problem

cfv is unable to recognize the type of md5summer files

evildeeds — Sat, 03 Sep 2011 01:22:53 -0000

cfv is unable to recognize the type of md5summer files, http://www.md5summer.org/
As far as I can tell they are just md5 files but contain a empty line before the filelist begins.