NOTICE: COMMUNITY PERFORMANCE DEGRADATION
Our community is currently experiencing some performance degradation with slow page loading. Our platform SaaS vendor is working on the issue.
Highlighted
Absent Member.
Absent Member.
1404 views

Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

Hi all. I know to get more disk space I should add another disk and use
NSS. I have a _ADMIN (what am I saying; we all have _ADMIN!) that is 100%
unused! All that memory out there. Is there any way at all I can assign
this space to another volume? I'm using NW6SP5. My other volumes are NSS
but I can't see _ADMIN anywhere (is that normal). thanks
Labels (1)
0 Likes
11 Replies
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

_Admin is usually about 4MB, so you won't fit much on there and is a
system generated dynamic volume anyway, so I'd leave it alone

Cheers Dave


--

Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

_ADMIN does not take any disk space. It's a virtual volume that only
exists in memory and the size reported is just bogus. If you try to write
random files to it, they are just lost. The purpose of the _ADMIN volume
is to allow certain things on the server to be configured or actions to be
performed through file system calls or check the status of certain server
components through file system calls. E.g. for example NSS statistics are
available on on of those virtual files.

--
Marcel Cox (using XanaNews 1.18.1.0)
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

On Mon, 27 Feb 2006 21:14:45 +0200, Marcel Cox <cimetmc@myrealbox.com>
wrote:

> _ADMIN does not take any disk space. It's a virtual volume that only
> exists in memory and the size reported is just bogus. If you try to
> write random files to it, they are just lost. The purpose of the _ADMIN
> volume is to allow certain things on the server to be configured or


So we can remove it from NDS? After deleting NDS object _ADMIN it's still
alive as shown in Portal. Is there a way recreate it to NDS? I have one
"bad" server_ADMIN volume, looking for properties C1 is giving error
"Unable to get attributes .... Failed to get current label on volume.
....error code was 152."

Server 6.0 sp5
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

Arno Arengu wrote:

> Is there a way recreate it to NDS?


By running dSREPAIR in the advanced options, you have the option to check
trustees and repair volume objects.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

On Tue, 28 Feb 2006 16:24:25 +0200, Marcel Cox <cimetmc@myrealbox.com>
wrote:

>> Is there a way recreate it to NDS?

>
> By running dSREPAIR in the advanced options, you have the option to
> check trustees and repair volume objects.


Yes, but this checks real volumes only(?), not ADMIN one. Functions, like
Salvage, are working without admin volume in NDS. Console Monitor shows
_ADMIN 4MB 0% full volume, also Netware portal. But no C1 and NWadmin32 as
NDS object.

Don't fix if it's working?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

For practical purposes, you probably don't need the admin volume in NDS. I
think it is only on clusters that the NDS admin volume is more important.

--
Marcel Cox (using XanaNews 1.18.1.0)
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

Within C1, you can create a new volume object, call it Admin and point it
at the correct server. I've had to do that here a couple of times

Cheers Dave


--

Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

Dave Parkes wrote:

> Within C1, you can create a new volume object, call it Admin and point it at
> the correct server. I've had to do that here a couple of times


Just right now I noticed, that the _ADMIN volume objects are named
"ADMIN_SERVERNAME". All other volumes are named "SERVERNAME_VOLUME".

So the name I would have expected would have been either "SERVER__ADMIN" or at
least "_ADMIN_SERVER". Amazing, this virtual volume...


Regards, Rudi.

--
IT-Beratung Rudolf Thilo
Schweinfurter Str. 131
97464 Niederwerrn
t: +49 (0)9721/6464840
f: +49 (0)9721/6464841
m: +49(0)171/685 9 685
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

So, (belatedly), it worked OK ?

Cheers Dave


--

Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

Dave Parkes wrote:

> So, (belatedly), it worked OK ?
>
> Cheers Dave


I had no problem. I just noticed, that the way the eDir volume name is build
differs from the default naming convention of all other volumes.


Regards, Rudi.

--
IT-Beratung Rudolf Thilo
Schweinfurter Str. 131
97464 Niederwerrn
t: +49 (0)9721/6464840
f: +49 (0)9721/6464841
m: +49(0)171/685 9 685
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Completley unused _ADMIN volume. Is there ANY WAY I can move that space...

Good <g>, as for the different name format, I'd guess the same, it is
because they are not real

Cheers Dave


--

Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.