Chris Murphy posted on Sat, 26 Apr 2014 15:28:03 -0600 as excerpted:
>>> btrfs balance start -dprofiles=single -mprofiles=single
>>> -sprofiles=single /mountpoint
>
>> After that btrfs fi df shows the following:
>>
>> Data, RAID1: total=2.64TiB, used=2.22TiB
>> System, RAID1: total=8.00MiB, us
Hi Linus,
Please pull these fixes from my for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Wang Shilong (3) commits (+24/-20):
Btrfs: avoid triggering bug_on() when we fail to start inode caching task
(+5/-1)
Btrfs: move btrfs_{set,clear}_
On Apr 26, 2014, at 12:18 PM, Stefan Malte Schumacher
wrote:
>>
>> They're harmless -- it's a side-effect of the way that mkfs works.
>> They'll go away if you balance them:
>>
>> btrfs balance start -dprofiles=single -mprofiles=single -sprofiles=single
>> /mountpoint
>
> btrfs refused
/me wonders if this
if (ret >= 0) {
/* Add an item for the type for the first time */
eb = path->nodes[0];
slot = path->slots[0];
offset = btrfs_item_ptr_offset(eb, slot);
} else if (ret == -EEXIST) {
/
>
>They're harmless -- it's a side-effect of the way that mkfs works.
> They'll go away if you balance them:
>
>btrfs balance start -dprofiles=single -mprofiles=single -sprofiles=single
> /mountpoint
btrfs refused this command, I had to pass --force to execute it.
It exited with this:Do
On Sat, Apr 26, 2014 at 04:09:15PM +0200, Stefan Malte Schumacher wrote:
> Hello
>
> Yesterday I created a btrfs-filesystem on two disk, using raid1 for
> data and metadata. I then mounted it and rsynced several TB of data
> onto it.
>
> mkfs.btrfs -m raid1 -d raid1 /dev/sdf /dev/sdg
>
> The com
Hello
Yesterday I created a btrfs-filesystem on two disk, using raid1 for
data and metadata. I then mounted it and rsynced several TB of data
onto it.
mkfs.btrfs -m raid1 -d raid1 /dev/sdf /dev/sdg
The command btrfs fi df /mnt/btrfs result in the following output:
Data, RAID1: total=2.64TiB, us
On 2014/04/16 05:22 PM, David Sterba wrote:
On Wed, Apr 16, 2014 at 04:59:09PM +0200, Brendan Hide wrote:
On 2014/04/16 03:40 PM, Chris Mason wrote:
So in my example with the automated tool, the tool really shouldn't be
deleting a snapshot where send is in progress. The tool should be told
tha
The mkfs.btrfs --features long option takes an argument but does not
declare it. Consequently getopt does not allocate an argument, which
makes an unconditional strdup() crash during options parsing.
Fix by declaring the argument in the options alias array.
Signed-off-by: Holger Hoffstätte
---
