All of lore.kernel.org
 help / color / mirror / Atom feed
From: Morey Roof <moreyroof@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: New feature Idea
Date: Wed, 13 Aug 2008 13:09:55 -0600	[thread overview]
Message-ID: <48A33183.7000305@gmail.com> (raw)
In-Reply-To: <48A32F68.90102@techmonkeys.org>

I was hoping to have it specified as a set of mount options or defaults 
controlled in the super block so that if you want to use it you can 
otherwise it doesn't exist.

-Morey

Jeff Fisher wrote:
>> Don't do it!!!
>>
>> OK, I know Chris has described some block sharing.  But I hate it.
>>
>> If I copy "resume" to "resume.save", it is because I want 2 copies
>> for safety.  I don't want the fs to reduce it to 1 copy.  And
>> reducing the duplicates is exactly opposite to Chris's paranoid
>> make-multiple-copies-by-default.
>>
>> Now feel free to tell me I'm an idiot (other people do) :)
>
> I would imagine that it would be optional and at worst, a specialized 
> fork of btrfs that follows the mainline but adds the deduplication bits.
>
> Jeff
>


  reply	other threads:[~2008-08-13 19:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 17:57 New feature Idea Morey Roof
2008-08-13 18:45 ` Jeff Fisher
2008-08-13 18:54 ` jim owens
2008-08-13 19:00   ` Jeff Fisher
2008-08-13 19:09     ` Morey Roof [this message]
2008-08-13 19:06   ` Joe Peterson
2008-08-13 19:28     ` jim owens
2008-08-13 19:40       ` Morey Roof
2008-08-13 19:28   ` btrfs-devel
2008-08-13 19:35     ` Kevin Cantu
2008-08-13 19:45       ` Morey Roof
2008-08-14 17:12   ` Chris Mason
2008-08-14 18:06     ` Anthony Roberts
2008-08-14 18:49     ` Zach Brown
2008-08-14 19:45       ` Morey Roof
2008-08-14 19:53       ` Chris Mason
2008-08-13 20:00 ` Andi Kleen
2008-08-13 20:10   ` Morey Roof

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=48A33183.7000305@gmail.com \
    --to=moreyroof@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.