www.fsarchiver.org

The code has been changed to attempt to read xattr and ACLs instead of expecting mount options to be present. This should be more reliable to find whether or not these attributes are supported.

The fix has been added to the latest git version and it will be in fsarchiver-0.6.22

fsarchiver will show this error message if the mount options cannot be found in /proc/self/mountinfo (this is verified by generic_get_mntinfo in the code) and if these mount options are not set in the default mount options in the filesystem attributes. The simplest solution to your problem is to cha...

fsarchiver is a linux application and will never run on Windows. It would be far too much work to rewrite as it is a system application which depend on lots of things which would be very different on windows.

I confirm this is a limitation of the mkfsopt: it does not support values which contains separators such as commas and semi-colons. There is no workaround or solution at the moment (escaping or quoting does not work)

This bug has been fixed in fsarchiver-0.6.21

This bug has been fixed in fsarchiver-0.6.21

Thanks for your bug report. Can you please test fsarchiver-0.6.17-beta001.tar.gz

Thanks for having tested the beta version.
I have just released the sources of fsarchiver-0.6.16.

Yes this was planned for fsarchiver-0.7 but am lacking time to work on it unfortunately

I have modified the function to consider "-" as a separator as it seems to be how we are supposed to parse this file according to linux/Documentation/filesystems/proc.txt

Would you please be able to test the beta1 with both sysvint and systemd, so that I can release the final version soon ?

I confirm the solution is correct as another RHEL5/CentOS5 has been affected.
The fix has been merged in git and will be part of fsarchiver-0.6.16 soon

fsarchiver does not have to be rebuilt after ntfs-3g is upgraded as it is not linked. Which ntfs-3g version are you using ?

fsarchiver works at the file level so it does not need this.

Which type of livecd are you using ? You simply need an execution environment which comes with an up to date version of e2fsprogs in order to create an ext4 filesystem. You can use SystemRescueCd which comes with all up to date fileystem tools and fsarchiver (including a 64bit version in case it nee...

Many thanks for your test. You can also use SystemRescueCd-2.8.0-beta to get the latest fsarchiver without having to update it.