From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Working on Btrfs as topic for master thesis
Date: Sun, 19 Jan 2014 21:44:39 -0800 [thread overview]
Message-ID: <lbid3r$1ui$1@ger.gmane.org> (raw)
In-Reply-To: <8E968DF3B7EC0D40B67B5A9D25675A6A03FC70@MBXSRV03EDU.edu.local>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 16/01/14 11:23, Toggenburger Lukas wrote:
> One of my ideas was to work on Btrfs.
One thing I would like see it automatic backup copies of data. For
example if you are only using 10% of the total space then make an
additional 9 copies of the data in the free space (low priority in the
background). As more space is used reclaim that dup/free space. The
principle especially applies when you have more than one device.
The goal is to ensure that all the space is used, and that there is the
maximum probability of data recovery.
If you are more interested in the theoretical side then looking into
compression would be interesting. ie how close to the theoretical best
compression are we. Various filesystems like btrfs and NTFS make all
sorts of compromises in algorithm choices but also especially in the size
of blocks they compress. How much better could be done?
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEARECAAYFAlLct8cACgkQmOOfHg372QTiNACgs1WNJF1tCM5boWP8L3obD0jU
4qsAnAjANq6TE6Gh5ATNbEGTmoA6/W+s
=YnrI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-01-20 5:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 19:23 Working on Btrfs as topic for master thesis Toggenburger Lukas
2014-01-17 15:34 ` David Sterba
2014-01-17 16:04 ` Tomasz Torcz
2014-01-18 12:50 ` Toggenburger Lukas
2014-01-22 12:05 ` David Sterba
2014-01-22 13:35 ` Hugo Mills
2014-01-20 5:44 ` Roger Binns [this message]
2014-01-22 12:12 ` David Sterba
2014-01-22 20:55 ` Roger Binns
2014-01-23 18:36 ` David Sterba
2014-01-23 21:47 ` Roger Binns
2014-01-20 12:20 ` Austin S Hemmelgarn
2014-01-21 6:42 ` Sandy McArthur
2014-01-21 12:25 ` Austin S Hemmelgarn
2014-01-21 16:52 ` Hugo Mills
2014-01-21 16:59 ` Austin S Hemmelgarn
2014-01-22 12:20 ` David Sterba
2014-01-22 12:24 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lbid3r$1ui$1@ger.gmane.org' \
--to=rogerb@rogerbinns.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox