github.com/rclone/rclone@v1.66.1-0.20240517100346-7b89735ae726/docs/content/bugs.md (about)

     1  ---
     2  title: "Bugs"
     3  description: "Rclone Bugs and Limitations"
     4  ---
     5  
     6  # Bugs and Limitations
     7  
     8  ## Limitations
     9  
    10  ### Directory timestamps aren't preserved on some backends
    11  
    12  As of `v1.66`, rclone supports syncing directory modtimes, if the backend
    13  supports it. Some backends do not support it -- see
    14  [overview](https://rclone.org/overview/) for a complete list. Additionally, note
    15  that empty directories are not synced by default (this can be enabled with
    16  `--create-empty-src-dirs`.)
    17  
    18  ### Rclone struggles with millions of files in a directory/bucket
    19  
    20  Currently rclone loads each directory/bucket entirely into memory before
    21  using it.  Since each rclone object takes 0.5k-1k of memory this can take
    22  a very long time and use a large amount of memory.
    23  
    24  Millions of files in a directory tends to occur on bucket-based remotes
    25  (e.g. S3 buckets) since those remotes do not segregate subdirectories within
    26  the bucket.
    27  
    28  ### Bucket-based remotes and folders
    29  
    30  Bucket-based remotes (e.g. S3/GCS/Swift/B2) do not have a concept of
    31  directories.  Rclone therefore cannot create directories in them which
    32  means that empty directories on a bucket-based remote will tend to
    33  disappear.
    34  
    35  Some software creates empty keys ending in `/` as directory markers.
    36  Rclone doesn't do this as it potentially creates more objects and
    37  costs more.  This ability may be added in the future (probably via a
    38  flag/option).
    39  
    40  ## Bugs
    41  
    42  Bugs are stored in rclone's GitHub project:
    43  
    44  * [Reported bugs](https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug)
    45  * [Known issues](https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Known+Problem%22)
    46