Messages in this thread | | | From | Andreas Dilger <> | Date | Fri, 12 Jul 2002 10:39:28 -0600 | Subject | Re: ext2 'remount' problem |
| |
On Jul 12, 2002 08:53 -0400, Richard B. Johnson wrote: > If file-systems are mounted upon boot with 'defaults' as options > > like /etc/fstab... > /dev/sdc1 /alt ext2 defaults 0 2 > > mount -o remount,rw,noatime /alt > > The result is (correctly) > /dev/sdc1 /alt ext2 rw,noatime 0 0 > > Now, if I shut down the system, properly dismounting all the drives, > then I reboot, the drives that were re-mounted end up being fscked > due to 'was not cleanly unmounted' inference. Nothing wrong is found. > > Now, if I mount the drives "noatime" from the start, i.e., from > /etc/fstab upon startup, there are no such errors upon re-boot.
There was once a problem that if you mounted a filesystem and crashed shortly thereafter the filesystem would mistakenly be marked clean and not checked when it should be, but I haven't heard the opposite problem.
I did a quick check (just mounting an ext2 filesystem on 2.4.18 from bash, remounting, then unmounting) and everything worked as expected. Could you try doing your test and running "dumpe2fs -h /dev/foo" between each step to check the filesystem state. It should be "not clean" until the filesystem is unmounted, at which point it should be "clean".
Also try doing the unmount steps manually before shutdown to see if it is a timing issue. If you have writeback cache enabled on your disks and this is not being flushed to the oxide before power is lost you may not just be having an fsck problem, but also a data loss/corruption problem.
Cheers, Andreas -- Andreas Dilger http://www-mddsp.enel.ucalgary.ca/People/adilger/ http://sourceforge.net/projects/ext2resize/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |