From mboxrd@z Thu Jan  1 00:00:00 1970
From: xerofoify@gmail.com (Nick Krause)
Date: Thu, 21 Aug 2014 00:18:42 -0400
Subject: Help with btrfs project
In-Reply-To: <CAPDOMVgKXe7ngB5VZ7S7SPtvnviL2b9rHQAKQ6n8WWobkjLBTg@mail.gmail.com>
References: <CAPDOMVjj5_hjvWh2CokdOCs4t3tY-Q7gEcAnPufbgUiKswkinQ@mail.gmail.com>
	<CADVatmO2LCb-hvRqD3z7og5fAod6yr3q82egVk2=dOXMHXc=6Q@mail.gmail.com>
	<33643.1408535442@turing-police.cc.vt.edu>
	<CADVatmP_SOjekxpi7B_OL=YfMi2J-H3LzNOHkT2cvjQ8ubWEOQ@mail.gmail.com>
	<CAGqxwZjxgJLGTBL3pPP4dSBoMAZfKdqaMHbOhTmRvmiFZJDTcg@mail.gmail.com>
	<CAC+QLdQ-Afj=Ab-CSL3-A-myd16_W=k9E7EY9cLuoh0B9LcZaw@mail.gmail.com>
	<CA+t4uCN8ih4H8aQ_adxh6zP4j=7_ft9RUCQfkx6AQu4wWqwj5g@mail.gmail.com>
	<CAPDOMVgcugZj2EX7_hW_91tnoH9Qof3jPcDqzgvWpLtst_Pnkw@mail.gmail.com>
	<53F4D9F0.9050200@gmail.com>
	<CAPDOMVgT2uTzCbFYEi2gmGNrt2k_QJhG+8p5tRzu6qKfEN-cHw@mail.gmail.com>
	<CAPDOMViAz6YbRamfZvpT69qzkPSjyuV6Tt_Q6dtouy2hhJ5MXg@mail.gmail.com>
	<CADVatmNX3YjmPTsQA7xPhaF_PpsP+trBXd0SR5tfQb9GaNsYRw@mail.gmail.com>
	<CAPDOMVhGea-ooaKwGXgrZoL=jGEM5-r=5QgYVnppje0qSa2Yig@mail.gmail.com>
	<1408580487.17932.28.camel@thorin>
	<CAPDOMVgKXe7ngB5VZ7S7SPtvnviL2b9rHQAKQ6n8WWobkjLBTg@mail.gmail.com>
Message-ID: <CAPDOMViiMBbXTik21pBFeC9yJj-3FfX3r=c0zxNZOA4Mp4qnKA@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Wed, Aug 20, 2014 at 10:47 PM, Nick Krause <xerofoify@gmail.com> wrote:
> On Wed, Aug 20, 2014 at 8:21 PM, Bernd Petrovitsch
> <bernd@petrovitsch.priv.at> wrote:
>> On Mit, 2014-08-20 at 17:25 -0400, Nick Krause wrote:
>>> On Wed, Aug 20, 2014 at 1:58 PM, Sudip Mukherjee
>>> <sudipm.mukherjee@gmail.com> wrote:
>> [...]
>>> > i asked a few questions . why dont you answer them and show every one that
>>> > you can.
>>> I may have deleted your email but , please send me your questions and
>>
>> It is *your* fault if *you* delete *your* mails, so fix it *youself*
>> and don't (try to) push effort to others - as you do from mail #2.
>>
>> How should *you* fix *your* immediate failure: Google the mails *you*
>> deleted or just search and find it one of the various archives of the
>> LKML.
>>
>> Sorry, you wasted too much time and bandwidth of everyone ....
>>
>>         Bernd
>> --
>> "I dislike type abstraction if it has no real reason. And saving
>> on typing is not a good reason - if your typing speed is the main
>> issue when you're coding, you're doing something seriously wrong."
>>     - Linus Torvalds
>>
> The areas for Sudip's questions are below.
> 1. Btrfs is suppose to replace ext4 as the default Linux file system
> due to ext4 having no
> features like sub volumes and build in compression. Over all due it's
> great features ZFS
> still is the default choice in the enterprise and data center space,
> but btrfs hows to challenge
> the reigning king and make btrfs the default, Oracle developers
> started this file system as
> their was no good file system on Linux with features like ZFS.
> 2. Btrfs  allows for unlimited files due to dynamic inode creation and
> not a fixed inode count.
> In addition in supports sub volumes and build in compression using
> certain compression
> algorithms. In addition most of it's design is build for large COW file systems.
> 3. Journaling is the ability of  a file system to keep a log of data
> and if the file system is not
> in a known good state , the file system will roll back the file system
> to the last known good
> state, mostly thought of as the file system log.
> 4. Btrfs does support this in a basic form but not as a tested and
> tried fsck online check for
> enterprise or critical workloads.
> Nick