User Functions
Don't have an account yet? Sign up as a New User
Who's Online
Guest Users: 15
|
| View previous topic :: View next topic |
| Author |
Message |
kawika RAID 5

Joined: 17 Sep 2009 Posts: 16
|
Posted: Thu Sep 17, 2009 2:39 pm Post subject: XSan 1.4.2 - Clients not mounting |
|
|
First, since this is my first post, let me give a little background about my self and my situation. I work in the (post)production department of the local cable company. All of our edit bays are running FCP6, and XSan 1.4.2. We have 2 Xserves to act as MDCs, with 3 XRaids for our storage pool.
I admin all of this, but when I say admin, I mean I set it up roughly 2 years ago, and it runs pretty well by itself, so I don't touch it. Well, yesterday, we decided to add an additional edit bay to the SAN, and now, not only does that machine not show up at all in Xsan, none of the clients or the MDC will mount the SAN volume.
I didn't touch anything in XSan admin, I simply connected the new machine up to the VLAN, and connected the Fiber Cables to both the router and the back of the new machine. I'm not sure how, or why, but nothing seems to work anymore. Here's the system log from the main MDC:
| Code: |
n: [482/349EB0] ERROR: get_remote_properties(SanDrive): HTTP_REQUEST_FAILED: https://172.20.105.55:311/commands/servermgr_nomadvol: authorization required
Sep 17 09:11:08 x1 servermgrd: xsan: [482/349EB0] ERROR: get_remote_properties(SanDrive): Failed revoking lN81DWth64FUHUb5YjdmskL2jbz-admin for 172.20.105.55
Sep 17 09:11:33 x1 servermgrd: xsan: [482/3DD1B0] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:11:33 x1 servermgrd: xsan: [482/3DD1B0] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:11:33 x1 servermgrd: xsan: [482/303220] ERROR: get_fsm_process_stats(SanDrive): Unable to find pid of fsm
Sep 17 09:11:33 x1 servermgrd: xsan: [482/303220] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:11:48 x1 servermgrd: xsan: [482/3E2110] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:11:48 x1 servermgrd: xsan: [482/3AD090] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:11:48 x1 servermgrd: xsan: [482/1437100] ERROR: get_remote_properties(SanDrive): HTTP_REQUEST_FAILED: https://172.20.105.55:311/commands/servermgr_nomadvol: authorization required
Sep 17 09:11:48 x1 servermgrd: xsan: [482/3AD090] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:11:48 x1 servermgrd: xsan: [482/3AD090] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:12:23 x1 servermgrd: xsan: [482/303220] ERROR: get_fsm_process_stats(SanDrive): Unable to find pid of fsm
Sep 17 09:12:48 x1 servermgrd: xsan: [482/303220] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:12:48 x1 servermgrd: xsan: [482/3D3550] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:12:48 x1 servermgrd: xsan: [482/3F4880] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:12:48 x1 servermgrd: xsan: [482/140C6C0] ERROR: get_remote_properties(SanDrive): HTTP_REQUEST_FAILED: https://172.20.105.55:311/commands/servermgr_nomadvol: authorization required
Sep 17 09:12:48 x1 servermgrd: xsan: [482/140C6C0] ERROR: get_remote_properties(SanDrive): Failed revoking lN81DWth64FUHUb5YjdmskL2jbz-admin for 172.20.105.55
Sep 17 09:12:48 x1 servermgrd: xsan: [482/3BC650] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:12:48 x1 servermgrd: xsan: [482/3BC650] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:12:49 x1 servermgrd: xsan: [482/3BC650] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:12:49 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:12:49 x1 servermgrd: xsan: [482/1416160] ERROR: get_remote_properties(SanDrive): HTTP_REQUEST_FAILED: https://172.20.105.55:311/commands/servermgr_nomadvol: authorization required
Sep 17 09:12:49 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:12:49 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:13:00 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:13:00 x1 servermgrd: xsan: [482/3C70D0] ERROR: set_computers_properties(SanDrive): No client list for volume
Sep 17 09:13:23 x1 servermgrd: xsan: [482/303220] ERROR: get_fsm_process_stats(SanDrive): Unable to find pid of fsm
Sep 17 09:13:48 x1 servermgrd: xsan: [482/303220] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:13:49 x1 servermgrd: xsan: [482/142F190] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:13:49 x1 servermgrd: xsan: [482/144BF10] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:13:49 x1 servermgrd: xsan: [482/142F190] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:13:49 x1 servermgrd: xsan: [482/142F190] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:14:00 x1 servermgrd: xsan: [482/142F190] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:14:00 x1 servermgrd: xsan: [482/35FAA0] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:14:02 x1 servermgrd: [482] ServerManager _SMSocketRead(fd=24) timed out (count=-1,remaining=5)\n
Sep 17 09:14:02 x1 servermgrd: [482] ServerManager SSLRead/_SMSocketRead(172.20.105.55:fd=24) failed with -36 (errno=35)\n
Sep 17 09:14:23 x1 servermgrd: xsan: [482/303220] ERROR: get_fsm_process_stats(SanDrive): Unable to find pid of fsm
Sep 17 09:14:48 x1 servermgrd: xsan: [482/303220] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:14:48 x1 servermgrd: xsan: [482/1458F90] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:14:48 x1 servermgrd: xsan: [482/1458F90] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:14:49 x1 servermgrd: xsan: [482/147D3C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:14:49 x1 servermgrd: xsan: [482/3AB9B0] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:14:50 x1 servermgrd: xsan: [482/147D3C0] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:14:50 x1 servermgrd: xsan: [482/147D3C0] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:15:03 x1 servermgrd: [482] ServerManager _SMSocketRead(fd=22) timed out (count=-1,remaining=5)\n
Sep 17 09:15:03 x1 servermgrd: [482] ServerManager SSLRead/_SMSocketRead(172.20.105.55:fd=22) failed with -36 (errno=35)\n
Sep 17 09:15:23 x1 servermgrd: xsan: [482/303220] ERROR: get_fsm_process_stats(SanDrive): Unable to find pid of fsm
Sep 17 09:15:48 x1 servermgrd: xsan: [482/303220] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:15:48 x1 servermgrd: xsan: [482/3E0300] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:15:48 x1 servermgrd: xsan: [482/14566A0] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:15:48 x1 servermgrd: xsan: [482/14566A0] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:16:03 x1 servermgrd: [482] ServerManager _SMSocketRead(fd=22) timed out (count=-1,remaining=5)\n
Sep 17 09:16:03 x1 servermgrd: [482] ServerManager SSLRead/_SMSocketRead(172.20.105.55:fd=22) failed with -36 (errno=35)\n
Sep 17 09:16:04 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:16:04 x1 servermgrd: xsan: [482/3C70D0] ERROR: set_computers_properties(SanDrive): No client list for volume
Sep 17 09:16:23 x1 servermgrd: xsan: [482/303220] ERROR: get_fsm_process_stats(SanDrive): Unable to find pid of fsm
Sep 17 09:16:48 x1 servermgrd: xsan: [482/303220] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:16:49 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:16:49 x1 servermgrd: xsan: [482/3DD120] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:16:49 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:16:49 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_computer_properties(SanDrive): No client list for volume
Sep 17 09:17:04 x1 servermgrd: xsan: [482/3C70D0] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:17:04 x1 servermgrd: xsan: [482/3BE3B0] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:17:23 x1 servermgrd: xsan: [482/303220] ERROR: get_fsm_process_stats(SanDrive): Unable to find pid of fsm
Sep 17 09:17:48 x1 servermgrd: xsan: [482/303220] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:17:49 x1 servermgrd: xsan: [482/3D3F80] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:17:49 x1 servermgrd: xsan: [482/3BC3C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because The Xsan File System Services may be stopped.
Sep 17 09:17:50 x1 servermgrd: xsan: [482/3BC3C0] ERROR: get_clients_for_fsmvol_named(SanDrive): Could not connect: The Xsan File System Services may be stopped.
Sep 17 09:17:50 x1 servermgrd: xsan: [482/3BC3C0] ERROR: get_computer_properties(SanDrive): No client list for volume
|
Any insight is greatly appreciated. |
|
| Back to top |
|
 |
matx Xsan Master

Joined: 15 Apr 2005 Posts: 378
|
Posted: Thu Sep 17, 2009 3:41 pm Post subject: |
|
|
So magically, without touching anything, it went POOF?! Hmmmm
Please review the basics, does this new machine:
- have the version of the OS that the others are all running (you didn't say 10.4 or 10.5) ?
- have an entry in DNS for both Xsan and data networks?
- in the same zone on the fiber switch
- same or different hardware from other edit bays?
And now for the controller....
- did you back up the config or run cvgather (before, after or during?)
- are the controllers the same OS, xsan version, hardware type, etc ?
And finally,
- Is your data backed up? |
|
| Back to top |
|
 |
kawika RAID 5

Joined: 17 Sep 2009 Posts: 16
|
Posted: Thu Sep 17, 2009 3:50 pm Post subject: |
|
|
Thanks for the quick reply.
The only thing I did was to restart each MDC, but that was after the SAN stopped responding on the client machines.
The new machine is running 10.5, everything else is running 10.4, however, I haven't even installed Xsan on the new machine yet, which is why I don't understand how it's effecting the setup. For the time being, I've disconnected the new machine from both the fiber and ethernet networks.
As for the controller, I've never run that command. Both controllers are running 10.4.11, Xsan 1.4.2, with mirrored hardware configurations.
The only "back-up" is the raid's configuration (RAID1). |
|
| Back to top |
|
 |
kawika RAID 5

Joined: 17 Sep 2009 Posts: 16
|
Posted: Thu Sep 17, 2009 3:53 pm Post subject: |
|
|
Also, when attempting to connect via cvadmin, I get a timeout response...
Command:
| Code: | | sudo cvadmin SanDrive -e stat |
Result:
| Code: | Connect to FSM failed - Operation timed out
Cannot select FSS "SanDrive" |
Not sure what that implies. |
|
| Back to top |
|
 |
kawika RAID 5

Joined: 17 Sep 2009 Posts: 16
|
Posted: Thu Sep 17, 2009 5:11 pm Post subject: |
|
|
| Another FYI (still not mounting), the LUNs show up in Disk Utility for both MDCs & all Clients. |
|
| Back to top |
|
 |
kawika RAID 5

Joined: 17 Sep 2009 Posts: 16
|
Posted: Thu Sep 17, 2009 6:05 pm Post subject: |
|
|
| After a simply restart of the XSan, all except one of the clients are mounting. Not sure what's causing this particular client to misbehave... |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|