Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Jul 2014 16:50:14 +0200
From:      Harald Schmalzbauer <h.schmalzbauer@omnilan.de>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        FreeBSD Stable <freebsd-stable@freebsd.org>
Subject:   Re: panic/lock on 9.3-RELEASE with nullfs/nfs/zfs combination
Message-ID:  <53D511A6.4010102@omnilan.de>
In-Reply-To: <53D5105A.6040204@omnilan.de>
References:  <53D12973.3010805@omnilan.de> <20140724165917.GT93733@kib.kiev.ua> <53D1503B.2030200@omnilan.de> <20140724193048.GU93733@kib.kiev.ua> <53D2006C.7090207@omnilan.de> <20140725151448.GY93733@kib.kiev.ua> <53D380B2.2080700@omnilan.de> <20140726114839.GF93733@kib.kiev.ua> <53D5105A.6040204@omnilan.de>

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

[-- Attachment #1 --]
 Bezüglich Harald Schmalzbauer's Nachricht vom 27.07.2014 16:44
(localtime):
>  …
>> After that, you could try the patch which I posted at winter, but which
>> was not tested. I do not know whether it is of any help, and I do need
>> the debugging information with the patch above before I can make any
>> conclusions.
>>
>> diff --git a/sys/fs/nullfs/null_subr.c b/sys/fs/nullfs/null_subr.c
>> index fa6c4af..3f74579 100644
>> --- a/sys/fs/nullfs/null_subr.c
>> +++ b/sys/fs/nullfs/null_subr.c
>> @@ -251,6 +251,7 @@ null_nodeget(mp, lowervp, vpp)
>>  	vp->v_type = lowervp->v_type;
>>  	vp->v_data = xp;
>>  	vp->v_vnlock = lowervp->v_vnlock;
>> +	vp->v_vflag = lowervp->v_vflag & VV_ROOT;
>>  	error = insmntque1(vp, mp, null_insmntque_dtr, xp);
>>  	if (error != 0)
>>  		return (error);
> I tested this without the ldvp-debug patch and besides the same
> ufs/devds LOR nothing else happens with my usual simple end limited test.

One thing to note: With the first rw-open on the nullfs-mount, there's
always a almost 1 second dely on an otherwise incredibly responsive
machine. That delay happens always after a reboot, and never after first
rw-opened any file, regardless if I rw-open the same or a different file
on the nullfs-mount. Is that something to worry about? Or a simple
reason I can understand?

Thanks,

-Harry


[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iEYEARECAAYFAlPVEaYACgkQLDqVQ9VXb8joEQCcC2bwmlpd7+ZeywOGbKwgNfuf
n2EAoKCaK4kDFUHZik8LxyZffE+9YfYs
=iArG
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D511A6.4010102>