Date: Sun, 23 May 2010 07:27:22 +0400 From: Roman Bogorodskiy <bogorodskiy@gmail.com> To: Jeff Roberson <jroberson@jroberson.net> Cc: current@freebsd.org Subject: Re: ffs_copyonwrite panics Message-ID: <20100523032720.GA89739@dirtyvegas> In-Reply-To: <alpine.BSF.2.00.1005190112030.1398@desktop> References: <20100518185201.GA2745@fsol> <alpine.BSF.2.00.1005190112030.1398@desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff Roberson wrote: > On Tue, 18 May 2010, Roman Bogorodskiy wrote: > > > Hi, > > > > I've been using -CURRENT last update in February for quite a long time > > and few weeks ago decided to finally update it. The update was quite > > unfortunate as system became very unstable: it just hangs few times a > > day and panics sometimes. > > > > Some things can be reproduced, some cannot. Reproducible ones: > > > > 1. background fsck always makes system hang > > 2. system crashes on operations with nullfs mounts (disabled that for > > now) > > > > The most annoying one is ffs_copyonwrite panic which I cannot reproduce. > > The thing is that if I will run 'startx' on it with some X apps it will > > panic just in few minutes. When I leave the box with nearly no stress > > (just use it as internet gateway for my laptop) it behaves a little > > better but will eventually crash in few hours anyway. > > This may have been my fault. Can you please update and let me know if it > is resolved? There was both a deadlock and a copyonwrite panic as a > result of the softupdates journaling import. I just fixed the deadlock > today. Tried today's -CURRENT and unfortunately the behaviour is still same. Roman Bogorodskiy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100523032720.GA89739>