> The question is, why is this important?
It probably isn't, its just my overactive sense of neatness ;-)
But, jokes aside, I am going to use the filesystem as it is now and
then when openSUSE 13.2 arrives I will give it another try with a new
kernel and new filesystem tools.
Thank you for y
Hi Stefan,
On Sat, Apr 26, 2014 at 11:28 PM, Chris Murphy 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 r
On Mon, Apr 28, 2014 at 01:57:02PM +0200, Stefan Malte Schumacher wrote:
>
>
> > So try this one:
> > btrfs balance start -musage=0 -v
>
> I fear that didn't work too.
>
> mars:/mnt # btrfs balance start -musage=0 -v btrfs/
> Dumping filters: flags 0x6, state 0x0, force is off
> METADATA (fl
> So try this one:
> btrfs balance start -musage=0 -v
I fear that didn't work too.
mars:/mnt # btrfs balance start -musage=0 -v btrfs/
Dumping filters: flags 0x6, state 0x0, force is off
METADATA (flags 0x2): balancing, usage=0
SYSTEM (flags 0x2): balancing, usage=0
Done, had to relocate
Stefan Malte Schumacher posted on Sun, 27 Apr 2014 17:37:26 +0200 as
excerpted:
> Chris and Duncan: I tried both your suggestions but unfortunately
> without success. Here is the output:
>
> mars:~ # btrfs balance start -susage=0 -f -v /mnt/btrfs/
> Dumping filters: flags 0xa, state 0x0, force is
Hello
Chris and Duncan: I tried both your suggestions but unfortunately
without success. Here is the output:
mars:~ # btrfs balance start -susage=0 -f -v /mnt/btrfs/
Dumping filters: flags 0xa, state 0x0, force is on
SYSTEM (flags 0x2): balancing, usage=0
Done, had to relocate 0 out of 2708 c
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
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
>
>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
11 matches
Mail list logo