OK, that seam to work however it is not exactly the correct solution for me since I need
to make it one command to be able to call it from an API
I have no name!@(none):/# ntfsresize /dev/sda1
ntfsresize v2012.1.15AR.5 (libntfs-3g)
ERROR: Volume is scheduled for check.
Run chkdsk /f and please try again, or see option -f.
I have no name!@(none):/# chkdsk /f
bash: chkdsk: command not found
I have no name!@(none):/#
I have no name!@(none):/# ntfsresize -f /dev/sda1
ntfsresize v2012.1.15AR.5 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 21472604672 bytes (21473 MB)
Current device size: 32210026496 bytes (32211 MB)
New volume size : 32210022912 bytes (32211 MB)
Checking filesystem consistency ...
100.00 percent completed
Accounting clusters ...
Space in use : 9815 MB (45.7%)
Collecting resizing constraints ...
WARNING: Every sanity check passed and only the dangerous operations left.
Make sure that important data has been backed up! Power outage or computer
crash may result major data loss!
Are you sure you want to proceed (y/[n])? y
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/sda1'.
Keresztes Péter-Zoltán
zozo(a)z0z0.tk
I haven’t lost my mind, I know exactly where I left it.
On 01 Jul 2014, at 20:45, Richard W.M. Jones <rjones(a)redhat.com> wrote:
[Let's keep everything on the mailing list]
On Tue, Jul 01, 2014 at 08:37:39PM +0300, Keresztes Péter-Zoltán wrote:
> Hi, I have run the command with virt-rescue and after getting lots of error I get a
prompt where I enter the ntfsresize —check /dev/sda1 and I get the following:
>
> I have no name!@(none):/# ntfsresize --check /dev/sda1
> ntfsresize v2012.1.15AR.5 (libntfs-3g)
> I have no name!@(none):/#
For comparison, here is the output using ntfs-3g-2014.2.15-1.fc20.x86_64:
$ guestfish -N fs:ntfs exit
$ virt-rescue --ro -a test1.img
[...]
> <rescue> ntfsresize --check /dev/sda1
ntfsresize v2014.2.15 (libntfs-3g)
> <rescue>
So that's basically the same as your output, and indicates that
the ntfsresize command itself is working.
Now you should try actually resizing the partition in virt-rescue.
Since it is inside ``virt-rescue --ro'' it won't actually alter the
disk image -- the ``--ro'' flag means that libguestfs puts a
protective overlay between the commands in the rescue shell and the
underlying disk image.
Here is what happens for me:
> <rescue> ntfsresize /dev/sda1
ntfsresize v2014.2.15 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 104727040 bytes (105 MB)
Current device size: 104727040 bytes (105 MB)
New volume size : 104727040 bytes (105 MB)
Nothing to do: NTFS volume size is already OK.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top