On Sun, 7 Jan 2007 [EMAIL PROTECTED] wrote:
> Wow! You are amazing!
Well, actually __you__ are ;) With this issue you have found three problems
in more than three different softwares.
ntfs-3g/etc: the number of on-disk blocks used is not always correctly
counted. This shouldn't have been a problem but it contributed.
samba: its method to decide about the sparseness of files is not reliable
(I'm sure they are aware of this, what they use is well known to be
unreliable).
activesync: it refuse to handle sparse files when it could be done easily.
> Is there anything I should be watching out for? I mean: any new problems
> that could arise following this patch? Not being pessimistic though ;-)
You shouldn't have any new problems. It was just a test patch to make sure
samba won't mark files sparse incorrectly. I must think a bit more on the
right solution (it's only a matter of correct disk space usage accounting,
if the total disk usage is overcommited then other softwares could break).
Thanks for the nice debug session :)
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
