[LU-17345] Interop conf-sanity test_116: FAIL: mkfs temporary xfs image Created: 08/Dec/23 Updated: 09/Dec/23 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.15.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/f5431cc6-90d2-4ce0-8ef6-209ce8abaf31 test_116 failed with the following error: mkfs temporary xfs image Test session details: <<Please provide additional information about the failure here>> CMD: onyx-112vm8 mkdir -p /tmp/d116.conf-sanity
onyx-112vm8: mkdir: cannot create directory '/tmp/d116.conf-sanity': No space left on device
pdsh@onyx-112vm4: onyx-112vm8: ssh exited with exit code 1
CMD: onyx-112vm8 touch /tmp/f116.conf-sanity-mdt0
CMD: onyx-112vm8 mkfs -t xfs -d file,size=1t,name=/tmp/f116.conf-sanity-mdt0
onyx-112vm8: mkfs.xfs: pwrite failed: No space left on device
pdsh@onyx-112vm4: onyx-112vm8: ssh exited with exit code 1
meta-data=/tmp/f116.conf-sanity-mdt0 isize=512 agcount=4, agsize=67108864 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1
data = bsize=4096 blocks=268435456, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=131072, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
conf-sanity test_116: @@@@@@ FAIL: mkfs temporary xfs image
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV |
| Comments |
| Comment by Peter Jones [ 09/Dec/23 ] |
|
As per Andreas "No space left on device" is probably a test system issue |
| Comment by Andreas Dilger [ 09/Dec/23 ] |
|
It looks like this might be leftovers from test_83? "{{ENOSPC on OST doesn't cause message VFS: Busy inodes after unmount ... }}" or possibly another patch that landed recently and maybe leaves some junk in /tmp? It should be easy to push a patch that adds "ls -ls /tmp" into this subtest. |