Replies: 3 comments
-
|
if you sync directory, you should add a slash after the directory name, such as juicefs sync gs://bucket_name/dir_name/ /jfs/dir_name/, if without slash, it will match all the file and dir names started with dir_name. |
Beta Was this translation helpful? Give feedback.
-
|
This is what meta cache do. |
Beta Was this translation helpful? Give feedback.
-
|
Where do I find more information on meta cache?
…On Wed, Jun 12, 2024 at 12:42 AM Zhou Cheng ***@***.***> wrote:
how about have a bit in the metadata server for the version of of the last
change? If the client detected that it has the latest version of the FS
metadata, it can skip getting all the info per inode? This could
significantly speed up lstat() in the common case when nothing has changed?
This is what meta cache do.
—
Reply to this email directly, view it on GitHub
<#4853 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPGF4LRZVNMSL7AXI6WKCDZG7GSTAVCNFSM6AAAAABHW45OPSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TONBWGQYTG>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
First of all I just started using juicefs in GCP. So far it works great and I really appreciate your work. I feel this piece of software is well architected and well made.
It seems though commands like git status is slow with juicefs due to a lot of lstat() calls to the metadata server. Here is an idea:
Also, on GCP, I noticed juicefs sync is behavior strangely. When I sync a file like:
juicefs sync gs://bucket_name/dir_name /jfs/dir_name
2 strange things feels like bugs:
I don't know where does the suffix "-16" came from really.
Beta Was this translation helpful? Give feedback.
All reactions