Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Feb 2012 21:20:36 +0100
From:      Florian Smeets <flo@FreeBSD.org>
To:        Gleb Kurtsou <gleb.kurtsou@gmail.com>
Cc:        decke@FreeBSD.org, Konstantin Belousov <kib@FreeBSD.org>, "current@freebsd.org" <current@FreeBSD.org>
Subject:   Re: Processes getting stuck in state tmpfs
Message-ID:  <4F469F94.5080606@FreeBSD.org>
In-Reply-To: <20120211102006.GA1274@reks>
References:  <4F358F01.1090508@FreeBSD.org> <20120211102006.GA1274@reks>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig33C98DBE6BD456685B857AFF
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 11.02.12 11:20, Gleb Kurtsou wrote:
> On (10/02/2012 22:41), Florian Smeets wrote:
>> Hi,
>>
>> if you set WRKDIRPREFIX to a tmpfs mountpoint and try to build audio/g=
sm
>> from ports one of the mv processes gets stuck in state tmpfs quite
>> often. Traces from a kernel with WITTNESS and DEBUG_VFS_LOCKS are
>> available here http://tb.smeets.im/~flo/tmpfs.txt
>=20
> It's because of incorrect vnode locking order in tmpfs_rename. Issue is=

> known and tmpfs is not the only file system suffering from it (e.g. ext=
2).
>=20
> There two ways of working around it in tree:
> * UFS: try locking vnode, unlock all vnodes on failure, restart,
> relookup vnodes needed.
> * ZFS: introduce directory entry locks to guarantee fvp won't disappear=
,
> fdvp can be safely traversed, etc. That won't be easy..
>=20
> UFS-way would be a good temporal solution, but I think we should work o=
n
> improving VOP_RENAME() in a long run.
>=20
> I'll try to prepare a patch in several days.
>=20

Hey Gleb,

did you get anywhere with this?

Thanks,
Florian


--------------enig33C98DBE6BD456685B857AFF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAk9Gn5QACgkQapo8P8lCvwkdwwCcDGIrgauqan48tjJ9LJoTGYOb
q/QAnj+38Vh72Pt4hf+cPxHAEywIGC9F
=lIx5
-----END PGP SIGNATURE-----

--------------enig33C98DBE6BD456685B857AFF--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F469F94.5080606>