Thawk9455's picture

Meta Data Lun Suggestions

I'm curious what others see as typical I/0s per second and what benefits we could expect from possible changes to our metadata luns. We are using our Xsan as general file server storage so there is a wide array of data types from large numbers of small files all the way up to 200+GB files depending on the user. We're currently using about 80 TB of storage and recently have started seeing much slower overall performance when accessing the file server.

According to the Promise Performance Monitoring our Meta Data Lun is regularly in the 200-300 I/Os per second.

We are on our original setup, with two 750 GB SATA drives mirrored and are considering a few options but don't have the money to evaluate all of them individually so I'm hoping others that have worked with these configurations can provide some guidance.

1. We're curious if anyone has replaced their metadata drives with SSDs. I'm assuming this would provide a significant performance increase but also not sure what drives would work with the Promise E610s (Apple version) and offer the reliability we obviously would want for this type of system.

2. Replace the SATA drives with higher speed SAS drives. I know we can get 1 TB 10K SAS drives that could just be swapped out with the spare and migrated one at a time. How much of a boost could we really expect from a slightly faster drive?

3. Try to beg and plead our way into getting a new x30 and migrate the metadata drives to a RAID 10 configuration with more drives involved. Seems like kind a waste to burn up drives but if it will significantly improve overall read/write performance it could be worth it.

Thoughts? Suggestions? Are we missing something simple?

dshott's picture

Replacement Apple Xraid Drives

Forums: 

Hi, I was wondering if anyone has any suggestions on a place to buy replacement drives (750GB) for the old Apple Xraids? Thanks!

aaron's picture

Xsanity is Back!

