Bug 1667998
| Summary: | Image size as reported from the fuse mount is incorrect | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> | |
| Component: | rhhi | Assignee: | Sahina Bose <sabose> | |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | rhgs-3.4 | CC: | godas, kdhananj, pasik, rhs-bugs | |
| Target Milestone: | --- | |||
| Target Release: | RHHI-V 1.7 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-6.0-6 | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1668001 (view as bug list) | Environment: | ||
| Last Closed: | 2020-02-13 15:57:20 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1668001, 1705884, 1716871 | |||
| Bug Blocks: | ||||
|
Description
SATHEESARAN
2019-01-21 16:28:52 UTC
Size of the file as reported from the fuse mount: [root@ ~]# ls -lsah /rhev/data-center/mnt/glusterSD/rhsqa-grafton10.lab.eng.blr.redhat.com\:_data/bbeee86f-f174-4ec7-9ea3-a0df28709e64/images/0206953c-4850-4969-9dad-15140579d354/eaa5e81d-103c-4ce6-947e-8946806cca1b 8.0Z -rw-rw----. 1 vdsm kvm 1.1T Jan 21 17:14 /rhev/data-center/mnt/glusterSD/rhsqa-grafton10.lab.eng.blr.redhat.com:_data/bbeee86f-f174-4ec7-9ea3-a0df28709e64/images/0206953c-4850-4969-9dad-15140579d354/eaa5e81d-103c-4ce6-947e-8946806cca1b [root@ ~]# du -shc /rhev/data-center/mnt/glusterSD/rhsqa-grafton10.lab.eng.blr.redhat.com\:_data/bbeee86f-f174-4ec7-9ea3-a0df28709e64/images/0206953c-4850-4969-9dad-15140579d354/eaa5e81d-103c-4ce6-947e-8946806cca1b 16E /rhev/data-center/mnt/glusterSD/rhsqa-grafton10.lab.eng.blr.redhat.com:_data/bbeee86f-f174-4ec7-9ea3-a0df28709e64/images/0206953c-4850-4969-9dad-15140579d354/eaa5e81d-103c-4ce6-947e-8946806cca1b 16E total The disk image is preallocated with 1072GB of space Are you able to recreate this directly on the gluster fuse-mount using a simple qemu-img command? If so, can you share the exact command? -Krutika (In reply to Krutika Dhananjay from comment #2) > Are you able to recreate this directly on the gluster fuse-mount using a > simple qemu-img command? > > If so, can you share the exact command? > > -Krutika Ignore this. I see the requested information is already provided in the clone. The dependent RHGS bug is already ON_QA and moving this bug too to ON_QA Tested with RHVH 4.3.5 based on RHEL 7.7 with interim RHGS 3.5.0 build ( glusterfs-6.0-7 ) with the following scenarios: 1. Created preallocated image file of size 1TB or more. -------------------------------------------------------- Observed that the size of the image file is consistent now. [root@ ]# qemu-img create -f raw -o preallocation=falloc vm2.img 1T Formatting 'vm2.img', fmt=raw size=1099511627776 preallocation=falloc [root@ ]# ls -lsah vm2.img 1.0T -rw-r--r--. 1 root root 1.0T Jul 3 21:26 vm2.img [root@ ]# qemu-img create -f raw -o preallocation=falloc vm3.img 1.5T Formatting 'vm3.img', fmt=raw size=1649267441664 preallocation=falloc [root@ ]# ls -lsah vm3.img 1.5T -rw-r--r--. 1 root root 1.5T Jul 3 21:26 vm3.img 2. Created preallocated image file with the same name ------------------------------------------------------ [root@]# qemu-img create -f raw -o preallocation=falloc vm1.img 10G Formatting 'vm1.img', fmt=raw size=10737418240 preallocation=falloc [root@ ]# ls -lsah vm1.img 10G -rw-r--r--. 1 root root 10G Jul 3 21:25 vm1.img [root@ ]# qemu-img create -f raw -o preallocation=falloc vm1.img 10G Formatting 'vm1.img', fmt=raw size=10737418240 preallocation=falloc [root@ ]# ls -lsah vm1.img 10G -rw-r--r--. 1 root root 10G Jul 3 21:26 vm1.img In this case, the size of the image file is consistent Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0508 |