On 06/26/2010 08:34 AM, Daniel Shiels wrote:
25.06.2010 22:58, Ric Wheeler wrote:
On 06/24/2010 06:06 PM, Daniel Taylor wrote:
[]
On Wed, Jun 23, 2010 at 8:43 PM, Daniel Taylor
daniel.tay...@wdc.com wrote:
Just an FYI reminder. The original test (2K files)
Daniel Taylor daniel.tay...@wdc.com writes:
As long as no object smaller than the disk block size is ever
flushed to media, and all flushed objects are aligned to the disk
blocks, there should be no real performance hit from that.
The question is just how large such a block needs to be.
Wheeler;
Andrew Morton; Linus Torvalds; The development of BTRFS
Subject: Re: Btrfs: broken file system design (was Unbound(?)
internal fragmentation in Btrfs)
On Wed, Jun 23, 2010 at 8:43 PM, Daniel Taylor
daniel.tay...@wdc.com wrote:
Just an FYI reminder. The original test (2K files
On Wed, 2010-06-23 at 20:43 -0700, Daniel Taylor wrote:
There is also the issue of btrfs over RAID (which I know is not
entirely sensible, but which will happen).
Well, we could discourage that by merging the RAID support that's been
pending for a while but I suspect Chris is a bit busy
; The development of BTRFS
Subject: Re: Btrfs: broken file system design (was Unbound(?)
internal fragmentation in Btrfs)
On Wed, Jun 23, 2010 at 8:43 PM, Daniel Taylor
daniel.tay...@wdc.com wrote:
Just an FYI reminder. The original test (2K files) is utterly
pathological for disk drives
Edward Shishkin wrote:
I have noticed that events in Btrfs develop by scenario not predicted
by the paper of academic Ohad Rodeh (in spite of the announce that
Btrfs is based on this paper). This is why I have started to grumble..
In btrfs, based on means started with the algorithm and ideas
Edward Shishkin wrote:
I'll try to help, but I am rather pessimistic here: working out
algorithms is something, which doesn't like timelines..
Nonsense. Working out algorithms is just work to an algorithm
designer, just like programming is work to a programmer. Sure, some
things are harder
Just an FYI reminder. The original test (2K files) is utterly
pathological for disk drives with 4K physical sectors, such as
those now shipping from WD, Seagate, and others. Some of the
SSDs have larger (16K0 or smaller blocks (2K). There is also
the issue of btrfs over RAID (which I know is
On Wed, Jun 23, 2010 at 8:43 PM, Daniel Taylor daniel.tay...@wdc.com wrote:
Just an FYI reminder. The original test (2K files) is utterly
pathological for disk drives with 4K physical sectors, such as
those now shipping from WD, Seagate, and others. Some of the
SSDs have larger (16K0 or
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin edw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs for using in enterprise
systems and the below are my first impressions (linux-2.6.33).
The first test I have made was filling an empty 659M (/dev/sdb2)
On Fri, Jun 18, 2010 at 1:32 PM, Edward Shishkin
edward.shish...@gmail.com wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin edw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs for using in enterprise
systems and the below are my first impressions
On Fri, Jun 18, 2010 at 03:32:16PM +0200, Edward Shishkin wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin edw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs for using in enterprise
systems and the below are my first impressions (linux-2.6.33).
Chris Mason wrote:
On Fri, Jun 18, 2010 at 03:32:16PM +0200, Edward Shishkin wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin edw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs for using in enterprise
systems and the below are my
On Fri, Jun 18, 2010 at 05:05:46PM +0200, Edward Shishkin wrote:
Chris Mason wrote:
On Fri, Jun 18, 2010 at 03:32:16PM +0200, Edward Shishkin wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin edw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs for
Chris Mason wrote:
On Fri, Jun 18, 2010 at 03:32:16PM +0200, Edward Shishkin wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkinedw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs for using in enterprise
systems and the below are my
On Fri, Jun 18, 2010 at 05:21:21PM +0200, Christian Stroetmann wrote:
Chris Mason wrote:
On Fri, Jun 18, 2010 at 03:32:16PM +0200, Edward Shishkin wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkinedw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs
Edward Shishkin wrote:
If you decide to base your file system on some algorithms then please
use the original ones from proper academic papers. DO NOT modify the
algorithms in solitude: this is very fragile thing! All such
modifications must be reviewed by specialists in the theory of
Chris Mason wrote:
On Fri, Jun 18, 2010 at 05:05:46PM +0200, Edward Shishkin wrote:
Chris Mason wrote:
On Fri, Jun 18, 2010 at 03:32:16PM +0200, Edward Shishkin wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin edw...@redhat.com wrote:
Daniel J Blueman wrote:
On Fri, Jun 18, 2010 at 1:32 PM, Edward Shishkin
edward.shish...@gmail.com wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin edw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs for using in enterprise
systems
On Fri, Jun 18, 2010 at 06:22:39PM +0200, Edward Shishkin wrote:
Chris Mason wrote:
On Fri, Jun 18, 2010 at 05:05:46PM +0200, Edward Shishkin wrote:
Chris Mason wrote:
On Fri, Jun 18, 2010 at 03:32:16PM +0200, Edward Shishkin wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin
Daniel J Blueman wrote:
On Fri, Jun 18, 2010 at 1:32 PM, Edward Shishkin
edward.shish...@gmail.com wrote:
Mat wrote:
On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkinedw...@redhat.com wrote:
Hello everyone.
I was asked to review/evaluate Btrfs for using in enterprise
Jamie Lokier wrote:
Edward Shishkin wrote:
If you decide to base your file system on some algorithms then please
use the original ones from proper academic papers. DO NOT modify the
algorithms in solitude: this is very fragile thing! All such
modifications must be reviewed by specialists in
Jamie Lokier wrote:
Edward Shishkin wrote:
If you decide to base your file system on some algorithms then please
use the original ones from proper academic papers. DO NOT modify the
algorithms in solitude: this is very fragile thing! All such
modifications must be reviewed by specialists in
On Fri, Jun 18, 2010 at 09:29:40PM +0200, Edward Shishkin wrote:
Jamie Lokier wrote:
Edward Shishkin wrote:
If you decide to base your file system on some algorithms then please
use the original ones from proper academic papers. DO NOT modify the
algorithms in solitude: this is very fragile
24 matches
Mail list logo
