FAQ SearchLogin
Tuxera Home
View unanswered posts | View active topics It is currently Fri May 07, 2021 00:02



Post new topic Reply to topic  [ 4 posts ] 
ntfsresize question 
Author Message

Joined: Wed Oct 01, 2014 00:33
Posts: 4
Post ntfsresize question
Greetings,

I am running to an issue with ntfsresize on a LVM snapshot of a windows kvm instance. This only happens 1 out of 10 times, and attempting again on the same instance (new lvm snapshot). The KVM parent is running CentOS 7.1 and I'm running the ntfs-3g v2015.3.14. Again this only happens 1 out of times times, and the same process on the very same KVM instance succeeded on the next attempt after failure. I'm hoping you guys could shed some light on the error messages i've been getting.

Code:
Error running 'ntfsresize -v -f -i /dev/mapper/LVM-SNNRT7--BACKUP--20150715T183016p2': : ntfsresize v2015.3.14 (libntfs-3g) ; Device name : /dev/mapper/LVM-SNNRT7--BACKUP--20150715T183016p2 ; NTFS volume version: 3.1 ; Cluster size : 4096 bytes ; Current volume size: 37056672256 bytes (37057 MB) ; Current device size: 37056675840 bytes (37057 MB) ; Checking for bad sectors ... ; Checking filesystem consistency ... ; 0.00 percent completed 0.04 percent completed 0.08 percent completed 0.12 percent completed 0.16 percent completed 0.20 percent completed 0.24 percent completed 0.28 percent completed 0.32 percent completed 0.36 percent completed 0.40 percent completed 0.44 percent completed 0.48 percent completed 0.52 percent completed 0.56 percent completed 0.60 percent completed 0.64 percent completed 0.68 percent completed 0.72 percent completed 0.76 percent completed 0.80 percent completed 0.84 percent completed 0.89 percent completed 0.93 percent completed 0.97 percent completed 1.01 percent completed 1.05 percent completed 1.09 percent completed 1.13 percent completed 1.17 percent completed 1.21 percent completed 1.25 percent completed 1.29 percent completed 1.33 percent completed 1.37 percent completed 1.41 percent completed 1.45 percent completed 1.49 percent completed 1.53 percent completed 1.57 percent completed 1.61 percent completed 1.65 percent completed 1.69 percent completed 1.73 percent completed 1.77 percent completed 1.81 percent completed 1.85 percent completed 1.89 percent completed 1.93 percent completed 1.97 percent completed 2.01 percent completed 2.05 percent completed 2.09 percent completed 2.13 percent completed 2.17 percent completed 2.21 percent completed 2.25 percent completed 2.29 percent completed 2.33 percent completed 2.37 percent completed 2.41 percent completed 2.45 percent completed 2.49 percent completed 2.53 percent completed 2.57 percent completed 2.61 percent completed 2.66 percent completed 2.70 percent completed 2.74 percent completed 2.78 percent completed 2.82 percent completed 2.86 percent completed 2.90 percent completed 2.94 percent completed 2.98 percent completed 3.02 percent completed 3.06 percent completed 3.10 percent completed 3.14 percent completed 3.18 percent completed 3.22 percent completed 3.26 percent completed 3.30 percent completed 3.34 percent completed 3.38 percent completed 3.42 percent completed 3.46 percent completed 3.50 percent completed 3.54 percent completed 3.58 percent completed 3.62 percent completed 3.66 percent completed 3.70 percent completed 3.74 percent completed 3.78 percent completed 3.82 percent completed 3.86 percent completed 3.90 percent completed 3.94 percent completed 3.98 percent completed 4.02 percent completed 4.06 percent completed 4.10 percent completed 4.14 percent completed 4.18 percent completed 4.22 percent completed 4.26 percent completed 4.30 percent completed 4.34 percent completed 4.38 percent completed 4.43 percent completed 4.47 percent completed 4.51 percent completed 4.55 percent completed 4.59 percent completed 4.63 percent completed 4.67 percent completed 4.71 percent completed 4.75 percent completed 4.79 percent completed 4.83 percent completed 4.87 percent completed 4.91 percent completed 4.95 percent completed 4.99 percent completed 5.03 percent completed 5.07 percent completed 5.11 percent completed 5.15 percent completed 5.19 percent completed 5.23 percent completed 5.27 percent completed 5.31 percent completed 5.35 percent completed 5.39 percent completed 5.43 percent completed 5.47 percent completed 5.51 percent completed 5.55 percent completed 5.59 percent completed 5.63 percent completed 5.67 percent completed 5.71 percent completed 5.75 percent completed 5.79 percent completed 5.83 percent completed 5.87 percent completed 5.91 percent completed 5.95 percent completed 5.99 percent completed 6.03 percent completed 6.07 percent completed 6.11 percent completed 6.16 percent completed 6.20 percent completed 6.24 percent completed 6.28 percent completed 6.32 percent completed 6.36 percent completed 6.40 percent completed 6.44 percent completed 6.48 percent completed 6.52 percent completed 6.56 percent completed 6.60 percent completed 6.64 percent completed 6.68 percent completed 6.72 percent completed 6.76 percent completed 6.80 percent completed 6.84 percent completed 6.88 percent completed 6.92 percent completed 6.96 percent completed 7.00 percent completed 7.04 percent completed 7.08 percent completed 7.12 percent completed 7.16 percent completed 7.20 percent completed 7.24 percent completed 7.28 percent completed 7.32 percent completed 7.36 percent completed 7.40 percent completed 7.44 percent completed 7.48 percent completed 7.52 percent completed 7.56 percent completed 7.60 percent completed 7.64 percent completed 7.68 percent completed 7.72 percent completed 7.76 percent completed 7.80 percent completed 7.84 percent completed 7.88 percent completed 7.93 percent completed 7.97 percent completed 8.01 percent completed 8.05 percent completed 8.09 percent completed 8.13 percent completed 8.17 percent completed 8.21 percent completed 8.25 percent completed 8.29 percent completed 8.33 percent completed 8.37 percent completed 8.41 percent completed 8.45 percent completed 8.49 percent completed 8.53 percent completed 8.57 percent completed 8.61 percent completed 8.65 percent completed 8.69 percent completed 8.73 percent completed 8.77 percent completed 8.81 percent completed 8.85 percent completed 8.89 percent completed 8.93 percent completed 8.97 percent completed 9.01 percent completed 9.05 percent completed 9.09 percent completed 9.13 percent completed 9.17 percent completed 9.21 percent completed 9.25 percent completed 9.29 percent completed 9.33 percent completed 9.37 percent completed 9.41 percent completed 9.45 percent completed 9.49 percent completed 9.53 percent completed 9.57 percent completed 9.61 percent completed 9.66 percent completed 9.70 percent completed 9.74 percent completed 9.78 percent completed 9.82 percent completed 9.86 percent completed 9.90 percent completed 9.94 percent completed 9.98 percent completed ..........99.53 percent completed 99.57 percent completed 99.61 percent completed 99.65 percent completed 99.69 percent completed 99.73 percent completed 99.77 percent completed 99.81 percent completed 99.85 percent completed 99.89 percent completed 99.93 percent completed 99.97 percent completed100.00 percent completed ; Accounting clusters ... ; Cluster accounting failed at 3393901 (0x33c96d): missing cluster in $Bitmap ; Cluster accounting failed at 3393902 (0x33c96e): missing cluster in $Bitmap ; Cluster accounting failed at 3393903 (0x33c96f): missing cluster in $Bitmap ; Cluster accounting failed at 3393904 (0x33c970): missing cluster in $Bitmap ; Cluster accounting failed at 3393905 (0x33c971): missing cluster in $Bitmap ; Cluster accounting failed at 3393906 (0x33c972): missing cluster in $Bitmap ; Cluster accounting failed at 3393907 (0x33c973): missing cluster in $Bitmap ; Cluster accounting failed at 3393908 (0x33c974): missing cluster in $Bitmap ; Cluster accounting failed at 3393909 (0x33c975): missing cluster in $Bitmap ; Cluster accounting failed at 3393910 (0x33c976): missing cluster in $Bitmap ; Filesystem check failed! Totally 10 cluster accounting mismatches. ; ERROR: NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE! ; The usage of the /f parameter is very IMPORTANT! No modification was ; and will be made to NTFS by this software until it gets repaired. [1]



Any help would greatly be appreciated, additionally please let me know if you need anymore information.

Thanks
jvandellen


Wed Jul 15, 2015 21:02
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: ntfsresize question
Hi,

Code:
Cluster accounting failed at 3393901 (0x33c96d): missing cluster in $Bitmap

This means cluster 3393901 has been found allocated to a file, but was not reserved in the general bitmap. This normally signals an allocation error.

Quote:
ntfsresize on a LVM snapshot of a windows kvm instance

Is this snapshot supposed to be consistent ? Depending on how it was created, recent updates may not yet be written to target location (if the snapshot was created on Windows, recent updates may be described in the journal).
Code:
ntfsresize -v -f -i /dev/mapper/   ....

Was the device not mounted while resizing ? The -f flag would cause the check to be ignored.

Similarly, is there some hardware or software cacheing in your architecture, which may hide some information (such as using the "fast restart" feature of Windows 8, or having a hardware cache on a SSD) ?

Do the errors always occur on the same clusters ? When an error occurs and the resizing is rejected, what happens when you restart the resizing of the same image ?

If the error stems from a recent update not yet written to device (cacheing issue), you can identify the file to which a cluster is allocated by using ntfscluster with option -c then check the timestamp of the file to tell whether it was recently updated.

Regards

Jean-Pierre


Thu Jul 16, 2015 14:17
Profile

Joined: Wed Oct 01, 2014 00:33
Posts: 4
Post Re: ntfsresize question
Thank you for your response. I suspected that it could possibly be a disk caching issue, as we've had issues like that before with these raid controllers.

It appears when the ntfsresize is failing on a snapshot (created via the linux parent) ntfsresize fails at the same clusters everytime for that snapshot. However, if i try the whole process over again (create a new snapshot) it usually works just fine.

I took your advice and ran ntfscluster -c on a snapshot which failed. This is what i received truncated due to message character limit (attached full log)

Code:
[root@tp81 ~]# ntfscluster -c 17774 /dev/mapper/LVM-6K8UKC--BACKUP--20150720T184449p2
Searching for cluster 17774
Inode 84 is an extent of inode 84143.
Inode 85 is an extent of inode 90207.
Inode 94 is an extent of inode 22655.
Inode 116 is an extent of inode 44.
Inode 122 /Windows/System32/config/systemprofile/AppData/Local/lastalive0.dat/$DATA
Inode 124 is an extent of inode 86980.
Inode 137 is an extent of inode 22249.




When i logged back into the instance it didn't look like /Windows/System32/config/systemprofile/AppData/Local/lastalive0.dat/$DATA even existed. I was wondering if you could give me more information on what exactly that all means, and possible solutions. Would simply running a sync on the linux parent before or after the snapshot is created possibly resolve the issue?


Mon Jul 20, 2015 22:00
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: ntfsresize question
Hi,

Quote:
It appears when the ntfsresize is failing on a snapshot (created via the linux parent) ntfsresize fails at the same clusters everytime for that snapshot.

So the problems is generated when you take the snapshot.

This leads back to my question : is the snapshot supposed to be consistent ?

What are your snapshots ? What is the state of the virtual machine when you take a snapshot ? Are the snapshot images of a virtual machine taken without the virtual OS being fully shut down ?

Quote:
This is what i received truncated due to message character limit (attached full log)

I do not see the attachment (note : this forum requires that attachments be compressed). Anyway, posting the full output is not much useful, just note what ntfscluster has to say about the unallocated clusters (17774 in your example), and mention whether the file was recently changed.
Quote:
When i logged back into the instance it didn't look like /Windows/System32/config/systemprofile/AppData/Local/lastalive0.dat/$DATA even existed.

This is not really the file name : it means the user data of file "/Windows/System32/config/systemprofile/AppData/Local/lastalive0.dat"
Quote:
Would simply running a sync on the linux parent before or after the snapshot is created possibly resolve the issue?

You have several layers of file systems : at least the one in the guest OS and the one in the host OS, moreover you have a LVM, and you have to sync all of them. Is the guest OS running when you take the snapshot ? Is the guest partition mounted ? Are you using Windows 8 as the guest OS ?
Quote:
I was wondering if you could give me more information on what exactly that all means, and possible solutions.

It would be helpful if you are more precise about your configuration, and the way you take snapshots. One possible solution is to run chkdsk on the snapshot.

Regards

Jean-Pierre


Tue Jul 21, 2015 12:45
Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 


Who is online

Users browsing this forum: Majestic-12 [Bot] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin.