On Mon, 28 Jul 2014, Gene Heskett wrote:
However, in one failure path it quoted, there are no softlinks. It simply
did not like /var/lib/nfs/rpc_pipefs, which actually goes 2 or 3 levels
deeper, encountering no softlinks as it goes.
So I'm still standing here on my stump and proclaiming that tars "--one-
file-system" implementation is broken. And has been since somewhere post
1.22.
Hi Gene,
There is a simple explanation for that: /var/lib/nfs/rpc_pipefs IS a
separate file system. On my system I have:
$ df /var/lib/nfs/rpc_pipefs
Filesystem 1K-blocks Used Available Use% Mounted on
rpc_pipefs 0 0 0 - /var/lib/nfs/rpc_pipefs
$ mount | grep pipe
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
So /var/lib/nfs/rpc_pipefs is a mountpoint for a file system of type
"rpc_pipefs" (whatever that might be). I'm pretty sure it is volatile and
will be recreated automatically at start-up, so no need to back it up.
Bob
