- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 107 for devices (0.2 sec)
-
cmd/storage-errors.go
// verification is empty or invalid. var errBitrotHashAlgoInvalid = StorageErr("bit-rot hash algorithm is invalid") // errCrossDeviceLink - rename across devices not allowed. var errCrossDeviceLink = StorageErr("Rename across devices not allowed, please fix your backend configuration") // errLessData - returned when less data available than what was requested.
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 04 12:04:40 GMT 2024 - 6.4K bytes - Viewed (0) -
internal/disk/stat_linux.go
info.Name = devName qst, err := bfs.SysBlockDeviceQueueStats(devName) if err != nil { // Mostly not found error // Check if there is a parent device: // e.g. if the mount is based on /dev/nvme0n1p1, let's calculate the // real device name (nvme0n1) to get its sysfs information parentDevPath, e := os.Readlink("/sys/class/block/" + devName) if e == nil {
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Feb 26 19:34:50 GMT 2024 - 4.8K bytes - Viewed (0) -
buildscripts/verify-healing-with-root-disks.sh
# Prepare fake disks with losetup function prepare_block_devices() { set -e mkdir -p ${WORK_DIR}/disks/ ${WORK_DIR}/mnt/ sudo modprobe loop for i in 1 2 3 4; do dd if=/dev/zero of=${WORK_DIR}/disks/img.${i} bs=1M count=2000 device=$(sudo losetup --find --show ${WORK_DIR}/disks/img.${i}) sudo mkfs.ext4 -F ${device} mkdir -p ${WORK_DIR}/mnt/disk${i}/ sudo mount ${device} ${WORK_DIR}/mnt/disk${i}/
Shell Script - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri May 26 05:07:25 GMT 2023 - 2.2K bytes - Viewed (0) -
docs/sts/web-identity.md
access policies for applications/users to interact with MinIO object storage. Calling AssumeRoleWithWebIdentity does not require the use of MinIO root or IAM credentials. Therefore, you can distribute an application (for example, on mobile devices) that requests temporary security credentials without including MinIO long lasting credentials in the application. Instead, the identity of the caller is validated by using a JWT id_token from the web identity provider. The temporary security credentials...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 19.2K bytes - Viewed (1) -
internal/mountinfo/mountinfo_linux.go
// - mount.Path doesn't match (means cross-device mount), should error out. if mount.Path != path { crossMounts = append(crossMounts, mount) } } } msg := `Cross-device mounts detected on path (%s) at following locations %s. Export path should not have any sub-mounts, refusing to start.` if len(crossMounts) > 0 { // if paths didn't match then we do have cross-device mount. return fmt.Errorf(msg, path, crossMounts)
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Jan 02 17:15:06 GMT 2022 - 4.7K bytes - Viewed (0) -
docs/orchestration/docker-compose/docker-compose.yaml
interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - data1-1:/data1 - data1-2:/data2 minio2: <<: *minio-common hostname: minio2 volumes:
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed May 01 02:45:52 GMT 2024 - 1.5K bytes - Viewed (1) -
.github/workflows/multipart/docker-compose-site1.yaml
environment: - MINIO_PROMETHEUS_AUTH_TYPE=public - CI=true # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: site1-minio1: <<: *minio-common hostname: site1-minio1 volumes: - site1-data1-1:/data1 - site1-data1-2:/data2 site1-minio2: <<: *minio-common hostname: site1-minio2
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Sep 30 10:13:56 GMT 2023 - 1.5K bytes - Viewed (0) -
.github/workflows/multipart/docker-compose-site2.yaml
environment: - MINIO_PROMETHEUS_AUTH_TYPE=public - CI=true # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: site2-minio1: <<: *minio-common hostname: site2-minio1 volumes: - site2-data1-1:/data1 - site2-data1-2:/data2 site2-minio2: <<: *minio-common hostname: site2-minio2
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Sep 30 10:13:56 GMT 2023 - 1.5K bytes - Viewed (0) -
.github/workflows/mint/minio-pools.yaml
interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - pdata1-1:/pdata1 - pdata1-2:/pdata2 minio2: <<: *minio-common hostname: minio2 volumes:
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Nov 03 21:18:18 GMT 2023 - 2.3K bytes - Viewed (0) -
helm/minio/values.yaml
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Apr 28 10:14:37 GMT 2024 - 18.4K bytes - Viewed (0)