Greetings !
Scenario : Alphaserver 8400, HSZ70, RAID5, DU 4.0B Patch #7
A vdump is taken on a cloned filesystem (base7, a database location),
while there is a fair amount of activity on the database (don't know
specifically about the activity on this location). And then, suddenly...
>From DECevent :
SWI Minor class 9. ASCII Message
SWI Minor sub class 1. Panic
ASCII Message panic (cpu 0): can't pin page
N1 = 5
>From /var/adm/messages :
Nov 10 01:30:24 alibd vmunix: AdvFS I/O error:
Nov 10 01:30:24 alibd vmunix: Domain#Fileset: base7_domain#base7
Nov 10 01:30:24 alibd vmunix: Mounted on: /base7
Nov 10 01:30:24 alibd vmunix: Volume: /dev/rzd8h
Nov 10 01:30:24 alibd vmunix: Tag: 0x000005da.8002
Nov 10 01:30:24 alibd vmunix: Page: 10526
Nov 10 01:30:24 alibd vmunix: Block: 7198144
Nov 10 01:30:24 alibd vmunix: Block count: 80
Nov 10 01:30:24 alibd vmunix: Type of operation: Read
Nov 10 01:30:24 alibd vmunix: Error: 5
Nov 10 01:30:24 alibd vmunix: To obtain the name of the file on which
Nov 10 01:30:24 alibd vmunix: the error occurred, type the command:
Nov 10 01:30:24 alibd vmunix: /sbin/advfs/tag2name /base7/.tags/1498
Nov 10 01:30:24 alibd vmunix: ^G^G^G^G^G^G^G^G^G^G
Nov 10 01:30:24 alibd vmunix:
Nov 10 01:30:24 alibd last message repeated 2 times
Nov 10 01:30:24 alibd vmunix: WARNING: advfs cannot copy-on-write data to a
clone file.
Nov 10 01:30:24 alibd vmunix: errno = 5
Nov 10 01:30:24 alibd vmunix: WARNING: encountered the following error:
errno
Nov 10 01:30:24 alibd vmunix: WARNING: do not continue using the clone
fileset.
Nov 10 01:30:24 alibd vmunix: WARNING: original file set: name = base7, id =
35c09726.000a8f10.00000001.8001
Nov 10 01:30:24 alibd vmunix: WARNING: clone file set: name = clone_base7,
id = 35c09726.000a8f10.00000002.806c
Nov 10 01:30:24 alibd vmunix: WARNING: file id = 000005da.8002
Nov 10 01:30:24 alibd vmunix:
Nov 10 01:48:28 alibd vmunix: AdvFS I/O error:
Nov 10 01:48:28 alibd vmunix: Domain#Fileset: base6_domain#base6
Nov 10 01:48:28 alibd vmunix: Mounted on: /base6
Nov 10 01:48:28 alibd vmunix: Volume: /dev/rzd8g
Nov 10 01:48:28 alibd vmunix: Tag: 0x00000004.8001
Nov 10 01:48:28 alibd vmunix: Page: 0
Nov 10 01:48:28 alibd vmunix: Block: 13904
Nov 10 01:48:28 alibd vmunix: Block count: 16
Nov 10 01:48:28 alibd vmunix: Type of operation: Read
Nov 10 01:48:28 alibd vmunix: Error: 5
Nov 10 01:48:28 alibd vmunix: To obtain the name of the file on which
Nov 10 01:48:28 alibd vmunix: the error occurred, type the command:
Nov 10 01:48:28 alibd vmunix: /sbin/advfs/tag2name /base6/.tags/4
Nov 10 01:48:28 alibd vmunix: AdvFS I/O error:
Nov 10 01:48:28 alibd vmunix: Volume: /dev/rzd8g
Nov 10 01:48:28 alibd vmunix: Tag: 0xfffffff9.0000
Nov 10 01:48:28 alibd vmunix: Page: 1
Nov 10 01:48:28 alibd vmunix: Block: 128
Nov 10 01:48:28 alibd vmunix: Block count: 16
Nov 10 01:48:28 alibd vmunix: Type of operation: Read
Nov 10 01:48:28 alibd vmunix: Error: 5
Nov 10 01:48:28 alibd vmunix: ADVFS EXCEPTION
Nov 10 01:48:28 alibd vmunix: Module = bs_sbm.c, Line = 774
Nov 10 01:48:28 alibd vmunix: can't pin page
Nov 10 01:48:28 alibd vmunix: N1 = 5
Nov 10 01:48:28 alibd vmunix: panic (cpu 0): can't pin page
Nov 10 01:48:28 alibd vmunix: N1 = 5
Nov 10 01:48:28 alibd vmunix: syncing disks... DUMP.prom: dev RAID 0 5 0 0 1
0 0, block 0
Nov 10 01:48:28 alibd vmunix: DUMP.prom: dev RAID 0 5 0 0 1 0 0, block 0
base6 and base7 are two domains sharing a physical disk (I know this is not
recommended
but it worked well for about half a year). We don't discard hardware
problems, but this is
a RAID5 volume, so I guess it should not handle a failure in this
catastrophic way.
This is 4.0B patch #7, does anybody know if there is another patch available
for this kind of problem ? Of course I'll summarize.
As usual, many thanks in advance,
Miguel Fliguer - MINIPHONE S.A.
Buenos Aires, Argentina
Received on Tue Nov 10 1998 - 14:10:28 NZDT