- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 308 for volume (0.15 sec)
-
cmd/naughty-disk_test.go
func (d *naughtyDisk) StatVol(ctx context.Context, volume string) (vol VolInfo, err error) { if err := d.calcError(); err != nil { return VolInfo{}, err } return d.disk.StatVol(ctx, volume) } func (d *naughtyDisk) DeleteVol(ctx context.Context, volume string, forceDelete bool) (err error) { if err := d.calcError(); err != nil { return err } return d.disk.DeleteVol(ctx, volume, forceDelete) }
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 23 17:15:52 GMT 2024 - 9.3K bytes - Viewed (0) -
cmd/xl-storage-disk-id-check.go
ctx, done, err := p.TrackDiskHealth(ctx, storageMetricDeleteVol, volume) if err != nil { return err } defer done(&err) w := xioutil.NewDeadlineWorker(globalDriveConfig.GetMaxTimeout()) return w.Run(func() error { return p.storage.DeleteVol(ctx, volume, forceDelete) }) }
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Apr 28 17:53:50 GMT 2024 - 33K bytes - Viewed (0) -
cmd/bitrot-whole.go
} // Returns whole-file bitrot writer. func newWholeBitrotWriter(disk StorageAPI, volume, filePath string, algo BitrotAlgorithm, shardSize int64) io.WriteCloser { return &wholeBitrotWriter{disk, volume, filePath, shardSize, algo.New()} } // Implementation to verify bitrot for the whole file. type wholeBitrotReader struct { disk StorageAPI volume string filePath string verifier *BitrotVerifier // Holds the bit-rot info
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jan 31 02:11:45 GMT 2024 - 2.7K bytes - Viewed (0) -
.github/workflows/mint.yml
for volume in $(docker volume ls -q | grep minio); do docker volume rm ${volume} || true done docker rmi -f quay.io/minio/minio:${{ steps.vars.outputs.sha_short }} docker system prune -f || true docker volume prune -f || true
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Mar 28 23:44:49 GMT 2024 - 2.6K bytes - Viewed (0) -
cmd/storage-errors.go
// errVolumeNotEmpty - volume not empty. var errVolumeNotEmpty = StorageErr("volume is not empty") // errVolumeAccessDenied - cannot access volume, insufficient permissions. var errVolumeAccessDenied = StorageErr("volume access denied") // errFileAccessDenied - cannot access file, insufficient permissions. var errFileAccessDenied = StorageErr("file access denied") // errFileCorrupt - file has an unexpected size, or is not readable
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) -
helm/minio/values.yaml
trustedCertsSecret: "" ## Enable persistence using Persistent Volume Claims ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/ ## persistence: enabled: true annotations: {} ## A manually managed Persistent Volume and Claim ## Requires persistence.enabled: true ## If defined, PVC must be created manually before volume will be bound existingClaim: ""
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) -
helm/minio/README.md
You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example,
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K bytes - Viewed (0) -
docs/orchestration/docker-compose/docker-compose.yaml
services: minio1: <<: *minio-common hostname: minio1 volumes: - data1-1:/data1 - data1-2:/data2 minio2: <<: *minio-common hostname: minio2 volumes: - data2-1:/data1 - data2-2:/data2 minio3: <<: *minio-common hostname: minio3 volumes: - data3-1:/data1 - data3-2:/data2 minio4: <<: *minio-common
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
## For custom volumes replace with volume driver configuration. volumes: site1-data1-1: site1-data1-2: site1-data2-1: site1-data2-2: site1-data3-1: site1-data3-2: site1-data4-1:
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
## For custom volumes replace with volume driver configuration. volumes: site2-data1-1: site2-data1-2: site2-data2-1: site2-data2-2: site2-data3-1: site2-data3-2: site2-data4-1:
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)