Symptom
When copying a file whose filename ends in a hexadecimal number with a leading pound sign (see "affected file names" below), either the client experiences a kernel panic or data loss occurs on the server. At the client, this occurs immediately after starting the copy, such as when you drag the file icon onto the server icon.
Data loss occurs at the server when you click Replace in response to an alert box that says the filename already exists. You may at this point see an "error" alert message. Files and folders on the server are then deleted.
Note: When a kernel panic occurs, you may see text stating that "You need to restart your computer," or it may take other forms. For help identifying a kernel panic, see technical document 106227, "
Mac OS X: What is a Kernel Panic?"
"Server" in this context refers to any computer offering an affected service, whether or not its operating system is sold and marketed as a "server". Mac OS 8.6, for example, is a server when file sharing is turned on.
Affected file names
You will
always see this issue with files whose filenames end specifically
in
#02, such as:
You
may or may not see the issue with any filename ending in a pound-led hexadecimal number (file_name#<hex_number>). Examples look like:
example_name#10ade
example_name#123
example_name#dead
Note: Hexadecimal (base-16) numbers are any created from a set of these characters:
This means that, by appearance alone, a hexadecimal number is not always distinguishable from a regular decimal (base-10) number, as in "example_name#123".
Services affected
This affects all versions of Apple file service, whether served by Mac OS or another operating system. This includes but is not limited to services known by these names:
- AppleShare, AppleShare IP
- File Sharing, Personal File Sharing
- Apple File Service
- Apple Filing Protocol (AFP)
- Windows 2000 Services for Macintosh
- Novell Native File Access for Macintosh
Solution
This issue is best prevented by updating to Mac OS X 10.2.2 or later, in which it is resolved. If you cannot update immediately, you should review this information:
Do not use filenames that end in
#<hex number>, where "<hex number>" may be any hexadecimal number as described in the "Affected file names" section above. The safest course of action is not to use any pound signs in file names at all.
If a dialog asks if you want to replace another file appears when copying such a file, click Stop. Rename the file so that it does not end in #<hex number>. Then you may safely copy the file.
This document will be updated when more information is available.
Information about products not manufactured by Apple is provided for information purposes only, and does not constitute Apple's recommendation or endorsement. Please contact the vendor for additional information.
Document 17159, "
Locating Vendor Information" can help you search for a particular vendor's address and phone number.