Re: mount option <rw> is unknown

From: Steve Kargl <sgk_at_troutmask.apl.washington.edu>
Date: Tue, 3 Jan 2006 15:34:58 -0800
On Tue, Jan 03, 2006 at 01:23:18PM -1000, Randy Bush wrote:
> >> 7-current system as of nov 27
> >> cvsupped
> >> removed CFLAGS and COPTFLAGS from make.conf
> >> built and installed kernel and world
> >> fsck ran fine
> >> when it went to mount file systems,
> >>     mount option <rw> is unknown
> >>     mount: /dev/da0s1a: Invalid argument
> >> this fstab was last touched in nov 2004, over a year ago
> >> had to do 
> >>     /rescue/mount -u -w /dev/da0s1a /
> >> and so on for all filesystems.  then had to comment out fstab
> >> so i could go multi.
> > http://lists.freebsd.org/pipermail/freebsd-current/2005-December/059330.html
> > http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/mount/mount.c
> > Backwards compatibility was broken in rev. 1.7 in mount.c
> 
> no comprendo
> 

The first URL notes the same problem with "mount option <rw> is unknown".
The second URL points to the CVS repository for sbin/mount/mount.c.  It
should have read "rev. 1.77".  In particular,

   Revision 1.77 / (download) - annotate - [select for diffs], Sat Dec 3
   01:57:58 2005 UTC (4 weeks, 3 days ago) by rodrigc
   Branch: MAIN
   Changes since 1.76: +1 -1 lines
   Diff to previous 1.76 (colored)

   Simplify parsing of mount options by passing
   "rw" option down to kernel, since vfs_donmount() can now parse it.

"Simplify" is a misspelling of "Break possibility of using older
kernels with newer sbin/mount command".  This, of course, makes 
panic recovery more difficult.

I don't recall what the outcome of using a newer kernel with an
old sbin/mount is.
-- 
Steve
Received on Tue Jan 03 2006 - 22:35:00 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:50 UTC