Archive for Dezember, 2020
Freitag, Dezember 11th, 2020
MinIO protects data against hardware failures and silent data corruption using erasure code and checksums with the highest level of redundancy you may lose up to half (N/2) of the total drives and still be able to recover the data
MinIO divides the drives you provide into erasure-coding sets of 4 to 16 drives therefore the number of drives you present must be a multiple of one of these numbers. Each object is written to a single erasure-coding set
root@rpi-iot-jsho-docker-01:~# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 59269452 5023168 51787272 9% /
devtmpfs 440244 0 440244 0% /dev
tmpfs 473524 0 473524 0% /dev/shm
tmpfs 473524 6532 466992 2% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 473524 0 473524 0% /sys/fs/cgroup
/dev/mmcblk0p1 258095 55052 203043 22% /boot
tmpfs 94704 4 94700 1% /run/user/1000
/dev/sdh 1424 1 1423 1% /media/pi/6C96-E1A0
/dev/sdg1 3899392 2944 3896448 1% /media/pi/MINIO 1
/dev/sdf 1424 1 1423 1% /media/pi/6C96-E1A01
/dev/sde 1424 1377 47 97% /media/pi/6C96-E1A02
/dev/sdd1 3899392 3008 3896384 1% /media/pi/MINIO 4
/dev/sdc 1424 1377 47 97% /media/pi/6C96-E1A03
/dev/sdb1 3899392 2976 3896416 1% /media/pi/MINIO 2
/dev/sda1 3899392 3008 3896384 1% /media/pi/MINIO 3
# docker run -p 9000:9000 –name MinIO-01 -v /media/pi/“MINIO 1″:/data0 -v /media/pi/“MINIO 2″:/data1 -v /media/pi/“MINIO 3″:/data2 -v /media/pi/“MINIO 4″:/data3 -e „MINIO_ACCESS_KEY=<AccessKey>“ -e „MINIO_SECRET_KEY=<SecretKey>“ minio/minio server /data{0…3}
Formatting 1st zone, 1 set(s), 4 drives per set.
WARNING: Host local has more than 2 drives of set. A host failure will result in data becoming unavailable.
Attempting encryption of all config, IAM users and policies on MinIO backend
Status: 4 Online, 0 Offline.
Endpoint: http://172.17.0.2:9000 http://127.0.0.1:9000
Browser Access:
http://172.17.0.2:9000 http://127.0.0.1:9000
Object API (Amazon S3 compatible):
Go: https://docs.min.io/docs/golang-client-quickstart-guide
Java: https://docs.min.io/docs/java-client-quickstart-guide
Python: https://docs.min.io/docs/python-client-quickstart-guide
JavaScript: https://docs.min.io/docs/javascript-client-quickstart-guide
.NET: https://docs.min.io/docs/dotnet-client-quickstart-guide
Posted in Administration | No Comments »
Donnerstag, Dezember 10th, 2020
root@rpi-iot-jsho-docker-01:~# docker pull minio/minio
root@rpi-iot-jsho-docker-01:~# docker run -p 9000:9000 –name MinIO-01 -v /media/usb:/data -e „MINIO_ACCESS_KEY=<AccessKey>“ -e „MINIO_SECRET_KEY=<SecretKey>“ minio/minio server /data
root@rpi-iot-jsho-docker-01:~# docker ps –all
root@rpi-iot-jsho-docker-01:~# docker rm <CONTAINER>
root@rpi-iot-jsho-docker-01:~# docker stop <CONTAINER>
root@rpi-iot-jsho-docker-01:~# docker start <CONTAINER>
MinIO server supports rolling upgrades, i.e. you can update one MinIO instance at a time in a distributed cluster and this allows upgrades with no downtime. Upgrades can be done manually by replacing the binary with the latest release and restarting all servers in a rolling fashion. However we recommend all our users to use mc admin update from the client. This will update all the nodes in the cluster simultaneously and restart them as shown in the following command from the MinIO client (mc)
MinIO Client Complete Guide – https://docs.min.io/docs/minio-client-complete-guide.html
pi@rpi-iot-jsho-docker-01:~ $ wget https://dl.minio.io/client/mc/release/linux-arm/mc
pi@rpi-iot-jsho-docker-01:~ $ ./mc config host add myminio http://192.168.1.151:9000 <AccessKey> <SecretKey>
pi@rpi-iot-jsho-docker-01:~ $ ./mc admin update myminio
Server `myminio` updated successfully from 2020-12-03T05:49:24Z to 2020-12-10T01-54-29Z
pi@rpi-iot-jsho-docker-01:~ $ ./mc mb myminio/photos
pi@rpi-iot-jsho-docker-01:~ $ ./mc cp mc myminio/photos
pi@rpi-iot-jsho-docker-01:~ $ ./mc cp -r dst/* myminio/photos
pi@rpi-iot-jsho-docker-01:~ $ ./mc ls myminio/photos
pi@rpi-iot-jsho-docker-01:~ $ ./mc mirror src myminio/photos
Posted in Administration, Docker, MinIO S3 Storage | No Comments »
