so I started using ffs to sync my files to google drive and I got this message a couple of times already after using total commander sync, and indeed it was right I had to go and delete the dupes on my own
Total Commander
---------------------------
Error, two files with the same name but different case exist on the remote server!
Because Windows doesn't support this on local drives, you need to delete one of the duplicates before proceeding!
extensions\ms-vscode.js-debug\resources\readme\link-debugging.gif
extensions\ms-vscode.js-debug\resources\readme\link-debugging.gif
gdrive: two files with the same name but different case exist on the remote server!
- Posts: 46
- Joined: 16 Feb 2019
- Posts: 4071
- Joined: 11 Jun 2019
What is the point of this post?
Bug report? Not a bug, intended behavior
Feature request? Not a FFS related behavior, NTFS is not case-sensitive
Bug report? Not a bug, intended behavior
Feature request? Not a FFS related behavior, NTFS is not case-sensitive
- Posts: 46
- Joined: 16 Feb 2019
of course it should be a ffs bug,
who else created those duplicate files then?
I think FFS did because these files didn't exist before,
I used ffs for the initial upload,
and this is for both cases
who else created those duplicate files then?
I think FFS did because these files didn't exist before,
I used ffs for the initial upload,
and this is for both cases
- Posts: 4071
- Joined: 11 Jun 2019
Gotcha! Very likely that FFS didn't create them, I would say guaranteed even.
I will say, the two paths/files you posted don't have any differences at all, even in case
I will say, the two paths/files you posted don't have any differences at all, even in case
- Posts: 46
- Joined: 16 Feb 2019
yes, my problem isn't that they're different. my problem is that they are the same!
and so I've got to go find them and delete them manually,
anyway, it doesn't make sense, who created those and why?
and so I've got to go find them and delete them manually,
anyway, it doesn't make sense, who created those and why?
- Posts: 1043
- Joined: 8 May 2006
Perhaps TC is displaying the two file/path names as the same (case),
but in fact, on the Google end, they are different?
viewtopic.php?t=6483
If these files were only sent up by FFS, then did case change on your end?
As is was the file (& or path) name originally something like \Readme\ & then you subsequently changed it to \readme\ (on the local end)?
(Sort of scratching my head on that, heh, as I guess FFS is treating things insensitively... where Google is not...)
but in fact, on the Google end, they are different?
viewtopic.php?t=6483
If these files were only sent up by FFS, then did case change on your end?
As is was the file (& or path) name originally something like \Readme\ & then you subsequently changed it to \readme\ (on the local end)?
(Sort of scratching my head on that, heh, as I guess FFS is treating things insensitively... where Google is not...)
- Posts: 46
- Joined: 16 Feb 2019
here are all the duplicates FFS created after uploading around 235gb of data
- Posts: 46
- Joined: 16 Feb 2019
9/11 are images and most of them (if not all) small files,
maybe @zenju would want to take a look at this,
also note that I'm using "mirror" to sync/upload these files,
but of course ffs couldn't delete (the one of?) them because it wouldn't know which one to keep,
but I'm working with gd many years now and duplicates are a common problem with it,
I was using their software before starting using ffs and it used to create the famous "(1)" files on my disk because of course windows wouldn't allow it to create two files with the same name (and path) as is the case with gd
maybe @zenju would want to take a look at this,
also note that I'm using "mirror" to sync/upload these files,
but of course ffs couldn't delete (the one of?) them because it wouldn't know which one to keep,
but I'm working with gd many years now and duplicates are a common problem with it,
I was using their software before starting using ffs and it used to create the famous "(1)" files on my disk because of course windows wouldn't allow it to create two files with the same name (and path) as is the case with gd