[Bugs] [Bug 1802016] read() returns more than file size when using direct I/O

bugzilla at redhat.com bugzilla at redhat.com
Sat Jun 6 11:59:48 UTC 2020


https://bugzilla.redhat.com/show_bug.cgi?id=1802016

SATHEESARAN <sasundar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |VERIFIED
   Fixed In Version|                            |gluster-6.0-34



--- Comment #5 from SATHEESARAN <sasundar at redhat.com> ---
Verified with RHVH 4.4.1 and RHGS 3.5.2 - glusterfs-6.0-37.el8rhgs with the
following steps:

[root@ ~]# ls
/rhev/data-center/mnt/glusterSD/rhsqa-grafton7.lab.eng.blr.redhat.com\:_vmstore/977e8d86-afd8-46c1-bf15-ed19d3cb6ed1/dom_md/
ids  inbox  leases  metadata  outbox  xleases

[root@ ~ ]# stat metadata 
  File: metadata
  Size: 391             Blocks: 1          IO Block: 131072 regular file
Device: 34h/52d Inode: 10208956554895298979  Links: 1
Access: (0644/-rw-r--r--)  Uid: (   36/    vdsm)   Gid: (   36/     kvm)
Context: system_u:object_r:fusefs_t:s0
Access: 2020-06-03 18:59:17.547192000 +0000
Modify: 2020-06-03 18:59:17.548192011 +0000
Change: 2020-06-03 18:59:17.600192582 +0000
 Birth: -

[root@ ~ ]# cat metadata 
ALIGNMENT=1048576
BLOCK_SIZE=4096
CLASS=Data
DESCRIPTION=vmstore
IOOPTIMEOUTSEC=10
LEASERETRIES=3
LEASETIMESEC=60
LOCKPOLICY=
LOCKRENEWALINTERVALSEC=5
POOL_UUID=0f3fc724-a5ca-11ea-a7a6-004755204901
REMOTE_PATH=rhsqa-grafton7.lab.eng.blr.redhat.com:/vmstore
ROLE=Regular
SDUUID=977e8d86-afd8-46c1-bf15-ed19d3cb6ed1
TYPE=GLUSTERFS
VERSION=5
_SHA_CKSUM=771d06cb29cd1ee6a7e5b4c72be119cd5078a87e

[root@ ~]# dd if=metadata of=/dev/null bs=4096 count=1
0+1 records in
0+1 records out
391 bytes copied, 0.000101469 s, 3.9 MB/s
[root@ ~]# dd if=metadata of=/dev/null bs=4096 count=1 iflag=direct
0+1 records in
0+1 records out
391 bytes copied, 0.00143502 s, 272 kB/s


So there are no zeroes padded


-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Bugs mailing list