add full operation traceback if `wcfs status` command fails
As described in !40 (a80a2bd1) we currently don't have any traceback when wcfs status command fails. !40 (comment 237529) suggests to implement an operational traceback:
Here we can see the codepath that lead to the error, but not the information about filesystem path that led to
ino. Maybe in this particual case we can deduce the information, but in general traceback of a program is not the same as traceback at operational level. In this particular case the traceback at operational level should be something like:/dev/shm/wcfs/ea94c11195da31e3232dad5ca6321e421a58101d: lookup wcfs server: procdb query: proc123: fd: 1: no 'ino' entryI know how to do it this way and will try to prepare the patch.