File corruption
I made an image backup of the webdisk to another – clean – disk in batch last night, and the log shows it did succeed with parity errors when reading the disk container: the one used previously containing the webs:
...
%BACKUP-S-CREATED, created $116$DKA201:[000000]USER.DIR;1
%BACKUP-S-CREATED, created $116$DKA201:[000000]VOLSET.SYS;1
%BACKUP-S-CREATED, created $116$DKA201:[000000]webdisk.dsk;1
%BACKUP-E-READVERR, virtual read error on file [000000]webdisk_old.dsk;1 at block 4193050
-SYSTEM-F-PARITY, parity error
%BACKUP-E-READVERR, virtual read error on file [000000]webdisk_old.dsk;1 at block 4193051
-SYSTEM-F-PARITY, parity error
...
-SYSTEM-F-PARITY, parity error
%BACKUP-E-READVERR, virtual read error on file [000000]webdisk_old.dsk;1 at block 4193795
-SYSTEM-F-PARITY, parity error
%BACKUP-S-CREATED, created $116$DKA201:[000000]webdisk_old.dsk;1
%BACKUP-E-READVERR, virtual read error on file []webdisk_old.dsk;1 at block 4193050
-SYSTEM-F-PARITY, parity error
...
%BACKUP-E-READVERR, virtual read error on file []webdisk_old.dsk;1 at block 4193795
-SYSTEM-F-PARITY, parity error
%BACKUP-S-CREATED, created $116$DKA201:[]webdisk_old.dsk;1
SYSTEM job terminated at 5-NOV-2007 03:45:22.66
So the file has been copied, but it’s quite likely that somehow the original backup was broken a;ready. And when a disk container is broken, the disk it represents is. No wonder it couldn’t be opened!
The other containers were fine. No trouble whatsoever.
I connected the original container to LD, but mount failed with too many party errrors reading header information. I disconnected the containerfile, and deleted it from the original disk.
Quite likely the dis wasn;t broken after all, so I put it back online, mounted it and examined the container file on that disk. Same problem! So I examined the file using LD/TRACE and mount it, but that didn’t get me much further. It just stated a lot of READ, some WRITE actions to disk on MOUNT, but that didn’t help much. So I quit the examinaton, dismounted the disk forgot to disconnect – an error only found when I tried to conenct the copied container on the same LD device. Thsi failed – and I disconnected the device, but from the wrong process.
Now, two processes got stuck in RWAST state: the one that allocated the real disk, and the one where I would have to disconnect the LD device…. All of a suden, the new webdisk was stated to have the wrong volume loaded – where it did work nicely before. I rebooted the system to prevent any more damage, the webdisk was found to be in mount verification mode so that took some time. Nevertheless, the system came up nicely, without errors.
Keep it under close watch, but hopefully this trouble is now over – at least for some time.
Mail statistics October
Processed October’s mail statistics:
Total number of messages: 3213
Blacklisted: 2271 (70.5%) – Average 73, min 34, max 149
Relayblock: 126 (4%) – Average 4, min 0, max 76
Filtered : 424 (13.1%) – Average 13.7, min 7, max
Delivered : 413 (12.9%) – Average 13.3, min 1, max 33
This does not take into account:
– False positives (just a few)
– False negatives (a few as well)
– known and expected relay attemps (check by ISP)
The program to analyse thes is still waiting completion 😉 but I’ve seen the peak on relay attempts is from just one address – probably trying to down the server (all within a minute!).