Date: Mon, 18 Mar 1996 16:19:43 -0800 (PST) From: Bryan Ogawa at Work <bogawa@netvoyage.net> To: FREEBSD-HACKERS-L <freebsd-hackers@freebsd.org> Subject: Re: Odd-looking files in lost+found after fsck? Message-ID: <Pine.BSF.3.91.960318160855.16108G-100000@digital.netvoyage.net> In-Reply-To: <199603182033.MAA00391@rah.star-gate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Mar 1996, Amancio Hasty Jr. wrote:
> Hi,
>
> The only time that I have seen this is went my old scsi disk was trashing
> about.
> Cheers,
> Amancio
>
> >>> Brian Tao said:
> > Our Web/FTP server had to be rebooted again today after another
> > instance of the "silent hang" problem (pingable, can switch virtual
> > consoles, but no other activity possible). fsck ran and recovered the
> > following files:
[...]
On the silent hang problem, two things:
1. Anecdote:
Our system hung, and when it came back, we had a full /usr .
Culprit: httpd being unable to create a socket (and trying, and
trying, and trying, and trying, and trying, and trying). The log
file ended up being over 2Gig in size. We were running NCSA httpd
1.5a -- we've been having trouble with it, so I'm not sure if it was
NCSA, or the hang, or both together, or NCSA+lots of open files,
or... I'm not sure if this happened before the system hung, or
after, though, so this could be coincidental.
2. Speculation:
Someone had mentioned that a certain thing looked like the system
had stopped switching between different processes. I think that
this system hang looks like that, too (has everyone else made this
connection/dismissed this connection and it just took me this long?)
Aren't the keyboard switch and ping responses interrupt driven
instead of being based on the kernel preempting?
If one process were to run constantly (without anything else to
run), it wouldn't be able to create network sockets, since the tcp
code would never run. I didn't trace through the code that
generates the error carefully, but it might keep trying over and
over, and be unable to do anything (on the other hand, it did seem
to be able to write to the filesystem).
Bryan K. Ogawa
Questions or Problems with NetVoyage? help@netvoyage.net
Check out the NetVoyage HelpWeb at.. <URL: http://www.netvoyage.net/~help/>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960318160855.16108G-100000>