On Wed Dec 19, 2012 at 03:16:22PM -0800, Ross Boylan wrote:
> On 12/19/2012 2:30 PM, Robin Hill wrote:
> > Otherwise, the issue could be filesystem corruption. A "fsck -f" on the
> > array should detect that.
> I think that's my next step. My understanding is that this guarantees
> the integrity of the file system, but not necessarily the integrity of
> the contents of individual files. I'm on ext3.
>
To check the files themselves, you'll have to have some info on their
correct state. A lot of distributions will include this as part of the
packaging, so that should be your first port of call (e.g. rpm
--verify). I'm not aware of any other way to verify the file contents
without previously having read their correct state (there's various file
integrity checking tools, intended for security checks to prevent
surreptitious replacement of system files).
HTH,
Robin
--
___
( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
Attachment:
pgp9dBsMjJuCs.pgp
Description: PGP signature
