On Sat, 6 Jan 2007 [EMAIL PROTECTED] wrote:
> > Only reading, writing of very small files to the ntfs-on-samba share goes
> > flawlessly
>
> ok, that makes things different.
> i would also recommend debugging this at the samba level
> samba logging/debugging can be set to be _very_ verbose
Could be samba but as I understood it worked with other filesystems.
Though it could be also configured differently for ntfs.
However the lack of full file timestamp support do cause such problems
(which will be fixed). But that would happen independently of the file
sizes and shouldn't give the errors it gave.
ActiveSync seems to do some strange things which make no sense on Linux,
for example,
stat64("My Documents/foo/bar/*", 0xbfb18a44) = -1 ENOENT (No such file or
directory)
stat64("", 0xbfb1a9b4) = -1 ENOENT (No such file or
directory)
Are the skipped files in the same directories? That is, directories are
either fully skipped or fully synced?
Szaka
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
