| `minio_node_replication_average_transfer_rate`          | Average replication transfer rate in bytes/sec                                                           |
| `minio_node_replication_max_transfer_rate`              | Maximum replication transfer rate in bytes/sec seen since server start                                   |

	return
}

func newDriveMetricsCache() *cachevalue.Cache[storageMetrics] {
	var (
		// prevDriveIOStats is used to calculate "per second"
		// values for IOStat related disk metrics e.g. reads/sec.
		prevDriveIOStats            map[string]madmin.DiskIOStats
		prevDriveIOStatsMu          sync.RWMutex
		prevDriveIOStatsRefreshedAt time.Time
	)

MinIO supports two different types of server-side encryption ([SSE](#sse)):

- **SSE-C**: The MinIO server en/decrypts an object with a secret key provided by the S3 client as part of the HTTP request headers. Therefore, [SSE-C](#ssec) requires TLS/HTTPS.
- **SSE-S3**: The MinIO server en/decrypts an object with a secret key managed by a KMS. Therefore, MinIO requires a valid KMS configuration for [SSE-S3](#sses3).

### Server-Side Encryption - Preliminaries

	// current cluster does not have the object yet. This is in a site/bucket replication scenario.
	MinIOTaggingProxied = "X-Minio-Tagging-Proxied"
	// Header indicates the actual replicated object size
	// In case of SSEC objects getting replicated (multipart) actual size would be needed at target
	MinIOReplicationActualObjectSize = "X-Minio-Replication-Actual-Object-Size"

	// predicted date/time of transition

pkg syscall (freebsd-386-cgo), type SysProcAttr struct, Setsid bool
pkg syscall (freebsd-386-cgo), type Timespec struct, Nsec int32
pkg syscall (freebsd-386-cgo), type Timespec struct, Sec int32
pkg syscall (freebsd-386-cgo), type Timeval struct, Sec int32
pkg syscall (freebsd-386-cgo), type Timeval struct, Usec int32
pkg syscall (freebsd-386-cgo), type WaitStatus uint32
pkg syscall (freebsd-386-cgo), var Stderr int

                /*
                 * The SMB_COM_NT_CREATE_ANDX response wordCount is wrong. There's an
                 * extra 16 bytes for some "Offline Files (CSC or Client Side Caching)"
                 * junk. We need to bump up the wordCount here so that this method returns
                 * the correct number of bytes for signing purposes. Otherwise we get a

	CRC32CW R9, R3, R21                        // 7558c91a
	CRC32CX R11, R0, R24                       // 185ccb9a
	CSELW LO, R4, R20, R12                     // 8c30941a
	CSEL GE, R0, R12, R14                      // 0ea08c9a
	CSETW GE, R3                               // e3b79f1a
	CSET LT, R30                               // fea79f9a
	CSETMW VC, R5                              // e5639f5a
	CSETM VS, R4                               // e4739fda

    protected String headerKey;

    protected boolean encryptedHeaderValue = true;

    protected String cookieKey;

    protected boolean encryptedCookieValue = true;

    protected long maxAge = 30 * 60; // sec

    protected Map<String, String> cookieNameMap;

    protected final List<String> defaultRoleList = new ArrayList<>();

    @PostConstruct
    public void init() {
        if (logger.isDebugEnabled()) {

			writeErrorResponse(ctx, w, toAPIError(ctx, errInvalidEncryptionParameters), r.URL)
			return
		}

		if crypto.SSEC.IsRequested(r.Header) && crypto.S3.IsRequested(r.Header) {
			writeErrorResponse(ctx, w, toAPIError(ctx, crypto.ErrIncompatibleEncryptionMethod), r.URL)
			return
		}

		if crypto.SSEC.IsRequested(r.Header) && crypto.S3KMS.IsRequested(r.Header) {

                readParameterWordsWireFormat( buffer, bufferIndex + 4 );

                /* The SMB_COM_NT_CREATE_ANDX response wordCount is wrong. There's an
                 * extra 16 bytes for some "Offline Files (CSC or Client Side Caching)"
                 * junk. We need to bump up the wordCount here so that this method returns
                 * the correct number of bytes for signing purposes. Otherwise we get a