As you guessed, the hurricane knocked out our multiply-redundant data center. (OK, it's really an Xserve G4. But it used to be awesome.)

The power is back on 23rd Street. Thanks to Con Edison for working so hard, and to all the Tekserve employees for working by candlelight for these last few days. The energy poured into perseverance has been very impressive, but it's good to have light!

Kasper Winding's picture

Qnap NAS + Atto Xtend issci software + Xsan 3.0 problems

Hi all

I got a problem with Qnap NAS + Atto Xtend software iscsi + Xsan 3.0

The issue is that the Qnab NAS (TS-879U RP) with firmware 3.7 is not showning the serial numbers on the HDD's. And that causes Xsan to not being able to detect multiple LUN's. Actually looks like Xsan detects them randomly and always one at a time.

Is there any firmware addons, 3. part etc. that can solve this HUGE problem?.

Best Regards
Kasper Winding

cinedigital's picture

Metadata LUN Setup

Forums: 

I am looking at setting up a Lion XSan 2.3 from scratch using:

2009 XServe MDC
2006 XServe Backup MDC
2x Infortrend S12F-G1840 12 drive 8Gb FC RAID (working at 4Gb)
QLogic 5600 4Gb FC switch 16 port

I also have an additional 2Gb FC Infortrend A16F-G2221 RAID

If I used this for the Metadata LUN with a dual FC link to the 4Gb switch would SAN performance be OK?

Metadata latency should still be low with this setup I think

Anyone tried anything similar ?

TIA
Dave

gregregreg's picture

Client dropped just one of it's 4 xsan volumes

I jhave a client that has dropped one of it's volumes and won't remount. Strange thing is that it has remounted it's other 3 volumes which share dns and MDC servers with the unmounted volume. It client is appearing as unreachable in xsan admin. This began with a client move between edit suites. MD and Public networks are pingable from the MDC and all other clients are mounting the volume as per usual. The log from the time of the incident is below. I really hope someone can help as I've not worked with Xsan for a while and having a baptism of fire here.

Obviously the stripe group down message loop that starts at the end of this log has been repeating ever since.

Cheers folks.

Oct 24 12:04:34 xsan-mdback fsmpm[1265]: NSS: Member 192.168.3.146 (id 192.168.3.146) coordinator list mismatch
Oct 24 12:05:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:06:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:07:13 xsan-mdback fsmpm[1265]: NSS: Member 192.168.3.146 (id 10.91.11.146) coordinator list mismatch
Oct 24 12:08:02 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:08:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:09:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:10:36 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:23:23 xsan-mdback mDNSResponder[35]: PenaltyTimeForServer: PenaltyTime negative -19184, (server penaltyTime 84534773, timenow 84553957) resetting the penalty
Oct 24 12:32:03 xsan-mdback servermgrd[47704]: -[AccountsRequestHandler(AccountsOpenDirectoryHelpers) openLocalLDAPNodeIfNeeded]: dsLocalLDAP = (null), error = Error Domain=com.apple.OpenDirectory Code=2000 UserInfo=0x102860660 "Unable to open Directory node with name /LDAPv3/127.0.0.1."
Oct 24 12:45:01 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': SNFS Client '192.168.3.142' (192.168.3.142) disconnected unexpectedly from file system 'SAN_02', reason: client socket shut down
Oct 24 12:45:01 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': SNFS Client '192.168.3.142' (192.168.3.142) disconnected unexpectedly from file system 'SAN_03', reason: client socket shut down
Oct 24 12:47:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:48:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:49:48 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:58:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 12:59:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:00:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:00:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:01:04 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:02:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:03:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:03:44 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:04:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:05:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:05:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:06:04 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:07:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:07:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:07:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (192.168.3.141) - error 22 (Invalid argument).
Oct 24 13:07:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:07:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (192.168.3.141) - error 22 (Invalid argument).
Oct 24 13:07:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:07:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:07:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:07:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:08:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:08:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:08:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:08:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:08:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:08:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:08:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:08:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:08:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:08:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:09:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:09:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:09:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:09:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:09:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:09:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:09:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:09:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:09:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:10:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:10:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:10:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:10:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:10:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:10:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:10:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:10:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:10:49 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:11:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:11:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:12:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:13:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:14:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:14:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:15:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:16:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:16:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:17:01 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': SNFS Client '???' (192.168.3.141) disconnected unexpectedly from file system 'SAN_03', reason: client socket shut down
Oct 24 13:17:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:18:04 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:18:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:19:04 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:20:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:21:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:21:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:22:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:23:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:23:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:24:04 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:25:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:26:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:26:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:27:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:28:03 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:28:33 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:29:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:30:04 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:30:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:31:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:32:04 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:32:34 xsan-mdback servermgrd[47704]: xsan: [47704/2112C0] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:32:48 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:32:48 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:32:48 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:32:48 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:32:48 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:32:48 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:32:48 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:32:48 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:04 xsan-mdback servermgrd[47704]: xsan: [47704/297D10] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Receive Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': setsockopt returned error/22 - Invalid argument.
Oct 24 13:33:18 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': Send Socket Buffer configuration failed for client (::) - error 22 (Invalid argument).
Oct 24 13:33:34 xsan-mdback servermgrd[47704]: xsan: [47704/7D8F560] ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out
Oct 24 13:34:02 xsan-mdback fsm[1270]: Xsan FSS 'SAN_02[1]': SNFS Client '???' (192.168.3.142) disconnected unexpectedly from file system 'SAN_02', reason: client socket shut down
Oct 24 13:35:16: --- last message repeated 1 time ---
Oct 24 13:35:16 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 96] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:35:21 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 102] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:35:35 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 107] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:35:50 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 111] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:36:05 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 114] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:36:20 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 122] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:36:35 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 123] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:36:50 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 124] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:37:05 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 127] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:37:20 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 130] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:37:35 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 131] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:37:50 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 132] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:38:05 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 136] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1
Oct 24 13:38:20 xsan-mdback fsm[5136]: Xsan FSS 'SAN_03[1]': [Node 5] Disk Stripe Group 1 is DOWN for this client. # disks 5 unitmap[1] 0xfffff partaccess 0x1

cass5064's picture

Xsan to StorNext WebEx

Quantum StorNext is hosting its first Xsan to StorNext Conversion WebEx on October 31 at 11am Pacific. The link is pasted below. There will be valuable information on the benefits of converting to StorNext as well as new special conversion offers.

http://quantum.mv.treehousei.com/Surveys/57/E79541B28D51D0BE/25725_OFT.aspx

gregregreg's picture

Problems with snmp on osx 10.6

Hi,

I'm having some issues while trying to add my metadata controllers (running on snow leopard) to a snmp monitoring system. I'm using solarwinds simply as a health monitor tool.

I have configured 4 servers which are responding as I would expect, but with seemingly identical configs another 2 are refusing to report correctly.

my snmpd.config files are very simple, with a rocommunity string of public and location and contact info. That's it. However when I test this with a snmpwalk (shown below) instead of the reams of data I expect I just get the server admin contact and the end of MIB table message.

I feel a bit of a dunce failing at such a simple setup but any help would be appreciated. Obviously I've tried restarts to both the server and the snmp daemon (from command line and server admin)

My snmpd.conf file :

        1. ###########################################################################

#

  1. snmpd.conf

#

  1. - created by the snmpconf configuration program

#

        1. ###########################################################################
  1. SECTION: Access Control Setup

#

  1. This section defines who is allowed to talk to your running
  2. snmp agent.
  1. rocommunity: a SNMPv1/SNMPv2c read-only access community name
  2. arguments: community [default|hostname|network/bits] [oid]

