tonyswu's picture

Xsan Volume Slow Only for FCPX After Expansion

Hi,

I have a client with a small Xsan volume (about 8TB). They got an used Xserve RAID, and we split it into 2 LUNs and added them into the volume to expand the storage size. We also did a defrag afterwards.

Everything seems to work, except FCPX now works very slow, especially during exporting. When we copy to / from the Xsan directly in Finder, it's still fast, so we are not quite sure what the problem is. One thing we did notice is when FCPX is working on local external hard drive, the CPU load is 99% all the time during exporting. However when working on the Xsan volume, the CPU load only hits 99% for a quarter of the duration during exporting. Sounds like something is preventing FCPX from working 100% that way it should.

Wondering if anyone has run into this before and can offer some insight. I am rebooting the whole thing tonight, and if that still doesn't fix it, then I'll have to backup, wipe, and re-do.

Thanks.

returnofxsan's picture

If using a lot of JBOD is LUN striping still useful?

If I have most of my storage in a configuration where there is one RAID head with a bunch of JBODs attached so they all share a single controller and fibre port, is it still useful to let Xsan stripe across LUNs? If I didn't break the storage into smaller LUNs so Xsan can stripe them, I could be more economical and use RAID-6 with larger LUNs.

nachoguapito's picture

Delete Volume

im having trouble deleting this luns and volume. please see attach photos

[img]http://www.flickr.com/photos/nachography/9335156582//img

[img]http://www.flickr.com/photos/nachography/9335156520//img

huntson's picture

Properly formatted LUNS not showing up

I have some raid units that are being run through an Atto SCSI->Fibre bridge. This unit went down so I shut down my SAN while the unit was getting repaired. Now that I have put everything back the LUNS that were showing up from the fibre bridge are not showing up anymore in Xsan Admin and thus the volumes are not able to mount. Interestingly the disks show up in Disk Utility and as Xsan formatted. Any ideas?

MDCS: 10.8.3

DLpres's picture

Fiber: Only the first 6 clients can see the storage?!

Forums: 

We have one SANBox 5602 in our facility, serving Mac Pro workstations with Atto Celerity FC-41 and 42 HBAs. It used to serve our Avid Unity with no issues. Last week I got rid of the Unity and upgraded all our systems to 10.8.4.

The problem is an invisible "quota" where only the first 6 systems to be powered on get to see the storage. Any consecutive machines see nothing on the fabric, yet ALL the devices (switch and HBAs) on all ports see a good link, and the switch reports the clients are active and logged in to the fabric.

I already went through the entire fiber infrastructure - ensuring all HBAs have the latest firmware and drivers, ditto for the switch, and matching SFP's and fiber runs. The switch is fully licensed.
I tried a switch factory reset; set a fixed port type and speed (F for the hosts, the storage only takes FL); ensured only hosts have I/O Streamguard; tried putting everyone in 1 zone, and even disabling zoning altogether; I even tried Device Scan on targets.

Nothing made any difference. The only workaround I know is to power-cycle everything which just restarts the "quota" again.

