[LU-3544] Writing to new files under NFS export from Lustre will result in ENOENT (SLES11SP2)

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.6.0
• Affects Version/s: Lustre 2.4.0
• Labels: patch
• Severity: 3
• Assignee: Lai Siyao
• Reporter: Cheng Shao (Inactive)

Description

After resolving the issues in LU-3484 and LU-3486, the testing of exporting NFS over Lustre on SLES11SP2 continues and we hit yet another issue.

Creating and reading files works fine, but attempting to write to a new file resulted in an ENOENT coming back.
It's coming from here:

00000080:00000001:1.0:1372108818.561839:0:12348:0:(file.c:407:ll_intent_file_open()) Process leaving via out (rc=18446744073709551614 : -2 : 0xfffffffffffffffe)

Here's the line of code:

        if (it_disposition(itp, DISP_LOOKUP_NEG))
                 GOTO(out, rc = -ENOENT);

Looking through the DK logs, we noticed something strange. This is the intent open log message for the attempted write:

00800000:00000002:0.0:1372108818.561125:0:12348:0:(lmv_intent.c:198:lmv_intent_open()) OPEN_INTENT with fid1=[0x2000056c1:0x2:0x0], fid2=[0x2000056c1:0x4:0x0], name='/' -> mds #0

Except this write is to a file named something like 'myfile'. Specifically, "echo 5 > myfile".
Comparing this to the normal case, not exported over NFS, we see the name of the file here like I'd expect.

Issue Links

• is duplicated by: LU-3765 2.5.0<->2.1.5 interop: sanity test 24u: (mdt_handler.c:224:mdt_lock_pdo_init()) ASSERTION( namelen > 0 ) failed
• is related to: LU-5109 Failure on test suite parallel-scale-nfsv3 test_compilebench: IOError: [Errno 22] Invalid argument
• is related to: LU-5177 object leak in mdt_open_by_fid_lock()