Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Feb 2008 12:15:57 +1100
From:      Sean <sean@gothic.net.au>
To:        Dominic Fandrey <LoN_Kamikaze@gmx.de>
Cc:        freebsd-current@freebsd.org
Subject:   Re: nfs mounts don't work through fstab
Message-ID:  <0FD9F726-6E45-4A81-9DE1-E3F0AAF3668B@gothic.net.au>
In-Reply-To: <47BB01BE.4010309@gmx.de>
References:  <47BADE07.9020402@gmx.de> <7CZsNG/ix1SXULta6Bdgf51ZwDE@TqmFlxFMySuiJ36EgnrGRgt6KQ8> <47BB01BE.4010309@gmx.de>

next in thread | previous in thread | raw e-mail | index | archive | help
 From FreeBSD 5.5 (the earliest I can check readily)

fstab(5)

      The fourth field, (fs_mntops), describes the mount options  
associated
      with the file system.  It is formatted as a comma separated list  
of
      options.  It contains at least the type of mount (see fs_type  
below) plus
      any additional options appropriate to the file system type.  See  
the
      options flag (-o) in the mount(8) page and the file system  
specific page,
      such as mount_nfs(8), for additional options that may be  
specified.


So the fs_type (rw, ro, etc.) has always been documented as  
obligatory, though in slightly less than obvious wording.


On 20/02/2008, at 3:20 AM, Dominic Fandrey wrote:

> Eygene Ryabinkin wrote:
>> Dominic, good day.
>> Tue, Feb 19, 2008 at 02:47:51PM +0100, Dominic Fandrey wrote:
>>> My nfs mounts haven't been working by their fstab entries, ever  
>>> since I switched to RELENG_7. Today I took the time tracking the  
>>> issue down by adding lots of printf to mount.c. I tracked the  
>>> problem down to the function
>>> fstabscan() in the file "/usr/src/lib/libc/gen/fstab.c".
>>>
>>> The result of my testing was that it is now obligatory to set  
>>> 'sw', 'ro' or 'rw' in the options list.
>> Could you, please, show your /etc/fstab?  I see that lib/libc/gen/ 
>> fstab.c
>> was last changed 4 years ago (not counting revision 1.15, where the
>> advertising license clause was removed), so perhaps fstabscan() is
>> not guilty.
>> Thank you!
>
> These 2 lines have been in use since 6.0 release:
>
> mobileKamikaze:/usr/src /usr/src nfs -b,-T,-R=5,noauto 0 0
> mobileKamikaze:/usr/obj /usr/obj nfs -b,-T,-R=5,noauto 0 0
>
> They stopped working with the switch to RELENG_7.
>
> # mount /usr/src/                                      0 /root
> fstab: /etc/fstab:27: Inappropriate file type or format
> fstab: /etc/fstab:28: Inappropriate file type or format
> fstab: /etc/fstab:27: Inappropriate file type or format
> fstab: /etc/fstab:28: Inappropriate file type or format
>
> mount: /usr/src: unknown special file or file system
>
> fstabscan() is the place where the "Inappropriate file type or  
> format" error is printed. The pointer char* cp either points to a  
> string "rw", "ro" or "sw". If none of these are present cp is a NULL- 
> pointer when the final check in line 207 is reached. So  
> error(EFTYPE) is called.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org 
> "
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0FD9F726-6E45-4A81-9DE1-E3F0AAF3668B>