Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase verbosity #19

Merged
merged 2 commits into from
Oct 29, 2016
Merged

Increase verbosity #19

merged 2 commits into from
Oct 29, 2016

Conversation

vain
Copy link
Contributor

@vain vain commented Sep 21, 2016

Don't suppress some warnings when verbosity == 0. See the individual commit messages on why I think this is a good idea. :-)

I get that this is some kind of a grey area due to the underlying race
condition (files vanishing after they have been scanned). However, if we
can't stat() a file it can have many different causes -- the file being
vanished is just one of them. Since this tool is meant to help detect
bit rot and corrupt file systems, I'd rather be informed about
un-stat-able files.
I had a semi-corrupt encfs (which I detected, thanks to this tool!). A
file was only partially readable. Somewhere in the middle, an IOError
occured. Essentially, this is a corrupt file system -- which this tool
is meant to help detect --, so this class of errors shouldn't be
suppressed by "-q".
@ambv ambv merged commit 8cfdf0c into ambv:master Oct 29, 2016
@ambv
Copy link
Owner

ambv commented Oct 29, 2016

I like those changes, makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants