jw's picture

Determining Current RAID

Forums: 

I just walked into a new job that has an Xraid and I am rather unfamiliar with Apple server products in general and would like to verify something with the crowd:

First some background:

In RAID Admin, it shows that there are 14 drives, each 698.63GB. Google shows that these hard drive models are 750GB. Question about this in a sec.

RAID Admin shows that these drives are in two Arrays of seven drives each, both RAID 0.

Finally, the Events tab of RAID Admin shows that a couple of months ago, there was an error:
Disk 9 Reported An Error. COMMAND:0x25 ERROR:0x49 STATUS:0x51 LBA:0x57464218.
A couple of days later, there is an event
Error Status Cleared Using Service ID Button
Currently, no non-green lights are showing on the front of the Xraid.

Questions:
I know my RAID, but not SANs in general (LUNs, etc) nor Xraid or its interfaces. I can see in this interface no indication that the two arrays are mirrored against each other, but I am not familiar enough with the interface to really know for certain. Am I missing either a different tool/interface or missing a basic assumption of Xraid here? Is this really saying that this Xraid is running entirely striped with no redundancy at all?!? Fast it would be, yes, but that sounds a bit crazy and just wanted to verify that I am not missing a key piece of data here.

If there is no mirroring or other redundant use, where is that last 50GB per drive going?

And the big one: Checking around online (including these forums), this drive error indicates that things are not critical but that the drive ought to be replaced reasonably soon. If this were a nice redundant array I could just hot swap out a drive and all would be well. However, if this has no redundancy, removing a drive from a RAID 0 array is a Bad Idea. What would you recommend?

Thanks in advance for any light you can shed on this for an experienced sysadmin but a newbie to this specific technology!

cinedigital's picture

Stornext 3.5 Compatibility with Lion XSan

According to the Apple compatibility matrix a Stornext v4 MDC is required to work with XSan 2.3 Lion clients.

[url]http://support.apple.com/kb/HT1517?viewlocale=en_US&locale=en_US/url

I have just upgraded 2 Macs to Lion 10.7.4, added them to a Stornext 3.5.1 SAN and they work very nicely it seems!

Is there anything I should check as a possible issue with this setup?

wrstuden's picture

WWDC

Anyone going? I'll be at the OS X Server lab Tuesday morning.

Take care,

Bill

morphenine's picture

Determine Xsan Version

Hi folks, rookie question, I know. I can't seem to find out what version of Xsan is installed.

cvversions returns a revision and build that I can't seem to match up to xsan versions.
/Library/Reciepts sometimes has a package with a plist that lists the version, but not all of my clients have that package.
I could try opening software update, but then I'd have to do that for many machines. Not feasable. Also its not 100% reliable on this.

Is there a plist somewhere that lists Xsan v 2.2.1 or 2.2.2? Some other way to get it?

Thanks.

Anubis666's picture

XSAN Metadata Controller Offline Unavailable Problem

Hello all,

I’m hoping someone here can help me with our XSAN problem.

First, our setup. We have 2 MDCs (let’s call them MDC-1 and MDC-2) running OS X 10.6.8 and multiple clients (both Apple xsan and Windows stornext). They all have public Ethernet card and private Ethernet card and fiber connections. We are running XSAN 2.2.2 and have a Windows DNS server for our Active Directory.

It is currently working in so far as the 3 volumes are online and accessible to clients. Currently all are hosted on MDC-1.

Our problem is that XSAN Admin only sees the MDC-2 as ready. MDC-1 shows us as offline or unreachable. We can failover using the cvadmin but not the GUI XSAN Admin. If we fail 1 volume, both MDCs become “offline or unreachable.” If all volumes are failed to MDC-2 then MDC-1 becomes “ready” and MDC-2 shows as “offline or unavailable.”

We are unable to expand any volume, unable to add any new volumes (we recently added another 6 LUNs) because XSAN Admin wants to see both MDCs as online.

Server Admin also stops working for the MDC that is hosting the volumes. You cannot connect locally or from another server.

Pings work both for the public and private networks.

I have tried many things over the last while. We shutdown the entire san and network and cold booted. We checked DNS settings, checking for multiple UUIDs, looking at etc/hosts. I have tried to see if it’s a bonjour problem. We've check the fsnameservers. I have poured over all the forum posts I can find and still have not been able to find an answer.

I have not tried to remove the MDC from the san because the one that’s unavailable is always the active one!

I suspect it may be some kind of bad config, or DNS, but I am not sure. I tried the "DNS worksheet" and everything checked out fine.

Any help or suggestions will be greatly appreciated.

jetsenwang's picture

LUN cache dirty

Xserver mdc1 : Xsan 2.2.1 controller
Xserver mdc2 : Xsan 2.2.1 failover

client:windows server 2003 ,stornext fx。

problem:recently,Client have the problem log ,such as:

(Critical) scan_disk_states: I/O path [ hostid : 4 lun :1 edev :0x0 path (PhysicalDriver20)] restarted afer 500 seconds.

I check the raid ,that‘s well,no disk is down. So I think this problem about LUN cache dirty .

how to do?

eg: the Volumes cvlog:

[0523 18:41:17] 0x113c16000 (Info) Node [51] [172.168.1.20:2883] Client Logout (active 20).
[0523 18:41:25.039556] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:2904.
[0523 18:41:25.043581] 0x7fff70fd4c20 (Debug) Node [53] [172.168.1.20:2905] connected.
[0523 18:41:25.046123] 0x10a8dd000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:41:25.046131] 0x10a8dd000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:41:25] 0x10a8dd000 (Warning) [Node 53] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:41:25] 0x10a8dd000 (Info) Node [53] [172.168.1.20:2905] Client Login (active 21).
[0523 18:41:25.050404] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:41:25.050417] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:41:25.050428] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/14+9 min/14+9 max/14+9.
[0523 18:41:25.050434] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/11+11 min/11+11 max/11+11.
[0523 18:41:25.050441] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/10+11 min/10+11 max/11+12.
[0523 18:41:25.050449] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:2905]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:41:25] 0x113c16000 (Info) Node [53] [172.168.1.20:2905] Client Logout (active 20).
[0523 18:41:25.628114] 0x7fff70fd4c20 (Debug) Node [56] [mdc1.thm.com:51237] connected.
[0523 18:41:25.628655] 0x7fff70fd4c20 (Debug) Active service - NSS ping from mdc1.thm.com:51236.
[0523 18:41:25] 0x113c16000 (Info) Node [56] [mdc1.thm.com:51237] Administrator Logout.
[0523 18:41:26.854197] 0x7fff70fd4c20 (Debug) Node [57] [mdc2.thm.com:52969] connected.
[0523 18:41:26.854730] 0x7fff70fd4c20 (Debug) Active service - NSS ping from mdc2.thm.com:52968.
[0523 18:41:26] 0x113c16000 (Info) Node [57] [mdc2.thm.com:52969] Administrator Logout.
[0523 18:41:33.179989] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:2926.
[0523 18:41:33.184014] 0x7fff70fd4c20 (Debug) Node [58] [172.168.1.20:2927] connected.
[0523 18:41:33.186168] 0x10cdb5000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:41:33.186176] 0x10cdb5000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:41:33] 0x10cdb5000 (Warning) [Node 58] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:41:33] 0x10cdb5000 (Info) Node [58] [172.168.1.20:2927] Client Login (active 21).
[0523 18:41:33.190528] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:41:33.190541] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:41:33.190552] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/18+11 min/18+11 max/18+11.
[0523 18:41:33.190558] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/15+13 min/15+13 max/15+13.
[0523 18:41:33.190565] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/13+15 min/13+14 max/13+16.
[0523 18:41:33.190572] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:2927]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:41:33] 0x113c16000 (Info) Node [58] [172.168.1.20:2927] Client Logout (active 20).
[0523 18:41:41.211027] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:2948.
[0523 18:41:41.214958] 0x7fff70fd4c20 (Debug) Node [60] [172.168.1.20:2949] connected.
[0523 18:41:41.217128] 0x10b39c000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:41:41.217136] 0x10b39c000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:41:41] 0x10b39c000 (Warning) [Node 60] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:41:41] 0x10b39c000 (Info) Node [60] [172.168.1.20:2949] Client Login (active 21).
[0523 18:41:41.221427] 0x113e22000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:41:41.221440] 0x113e22000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:41:41.221450] 0x113e22000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/18+11 min/18+11 max/18+11.
[0523 18:41:41.221456] 0x113e22000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/16+12 min/16+12 max/16+12.
[0523 18:41:41.221463] 0x113e22000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/14+14 min/14+13 max/14+15.
[0523 18:41:41.221471] 0x113e22000 (Debug) NETWORK SUMMARY [172.168.1.20:2949]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:41:41] 0x113e22000 (Info) Node [60] [172.168.1.20:2949] Client Logout (active 20).
[0523 18:41:49.241603] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:2970.
[0523 18:41:49.245976] 0x7fff70fd4c20 (Debug) Node [61] [172.168.1.20:2971] connected.
[0523 18:41:49.248145] 0x10b296000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:41:49.248153] 0x10b296000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:41:49] 0x10b296000 (Warning) [Node 61] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:41:49] 0x10b296000 (Info) Node [61] [172.168.1.20:2971] Client Login (active 21).
[0523 18:41:49.252368] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:41:49.252380] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:41:49.252390] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/18+11 min/18+11 max/18+11.
[0523 18:41:49.252396] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/16+12 min/16+12 max/16+12.
[0523 18:41:49.252403] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/14+14 min/14+14 max/14+15.
[0523 18:41:49.252411] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:2971]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:41:49] 0x113c16000 (Info) Node [61] [172.168.1.20:2971] Client Logout (active 20).
[0523 18:41:57.272456] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:2992.
[0523 18:41:57.276790] 0x7fff70fd4c20 (Debug) Node [62] [172.168.1.20:2993] connected.
[0523 18:41:57.279406] 0x10b525000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:41:57.279413] 0x10b525000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:41:57] 0x10b525000 (Warning) [Node 62] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:41:57] 0x10b525000 (Info) Node [62] [172.168.1.20:2993] Client Login (active 21).
[0523 18:41:57.283874] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:41:57.283886] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:41:57.283897] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/18+12 min/18+12 max/18+12.
[0523 18:41:57.283902] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/18+13 min/18+13 max/18+13.
[0523 18:41:57.283910] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/15+15 min/15+15 max/15+16.
[0523 18:41:57.283917] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:2993]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:41:57] 0x113c16000 (Info) Node [62] [172.168.1.20:2993] Client Logout (active 20).
[0523 18:42:05.319198] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:3016.
[0523 18:42:05.323310] 0x7fff70fd4c20 (Debug) Node [64] [172.168.1.20:3017] connected.
[0523 18:42:05.325490] 0x10cba9000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:42:05.325497] 0x10cba9000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:42:05] 0x10cba9000 (Warning) [Node 64] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:42:05] 0x10cba9000 (Info) Node [64] [172.168.1.20:3017] Client Login (active 21).
[0523 18:42:05.329826] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:42:05.329838] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:42:05.329849] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/17+13 min/17+13 max/17+13.
[0523 18:42:05.329855] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/15+13 min/15+13 max/15+13.
[0523 18:42:05.329862] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/14+16 min/13+15 max/15+17.
[0523 18:42:05.329869] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:3017]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:42:05] 0x113c16000 (Info) Node [64] [172.168.1.20:3017] Client Logout (active 20).
[0523 18:42:13.350337] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:3038.
[0523 18:42:13.354412] 0x7fff70fd4c20 (Debug) Node [65] [172.168.1.20:3039] connected.
[0523 18:42:13.356947] 0x10d97a000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:42:13.356955] 0x10d97a000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:42:13] 0x10d97a000 (Warning) [Node 65] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:42:13] 0x10d97a000 (Info) Node [65] [172.168.1.20:3039] Client Login (active 21).
[0523 18:42:13.361362] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:42:13.361374] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:42:13.361384] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/17+13 min/17+13 max/17+13.
[0523 18:42:13.361390] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/15+13 min/15+13 max/15+13.
[0523 18:42:13.361397] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/13+15 min/13+15 max/13+15.
[0523 18:42:13.361405] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:3039]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:42:13] 0x113c16000 (Info) Node [65] [172.168.1.20:3039] Client Logout (active 20).
[0523 18:42:21.410580] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:3060.
[0523 18:42:21.415835] 0x7fff70fd4c20 (Debug) Node [67] [172.168.1.20:3061] connected.
[0523 18:42:21.418053] 0x10e4bc000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:42:21.418061] 0x10e4bc000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:42:21] 0x10e4bc000 (Warning) [Node 67] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:42:21] 0x10e4bc000 (Info) Node [67] [172.168.1.20:3061] Client Login (active 21).
[0523 18:42:21.422194] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:42:21.422206] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:42:21.422217] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/13+9 min/13+9 max/13+9.
[0523 18:42:21.422223] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/13+10 min/13+10 max/13+10.
[0523 18:42:21.422231] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/11+12 min/11+11 max/12+13.
[0523 18:42:21.422238] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:3061]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:42:21] 0x113c16000 (Info) Node [67] [172.168.1.20:3061] Client Logout (active 20).
[0523 18:42:25.215666] 0x7fff70fd4c20 (Debug) Node [69] [mdc1.thm.com:51296] connected.
[0523 18:42:25.216179] 0x7fff70fd4c20 (Debug) Active service - NSS ping from mdc1.thm.com:51295.
[0523 18:42:25] 0x113c16000 (Info) Node [69] [mdc1.thm.com:51296] Administrator Logout.
[0523 18:42:28.024018] 0x7fff70fd4c20 (Debug) Node [70] [mdc2.thm.com:52998] connected.
[0523 18:42:28.024578] 0x7fff70fd4c20 (Debug) Active service - NSS ping from mdc2.thm.com:52997.
[0523 18:42:28] 0x113c16000 (Info) Node [70] [mdc2.thm.com:52998] Administrator Logout.
[0523 18:42:29.456980] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:3082.
[0523 18:42:29.462550] 0x7fff70fd4c20 (Debug) Node [71] [172.168.1.20:3083] connected.
[0523 18:42:29.464877] 0x10db86000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:42:29.464884] 0x10db86000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:42:29] 0x10db86000 (Warning) [Node 71] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:42:29] 0x10db86000 (Info) Node [71] [172.168.1.20:3083] Client Login (active 21).
[0523 18:42:29.468837] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:42:29.468849] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:42:29.468860] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/17+11 min/17+11 max/17+11.
[0523 18:42:29.468866] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/15+12 min/15+12 max/15+12.
[0523 18:42:29.468873] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/13+13 min/13+13 max/14+14.
[0523 18:42:29.468881] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:3083]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:42:29] 0x113c16000 (Info) Node [71] [172.168.1.20:3083] Client Logout (active 20).
[0523 18:42:37.503450] 0x7fff70fd4c20 (Debug) Active service - NSS ping from 172.168.1.20:3104.
[0523 18:42:37.508525] 0x7fff70fd4c20 (Debug) Node [72] [172.168.1.20:3105] connected.
[0523 18:42:37.510815] 0x10bcd2000 (Debug) FSM received client capabilities: capsClient = 0x5680effef
[0523 18:42:37.510823] 0x10bcd2000 (Debug) CvRootDir is /: CvRootCookie is 0x2
[0523 18:42:37] 0x10bcd2000 (Warning) [Node 72] Disk Stripe Group 1 is DOWN for this client. # disks 4 unitmap[1] 0xfffff partaccess 0x1
[0523 18:42:37] 0x10bcd2000 (Info) Node [72] [172.168.1.20:3105] Client Login (active 21).
[0523 18:42:37.515025] 0x113c16000 (Debug) Cache SUMMARY [172.168.1.20] attrs now/0 min/0 max/0.
[0523 18:42:37.515038] 0x113c16000 (Debug) RSVD SUMMARY [172.168.1.20] reserved space max requested/32 MB accounted now/0 MB
[0523 18:42:37.515049] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopCapNegotiate cnt/1 avg/14+9 min/14+9 max/14+9.
[0523 18:42:37.515055] 0x113c16000 (Debug) VOP SUMMARY [172.168.1.20] VopClientId cnt/1 avg/12+11 min/12+11 max/12+11.
[0523 18:42:37.515062] 0x113c16000 (Debug) TKN SUMMARY [172.168.1.20] TokenRequestV2 cnt/2 avg/10+11 min/10+10 max/10+12.
[0523 18:42:37.515070] 0x113c16000 (Debug) NETWORK SUMMARY [172.168.1.20:3105]: QueuedInputMsgs max/1 QueuedOutputBytes max/0.
[0523 18:42:37] 0x113c16000 (Info) Node [72] [172.168.1.20:3105] Client Logout (active 20).

oliver's picture

Re-linking proxy files to moved assets

Hi,

Our FCSVR is currently set to reference media in our FCSVR>Productions folder which in turn has various subfolders, each containing media relating to individual productions.

Due to a re-organisation on the server, we've moved everything in the Productions folder to a new folder FCSVR>PRE_22-05-12. This has caused the Final Cut Server application to show nothing in the database (as the path has changed)

So I've set up PRE_22-05-12 to be scanned in the admin pane of FCSVR, adding the folder as a new device, adding a new scan response and schedule. This is fine and the assets are re-appearing in final cut server application. However, it's re-creating a new set of proxies for every asset again. Is there anyway to stop this and redirect fcsvr to use the old proxies rather than it recreating a whole new batch?

Thanks,

Oliver

Gerard's picture

Can't Color Label on Xsan

Here is my setup:

16tb Xsan
2 Mac Pro, MDCs
6 total Xsan clients via fiber
20-30 non-fiber clients accessing the Xsan via afp/nfs
All machines are bound to Open Directory
Using ACLs for permissions
All users have the same permission access

There are random folders, within my Xsan that I cannot color label whether I am on a fiber station, using afp/nfs.

If I do a "CMD I" on two folders, one that is able to be colored and one that isn't, their permissions are identical. The same is true if I check their permissions via Xsan Admin.

