panic/lock on 9.3-RELEASE with nullfs/nfs/zfs combination

[Harald Schmalzbauer]

 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20140727/c80544a3/attachment.sig>