Help me understand Apple's reply to my bug report
Help me understand Apple's reply to my bug report
- Subject: Help me understand Apple's reply to my bug report
- From: Thomas Tempelmann <email@hidden>
- Date: Mon, 4 May 2009 10:18:39 +0200
Hi,
I have recently reported a bug where the Finder would behave oddly
when showing file sizes of remote files.
What follows is Apple's response, with my orginal report attached.
What do you make of the reponse? I suspect that the Apple engineer
didn't understand my report at all and assumed I was complaining that
a file changing on the server side would not get updated on the client
right away, or why would he talk of "sync" otherwise?
-----------------------
Hi Thomas,
This is a follow-up to Bug ID# 6735259.
Engineering has determined that this issue behaves as intended based
on the following information:
There is no notification from afp to do this. So the best we can do
is sync the item as it gets selected to be as up to date as possible
without constantly polling.
We consider this issue closed. If you have any questions or concern
regarding this issue, please update your report directly
(http://bugreport.apple.com).
Thank you for taking the time to notify us of this issue.
Best Regards,
KIT CHEUNG
Apple Developer Connection
Worldwide Developer Relations
**************************************************************************
THE INFORMATION CONTAINED IN THIS MESSAGE IS UNDER NON-DISCLOSURE
**************************************************************************
-------------------------------------------------------
Bug ID #: 6735259
Bug Title: Finder displays invariable file sizes of remote volumes
with variable values
-------------------------------------------------------
<GMT29-Mar-2009 08:46:33GMT>
Summary:
When using the Finder to look at the "on disk" size of files from a
mounted AFP volume, they often change when the user selects the items.
This is irritating and should be looked into.
Steps to Reproduce:
1. Mount a network volume of a HFS+ volume served over AFP (e.g. from
another 10.5.6 system).
2. Change the window view to "as List".
3. Find files on the volume that are below 1000KB in size.
4. Click on (select) such files and watch the displayed file size
before and after the click
Here is a video showing what's happening:
http://homepage.mac.com/tempelorg/finder-size-changing-bug.mov
Expected Results:
The displayed file size should be constant
Actual Results:
The file size often gets reduced by a multiple of 4K, then switches
back to the higher value once a different application gets frontmost.
Regression:
All I know is that this happens for other people, too. See this
discussion thread:
http://lists.apple.com/archives/Macos-x-server/2009/Mar/msg00640.html
I did some searching and found that this may indeed be related to
assuming resource forks: If the file has a rsrc fork, the displayed
size remains constant. Also, I check if it is related to other
metadata, but found that even a freshly created file (using the
"touch" cmd) with no extended data such as FinderInfo will show this
misbehavior.
On a side note, the Finder also shows that a 0-length file occupies
4KB (or a multiple thereof) on disk, even though this is not correct:
A 0-length file does not occupy any allocation blocks (apart from
what's used in the directory file for it). It would be nice if the
Finder would tell the user that an empty file is actually empty by
showing "0" in the size column in list view.
--
Thomas Tempelmann, http://www.tempel.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden