BootStrap

Insufficient disk space (error code -4290)

In OceanBase Database V3.x and earlier versions, the log disk must be deployed independently and exclusively. Starting from OceanBase Database V4.0, logs and other files can be stored together, and users need to configure the specific size of the log disk. OceanBase Database will pre-allocate the disk space for the data disk and CLOG disk when the OBServer starts based on the user's configuration.

Therefore, the configuration items log_disk_size and log_disk_percentage are introduced, and they need to be used together.

• log_disk_size: The size of the log disk, which is the total space available for the OBServer. The default value is 0, indicating that the space should be calculated based on the actual space of the local log disk (compatible with the behavior of OceanBase Database V3.x).

• log_disk_percentage: The percentage of the log disk. When log_disk_size = 0, the log disk space is allocated based on log_disk_percentage. The default value is 0, indicating that the space is automatically calculated based on whether the data and log disks are shared. In scenarios where both configuration items are set, log_disk_size has higher priority.

If both log_disk_size and log_disk_percentage are 0 (default values), the disk space calculation is as follows:

• If data and CLOG are on the same disk, data occupies 60% of the disk space, and CLOG occupies 30%.

• If data and CLOG are on different disks, both data and CLOG occupy 90% of their respective disk spaces.

During the Bootstrap process, if the following error occurs, it indicates insufficient disk space:

grep 'ret=-4290' observer.log

Solution

Correctly specify log_disk_percentage or log_disk_size. For example, specify -o log_disk_percentage=10 during startup.