Back to bug 1020304
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Alasdair Kergon | 2013-10-18 21:05:37 UTC | Priority | unspecified | high |
| Status | NEW | ASSIGNED | ||
| Severity | unspecified | medium | ||
| Peter Rajnoha | 2013-10-22 14:34:37 UTC | Status | ASSIGNED | POST |
| Tom Lavigne | 2013-10-23 11:40:35 UTC | CC | tlavigne | |
| Peter Rajnoha | 2013-10-23 15:26:00 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.100-7.el6 | |||
| errata-xmlrpc | 2013-10-23 15:40:26 UTC | Status | MODIFIED | ON_QA |
| Nenad Peric | 2013-10-24 09:07:34 UTC | Status | ON_QA | VERIFIED |
| Peter Rajnoha | 2013-11-05 08:29:42 UTC | Doc Text | The blkdeactivate script iterates over the list of devices if they're given as an argument and it tries to unmount/deactivate them one by one. However, this iteration failed to proceed if any of the umount/deactivation was unsuccessful. As a result of this bug, the same device was tried again and again, causing an endless loop, never proceeding to the next device given. This has been fixed and if blkdeactivate fails to unmount/deactivate any of the devices given as an argument, the processing of the device is properly skipped and blkdeactivate proceeds with processing the next device given. | |
| errata-xmlrpc | 2013-11-21 23:29:32 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-11-21 18:29:32 UTC |
Back to bug 1020304