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.

Sign up for GitHub

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

Jump to bottom

Detect unexpected changes (AKA "hardware corruption") #2

Closed
moy opened this issue Sep 9, 2015 · 0 comments
Closed

Detect unexpected changes (AKA "hardware corruption") #2

moy opened this issue Sep 9, 2015 · 0 comments
Assignees
@evrignaud
Labels
enhancement
Milestone
1.0.3

Comments

@moy
Copy link

moy commented Sep 9, 2015

fim is good at finding which file changed in a normal way.

It would be nice to have a way to find changes most likely caused by a hardware corruption or a filesystem bug: change in content, but not in any of the timestamps (ctime, mtime). This could be done by filtering fim diff to only show changes to files having unmodified timestamp since last commit.
evrignaud added a commit that referenced this issue Sep 24, 2015
@evrignaud
Fix issue #2. Add the 'fim corrupt' command that find changes most li…
2410649 
…kely caused by a hardware corruption or a filesystem bug. Change in content, but not in creation time and last modified time
@evrignaud evrignaud self-assigned this Sep 25, 2015
@evrignaud evrignaud added this to the 1.0.3 milestone Sep 25, 2015
evrignaud added a commit that referenced this issue Oct 9, 2016
@evrignaud
✨ fdup command is now able to remove duplicates (part #2)
dab34b0
evrignaud added a commit that referenced this issue Oct 9, 2016
@evrignaud
✨ fdup command is now able to remove duplicates (part #2)
583757c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@evrignaud evrignaud

Labels
enhancement
Projects
None yet
Milestone
1.0.3
Development

No branches or pull requests
2 participants
@moy @evrignaud