[OpenAFS] Not a directory

Turbo Fredriksson turbo@bayour.com
08 Apr 2002 10:07:49 +0200


Quoting Charles Clancy <security@xauth.net>:

> If you don't intend to recreate user.backup, then you might as well "fs
> rmm /afs/.bayour/user.backup" to remove the mount point.

----- s n i p -----
[papadoc.pts/3]$ fs rmm /afs/.bayour/user.backup 
fs:'/afs/.bayour/user.backup': Not a directory
----- s n i p -----

> According to the above, you deleted both the volume and the VLDB entry,
> but the entry still shows up in the VLDB.  Try doing the "vos delentry
> 536870918" again,

Deleted one entry...

> but "vos examine user.backup" before syncing the VLDB
> (the syncvldb step should not be needed).

----- s n i p -----
[papadoc.pts/3]$ vos examine user.backup
VLDB: no such entry
----- s n i p -----

Tried the syncvldb command (after all the commands below),
and it synced the state with the server. Still the 'Connection
timed out' error...

>  Also, what does a "vos examine
> user" give you?  Does it list the backup volume?

Oups!
----- s n i p -----
[papadoc.pts/3]$ vos examine user
VLDB: no such entry
----- s n i p -----

The data is still there though. *puhe*

> My only other suggestion, if you haven't tried it already, would be to
> "bos restart papadoc vlserver" to restart the vlserver process.

Well, I've tried to restart the whole system (not intentionaly though, the
UPS power wasn't enough after a power failiure... :) but tried the restart
command, still get the 'Connection timed out'...

> > Yes. But you have to 'mount' the snapshot for it to be usefull, and if
> > the new mountpoint is big, you need a tape to back it up to... :)
> 
> In general, you should have bos cron process that runs "vos backupsys"
> daily to create backup volumes for everything.  This can be done
> independently of implementing a tape-backup system.  

I see. I thought I had to 'mount' it to be able to put it on tape... But
if I have non-AFS FS' that I'd like to have on the same tape, then what?

> If you can't get rid
> of the VLDB entry for user.backup, then I strongly suggest trying to
> recreate the volume with a "vos backup user".  If you have no desire to
> keep the volume, then delete it "properly" with a "vos remove papadoc
> vicepa user.backup".

Since I have no intention on keeping user.backup (it was just some test
with the backup commands) I tried the remove command line:

----- s n i p -----
[papadoc.pts/3]$ vos remove papadoc vicepa user.backup
Can't find volume name 'user.backup' in VLDB
VLDB: no such entry
----- s n i p -----


Creating a backup volume for user worked, but how do I get rid of it?
Something like "I'm done with the backup, remove the entry" ? Is it
ok/correct to just do 'vos remove -id user.backup' after a backup is
finished, or could it be leaved alone, and after the next 'vos backup user'
it will be "recreated"?
-- 
KGB Delta Force iodine South Africa Ft. Bragg World Trade Center CIA
Uzi strategic assassination PLO [Hello to all my fans in domestic
surveillance] jihad SDI nuclear
[See http://www.aclu.org/echelonwatch/index.html for more about this]