[LU-1253] obd_set_info_async: dev 0 no operation

• Type: Bug
• Resolution: Won't Fix
• Priority: Minor
• Affects Version/s: Lustre 2.1.0
• Labels: llnl
• Environment: Lustre 1.8 and 2.1 clients, servers are lustre 2.1.0-24chaos
• Severity: 3
• Assignee: Hongchao Zhang
• Reporter: Christopher Morrone (Inactive)

Description

Our admins are expanding a 2.1 filesystem with new OSTs. Because of known-and-never-solved issues in 1.8 that made adding OSTs in non-sequential order problematic (break out your hexeditor to fix), the admins are adding the new OSTs one at a time in sequential order.

Each addition causes the MGS lock to be revoked from all clients, which causes an MGS reconnect storm. When this happens we see the following:

2012-03-22 15:37:11 Lustre: MGS: Client 1aea7ac4-5b27-3e30-3c57-467cd6aed36f (at 192.168.120.118@o2ib7) reconnecting
2012-03-22 15:37:11 Lustre: Skipped 995 previous similar messages
2012-03-22 15:37:11 LustreError: 12649:0:(obd_class.h:501:obd_set_info_async()) obd_set_info_async: dev 0 no operation
2012-03-22 15:37:11 LustreError: 12649:0:(obd_class.h:501:obd_set_info_async()) Skipped 861 previous similar messages

I assume that the call to obd_set_info_async() is the one in target_handle_connect().

Device 0 is the MGS device.