rocommunity public

        1. ###########################################################################
  1. SECTION: System Information Setup

#

  1. This section defines some of the information reported in
  2. the "system" mib group in the mibII tree.
  1. syslocation: The [typically physical] location of the system.
  2. Note that setting this value here means that when trying to
  3. perform an snmp SET operation to the sysLocation.0 variable will make
  4. the agent return the "notWritable" error code. IE, including
  5. this token in the snmpd.conf file will disable write access to
  6. the variable.
  7. arguments: location_string

syslocation "B1_D15"

  1. syscontact: The contact information for the administrator
  2. Note that setting this value here means that when trying to
  3. perform an snmp SET operation to the sysContact.0 variable will make
  4. the agent return the "notWritable" error code. IE, including
  5. this token in the snmpd.conf file will disable write access to
  6. the variable.
  7. arguments: contact_string

syscontact blah.blahl@blahblah.com

and when I run a snmpwalk -c instead of getting tons of info I get this :

chskod02mp:snmp admin$ snmpwalk -c public localhostSNMPv2-MIB::sysContact.0 = STRING: blah.blah@blah.com

SNMPv2-MIB::sysContact.0 = No more variables left in this MIB View (It is past the end of the MIB tree)

xsanguy's picture

Explicit configuration label verify failed

new xSan setup - (this is on a client)

client$ sudo cvlabel -l
/dev/rdisk0 [ DC WD7500AACS-0 1.01A0] EFI Sectors: 1465130703. SectorSize: 512.
/dev/rdisk1 [ExternalRAID 0 ] APM Sectors: 3907031867. SectorSize: 512.
/dev/rdisk2 [APPLE Xserve RAID 1.51] acfs "500_ct2" Sectors: 5860554719. SectorSize: 512. Maximum sectors: 5860554719.
/dev/rdisk3 [APPLE Xserve RAID 1.51] acfs "500_ct1" Sectors: 5860554719. SectorSize: 512. Maximum sectors: 5860554719.
/dev/rdisk4 [APPLE Xserve RAID 1.51] acfs "750_ct1" Sectors: 7325644767. SectorSize: 512. Maximum sectors: 7325644767.
/dev/rdisk5 [APPLE Xserve RAID 1.51] acfs "750_ct2" Sectors: 7325644767. SectorSize: 512. Maximum sectors: 7325644767.
/dev/rdisk6 [APPLE Xserve RAID 1.51] acfs "metassd" Sectors: 62470111. SectorSize: 512. Maximum sectors: 62470111.
[b]cvlabel: Explicit configuration label verify failed for device /dev/rdisk7!
cvlabel: expected found !
/b/dev/rdisk7 [APPLE Xserve RAID 1.51] acfs "metassd" Sectors: 62470111. SectorSize: 512. Maximum sectors: 23442192351.[b] [Unusable: Expected label not found]
/b

Appears correctly on the MDC:

meta1:Volumes admin$ sudo cvlabel -l
Password:
/dev/rdisk5 [ T380013AS .05 ] EFI Sectors: 156283023. SectorSize: 512.
/dev/rdisk4 [APPLE Xserve RAID 1.51] acfs "metassd" Sectors: 62470111. SectorSize: 512. Maximum sectors: 62470111.
/dev/rdisk0 [APPLE Xserve RAID 1.51] acfs "500_ct2" Sectors: 5860554719. SectorSize: 512. Maximum sectors: 5860554719.
/dev/rdisk1 [APPLE Xserve RAID 1.51] acfs "500_ct1" Sectors: 5860554719. SectorSize: 512. Maximum sectors: 5860554719.
/dev/rdisk2 [APPLE Xserve RAID 1.51] acfs "750_ct1" Sectors: 7325644767. SectorSize: 512. Maximum sectors: 7325644767.
/dev/rdisk3 [APPLE Xserve RAID 1.51] acfs "750_ct2" Sectors: 7325644767. SectorSize: 512. Maximum sectors: 7325644767.

yoth's picture

alternatives?

So, I have a client that does video and podcast production with eight work stations connected to xsan 2.2 with everyone on snow leopard.

They are looking to move from final cut to premiere. from what i understand, there are some significant gains going to lion or mountain lion in regards to gpu acceleration in premiere if you have invidia cards. this will cause us to upgrade the xsan.

They would like to know what the other alternatives are to xsan and so they can decide whether to upgrade or jump ship.

What would you consider an alternative in a collaborative video production environment? 10 gig ethernet? But they lose shared file system. anything else you like?

Thanks.

Pages

Subscribe to Xsanity RSS