On 9/5/20 3:34 PM, [email protected] wrote: ...
Yes we do! I checked a log I had saved from before I did the e2fsck and those values are identical to the post-e2fsck log.
If they are identical, then it would seem that the fsck did not trigger the reallocation. However, what caused the corruption and what caused the reallocation *may* be something different. They may be two separate unrelated events. The runtime of the disk is low. So it is likely that it is the same event. The way to know would be to idenitfy that is if the sectors that were reallocated to are the same area where fsck found the corruption.
That's just a bit too much to get into. I would only worry about it if the reallocated sector count keeps rising.
For always connected disks, smartd is your friend. Best regards, Simon _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
