Back to bug 1302332
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Marcel Kolaja | 2016-01-27 14:05:47 UTC | Link ID | Red Hat Knowledge Base (Solution) 2136291 | |
| Karel Zak | 2016-01-28 11:52:11 UTC | Status | NEW | ASSIGNED |
| Karel Zak | 2016-01-28 13:09:00 UTC | Status | ASSIGNED | MODIFIED |
| errata-xmlrpc | 2016-01-28 13:20:02 UTC | Status | MODIFIED | ON_QA |
| Filip Krska | 2016-02-03 08:53:30 UTC | CC | harald | |
| Flags | needinfo?(harald) | |||
| Harald Hoyer | 2016-02-03 09:32:35 UTC | Flags | needinfo?(harald) | |
| Milan Navratil | 2016-02-08 15:43:31 UTC | CC | mnavrati | |
| Doc Text | Previously, the libblkid library did not provide XFS log signature offset. As a consequence, the wipefs command and LVM tools failed to erase XFS log from block devices. A patch has been applied to fix this bug, and XFS log can now be removed as expected. | |||
| errata-xmlrpc | 2016-02-10 12:24:52 UTC | Status | ON_QA | VERIFIED |
| Milan Navratil | 2016-03-23 12:24:18 UTC | Doc Text | Previously, the libblkid library did not provide XFS log signature offset. As a consequence, the wipefs command and LVM tools failed to erase XFS log from block devices. A patch has been applied to fix this bug, and XFS log can now be removed as expected. | Previously, the libblkid library did not provide the XFS log signature offset. As a consequence, the wipefs command and LVM tools failed to erase XFS log from block devices. A patch has been applied to fix this bug, and XFS log can now be removed as expected. |
| errata-xmlrpc | 2016-03-31 00:31:35 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-03-31 22:09:06 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-03-31 18:09:06 UTC |
Back to bug 1302332