Date: Wed, 3 Oct 2012 17:25:44 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Norbert Aschendorff <norbert.aschendorff@yahoo.de>, freebsd-stable@freebsd.org Subject: Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS" Message-ID: <1965862480.1682152.1349299544413.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20121003173931.GZ35915@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Konstantin Belousov wrote:
> On Wed, Oct 03, 2012 at 07:26:47PM +0200, Norbert Aschendorff wrote:
> > On 10/03/2012 05:54 PM, Konstantin Belousov wrote:
> > > So do you use nullfs exported mounts ? And stable ?
> > > Can you try to remove nullfs from the set up ?
> >
> > Yes, I am using nullfs for the exports (mounting the exported
> > directories to subdirectories of /srv). In the FreeBSD man pages and
> > the
> > documentation, the V4 export line in /etc/exports is often set to /,
> > but
> > as I come from Linux where /etc/exports looks completely different,
> > I
> > just followed my habits.
> >
> > As I wrote this, I executed the critical operation. It's finished
> > and
> > the FreeBSD server still runs *yay* :) So it's quite likely that the
> > problem stems from the nullfs mount.
> >
> > I just remember an issue I already wanted to tell: Before the server
> > crashed, the nfsd process ('nfsd: server') used 100% CPU (one core),
> > but
> > without progress on client side. Usually, the nfsd uses only up to
> > 10%
> > cpu time when rsyncing (values taken from htop - 100% = one used
> > CPU).
> >
> > ...aaand I just run it once more, and it worked again :)
>
> Can you try HEAD kernel ?
Kostik, thanks for thinking of this. The crash had me baffled, rick.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1965862480.1682152.1349299544413.JavaMail.root>