Gerard's picture

Xsan 2.2 Permissions Issue

16Tb Xsan
Xsan 2.2
Two fiber attached stations
Non fiber users connecting via nfs auto-mount
2 MDCs
Using ACL to set permissions.

Experiencing permission issues when users create, read, write files. It is very sporadic of a case. Some users will be able to read/write
files/folders & there are some who cannot with the same files/folders.

For example:
One user will create a folder and add in content, but others users will have trouble accessing the data.

Propagating permissions, via Xsan Admin, usually fixes the issues, but it doesn't resolve the issue of why this is happening.

kjaer.casper's picture

Promise X30 issue - Command times out on 10 disk

Forums: 

Hi all.

I get theese errors on my X30 48TB raid , 10 disks makes command time out at same time, all 10 disk, in that raid6 is controlled by controller 2. Promise has sent me a new controller, and i have installed it, but the command times out is still here.

When i changes all traffic to controller 1, i dont see the issue. I have now received a new chassis from Promise, that we are gonna try.

The command time out, makes XSAN crash totally, finder is not responding on all machines, including metadata controllers. Which is normal i guess , if XSAN is loosing a LUN.

Any suggestions???

THX!!

Error log from NVRAM events.

417PD 240x000D0003InfoNov 4, 2012 21:51:09Physical Disk has been reset416PD 240x000D0011MinorNov 4,
2012 21:51:09Command times out on physical disk415PD 230x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset414PD 230x000D0011MinorNov 4,
2012 21:51:09Command times out on physical disk413PD 200x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset412PD 200x000D0011MinorNov 4,
2012 21:51:09Command times out on physical disk411PD 190x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset410PD 190x000D0011MinorNov 4,
2012 21:51:09Command times out on physical disk409PD 160x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset408PD 160x000D0011MinorNov 4, 2012 21:51:09Command times out on physical disk407PD 120x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset406PD 120x000D0011MinorNov 4, 2012 21:51:09Command times out on physical disk405PD 110x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset404PD 110x000D0011MinorNov 4, 2012 21:51:09Command times out on physical disk403PD 80x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset402PD 80x000D0011MinorNov 4, 2012 21:51:09Command times out on physical disk401PD 70x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset400PD 70x000D0011MinorNov 4, 2012 21:51:09Command times out on physical disk399PD 40x000D0003InfoNov 4,
2012 21:51:09Physical Disk has been reset398PD 40x000D0011MinorNov 4, 2012 21:51:09Command times out on physical disk397PD 150x000D0003InfoNov 4,
2012 21:07:14Physical Disk has been reset396PD 150x000D0011MinorNov 4, 2012 21:07:14Command times out on physical disk

morphenine's picture

Premiere Pro CS6 Permissions

We're evaluating moving to Premiere Pro CS6 from FCP7. We ran into a problem and I'm wondering if anyone else has hit this wall...

Basically if edit station A saves a project, then edit station B can open and manipulate the project but cannot save it unless he is the POSIX owner of the file. Premiere Pro doesn't seem to respect Group or Other permissions, nor the ACLs.

Thoughts?
Going to reach out to Adobe tomorrow.

xsanguy's picture

ACLs are busted - force some clients to mount a volume RO?

ACLs aren't working on a fairly large production XSan. The auto-complete in group-name when adding an ACL takes 20+ hours (!) This is a large system, a couple Petabytes and millions of files.

There are 5 Volumes, we would like to mount 2 of them RO on some of the client machines, the rest RW.

Is there a way to force certain clients to mount RO?

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

Pages

Subscribe to Xsanity RSS