I should disclose that I'm not running XSAN but metaSAN... but this is independent of any SAN software; if the underlying fabric doesn't work then nothing works (besides, I'm still considering XSAN :-) ).

Qlogic inspected the switch service dumps and couldn't find a single thing wrong with it. I'm at my wit's end, and know most everyone here is experienced with similar fiber setups. Do you have any ideas??

arls1481's picture

Tape library compatibility

Does ArchiWare provide a recommended or compatible hardware list?
I am in the process of an upgrade of my arrays and will need to increase my tape library capacity.

arls1481's picture

Volume not mounting - LUNS with exclamation points

So after withering through a full failure on one of my LUNs, well haven't really got through it but I got all my LUNs back online as far as I can tell from the WebPAM on all my Vtraks, my volumes will not mount and I need some guidance please!

The long end of the story is that I had 1 of 2 drives in my meta-data & journal volume drive fail at the same time as 4 of 6 drives in a data LUN died. With only 4 GR Spares available for that drawer, I think you all know what I was faced with. I have a vtrak Ex610Fd system with 4 E-class and 4 J-class with 4 GR spares per E&J all compounded in to 2 Xsan volumes.
I've attached a screen grab of my LUNs for reference if it helps.

Basically, Vtrak1 (my top E&J) had the failures and as a result I ended up successfully recovering the meta-data/journal LUN but the data LUN went offline and I ended up having no choice but to replace the bad disks and initialize it as a new LUN duplicating the naming/settings that were there before. Promise support was of little help and told me my volume was lost because of that. Which I don't buy but that's why I am turning to you all for some help here.
I can download and attach whatever other logs/images you need if it helps or try to explain more but what I need is some help figuring out how to get my volume back online.
I think that the exclamation point icons mean that Xsan can't see those LUNs but I have all 4 subsystems online and OK so I don't know why I'm stuck here.
Also, I realize that everyone sets things up differently but is it conceivable that my LUN schema provides for failure in this manner? What I mean is that is the XSan able to deal with a single LUN failing in a multi-LUN volume?
Hopefully that makes some sense?!?!!!
And thanks for anyone's time and effort in advance!
-AMH

[img]https://lh4.googleusercontent.com/-y7Bt6VnCkY0/Ud73S7JjAlI/AAAAAAAABEA/5.../img

returnofxsan's picture

LUN numbering issue

I've been reusing the same LUN numbers across my fibre targets ie 0-6 without problem until recently. I attached an additional target with the intention of creating a new Xsan volume on the same MDCs. This time just having the new storage (Xyratex) on the same SAN causes one of my other targets (Enhance) to be knocked offline. I was able to stop that from happening by changing the LUNs to a higher number on the Xyratex. However I still have to leave LUN 0 duplicated because both the Xyratex and the Enhance don't even show up on the Mac without having a LUN 0 present.

I've never heard of there being any sort of LUN restrictions in any of the Xsan docs or things I've read online. Is there some known reasoning behind what I'm experiencing? I'm still having some issue here because even though the Enhance no longer gets bumped off, the Xyratex has ridiculously slow speeds ~10MB/s and reports errors.

Thanks

TRANSIT's picture

Xsan - No Visible LUNS - LSI Issue?

I have a small Xsan (2 MDCs, 7 Clients) running on 10.8.3 with a Promise x30 24 Bay RAID and a Qlogic 5800 fibre switch. I just added a new client running on a Thunderbolt iMac with a Sonnet Express SE housing an LSI7204EP-LC. The client added fine but its coming up with No Visible LUNS in Xsan admin and I can't mount the volume or see the LUNS in disk utility.

I looked at the firmware of the card, and its 1.03.24.00; all Apple branded LSI Cards only go up to 1.03.23.00 and they have an EFI version, which mine does not. Is this the culprit and if so, is there any way to get this firmware to work or downgrade to the Apple approved version?

LSI says Apple does its own firmware and they dont have access to it. Is this floating around anywhere on the internet?

mrwitherspoone's picture

Bus Error on mount

I've got an xsan that was working, but then there was some networking issues that cause the fs to get "dirrty" so I ran the cvfsck and now the fs is in a clean state. I've reduced the potential issue variables by using 1 meta controller and using it as the client (nothing else connected). I get a Bus error when trying to mount (crash log at bottom).

When I bring up meta 1 I can query the SanVol:

File System Services (* indicates service is in control of FS):
1>*SanVol1[0] located on meta1.local:49161 (pid 260)

Select FSM "SanVol1"

Created : Tue Feb 28 11:44:18 2006
Active Connections: 0
Fs Block Size : 8K
Msg Buffer Size : 4K
Disk Devices : 9
Stripe Groups : 2
Fs Blocks : 586021888 (4.37 TB)
Fs Blocks Free : 215315920 (1.60 TB) (36%)
_________________________________________________________________

when I try and mount the sanvol:
/Library/Filesystems/Xsan/bin/mount_acfs
Bus error

__________________________________________________________________
then I can no longer query the FS:
List FSS

File System Services (* indicates service is in control of FS):
1>*SanVol1[0] located on meta1.local:49161 (pid 260)

Select FSM "SanVol1"

Admin Tap Connection to FSM failed. - Operation timed out
Cannot select FSS "SanVol1"
Xsanadmin>

________________________________________________________________

        • **********

Host Name: meta1-pictureframes-com
Date/Time: 2013-07-08 11:53:58.529 -0400
OS Version: 10.4.11 (Build 8S169)
Report Version: 4

Command: mount_acfs
Path: /Library/Filesystems/Xsan/bin/mount_acfs
Parent: bash [306]

Version: ??? (???)

PID: 327
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000001

Thread 0 Crashed:
0 libSystem.B.dylib 0x90004ce0 strncmp + 128
1 mount_acfs 0x0000275c 0x1000 + 5980
2 mount_acfs 0x00001af4 0x1000 + 2804
3 mount_acfs 0x0000199c 0x1000 + 2460

Thread 0 crashed with PPC Thread State 64:
srr0: 0x0000000090004ce0 srr1: 0x000000000000d030 vrsave: 0x0000000000000000
cr: 0x44000422 xer: 0x0000000020000004 lr: 0x000000000000275c ctr: 0x0000000000000003
r0: 0x0000000000000003 r1: 0x00000000bfffe4f0 r2: 0x00000000fefefeff r3: 0x00000000fffffffd
r4: 0x000000000001c884 r5: 0x0000000000000006 r6: 0x0000000080808080 r7: 0x0000000000000030
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000005 r11: 0x0000000042000428
r12: 0x0000000090004c60 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000000
r20: 0x0000000000000000 r21: 0x0000000000000000 r22: 0x0000000000000000 r23: 0x00000000bffffc64
r24: 0x0000000000000000 r25: 0x0000000000000001 r26: 0x00000000bffffbdc r27: 0x0000000000000008
r28: 0x0000000000000001 r29: 0x0000000000029ae4 r30: 0x00000000bffffbe0 r31: 0x00000000000026b8

Binary Images Description:
0x1000 - 0x22fff mount_acfs /Library/Filesystems/Xsan/bin/mount_acfs
0x8fe00000 - 0x8fe52fff dyld 46.16 /usr/lib/dyld
0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x907bb000 - 0x90895fff com.apple.CoreFoundation 6.4.11 (368.35) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x908e0000 - 0x909e2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x90a3c000 - 0x90ac0fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90aea000 - 0x90b5afff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90b70000 - 0x90b82fff libauto.dylib /usr/lib/libauto.dylib
0x91110000 - 0x9111efff libz.1.dylib /usr/lib/libz.1.dylib
0x913f7000 - 0x9141ffff com.apple.SystemConfiguration 1.8.3 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x91432000 - 0x9143dfff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib

        • **********

Host Name: meta1-pictureframes-com
Date/Time: 2013-07-08 12:10:23.971 -0400
OS Version: 10.4.11 (Build 8S169)
Report Version: 4

Command: mount_acfs
Path: /Library/Filesystems/Xsan/bin/mount_acfs
Parent: bash [305]

Version: ??? (???)

PID: 315
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000001

Thread 0 Crashed:
0 libSystem.B.dylib 0x90004ce0 strncmp + 128
1 mount_acfs 0x0000275c 0x1000 + 5980
2 mount_acfs 0x00001af4 0x1000 + 2804
3 mount_acfs 0x0000199c 0x1000 + 2460

Thread 0 crashed with PPC Thread State 64:
srr0: 0x0000000090004ce0 srr1: 0x000000000000d030 vrsave: 0x0000000000000000
cr: 0x44000422 xer: 0x0000000020000004 lr: 0x000000000000275c ctr: 0x0000000000000003
r0: 0x0000000000000003 r1: 0x00000000bfffe4f0 r2: 0x00000000fefefeff r3: 0x00000000fffffffd
r4: 0x000000000001c884 r5: 0x0000000000000006 r6: 0x0000000080808080 r7: 0x0000000000000030
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000005 r11: 0x0000000042000428
r12: 0x0000000090004c60 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000000
r20: 0x0000000000000000 r21: 0x0000000000000000 r22: 0x0000000000000000 r23: 0x00000000bffffc64
r24: 0x0000000000000000 r25: 0x0000000000000001 r26: 0x00000000bffffbdc r27: 0x0000000000000008
r28: 0x0000000000000001 r29: 0x0000000000029ae4 r30: 0x00000000bffffbe0 r31: 0x00000000000026b8

Binary Images Description:
0x1000 - 0x22fff mount_acfs /Library/Filesystems/Xsan/bin/mount_acfs
0x8fe00000 - 0x8fe52fff dyld 46.16 /usr/lib/dyld
0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x907bb000 - 0x90895fff com.apple.CoreFoundation 6.4.11 (368.35) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x908e0000 - 0x909e2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x90a3c000 - 0x90ac0fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90aea000 - 0x90b5afff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90b70000 - 0x90b82fff libauto.dylib /usr/lib/libauto.dylib
0x91110000 - 0x9111efff libz.1.dylib /usr/lib/libz.1.dylib
0x913f7000 - 0x9141ffff com.apple.SystemConfiguration 1.8.3 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x91432000 - 0x9143dfff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib

Pages

Subscribe to Xsanity RSS