mirror of
https://github.com/rclone/rclone.git
synced 2024-11-26 02:14:42 +01:00
Document rclone's limitations with directories - fixes #69
This commit is contained in:
parent
90744301d3
commit
87ed7fc932
@ -1,13 +1,28 @@
|
||||
---
|
||||
title: "Bugs"
|
||||
description: "Rclone Bugs"
|
||||
description: "Rclone Bugs and Limitations"
|
||||
date: "2014-06-16"
|
||||
---
|
||||
|
||||
Bugs
|
||||
----
|
||||
Bugs and Limitations
|
||||
--------------------
|
||||
|
||||
Empty directories are left behind with Local and Drive
|
||||
### Empty directories are left behind / not created ##
|
||||
|
||||
eg purging a local directory with subdirectories doesn't work
|
||||
With remotes that have a concept of directory, eg Local and Drive,
|
||||
empty directories may be left behind, or not created when one was
|
||||
expected.
|
||||
|
||||
This is because rclone doesn't have a concept of a directory - it only
|
||||
works on objects. Most of the object storage systems can't actually
|
||||
store a directory so there is nowhere for rclone to store anything
|
||||
about directories.
|
||||
|
||||
You can work round this to some extent with the`purge` command which
|
||||
will delete everything under the path, **inluding** empty directories.
|
||||
|
||||
### Directory timestamps aren't preserved ##
|
||||
|
||||
For the same reason as the above, rclone doesn't have a concept of a
|
||||
directory - it only works on objects, therefore it can't preserve the
|
||||
timestamps of directories.
|
||||
|
Loading…
Reference in New Issue
Block a user