Oddball client not mounting XSan Volumes

Background: My client, a TV News broadcast station, had Apple and a third-party design and install a Apple based XSan storage and network. They ran all new fiber and gigabit ethernet to each station to use the XSan. It has been working great, with the exception noted below.
Setup: 2 MD Controllers, 1 XServe, 4 XRaids, each make up two 2 large TB volumes (raid 5, stripped together).
XServe, XRAID, MD controllers, and all clients are all connected together on a Fibre and Fiber Optic network using QLogic switches. SUBNET: 10.200.1.x.
Ethernet Network, also connected all the above together on HP Gigabit Switches. SUBNET: 10.100.1.x The public WAN is made available on this subnet by a connection to the HP switches. Still getting details on how this was done.
Everything is running OS X 10.4.8 or better, XSan File System 1.4.
Setup
There are 8 workstations (edit bays) that act as infusion and editing stations. Each station has two XSans volumes mounted NEWS01 and NEWS02. They have the odd numbered bays use NEWS01 and the even numbered bays use NEW02.
PROBLEM
All bays mount the XSan volumes, except one. FCP08 will not mount the XSan volumes. We have rebooted the workstation, and even went to the extreme of shutting down the entire setup all bays and MD controllers, File Servers, etc.. then bringing everything backup up. Same problem.
Based on some forum discussion, we have tried the following:
* Ensured that there is no empty mount point in /Volumes
* Uninstalled all XSan Software and resinstalled v1.4 from Apple's website.
* Removed the client from the XSan Admin, and readded it, made sure to enter valid serial number, etc..
* Verified that all fibers are working, all link lights look good, and you can ping across the MD network.
When you use the XSan admin from either FCP08 (edit bay 08) or from the server, and you add both MD XSans to it, you see the client, and you click on the client and click either Mount (read-only) or Mount (Read/write).
It will show "Mounting..." and then it will flip back to "not mounted". The only feedback we have received so far is "ACCESS DENIED". All affinity setting are set to rwxrwxrwx (wide open), and all the volumes and workstation logins all have the same access to the volumes. I can not find any restrictive permissions anywhere.
I plan on trying to move them away from a /etc/hosts type setup to a proper DNS Server running on their XServe using the DNS Server function of OS X Server. But currently all edit bay stations have the same /etc/hosts file installed, which accounts for MD and ethernet networks.
ANY IDEAS what is wrong with this workstation? With the setup?
I have had extreme ideas from some who have said that we need to blitz the entire client, and reinstall the operating system. I am not willing to go down that route, since each edit bay was built manually without an image (another aspect I will remedying soon). It will take sometime to rebuild this edit bay client if I that is the only solution.
The only this question I have if that is the popular opinion, is what is different from a client OS install and the existing one regarding the XSan? This are edit bays, not private workstations, and no one installs any extra software or surfs the net, etc.. They are used for ingest and editing only.
HELP!
Mac OS X (10.4.10)

Hi,
You could check if it is Fibre Channel related:
from a terminal do a cvlabel -l
this should give you a list of the lun's in your volume.
When this tool does not show luns, you might have a zoning issue.
Regards
Donald

Similar Messages

Backup Controller cannot mount XSAN Volume

Hi Guys,
I've really have a big problem regarding the XSAN that I've just setup: There are 3 Xserves connected to the SAN - one for the main controller, one for backup and another one for fileserver. After a fresh install of the Leopard Server 10.5.6 on all servers and fresh install of Xsan 2.0 updated to 2.1.1, I tried creating an SAN from the main controller, I added first the main and backup controllers, authenticated them properly and was successful adding them to the SAN. After this, I created the volume and it mounted properly on the main controller. What I don't understand is that whenever I try to mount the volume to the backup controller, it is saying unable to mount and even I tried forcing it to mount in terminal using the command xsanctl mount VOLNAME, its giving me an error saying
"unable to mount volume, Cannot mount XSAN volume error code: 5"
What is that error message? When I tried typing cvadmin to the main controller, it only gave me this message:
Main Controller:
File System Services (* indicates service is in control of FS)
1>*XSAN[0] located on 10.0.0.101:49930 (pid 317)
Select FSM "XSAN"
When I type the same cvadmin to the backup controller, it gave me this message:
Backup Controller:
File System Service (* indicates service is in control of FS)
1> XSAN[1] located on 10.0.0.102:50384 (pid 331)
No FSSs are active
Select FSM "none"
What is happening? both servers are having a DNS name. Before I created the SAN, from the authenticate window, the server name is just the IP address of the Ethernet 0 (first ethernet port). Now whenever I fire up Xsan Admin, both controllers are now offline and if you authenticate them, the server name info suddenly changed from IP address to a DNS Name (e.g. from 194.170.34.12, changed to hct-mdc.ad.hct.ac.ae) which even if I type my admin username and password cannot authenticate saying "server not found in network"
I really don't know now what to do and they need to fix the issue asap.
I would really appreciate your help guys!
Thanks.
jantoniophi

