Submitted by carlota on Wed, 06/29/2016 - 5:52am
No one could see the Xsan volume. Logged into Xsan Admin, the volume was unmounted for everyone. Mounted the volume and Xsan Admin said it mounted for everyone. No errors in the logs. In a nice place mentally, I stepped away from my desk. The phone rings petardas, no one has access to the volume. Crap, what now? Log in, shows mounted. Log into a client, well, isn’t there. The other volumes are on the desktop. Go to /Volumes and it doesn’t appear there. Go to /Volumes/VOLUMENAME and viola, it’s there. But in the sidebar it’s hidden?!?!?!
Submitted by mora0022 on Tue, 01/26/2016 - 12:27pm
I am upgrading my 10.9.5 clients to 10.10.5 clients. We have Stornext MDCs. Does anyone have an upgrade guide since there were major changes to how XSAN 4 works?
Submitted by iroad on Thu, 10/22/2015 - 11:12am
I NEED HELP...
I have a Xsan 4 installed on my Xserve. Everything work well, I have the volume mounted on my desktop and the DNS is up e the Profile Manager is running.
The problem is this: I am trying to install the volume on a MacPro Yosemite, but doesn't work.
I tried everything, I pushed the certificate/profile from Profile Manager, nothing... i tried to install directly the certificate from the XSAN OS server...nothing.
I tried to change the fiber cable...nothing.
I have two network switches, one for regular connection with the internet and another one on another ip address for the metadata.
Mac pro has the Server applications...I NEED HELP please...
any suggestion will be appreciated.
Submitted by billgarmen on Fri, 08/28/2015 - 7:41pm
So after lots of testing and trials, I got this process to work. WRSTUDEN had the steps all right, it was just missing some steps to make it work for me.
This is to fixed a 10.10 OD issues by rebuilding the OD and connecting to back to an existing Xsan system
Backup your old xsan config files from /Library/Preference/Xsan
backup the system (just in case you need to restore)
back up your users if you can
Format the hard drive and reinstall the OS and server app
Now you have a clean fresh install.
In Server App Create New OD MASTER, import your users if you want to at this stage. (I did it at the end but I don’t think it makes a difference)
In Server App turn on Xsan (For SAN NAME use the exact same name you had used before)
This creates new Xsan config files and a new xsan config group in LDAP
Close Server app
Open up the new xsan config file (config.plist) at /Library/Preferences/Xsan and copy and past the following into the original config file from your old system:
the line below certSetRevision,
the line below sanRevision
and the line below sanUUID
The idea is to trick the system into thinking it created these files, and to re connect to the existing xsan
Once you copy the strings over, replace the original xsan config files the system made with the originals with modified stings of into /Library/Preferences/Xsan (I replaced all of the config files in the folder)
Copy those config files settings into LDAP with terminal - “sudo xsanctl pushConfigUpdate”
This will update the LDAP with the new xsan settings. If you got the stings wrong, they commend will error out and not work
Open server app
You should now have your original volumes listed in the Xsan pan
You can start the SAN from the GUI
Add all your users back and you are golden. If you have to rebuild the users you will have to reset permission on the volume for you clients to work.
This took a while to figure out, I hope it will help others.
Submitted by phil_t on Mon, 08/24/2015 - 7:58am
I am currently still running a .local environment and was considering updating from 10.9.5 with XSAN 3 to XSAN4 (Server App). Heard that it won't allow dot local anymore.. Unfortunately I wont be able to change the environment because we have several subsidiaries.
Does anyone have experience with this issues? Been thinking of maybe setting up another DNS just for the production but worried about certificates...
Submitted by roadmac on Fri, 08/14/2015 - 4:35pm
Promise E class and J class SAS expansion chassis
ActiveRaid with SAS expansion chassis
QLogic 5800 and 5600 FC switches
Mac 12 core 10.6.8 FinalCutServer Host
StorNext 4.7.1 HA MDC
StorNext and Suse Linux can not see 2 stripe groups that are associated with the Promise Raid.
Running fs_scsi -p shows all devices except for the missing SG’s from the Promise Raid
Running “paths” in CVadmin shows the same results
The GUI for Active and Promise show all drives, LUNs mounted, controllers up.
Disk Utility shows missing LUNs on the ActiveRaid, but all LUNs for the Promise.
Quantum engineering spent hours on this issue and conclude that it is a hardware issue and can not be repaired in software.
Question: Can the 2 missing stripe groups be restored ?
Submitted by Nolf on Fri, 08/14/2015 - 4:32am
Need help and advice in the optimization of the raid for xsan. There raid 3 LUN (raid 1 - medatada, and 2 to 6 disk LUNs, the total partition data ± 40Tb). 99% of the information will be large-sized videos.
The question is what values for the parameters will be the most optimal.
block allocation size
Thanks in advance for any advice<
Submitted by XR on Sun, 04/26/2015 - 4:45pm
I am facing a problem in XSAN 2.1.1 volume. My XSAN volume gets interrupted whenever i delete data from it or move large number of files from one folder to another within a volume. Plus MDCs are updating metadata journal quite slow. (takes 4 to 5 seconds for updating any newly placed files)
Sometimes when i create a folder on volume from one mdc or client, other mdc and clients show it zero kb and as a ghost folder until i restart that client or mdc.
Anyone could please help me on this :(
Submitted by Michael AE on Mon, 03/02/2015 - 2:56am
Im sitting here with a Mac Pro as MDC, and a 20TB SAN.
Ive added multiple clients on here before, and never had any issues.
Now I need to add more clients, but it simply won't work! I get the "client config error" when using the MDC to add them.
I have tried to remove the xsan config folder, disabling/enabling xsan, restarted all machines and servers etc.
When I remove everything from the client, and go to the xsan to add a machine, I can see the machine, I can authenticate, and I don't make it a MDC - but then it starts to write the conf file, and it fails.
Anyone has any suggestions at all?
Submitted by AnthonyRS on Tue, 08/19/2014 - 9:43am
Xsan 1.4.2 MDC 10.5.8 freezes and crashes when trying to mount the Volume on the MDC. the only error that gets reported is a malloc error.
This is an old Xsan 1.4.2 that can only mount on the MDC so they can backup the data so we can stop using the system. now in the middle of backing up this happens.
By the way this system has been running as a general use area and not really in proper use and not critical so it has only 1 MDC. But it turns out some people have put data on it they shouldnt have.
I can start and activate the Volume without any problems but the problem comes in when i want to mount the volume
The following is what the logs report when i run "sudo mount -t acfs DataSan /Volumes/DataSan" to mount the volume.
Aug 19 15:27:13 xserve03 kernel: CVFS 'DataSan': Buffer Cache blksize 4096, #blocks min 256 max 8192
Aug 19 15:27:13 xserve03 kernel: CVFS 'DataSan': request reserved space 0x2333333
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label MD_Lun con 2 lun 0 unit 0.0 state 0xf4 dev 0xe00000a rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label RLUN08 con 2 lun 0 unit 1.0 state 0xf4 dev 0xe000004 rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label RLUN07 con 1 lun 0 unit 2.0 state 0xf4 dev 0xe00000b rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label RLUN06 con 2 lun 0 unit 3.0 state 0xf4 dev 0xe00000c rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label RLUN05 con 1 lun 0 unit 4.0 state 0xf4 dev 0xe000003 rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label RLUN04 con 2 lun 0 unit 5.0 state 0xf4 dev 0xe000006 rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label RLUN03 con 1 lun 0 unit 6.0 state 0xf4 dev 0xe000005 rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label RLUN02 con 1 lun 0 unit 7.0 state 0xf4 dev 0xe000007 rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label RLUN01 con 2 lun 0 unit 8.0 state 0xf4 dev 0xe000008 rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label Alt_Lun03 con 1 lun 0 unit 9.0 state 0xf4 dev 0xe000009 rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label Alt_Lun02 con 1 lun 0 unit 10.0 state 0xf4 dev 0xe00000d rawname
Aug 19 15:27:13 xserve03 kernel: MdOpenDisks: label Alt_lun01 con 2 lun 0 unit 11.0 state 0xf4 dev 0xe00000e rawname
Aug 19 15:27:13 xserve03 kernel: CVFS 'DataSan': FsBlk size 16384, bits 14, mask 0x3fff
Aug 19 15:27:13 xserve03 kernel: CVFS 'DataSan': Sector size 512, bits 9, mask 0x1ff
Aug 19 15:27:13 xserve03 kernel: Mounted filesystem DataSan to FSM on host 192.168.101.24
Aug 19 15:27:13 xserve03 kernel: Using v1 readdir for 'DataSan'
Aug 19 15:27:13 xserve03 kernel: Xsan: enabling extended security on volume "DataSan"
Aug 19 15:27:13 xserve03 fsmpm: PortMapper: Mount Event for /Volumes/DataSan on /dev/disk16
Aug 19 15:27:13 xserve03 com.apple.launchd (org.openldap.slapd): Throttling respawn: Will start in 2 seconds
Aug 19 15:27:13 xserve03 fsmpm: fsmpm(177,0xa0847720) malloc: *** error for object 0x809a00: non-page-aligned, non-allocated pointer being freed\n*** set a breakpoint in malloc_error_break to debug
Aug 19 15:27:22 xserve03 com.apple.launchd (org.openldap.slapd): Exited with exit code: 1
Aug 19 15:27:22 xserve03 com.apple.launchd (org.openldap.slapd): Throttling respawn: Will start in 3 seconds
Aug 19 15:27:33 xserve03 com.apple.launchd (org.openldap.slapd): Exited with exit code: 1
Aug 19 15:27:33 xserve03 com.apple.launchd (org.openldap.slapd): Throttling respawn: Will start in 3 seconds
Aug 19 15:27:39 xserve03 ReportCrash: Formulating crash report for process fsmpm
Aug 19 15:27:39 xserve03 kernel: Reconnecting to local portmapper on host '127.0.0.1'
Aug 19 15:27:39 xserve03 kernel: Fsmportmapper on host 127.0.0.1 not responding, retrying...
Aug 19 15:27:39 xserve03 KernelEventAgent: tid 00000000 received VQ_NOTRESP event (1)
Aug 19 15:27:39 xserve03 KernelEventAgent: tid 00000000 type 'acfs', mounted on '/Volumes/DataSan', from '/dev/disk16', not responding
Aug 19 15:27:40 xserve03 ReportCrash: Saved crashreport to /Library/Logs/CrashReporter/fsmpm_2014-08-19-152738_xserve03-2.crash using uid: 0 gid: 0, euid: 0 egid: 0
Aug 19 15:27:41 xserve03 kernel: Reconnecting to FSS 'DataSan'
Aug 19 15:27:41 xserve03 com.apple.launchd (org.openldap.slapd): Exited with exit code: 1
Aug 19 15:27:41 xserve03 com.apple.launchd (org.openldap.slapd): Throttling respawn: Will start in 5 seconds
Aug 19 15:27:43 xserve03 sshd: DEAD_PROCESS: 307 ttys001
Aug 19 15:27:50 xserve03 com.apple.launchd (org.openldap.slapd): Exited with exit code: 1
Aug 19 15:27:50 xserve03 com.apple.launchd (org.openldap.slapd): Throttling respawn: Will start in 7 seconds
I have run permissions repairs
run cvfsck -nv, cvfsck -wv and cvfsck -j
but none of these report any INode errors or any problems with the volume.
There isn't really another machine to setup as an Xsan client that will work with this version of Xsan so some help to get the MDC up and running would be great