Conversation

Notices

1. Embed this notice
   argv minus one (argv_minus_one@mastodon.sdf.org)'s status on Saturday, 30-Nov-2024 08:51:54 JST argv minus one

   So, somebody wrote a program that converts, in-place, an #NTFS volume into #btrfs.

   It even keeps an image of the original NTFS volume as a file in the resulting btrfs volume. This can be used to undo the conversion or deleted to free up space and make the conversion permanent.

   That is absolutely wild.

   https://github.com/maharmstone/ntfs2btrfs

   #Linux

   • Haelwenn /элвэн/ :triskell: and Puniko ? like this.
   • Embed this notice
     argv minus one (argv_minus_one@mastodon.sdf.org)'s status on Sunday, 01-Dec-2024 17:49:14 JST argv minus one

     in reply to

     Btrfs is copy-on-write, so keeping an image of the original NTFS does *not* involve duplicating every file on it. The blocks of the NTFS image are shared with the files on the new btrfs.

     Which, again, is wild. One file's contents can be *part of* another, much larger file's contents, without duplication (until one of them is written to).

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 01-Dec-2024 17:51:29 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @argv_minus_one Well for me it's kind of normal but I've been a ZFS user since at least 2007, so Copy-on-Write abilities are something I'm familiar with.