What is true about crash dump configuration?

What is true about crash dump configuration?

What is true about crash dump configuration?

A.
The minfree value can be to protect a percentage of available disk space.

B.
The default size of the dump device is configurable.

C.
You can use one ZFS volume for both swap and dump.

D.
You can set quota on a ZFS dump device.

E.
When set on the dump device, the minfree value sets the total size of the dump device to be a
percentage of the total size of the root pool.

Explanation:
See % below.

coredump parameter: -m mink | minm | min%
Create a minfree file in the current savecore directory indicating that savecore should maintain at
least the specified amount of free space in the file system where the savecore directory is located.
The min argument can be one of the following:
k
A positive integer suffixed with the unit k specifying kilobytes.
m
A positive integer suffixed with the unit m specifying megabytes.
%
A % symbol, indicating that the minfree value should be computed as the specified percentage of
the total current size of the file system containing the savecore directory.
The savecore command will consult the minfree file, if present, prior to writing the dump files. If the
size of these files would decrease the amount of free disk space below the minfree threshold, no
dump files are written and an error message is logged. The administrator should immediately
clean up the savecore directory to provide adequate free space, and re-execute the savecore
command manually. The administrator can also specify an alternate directory on the savecore
command-line.
Incorrect:
Not C: Separate ZFS volumes must be used for the swap area and dump devices.



Leave a Reply 1

Your email address will not be published. Required fields are marked *