Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Mar 2000 09:52:17 +0200 (IST)
From:      Nadav Eiron <nadav@cs.Technion.AC.IL>
To:        Jim Mercer <jim@reptiles.org>
Cc:        hackers@freebsd.org
Subject:   Re: spontaneous reboots FreeBSD 3.x and 4.0-stable
Message-ID:  <Pine.GSO.3.95-heb-2.07.1000321094543.21518A-100000@csd>
In-Reply-To: <20000321024104.S15100@reptiles.org>

next in thread | previous in thread | raw e-mail | index | archive | help


On Tue, 21 Mar 2000, Jim Mercer wrote:

> 
> i've got two systems, one a pentium 233 with adaptec 2940, scsi, using vinum
> running a big postgresql database, and a new one, dual pentium 550, dual adaptec
> 29160, not using vinum, and another big postgresql database.
> 
> the first system runs 3.4-stable and gets spontaneous reboots infrequently,
> and there are no messages (dmesg, console or syslog) indicating why it rebooted.
> 
> initially, i though it might be the vinum.
> 
> the new system runs 4.0-stable, doesn't have vinum, and is spontaneously
> rebooting (several times in 48 hrs).  again no messages indicting the problem.
> 
> postgres runs as a non-root user.
> 
> on the second system, it has rebooted during heavy database processing, but
> mysterously, has rebooted again within 30-40 minutes, even though the
> database processing doesn't automatically restart (ie. the second reboot
> was not caused by heavy processing, as there was no processing happening).
> 
> has anybody had similar issues?  solutions?  suggestions?

I have (had?) some similar reboots, but I'm not sure it's the same. Still,
it's another data point: I have a 133MHz Pentium with two IDE disks,
running Postgresql over vinum. The machine is underpowered (only 32MB RAM,
so it swaps heavily when more than 2-3 clients are concurrently active),
and under heavy loads it rebooted several times. Naturaly, it all stoppoed
once I added dumping to the config to debug it ;-) It also used to give
bad file descriptor errors for files both on the vinum volumes and on
other volumes in the nightly cron runs. What's even weirder is that some
of these bad file descriptor errors disappeared (files were back to normal
when I came to check in the morning). I thought this was all related to
one of the disks being flaky (it has a large area with bad sectors that I
just partitioned around), but your description kinda rings a bell. Anyway,
I haven't seen any of these reboots for about 3 weeks now, but would sure
like to get to the bottom of this, if I can.

> 
> -- 
> [ Jim Mercer                jim@reptiles.org              +1 416 506-0654 ]
> [          Reptilian Research -- Longer Life through Colder Blood          ]
> [  Don't be fooled by cheap Finnish imitations; BSD is the One True Code.  ]
> 

Nadav



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.95-heb-2.07.1000321094543.21518A-100000>