Bug 1371634
| Summary: | ioprocess keep open file on shared storage after touching or truncating a file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Nir Soffer <nsoffer> | ||||
| Component: | ioprocess | Assignee: | Nir Soffer <nsoffer> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Kevin Alon Goldblatt <kgoldbla> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6.0 | CC: | acanan, amureini, bronhaim, dougsland, extras-qa, gklein, kgoldbla, mkalinin, nsoffer, ratamir, smizrahi, tnisan, ylavi | ||||
| Target Milestone: | ovirt-3.6.9 | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ioprocess-0.15.2-1 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1339777 | Environment: | |||||
| Last Closed: | 2016-09-21 18:08:08 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1339777, 1373491 | ||||||
| Bug Blocks: | 1339780, 1370564 | ||||||
| Attachments: |
|
||||||
|
Description
Nir Soffer
2016-08-30 16:59:40 UTC
How to test: 1. Setup system with one NFS storage domain and one host 2. Activate the spm 3. Wait about one minute after the host was activated, until one ioprocess child process is running. You can use "ps auxf" on the host 4. Check open files by this ioprocess using "lsof -p <ioprocess pid>" If you find more then one ioprocess child process, check all of them. Expected results before this fix (ioprocess-0.15.0): ioprocess keeps open the file /rhev/data-center/mnt/server:_path/__DIRECT_IO_TEST__ Expected results with this fix (ioprocess-0.15.2): No open file on shared storage. Created attachment 1198257 [details]
vdsm server and engine logs
Added logs
You can test the build mentioned in comment 4, or wait until the package is released. Tested with the following code: ---------------------------------------- rhevm-4.0.4.2-0.1.el7ev.noarch vdsm-4.18.13-1.el7ev.x86_64 Tested with the following scenario: Steps to Reproduce: 1. Setup system with one NFS storage domain and one host 2. Activate the spm 3. Wait about one minute after the host was activated, until one ioprocess child process is running. You can use "ps auxf" on the host 4. Check open files by this ioprocess using "lsof -p <ioprocess pid>" If you find more then one ioprocess child process, check all of them. Expected results before this fix (ioprocess-0.15.0): ioprocess keeps open the file /rhev/data-center/mnt/server:_path/__DIRECT_IO_TEST__ Results after the fix: lsof -p 10158 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME ioprocess 10158 vdsm cwd DIR 8,3 4096 2 / ioprocess 10158 vdsm rtd DIR 8,3 4096 2 / ioprocess 10158 vdsm txt REG 8,3 42192 1819196 /usr/libexec/ioprocess ioprocess 10158 vdsm mem REG 8,3 2112384 1819202 /usr/lib64/libc-2.17.so ioprocess 10158 vdsm mem REG 8,3 142304 1819228 /usr/lib64/libpthread-2.17.so ioprocess 10158 vdsm mem REG 8,3 40600 1820785 /usr/lib64/libyajl.so.2.0.4 ioprocess 10158 vdsm mem REG 8,3 6928 1819494 /usr/lib64/libgthread-2.0.so.0.4200.2 ioprocess 10158 vdsm mem REG 8,3 1287904 1819488 /usr/lib64/libglib-2.0.so.0.4200.2 ioprocess 10158 vdsm mem REG 8,3 164440 1819195 /usr/lib64/ld-2.17.so ioprocess 10158 vdsm mem REG 8,3 26254 1845006 /usr/lib64/gconv/gconv-modules.cache ioprocess 10158 vdsm 1w FIFO 0,8 0t0 97430 pipe ioprocess 10158 vdsm 2w FIFO 0,8 0t0 97431 pipe ioprocess 10158 vdsm 53w FIFO 0,8 0t0 97427 pipe ioprocess 10158 vdsm 54r FIFO 0,8 0t0 97428 pipe Actual results: No open file on shared storage. Expected results: Moving to VERIFIED! 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://rhn.redhat.com/errata/RHBA-2016-1927.html |