HAMMER2 is Copy on Write, meaning changes are made to copies of existing data. This means operations are generally atomic and can survive a power outage, etc. (You should read up on it!) However, there’s now a fsck command, useful if you want a report of data validity rather than any manual repair process.
2 Replies to “HAMMER2 and fsck for review”
Comments are closed.
How spinning up a new compute node on an IaaS service like AWS, Google Cloud etc – should the first thing you do is run fsck to ensure you were provisioned a compute node with a bad disk?
I know with cheaper cloud services they get super aggressive in reusing repaired hard drives.
@Anonymous
at least AWS checks the underlying storage for you ( -> https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-volume-status.html )
So running fsck is considered harmful https://unix.stackexchange.com/questions/45422/should-i-run-fsck-on-boot-for-an-amazon-ec2-image