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
[-- Attachment #1 --] 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/gsm >> 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 > > 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. ext2). > > 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.. > > UFS-way would be a good temporal solution, but I think we should work on > improving VOP_RENAME() in a long run. > > I'll try to prepare a patch in several days. > Hey Gleb, did you get anywhere with this? Thanks, Florian [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk9Gn5QACgkQapo8P8lCvwkdwwCcDGIrgauqan48tjJ9LJoTGYOb q/QAnj+38Vh72Pt4hf+cPxHAEywIGC9F =lIx5 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F469F94.5080606>