Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Oct 2010 22:06:05 +0200
From:      Willem Jan Withagen <wjw@digiware.nl>
To:        Jeremy Chadwick <freebsd@jdc.parodius.com>
Cc:        "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject:   Re: ZFS freeze/livelock
Message-ID:  <A4E83B4F-44CB-41C0-B3A1-3B327F0BA20B@digiware.nl>
In-Reply-To: <20101010193415.GA93540@icarus.home.lan>
References:  <4CB1DD0F.6000209@digiware.nl> <20101010193415.GA93540@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
Op 10 okt. 2010 om 21:34 heeft Jeremy Chadwick =
<freebsd@jdc.parodius.com> het volgende geschreven:

> On Sun, Oct 10, 2010 at 05:34:39PM +0200, Willem Jan Withagen wrote:
>> Just had my FreeBSD freeze on me with what I would think is sort of
>> an livelock....
>>=20
>> While I was receiving zfs snapshots on my data pool.
>>=20
>> Top and systat just kept running,
>> but anything getting near a shell (and perhaps disk-io) ended up in:
>>=20
>> root@zfs.digiware.nl# gpart create -s gpt da6
>> load: 0.00  cmd: csh 12393 [zfsvfs->z_teardown_inactive_lock] 26.12r
>> 0.00u 0.00s 0% 2480k
>> load: 0.10  cmd: csh 12393 [zfsvfs->z_teardown_inactive_lock] 96.01r
>> 0.00u 0.00s 0% 2480k
>>=20
>> Trying to execute to execute shutdown -r now had no effect what so =
ever.
>> Neither did the three-finger salute.
>> (Well at least not in 60 sec I was willing to wait.)
>>=20
>> Only way out of this situation was hard-reset. And I do have to
>> admit I like ZFS for the speed it recovers after unexpected reboot.
>>=20
>> To bad there was no alt-ctrl-backspace escape to debugger compiled
>> in. I'll do that with the next kernel, just in case.
>>=20
>> So the only data point I can give is the ^T output above.
>=20
> We don't know what FreeBSD version you're using (specifically uname -a
> output, since build date matters), but if it's RELENG_8 with ZFS v15,
> you might check out this thread (be sure to read Kai and I's diagnoses

Sorry about that.
I'm running Stable on this box, as of last  tuesday so thats v15, but =
the disks are still at v14.=20

>=20
> http://lists.freebsd.org/pipermail/freebsd-fs/2010-October/009687.html

I'll check It out.

> I'm in the process of moving all of my machines, including my home
> server, over to gmirror.  (Home machine started showing signs of =
serious
> ZFS performance degredation; mutt doing a stat() on 24 files and
> directories total taking literally 0.4 seconds on a dual-core machine.
> Makes no sense, doesn't happen with UFS2, I'm done.)

Well, all new things require time, hard work and diligent testing. It is =
no different than any new serious component added. Be It the migration =
to real multi processor, or giant removal.
Both went through phases of better and not so better stability.
Had we all given up, then there would not have been the current state of =
freebsd.

So i understand your feelings, but then i'm not running It on super =
essential servers and not giving up so easily.

--WjW   =20=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A4E83B4F-44CB-41C0-B3A1-3B327F0BA20B>