Pics or id didn't happen. Sorry, but it is really difficult to believe.
I do not use Filezilla, so I'm not sure how it works, but the only scenario, that I can think of, which would explain the described behaviour would hinge on:
- Filezilla queueing a file for transfer, but showing it as present on the remote site (which would be a bug IMO). Therefore it shows you the file as transferred, before it really is.
- Filezilla not refreshing directory content when a new entry is added. Therefore it would not know about new entries until it refreshed the view. This isn't anything bad, as long, as the refreshing of directory listing work, you claim that it does not. Another bug?
If you are sure, that the problem isn't caused by lack of sleep/low caffeine and/or blood sugar level, then it would help if you documented the whole scenario:
- ssh to the server.
- Create an empty directory. Name it something unique, including a timestamp, e.g. /tmp/fz-hostname-YYYYMMDD-hhmm.
cd into that directory.
- Use Filezilla to access the directory.
- Now we are sure, you access the same directory on the same server using both methods.
- From ssh do
touch newfile; sync; ls -al. We will see the new file created, with a timestamp.
- In Filezilla force a directory listing refresh. I don't know how, maybe there's a "refresh" button, maybe (extreme case) you'll need to close the program and re-open on a different machine (only joking, I don't think they are caching remote directory entries locally; or are they?).
- See that you can see the newfile.
- Transfer a
testfile from local station to the remote location. Double check that the transfer completed.
ls -al in ssh session. Verify that you see
If it still doesn't work, open a bug ticket for Filezilla.