[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Recommendations on forced disk check



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2008-05-14 17:32, Ramiro Caire wrote:
> Rico Secada wrote:
>> Hi.
>>
>> What are your recommendations on using tune2fs to turn off the forced
>> HD check on a server that needs to be available as much as possible?
>>
>> If the forced check is shut off, should one run some manual check? Also
>> I don't have physical access to the machine only SSH.
>>   
> I think that the first recommendation are: BACKUP YOUR DATA!!!.
> It shouldn´t have any problem with tune2fs.

You are right, one should regularly backup the data. But any backup
software will backup what it reads, so if -- for any reason -- that data
gets corrupted, your next backup might get the corrupted data, too.

One way to check for corruption to the file system is to regularly fsck it.

There will never be perfect security for your data no matter how careful
you are. For me the care for my data includes regular file system checks
as well as the occasional 'diff -r' of data and backup. ('diff -r' once
gave me the surprise of diffs in some of my jpg-files. It turned out
some images on the backup were corrupted. fsck was ok on this just one
year old drive. )

One could argue about the frequency of those file system checks. With a
journalling file system, the frequency could probably be reduced. On the
other hand this also depends on the amount of data written/changed per
time interval and how important that data is, and how rapidly you want /
need to get aware of any problems.

If your data is important, I'd recommend a combination of
- - raid
- - several backups on different media
- - regular fsck's
- - regular diff's
- - at least two computers involved (so hopefully the hardware won't fail
on both simultaneously)

HTH, take care, good luck!

Johannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIKw6FC1NzPRl9qEURAggOAJ40vZXv6iA/dqjCm/Q4ohx0QEnfcQCcCeTw
Ed0wz+n0KjY6bEEmMp4Q6fY=
=GxHF
-----END PGP SIGNATURE-----


Reply to: