Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Another issue to take notice. When shrinking the ntfs filesystem, filesystem size specified in ntfsresize-size is 52396032 bytes, which is 12792 blocks. But statvfs reports block counts is 12791, which is one block less than requested. Is is a problem? (I didn't file another bug for this issue for it is a minor one.)
Comment 2Richard W.M. Jones
2011-03-15 08:50:47 UTC
I'll have a closer look later, but I think this is
by design -- the ntfsresize utility cannot resize the
same filesystem twice in a row without the VM being
rebooted and checked (ie. chkdsk/scandisk).
It will probably work if you boot the VM and let it
do the check between resizes.
Comment 3Richard W.M. Jones
2011-06-10 09:33:39 UTC
I'm going to investigate this for 6.2. I think
comment 2 is the correct analysis, but this limitation
in ntfsresize should be documented.
Comment 4Richard W.M. Jones
2011-07-12 13:16:48 UTC
Comment 6Richard W.M. Jones
2011-08-10 12:43:47 UTC
I've included the documentation fix in
libguestfs-1.7.17-23.el6.
The other two commits can't be easily applied to RHEL 6.2
because virt-resize was rewritten from Perl -> OCaml between
1.8 and 1.12. In RHEL 6.3 we may rebase libguestfs, so we will
get those two commits as well.
Checked in libguestfs-1.7.17-26, the following info is documented in ntfsresize's help.
*Note:* After the resize operation, the filesystem is marked as
requiring a consistency check (for safety). You have to boot into
Windows to perform this check and clear this condition. Furthermore,
ntfsresize refuses to resize filesystems which have been marked in this
way. So in effect it is not possible to call ntfsresize multiple times
on a single filesystem without booting into Windows between each resize.
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.
http://rhn.redhat.com/errata/RHBA-2011-1512.html