I was able to narrow down the conditions under which the mv command
problem was triggered. When using 'mv a b' and when file 'b' was
being read, 'b' would sort of vanish.
To somewhat summarize, a mv on dual cpu DS20s with:
1. Tru64 5.0a target file vanishes on both CPUs
2. Tru64 5.0a target file vanishes on the CPU when the secondary
CPU is shut down.
3. Tru64 5.1 target file vanishes on one CPU but not on the other.
4. Tru64 5.1 target file vanishes on the CPU when the secondary
CPU is shut down.
The instructions and scripts for replicating this as any user are
found in:
http://www.mtholyoke.edu/lits/network/tu5x-bug/0_Readme.html
A great deal of thanks go to Tom Blinn and Chang Song at Compaq/Digital
who were able to replicate this problem on both UFS and ADFS.
Chang is working on general patches for this problem or problems.
The probability of triggering this problem is reduced, perhaps to zero,
if the command:
mv a b is replaced with:
ln -f a b
rm a
I only have tested this on UFS.
(In my testing, I did find out that you could use psradm to shut down
the primary CPU, but after doing that, little testing of anything
was possible since the prompt became >>> I wouldn't mind finding out
how to make CPU 0 back to the primary without rebooting and shutting
down CPU 1 which had become the primary. (I didn't try power cycling
the system.))
-mike
-----------------------------------------------------------------------------
Michael A. Crowley Director of Networking
mcrowley_at_mtholyoke.edu 216 Dwight Hall, Mount Holyoke College
413-538-2140 fax: 413-538-2331 South Hadley, MA 01075-6415
http://www.mtholyoke.edu/~mcrowley http://www.mtholyoke.edu/lits/network
-----------------------------------------------------------------------------
Received on Sun Feb 11 2001 - 05:08:32 NZDT