I just started reading the thread so excuse my ignorance:
Have you mentioned what server you use and how it is configured?
Are you getting anything in the logs?
I don't know if it helps but I have used NFS-root with all sorts of wrong
parameters in fstab (including none at all) for both 2.4 and 2.6 kernels and i
have never experienced the type of problems you are referring to.
I'm writing this because sometimes I find it helpful with messages like "Works
for me" even though they don't actually suggest any solutions. I have no real
time clock on my TS7250 so i let another NFS client write the current time
every minute in a file that is read during bootup. (This is just to avoid a
lot of warnings about modification times in the future during init.) This have
never failed me.
Regards
Per Öberg
-------------------------------------------------------------------------------------
On Thursday 08 April 2010 11.32.40 you wrote:
> --- In <ts-7000%40yahoogroups.com>, Jim
Jackson <> wrote:
> > On Wed, 7 Apr 2010, j.chitte wrote:
> > >>> Where are these settings determined?
> > >>
> > >> Suspect different versions of the nfs mount program have different
> > >> defaults. I'm using the mount in busybox v1.00-rc3.
> > >>
> > >> However you can specify what options you require in the mount command
> > >> you use, or in /etc/fstab . Check the man page for the version of
> > >> mount you are using, or the busybox documentation. (wossat?)
> > >>
> > >> Jim
> > >
> > > sorry I should have said explicitly , I'm booting nfsroot so I don't
> > > think there's much scope for passing parameters.
> >
> > I believe the root partition should remounted with the options specified
> > for / in the /etc/fstab . I always have the noatime option
> > specified for all partitions in fstab, and it always gets actioned
>
> It seems that it is remounted by mount -a , although I don't see it
> documented that it will do a remount implicitly on an already mounted
> device.
>
> I found I had to remove the fstab line in order to get around another
> problem where modifications made programatically on the client were not
> getting committed. This was screwing up my control loop since the adc data
> written to disk never changed during the day. It could write every minute
> for 24h and still see the same thing on read.
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|