Hi all,
I have a problem with an AdvFS domain.
(We are running OSF/1 3.0B on this 3000/300MX)
Recently during our regular backups I noticed several warnings on one fileset
within this domain. (BTW: the domain contains 5 filesets and spans 3 disks)
> dump: unable to get info for file <./users/jufische/error/cosm0196.bdf>; [5] I/O error
> dump: unable to get info for file <./users/jufische/error/opti0196.bdf>; [9] Bad file number
> dump: unable to get info for file <./users/jufische/error/middummr.bdf>; [9] Bad file number
> dump: unable to get info for file <./users/jufische/error/sigf0196.bdf>; [9] Bad file number
So I decided to vdump the fileset to tape, remove the fileset, recreate it and
vrestore it again. Everything went smoothly. No anomalies on our backups were
seen any more. Everything seemed fine.
Now the time for our weekly defragment came. And this is what I get:
> defragment: Defragmenting domain 'dom_rosat'
>
> Pass 1; Clearing
> Volume 1: area at block 5761392 ( 1225648 blocks): 66% full
> Volume 2: area at block 1136 ( 480144 blocks): 51% full
> Volume 3: area at block 513584 ( 330352 blocks): 48% full
> defragment: Can't find file set hdr - tag 2.32769
> defragment: Can't defragment domain 'dom_rosat'
> Defragment failed for file domain dom_rosat
Remembering some notices on the /usr/field utilities on this list,
I used vchkdir on all 5 filesets - no problems.
BUT msfsck shows a whole bunch of errors, some of them are e.g.:
> check_bitmap: bitmap mismatch
> disk : 2
> map index: 659
> clusters - start: 21088, end: 21119
> real : 0xffffffff
> expected : 0x00000000
....
> set_bitmap: found tag for invalid stg map index 484
> tag = 0x00001c57.04x, set tag = 0x00008010.04x
....
> check_disk: checking storage allocated on disk /dev/rz0g
> check_rec: bad bitfile state - DELETING
> disk: 3, mcell id (page.cell): 750.11
> set tag: 4.32769 (0x00000004.0x00008001)
> tag: 11402.32769 (0x00002c8a.0x00008001)
....
> insert_set_tag: can't get bitfile set params
> error: -1093, E_NO_SUCH_BF_SET (-1093)
> set tag: 2.32769 (0x00000002.0x00008001)
> insert_tag: can't insert set tag
> set tag: 2.32769 (0x00000002.0x00008001)
> tag: 7705.32775 (0x00001e19.0x00008007)
....
> Checking mcell position field...
> check_mcell_position_field: inuse mcell hdr position field zero
> disk: 2, mcell id (page.cell): 457.25
> type: Extent 6
> set tag: 2.32769 (0x00000002.0x00008001)
> tag: 7705.32775 (0x00001e19.0x00008007)
....
> Checking tag directories...
> check_tagdirs: in-mem tag does not have a matching on-disk tag
> set tag: 4.32769 (0x00000004.0x00008001)
> tag: 11402.32769 (0x00002c8a.0x00008001)
These error messages appear while checking any of the 5 filesets in this
domain. No problems appear during vdump of any of the filesets.
Can anybody give me some hints on what to to and where the problem is???
TIA
Andreas Priebe
--
Welcome to the Internet, now go home! <carrel_at_cisco.com>
****************************************************************************
* Andreas Priebe * Phone/FAX: +49 331 7499 320/309 *
* Astrophysical Institute * Email : APriebe_at_aip.de (PGP key available) *
* Potsdam, Germany * WWW : http://www.aip.de:8080/~apr/ *
****************************************************************************
Received on Mon Jul 22 1996 - 10:51:03 NZST