Apple Knowledge Base's picture

Apple Cinema Display: Troubleshooting steps (Apple KB)

Learn about troubleshooting steps you should follow if you experience any issues with your display.

Read more:

Apple Knowledge Base's picture

Final Cut Pro X 10.1: Scroll bars intermittently disappear (Apple KB)

The horizontal and vertical scroll bars might intermittently disappear in the Event Browser and Timeline in Final Cut Pro X 10.1.x. This can occur after you pair a mouse or trackpad with your MacBook Pro (Retina, Late 2013) or Mac Pro (Late 2013).

Read more:

Apple Knowledge Base's picture

Using 4K displays and Ultra HD TVs with Mac computers (Apple KB)

Learn about using 4K displays and Ultra HD TVs with Mac computers.

Read more:

Apple Knowledge Base's picture

Mac Pro (Late 2013): "Boot Configuration" alert when installing Windows 8 (Apple KB)

A "Boot Configuration" alert might appear when installing Windows 8 on a Mac Pro (Late 2013) via Boot Camp Assistant.

Read more:

Andrew Allen's picture

Can a corrupt/buggy Xsan filesystem cause extremely low read/write speeds on a SAN?

For the sake of brevity, I've leave out the 3 months of background information trying to resolve the problems we've had.

We have a SAN that used to have 450-550 MG/s read/write speeds. It preformed this way for 4.5 years. Now it's writing and reading at much lower speeds, like 40-150 MG/s write speeds and 250-300 read speeds. YES, we've investigated all the likely things: SFPs, fibre cables, thoroughly investigated the fibre switch, checked the RAID controller, etc.

My question is simply this: Does anyone know if it's possible for a degraded/corrupted/buggy Xsan filesystem to cause such heavily reduced speeds? To our knowledge, we have never run a cvfsck on this Xsan volume and it's been in heavy use for almost 5 years. I'm going to do run this tomorrow. Could the Xsan filesystem be the cause of our degraded drive speeds?

Apple Knowledge Base's picture

Intel-based Mac: Startup sequence and error codes, symbols (Apple KB)

The following is an overview of the startup sequence, error conditions, and behaviors for all Intel-based Macintosh systems.
Note that some newer Macintosh models only use tones to indicate error conditions. See this article for more information.

Read more:

aaulich's picture

Archiware P5 Archive v5.1.2 adds incremental archives to CP Archive App

Archiware has just released the 5.1.2 version of P5, their data management suite, which the CP Archive App uses to add archiving features to Cantemo Portal.

Version 5.1.2 introduces a feature I've been asked for many times in the past, and finally it's there: incremental archives.
Though P5 has already supported incremental archives in earlier versions, version 5.1.2 adds this feature to the command-line API, which the CP Archive App uses. P5 now checks for every file the CP Archive App sends to P5 on the command-line, if it has already been archived and hasn't changed since then.

If a file is new or has been modified since its original archiving, P5 will archive it again, otherwise, it will not store it on tape again.
This is a huge benefit for media archives, as most restores of media files happen to read these files only without modifying them.
The CP Archive App as well as other solutions usually trigger archiving of items automatically x days after creation, so without incremental archiving your archive can grow much faster than you expect.

If you prefer to archive complete projects without linking to older, existing tapes, you can still do this. Incremental archiving can be turned on in the UI while setting up an archive plan:

As you can see in the screenshot, activating incremental archiving is a single switch in the settings of an archive plan.

I think this alone is a very good reason to upgrade (or switch) to Archiware P5 Archive.

growl88's picture

Xsan 2 on a Xserve2,1 (10.6.8) and Marvericks

Hi everibody,

I've a question about the old osx server and his client. Can I have different OSX version client using Xsan 2 on my 10.6.8 Xserve2,1 server?

Because i want to buy a new mac, and maybe upgrade another one, but I don't know if can coexist different OS-Client in the same Xsan network

Thamk you so much!


Andrew Allen's picture

Xsan Failback


We have an Xsan 2.1 environment with 3 SANs, 3 MDCs and 11 clients. Occasionally we've had the odd failover occur over the years. We're currently in a state where the 3 MDCs and 2 of the clients are running Mavericks and Xsan 3.1. We're eventually aiming to move all cilents to Mavericks and Xsan 3.1 but in the mean time the older snow leopard machines are running Xsan 2.2.2 (build 148)

Every once in a while a SAN will failover to it's secondary metadata controller. However, recently we had our second SAN failover and then fail BACK to the original controller. I read in the physical copy of the Xsan 2 Administration guide (2009) I have that this is called failback and that a failback should never occur automatically: it must be manually instigated by person. However, we had a failback occur without a person insitigating it.

Has anyone experienced this? Is it a concern? I'm heading to the site to investigate the console logs and I'll post them below shortly.


Gerard's picture

Xsan Permission Propagation


Within my environmentw we have:

A 70Tbs Xsan volume running v3.0, two 10.8.5 MDCs on Xserves, combination of Promise E&J raids, four Qlogic 5600 switches and another Xserve used as a fileserver sharing out folders from the Xsna volume.

I have noticed when I propogate ACL permissions with full read/write, from the root folders, down our folder strucutre, the permissions don't trickle down all the way.

Ex: I have a folder structure with ten folders and within the last folder, there are files. Via Xsan Admin, the files lack ACL rights because the last (tenth) folder doesn't have proper rights. Though, the above folders (1-9) do have the ACL rights. 

Is there any type of bug within Xsan where permissions stop tricking down at a certain point?



Subscribe to Xsanity RSS