Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Since qemu-kvm-rhev-2.10.0-3.el7, image locking is enabled by default. It makes qemu to operate one more file descriptor per file. When create a vmdk image with large size, hundreds of extent raw images will be created. However the default maximum number of open file descriptors is 1024. The limit FDs will make qemu fail to open the vmdk image.
It will helpful to document this to make user know clear about it.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.10.0-21.el7
How reproducible:
100%
Steps to Reproduce:
1. Check the default limit of file descriptors for usr
# ulimit -n
1024
2. Create 1TB vmdk iamge
# qemu-img create -f vmdk -o subformat=twoGbMaxExtentFlat test.vmdk 1T
Formatting 'test.vmdk', fmt=vmdk size=1099511627776 compat6=off hwversion=undefined subformat=twoGbMaxExtentFlat
3. Get image info
# qemu-img info test.vmdk
qemu-img: Could not open 'test.vmdk': Could not open 'test-f507.vmdk': Too many open files
4. Increase limit of file descriptors
# ulimit -n 2048
5. Get image info
# qemu-img info test.vmdk
image: test.vmdk
file format: vmdk
virtual size: 1.0T (1099511627776 bytes)
disk size: 20K
Format specific information:
cid: 121892516
parent cid: 4294967295
create type: twoGbMaxExtentFlat
extents:
[0]:
virtual size: 2147483648
filename: test-f001.vmdk
format: FLAT
...
[511]:
virtual size: 2147483648
filename: test-f512.vmdk
format: FLAT
Actual results:
Expected results:
Additional info:
Fam, you mentioned in an upstream discussion that we don't technically need s->lock_fd any more [1]. So maybe instead of documenting that we need the double amount of file descriptors, we can just avoid that?
In any case, congratulations, you just won a bug. :-)
[1] http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg07412.html
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/RHSA-2019:2553
Description of problem: Since qemu-kvm-rhev-2.10.0-3.el7, image locking is enabled by default. It makes qemu to operate one more file descriptor per file. When create a vmdk image with large size, hundreds of extent raw images will be created. However the default maximum number of open file descriptors is 1024. The limit FDs will make qemu fail to open the vmdk image. It will helpful to document this to make user know clear about it. Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.10.0-21.el7 How reproducible: 100% Steps to Reproduce: 1. Check the default limit of file descriptors for usr # ulimit -n 1024 2. Create 1TB vmdk iamge # qemu-img create -f vmdk -o subformat=twoGbMaxExtentFlat test.vmdk 1T Formatting 'test.vmdk', fmt=vmdk size=1099511627776 compat6=off hwversion=undefined subformat=twoGbMaxExtentFlat 3. Get image info # qemu-img info test.vmdk qemu-img: Could not open 'test.vmdk': Could not open 'test-f507.vmdk': Too many open files 4. Increase limit of file descriptors # ulimit -n 2048 5. Get image info # qemu-img info test.vmdk image: test.vmdk file format: vmdk virtual size: 1.0T (1099511627776 bytes) disk size: 20K Format specific information: cid: 121892516 parent cid: 4294967295 create type: twoGbMaxExtentFlat extents: [0]: virtual size: 2147483648 filename: test-f001.vmdk format: FLAT ... [511]: virtual size: 2147483648 filename: test-f512.vmdk format: FLAT Actual results: Expected results: Additional info: