On Sat, 27 Nov 1999, Eivind Eklund wrote:
> On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote:
> >
> > I'm running a -current system from Nov 26th (approx 4am EST).
> >
> > I can currently reliably crash the system by doing:
> >
> > ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html
> >
> >
> > The crash only works when I do it on a NFS mounted filesystem. I'm
> > using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running
> > softupdates on the exported filesystem. I just checked that local
> > filesystem on the server, and it is a 100% full. Can this just be put
> > down to the known "softupdates full filesystem bug"?
> >
> > [BTW: the server hasn't crashed, it's only the FreeBSD client that
> > crashes]
>
> I *think* I know what this is due to - please upgrade
> src/sys/nfs/nfs_vnops.c to revision 1.146 (which I just committed) and
> try again.
> My bad.
> Eivind.
Ouch! I noticed this problem as a system crash while starting netscape
under the condition that it was able to write the lock file (err soft
link), but since it created the link before the kernel panic I thought it
was a strange FreeBSD->Sun NFS v2 oddity with the profile reading and some
sort of file locking problem.
I will build a fresh -current and let you know if it fixes the problem!
Thanks!
--
Lester Igo
[EMAIL PROTECTED]
http://www.vtic.net/~igo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
