[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
copying directories to remote location = data loss
From: |
Marco Cawthorne |
Subject: |
copying directories to remote location = data loss |
Date: |
Fri, 23 Sep 2022 11:59:41 -0700 |
I've been investigating this and I can reproduce it every time.
It started out with me doing it in GWorkspace. I filed a bug here:
https://github.com/gnustep/apps-gworkspace/issues/18
I can also reproduce it in StepSync, which hints at NSFileManager
and not specifically GWorkspace. I am still investigating more as I am
testing more.
However this is critical enough to disclose immediately.
To reiterate the steps for reproduction (in this example, GWorkspace):
- Create a directory with some dummy files in it on a local hard disk
drive.
- Cut or copy the directory into a remote location, either one mounted
via NFS or SSHFS.
- You will discover that only the directory has been moved, and none
of the files within, as well as sub-directories, exist.
- If you cut the directory from the local location, you will
experience data loss.
It does not seem to matter if I run -git or a release version of any
of the components.
I'm running Slackware 15. I do not use the packages provided by
SlackBuilds.org either.
So none of the software has been patched or tampered with by a package
maintainer.
As mentioned in the GWorkspace GitHub filing, the standard output of
GWorkspace
does not log anything of use.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- copying directories to remote location = data loss,
Marco Cawthorne <=