Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Mar 2010 10:24:49 +0100
From:      Borja Marcos <borjam@sarenet.es>
To:        Borja Marcos <borjam@sarenet.es>
Cc:        FreeBSD Stable <freebsd-stable@freebsd.org>, Pawel Jakub Dawidek <pjd@FreeBSD.org>, Stefan Bethke <stb@lassitu.de>
Subject:   Re: Many processes stuck in zfs
Message-ID:  <BFF1E2D6-B48A-4A5E-ACEE-8577FDB07820@sarenet.es>
In-Reply-To: <CB854F58-03AF-46DD-8153-85FA96037C21@sarenet.es>
References:  <864468D4-DCE9-493B-9280-00E5FAB2A05C@lassitu.de> <20100309122954.GE3155@garage.freebsd.pl> <EC9BC6B4-8D0E-4FE3-852F-0E3A24569D33@sarenet.es> <20100309125815.GF3155@garage.freebsd.pl> <CB854F58-03AF-46DD-8153-85FA96037C21@sarenet.es>

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

On Mar 9, 2010, at 3:18 PM, Borja Marcos wrote:

>=20
> On Mar 9, 2010, at 1:58 PM, Pawel Jakub Dawidek wrote:
>=20
>>>> What kind of hardware do you have there? There is 3-way deadlock =
I've a
>>>> fix for which would be hard to trigger on single or dual core =
machines.
>>>>=20
>>>> Feel free to try the fix:
>>>>=20
>>>> 	http://people.freebsd.org/~pjd/patches/zfs_3way_deadlock.patch
>>>=20
>>> Maybe related to the deadlock I reported when I was receiving an =
incremental snapshot while the target dataset was being read?
>>=20
>> Could be. This deadlock is in general related to zfs recv =
functionality.
>=20
> Aye aye, Sir
>=20
> set fingers -position crossed
>=20
> testing :)

Tested. Same deadlock remains.







Borja.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BFF1E2D6-B48A-4A5E-ACEE-8577FDB07820>