Probably too late here ... the volserver can be killed without
restarting the fileserver. That will clear the volserver queue without
causing the fileserver to detach/reattach all the volumes, which can
take some minutes depending on how many volumes there are. It also
leaves your file
On Wed, 11 Jul 2007, Kim Kimball wrote:
Probably too late here ... the volserver can be killed without restarting the
fileserver. That will clear the volserver queue without causing the
fileserver to detach/reattach all the volumes, which can take some minutes
depending on how many volumes
Steve Devine wrote:
I committed the cardinal sin of letting a server partition fill up.
I have tried vos remove and vos zap .. I can't get rid of any
vols.Volume management fails on this machine.
Its the old style (non namei) fileserver. It doesn't seem like I can
just rm the V#.vol can I?
I committed the cardinal sin of letting a server partition fill up.
I have tried vos remove and vos zap .. I can't get rid of any
vols.Volume management fails on this machine.
Its the old style (non namei) fileserver. It doesn't seem like I can
just rm the V#.vol can I?
Any help?
--
Steve
Steve Devine wrote:
Hartmut Reuter wrote:
Steve Devine wrote:
I committed the cardinal sin of letting a server partition fill up.
I have tried vos remove and vos zap .. I can't get rid of any
vols.Volume management fails on this machine.
Its the old style (non namei) fileserver. It doesn't
Am Freitag, 6. Juli 2007 schrieb ext Steve Devine:
I committed the cardinal sin of letting a server partition fill up.
I have tried vos remove and vos zap .. I can't get rid of any
vols.Volume management fails on this machine.
Did you try vos remsite to remove readonly copies of rw volumes
Hartmut Reuter wrote:
Steve Devine wrote:
I committed the cardinal sin of letting a server partition fill up.
I have tried vos remove and vos zap .. I can't get rid of any
vols.Volume management fails on this machine.
Its the old style (non namei) fileserver. It doesn't seem like I can
just
Hartmut Reuter wrote:
Steve Devine wrote:
Hartmut Reuter wrote:
Steve Devine wrote:
I committed the cardinal sin of letting a server partition fill up.
I have tried vos remove and vos zap .. I can't get rid of any
vols.Volume management fails on this machine.
Its the old style (non namei)
I tried a
/afs/ipp/backups: vos listvldb 1938590434 -cell msu.edu
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
svc.ml.mdsolids.31
RWrite: 1938590433ROnly: 1938590434RClone: 1938590434
number of sites - 3
server afsfs7.cl.msu.edu partition /vicepa RW
Am Freitag, 6. Juli 2007 schrieb Dirk Heinrichs:
Am Freitag, 6. Juli 2007 schrieb ext Steve Devine:
I committed the cardinal sin of letting a server partition fill up.
I have tried vos remove and vos zap .. I can't get rid of any
vols.Volume management fails on this machine.
Did you try
Hartmut Reuter wrote:
I tried a
/afs/ipp/backups: vos listvldb 1938590434 -cell msu.edu
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
svc.ml.mdsolids.31
RWrite: 1938590433ROnly: 1938590434RClone: 1938590434
number of sites - 3
server
On Fri, 6 Jul 2007, Steve Devine wrote:
Ok in the end we killed all vos commands to that server and restarted
the Bosserver- volserver.
Then we were able to vos remove the RO vols I stupidly put on there in
the first place.
Ran salvager on some horked vols and so far so good.
Just for
12 matches
Mail list logo
