Description of problem:
we use ibm tsm solution to backup linux host, kernel panic when libc-2.3.4.so be
restored by tsm agent. even i recover it with a backup file from localhost.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.cp libc-2.3.4.so libc-2.3.4.so.bak
3.cp libc-2.3.4.so.bak libc-2.3.4.so
kernel panic: reboot
show the following messages:
/sbin/init :error while loading share libraries: /lib/tls/libc.so.6: file too
short kernel panic - not syncing: Attemped to kill init !
That's user error. You really can't restore libc.so (or any other widely used
shared library or the dynamic linker) using cp on a running system.
cp overwrites the target file (opens it with O_WRONLY|O_TRUNC) and at that point
any program that have the current libc.so.6 mapped can crash. If init crashes,
the whole system is dead of course, the root just shot himself in the foot.
The way shared libraries should be restored is that they are copied to a
temporary file in the same directory where they should be installed to and
once copied there, they are moved or linked over the target file (mv -f or ln
-f). install(1) gets close, it unlinks the target file and then copies it over,
but there is still a window in which the old libc doesn't exist and new one
doesn't either, so e.g. newly started programs in that timeframe could die.
rpm does the right thing AFAIK.