Policy after fsck fixes errors

[Joseph D. Wagner]

> > It's also possible I suppose that data
> > blocks were actually corrupted, but that really depends on
> > how the inode table blocks got corrupted in the frist
> > place.
> >
> 
> This is what really troubles me.  If the problem is in a
> library or some seldom-used but essential utility then I am
> going to be in trouble when I am not expecting it.
> 
> I really should bring my backup up-to-date in any case.
> If smartmontools don't reveal any hardware problems then the
> best strategy must be to substitute the backup for my
> current, drive do the update, then copy back to the the
> current drive.

Did you take the time to check for bad blocks?