From: Greg Rudd (g.rudd@isu.usyd.edu.au)
Date: Tue Nov 05 2002 - 17:06:39 EST
Thanks to Thomas Sjolshagen (Thomas.Sjolshagen@hp.com) and "violin zhang"
<crashdump@altavista.net>
The problem was caused by a bad volume index by executing chvol -A /dev/rz18c
syb_domain fixed the problem. As the volume name was still listed in the
/etc/fdms/syb_domain directory.
Once again thanks to all that replied
Thomas's reply
>From the error message it would seem like you've got a bad volume index
on the device (it's invalid for whatever reason, could be an interrupted
rmvol operation, could be something else). Try doing a 'chvol -A
<domain>' and see if that doesn't clear it up. If this doesn't fix
things, check /etc/fdmns/<domain> for junk (and wheter the device is
still listed there or not) Also, it's *possible* that a reboot may work
(long shot). Lastly, try to run verify.
If verify doesn't work then you're most likely looking at recreating the
data in the domain. Salvage is another utility you can use to minimize
the loss (however, salvage may take a *long* while considering the size
of your domain).
Violin's reply
1) make sure you have a up-to-date backup set for your file system
2) chvol -A to active /dev/rz18c
3) rmvol
4) if step 3 failed, umount your file systems, then remove the link
rz18c in the /etc/fdmns/syb_domain
5) if step 4 failed again, recreate the link rz18c in the
/etc/fdmns/syb_doamain, then run "verify" to check your
domain
6) if verify report error, you should use your backup set to restore
your file systems
---------- Original Message ----------
Subject: adfs error messages.
Date: Tue, 5 Nov 2002 19:05:11 +1100
From: Greg Rudd <g.rudd@isu.usyd.edu.au>
To: tru64-unix-managers@ornl.gov
Hi all
I am getting the fllowing error messages when trying to delete a volume from
a advfs file domain
rmvol: Removing volume '/dev/rz18c' from domain 'syb_domain'
rmvol: Can't get volume parameters
rmvol: Error = EBAD_VDI (-1030)
rmvol: Can't remove volume '/dev/rz18c' from domain 'syb_domain'
When I do a show fdmn on the file domain the following is displayed:
3 60431355 21353936 65% on 256 256 /dev/rzc17c
4 4269351 1226336 71% on 256 256 /dev/rzd19c
5 12432899 2576992 79% on 256 256 /dev/rzg20c
7 18649543 17088 100% on 256 256 /dev/rz20c
8 4269351 0 100% on 256 256 /dev/rze19c
9 10240000 27936 100% on 256 256 /dev/rzc18d
-data unavailable- on 256 256 /dev/rz18c
12 10240000 125088 99% on 256 256 /dev/rzc18b
13 157286400 137486576 13% on 256 256 /dev/rzf24c
Note that /dev/rz18c is the volume I want to delete.
Also I am getting the following messages in the /var/adm/messages log:
Nov 5 12:56:21 vmunix: advfs_logger: pg #510 is bad; truncating log
Nov 5 12:56:21 vmunix: advfs_logger: pg #509 is bad; truncating log
Nov 5 12:56:21 vmunix: advfs_logger: pg #508 is bad; truncating log
Nov 5 12:56:21 vmunix: advfs_logger: pg #507 is bad; truncating log
Nov 5 12:56:21 vmunix: advfs_logger: pg #506 is bad; truncating log
Nov 5 12:56:21 vmunix: advfs_logger: pg #505 is bad; truncating log
Nov 5 12:56:21 vmunix: advfs_logger: pg #504 is bad; truncating log
Nov 5 12:56:21 vmunix: advfs_logger: pg #503 is bad; truncating log
Nov 5 12:56:21 vmunix: advfs_logger: pg #502 is bad; truncating log
Nov 5 12:56:22 vmunix: advfs_logger: can't find log end
My question is there a way to remedy this problem without having to blow the
fileset away and restoring all the data from scratch??
Thanks in advance will summarise.
-greg
-------------------------------------------------------
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:58 EDT