Mirroring a read-only filesystem

Get help for specific problems
Posts: 3
Joined: 3 Oct 2014

macmelon

I'm using FFS 6.10 on Win7 (I'm new, but FFS is a very nice software indeed) and I'm trying to make a mirror of a read-only filesystem. (Ofc the target is not read-only.) It is working with the same settings as the source is not read-only.

I've tried various things, and read the discussions, but could not find the solution. The only difference between the two pair is a file: H:\test_file. FFS find the difference, but somehow can not write the new file to the mirror. (Tested also: can delete a file from the mirror if the mirror contains an additional file.)

Here is the log, H:\ is the read-only source (and it must be read-only), e:\h\ is the target.


|2014.10.03. - szorakozas: Synchronization completed with errors
|
| Items processed: 0
| Items remaining: 1 (584 bytes)
| Total time: 00:00:17
|_______________________________________________________________

[21:02:58] Info: Starting comparison
[21:02:58] Warning: Cannot set directory lock for "H:\".
Cannot write file "H:\sync.ffs_lock".
Error Code 5: A hozzáférés megtagadva.* (CreateFile)
[21:03:15] Info: Synchronizing folder pair:
H:\
e:\h\
[21:03:15] Info: Creating file "e:\h\test_file"
[21:03:15] Error: Cannot copy file
"H:\test_file" to
"e:\h\test_file.ffs_tmp".
Error Code 5: A hozzáférés megtagadva. (CopyFileEx)
[21:03:15] Error: Cannot write file "H:\sync.tmp.ffs_db".
Error Code 5: A hozzáférés megtagadva. (CreateFile)
[21:03:15] Error: Synchronization completed with errors

*A hozzáférés megtagadva. = Access denied in Hungarian :)

Any idea where is the problem (or the solution)? Thank you in advance!
User avatar
Site Admin
Posts: 7281
Joined: 9 Dec 2007

Zenju

First you should set the sync variant to "mirror" not "two way". Then there's the "access denied" which can have a variety of reasons, none of which have to do with FFS. Most likely it can be solved by setting NTFS permission for the target folder properly.
Posts: 3
Joined: 3 Oct 2014

macmelon

Oh! Thank you very much. The problem wasn't the mirroring (Variant was mirror), and the permission was absolutely okay for the target foldert (I double checked before posting here, and now triple checked with icacls), but you still guided me to the right direction:

I write the solution, I was lame, but maybe somebody can use the information:
So, the target was ok, but the test file on source was unreadable for me (was readable for another group, for others no permission). The tricky part was that: compare could find the difference, as the folder was readable, and ffs considered as a new file (it was a new one indeed) but the file wasn't readable.

After granted read permissions for the test file: In the log I can still see the two CreateFile errors (sync.ffs_lock, sync.tmp.ffs_db) but it is pretty normal for a RO fs. And synchronization (mirroring) working as should be

Thank you very much, not only for guide me, but for the clever software called FFS!
User avatar
Site Admin
Posts: 7281
Joined: 9 Dec 2007

Zenju

Oh! Thank you very much. The problem wasn't the mirroring (Variant was mirror), and the permission was absolutely okay for the target foldert (I double checked before posting here, and now triple checked with icacls), but you still guided me to the right direction:

I write the solution, I was lame, but maybe somebody can use the information:
So, the target was ok, but the test file on source was unreadable for me (was readable for another group, for others no permission). The tricky part was that: compare could find the difference, as the folder was readable, and ffs considered as a new file (it was a new one indeed) but the file wasn't readable.

After granted read permissions for the test file: In the log I can still see the two CreateFile errors (sync.ffs_lock, sync.tmp.ffs_db) but it is pretty normal for a RO fs. And synchronization (mirroring) working as should be

Thank you very much, not only for guide me, but for the clever software called FFS!macmelon
I'm glad you found the problem so quickly. I though you'd be using "two-way" because of the "H:\sync.tmp.ffs_db". If you have "mirror" set it means you have enabled "detect moved files", which you can uncheck to get rid of one more error message.
Posts: 3
Joined: 3 Oct 2014

macmelon

Exactly, I have "detect moved files" checked.

That means, without the db file detect move won't work? Is it possible to save it to a different (notRO) location?