[LU-359] Confused error message after write failure

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.3.0, Lustre 1.8.9
• Affects Version/s: Lustre 2.3.0, Lustre 1.8.6
• Severity: 3
• Assignee: nasf (Inactive)
• Reporter: nasf (Inactive)

Description

The issues were found in sanity-quota test. When application writes failed for out of quota (-EDQUOT), it will close the file and exit. But the close returns "-EIO" related with former write failure, like that:

===============
running as uid/gid/euid/egid 60000/60000/60000/60000, groups:
[dd] [if=/dev/zero] [of=/mnt/lustre/d0.sanity-quota/d1/f1-1] [bs=1024] [count=9410] [seek=9410]
dd: writing `/mnt/lustre/d0.sanity-quota/d1/f1-1': Disk quota exceeded
dd: closing output file `/mnt/lustre/d0.sanity-quota/d1/f1-1': Input/output error
running as uid/gid/euid/egid 60000/60000/60000/60000, groups:
[dd] [if=/dev/zero] [of=/mnt/lustre/d0.sanity-quota/d1/f1-1] [bs=1024] [count=1024] [seek=18821]
dd: writing `/mnt/lustre/d0.sanity-quota/d1/f1-1': Disk quota exceeded
dd: closing output file `/mnt/lustre/d0.sanity-quota/d1/f1-1': Input/output error
0
===============

The message of "dd: closing output file `/mnt/lustre/d0.sanity-quota/d1/f1-1': Input/output error" is confused, which is quite different from "dd" against local FS output. The expected output should be:

===============
running as uid/gid/euid/egid 60000/60000/60000/60000, groups:
[dd] [if=/dev/zero] [of=/mnt/lustre/d0.sanity-quota/d1/f1-0] [bs=1024] [count=14631] [seek=14631]
dd: writing `/mnt/lustre/d0.sanity-quota/d1/f1-0': Disk quota exceeded
13182+0 records in
13181+0 records out
13497344 bytes (13 MB) copied, 0.999215 seconds, 13.5 MB/s
running as uid/gid/euid/egid 60000/60000/60000/60000, groups:
[dd] [if=/dev/zero] [of=/mnt/lustre/d0.sanity-quota/d1/f1-0] [bs=1024] [count=1024] [seek=29262]
dd: writing `/mnt/lustre/d0.sanity-quota/d1/f1-0': Disk quota exceeded
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00409484 seconds, 0.0 kB/s
0
===============

Issue Links

• Trackbacks: Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA