Hi, and kudos on such a great and useful software.
Here is my problem. I have problems syncing my Linux laptop with my NAS
storage, but I will look into that later. Seems it has to do with permissions.
What I do for now is sync it to a USB key (now formated to NTFS), then sync it
to my Windows 7 desktop and then to the network storage. I get to have four
copies of the same, which is ubersafe I figure ;)
Nevertheless, when I try to sync the same files directly from the laptop to
the network drive after the fact (laptop to USB to desktop to NAS), I get 3
seconds difference between all dates of the files.
Might be useful to say at this point that it's a Seagate GoFlex Home drive.
Its format is also NTFS, which I read here was better exactly for dating
issues.
3 seconds difference
- Posts: 3
- Joined: 19 Jun 2007
- Posts: 3
- Joined: 19 Jun 2007
Probably good to mention too that the laptop runs Linux Mint Maya (Ubuntu)
with Cinnamon.
with Cinnamon.
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
> your copies of the same, which is ubersafe
You know you need to keep at least one copy external, in case the house is on
fire ...?
About the 3 sec difference, this looks like a bug somewhere (but not in FFS
;). FAT has probably the worst resolution with 2 seconds, but there's hardly a
modern file system with a resolution > 2 sec for file modification times. So
it's probably the network drive at fault, either its file system or its
protocol.
You know you need to keep at least one copy external, in case the house is on
fire ...?
About the 3 sec difference, this looks like a bug somewhere (but not in FFS
;). FAT has probably the worst resolution with 2 seconds, but there's hardly a
modern file system with a resolution > 2 sec for file modification times. So
it's probably the network drive at fault, either its file system or its
protocol.
- Posts: 3
- Joined: 19 Jun 2007
> You know you need to keep at least one copy external, in case the house is
on fire ...?
How very true. It has crossed my mind indeed.
> So it's probably the network drive at fault, either its file system or its
protocol.
Thank you. As I was finishing to describe my problem, I was beginning to
suspect that the NAS drive could be the problem.
I will investigate that.
on fire ...?
How very true. It has crossed my mind indeed.
> So it's probably the network drive at fault, either its file system or its
protocol.
Thank you. As I was finishing to describe my problem, I was beginning to
suspect that the NAS drive could be the problem.
I will investigate that.