[LU-642] LBUG in client when activating an OST which was registered as initially inactive

• Type: Bug
• Resolution: Low Priority
• Priority: Minor
• Fix Version/s: Lustre 2.4.0
• Affects Version/s: Lustre 2.1.0
• Labels: ptr
• Severity: 3
• Assignee: Zhenyu Xu
• Reporter: John Spray (Inactive)

Description

What we're trying to accomplish is to have an OST be inactive when it's first registered, by tunefs'ing the osc.active setting on the OST before we first mount it. I'm seeing that when I activate an OST which was initially inactive, I hit an LBUG on client trying to write to it.

The config is MGS+MDT+OST0+OST1. Tried with all on one host, and with OSTs+client on different hosts, same effect.
Steps to reproduce:
1. Format all targets
2. On one of the OSTs, run tunefs.lustre --param osc.active=0
3. Start all targets (one of the OSTs is initially activated, the other initially deactivated)
4. Mount the filesystem
5. Create some files on the client mount
6. Run lctl conf_param OSTxxxx.osc.active=1 on the MGS
7. Create some more files on the client mount (some of them should be written to the newly activated OST)
-> LBUG on the client

Using lustre-2.1.0-2.6.18_238.19.1.el5_lustre.g65156ed_gf426fb9 + other packages from the same build on CentOS5.

Logs etc to follow.

Issue Links

• is related to: LU-4302 If a client mounts FS with conf_param active=0 OST, it will not be able to activate it later
• is related to: LU-1459 Disabling OSC in file system causes multiple issues