ext2 drives under 5.3 not umounting on reboots

[M. Parsons]

c0ldbyte wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, 16 Apr 2005, M. Parsons wrote:
>
>> I have a ext2 linux partition mounted under /linux via the fstab line:
>>
>> /dev/ad2s1             /linux          ext2fs  rw              1       2
>>
>> It will automount on bootup, but if I do a reboot or shutdown -h now, 
>> it doesnt get umounted properly.  In fact, if this /linux is mounted, 
>> then /, /usr, /var, and /tmp (all seperate ufs slices on another hard 
>> drive) also get tainted during a reboot.  And on the next startup I 
>> get the good ole: WARNING: /usr was not properly dismounted, leaving 
>> me to fsck the drives in single mode (which sucks, as the fbsd 
>> machine is a headless NAT machine). Running fsck in single mode does 
>> fix everything.
>>
>> So whats going on here?  reboot aint properly umounting partitions, 
>> and fsck doesnt seem to be properly running during bootup if it 
>> detects tainted filesystems.
>>
>> Any ideas?
>>
>> Freebsd 5.3 SMP kernel.
>
>
> Try this line:
> /dev/ad2s1             /linux          ext2fs  rw              0       0
>
> But remember the ext2 code has been buggy for a while and is not allways
> a good choice to try and do writes on it. Might be a better choice to
> change rw to ro and to also check that drive/partition for errors with
> its original fsck to fix any errors if there is any then it will most
> likely mount properly and umount properly.
>
> Best of luck,
>     --c0ldbyte

Well, I just said screw it, backed up the files I needed, then converted 
the whole disk to UFS.  Time to wash my hands clean of linux anywas. :-)

Still sort of worried that reboot wasnt unmounting the linux drive, but 
oh well, no more worries now. :)

Mark