[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