Re: [DISCUSS] Replace goofys

2025-07-14 Thread Wei-Chiu Chuang
Looks like mountpoint-s3 is the way to go. If we adopt mountpoint-s3, we can also leverage AWS's CSI driver https://github.com/awslabs/mountpoint-s3-csi-driver?tab=readme-ov-file Would be interesting to see how well it works for Ozone to be mounted as a kubernetes storage. On Fri, Jul 11, 2025 at

Re: [DISCUSS] Replace goofys

2025-07-11 Thread Siyao Meng
+1 mountpoint-s3 sounds promising. s3fs-fuse has lower performance than Goofys but might have the lowest friction as a replacement. -Siyao On Mon, Jul 7, 2025 at 11:02 AM Abhishek Pal wrote: > +1 on looking for a replacement since goofys is not being maintained. > JuiceFS seems to introduce t

Re: [DISCUSS] Replace goofys

2025-07-07 Thread Abhishek Pal
+1 on looking for a replacement since goofys is not being maintained. JuiceFS seems to introduce the problem of having to maintain an extra component for metadata which might come back to bite us, unless we let users setup and manage it by themselves. Maybe understanding what POSIX operations we a

Re: [DISCUSS] Replace goofys

2025-07-07 Thread Ethan Rose
+1 for finding a goofys replacement. All of s3fs-fuse, mountpoint-s3, and juicefs are probably worth testing since they seem to have different use cases. mountpoint-s3 and s3fs are most similar to goofys in that the namespace exposed matches what is stored in Ozone but some posix operations are not

Re: [DISCUSS] Replace goofys

2025-07-07 Thread Sammi Chen
+1, goofys is not stable after hours of running, especially in the continuous file write case. We'd better benchmarking these new candidates. BTW, I have heard of one JuiceFS + Ozone case, which seems running well. Sammi On Sun, 6 Jul 2025 at 15:29, Tsz-Wo Nicholas Sze wrote: > +1 If goofys i

Re: [DISCUSS] Replace goofys

2025-07-06 Thread Tsz-Wo Nicholas Sze
+1 If goofys is unmaintained, we should find a replacement. Tsz-Wo On Tue, Jul 1, 2025 at 11:46 AM Wei-Chiu Chuang wrote: >1. HDDS-13356 > > Goofys is a s3 fuse client. We rely on goofys to mount s3 locally and our > ozone csi driver depen