Apple Knowledge Base's picture

Xsan: compatibele grootten van LUN-sector (Apple KB)

Xsan ondersteunt een LUN-sector met een grootte van 512 bytes per sector.

Read more:

Xsan: Unable to enable case insensitivity on a volume (Apple KB)

Xsan 2.3 introduces the ability to create case insensitive volumes. You can also change case sensitivity after you create a volume.

Read more:

Xsan 2.3 or later: Deactivating a storage pool (Apple KB)

It may be necessary to deactivate (down) an Xsan data storage pool in a volume, but retain access to data on other storage pools within the volume. You may need to do this if there is a LUN issue in an Xsan storage pool and Xsan clients are unable to mount the Xsan volume, for example.

Read more:

Apple Knowledge Base's picture

About EFI firmware updates (Apple KB)

Learn how to identify if your Intel-based Macintosh computer needs an EFI firmware update and how to apply EFI firmware updates to Intel-based Macintosh computers.

Read more:

Xsan: How to set Spotlight search levels (Apple KB)

You can change how Spotlight searches work with your Xsan.

Read more:

abstractrude's picture

OS X 10.10 Yosemite and Xsan

OS X Server and Xsan live on!

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?

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.



Subscribe to Xsanity RSS