From lewiz@black.lewiz.org  Thu Sep 18 16:28:53 2003
Return-Path: <lewiz@black.lewiz.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AED5C16A4B3
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 18 Sep 2003 16:28:53 -0700 (PDT)
Received: from lon1-mail-1.visp.demon.net (lon1-mail-1.visp.demon.net [193.195.70.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5039643FBF
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 18 Sep 2003 16:28:52 -0700 (PDT)
	(envelope-from lewiz@black.lewiz.org)
Received: from mail.lewiz.org (host-70b-en-u-191.dial.beeb.net [62.56.3.191] (may be forged))
	by lon1-mail-1.visp.demon.net (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id AOP07097;
	Fri, 19 Sep 2003 00:28:44 +0100 (BST)
Received: from black.lewiz.org ([192.168.0.12])
	by mail.lewiz.org with smtp (Exim 4.20)
	id 1A08C2-0007cZ-V5
	for FreeBSD-gnats-submit@freebsd.org; Fri, 19 Sep 2003 00:28:10 +0100
Received: (nullmailer pid 41182 invoked by uid 4001);
	Thu, 18 Sep 2003 23:28:11 -0000
Message-Id: <1063927691.218167.41181.nullmailer@black.lewiz.org>
Date: Fri, 19 Sep 2003 00:28:11 +0100
From: Lewis Thompson <lewiz@black.lewiz.org>
Reply-To: Lewis Thompson <lewiz@black.lewiz.org>
To: FreeBSD-gnats-submit@freebsd.org
Subject: system panic with doubled up unionfs
X-Send-Pr-Version: 3.113

>Number:         56988
>Category:       kern
>Synopsis:       system panic with doubled up unionfs
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 18 16:30:17 PDT 2003
>Closed-Date:    Sun Jan 18 22:50:29 PST 2004
>Last-Modified:  Sun Jan 18 22:50:29 PST 2004
>Originator:     Lewis Thompson
>Release:        FreeBSD 5.1-RELEASE-p3 i386
>Organization:
>Environment:
System: FreeBSD black.lewiz.org 5.1-RELEASE-p3 FreeBSD 5.1-RELEASE-p3 #0: Tue Sep 16 22:38:04 BST 2003 lewiz@black.lewiz.org:/usr/src/sys/i386/compile/BLACK i386

>Description:
	If I double up union mounts my system panis with the following message:

panic: union_lookup returning . (0xd1328c3c) not same as startdir (0xc29c8000)
syncing disks, buffers remaining... 2125 2125 panic: free locked buf
*rebooted*

By ``double up'' I mean:

mount -t unionfs -o -b /usr/ports /usr/jail/base/usr/ports
mount -t unionfs -o -b /usr/jail/base /usr/jail/yellow

If I then start the jail (yellow) (I didn't check if it actually required the jail to be running) and
attempt to access /usr/ports (which is /usr/jail/yellow/usr/ports -> /usr/jail/base/usr/ports ->
/usr/ports) then the system panics.

It might sound obscure to do (and I'm now using nfs) but it would make things a bit easier.  I should be able to provide any necessary details.

A final note:  I'm using vinum for my whole fs:



>How-To-Repeat:
>Fix:

	


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->suspended 
State-Changed-By: kris 
State-Changed-When: Wed Oct 8 15:14:01 PDT 2003 
State-Changed-Why:  
Unionfs is documented to be broken. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=56988 
State-Changed-From-To: suspended->open 
State-Changed-By: scrappy 
State-Changed-When: Fri Nov 14 07:24:31 PST 2003 
State-Changed-Why:  

David just commit'd code to fix the union_lookup issue reported 
in your message below ... can you upgrade and confirm whether  
or not it addressed your problem? 


http://www.freebsd.org/cgi/query-pr.cgi?pr=56988 
State-Changed-From-To: open->suspended 
State-Changed-By: kris 
State-Changed-When: Sat Nov 15 13:44:15 PST 2003 
State-Changed-Why:  
Suspended awaiting patch 

http://www.freebsd.org/cgi/query-pr.cgi?pr=56988 
State-Changed-From-To: suspended->closed 
State-Changed-By: das 
State-Changed-When: Sun Jan 18 22:47:03 PST 2004 
State-Changed-Why:  
As Marc mentioned, I made some changes a while ago to address certain 
layering problems.  I was unable to reproduce the behavior you are 
reporting on a recent -CURRENT.  If you still have trouble, please try 
to reproduce the problem on a recent -CURRENT or -STABLE and report 
the exact commands needed to reproduce it (including the creation and 
mounting of the filesystems and directories on top of the union mount.) 
Thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=56988 
>Unformatted:
 >z@purple /usr/jail # vinum printconfig
 # Vinum configuration of purple.lewiz.org, saved at Fri Sep 19 00:25:43 2003
 drive vinumdrive1 device /dev/ad2s1h
 drive vinumdrive0 device /dev/ad0s1h
 volume root
 volume swap
 volume var
 volume usr
 volume data
 plex name root.p0 org concat vol root 
 plex name root.p1 org concat vol root 
 plex name swap.p0 org concat vol swap 
 plex name swap.p1 org concat vol swap 
 plex name var.p0 org concat vol var 
 plex name var.p1 org concat vol var 
 plex name usr.p0 org concat vol usr 
 plex name usr.p1 org concat vol usr 
 plex name data.p0 org concat vol data 
 sd name root.p0.s0 drive vinumdrive0 plex root.p0 len 524007s driveoffset 265s plexoffset 0s
 sd name root.p1.s0 drive vinumdrive1 plex root.p1 len 524007s driveoffset 265s plexoffset 0s
 sd name swap.p0.s0 drive vinumdrive0 plex swap.p0 len 940896s driveoffset 524272s plexoffset 0s
 sd name swap.p1.s0 drive vinumdrive1 plex swap.p1 len 940896s driveoffset 524272s plexoffset 0s
 sd name var.p0.s0 drive vinumdrive0 plex var.p0 len 524288s driveoffset 1465168s plexoffset 0s
 sd name var.p1.s0 drive vinumdrive1 plex var.p1 len 524288s driveoffset 1465168s plexoffset 0s
 sd name usr.p0.s0 drive vinumdrive0 plex usr.p0 len 28731392s driveoffset 1989456s plexoffset 0s
 sd name usr.p1.s0 drive vinumdrive1 plex usr.p1 len 28731392s driveoffset 1989456s plexoffset 0s
 sd name data.p0.s0 drive vinumdrive0 plex data.p0 len 209400864s driveoffset 30720848s plexoffset 0s
 sd name data.p0.s1 drive vinumdrive1 plex data.p0 len 209400864s driveoffset 30720848s plexoffset 209400864s
 
 How-To-Repeat:
 	See ``Description''
