Bug 443065
Summary: | mkswap does not zero out old pvcreate signatures | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eric Sandeen <esandeen> |
Component: | util-linux-ng | Assignee: | Karel Zak <kzak> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-31 10:17:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eric Sandeen
2008-04-18 13:58:42 UTC
Well, this is pretty common and often reported problem. It seems we need a solution, but... from mkswap man page: The new style header does not touch the first block, so may be preferable, in case you have a boot loader or disk label there. so my question is: is it safe to zero out the device? I see that (for example) mkfs.e2fs checks for BSD labels and zaps few blocks... but is it enough for swap area? I have no clue. Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping The problem has been fixed in util-linux-ng v2.15-rc1 upstream release. The release should be included in F-12 and (probably) RHEL6. |