One constant is that I am only experiencing this issue within a certain project structure. All others are not having this issue.

Thanks in advance

Xsan 2: Xsan Admin displays an authentication alert if HTTPS proxy is used (Apple KB)

When using Xsan Admin on a Mac that has been configured to use an HTTPS proxy, you may encounter unexpected authentication issues when connecting to Xsan systems. The following alert may appear:
"Authentication failures occurred. Not all clients were successfully authenticated."

Read more: http://support.apple.com/kb/TS4277

cinedigital's picture

Lion XSan or StorNext Upgrade?

I'm looking at upgrading an existing small StorNext 3.5.1 SAN (RHEL 5 MDC & W2K8 Client) so that 5 Lion MacPro's can acces the 3 SAN volumes via Fibre Channel

The software is out of mainenance and the costs to upgrade StorNext to a version suitable for Lion's XSan client are quite high

It looks like an alternative would be to migrate to a XSan MDC running on a beefed up MacMini or s/h XServe

To keep filesystem compatability, would the migration first have to be done to V2.2 on Snow Leopard & then upgraded to Lion?

Would the W2K8 licence need to be replaced by a StornextFX licence or does a full StorNext licence also work with XSan?

Anyone have any thoughts about migrating from StorNext to XSan rather than the reverse?

TIA
Dave

Pages

Subscribe to Xsanity RSS