ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs

Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by chasil on Monday March 07, 2022 @03:56PM (#30593219)

BtrFS was previously restricted to crc32c checksums. This was enhanced to allow several more, including sha256. The crc32c checksum has also been improved as xxhash, which promises fewer collisions for safer deduplication. When configured for sha256, BtrFS uses a checksum that is as strong as ZFS.

However, the checksum must be chosen at the time of filesystem creation. I don't know of any way to upgrade an existing BtrFS filesystem.

Contrast this to ZFS, which allows the checksum to be modified on a file-by-file basis.

[ Parent | on HN ]

Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by ziml77 on Monday March 07, 2022 @07:48PM (#30595241)

Hmm well that's good to know. I like the idea of being able to have mismatched drive capacities and easy expandability which is why I had been looking at Btrfs. I will have to look more into the checksum options.

[ Parent | on HN ]

Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by namibj on Tuesday March 08, 2022 @12:38AM (#30596797)

send/receive should allow for checksum rotation; however this isn't in-place.

[ Parent | on HN ]

Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by chasil on Tuesday March 08, 2022 @02:38PM (#30605407)

I didn't think of that as a migration path.

[ Parent | on HN ]

Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by namibj on Wednesday March 09, 2022 @01:05PM (#30617903)

Breadth/creativity in the search of technical solutions is my specialty. Hope it helped!

[ Parent | on HN ]