<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>S3 on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/s3/</link><description>Recent content in S3 on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Sat, 07 Feb 2026 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/s3/atom.xml" rel="self" type="application/rss+xml"/><item><title>MinIO Multi-Node, Multi-Disk Deployment and Operations</title><link>https://www.chenshaowen.com/en/blog/minio-multi-node-multi-disk-deployment-and-maintenance.html</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><atom:modified>Sat, 07 Feb 2026 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/minio-multi-node-multi-disk-deployment-and-maintenance.html</guid><description>1. Environment Preparation 1.1 Preparing Data Disks Inspect the data disks 1 lsblk -d -o NAME,SIZE,TYPE | grep nvme 1 2 3 4 nvme0n1 745.2G disk nvme1n1 745.2G disk nvme2n1 745.2G disk nvme3n1 745.2G disk Prepare the storage directories 1 2 3 for i in {0..3}; do mkdir -p /mnt/data${i} done Format the data disks 1 2 3 for i in {0.</description><dc:creator>微信公众号</dc:creator><category>MinIO</category><category>Storage</category><category>Distributed Systems</category><category>Operations</category><category>Learning</category><category>Object Storage</category><category>S3</category><category>Deployment</category><category>High Availability</category></item><item><title>Using Fluid and S3FS to Access S3 Storage and Performance Testing</title><link>https://www.chenshaowen.com/en/blog/using-fluid-and-s3fs-to-access-s3-storage-and-performance-testing.html</link><pubDate>Thu, 05 Dec 2024 00:00:00 +0000</pubDate><atom:modified>Thu, 05 Dec 2024 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/using-fluid-and-s3fs-to-access-s3-storage-and-performance-testing.html</guid><description>This post uses Fluid 1.0. In later versions the configuration file paths changed, so adjust according to your actual situation.
1. Building the Image 1.1 fluid_config_init.py 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 #!</description><dc:creator>微信公众号</dc:creator><category>s3</category><category>Fluid</category><category>JuiceFS</category><category>AI</category><category>Data</category></item><item><title>Build Artifacts and Cache in Jenkins</title><link>https://www.chenshaowen.com/en/blog/artifacts-and-cache-in-jenkins.html</link><pubDate>Sun, 21 Jun 2020 00:00:00 +0000</pubDate><atom:modified>Sun, 21 Jun 2020 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/artifacts-and-cache-in-jenkins.html</guid><description>In a CICD flow, there are two main kinds of things that need to be saved: build artifacts and caches. Build artifacts are the final execution result, and caches exist to speed up the next build. This post mainly describes how to archive build artifacts and caches in Jenkins, along with a hands-on example backed by object storage.</description><dc:creator>微信公众号</dc:creator><category>Jenkins</category><category>S3</category><category>DevOps</category><category>Cache</category></item></channel></rss>