Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Sep 2003 00:28:11 +0100
From:      Lewis Thompson <lewiz@black.lewiz.org>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   kern/56988: system panic with doubled up unionfs
Message-ID:  <1063927691.218167.41181.nullmailer@black.lewiz.org>
Resent-Message-ID: <200309182330.h8INUIXa068218@freefall.freebsd.org>

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

>Number:         56988
>Category:       kern
>Synopsis:       system panic with doubled up unionfs
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 18 16:30:17 PDT 2003
>Closed-Date:
>Last-Modified:
>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:
>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''



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