what version of server are you running...???
I've noticed in pre 3.1.2.30(?) prior to the "cleanup archdir fix=yes"
option,  that if I'd try to delete a filespace with a server that had
archived data (and thus the archived entry into the longest retention
archive management class) and if that entry had not yet naturally expired
(which was tough 'cause I have 10 year archive management classes) THAT it
would bring down the adsm server and never clean up the data for the
filespace.

Now how I got around that prior to upgrading the server, was to set a domain
(I called remove) with no retention of anything longer than a day... (that
is primarily that archive retention grace period) anyway I'd move the node
over into that domain, run expiration, then I could delete the filespaces
and remove the node...

I was shooting for total removal of the node.

This might not fit your problem but in case anyone running an older version
of adsm has been wondering why their server abended when you run a delete
file space, hope this helps.

Dwight

> ----------
> From:         Elaine Luty[SMTP:elaine_luty AT CSUFRESNO DOT EDU]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Tuesday, April 18, 2000 3:45 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      junk filespace
>
> Does someone have a magic way to delete a filespace that doesn't want to
> be
> deleted, i.e., a force-type command?  I've tried renaming, by gui, by
> command line.  I don't get an errors when trying to delete the filespace,
> but 0 files get deleted and the filespace remains intact with data still
> existing.
>
> Thanks very much in advance,
>
> Elaine C. Luty
>
> elaine_luty AT csufresno DOT edu
> Operating Systems Analyst
> Information Technology Services
> California State University, Fresno
>
> PGP PUBLIC KEY AVAILABLE UPON REQUEST