> So my idea is to mount the vicepa (from external SAN) from the crashed
> file server to the working fileserver as /vicepb so i could get the
> volumes and register the volumes to the working afs fileserver.
Yes, that will need a file server restart to make the working file
server look for a ne
Hallo,
one afs hardware server doesnt come up.
I have got a second working fileserver and want to mount the partition
from the crashed fileserver to the working fileserver.
crashed fileserver has a /vicepa (from external SAN)
working fileserver has a /vicepa (from external SAN)
So my idea is t
If you're on a namei server, you
Well, the volume header names/volume IDs are also visible to ls with
the non-namei server.
And "vos listvol -fast" happily lists off line volumes in the output:
[EMAIL PROTECTED] ~]$ vos listvol angel a | grep bogus
bogusdupevolume.readonly 536
On Dec 7, 2007 6:46 PM, Steve Devine <[EMAIL PROTECTED]> wrote:
...
> Just a datapoint .. running vos listvol with the fast option gives you
> very little info about the vols. It is great if all you are after is
> volume ids but if you want to know whats offline vs whats online its of
> no use.
C
Steven Jenkins wrote:
> On Dec 7, 2007 1:21 PM, Steve Devine <[EMAIL PROTECTED]> wrote:
>
> ...
>
>> As it turns out if you run vos listvol on the server itself its a little
>> quicker and now it seems we are back up for the most part.
>> I have often wondered however if there is a good way t
Look at the FileLog and see what failed to attach.
This is one reason I dislike that optimization.
For the most part, its been a win for me. With a decent filesystem on
the back-end, I haven't had volume attachment problems running with a
fast-restart fileserver. I'd say if I had se
On Dec 7, 2007 1:21 PM, Steve Devine <[EMAIL PROTECTED]> wrote:
>
...
> As it turns out if you run vos listvol on the server itself its a little
> quicker and now it seems we are back up for the most part.
> I have often wondered however if there is a good way to periodically
> check the status of
On Dec 7, 2007 11:53 AM, Steve Devine <[EMAIL PROTECTED]> wrote:
We had a server crash this morning and I after bringing it back up I am
unable to get a vos listvol back from it. Or it is taking a very long
time. These partitions are greater than 150 G . Its been running for 30
minutes now a
What do your bosserver, fileserver, volserver, and salvager logs say?
Steven
On Dec 7, 2007 11:53 AM, Steve Devine <[EMAIL PROTECTED]> wrote:
> We had a server crash this morning and I after bringing it back up I am
> unable to get a vos listvol back from it. Or it is taking a very long
> time. T
Steve Devine wrote:
We had a server crash this morning and I after bringing it back up I am
unable to get a vos listvol back from it. Or it is taking a very long
time. These partitions are greater than 150 G . Its been running for 30
minutes now and nothing back yet.
The server (Version 1.4.2 )
On Dec 7, 2007 11:53 AM, Steve Devine <[EMAIL PROTECTED]> wrote:
> We had a server crash this morning and I after bringing it back up I am
> unable to get a vos listvol back from it. Or it is taking a very long
> time. These partitions are greater than 150 G . Its been running for 30
> minutes now
We had a server crash this morning and I after bringing it back up I am
unable to get a vos listvol back from it. Or it is taking a very long
time. These partitions are greater than 150 G . Its been running for 30
minutes now and nothing back yet.
The server (Version 1.4.2 ) is compiled with fas
12 matches
Mail list logo