Hi,
I am accessing this WS via ARD, so public LAN is definitely there. I have not connected the "Xsan" network (but it should be no problems communicating the Xsan traffic over this single LAN connection).
With the firewall, the situation is more strange. When I try to open the Firewall settings on Sharing, there is a dialog "Other firewall software is running on this computer." I googled this and it seems that this was a common problem on 10.3. They suggest to delete com.apple.sharing.firewall.plist file but it is not there on 10.4.
"sudo ipfw list" shows this:
00001 allow udp from any 626 to any dst-port 626
65535 allow ip from any to any
Any ideas on how to make Firewall behave as expected? I will try to reinstall if I don't receive a reply.
Thanks.

Unable to mount XSAN volume on client workstation

We just reimaged one of our machines and we are now unable to mount the xsan volume. Originally when the machine hooked up the IP was wrong and the XSAN couldn't see it. This has been fixed and the XSAN sees it now and it is authenticated, but when we try to mount the volume we get this error
Jan 26 13:54:48 *** Xsan Admin[23616]: ERROR: Error reading computer properties: kOfflineError (0)
Jan 26 13:55:37 *** Xsan Admin[23616]: ERROR: Error mounting volumeâ€¦: Server returned a non-zero status code (100007)
Jan 26 13:55:48 *** Xsan Admin[23616]: The temporary directory at "/private/var/folders/Eu/Euvo7L8cHAmWwo7ntmj8ak+TI/TemporaryItems/(A Document Being Saved By Xsan Admin 33)" could not be deleted.
The *'s was the name of the machine, apple has been little to no help. We have tried removing the machine form the XSAN and then adding it back in, same issue. Tried reinstallingt eh client, same issue. Any ideas?

This is the error on server
ERROR: Error mounting volumeâ€¦: Server returned a non-zero status code (100007)

Cannot mount Xsan volume on Mac Pro

Hi,
I installed a new workstation - a first Mac Pro in our PPC Xsan deployment. I installed Xsan, then latest updates. However, I cannot mount an Xsan volume on this workstation. This is an abstract from the log:
May 16 19:06:14 Mac-Pro kernel[0]: Xsan Client Revision 2.7.201 Build 7.23 Built for Darwin 8.0 Created on Mon Nov 13 11:53:07 PST 2006
May 16 19:06:14 Mac-Pro sudo: root : TTY=unknown ; PWD=/Library/Filesystems/Xsan/debug ; USER=root ; COMMAND=/sbin/kextload -v -s /Library/Filesystems/Xsan/debug /System/Library/Extensions/acfsctl.kext
May 16 19:06:14 Mac-Pro /Library/Filesystems/Xsan/bin/fsmpm: NSS: No FS Name Servers file - NAME SERVICE DISABLED.
May 16 19:06:14 Mac-Pro fsmpm[246]: Portmapper: ComputerInfo: computer_name = "Mac Pro", hostname = "Mac-Pro"
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume Meta on device: /dev/rdisk1 (blk 0xe000003 raw 0xe000003) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018365' serial # '5000393000018365L0' Size: 490190848 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID2_Left on device: /dev/rdisk2 (blk 0xe000004 raw 0xe000004) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018A78' serial # '5000393000018A78L0' Size: 5860554719 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID2_Right on device: /dev/rdisk3 (blk 0xe000005 raw 0xe000005) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018805' serial # '5000393000018805L0' Size: 5860554719 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID1_Right on device: /dev/rdisk4 (blk 0xe000006 raw 0xe000006) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018319' serial # '5000393000018319L0' Size: 5860554719 Sector Size: 512
May 16 19:06:15 Mac-Pro servermgrd: xsan: [52] main: Waited 21 secs for fsmpm to start (now running)
May 16 19:06:15 Mac-Pro fsmpm[246]: PortMapper: Local FSD client is registered.
May 16 19:06:17 Mac-Pro servermgrd: xsan: [52] Done waiting for fsmpm to start
May 16 19:06:40 Mac-Pro servermgrd: xsan: [52/358E60] ERROR: mountvolumenamed(EditSAN): Cannot mount volume, file system does not know about it.
I tried reinstalling Xsan on this workstation, re-entering a licence key to the Xsan admin and rewriting Xsan settings, with no success.
All of the other 10 PowerMac workstations can access the Xsan volume with no problems.
Your help would be highly appreciated.

Hi,
I am accessing this WS via ARD, so public LAN is definitely there. I have not connected the "Xsan" network (but it should be no problems communicating the Xsan traffic over this single LAN connection).
With the firewall, the situation is more strange. When I try to open the Firewall settings on Sharing, there is a dialog "Other firewall software is running on this computer." I googled this and it seems that this was a common problem on 10.3. They suggest to delete com.apple.sharing.firewall.plist file but it is not there on 10.4.
"sudo ipfw list" shows this:
00001 allow udp from any 626 to any dst-port 626
65535 allow ip from any to any
Any ideas on how to make Firewall behave as expected? I will try to reinstall if I don't receive a reply.
Thanks.

[SOLVED] pam_mount will not mount truecrypt volume on login.

Hello.
I did system upgrade yesterday and encountered some problems with mounting my Truecrypt volume with pam_mount. I use pam_mount to mount my encrypted /home partionion at login. After first reboot and loging in I was dropped to / directory, with my /home partition clearly not mounted. I acknowledged the message from udev in pacman, that in some circumstances adding 'loop' to MODULES array in /etc/mkintcpio.conf is required and for a moment I thought it was it, but I tried this and it didn't help. Suprisingly, after another reboot I was placed im my home directory afer login, but it appears to be empty - I can see only dotfiles of few programs I used after the upgrade:
$ls -A ~/
.bash_history .links .qingy .viminfo .wicd
but my /home partition is obviously still not mounted. My relevant config files:
/etc/security/pam_mount.conf.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">

<pam_mount>

<debug enable="0" />




<mntoptions allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other" />

<mntoptions require="nosuid,nodev" />

<logout wait="0" hup="0" term="0" kill="0" />

<cryptmount>truecrypt --text --protect-hidden=no --keyfiles="/etc/home.key" %(VOLUME) %(MNTPT)</cryptmount>
<cryptumount>truecrypt -d</cryptumount>
<volume user="schirase" fstype="crypt" path="/dev/sda7" mountpoint="/home" options="fsck,relatime" />
<mkmountpoint enable="1" remove="true" />
</pam_mount>
/etc/pam.d/login
#%PAM-1.0
auth required pam_securetty.so
auth requisite pam_nologin.so
auth required pam_unix.so nullok
auth required pam_tally.so onerr=succeed file=/var/log/faillog
auth optional pam_mount.so
# use this to lockout accounts for 10 minutes after 3 failed attempts
#auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/var/log/faillog
account required pam_access.so
account required pam_time.so
account required pam_unix.sof
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
password optional pam_mount.so
#password required pam_unix.so sha512 shadow use_authtok
session required pam_unix.so
session optional pam_mount.so
session required pam_env.so
session required pam_motd.so
session required pam_limits.so
session optional pam_mail.so dir=/var/spool/mail standard
session optional pam_lastlog.so
session optional pam_loginuid.so
-session optional pam_ck_connector.so nox11
-session optional pam_systemd.so
/etc/pam.d/qingy
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_unix.so
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_unix.so
password required /lib/security/pam_unix.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_console.so
Any ideas how to make it work again?
[EDIT] OK, I've looked into it a little more and I realised that I should try loging in without qingy. I tried on agetty console and it worked as before. It looks like qingy upgrade changed my /etc/pam.d/qingy file into default one. The one above is and obviously unsuitable for use with pam_mount and I failed to see that at first. It should look similar to the example file for slim in the wiki article on pam_mount:
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_unix.so
auth optional /lib/security/pam_mount.so
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_unix.so
password required /lib/security/pam_unix.so
password optional /lib/security/pam_mount.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_mount.so
session optional /lib/security/pam_console.so
Sorry for the trouble, maybe at least it will help someone.
Last edited by Schirase (2012-03-25 17:49:21)

Having looked again, hal fails to start. I have it in rc.conf DAEMONS. When i try to start Hal manually, it also fails to start ...
Last edited by whitetimer (2010-11-09 16:45:46)

[Solved]NFS Client Not Mounting Shares

Here is my setup:
I have two Arch boxes that I am attempting to setup NFS shares on. The box that is going to be the server is headless FYI. So far, I have installed nfs-utils, started `rpc-idmapd` and `rpc-mountd` successfully on the server, and started `rpc-gssd` successfully on the client.
The folder I am trying to share is the /exports folder.
ls -l /exports
produces
total 8
drwxrwxrw-+ 110 daniel 1004 4096 Dec 6 17:26 Movies
drwxrwxrwx+ 13 daniel users 4096 Jan 8 19:12 TV-Shows
On the server:
/etc/exports
# /etc/exports
# List of directories exported to NFS clients. See exports(5).
# Use exportfs -arv to reread.
# Example for NFSv2 and NFSv3:
# /srv/home hostname1(rw,sync) hostname2(ro,sync)
# Example for NFSv4:
# /srv/nfs4 hostname1(rw,sync,fsid=0)
# /srv/nfs4/home hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/home gss/krb5i(rw,sync,nohide)
/exports 192.168.1.10(rw,fsid=0)
On the client:
showmount -e 192.168.1.91
Export list for 192.168.1.91:
/exports 192.168.1.10
Everything is looking hunky-dory. However, I go to mount using
sudo mount -t nfs4 192.168.1.91:/exports /mnt/Media
and the mount never takes place. It sits there and does nothing. I CAN, however, kill the process with Ctrl-c.
So does anybody have ANY idea why my shares aren't working.
EDIT: Just thought I should mention that all of the data in the /exports folder is a mount --bind from /mnt/media. All of the /mnt/media is contained on a USB external hard drive. I did notice that there is an ACL.
getfacl /exports
getfacl: Removing leading '/' from absolute path names
# file: exports/
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
Last edited by DaBungalow (2014-01-10 03:18:05)

I found what the problem was. Apparently rpc_gssd was causing a problem. Stopping it fixed everything.

Disk Utility from Install CD will not mount valid volumes

I'm trying to make an image of my internal disk onto an external USB disk. This disk has a FAT32 partition that is automatically seen and mounted when I am booted into the OS. (It also contains an unformatted partition.)
When I boot from the OS X 10.3 Install CD and run Disk Utility (in order to image the internal disk), the external disk and its partition are correctly detected and can be scanned, polled, and ejected without error, but are not automatically mounted. Clicking the "Mount" button has no effect.
A FAT16 flash drive exhibits the same behavior.
Thanks.

Hello! There's another way to image your disk without starting form another disk. Open disk utility and choose new image. It will bring up the box showing you the options. Choose sparse disk image and then under size choose custom. There set the image size in MB. As an example I chose 7000 mb for a 7 gig image. Now name the file and let it mount the image. Once it's mounted go to the disk utility and click on your drive and then select the restore tab. Once there drag your main disk to the source pane and then drag the mounted disk image to the destination pane and then click on restore. You will now have created a disk image of the drive you need. Tom

H: drive on Windows client not mounted

In WGM I defined network accounts for about 10 windows clients.
Our Xserve is used as a PDC and I can connect the clients to the domain and login using the accounts.
However, I tested the login procedure before creating a Home folder for each accounts and now the H: drive doesn't get mounted.
Next I removed the Windows-profiles hoping to start with a clean profile but they don't get recreated.
Can I force OS X server to recreate the profile info?

I've got a better understanding now of how to make folders and profiles by hand and setting the right privileges.

Xsan will not mount on clients

Xsan updated recently to 1.4. Problem started on 1.3 Working fine until reboot of one of the client computers. Now Xsan volume will not mount on any client. Updated to 1.4, ran cvfsck. Still no go. Volume is over 90%. I have read that this may cause issues. How can I get files off if I cannot mount? Thanks!

Try the following:
From finder -->Go --> Go to folder --> /Volumes
Delete the alias for the XSAN volume you want to mount.
For whatever reason the alias sticks even if the volume was unmounted. Below is an explanation from Apple.
Xsan mounts will fail if they have the same name
Xsan will not mount any volume that has the same name as any existing volume or folder located at /Volumes/.
Unlike some mounting mechanisms that automatically resolve name conflicts (for example, the Finder will append characters to each mounted volume name), the Xsan backend agent simply won't mount the volumes.
To avoid this issue, create a unique name for each volume to be mounted.

Xsan 4 will not mount volume on client

I recently upgraded my MDC and my client computer to Yosemite. I went through the migration process the best I could and created a Configuration Profile on my MDC for my client computer. I installed the profile successfully but the volume will not mount on the client computer. On the client computer within Profiles, the Xsan Configuration Profile has in red "Unsigned" underneath it, is that what is causing the problem?
Also a few notes: there are two other client computers that haven't been upgraded and are running Maverick and the volume does mount to those computers. The volume is also mounted on the MDC and if I go to Disk Utilities on the client computer I do see the volume, just not mounted.
Any help would be great! Thank you.

Thank you Claudio,
After doing much research and testing I believe you are onto something with my fsmpm or my .auth_secret file not being created. After using Server.app on the MDC I used the configure profile within Server.app. After installing the profile on my client computer it didn't mount and when looking within the Library/Preferences/Xsan folder there was no files (including the hidden .auth_secret file). So I then I used the web profile interface to create the configuration profile and this time it installed the fsnameservers and config.plist files but not the hidden auth_secret file and still no mount.
To answer some of you questions, I did try several times the "sudo xsanctl mount Volume Name" but had no success. I was previously running 10.9 on the MDC and my client computer. I am not sure if the MDC already had an Open Directory Master before upgrading and I did have a little bit of problems activating Xsan, because some of my DNS settings had changed. I got that all squared away and Xsan started working.
The reason I believe it is a fsmpm issue is because when I executed the command "sudo xsanctl i" (views the volumes connected to Xsan) I go a message reading "fsmpm not running error3". So after reading this forum Xsan: "fsmpm not running" message in Xsan Admin - Apple Support I copied the .auth_secret from the MDC to my client and still no mount. I tried again with all the files within Library/Preferences/Xsan folder and nothing. I then got the .auth_secret file from another client computer running 10.9 and still no mount, BUT when I copied all the files within the 10.9 client's Library/Preferences/Xsan the volume appeared! YEAH! But I'm not sure if this is a fix I should be happy with or continue to figure out why its not working the proper way? That way in the future I'm not running into this issue over and over again.
So I need to figure out either how to get my fsmpn running in 10.10 or figure out why my my Server.app on the MDC won't create the auth_sect file. I read somewhere that within the Xsan screen in the Sever app it should show the Authentication Secret, but I do not see this on my Xsan screen. Should it be there and if so is this where my problem steams from? Any thoughts? Thank you so much!

NEED HELP Xsan volume is not mounted (strange problem)

