| View previous topic :: View next topic |
| Author |
Message |
Jay Belanger
n00b
Joined: 01 Feb 2004
Posts: 37
|
 Posted: Mon May 03, 2004 4:09 pm Post subject: Check forced on ext3 partition |
 |
|
I have two main partitions on my hard drive, the root partition and a partition for storage. Both are ext3 partitions.
Every so often when I boot up, there is a file system check forced on my storage partition. I thought that ext3 partitions didn't need that. However, there is never a file system check on my root partition.
So I was wondering: are file system checks necessary for ext3 partitions? And either way, why the discrepency between my two ext3 partitions?
Thanks for any information,
Jay |
|
| Back to top |
|
 |
adaptr
Watchman
Joined: 06 Oct 2002
Posts: 6730
Location: Rotterdam, Netherlands
|
| Posted: Mon May 03, 2004 8:11 pm Post subject: |
|
|
What is the FS check setting in your fstab ?
These are still checked AFAIK.
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
| Back to top |
|
|
Jay Belanger
n00b
Joined: 01 Feb 2004
Posts: 37
|
| Posted: Mon May 03, 2004 8:23 pm Post subject: |
|
|
| adaptr wrote: | | What is the FS check setting in your fstab? |
Well, I feel pretty dumb for not knowing that the fstab had a field for checking, but that doesn't seem to be the problem, since it's 0 for both partitions.
/dev/hda3 / ext3 noatime 0 0
...
/dev/hda4 /attic ext3 defaults 0 0
Thanks for the tip, though.
Jay |
|
| Back to top |
|
|
adaptr
Watchman
Joined: 06 Oct 2002
Posts: 6730
Location: Rotterdam, Netherlands
|
| Posted: Mon May 03, 2004 8:27 pm Post subject: |
|
|
Then the cause is obviously the "defaults" option for mounting 
Simple elimination, Watson...
Check with the man page what exactly is set for ext3 if you use "defaults", and then replace that by its equivalent line and start removing options one by one until the problem goes away...
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
| Back to top |
|
|
Jay Belanger
n00b
Joined: 01 Feb 2004
Posts: 37
|
| Posted: Mon May 03, 2004 8:51 pm Post subject: |
|
|
| adaptr wrote: | | Then the cause is obviously the "defaults" option for mounting |
Ingenious, Holmes! How did you arrive at that deduction?
| Quote: | | Simple elimination, Watson... |
| Quote: | | Check with the man page what exactly is set for ext3 if you use "defaults", and then replace that by its equivalent line and start removing options one by one until the problem goes away... |
Thanks; I'll start doing that.
Jay |
|
| Back to top |
|
|
PowerFactor
Veteran
Joined: 30 Jan 2003
Posts: 1693
Location: out of it
|
| Posted: Mon May 03, 2004 9:11 pm Post subject: |
|
|
| man tuen2fs |
|
| Back to top |
|
|
adaptr
Watchman
Joined: 06 Oct 2002
Posts: 6730
Location: Rotterdam, Netherlands
|
| Posted: Mon May 03, 2004 9:30 pm Post subject: |
|
|
I did - now tell us why it's relevant here ?
The OP did not set any checking options on either FS - yet one does the checks, and the other doesn't.
That's inconsistent behaviour, which is not resolvable by running tune2fs (sic) on one of two filesystems which were probably created with the exact same FS options - in other words, there are no differences to clear out with tune2fs.
AFAIK ext3 runs just the journal check when it is first mounted, and only does the real fsck when the journal does not replay cleanly.
Since the OP did not report any errors it seems unlikely that any were encountered by the kernel.
Hence no need for the check.
And yet it does.
Please read the post next time
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
| Back to top |
|
|
PowerFactor
Veteran
Joined: 30 Jan 2003
Posts: 1693
Location: out of it
|
| Posted: Tue May 04, 2004 12:00 am Post subject: |
|
|
I did read your post, try actually groking the man pages next time.
| Code: | OPTIONS
-c max-mount-counts
Adjust the maximal mounts count between two filesystem checks.
If max-mount-counts is 0 then the number of times the filesystem
is mounted will be disregarded by e2fsck(8) and the kernel.
Staggering the mount-counts at which filesystems are forcibly
checked will avoid all filesystems being checked at one time
when using journaled filesystems.
You should strongly consider the consequences of disabling
mount-count-dependent checking entirely. Bad disk drives,
cables, memory, and kernel bugs could all corrupt a filesystem
without marking the filesystem dirty or in error. If you are
using journaling on your filesystem, your filesystem will never
be marked dirty, so it will not normally be checked. A filesys-
tem error detected by the kernel will still force an fsck on the
next reboot, but it may already be too late to prevent data loss
at that point. |
The "max mount counts" setting affects ext3 same as ext2. If you don't have it set to 0(or -1) then the filesystem will be checked when it reaches that mount count regardless of wheather it is ext2 or ext3. And the man pages states that disabling this is not exactly a good idea(right near the top otherwise I would have took a bit more pains to point it out), especialy on ext3, so I figured you and the OP should be aware of that.
And as far as I can tell what you told the OP was flat out wrong.
- There is nothing set by defaults that would affect periodic filesystem checks as far as I can tell.
- Defaults is implied(because every option it sets is a default) whether or not you actually have it in fstab. You have to specifically set the opposite of ony of the options it sets to disable them. It's more or less just a placeholder for the field in fstab if you don't want any other options.
I had thought that having 0 0 at the end of the fstab line would disable this periodic check, but it doesn't on my redhat box(don't want to reboot my gentoo box right now). I can't account for the discrepancy between tho OP's root and data partitions though. Even if he did create them with the same options they would not have the same max mount count unless he set it specifically. But the difference wouldn't be so large that he would have seen several checks of his data partition and none on his root partition. Unless he mounts and unmounts the data partition sometimes when the system is running.
And I really trying to be helpful with that first post, I was just in a bit of a hurry. |
|
| Back to top |
|
|
PowerFactor
Veteran
Joined: 30 Jan 2003
Posts: 1693
Location: out of it
|
|
| Back to top |
|
|
ian!
Bodhisattva
Joined: 25 Feb 2003
Posts: 3829
Location: Essen, Germany
|
| Posted: Tue May 04, 2004 6:06 am Post subject: |
|
|
Moved to dups.
_________________
"To have a successful open source project, you need to be at least somewhat successful at getting along with people." -- Daniel Robbins |
|
| Back to top |
|
|
|
Duplicate Threads
