ggatec/ggated cache or buffer?

[Brian McCann]

Hi all...I posted this in -stable and wanted to post in here as well
to see if anyone else can help me out.  I'm playing around with ggatec
and ggated, and
would like to eventually be able to mirror a partition over the
network...but for now I've just exported /dev/da1s1d as RO, created
the ggate device on the client as RO, mounted it as RO (and tried
using async as well), and when I make  change on the server, I NEVER
see it on the client without unmounting and remounting the client.
What's odd, is say I make file 1 by doing:

#echo "foo" > /share/bar

Then mounting the client, I see the file.  Now I delete the file on
the server, I can still cat the file on the client.  It's like the
client can still read the old superblock or something.  It appears
that ggatec is caching the superblock or something.  Is there a way to
NOT get it to do this?  It seams that if there isn't, right now
ggatec/d would only be useful for sharing file systems that don't
change.

Any and all information is of course welcome!

Thanks,
--Brian