From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: Richard Miller <miller@hamnavoe.demon.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20020819193803.27D52199EC@mail.cse.psu.edu>
Subject: [9fans] vac merge semantics
Date: Mon, 19 Aug 2002 20:37:32 +0100
Topicbox-Message-UUID: de907138-eaca-11e9-9e20-41e7f4b1d025

When vac(1) file trees of depth > 1 are merged with 'vac -m', the resulting
tree when served by vacfs(1) can contain (?usually will contain) multiple
files with identical qid values.

Demonstration:

	cpu% mkdir one
	cpu% echo one a >one/a
	cpu% mkdir two
	cpu% echo two b >two/b
	cpu% vac -f one.vac one
	cpu% vac -f two.vac two
	cpu% vac -f both.vac -m one.vac two.vac
	cpu% vacfs -m /n/kremvax both.vac
	cpu% ls -lq /n/kremvax
	(0000000000000003 0 80) d-rwxrwxr-x M 61 miller miller 0 Aug 19 19:56 /n/kremvax/one
	(0000000000000006 0 80) d-rwxrwxr-x M 61 miller miller 0 Aug 19 19:56 /n/kremvax/two
	cpu% ls -lq /n/kremvax/*
	(0000000000000001 0 00) --rw-rw-r-- M 61 miller miller 6 Aug 19 19:56 /n/kremvax/one/a
	(0000000000000001 0 00) --rw-rw-r-- M 61 miller miller 6 Aug 19 19:56 /n/kremvax/two/b
	cpu% grep . /n/kremvax/*/*
	/n/kremvax/one/a:one a
	/n/kremvax/two/b:two b

No, I haven't got a correction for this one.  I'm wondering how much of a Bad Thing
it is.  Clearly it contradicts the specification in intro(5) that qids are unique
within a server hierarchy.  Although I've never been very clear about what qids are
used for in practice, it would seem for example that using cfs(4) to cache a merged
vacfs tree, or mounting it with '-C', would lead to serious confusion.

-- Richard Miller