http://bugzilla.novell.com/show_bug.cgi?id=504590
User alpha096@virginbroadband.com.au added comment
http://bugzilla.novell.com/show_bug.cgi?id=504590#c12
--- Comment #12 from Scott Couston 2009-05-22 14:57:14 MDT ---
I suppose this is the first time this type of error has happened and it wont be
the last. We need a strategy for dealing with this type of update error and I
suppose we have three different ways to manage it.
1. Change the corrupted file on the master so that when all the mirrors
replicate the new file is taken up.
2. If we can determine the mirror by geography, which is not too hard in my
case, offer directions to the mirrors to manually check the files validity.
a. If the Mirror is running an NTFS Partitioned server the command to run check
disk AGAINST the file will work - This is a 25 Year old external command but it
will still work - Its just that NO NTFS admin will re-call it.
chkdsk \absolute_ path_excluding_drive_letter\offending_file_name.extension
Response will be
'The file...name.... Is contiguous' if all is o.k OR
'The file contains...n..x..errors' if its not o.k
Solution: Manually copy and verify and copy directory above if empty
from new source to destination
copy ...absolute path..file.name ..destination /V /E
As far as I know NTFS does not perform any hotfix for files so copied..big
issue.
If its a Novell Server we can
Purge the file's salvageable records
ncopy \absolute...path....\origin\ new destination /V /E
Solution: Manually copy and verify and copy directory above if empty
from new source to destination
Personally I like option 1 above ....???????
Your ball.....
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.