All of lore.kernel.org
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (Nick Krause)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Help with btrfs project
Date: Thu, 21 Aug 2014 00:18:42 -0400	[thread overview]
Message-ID: <CAPDOMViiMBbXTik21pBFeC9yJj-3FfX3r=c0zxNZOA4Mp4qnKA@mail.gmail.com> (raw)
In-Reply-To: <CAPDOMVgKXe7ngB5VZ7S7SPtvnviL2b9rHQAKQ6n8WWobkjLBTg@mail.gmail.com>

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

  reply	other threads:[~2014-08-21  4:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  2:33 Help with btrfs project Nick Krause
2014-08-20  5:14 ` Sudip Mukherjee
2014-08-20 11:50   ` Valdis.Kletnieks at vt.edu
2014-08-20 12:11     ` Sudip Mukherjee
2014-08-20 15:46       ` Jason Conklin
2014-08-20 16:33         ` Mandeep Sandhu
2014-08-20 17:15           ` Lidza Louina
2014-08-20 17:20             ` Nick Krause
2014-08-20 17:24               ` Nick Krause
2014-08-20 17:25               ` Philipp Muhoray
2014-08-20 17:30                 ` Nick Krause
2014-08-20 17:33                   ` Nick Krause
2014-08-20 17:58                     ` Sudip Mukherjee
2014-08-20 21:25                       ` Nick Krause
2014-08-20 23:58                         ` Andrej Manduch
2014-08-20 23:59                         ` Andrej Manduch
2014-08-21  0:21                         ` Bernd Petrovitsch
2014-08-21  2:47                           ` Nick Krause
2014-08-21  4:18                             ` Nick Krause [this message]
2014-08-20 15:22     ` Philipp Muhoray
2014-08-20 11:49 ` Valdis.Kletnieks at vt.edu

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='CAPDOMViiMBbXTik21pBFeC9yJj-3FfX3r=c0zxNZOA4Mp4qnKA@mail.gmail.com' \
    --to=xerofoify@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.