[colug-432] Troubleshooting Suggestions: File Truncation Issue
William E. T.
linux.hacker at gmail.com
Sun Jan 10 09:45:17 EST 2016
> 1) hard links typically don't work across filesystem boundaries, and
That's why I explicitly stated that the files are in the same directory,
the traces demonstrate that, they show the link call succeeding, and the
"real file" exists, it just is truncated. If I tried to make a hard link
across a filesystem boundary, I would (incorrectly?) expect the call to
fail and the link to not exist.
> 2) does the program check the exit code from the link command and give
> appropriate error messages?
It would be a system call and the traces show that every system call is
returning codes indicating they are successful. I"m sure I'm missing some
checks in my c program and I have no idea on the proprietary applications
since I don't have access to its code, but I would expect the traces to be
the ultimate source of truth in determining if the OS is saying they were
> I think I understand the symptom okay, but don't have good enough
> visibility into the application
I wrote as small a program as I can think to write that demonstrates the
problem and linked to the source. I'm not sure how to provide more insight.
> and underlying system configuration.
It may be something simple, or it may be something complex... and there's
> really not enough data for a complex problem diagnosis.
Fair enough, this was a bit of a Hail Mary. If I don't get any answers I
won't be upset, but I figured it was worth throwing out there in case some
one had seen something similar or had some insight since I'm not getting
much help elsewhere.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the colug-432