[DragonFlyBSD - Bug #2476] tmpfs namecache(?)
John Marino via Redmine
bugtracker-admin at leaf.dragonflybsd.org
Fri Dec 21 01:53:29 PST 2012
Issue #2476 has been updated by John Marino.
Okay, I figured out what was going on.
I will try to describe.
"rollback" /pfs/mypfs to a known clean configuration
What was intended:
mount /pfs/mypfs to /myworkarea
mkdir -p /myworkarea/build/01/
mount tmpfs to /myworkarea/build/01
The "known clean configuration" got contaminated and had these directories in it: "/build/01"
so the mkdir -p step was ignored and mount tmpfs presumably mounted back to /pfs/mypfs/build/01
This worked sometimes, sometimes not. about 50%.
The "fix" is to restore the known clean configuration.
However, this might still be a bug.
Bug #2476: tmpfs namecache(?)
Author: John Marino
Using cpdup, I directly copied a pfs snapshot to a tmpfs mount:
mount -t tmpfs tmpfs /path/to/mypoint
cpdup -x -i0 /path/to/snapshot/ /path/to/mypoint/
mount -t devfs devfs /path/to/mypoint/dev
(/path/to/snapshot/dev exists, is a directory, and is empty)
The final mount will fail unless a sleep command of a second or two is put between the cpdup and mount commands, or if something accesses mymount point like ls command.
Seems that this is an issue with tmpfs, possibly with namecache according to Venkatesh.
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
More information about the Bugs