Re: Balancing leaves when walking from top to down (was Btrfs:...)

2010-06-18 Thread Edward Shishkin
Ric Wheeler wrote: On 06/18/2010 06:04 PM, Edward Shishkin wrote: Chris Mason wrote: 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 p

Re: Balancing leaves when walking from top to down (was Btrfs:...)

2010-06-18 Thread Ric Wheeler
On 06/18/2010 06:04 PM, Edward Shishkin wrote: Chris Mason wrote: 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

Balancing leaves when walking from top to down (was Btrfs:...)

2010-06-18 Thread Edward Shishkin
Chris Mason wrote: 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

[PATCH] current btrfs-progs-unstable fails to compile

2010-06-18 Thread Bernhard Rosenkraenzer
Hi, current btrfs-progs-unstable fails to compile for me (Ark Linux devel branch, using gcc 4.5 and eglibc 2.12): /usr/bin/ld: btrfsck.o: in function maybe_free_inode_rec:btrfsck.c:323: error: undefined reference to 'S_ISDIR' /usr/bin/ld: btrfsck.o: in function maybe_free_inode_rec:btrfsck.c:340:

Re: default subvolume abilities/restrictions

2010-06-18 Thread C Anthony Risinger
On Sun, Jun 13, 2010 at 12:47 PM, C Anthony Risinger wrote: > On Sat, Jun 12, 2010 at 8:06 PM, C Anthony Risinger wrote: >> On Sat, Jun 12, 2010 at 7:22 PM, David Brown wrote: >>> On Sat, Jun 12, 2010 at 06:06:23PM -0500, C Anthony Risinger wrote: >>> > # btrfs subvolume create new_root

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Chris Mason
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 ver

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Edward Shishkin
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 t

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Christian Stroetmann
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

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Christian Stroetmann
Daniel J Blueman wrote: On Fri, Jun 18, 2010 at 1:32 PM, Edward Shishkin wrote: Mat wrote: On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin wrote: Hello everyone. I was asked to review/evaluate Btrfs for using in enterprise systems and the below are my first impressions (l

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Chris Mason
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

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Edward Shishkin
Daniel J Blueman wrote: On Fri, Jun 18, 2010 at 1:32 PM, Edward Shishkin wrote: Mat wrote: On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin wrote: Hello everyone. I was asked to review/evaluate Btrfs for using in enterprise systems and the below are my first impressions (linux

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Edward Shishkin
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 wrote: Hello everyone. I was

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Jamie Lokier
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 > alg

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Chris Mason
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 Shishkin wrote: > Hello everyone. > > I was asked to review/evaluat

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Christian Stroetmann
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 wrote: Hello everyone. I was asked to review/evaluate Btrfs for using in enterprise systems and the below are my first impressions

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Chris Mason
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 wrote: > Hello everyone. > > I was asked to review/evaluate Btr

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Edward Shishkin
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 wrote: Hello everyone. I was asked to review/evaluate Btrfs for using in enterprise systems and the below are my first impressions (li

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Chris Mason
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 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). > >>

Re: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Daniel J Blueman
On Fri, Jun 18, 2010 at 1:32 PM, Edward Shishkin wrote: > Mat wrote: >> >> On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin 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). >>> >>>

Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

2010-06-18 Thread Edward Shishkin
Mat wrote: On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin 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) btrfs partition (mo

Re: Unbound(?) internal fragmentation in Btrfs

2010-06-18 Thread Christian Stroetmann
Aloha Mat: On Thu, Jun 3, 2010 at 4:58 PM, Edward Shishkin 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) btrfs partition (m