szumlins's picture

10.3.9 Clients/10.4.2 MDCs

Has anyone gotten this situation to work? For some reason when I have the clients on 10.3.9, they refuse to save the serial numbers. I'm also seeing that the 10.3.9 machines won't let me add Organization and Registered To fields when trying to save the serials.

I took my pocket diagnostic firewire drive with 10.4.2 installed on it, booted off one of the client machines and was able to install and make it a client with no it is most definitely a 10.3.9 issue.

Given the layout of this particular group, I'm not comfortable moving them to 10.4.2 unless it is my one and only last option to get the Xsan alive. I'd really like to figure out how to get it working as advertised (Xsan 1.1, 10.3.9,10.4.1,10.4.2)

Any ideas would be much appreciated.

dgf's picture

Xsan and FC-DAS on same host

Good Day,

Has anyone attempted to attach an XserveRAID (HFS+) to an Xsan client (via a second HBA)? I just tried today on a dual 1GHz G4 with 1.25 GB RAM, and while the host can browse the SAN filesystem, it cannot read known good files on the SAN. When writing a text file to the SAN, the result is jibberish. This is the case for Finder drag and drop, and cvcp.

Remove the FC-DAS from the second HBA and all is well.

OS X 10.4.2
Xsan 1.1


BlanchHudson's picture

Still curious about 2 vs 3 servers as an xsan config

I am still having a hard time wrapping my head around the bandwidth requirements for metadata; there is a lot to consider. This is a nine seat SAN consisting of 2 servers, 6 clients, 1 Digital Rapids Z-Stream PC server using ADIC that pushes material to a VOD server with 10 set top boxes. The SAN is being used to edit finished program to clock (it couldn’t be easier editing). The LAN is completely separate from the rest of the house intranet. The DNS will run from the OD. FTP will happen at the flip server and no other sharing will occur. They will have a direct connect to the web through a firewall. So from your response I gather that having MDC and OD on the same server is fine in this type of application. Is that right, or does Apple require three reqardless of the application?

Because the flip server will mount the Xsan volumes do the FTP services need to be turned on at the OD?

If you would still require an extra server than would this scenario be all right: One MDC, one MDC replica/OD master, and one OD replica using a single processor Xserve that doesn’t connect to the Xsan. I am temped to turn on sharing for what I don’t know but coolness. I would guess because of your response the sharing would go away in case of an OD failure in this scenario?


ScottyD's picture

Xsan crashes every night at relatively the same time...

Xsan 1.1, 10.4 server

One of our clients is having a crashing problem with their Xsan. Approximately every night the MDC will beach ball and freeze up. Anyone else seeing this? My best guess is that this might be related to the daily periodic script that runs at approximately 3 or 4 in the morning. Anyone know how to turn this cron script off on Tiger? I know it's run from a different place than Panther.

Any ideas as to what might be causing this?

Scotty D

BlanchHudson's picture

Is three servers really better than two?

I am installing a XSAN for a client in roughly two months.
2 servers
5 FCPs
1 graphic/fcp
1 PC/Adic bit flipper

It is all very exciting and I will be more forthcoming as I get closer to the installation.

I have failover concerns with the two servers. Server1 will handle the metadata, and Server2 will provide open directory. If either fails the other will be on double duty-- the failed server would be back on line at a maximum of 2 days. What are the drawbacks to this configuration?

Each of the servers is a dual 2.3 with 4 gigs of ram.

In reading I've seen the sort of optimal setup to be 3 servers. I would really like to stick with two, but if I there are strong reasons I would fight to insert a hopefully cheaper single processor system as the open directory failover.

...Or would it be necessary to spec another monster and make it the failover for both the Open Directory and the metadata?

Looking to get is right the first time,

ScottyD's picture

Major problems adding a new storage pool in Xsan.

We have talked to Apple already about this issue over a 3 hour tech support call. Here is the situation:

We have two existing volumes. Both are running fine. I want to add another storage pool with two luns to the 2nd volume. I unmount each client and shut them down. Then I turn off both volumes. I connect a new xserve raid with two RAID5 luns (pre configured) and then label the luns in Xsan Admin. Then I proceed to add a new storage pool to the desired volume. The MDCs lights light up and do their thing, as well as the Xserve RAID containing my metadata. Then I check the volume and the size is correct. Then I proceed to start the volume and it won't start up. I had had this problem before and reverted to my earlier config as per Apple's instructions in Xsan help: Tips to avoid unexpected volume behaviour. After doing this I couldn't even start the volume. Then I ran cvfsck with the -j flag. I got this error:

  • Warning*: Icb has a configuration mismatch!

Icb mismatches configuration:
File System Stripegroup Count Mismatch. exp-2 rcv-3

    • Cannot re-create Icb with uncertain configuration parameters. **
    • You must use cvfsck interactively to correct this problem. **

Then I ran cvfsck again without the -j flag. Same error. I don't want to try the newer config because I don't want to risk screwing up my data. I've done everything properly and now Apple is saying this is a possible bug with Xsan. This is a little disconcerting being that I recently lost 2.5 TB of data due to my own mistakes and now I might lose more due to a problem with the software. Apple says they'll get back to us tomorrow with a possible workaround. Let's hope so.

If anyone has any thoughts to add please do so.

Scott Dominick

ScottyD's picture

IPs not showing up as private IPs but pub IPs in Xsan Admin

Normally we have been keeping our main MDC off our public internet. However, due to a rather large migration I have had to turn on the public internet to access the MDC from Apple Remote Desktop. When I enabled the public internet all of my clients started showing up as their public IPs instead of the expected private IPs. Then when I shut off the internet on the MDC, now all of these IPs are red. Also I can't get access to my mounted clients to unmount them. I understand that Xsan Admin uses Rondevous (Bonjour) to find clients, however, I don't want the MDC to find public IPs. Would it be wise to disable mDNSResponder? Also what is the best way to get my private IPs back? Should I deinstall all of the Xsan clients and reinstall?

Any suggestions are appreciated?

Scott Dominick

riegersteve's picture

xsan mounted on unix servers

is there any way that i can mount my xsan shares unto a unix (freebsd 5.4) server via fibre card instead of using nfs

clickspace's picture

Xsan for sharing images between application and web servers?


I will be putting together an environment with multiple web servers and multiple WebObjects application servers. All Xserves. Our application allows us to upload images and have them available to the web server for displaying to the web server. These are typical web files anywhere between 500 bytes to 1 MB in size. There will be LOTS of them. Millions actually. I was hoping that I could use Xsan so my application servers can write the files and the web servers can read the files all from the same location. This would be an Xserve RAID.

I've seen a lot of talk on using Xsan with video footage (very large files --> few requests) and no talk about using Xsan with many small files and many many requests.

Is Xsan an appropriate solution to this problem? Or should I be looking at a different solution? If so, what would that be? I want a fully redundant environment so if something goes down, our web site is still up and running just as before. I also want the ability to upgrade the OS on various machines over time without having to take down the site.



BlanchHudson's picture

OS 10.4 with a UPS system


Best I can tell no UPS systems manufacture supports automatic shut during power failure at this point.

APC has software for 10.3 and are developing for 10.4 but that is appearently six months out, the end of the year.

TrippLite has never had support for MAC, but are now writing software. They seem as though they are planning to release at the end of the year.

Emerson no MAC support.

Powerware no MAC support.

Falcon no Mac support.

If anyone knows of anyone please, please let me know.



Subscribe to Xsanity RSS