ADSM-L

FLASH: TSM Mac client and MacOS X 10.3 new case sensitive HFS+ file system

2003-10-24 15:58:37
Subject: FLASH: TSM Mac client and MacOS X 10.3 new case sensitive HFS+ file system
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 24 Oct 2003 13:56:47 -0600
I have been asked to post the following item:

============================================================
Customers using Apple MacOS X 10.3 (Panther)'s new optional Case Sensitive
HFS+ file system with the IBM TSM Mac client should read this flash


Apple MacOS X 10.3 (Panther) customers using the new optional Case
Sensitive HFS+ filesystem with the IBM TSM Mac client need to apply
interim fix 5.2.0.3, and ensure the new CS HFS+ volume does not have the
same name as existing TSM volumes on the node.


Immediate Action needed:

If planning to use the new MacOS X 10.3 optional Case Sensitive HFS+
filesystem, before backing up any files in that filesystem:

- Apply interim fix 5.2.0.3 (or later deliverables such as the 5.2.2
maintenance when available)

- Ensure the new Case Sensitive HFS+ volume does not have the same name as
existing TSM volumes for the node. Either the TSM volumes can be renamed
on the TSM server, or the CS HFS+ volume can be renamed locally.
Customers using the default HFS+ or other filesystem with MacOS X 10.3 do
not need to do anything.


Problem Description:

The new optional Case Sensitive HFS+ filesystem in MacOS X 10.3 is case
sensitive, not case-preserving like previous Mac filesystems. The existing
TSM Mac clients do not treat file names in a case sensitive manner on
backup or restore.

With the new filesystem, if two files have the same path and the same
name, but different casing on the name, the existing TSM Mac clients will
not be able to distinguish between the two files on backup and restore.
Both files will be backed up on the very first incremental backup, but
both will be treated as the same file, so the backup of the first file
will become the inactive version, and the second file will become the
active backup version.

On the next incremental, the file that is the inactive version won't be
found and will be backed up, becoming the new active version, and the
second file's backup will become the inactive version.

This problem only occurs with the new Case Sensitive HFS+ filesystem and
MacOS X 10.3.

This problem is described in APAR IC37907, and is fixed in TSM Mac client
interim fix 5.2.0.3 and subsequent V5.2 deliverables. The interim fix
client will recognize the Case Sensitive HFS+ filesystem type, and will
treat its files in a case sensitive manner on backup and restore. The
volume name for the new Case Sensitive HFS+ filesystem must be a unique
TSM volume name for that node, to ensure correct backup and restore
operations.


Recommended Action:

Before backing up any files in a Case Sensitive HFS+ filesystem:

1. Install the TSM Mac client interim fix 5.2.0.3 or a later V5.2
deliverable.

2. If the Case Sensitive HFS+ filesystem volume is the same name as an
existing TSM volume, either rename that existing TSM volume or rename the
new CS HFS+ volume, to prevent case sensitive files from being mixed with
case preserving files.
============================================================

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

<Prev in Thread] Current Thread [Next in Thread>
  • FLASH: TSM Mac client and MacOS X 10.3 new case sensitive HFS+ file system, Andrew Raibeck <=