That looks quite interesting! Unfortunately this removes the ability to specify different RAID-levels for metadata vs data and actually behaves more like btrfs "single" mode. According to your link it fills drive by drive instead of distributing files equally across them:
"When you create a new file in the virtual filesystem, |mhddfs| will look at the free space, which remains on each of the drives. If the first drive has enough free space, the file will be created on that first drive." What I propose (simplest implementation): "When you create a new file in the filesystem, btrfswill look at used space on each of the drives. The file will be created on the drive with the least used space that can hold the file." Difference: mhddfs only achieves maximum recoverability once the filesystem is full (just like "single"), while my proposal achieves such recoverability from the start. (maximum recoverability by (totalDisks-failedDisks)/totalDisks as percentage of recoverable data/files (depending on by which the fs is balanced)) Also I'm not sure if it's compatible to btrfs's special remaining-space-calculation magic ^^ On 06.07.2015 18:45, Roman Mamedov wrote: > On Mon, 6 Jul 2015 18:22:52 +0200 > Johannes Pfrang <johannespfr...@gmail.com> wrote: > >> The simplest implementation would probably be something like: Always >> write files to the disk with the least amount of space used. I think >> this may be a valid software-raid use-case, as it combines RAID 0 (w/o >> some of the performance gains[2]) with recoverability of about half of >> the data/files (balanced by filled space or amount of files) in the >> event of a drive-failure[3] by using filesystem information a >> hardware-raid doesn't have. In the end this is more or less JBOD with >> balanced disk usage + filesystem intelligence. > mhddfs does exactly that: https://romanrm.net/mhddfs >
signature.asc
Description: OpenPGP digital signature