I ask the help in solving the volume mount problem. (advance I am sorry for my english)
All began with the fact that the MDC is rebooted and on the two LUNs were gone XSAN label. I relabeled these LUNs using commands:
cvlabel -c >label_list
then in the file label_list I corrected unknown disks on the label with a same names that were. Then I ran the cvlabel label_list command. Finally I got the correct label on all drives.
# cvlabel -l
/dev/rdisk14 [Raidix meta_i          3365] acfs-EFI "META_I"Sectors: 3906830002. Sector Size: 512. Maximum sectors: 3906975711.
/dev/rdisk15 [Raidix QSAN_I          3365] acfs-EFI "QSAN_I"Sectors: 7662714619. Sector Size: 4096. Maximum sectors: 7662714619.
/dev/rdisk16 [Raidix meta_ii         3365] acfs-EFI "META_II"Sectors: 3906830002. Sector Size: 512. Maximum sectors: 3906975711.
/dev/rdisk17 [Raidix 2k_I            3365] acfs-EFI "2K_I"Sectors: 31255934943. Sector Size: 512. Maximum sectors: 31255934943.
/dev/rdisk18 [Raidix 2k_II           3365] acfs-EFI "2K_II"Sectors: 31255934943. Sector Size: 512. Maximum sectors: 31255934943.
/dev/rdisk19 [Raidix QSAN_II         3365] acfs-EFI "QSAN_II"Sectors: 7662714619. Sector Size: 4096. Maximum sectors: 7662714619.
The volume [2K] starts successfully.
but not mounted on the MDC and client.
I ran a volume check:
sh-3.2# cvfsck -wv 2K
Checked Build disabled - default.
BUILD INFO:
#!@$ Revision 4.2.2 Build 7443 (480.8) Branch Head
#!@$ Built for Darwin 12.0
#!@$ Created on Mon Jul 29 17:01:44 PDT 2013
Created directory /tmp/cvfsck3929a for temporary files.
Attempting to acquire arbitration block... successful.
Creating MetadataAndJournal allocation check file.
Creating Video allocation check file.
Creating Data allocation check file.
Recovering Journal Log.
Super Block information.
FS Created On               : Wed Oct 2 23:59:20 2013
Inode Version               : '2.7' - 4.0 big inodes + NamedStreams (0x207)
File System Status          : Clean
Allocated Inodes            : 4022272
Free Inodes                 : 16815
FL Blocks                   : 79
Next Inode Chunk            : 0x51a67
Metadump Seqno              : 0
Restore Journal Seqno       : 0
Windows Security Indx Inode : 0x5
Windows Security Data Inode : 0x6
Quota Database Inode        : 0x7
ID Database Inode           : 0xa
Client Write Opens Inode    : 0x8
Stripe Group MetadataAndJournal             ( 0) 0x746ebf0 blocks.
Stripe Group Video                          ( 1) 0x746ffb60 blocks.
Stripe Group Data                           ( 2) 0xe45dfb60 blocks.
Inode block size is 1024
Building Inode Index Database 4022272 (100%).
   4022272 inodes found out of 4022272 expected.
Verifying NT Security Descriptors
Found 13 NT Security Descriptors: all are good
Verifying Free List Extents.
Scanning inodes 4022272 (100%).
Sorting extent list for MetadataAndJournal pass 1/1
Updating bitmap for MetadataAndJournal extents 21815 ( 0%).
Sorting extent list for Video pass 1/1
Updating bitmap for Video extents 3724510 ( 91%).
Sorting extent list for Data pass 1/1
Updating bitmap for Data extents 4057329 (100%).
Checking for dead inodes 4022272 (100%).
Checking directories 11136 (100%).
Scanning for orphaned inodes 4022272 (100%).
Verifying link & subdir counts 4022272 (100%).
Checking free list. 4022272 (100%).
Checking pending free list.
Checking Arbitration Control Block.
Checking MetadataAndJournal allocation bit maps (100%).
Checking Video allocation bit maps (100%).
Checking Data allocation bit maps (100%).
File system '2K'. Blocks-5784860352 free-3674376793 Inodes-4022272 free-16815.
File System Check completed successfully.
check not helping
sh-3.2# cvadmin
Xsan Administrator
Enter command(s)
For command help, enter "help" or "?".
List FSS
File System Services (* indicates service is in control of FS):
1>*2K[0]                located on big.local:64844 (pid 5217)
Select FSM "2K"
Created           :          Wed Oct 2 23:59:20 2013
Active Connections:          0
Fs Block Size     :          16K
Msg Buffer Size   :          4K
Disk Devices      :          5
Stripe Groups     :          3
Fs Blocks         :          5784860352 (86.20 TB)
Fs Blocks Free    :          3665561306 (54.62 TB) (63%)
Xsanadmin (2K) > show
Show stripe groups (File System "2K")
Stripe Group 0 [MetadataAndJournal] Status:Up,MetaData,Journal,Exclusive
Total Blocks:122088432 (1.82 TB) Reserved:0 (0.00 B) Free:121753961 (1.81 TB) (99%)
MultiPath Method:Rotate
    Primary Stripe [MetadataAndJournal] Read:Enabled Write:Enabled
Stripe Group 1 [Video] Status:Up
Total Blocks:1953495904 (29.11 TB) Reserved:270720 (4.13 GB) Free:129179 (1.97 GB) (0%)
MultiPath Method:Rotate
    Primary Stripe [Video] Read:Enabled Write:Enabled
Stripe Group 2 [Data] Status:Up
Total Blocks:3831364448 (57.09 TB) Reserved:270720 (4.13 GB) Free:3665432127 (54.62 TB) (95%)
MultiPath Method:Rotate
    Primary Stripe [Data] Read:Enabled Write:Enabled
I checked the availability of LUNs on MDC and client, there also all right.
But, unfortunately, the Volume is not mounted
xsanctl mount 2K
mount command failed: Unable to mount volume `2K' (error code: 5)
Please help me to figure out this situation, I will be grateful for any information.
Thanks

That looks like an I/O error. You may have an issue with one or more of the data LUNs. Check the system log for errors.

Can't mount 3rd party DAS storage and Xsan volume simutaneously

Xsan client(MacPro) equipped an Apple FC HBA card can't mount SGI TP9300 DAS storage and Xsan volume simutaneously when powering on or restarting.
Among 2 FC ports, one port is used for Xsan volume using Xserve RAID, and the other port is used for SGI TP9300 storage which is directly connected to that Mac.
When booting, Xsan volume is always mounted normally, but SGI TP9300 volume is not.
Sometimes TP9300 volume is mounted about 20~30 minutes later.(I attached system.log file)
The LUN of TP9300 is seen at Disk Utility, so it's not physical problem.
It seems that actual volume information is not correctly processed at booting time.
While, after booting the system with the FC cable for TP9300 disconnected and confirming that Xsan volume mounted normally, then connecting the FC cable for TP9300, the TP9300 volume is mounted immediately.
Mac OS X 10.4.8, Xsan 1.4 is being used.

Yes, I think you screwed your xsan volume. You can not remove luns from pools, and you can not remove volumes from volumes.
How important is your existing data? In your case I would concentrate on that. This is not trivial. Theorotically you have lost your data allready. In practise you might have luck.
Once I was in your kind of twilight zone, and managed to keep the data. It is a complete cli job. You have to be very carefull about with your config files. You could hire an experienced xsan consultant. If that is not possible, read the manpages very carefully before doing anything on the volume.
Regards
Donald

Volumes not mounting

I've got two xserver XSAN controllers, one XRAID array,
and an emulex FC switch. The servers, xraid, and FC switch
are connected on a private ethernet network, 192.168.1.x.
I'm trying to get the volumes defined in the SAN mounted on
both servers. The SAN volumes mount on one server but not
the other. I'm running 10.4 and the just recently released
XSAN version.
On xserver 1 the SAN is visible (via SAN admin) and the volumes mount on the desktop. Everything is happy.
On xserver 2 I can see the san, and both servers show
up in the clients/participants list. I can see the volumes defined
in the SAN listed in the SAN components window. However
I can't mount the volumes defined in the SAN. Both the xservers
are defined as controllers, with xserver 2 defined as the medium
priority failover.
I'm seeing these error messages in /var/log/system.log ("Video" and "Outside" are the volume names) on xserver 2:
Nov 15 23:19:17 faster fsmpm[336]: PortMapper: Rescanning for available CVFS volumes.
Nov 15 23:19:17 faster fsmpm[336]: PortMapper: QUEUEING RESTART of FSS service 'Outside[1]' on host 192.168.1.17.
Nov 15 23:19:19 faster kernel[0]: Can not get FSM address for filesystem 'Outside'
Nov 15 23:19:27 faster fsmpm[336]: PortMapper: RESTART FSS service 'Outside[1]' on host 192.168.1.17.
Nov 15 23:19:27 faster fsmpm[336]: PortMapper: Starting FSS service 'Outside[1]' on host 192.168.1.17.
Nov 15 23:19:27 faster fsmpm[336]: PortMapper: FSS 'Outside'[1] (pid 428) at 192.168.1.17:49215 is registered.
Nov 15 23:23:13 faster servermgrd: xsan: [46/133F290] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "Video" on 192.168.1.17 is on standby.
Nov 15 23:23:13 faster fsmpm[336]: PortMapper: Initiating activation vote for FSS 'Video'.
Nov 15 23:23:17 faster fsmpm[336]: PortMapper: FSS 'Video' disconnected.
Nov 15 23:23:17 faster KernelEventAgent[43]: tid 00000000 received VQ_NOTRESP event (1)
Nov 15 23:23:17 faster fsmpm[336]: PortMapper: Rescanning for available CVFS volumes.
Nov 15 23:23:17 faster kernel[0]: No FSS registered with PortMapper on host 192.168.1.17, retrying...
Nov 15 23:23:17 faster fsmpm[336]: PortMapper: QUEUEING RESTART of FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:27 faster fsmpm[336]: PortMapper: RESTART FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:27 faster fsmpm[336]: PortMapper: Starting FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:28 faster fsmpm[336]: PortMapper: FSS 'Video'[1] (pid 450) at 192.168.1.17:49266 is registered.
Nov 15 23:23:28 faster fsmpm[336]: PortMapper: Initiating activation vote for FSS 'Video'.
Nov 15 23:23:30 faster fsmpm[336]: PortMapper: Initiating activation vote for FSS 'Video'.
Nov 15 23:23:36 faster kernel[0]: Could not mount filesystem Video, cvfs error ' Timeout' (25)
Nov 15 23:23:37 faster fsmpm[336]: PortMapper: FSS 'Video' disconnected.
Nov 15 23:23:37 faster fsmpm[336]: PortMapper: Rescanning for available CVFS volumes.
Nov 15 23:23:37 faster fsmpm[336]: PortMapper: QUEUEING RESTART of FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:39 faster kernel[0]: Can not get FSM address for filesystem 'Video'
Nov 15 23:23:47 faster fsmpm[336]: PortMapper: RESTART FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:47 faster fsmpm[336]: PortMapper: Starting FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:47 faster fsmpm[336]: PortMapper: FSS 'Video'[1] (pid 452) at 192.168.1.17:49271 is registered.
Any ideas? Shouldn't I be seeing other messages attempting contact with the other controller?

I'm not sure about your emulex FC switch, because I use Qlogic, but for the rest of it, I know I can comment.
In my previous attempts to make volumes mount I found it was usually due to either bad DNS (improper name of machine) and/or bad network connection (metadata network connections not working either due to bad cable, or bad NIC or bad switch port).
Check the name of the machine, whether it resolves properly, and also check your IP networks (if you're using two, or just metadata).
I hope that helps.
-x

Xsan2.2 client cannot mount StorNext3.5.2 volume

Hello,
On an OSX 10.6.4 system , I am trying to mount a Stornext3.5.2 filesystem, whose MDC is a Linux system.
On the MAC I can see all the LUNs,
I can somehow see the fylesystem:
+sh-3.2# xsanctl list+
+snfs01 - not mounted+
I cannot mount it:
+sh-3.2# xsanctl mount snfs01+
+mount command failed: Unable to mount volume `snfs01' (error code: 5)+
I would like to know what +error code: 5+ means, and whether anybody can help me in mounting the filesystem.

Apple's XSAN enterprise support claims error code 5 is proprietary.
Quite frustrating.
From our experience with the same set up (RHEL MDCs running Storenext 3.5.x) typically error code 5 on clients after an xsanctl mount command means: reboot the computer and try again.. the computer will automount the san volume(s) 60% of the time.
mcacciagrano- have you had any success deciphering what error code 5 is actually a complaint about?
It is not a unique serial number issue (verified through the system's config.plist).
It's not a fibre issue (we can see the LUNs)
It's NOT a ghosted mount point folder issue (from early xsan days)
It IS a (VERY COSTLY) annoyance, that's for sure.

Client will not mount SAN after upgrade to 10.4.8 Server

Living life on the bleeding edge, I loaded the 10.4.8 Server upgrade onto my G4 Xserve which is the MDC for my single Xraid SAN. The SAN started without a hitch, however, the volume would not mount on the client side. The MDC shows up in the client list and the mount buttons are active, but the SAN will not mount. The system log yields the following error:
Can not mount filesystem, cvfs error 'Invalid argument' (0xb) while initializing local portmapper
I checked the obvioius: /volume is clear of old links, running cvfsck showed no problems, and cvadmin stat looks ok and who shows the MDC as FSM and ADM.
Has anybody else run into this? Any observations would be welcomed!
Thanks,
babcom

As indicated on the tag line, Xsan 1.4. Upgrade from OS 10.4.7. SAN created using version 1.4. SAN mounted just fine under 10.4.7. In an attempt to isolate the problem, I tried mounting the SAN from the command line:
mount -t acfs iplVol1.cfg /Volumes
only to received the same invalid argument error. I suspect that a parameter name has been changed/deleted/munged when parsing the volume's cfg file. Since Apple did NOT reference the invalid string token in the error message, I can not be sure. I am just now getting back to work the issue.
Regards,
babcom

Oddball client not mounting XSan Volumes

Similar Messages

Maybe you are looking for