On Wed, Mar 16, 2016 at 5:20 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
On 03/16/2016 09:04 AM, Andrei Borzenkov wrote:
On Wed, Mar 16, 2016 at 3:55 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
That's the whole point: with BtrFS there is *no* partitioning, its all one file system. There are no boundaries.
There are, on subvolume granularity.
Could you explain that and illustrate it please.
It is illustrated by default openSUSE install and explained many times in this thread.
Some people seem to consider this a good thing. While I can see why, I personally don't. I think that being unconstrained leads to poor operational discipline.
"No partitions" does not automatically imply "unconstrained".
The assertion made elsewhere that this is all one file system so that a subvolume is allocated space from the general 'pool' as files are created there is something that I take to be 'unconstrained'.
If there is a way to limit the number of files in a subvolume (aka the
btrfs does not limit number of created files by design.
number of inodes or inode/data ratio), or the amount of space those files can take up before a limit is forcible imposed, I would like an explanation of 'how'.
I already answered it in this very thread. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org