Why do some of my folders within an ExtremeZ-IP volume and/or the volumes themselves appear locked from OS 10.4.6 (and higher) clients?

1 Star2 Stars3 Stars4 Stars5 Stars
Loading...
  • Product:
    ExtremeZ-IP
  • Version:
    All
  • Document Type:
    FAQ
  • Revised:
    4/26/2010
  • Reviewed:
    4/26/2006

Question:

Why do some of my folders within an ExtremeZ-IP volume and/or the volumes themselves appear locked from OS 10.4.6 (and higher) clients?

Answer:

In OS 10.4.6, Apple added support for viewing and modifying the “locked” status of folders over the network. ExtremeZ-IP has always reported certain folders as locked to Macintosh clients, but until OS 10.4.6, the clients never displayed these folders as locked.

ExtremeZ-IP maps the Windows “read-only” attribute to the Macintosh “locked” attribute for both files and folders. However, the concept of a “read-only” folder on Windows is not intuitive – a “read-only” folder can be renamed, and have files added or deleted from it. In fact, the “read-only” attribute implies nothing about the ability of users to modify data in that folder – it’s used by Windows to mark folders that have customized views (e.g. custom icons).

Locked folders can be unlocked by any Macintosh client – doing so will clear the “read-only” attribute of the folder on Windows. There is a chance that the activity of Windows users (customizing the folder view) could reenable the “read-only” attribute, causing the file to appear locked again by Macintosh clients.

Folders and volumes can be unlocked by simplying unchecking the “locked” checkbox within the folder or volume’s Get Info window. Unlocking can also be performed through the “chflags” command-line utility (via the “nouchg” flag). Folders and volumes can also be unlocked on the Windows server itself through the use of the “attrib” command-line utility (using the “-r” command-line switch). Note that the “read-only” checkbox in Windows Explorer does not accurately reflect the read-only status of the folder, so the “attrib” utility should be used if administrators would like to clear the lock from the server.

Note that clearing the lock on the root of an ExtremeZ-IP volume (unlocking the volume itself, rather than a subfolder) may require a restart of the ExtremeZ-IP service. Unlocking a volume from a Macintosh client will take effect immediately, while clearing the “read-only” attribute from Windows requires that the ExtremeZ-IP service be restarted.

Related Article:

Tags: