Now I do. I've not needed to mount anything manually since everything is
in /etc/fstab. The output from the mount command during boot goes to the
console but, by default, none of the log files. Consequently, soft-updates
state is never displayed on a standard configuration except for the
messages flying by on the console without some work on the part of the
operator.
Actually, it had never occurred to me that soft-updates was a property of a
file-system and not a global flag in the kernel. That is why I suggested a
more prominent note about soft-updates. In my case (and perhaps others),
write caching was turned off starting in 4.3 with soft-updates still off.
-Michael
At 12:13 PM 5/30/2001, Peter Pentchev wrote:
>On Wed, May 30, 2001 at 10:50:32AM -0400, Michael Adler wrote:
> > Thank you for the tuning page! I and, I fear, others made the mistake
> of
> > assuming that because SOFTUPDATES is in the kernel that it is
> automatically
> > enabled for the disks. Nothing printed during boot leads me to believe
>
> > otherwise and no mention was made of checking the flag using tunefs in
> > /usr/src/UPDATING. My drives formatted with standard methods in the
> past
> > had soft updates disabled.
> >
> > Perhaps there should be a message somewhere prominent encouraging
> people to
> > check whether their drives really have soft updates enabled. It would
> also
> > be useful if something during boot showed whether a mount would be
> using
> > soft updates.
>
>You do realize, don't you, that just issuing a 'mount' command would
>show 'soft-updates' for the filesystems that have soft updates enabled?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
