Quote:
Originally Posted by
manivanm
While a tar file was created, the file system got full and there was no message on the tar failure.
"tar" will
always issue an error message (as well as a non-zero exit code) in such a case. There could only be "no error message" because it was redirected to "/dev/null". Either the exit code or the error message should have been watched in this case.
Quote:
Originally Posted by
manivanm
Then the system was shut down and the administrator says because the file system was full the shut down procedure corrupted the file system.
At first sight i think this is hardly believable. I do not know the shutdown procedure of this specific system (which might be heavily customized to produce such results), but any
normal shutdown-procedure will not bear such results.
Whats more, it happens all the time that filesystems become full. Why should a shutdown-procedure - any normal action a system undertakes, for that matter - corrupt a filesystem? Linux would not be the stable server operating system it is if
any normal operation would cause filesystems - full or not - to become corrupted.
To be honest, lacking any further evidence, i think the admin is telling bullshit. Let him explain what
exactly has happened and post it here if you can't prove//disprove it yourself.
I hope this helps.
bakunin
