misc/118160: unable to mount / rw while booting 7.0-BETA3

Gary Palmer gpalmer at FreeBSD.org
Tue Nov 27 20:10:05 PST 2007

The following reply was made to PR bin/118160; it has been noted by GNATS.

From: Gary Palmer <gpalmer at freebsd.org>
To: Yuri <yuri at rawbw.com>
Cc: Bruce Evans <brde at optusnet.com.au>, Yuri <yuri at tsoft.com>,
	freebsd-gnats-submit at freebsd.org, freebsd-bugs at freebsd.org
Subject: Re: misc/118160: unable to mount / rw while booting 7.0-BETA3
Date: Tue, 27 Nov 2007 23:06:20 -0500

 On Tue, Nov 27, 2007 at 07:11:52PM -0800, Yuri wrote:
 > > > While booting log says:
 > > > Starting file system checks:
 > > > <here goes the list of file systems that it reports, this is ok>
 > > > mount:  : Operation not permitted.
 > > 
 > > This is probably a secondary problem.  You apparently have the root device
 > > mounted on "" or something like that.
 > > What does mount shouw for the root device?
 > > 
 > No, when I get to shell after this failure during the normal boot process
 > mount shows:
 > /dev/ad12s1c    /   (ufs,local,read-only)
 > swapinfo shows that swap volume is /dev/ad12s1b
 Is your root partition really on the "c" partition?  The "c" partition
 represents the whole disk slice.  Sure you don't mean ad12s1a?
 The conflict between using the c partition and swap on the b partion
 (which logically is a subset of the entire slice) could be the cause
 > > > The major bug seems to be in the 'mount' system call. 'man mount' says that
 > > EPERM is returned if "The caller is neither the super-user nor the owner of
 > > dir." I am root.
 > > 
 > > You are apparently attempting to mount the same device twice (even though
 > > -u specifies an already-mounted device, the kernel is apparently confused
 > > about where it is mounted).
 > > 
 > I thought that mount command is supposed to pick up the locations correctly,
 > so that when I say 'mount -uw /' device should be picked up from the already
 > mounted list.
 > Also I found that swapon and mount are related in my case. Once swapon is done
 > I can't remount root as r/w. And vice versa, when mount -uw is done swapon
 > returns EPERM.
 > This happens when I boot as single user. When I do swapon consecutive
 > 'mount -uw ' fails. When I do 'mount -uw' consecutive swapon fails.
 > So I don't have swap at all since this command failed during boot.
 > I guess 'nmount' and 'swapon' system calls are similar and somehow interfere
 > with each other.
 > So I still can't boot normally, only through single user mode and I don't
 > have swap at all after this.
 > Yuri
 > _______________________________________________
 > freebsd-bugs at freebsd.org mailing list
 > http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
 > To unsubscribe, send any mail to "freebsd-bugs-unsubscribe at freebsd.org"

More information about the freebsd-bugs mailing list