Massimiliano Ghilardi

Since you say that `ftype=1` is the default, then `fstransform /dev/sda3 xfs` is enough Usual disclaimer: you'd better have a backup in case `fstransform` damages your filesystem, and I do...

Yes, the converted filesystem will have a new, auto-generated UUID. Preserving the filesystem UUID and label (if any) during the conversion could be a useful improvement - it's also quite...

Yes, it's very filesystem dependent. Setting the UUID at creation is probably (slightly) easier. And yes, it should be in the README. I'll add it

I have never used xattrs, and fstransform does not copy them... It's surely worth adding, in the next weeks I will try to extract the relevant from GNU 'cp'

Commit c1bd8c59342ade582485e4b124f5020f5c5b6f87 adds initial support to copy xattrs using `ioctl(FS_IOC_FSSETXATTR)` Among other things, it correctly manages both xattr `+i` (immutable) and xattr `+a` (append-only), which must be handled specially because:...

Yes, you can use fstransform to create a new filesystem with different options and move the content of existing filesystem into it, in place. For example, if a certain filesystem...

Hi @sivapvarma, fstransform mounts the partition as one of the first steps to convert it. Attempting to convert a filesystem with errors is destined to cause a lot of problems,...

Last time I tested fstransform with btrfs, I got kernel errors. But that was some years ago... let's hope btrfs is more solid now. The alternative to use fstransform for...

The commands are correct, but it seems that `mount -r` does not work as expected on your `/dev/loop0`. Which filesystem does it contain?

Update: there is a mismatch in the paths you're using. You mount `/dev/loop0` to the directory `/tmp/weiwei2`, but then you attempt to use a file `/tmp/fstransform.mount.23404/.fstranform.loop.26458` which is **not** inside...