[GH-ISSUE #787] S3FS-Issues Cache #451

New issue

Closed

opened 2026-03-04 01:45:41 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:45:41 +03:00

Owner

Originally created by @SakshiGarg123 on GitHub (Jul 4, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/787

I ran the following commands to run the s3fs.

RUN apt-get -y install automake autotools-dev fuse g++ git libcurl4-gnutls-dev libfuse-dev libssl-dev libxml2-dev make pkg-config
RUN git clone https://github.com/s3fs-fuse/s3fs-fuse.git
RUN cd s3fs-fuse && ./autogen.sh && ./configure --prefix=/usr && make && make install.

After mounting though I didn't mention use_cache="" which should be by default false but executing du -h I saw that entire data was occupying space. Why is it so ?

Originally created by @SakshiGarg123 on GitHub (Jul 4, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/787 I ran the following commands to run the s3fs. ``` RUN apt-get -y install automake autotools-dev fuse g++ git libcurl4-gnutls-dev libfuse-dev libssl-dev libxml2-dev make pkg-config RUN git clone https://github.com/s3fs-fuse/s3fs-fuse.git RUN cd s3fs-fuse && ./autogen.sh && ./configure --prefix=/usr && make && make install. ``` After mounting though I didn't mention `use_cache=""` which should be by default false but executing `du -h` I saw that entire data was occupying space. Why is it so ?

kerem closed this issue

2026-03-04 01:45:41 +03:00

kerem commented

2026-03-04 01:45:42 +03:00

Author

Owner

@gaul commented on GitHub (Jun 25, 2019):

s3fs uses the temporary directory to stage uploads. The application writes to s3fs which writes to the temporary directory and on close s3fs uploads to S3.

@gaul commented on GitHub (Jun 25, 2019): s3fs uses the temporary directory to stage uploads. The application writes to s3fs which writes to the temporary directory and on close s3fs uploads to S3.

kerem referenced this issue

2026-03-04 02:00:49 +03:00

[PR #451] [MERGED] Correct path in README #1512