Date: Sun, 17 Nov 1996 10:55:03 +0200 (EET) From: Heikki Suonsivu <hsu@clinet.fi> To: Heikki Suonsivu <hsu@clinet.fi> Cc: Peter Wemm <peter@spinner.DIALix.COM>, FreeBSD-gnats@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org Subject: Re: kern/1698: sup from around 21:51 GMT 28th very unstable (mmap, maybe?) Message-ID: <199611170855.KAA25317@katiska.clinet.fi> In-Reply-To: <199610221604.TAA04027@katiska.clinet.fi> References: <199610220516.IAA00811@katiska.clinet.fi> <199610220643.OAA10951@spinner.DIALix.COM> <199610221604.TAA04027@katiska.clinet.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
November 16 kernel is still unstable. For last two kernels I got a
deadlock within 5 minutes of newsfeed starting up, so something might have
changed, from crash and filesystem corruption to deadlock. August 19
kernel still runs with no serious problems.
Has anyone got a news server running reliably with kernels later than end
of August (preferably ones with tag RELENG_2_2) ? It seems odd that I can
repeat this so easily, I would assume a lot of people should see this ? I
have gotten metoos from (only?) three people now. This problem has been
there for about 2 months now.
The system is 3940, seagate Hawks for news disks, P120 ASUS TritonII, 96M.
Exports two NFS disks (not the news partitions).
Heikki Suonsivu writes:
> Peter Wemm writes:
> > Heikki Suonsivu wrote:
> > >
> > > Heikki Suonsivu writes:
> > > > FreeBSD-gnats@freefall.freebsd.org writes:
> > > > > Thank you very much for your problem report.
> > > > > It has the internal identification `kern/1698'.
> > > > > The individual assigned to look at your
> > > > > bug is: freebsd-bugs.
> > > > >
> > > > > >Category: kern
> > > > > >Responsible: freebsd-bugs
> > > > > >Synopsis: sup from around 21:51 GMT 28th very unstable (mmap, ma
> > ybe?)
> > > > > >Arrival-Date: Mon Sep 30 21:10:01 PDT 1996
> > > >
> > > > Crashes without mmap also; apparently the problem has to be somewhere else
> > .
> > >
> > > sup from 20th october still bad, panic within 24 hours (news+nfs),
> > > filesystems get badly corrupted (lots of dup/bad inodes, zero-length director
> > y,
> > > usually sequential inodes get killed).
> >
> > Are you using a 4K blocksize on your news file system by any chance? I've
> > been having corruption problems like this for 12 months now, and changing
> > to 8K blocks seems to have cured it.. (at least, the machine has been up
> > for 7 days now, previous record was 3 and a half days). The disk
> > overheads are a killer though... :-(
>
> We use 4K blocksize. With the previous kernel from about a month a go we
> have been getting uptimes of about a week, I do not know for sure how much
> average would be as I have been about once a week tried to upgrade to a
> newer current. I haven't seen a single corruption problem with that
> kernel, though some panics, so something bad happened about month ago.
>
> We mount some thing from the news server with NFS, so it might be related
> to other people reporting NFS being flakey for last couple of weeks. The
> filesystem corruption is nasty, as it requires manual care to get things up
> and going...
>
> > > > Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi
> > > > mobile +358-40-5519679 work +358-0-43542270 fax -4555276 home -8031121
> >
> > Cheers,
> > -Peter
>
> --
> Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi
> mobile +358-40-5519679 work +358-0-43542270 fax -4555276
--
Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi
mobile +358-40-5519679 work +358-9-43542270 fax -4555276
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611170855.KAA25317>