#1 nfsreplay cannot replay rdump against original FS hierarchy

[Shehjar Tikoo]

nfsreplay needs some mapping
information to start the replay. This information contains the filehandles of orphan files and directories in the trace and the place where these can be found in the file system hierarchy created using tracedigester.

When we use tracedigester to create the FS hierarchy from the anonymized file, this info gets dumped into what
is called the orphans file which is then passed to
nfsreplay. When we attempt to replay against the original hierarchy, we assume that since the hierarchy in the trace is the same as that on the server, the replay should proceed correctly. This is the reason why no orphan files are supposed to be needed.
BUT
In some cases, where the trace is incomplete, this orphan file is required even for replaying against the original hierarchy.

The thread that brought up this problem is here.
http://sourceforge.net/mailarchive/forum.php?thread_name=BAY137-W1426E98040DF4C6032CCECBA1A0%40phx.gbl&forum_name=nfsreplay-users

We know that the mapping info is missing in this case(..as we can see in replay.dump where the LOOKUPS are using a mostly zeroed out dir handle, which was written into the anonymized file by the
anonymizer..), nfsreplay just uses this dir handle from
the rdump directly, in the absence of the orphans file. Following that, because these dir handles are not really the valid ones present in nfs server's state, it returns a stale handle error during replay.

It looks like orphan files analysis needs to be performed even in the case of replaying against the original filesystem hierarchy.

[Shehjar Tikoo]

Files contain the original nfs trace, anonymized trace, rdump and the trace collected at the time of replay.