Hi!
I'm justing in the process of setting up a new fileserver for our company. I'm installing CentOS 5.3 (64 bit) on it.
One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3. Now my experience with our current fileserver is that a 0.5TB ext3 filesystem needs approx half an hour to complete (and kicks in every so and so reboots or every 180days). My estimate is that for the larger filesystem (and the faster machine) the fsck would need well over an hour (being optimistic). I dread the day when I have to reboot the server and wait for 2hours or more just because the system thought it would be a prudent thing to check the filesystem.
My question:
- is there another stable filesystem (XFS, ReiserFS ...) in the centosplus-kernel where this could be avoided (fsck is faster) and that is as safe as ext3 - Or would it be better to switch off automatic checking with tune2fs
Any opinion/experience welcome. I looked around a bit but couldn't find a good answer
Bernhard
PS: Sorry for the stupid question, but I'm only part-time admin and testing this myself would take weeks, I guess
On Thu, May 14, 2009 at 05:44:11PM +0200, Bernhard Gschaider wrote:
Hi!
I'm justing in the process of setting up a new fileserver for our company. I'm installing CentOS 5.3 (64 bit) on it.
One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3. Now my experience with our current fileserver is that a 0.5TB ext3 filesystem needs approx half an hour to complete (and kicks in every so and so reboots or every 180days). My estimate is that for the larger filesystem (and the faster machine) the fsck would need well over an hour (being optimistic). I dread the day when I have to reboot the server and wait for 2hours or more just because the system thought it would be a prudent thing to check the filesystem.
My question:
- is there another stable filesystem (XFS, ReiserFS ...) in the centosplus-kernel where this could be avoided (fsck is faster) and that is as safe as ext3
- Or would it be better to switch off automatic checking with tune2fs
Yes, you could use XFS. Or, use tune2fs on the filesystem to disable the automatic checking:
# tune2fs -c 0 -i 0 /dev/whatever
See tune2fs(8) for more information. The -m 0 parameter may also be useful as by default 5% of blocks are "reserved" (useful for root filesystems).
Any opinion/experience welcome. I looked around a bit but couldn't find a good answer
Bernhard
PS: Sorry for the stupid question, but I'm only part-time admin and testing this myself would take weeks, I guess
Ray
2009/5/14 Bernhard Gschaider bgschaid_lists@ice-sf.at:
One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3.
Yes, using ext3 is a real pain especially on such large partitions. I advice you to switch to XFS.
Bernhard Gschaider wrote:
Hi!
I'm justing in the process of setting up a new fileserver for our company. I'm installing CentOS 5.3 (64 bit) on it.
One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3. Now my experience with our current fileserver is that a 0.5TB ext3 filesystem needs approx half an hour to complete (and kicks in every so and so reboots or every 180days). My estimate is that for the larger filesystem (and the faster machine) the fsck would need well over an hour (being optimistic). I dread the day when I have to reboot the server and wait for 2hours or more just because the system thought it would be a prudent thing to check the filesystem.
My question:
- is there another stable filesystem (XFS, ReiserFS ...) in the centosplus-kernel where this could be avoided (fsck is faster) and that is as safe as ext3
- Or would it be better to switch off automatic checking with tune2fs
Any opinion/experience welcome. I looked around a bit but couldn't find a good answer
Bernhard
PS: Sorry for the stupid question, but I'm only part-time admin and testing this myself would take weeks, I guess
If you use ext3 on LVM, you could every once in a while make a snapshot of the fs & do a background fsck on the snapshot.
https://www.redhat.com/archives/ext3-users/2008-January/msg00032.html
On Thu, May 14, 2009 at 8:44 AM, Bernhard Gschaider bgschaid_lists@ice-sf.at wrote:
One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3.
An option I haven't seen suggested yet is to split this into several filesystems that can be fsck'd in parallel.
Am 14.05.2009 um 21:25 schrieb Bart Schaefer:
On Thu, May 14, 2009 at 8:44 AM, Bernhard Gschaider bgschaid_lists@ice-sf.at wrote:
One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3.
An option I haven't seen suggested yet
For a reason, believe me.
is to split this into several filesystems that can be fsck'd in parallel.
The eighties called - they want their stone-age way to handle disks back....
Rainer
On Thu, May 14, 2009 at 2:12 PM, Rainer Duffner rainer@ultra-secure.de wrote:
The eighties called - they want their stone-age way to handle disks back....
Heh. Well, if he wants them fsck'd in the first place ...