You can get the mirrors offline and then fsck the master disk and then
attach the mirror again to re-sync it. Hopefully, it should fix the
problem.
Josh
-----Original Message-----
From: Steven Law
To: [EMAIL PROTECTED]
Sent: 1/22/01 4:08 AM
Subject: Block errors with Mirror disk
Hi
I recently added a new disk mirror to one of our SUN servers but I can't
get amanda to back it up. The other disk mirrors backup fine and the
metatool program doesn't report any problems with this mirror. The
errors
I get in sendsize.debug are as follows .....
DUMP: Writing 32 Kilobyte records
DUMP: Date of this level 0 dump: Fri Jan 19 21:30:59 2001
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/md/rdsk/d17 (ms-utilserver:/opt) to standard
output.
DUMP: Mapping (Pass I) [regular files]
DUMP: Mapping (Pass II) [directories]
DUMP: Warning - block 1751264504 is beyond the end of
`/dev/md/rdsk/d17'
DUMP: Warning - directory at inode `195147' is corrupted
DUMP: bread: dev_seek error: Invalid argument
DUMP: Warning - directory at inode `195147' is corrupted
DUMP: Warning - block 827549914 is beyond the end of
`/dev/md/rdsk/d17'
DUMP: Warning - directory at inode `195147' is corrupted
DUMP: bread: dev_seek error: Invalid argument
[ .... etc ....]
Maybe I need to change a parameter. Anyone any ideas ?
Regards
Steve Law
--
Computing Officer
Department of Mathematics and Statistics, Edinburgh University.
Phone: 0131 650 5037 , Email: [EMAIL PROTECTED]
Home Page: http://www.maths.ed.ac.uk/~steve
