Hello,

I wonder if anyone has seen this... I am (not) having fun with the 
rescan-scsi-bus.sh command especially with the -r switch. Even though there are 
no devices removed the script seems to interrupt currently working NSDs and 
these messages appear in the mmfs.logs:

2019-06-25_06:30:48.706+0100: [I] Connected to <IP> <node> <c0n0>
2019-06-25_06:30:48.764+0100: [E] Local access to <NSD> failed with EIO, 
switching to access the disk remotely.
2019-06-25_06:30:51.187+0100: [E] Local access to <NSD> failed with EIO, 
switching to access the disk remotely.
2019-06-25_06:30:51.188+0100: [E] Local access to <NSD> failed with EIO, 
switching to access the disk remotely.
2019-06-25_06:30:51.188+0100: [N] Connecting to <IP> <node> <c0n5>
2019-06-25_06:30:51.195+0100: [I] Connected to <IP> <node> <c0n5>
2019-06-25_06:30:59.857+0100: [N] Connecting to <IP> <node> <c0n4>
2019-06-25_06:30:59.863+0100: [I] Connected to <IP> <node> <c0n4>
2019-06-25_06:33:30.134+0100: [E] Local access to <NSD> failed with EIO, 
switching to access the disk remotely.
2019-06-25_06:33:30.151+0100: [E] Local access to <NSD> failed with EIO, 
switching to access the disk remotely.

These messages appear roughly at the same time each day and I've checked the 
NSDs via mmlsnsd and mmlsdisk commands and they are all 'ready' and 'up'. The 
multipaths to these NSDs are all fine too.

Is there a way of finding out what 'access' (local or remote) a particular node 
has to an NSD? And is there a command to force it to switch to local access - 
'mmnsdrediscover' returns nothing and run really fast (contrary to the 
statement 'This may take a while' when it runs)?

Any ideas appreciated!

Regards,
Son

Son V Truong - Senior Storage Administrator
Advanced Computing Research Centre
IT Services, University of Bristol
Email: [email protected]<mailto:[email protected]>
Tel: Mobile: +44 (0) 7732 257 232
Address: 31 Great George Street, Bristol, BS1 5QD

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Reply via email to