Bug 1134142
| Summary: | After ntfsresize is used, Windows 8.1 chkdsk doesn't clear the dirty bit | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> |
| Component: | ntfs-3g | Assignee: | Tom "spot" Callaway <tcallawa> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | jean-pierre.andre, tcallawa |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-02 03:32:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chris Murphy
2014-08-27 00:41:16 UTC
"The question is, does ntfsresize set the correct flag on Window 8 NTFS volumes? (Is it possible there's a new one that differs from Windows 7?)" Possible, but unlikely. Windows 8 just cannot imagine a flag could pop out of nowhere. "If it's not cleared is there any harm down the road?" No danger related to the flag being set. The danger stems from the resizing, so doing a chkdsk is a safety measure. For example, a backup boot sector should be copied to the last sector of the resized partition, but if an approximate new partition size is requested (such as in "ntfsresize -s 45G /dev/sda2"), ntfsresize cannot know for sure where the future last sector will be, and this is left for chkdsk to repair. After the Windows 8 reboot, does "ntfsfix -n" report a bad backup boot sector ? This will show whether chkdsk was run. The backup boot sector is a minor concern as it is only used when the normal boot sector has been damaged, and this issue can be avoided by telling ntfsresize the exact future size of the partition (a byte count multiple of the sector size), or by starting ntfsfix after the partition is created. After Windows 8 reboot, "ntfsfix -n" does not report a bad backup boot sector, but "ntfsresize -i" still sees a volume check flag set. Windows 7 fixes the backup boot sector, and unsets the volume check flag at the next boot. While Windows 8 only fixes the backup boot sector. If "ntfsfix -n" reports a bad backup boot sector before the Windows 8 reboot (but after the new partition table has been written), and it does not after the reboot, then Windows 8 has made a check (probably through a minimal chkdsk on the mounted partition) and there is nothing to worry about. As Windows behavior may change in the future, GUIs should nevertheless recommend starting chkdsk manually. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |