🚀 go-pugleaf

Hello,
After christmas we found that our 4D-220VGX had crashed in a mysterious way:
many programs of the OS could not be found any more, we had to reload 
the root partition from the last backup. In SYSLOG there were the following
messages:
Dec 27 03:13:19 gt unix: WARNING: dma_map: address not word aligned
Dec 27 03:13:19 gt unix: sc0,1,0: cmd=0x28 disconnected on non-word boundary (ad
dr=C046AE4F, 0x0 left)
Dec 27 03:13:21 gt unix: .  Resetting SCSI bus
Dec 27 03:13:21 gt unix: dks0d3s0 (/usr): retrying request
Dec 27 03:13:21 gt unix: dks0d1s6 (/usr/amandus): retrying request

(repeated several times) and

Dec 27 05:02:12 gt unix: dks0d1s0 (/): Directory 13 is corrupted (4d)
Dec 27 05:02:13 gt unix: dks0d1s0 (/): inum: 19 illegal number of indirect exten
ts
Dec 27 05:02:13 gt unix: 
Dec 27 05:02:13 gt unix: dks0d1s0 (/): inum: 20 illegal number of indirect exten
ts

(also with some other numbers instead of 19,20)

After restoring the backup everything worked just fine. However, a few
minutes ago I saw 
Jan  1 05:00:15 gt unix: dks0d1s6 (/usr/amandus): inum: 1724 illegal number of i
ndirect extents
Jan  1 05:00:15 gt unix: 
Jan  1 05:00:16 gt unix: dks0d1s6 (/usr/amandus): inum: 1725 illegal number of i
ndirect extents

in SYSLOG. Is this just a sign of the disk going bad (I admit it's no SGI disk,
but has workes flawlessly for at least 3 years now) or did we
inadvertently make some configuration or software error ?

Thanks very much for any hints,



-- 

   Rainer Kleinrensing,    rainer@indigo.mathematik.uni-freiburg.de
   Institute for Applied Mathematics
   Freiburg University