On Thu, Apr 12, 2012 at 2:32 PM, David Sterba d...@jikos.cz wrote:
On Thu, Apr 12, 2012 at 02:09:08PM +0300, Kasatkin, Dmitry wrote:
Where is it? Can you please point out?
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/16662
the relevant part:
-- a/fs/btrfs/super.c
+++
In the latest btrfs tools from git it's a typo:
ierdnac-hp ~ # btrfs|grep dafault
btrfs subvolume get-dafault path
btrfs subvolume set-dafault subvolid path
ierdnac-hp ~ #
Andrei
--
Andrei Popa
NOC Manager - Nextgen Communications
0760 683 280
smime.p7s
Description: S/MIME
In normal cases, we would not be allowed to do balance in RO mode.
However, when we're using a seeding device and adding another device to sprout,
things will change:
$ mkfs.btrfs /dev/sdb7
$ btrfstune -S 1 /dev/sdb7
$ mount /dev/sdb7 /mnt/btrfs -o ro
$ btrfs fi bal /mnt/btrfs
Hello,
In the btrfs wiki
( https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories ) it
says:
Hugo Mills maintains an integration branch of all the patches for the
userspace tools that have been seen on the mailing list. There are two
important branches in this repository. For stable
On Friday 11 May 2012 19:26:16 Andrei Popa wrote:
In the latest btrfs tools from git it's a typo:
I'll send a patch now.
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see:
Andrei Popa reported that there were two typos of default as dafault,
this patch fixes those two typos up.
Signed-off-by: Chris Samuel ch...@csamuel.org
---
cmds-subvolume.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/cmds-subvolume.c b/cmds-subvolume.c
index
On Thu, May 10, 2012 at 04:35:23PM -0400, Josef Bacik wrote:
On Fri, Apr 27, 2012 at 01:02:08PM +0200, Christian Brunner wrote:
Am 24. April 2012 18:26 schrieb Sage Weil s...@newdream.net:
On Tue, 24 Apr 2012, Josef Bacik wrote:
On Fri, Apr 20, 2012 at 05:09:34PM +0200, Christian Brunner
2012/5/10 Josef Bacik jo...@redhat.com:
On Fri, Apr 27, 2012 at 01:02:08PM +0200, Christian Brunner wrote:
Am 24. April 2012 18:26 schrieb Sage Weil s...@newdream.net:
On Tue, 24 Apr 2012, Josef Bacik wrote:
On Fri, Apr 20, 2012 at 05:09:34PM +0200, Christian Brunner wrote:
After running
On Fri, May 11, 2012 at 06:11:26PM +0800, Liu Bo wrote:
In normal cases, we would not be allowed to do balance in RO mode.
However, when we're using a seeding device and adding another device to
sprout,
things will change:
$ mkfs.btrfs /dev/sdb7
$ btrfstune -S 1 /dev/sdb7
$ mount
Hi Josef,
Am 11.05.2012 15:31, schrieb Josef Bacik:
That previous patch was against btrfs-next, this patch is against 3.4-rc6 if you
are on mainline. Thanks,
I tried your patch against mainline, after a few minutes I hit this bug.
[ 1078.523655] [ cut here ]
[
On Fri, May 11, 2012 at 09:06:31AM +0300, Kasatkin, Dmitry wrote:
On Thu, Apr 12, 2012 at 2:32 PM, David Sterba d...@jikos.cz wrote:
On Thu, Apr 12, 2012 at 02:09:08PM +0300, Kasatkin, Dmitry wrote:
Where is it? Can you please point out?
On Fri, May 11, 2012 at 08:33:34PM +0200, Martin Mailand wrote:
Hi Josef,
Am 11.05.2012 15:31, schrieb Josef Bacik:
That previous patch was against btrfs-next, this patch is against 3.4-rc6 if
you
are on mainline. Thanks,
I tried your patch against mainline, after a few minutes I hit
Hello,
There seems to be a 256 MiB lower limit on device size : mkfs.btrfs
refuses to create a filesystem
on a device that is smaller than that.
I'm interested in using the btrfs RAID facility to provide redundancy
for an embedded system, but I can't afford
two 256 MiB partitions.
What are the
On Fri, May 11, 2012 at 03:57:24PM -0400, Berke Durak wrote:
There seems to be a 256 MiB lower limit on device size : mkfs.btrfs
refuses to create a filesystem on a device that is smaller than that.
I've noticed the same. I'm interested in researching the patterns the
filesystem puts down on an
I think I may have found a workaround.
One very interesting use of dm-zero is for creating sparse devices in
conjunction with dm-snapshot. A sparse device reports a device-size
larger than the amount of actual storage space
available for that device. A user can write data anywhere within the
On Fri, May 11, 2012 at 4:50 PM, Aaron Toponce
aaron.topo...@gmail.com wrote:
I've noticed the same. I'm interested in researching the patterns
the filesystem puts down on an encrypted container, but would like
to use 1MB files as the block device for the filesystem. Looking for
patterns in
Unfortunately nothing guarantees that the footprint of the filesystem
will stay bounded.
In other words, even if the number of blocks occupied by the
filesystem at any time is less than the capacity of the physical
device backing the sparse device, the total number of blocks ever
occupied by the
17 matches
Mail list logo