[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Whose bug is this?



On Fri, Nov 16, 2001 at 01:40:05AM +1100, Martijn van Oosterhout wrote:
> 
> I had this problem once (I forget exactly what) but I solved it differently.
> I edited the umountfs script so that it first went through and remounted all
> the partitions read-only. Since the library is open but not writable this
> succeeds.

umm, he wrote:

	the S40umountfs script is executed (/etc/init.d/umountfs).  This
	script basically does an 'umount -a -r'.

now from man umount:

       -r     In case unmounting fails, try to remount read-only.

so if you had to change anything to accomplish this then mount needs a
bug reported against it, i can say that umount -a -r works as
documented in potato since my chroot partition always fails to umount
since umount -a seems to not bother with the extra /proc mounted under
there...  i simply get a warning that umount failed, remounting ro and
it works, no fsck etc.

> The umount still fails but since the drive isn't read-write on the reboot,
> no fsck on next boot.

yes this should be standard behavior under unmodified debian.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgpML8f77J8NX.pgp
Description: PGP signature


Reply to: