Page 2 of 2

Re: Errors when running fsarchiver

Posted: Mon Sep 30, 2013 10:47 pm
by clepsydrae
For the record, the ntfs-3g person said that he could advise someone in developing a "workaround" (I was not clear from his posts why a direct solution is not possible, but the technicalities are beyond me).

For more info see: http://tuxera.com/forum/viewtopic.php?f ... 7461953121

Possibly the fsarchiver developer(s) know all about this already, but at least we users now have some kind of an answer?

-c

Re: Errors when running fsarchiver

Posted: Mon Sep 30, 2013 10:53 pm
by clepsydrae
zappacor wrote:wow! followed your link and those pointed to from there too, it seems to be a one-year old issue, am I right? Any hope to have this fixed?
Note that fsarchiver states that ntfs support is "unstable and incomplete", but those adjectives are not on the main page, only on the "cloning ntfs" page. The main page lists "Support for ntfs filesystems (ability to create flexible clones of windows partitions)" as one of the "Implemented features" -- this might be why some people are confused. It would maybe be a good idea to change that wording.

Re: Errors when running fsarchiver

Posted: Tue Oct 01, 2013 6:42 am
by zappacor
Any dev aware of this? Or of any other thing that could make fsarchiver work fine with Windows 7?
clepsydrae wrote:For the record, the ntfs-3g person said that he could advise someone in developing a "workaround" (I was not clear from his posts why a direct solution is not possible, but the technicalities are beyond me).

For more info see: http://tuxera.com/forum/viewtopic.php?f ... 7461953121

Possibly the fsarchiver developer(s) know all about this already, but at least we users now have some kind of an answer?

-c

Re: Errors when running fsarchiver

Posted: Thu Jan 30, 2014 9:22 pm
by feffer777
hmmm, I've been using fsarchiver for win7 for a few years with zero errors?

Code: Select all

Statistics for filesystem 0
* files successfully processed:....regfiles=103943, directories=26465, symlinks=66, hardlinks=26538, specials=3
* files with errors:...............regfiles=0, directories=0, symlinks=0, hardlinks=0, specials=0
I mostly run linux, so my win7 install is pretty basic (I think I have restore points turned off). I have restored from my images too and they work fine. I run fsarchiver separately for the boot partition and the rest of the system. My win7 data is on a separate partition which is backed with rsync.

Maybe your win7 is configured differently?
OK, I just saw another thing. I'm running fsarchiver from the Ubuntu repos, currently .6.12-1build1 so this is far from .6.17 and perhaps I'd get error with the latest version too...

Re: Errors when running fsarchiver

Posted: Thu Jan 30, 2014 10:01 pm
by clepsydrae
feffer777 wrote:hmmm, I've been using fsarchiver for win7 for a few years with zero errors?

Code: Select all

Statistics for filesystem 0
* files successfully processed:....regfiles=103943, directories=26465, symlinks=66, hardlinks=26538, specials=3
* files with errors:...............regfiles=0, directories=0, symlinks=0, hardlinks=0, specials=0
I mostly run linux, so my win7 install is pretty basic (I think I have restore points turned off). I have restored from my images too and they work fine. I run fsarchiver separately for the boot partition and the rest of the system. My win7 data is on a separate partition which is backed with rsync.

Maybe your win7 is configured differently?
OK, I just saw another thing. I'm running fsarchiver from the Ubuntu repos, currently .6.12-1build1 so this is far from .6.17 and perhaps I'd get error with the latest version too...
What version of ntfs-3g are you using?

My only-partially-educated guess is that your WinSXS directory is not being backed up "perfectly" but probably well enough that you wouldn't notice. If I understand things correctly, later versions of ntfs-3g cause fsarchiver to not include files with >1 hard link (e.g. many files in WinSXS), but earlier versions (such as the one you may be using) would not trigger this and instead would back the file up without preserving all of its attributes. Whether this matters or is ever noticed is another matter.

If you wanted to test, you'd have to use the ntfsinfo utility to find a file (in a virginal Windows 7 install, not a restored install) in \WinSXS with >1 hard link, do a backup, do a restore, and see if the file is there and still has >1 hard link. I assume it would not.

Definitely see this thread (and what it links to) for more info.

Hopefully this will get cleared up one fine day. For now I only use partimage for ntfs, which itself is "experimental", but i'm not aware of any other linux-based options. fsarchiver is so very close to being the go-to solution for ntfs backups in linux. :-)

Re: Errors when running fsarchiver

Posted: Thu Jan 30, 2014 11:46 pm
by zappacor
After so long and with no news I'm loosing the hope of having it working fine

Re: Errors when running fsarchiver

Posted: Sat Feb 01, 2014 9:23 pm
by feffer777
Did some more reading about the winsxs directory etc. Mine is 15gb in size. I see why it is important to have the hard links to winsxs components accurately backed up by fsarchiver.
btw my ntfs-3g ...

Code: Select all

# dpkg -l ntfs-3g
ii  ntfs-3g             1:2012.1.15AR.1-1ub read/write NTFS driver for FUSE
I guess I was happy in my ignorance about the issue. But until I start getting errors, I probably won't bother doing anything differently.

I use fsarchiver and rsync in bash scripts for unattended nightly backups of my home systems. And since I can and have restored both linux and win7 from the backups, I'm comfortable. In any case, win7 is not really important to me. I rarely boot into it, and I don't really need anything on it. On the linux side, my scripts seem to work perfectly; so for me that's golden.

From what I can tell, the developer is well aware of the issue, but the next version is major revision so the hard link error issue could be addressed then.

Re: Errors when running fsarchiver

Posted: Sun Feb 02, 2014 8:58 am
by clepsydrae
feffer777 wrote:ii ntfs-3g 1:2012.1.15AR.1-1ub read/write NTFS driver for FUSE
Yeah, if my shakey understanding of the chronology of ntfs-3g and files with multiple names (hard links) is right, that's old enough that ntfs-3g is ignoring the hard links or otherwise silently handling them in a manner that doesn't trigger fsarchiver to skip the files.
I guess I was happy in my ignorance about the issue. But until I start getting errors, I probably won't bother doing anything differently.
Yeah, maybe the result is that the "important"/modern version of the file is backed up and the unimportant one (i.e. the old-style dos name) is not, or something to that effect. I personally would chance it with partimage's "experimental" imaging over fsarchiver's known-flawed backups, but maybe it's a toss-up (and of course with more recent versions of ntfs-3g you don't have a choice anyway, since such files are skipped entirely, afaict).
From what I can tell, the developer is well aware of the issue, but the next version is major revision so the hard link error issue could be addressed then.
Out of curiosity, what leads you to believe that the developer knows about the issue or that a new version is on the way?

Thanks,
-c

Re: Errors when running fsarchiver

Posted: Wed Feb 05, 2014 6:27 pm
by feffer777
Out of curiosity, what leads you to believe that the developer knows about the issue or that a new version is on the way?
The fsarchiver "status" page says ver .7 is being worked on and that ntfs support needs work. Also, I'm pretty sure the developer is aware of the questions/issues here even though he only comments from time to time.

I agree that errors on ntfs are significant and should ultimately be resolved. I previously used partimage as my OS backup app, but changed to fsarchiver to handle Linux ext4 and win7. Before I made the change, I did extensive testing that fsarchiver could save AND restore both linux and win7. I currently have a win7 system on /dev/sda, an SSD, and /dev/sdc5 a hdd partition. The later is a test fsarchiver restore that functions properly. So I do trust my backup process using fsarchiver even though it still has imperfect ntfs support. Like you, I look forward to futher development of fsarchiver.

Re: Errors when running fsarchiver

Posted: Wed Feb 05, 2014 8:30 pm
by clepsydrae
feffer777 wrote:
Out of curiosity, what leads you to believe that the developer knows about the issue or that a new version is on the way?
The fsarchiver "status" page says ver .7 is being worked on and that ntfs support needs work. Also, I'm pretty sure the developer is aware of the questions/issues here even though he only comments from time to time.
Oh, good find. That's nice to see, but i note that that page and the post that page links to are a bit over 3 years old, so that's not such a great sign. Last changes at sourceforge ~1 year ago... Here's hoping the dev(s) or someone finds the time in life to pick fsarchiver back up!

-c