There's a server that was decommissioned many moons ago that I'm trying to
delete. The problem is there's a volume still associated with it [1], a RO
volume at that. When I attempt to remove the volume usin its volume id I get
this message:
--BEGIN--
Could not delete entry for volume 536988828
On Sun, 31 Jul 2011, Aaron Knister wrote:
There's a server that was decommissioned many moons ago that I'm trying to
delete. The problem is there's a volume still associated with it [1], a RO
volume at that. When I attempt to remove the volume usin its volume id I get
this message:
Try vos
Gary,
Thanks for the suggestion, unfortunately that didn't work:
$ vos remsite -server 130.85.24.58 -partition /vicepa -id 536988828
Could not lock the VLDB entry for volume 536988828
VLDB: no such entry
Error in vos remsite command.
VLDB: no such entry
Something I did just now was change the
Make that a vos syncserv not a syncvldb
On Sun, Jul 31, 2011 at 4:09 PM, Aaron Knister aar...@umbc.edu wrote:
Gary,
Thanks for the suggestion, unfortunately that didn't work:
$ vos remsite -server 130.85.24.58 -partition /vicepa -id 536988828
Could not lock the VLDB entry for volume
On 31 Jul 2011, at 21:15, Aaron Knister aar...@umbc.edu wrote:
Make that a vos syncserv not a syncvldb
If I'm understanding your problem correctly you have a single entry for a RO
volume in your VLDB, with the corresponding server long since departed. In this
case, vos delentry should let
That's what I thought, however delent doesn't seem to work on RO volumes IIRC.
Whatever the reason, delent fails.
Sent from my iPhone
On Jul 31, 2011, at 7:38 PM, Simon Wilkinson s...@inf.ed.ac.uk wrote:
On 31 Jul 2011, at 21:15, Aaron Knister aar...@umbc.edu wrote:
Make that a vos
What happens if you use the old hostname or the old ip address? Whatever
the vldb gives indications that it thinks it is on? (Same thing with the
partition) If it thinks it s a hostname, use that one. If it thinks
its an IP address, use that one.
I think vos remsite only works with the
On Jul 31, 2011, at 14:51, Aaron Knister aar...@umbc.edu wrote:
There's a server that was decommissioned many moons ago that I'm trying to
delete. The problem is there's a volume still associated with it [1], a RO
volume at that. When I attempt to remove the volume usin its volume id I
On Mon, Aug 26, 2002 at 06:01:42PM -0400, Derrick J Brashear wrote:
Fine, so I'd guess:
if ((fd = open(path, O_RDONLY)) == -1 || fstat(fd,status) == -1) {
close(fd);
VOL_LOCK
*ec = VNOVOL;
goto done;
}
That doesn't fail but...
fails. strace is your
