Recommendations on forced disk check
 

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.

Best regards

Rico.




I think that the first recommendation are: BACKUP YOUR DATA!!!.
It shouldn´t have any problem with tune2fs.

Kind regards.
Ramiro


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Recommendations on forced disk check
 

On Wed, May 14, 2008 at 05:27:47PM +0200, Rico Secada wrote:
> 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.

Since the forced checks only happen at boot (or perhaps remount), if the
server is supposed to be available 24/7, it shouldn't be rebooted except
at kernel update time anyway.

I would assume that the people who wrote ext2/3 knew what they were
doing when they implemented forced checks.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Recommendations on forced disk check
 

On Wed, 14 May 2008 17:27:47 +0200
Rico Secada <coolzone@it.dk> 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.
>
> Best regards
>
> Rico.
>

I guess that I'm having trouble understanding what the problem is.
On my servers, e2fsck is only run when the machine is rebooted and
then only after it's been rebooted 30 or 40 times (or whatever the
number is).

--
Raquel
================================================== ==========
Shake off all the fears of servile prejudices, under which weak minds
are servilely crouched. Fix reason firmly in her seat, and call on
her tribunal for every fact, every opinion. Question with boldness
even the existence of a God; because, if there be one, he must more
approve of the homage of reason than that of blindfolded fear.

--Thomas Jefferson


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

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-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Recommendations on forced disk check
 

On Wednesday 14 May 2008 08:27:47 am Rico Secada wrote:
> 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?

Don't. If your machine is truly available as much as possible, the odds of it
running into a fsck are low (and over longer periods of time, it probably
should be done anyway, and hey, since the machine's already down...).

--
Paul Johnson
baloo@ursine.ca

Explaination of .pgp part: http://linuxmafia.com/faq/Mail/rant-gpg.html

Recommendations on forced disk check
 

On Wednesday 14 May 2008 08:57:58 am Raquel wrote:

> I guess that I'm having trouble understanding what the problem is.
> On my servers, e2fsck is only run when the machine is rebooted and
> then only after it's been rebooted 30 or 40 times (or whatever the
> number is).

I think by default it's X number of days, or Y number of reboots to force a
check.

--
Paul Johnson
baloo@ursine.ca

Explaination of .pgp part: http://linuxmafia.com/faq/Mail/rant-gpg.html

Recommendations on forced disk check
 

Douglas A. Tutty wrote:

On Wed, May 14, 2008 at 05:27:47PM +0200, Rico Secada wrote:

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.


Since the forced checks only happen at boot (or perhaps remount), if the
server is supposed to be available 24/7, it shouldn't be rebooted except
at kernel update time anyway.


With ksplice (http://web.mit.edu/ksplice/) even that should not be
necessary!




I would assume that the people who wrote ext2/3 knew what they were
doing when they implemented forced checks.

Doug.





--
Raj Kiran Grandhi
--
Politics is for the moment. An equation is for eternity.
-- Albert Einstein


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org