Unresponiveness of 2.4.16 revisited
Quoted 4 lines · Andrew Morton
If you can generate hard numbers (just time the RP command, for a start) and they show regression, then go ahead and post!
Quoted 8 lines
Let's put the atime thing down as a known ext3 problem for a while. (does it happen with ext2? You sure?).
Running noatime won't hurt a thing. It just prevents the kernel from recording when a file was last accessed, within the file's inode. It's a feature whichis used by backup/archiving programs, and probably by mailbox monitoring programs (xbiff, etc). People turn it off all the time...
ok, I doubled checked things. It seems mounting an ext3 filesystem as ext2 is somewhat a myth. If the kernel supports ext3 it still mounts it as ext3 even if /etc/fstab says ext2. When I tried 2.4.16 with ext3 support, but with the journal exactly removed to make it a ext2 filesystem the --rebuild worked just like it does in 2.4.9-13. So it does seem to be a problem with just ext3, and I guess they changed the journaling of atimes between the version in 2.4.9-13 and 2.4.16. It all now makes sense. Thank you for your help.
As for my comment before and Rik's VM vs AA's VM on cache agressiveness, it looks like I was off. It just seems to vary on some dynamic. I thought I checked them at the same points after boot, but between different boots seemed to get different results, who knows.
Quoted 3 lines · Nathan G. Grennan
ok, I doubled checked things. It seems mounting an ext3 filesystem as ext2 is somewhat a myth. If the kernel supports ext3 it still mounts it as ext3 even if
/etc/fstabsays ext2.
really on other partitions than root-fs ?
Signature · 1 line
Oktay Akbal
Quoted 10 lines · Oktay Akbal
Quoted 3 lines · Nathan G. Grennan
ok, I doubled checked things. It seems mounting an ext3 filesystem as ext2 is somewhat a myth. If the kernel supports ext3 it still mounts it as ext3 even if
/etc/fstabsays ext2.really on other partitions than root-fs ?
Signature · 1 line
Oktay Akbal
I am not positive about mounting non-root filesystems. I would suspect it is just a problem with root filesystems.
Quoted 11 lines
Quoted 8 lines
Quoted 3 lines
ok, I doubled checked things. It seems mounting an ext3 filesystem as ext2 is somewhat a myth. If the kernel supports ext3 it still mounts it as ext3 even if
/etc/fstabsays ext2.really on other partitions than root-fs ?
Signature · 1 line
Oktay AkbalI am not positive about mounting non-root filesystems. I would suspect it is just a problem with root filesystems.
Why do you think that fstab matters for root-fs ? root-fs needs to be mounted to read fstab. So autodetection must be done for root-fs. And if the fs has a journal it is ext3. If you do not want that behaviour you might use a option to lilo, but I don't know of any option to specify the root-fs-tyoe. Or you need to use an initrd to mount explicit as ext2 and pivot-root it to / ?
Signature · 1 line
Oktay Akbal
Quoted 9 lines · Oktay Akbal
Why do you think that fstab matters for root-fs ? root-fs needs to be mounted to read fstab. So autodetection must be done for root-fs. And if the fs has a journal it is ext3. If you do not want that behaviour you might use a option to lilo, but I don't know of any option to specify the root-fs-tyoe. Or you need to use an initrd to mount explicit as ext2 and pivot-root it to / ?
Signature · 1 line
Oktay Akbal
Actually, I think it should respect fstab. It does mount it, then fsck it while mounted read-only, then remounts(key point) read-write. IMHO it should remount it with whatever fstab says. I realize this could be a little tricky, but I bet doable.
Quoted 9 lines · Nathan G. Grennan
Quoted 3 lines · Oktay Akbal
Why do you think that fstab matters for root-fs ? root-fs needs to be mounted to read fstab. So autodetection must be done for root-fs. And if the fs has a journal it is ext3.
Actually, I think it should respect fstab. It does mount it, then fsck it while mounted read-only, then remounts(key point) read-write. IMHO it should remount it with whatever fstab says. I realize this could be a little tricky, but I bet doable.
Well, then you would be wrong. The only case where this really matters is if you are using ext3/ext2 because all other cases will be autodetected as only a single fs type (OK, maybe msdos/vfat, but who would use that as root, I don't know, and it still has the same issues).
Once the root filesystem is mounted, and init (+ rc.sysinit or whatever your startup scripts are) is run, your filesystem is in use. How do you expect to remount it as a different filesystem while it is in use? Note that _today's_ ext2 and ext3 are totally separate drivers, so you cannot "remount" from one driver to another. Maybe in the future it would be possible for the ext3 filesystem driver to support ext2 (i.e. unjournaled), but not today, and it would be even less likely to allow stopping journaling on the filesystem once it is started (journaling is complex business).
Quoted 4 lines
Quoted 4 lines
If you do not want that behaviour
you might use a option to lilo, but I don't know of any option to specify the root-fs-tyoe. Or you need to use an initrd to mount explicit as ext2 and pivot-root it to / ?
Well, the lilo option you want is "rootfstype=ext2". It is part of 2.4.15. Put it into an "append=" statement in lilo (per kernel, or global). Even so, 99.9% of people who can use ext3 do not want to go back to ext2.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
Quoted 8 lines · Nathan G. Grennan
Quoted 6 lines · Oktay Akbal
Why do you think that fstab matters for root-fs ? root-fs needs to be mounted to read fstab. So autodetection must be done for root-fs. And if the fs has a journal it is ext3. If you do not want that behaviour you might use a option to lilo, but I don't know of any option to specify the root-fs-tyoe. Or you need to use an initrd to mount explicit as ext2 and pivot-root it to / ?
Quoted 4 lines
Actually, I think it should respect fstab. It does mount it, then fsck it while mounted read-only, then remounts(key point) read-write. IMHO it should remount it with whatever fstab says. I realize this could be a little tricky, but I bet doable.
Using the precognition() system call no doubt. It can't read fstab without mounting, how can kernel use fstab to mount to read fstab? Original response was correct, you need to learn to use initrd.
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.