Share:|

This is a frequent Support problem.

 

This blog addresses 3 cases:

 

1) I am running low on space on my datastore disk

 

2) I am out of space on my datastore disk

 

3) I am out of space in /usr  and my datastore is part of /usr  (i.e. we never created a new disk for the datastore)

 

 

FAQ:

1) Can I remove files from my datastore disk to reduce the space?
    NO.  Absolutely not.  You will corrupt your datastore by trying this option.

 

2) Can I remove files from the /usr partition to clear space?
    Yes, see this blog:    ADDM out of disk space in /usr

 

 

Solutions for each problem:

 

1) I am running low on space on my datastore disk

 

You have options because you still have some space, so your services have not been shut down (yet).

 

Options for solution:

 

a) You could compact your datastore:
    You use tw_ds_offline_compact command.  Instructions for ADDM 11 are here:

   tw_ds_offline_compact - BMC Discovery 11.0 - BMC Documentation 

 

    This may or may not improve discovery performance.

 

    A compact may take a long time, such as "over the weekend".  The larger your datastore, the longer it will take.

 

    You may not have enough space to perform the compact, but the tw_ds_offline_compact utility will tell you that at the beginning of its run.

 

b) You can move your datastore to a new disk:

     Instructions:

     First, you need a new disk large enough to contain the entire existing datastore + plenty of space for growth.

     You can not extend the disk where your datastore is.

 

     After you add a new disk, the Administration->Disk Configuration page will become useful, and will allow you to move the disk to the new datastore with the click of a button.

 

c) Compacting the datastore, and then moving it to a larger disk is probably the best choice.

 

2) I am out of space on my datastore disk

 

You do not have options because your services are shut down at this point.

There is no GUI to move your datastore, and there is no space to perform a compact.

 

So, your only option is this:

You must move your datastore to a new disk:

    Instructions:

    First, you need a new disk large enough to contain the entire existing datastore + plenty of space for growth.

    You can not extend the disk where your datastore is.

 

    After you add a new disk, you can try using the undocumented command tw_disk_utils to move your datastore.

     If you do this, you will see some good help for tw_disk_utils:

 

     cd /usr/tideway/bin

     tw_disk_utils --help

 

     After you add new disk, you can use "fdisk -l" to list the new disk so you know how it is named.

 

    There is a helpful Knowledge Article about this:  000082640

 

     Probably best to open a ticket with Support for this operation.

 

     After you move your datastore to new disk, you could run a compact.  (See item 1a above).

 

3) I am out of space in /usr  and my datastore is in /usr (i.e. we never created a new disk for the datastore)

 

    First, see this blog:  ADDM out of disk space in /usr

 

     Using those steps, you should be able to at least get your services started.

     Then, you can follow the steps for problem #1.

 

FAQ:

a)  QUESTION:  I had 200gig available for ADDM partitions, but after the install, ADDM only takes 50gig.  How can I get my datastore to use that other 150gig?  

     ANSWER: You can't, sorry.

 

b)  QUESTION:  Can I extend my datastore partition?

      ANSWER:  Not recommended

 

c)  QUESTION:  I really don't want to add a new disk.  What can I do?   

     ANSWER:  You really need to add a new disk.

 

See these related Knowledge Article(s):

 

000094102 - ADDM: The appliance has shut down because available disk space is low