[OpenAFS-devel] delete volume

[chechu chechu]

hey
how can i delete the volume root.afs?
I get this error when i execute the script afs-newcell.

root@shogun:~# afs-newcell 
                            Prerequisites

In order to set up a new AFS cell, you must meet the following:

1) You need a working Kerberos realm with Kerberos4 support.  You
   should install Heimdal with KTH Kerberos compatibility or MIT
   Kerberos 5.

2) You need to create the single-DES AFS key and load it into
   /etc/openafs/server/KeyFile.  If your cell's name is the same as
   your Kerberos realm then create a principal called afs.  Otherwise,
   create a principal called afs/cellname in your realm.  The cell
   name should be all lower case, unlike Kerberos realms which are all
   upper case.  You can use asetkey from the openafs-krb5 package, or
   if you used AFS3 salt to create the key, the bos addkey command.

3) This machine should have a filesystem mounted on /vicepa.  If you
   do not have a free partition, then create a large file by using dd
   to extract bytes from /dev/zero.  Create a filesystem on this file
   and mount it using -oloop.  realm.  This principal will be added to
susers and
   system:administrators and thus will be able to run administrative
   commands.  Generally the user is a root or admin instance of some
   administrative user.  For example if jruser is an administrator then
   it would be reasonable to create jruser/admin (or jruser/root) and
   specify that as the user to be added in this script.

5) The AFS client must not be running on this workstation.  It will be
   at the end of this script.

Do you meet these requirements? [y/n] y
If the fileserver is not running, this may hang for 30 seconds.
/etc/init.d/openafs-fileserver stop
Stopping AFS Server: bosserver.
What administrative principal should be used? chechu/admin

/etc/openafs/server/CellServDB already exists, renaming to .old
/etc/init.d/openafs-fileserver start
Starting AFS Server: bosserver.
bos adduser shogun.ironman.es chechu.admin -localauth

Creating initial protection database.  This will print some errors
about an id already existing and a bad ubik magic.  These errors can
be safely ignored.

pt_util: /var/lib/openafs/db/prdb.DB0: Bad UBIK_MAGIC. Is 0 should be
354545
Ubik Version is: 2.0
Error while creating system:administrators: Entry for id already exists
pt_util: Ubik Version number changed during execution.
Old Version = 2.0, new version = 33554432.0

bos create shogun.ironman.es ptserver simple /usr/lib/openafs/ptserver
-localaut                                                                                                                                 
h
bos create shogun.ironman.es vlserver simple /usr/lib/openafs/vlserver
-localaut                                                                                                                                 
h
bos create shogun.ironman.es fs fs -cmd '/usr/lib/openafs/fileserver -p
23
-busy                                                                                                                                 
at 600 -rxpck 400 -s 1200 -l 1200 -cb 65535 -b 240 -vc 1200'
-cmd /usr/lib/opena                                                                                                                                 
fs/volserver -cmd /usr/lib/openafs/salvager -localauth
Waiting for database elections: 
done.
vos create shogun.ironman.es a root.afs -localauth
vos : partition a does not exist on the server
Failed: 65280

Cell setup failed, ABORTING
bos shutdown shogun.ironman.es -localauth -wait
bos delete shogun.ironman.es fs -localauth
bos delete shogun.ironman.es vlserver -localauth
bos delete shogun.ironman.es ptserver -localauth
rm /var/lib/openafs/db/prdb*
bos removeuser shogun.ironman.es chechu.admin -localauth


thanks


4) You will need an administrative principal created in a Kerberos
   realm.  This principal will be added to susers and