What is giving me an alarm signal is:
Since it is a raid1 I expected user space not being affected.
(The other drive did not show any error messages since installation,
they are Maxtors 6Y120L0 (120 GB) cooled quite well) So I thought that
ClearCase should not have seen any error return code.
In the meantime I have just re-synced the faulty drive and there were
no write error messages and the bad block seems to be properly re-mapped
>
> Consult the clearcase support I guess, there should be tools to verify
> your clearcase datasets. You might also want to force an fsck on your
fortunately only one replica packet seems to be corrupted and I can
request it again - the database seems ok after a run of the equivalent
of fsck.
> file systems while the box is down for disk replacement to check
> everything out.
there is still interest what "sector=1766272" actually means, e.g given
a partition table and LBAsect, how to calculate 'sector' or vice versa.
Thanks,
Karl
-- Karl Kiniger karl.kiniger@med.ge.com GE Medical Kretztechnik Tiefenbach 15 A-4871 Zipf Tel: (++43) 7682-3800-710 Fax (++43) 7682-3800-47 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/