Thomas Mohr posted on Thu, 06 Dec 2018 12:31:15 +0100 as excerpted:
> We wanted to convert a file system to a RAID0 with two partitions.
> Unfortunately we had to reboot the server during the balance operation
> before it could complete.
>
> Now following happens:
>
> A mount attempt of the
Dear developers of BTRFS,
we have a problem. We wanted to convert a file system to a RAID0 with
two partitions. Unfortunately we had to reboot the server during the
balance operation before it could complete.
Now following happens:
A mount attempt of the array fails with following error
it a helper
> function and use it to log the balance operations.
>
> Kernel logs are very important for the forensic investigations of the
> issues, these patchs make balance logs easy to review.
>
> Anand Jain (3):
> btrfs: add helper function describe_block_group()
>
patchs make balance logs easy to review.
Anand Jain (3):
btrfs: add helper function describe_block_group()
btrfs: balance: add args info during start and resume
btrfs: balance: add kernel log for end or paused
fs/btrfs/relocation.c | 30 +--
fs/btrfs/volume
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
Signed-off-by: Anand Jain
---
v5->v6: Quite soul. nothing.
v4->v5: nothing.
v3->v4: nothing.
v2->v3: nothing.
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c | 7 +++
1 file changed, 7 insertions(+)
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
->btrfs bal start -f -mprofiles=raid1,convert=single,soft
-dlimit=10..20,usage=50 /btrfs
kernel: BTRFS info (device sdb): balance: start -f
On 11/20/2018 01:07 AM, David Sterba wrote:
On Wed, Nov 14, 2018 at 09:17:11PM +0800, Anand Jain wrote:
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
->btrfs bal start -f
On Wed, Nov 14, 2018 at 09:17:11PM +0800, Anand Jain wrote:
> Balance arg info is an important information to be reviewed for the
> system audit. So this patch adds them to the kernel log.
>
> Example:
> ->btrfs bal start -f -mprofiles=raid1,convert=single,soft
> -dlimit=10..20,usage=50 /btrfs
>
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
Signed-off-by: Anand Jain
---
v4->v5: nothing.
v3->v4: nothing.
v2->v3: nothing.
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c | 7 +++
1 file changed, 7 insertions(+)
diff --git
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
->btrfs bal start -f -mprofiles=raid1,convert=single,soft
-dlimit=10..20,usage=50 /btrfs
kernel: BTRFS info (device sdb): balance: start -f
function and use it to log the balance operations.
Kernel logs are very important for the forensic investigations of the
issues, these patchs make balance logs easy to review.
Anand Jain (3):
btrfs: add helper function describe_block_group()
btrfs: balance: add args info during start and resum
On 05/31/2018 05:47 PM, David Sterba wrote:
On Fri, May 25, 2018 at 11:05:47AM +0800, Anand Jain wrote:
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
->btrfs bal start -f
On Mon, Jun 25, 2018 at 01:07:10PM -0400, Austin S. Hemmelgarn wrote:
> > - mount -o recovery still hung
> > - mount -o ro did not hang though
> One tip here specifically, if you had to reboot during a balance and the FS
> hangs when it mounts, try mounting with `-o skip_balance`. That should
>
On 2018-06-25 12:07, Marc MERLIN wrote:
On Tue, Jun 19, 2018 at 12:58:44PM -0400, Austin S. Hemmelgarn wrote:
In your situation, I would run "btrfs pause ", wait to hear from
a btrfs developer, and not use the volume whatsoever in the meantime.
I would say this is probably good advice. I
t fully remember at this point, I keep notes, but not
detailled enough and it's been a little while.
I know I've had to delete/recreate this filesystem twice already over
the last years, but I'm not fully certain I remember when this one was
last wiped.
Yes, I do run balance along with scrub
On 06/25/2018 06:07 PM, Marc MERLIN wrote:
> On Tue, Jun 19, 2018 at 12:58:44PM -0400, Austin S. Hemmelgarn wrote:
>>> In your situation, I would run "btrfs pause ", wait to hear from
>>> a btrfs developer, and not use the volume whatsoever in the meantime.
>> I would say this is probably good
On Tue, Jun 19, 2018 at 12:58:44PM -0400, Austin S. Hemmelgarn wrote:
> > In your situation, I would run "btrfs pause ", wait to hear from
> > a btrfs developer, and not use the volume whatsoever in the meantime.
> I would say this is probably good advice. I don't really know what's going
> on
Austin S. Hemmelgarn posted on Tue, 19 Jun 2018 12:58:44 -0400 as
excerpted:
> That said, I would question the value of repacking chunks that are
> already more than half full. Anything above a 50% usage filter
> generally takes a long time, and has limited value in most cases (higher
> values
On 2018-06-19 12:30, james harvey wrote:
On Tue, Jun 19, 2018 at 11:47 AM, Marc MERLIN wrote:
On Mon, Jun 18, 2018 at 06:00:55AM -0700, Marc MERLIN wrote:
So, I ran this:
gargamel:/mnt/btrfs_pool2# btrfs balance start -dusage=60 -v . &
[1] 24450
Dumping filters: flags 0x1, state 0x0, f
On Tue, Jun 19, 2018 at 11:47 AM, Marc MERLIN wrote:
> On Mon, Jun 18, 2018 at 06:00:55AM -0700, Marc MERLIN wrote:
>> So, I ran this:
>> gargamel:/mnt/btrfs_pool2# btrfs balance start -dusage=60 -v . &
>> [1] 24450
>> Dumping filters: flags 0x1, state 0x0, fo
On Mon, Jun 18, 2018 at 06:00:55AM -0700, Marc MERLIN wrote:
> So, I ran this:
> gargamel:/mnt/btrfs_pool2# btrfs balance start -dusage=60 -v . &
> [1] 24450
> Dumping filters: flags 0x1, state 0x0, force is off
> DATA (flags 0x2): balancing, usage=60
> gargamel:/mnt/bt
So, I ran this:
gargamel:/mnt/btrfs_pool2# btrfs balance start -dusage=60 -v . &
[1] 24450
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=60
gargamel:/mnt/btrfs_pool2# while :; do btrfs balance status .; sleep 60; done
0 out of about 0 chunks balance
On Fri, May 25, 2018 at 11:05:47AM +0800, Anand Jain wrote:
> Balance arg info is an important information to be reviewed for the
> system audit. So this patch adds them to the kernel log.
>
> Example:
> ->btrfs bal start -f -mprofiles=raid1,convert=single,soft
> -dlimit=10..20,usage=50 /btrfs
>
On Mon, May 28, 2018 at 01:48:20PM +0800, Ethan Lien wrote:
> [Problem description and how we fix it]
> We should balance dirty metadata pages at the end of
> btrfs_finish_ordered_io, since a small, unmergeable random write can
> potentially produce dirty metadata which is multiple times larger
[Problem description and how we fix it]
We should balance dirty metadata pages at the end of
btrfs_finish_ordered_io, since a small, unmergeable random write can
potentially produce dirty metadata which is multiple times larger than
the data itself. For example, a small, unmergeable 4KiB write may
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
->btrfs bal start -f -mprofiles=raid1,convert=single,soft
-dlimit=10..20,usage=50 /btrfs
kernel: BTRFS info (device sdb): balance: start -f
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
->btrfs bal start -f -mprofiles=raid1,convert=single,soft
-dlimit=10..20,usage=50 /btrfs
kernel: BTRFS info (device sdb): balance: start force
On 05/24/2018 09:03 PM, David Sterba wrote:
On Wed, May 23, 2018 at 02:35:07PM +0800, Anand Jain wrote:
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
->btrfs bal start --full-balance -f
David Sterba 於 2018-05-23 00:28 寫到:
On Fri, Apr 27, 2018 at 03:05:24PM +0800, Ethan Lien wrote:
We should balance dirty metadata pages at the end of
btrfs_finish_ordered_io, since a small, unmergeable random write can
potentially produce dirty metadata which is multiple times larger than
the
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
Signed-off-by: Anand Jain
---
v3->v4: nothing.
v2->v3: nothing.
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c | 7 +++
1 file changed, 7 insertions(+)
diff --git
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
->btrfs bal start --full-balance -f -mprofiles=raid1,convert=single,soft
-dlimit=10..20,usage=50 /btrfs
kernel: BTRFS info (device sdc): balance: start -f -d
alance logs easy to review.
Anand Jain (3):
btrfs: add helper function describe_block_group()
btrfs: balance: add args info during start and resume
btrfs: balance: add kernel log for end or paused
fs/btrfs/relocation.c | 30 ++-
fs/btrfs/volumes.c
On 05/22/2018 08:35 PM, David Sterba wrote:
On Mon, May 21, 2018 at 02:37:44PM +0800, Anand Jain wrote:
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
-> btrfs bal start
On Fri, Apr 27, 2018 at 03:05:24PM +0800, Ethan Lien wrote:
> We should balance dirty metadata pages at the end of
> btrfs_finish_ordered_io, since a small, unmergeable random write can
> potentially produce dirty metadata which is multiple times larger than
> the data itself. For example, a
On Mon, May 21, 2018 at 02:37:44PM +0800, Anand Jain wrote:
> Balance arg info is an important information to be reviewed for the
> system audit. So this patch adds them to the kernel log.
>
> Example:
>
> -> btrfs bal start -dprofiles='raid1|single',convert=raid5
>
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
Signed-off-by: Anand Jain
---
v2->v3: nothing.
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/fs/btrfs/volumes.c
(3):
btrfs: add helper function describe_block_group()
btrfs: balance: add args info during start and resume
btrfs: balance: add kernel log for end or paused
fs/btrfs/relocation.c | 30 +-
fs/btrfs/volumes.c| 157 +-
fs/btrfs/volume
Balance arg info is an important information to be reviewed for the
system audit. So this patch adds them to the kernel log.
Example:
-> btrfs bal start -dprofiles='raid1|single',convert=raid5
-mprofiles='raid1|single',convert=raid5 /btrfs
kernel: BTRFS info (device sdb): balance: start
On 05/17/2018 08:06 PM, David Sterba wrote:
On Wed, May 16, 2018 at 10:51:28AM +0800, Anand Jain wrote:
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
Missing S-O-B.
oops. Fixed in v3.
---
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c |
On 05/17/2018 07:59 PM, David Sterba wrote:
On Wed, May 16, 2018 at 10:51:27AM +0800, Anand Jain wrote:
Balance args info is an important information to be reviewed for the
system audit. So this patch adds it to the kernel log.
Example:
-> btrfs bal start
On Wed, May 16, 2018 at 10:51:28AM +0800, Anand Jain wrote:
> Add a kernel log when the balance ends, either for cancel or completed
> or if it is paused.
Missing S-O-B.
> ---
> v1->v2: Moved from 2/3 to 3/3
>
> fs/btrfs/volumes.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git
On Wed, May 16, 2018 at 10:51:26AM +0800, Anand Jain wrote:
> Kernel logs are very important for the forensic investigations of the
> issues in general make it easy to use it. This patch adds 'balance:'
> prefix so that it can be easily searched.
>
> Signed-off-by: Anand Jain
On Wed, May 16, 2018 at 10:51:27AM +0800, Anand Jain wrote:
> Balance args info is an important information to be reviewed for the
> system audit. So this patch adds it to the kernel log.
>
> Example:
>
> -> btrfs bal start -dprofiles='raid1|single',convert=raid5
>
On Wed, May 16, 2018 at 10:57:57AM +0300, Nikolay Borisov wrote:
> On 16.05.2018 05:51, Anand Jain wrote:
> > Balance args info is an important information to be reviewed for the
> > system audit. So this patch adds it to the kernel log.
> >
> > Example:
> >
> > -> btrfs bal start
On 2018-05-16 09:23, Anand Jain wrote:
On 05/16/2018 07:25 PM, Austin S. Hemmelgarn wrote:
On 2018-05-15 22:51, Anand Jain wrote:
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
---
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c | 7 +++
1
On 05/16/2018 07:25 PM, Austin S. Hemmelgarn wrote:
On 2018-05-15 22:51, Anand Jain wrote:
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
---
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c | 7 +++
1 file changed, 7 insertions(+)
diff
On 2018-05-15 22:51, Anand Jain wrote:
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
---
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index
On 05/16/2018 03:57 PM, Nikolay Borisov wrote:
On 16.05.2018 05:51, Anand Jain wrote:
Balance args info is an important information to be reviewed for the
system audit. So this patch adds it to the kernel log.
Example:
-> btrfs bal start -dprofiles='raid1|single',convert=raid5
On 16.05.2018 05:51, Anand Jain wrote:
> Balance args info is an important information to be reviewed for the
> system audit. So this patch adds it to the kernel log.
>
> Example:
>
> -> btrfs bal start -dprofiles='raid1|single',convert=raid5
> -mprofiles='raid1|single',convert=raid5 /btrfs
>
On 16.05.2018 05:51, Anand Jain wrote:
> Add a kernel log when the balance ends, either for cancel or completed
> or if it is paused.
Reviewed-by: Nikolay Borisov
> ---
> v1->v2: Moved from 2/3 to 3/3
>
> fs/btrfs/volumes.c | 7 +++
> 1 file changed, 7 insertions(+)
>
On 16.05.2018 05:51, Anand Jain wrote:
> Kernel logs are very important for the forensic investigations of the
> issues in general make it easy to use it. This patch adds 'balance:'
> prefix so that it can be easily searched.
>
> Signed-off-by: Anand Jain
Add a kernel log when the balance ends, either for cancel or completed
or if it is paused.
---
v1->v2: Moved from 2/3 to 3/3
fs/btrfs/volumes.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index ce68c4f42f94..a4e243a29f5c 100644
---
Kernel logs are very important for the forensic investigations of the
issues in general make it easy to use it. This patch adds 'balance:'
prefix so that it can be easily searched.
Signed-off-by: Anand Jain
---
v1-v2: Change log update.
fs/btrfs/volumes.c | 34
Kernel logs are very important for the forensic investigations of the
issues, these patchs make balance logs easy to review.
Anand Jain (3):
btrfs: balance: prefix kernel logs
btrfs: balance: add args info during start and resume
btrfs: balance: add kernel log for end or paused
fs/btrfs
We should balance dirty metadata pages at the end of
btrfs_finish_ordered_io, since a small, unmergeable random write can
potentially produce dirty metadata which is multiple times larger than
the data itself. For example, a small, unmergeable 4KiB write may
produce:
16KiB dirty leaf (and
multi-queue or not?
>
Thank you. The install had defaulted to deadline.
I have now switched it to CFQ, and the system is much more
responsive/interactive now during a btrfs balance.
I will test it when I next get a chance, to see if that has helped me.
After reading about it:
deadline: more like
On 12/28/2017 12:15 PM, Nikolay Borisov wrote:
>
> On 23.12.2017 13:19, James Courtier-Dutton wrote:
>>
>> During a btrfs balance, the process hogs all CPU.
>> Or, to be exact, any other program that wishes to use the SSD during a
>> btrfs balance is blocked for lo
Am Thu, 28 Dec 2017 00:39:37 + schrieb Duncan:
>> I can I get btrfs balance to work in the background, without adversely
>> affecting other applications?
>
> I'd actually suggest a different strategy.
>
> What I did here way back when I was still on reiserfs o
On 23.12.2017 13:19, James Courtier-Dutton wrote:
> Hi,
>
> During a btrfs balance, the process hogs all CPU.
> Or, to be exact, any other program that wishes to use the SSD during a
> btrfs balance is blocked for long periods. Long periods being more
> than 5 seconds.
t I shouldn't have to...
>> On 23 December 2017 at 11:56, Alberto Bursi <alberto.bu...@outlook.it>
>> wrote:
>>>
>>> On 12/23/2017 12:19 PM, James Courtier-Dutton wrote:
>>>>
>>>> During a btrfs balance, the process hogs all CPU.
>>&g
Hi,
Thank you for your suggestion.
It does not help at all.
btrfs balance's behaviour seems to be unchanged by ionice.
It still takes 100% while working and starves all other processes of
disk access.
I can I get btrfs balance to work in the background, without adversely
affecting other
On 12/23/2017 12:19 PM, James Courtier-Dutton wrote:
> Hi,
>
> During a btrfs balance, the process hogs all CPU.
> Or, to be exact, any other program that wishes to use the SSD during a
> btrfs balance is blocked for long periods. Long periods being more
> than 5 seconds.
Hi,
During a btrfs balance, the process hogs all CPU.
Or, to be exact, any other program that wishes to use the SSD during a
btrfs balance is blocked for long periods. Long periods being more
than 5 seconds.
Is there any way to multiplex SSD access while btrfs balance is
operating, so that other
Markus Baier posted on Fri, 07 Apr 2017 16:17:10 +0200 as excerpted:
> Hello btrfs-list,
>
> today a strange behaviour appered during the btrfs balance process.
>
> I started a btrfs balance operation on the /home subvolume that
> contains, as childs, all the subvolumes for th
Hello btrfs-list,
today a strange behaviour appered during the btrfs balance process.
I started a btrfs balance operation on the /home subvolume
that contains, as childs, all the subvolumes for the home directories
of the users, every subvolume with it's own quota.
A short time after the start
1 conversion using the command
> btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/btrfs
>
> It was running OK, but then I restarted the computer without pausing
> the rebalance (I wasn't aware that would be necessary). Upon reboot,
> the system got stuck on the mounting opera
I had an 8TB btrfs filesystem setup with my data, and added a 4TB and
3TB drive to it and then ran a raid1 conversion using the command
btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/btrfs
It was running OK, but then I restarted the computer without pausing
the rebalance (I wasn't aware
t;> I didn't notice this until it was nearly too late. I had run out of
>> metadata space so I ran
>> btrfs balance start -v -dusage=0 /mnt/btrfsroot
>>
>> That went fine, but I was still low on metadata space, so I tried a
>> few variations:
>> btrfs balance
On Sun, Oct 09, 2016 at 04:59:04PM -0400, Jeremy Yoder wrote:
> I didn't notice this until it was nearly too late. I had run out of
> metadata space so I ran
> btrfs balance start -v -dusage=0 /mnt/btrfsroot
>
> That went fine, but I was still low on metadata space, so
I didn't notice this until it was nearly too late. I had run out of
metadata space so I ran
btrfs balance start -v -dusage=0 /mnt/btrfsroot
That went fine, but I was still low on metadata space, so I tried a
few variations:
btrfs balance start -v -dusage=1 /mnt/btrfsroot
btrfs balance start
On 2016-06-21 15:17, Graham Cobb wrote:
> On 21/06/16 12:51, Austin S. Hemmelgarn wrote:
>> The scrub design works, but the whole state file thing has some rather
>> irritating side effects and other implications, and developed out of
>> requirements that aren't present for balance (it might be
Le 21/06/2016 15:17, Graham Cobb a écrit :
> On 21/06/16 12:51, Austin S. Hemmelgarn wrote:
>> The scrub design works, but the whole state file thing has some rather
>> irritating side effects and other implications, and developed out of
>> requirements that aren't present for balance (it might be
On 21/06/16 12:51, Austin S. Hemmelgarn wrote:
> The scrub design works, but the whole state file thing has some rather
> irritating side effects and other implications, and developed out of
> requirements that aren't present for balance (it might be nice to check
> how many chunks actually got
On Tue, Jun 21, 2016 at 07:24:24AM -0400, Austin S. Hemmelgarn wrote:
> (for example, you can't easily start a balance on a remote
> system via a ssh command, which is the specific use case I have).
Wait, what?
ssh remotehost -n btrfs balance start -d... -m... /foo \&
or
d1 btrfs volume and decided to
> >>perform balancing so that data distributes "fairly" among drives. I have
> >>started "btrfs balance start", but it stalled for about 5-10 minutes
> >>intensively doing the work. After that time it has printed some
and decided to
perform balancing so that data distributes "fairly" among drives. I have
started "btrfs balance start", but it stalled for about 5-10 minutes
intensively doing the work. After that time it has printed something
like "had to relocate 50 chunks" and exited.
On 2016-06-21 04:55, Duncan wrote:
Dmitry Katsubo posted on Mon, 20 Jun 2016 18:33:54 +0200 as excerpted:
Dear btfs community,
I have added a drive to existing raid1 btrfs volume and decided to
perform balancing so that data distributes "fairly" among drives. I have
started &quo
Dmitry Katsubo posted on Mon, 20 Jun 2016 18:33:54 +0200 as excerpted:
> Dear btfs community,
>
> I have added a drive to existing raid1 btrfs volume and decided to
> perform balancing so that data distributes "fairly" among drives. I have
> started "btrfs
Dear btfs community,
I have added a drive to existing raid1 btrfs volume and decided to
perform balancing so that data distributes "fairly" among drives. I have
started "btrfs balance start", but it stalled for about 5-10 minutes
intensively doing the work. After that
depends on a number of factors. I
have no issues using my disks while they're being balanced (even hen
doing a full balance), but they also all support command queuing, and
are either fast disks, or on really good storage controllers.
3) My btrfs-balance-slowly script would work better i
tions are likely to be the things blocking for a really long time
(hours).
If this can occur, I think the warnings to users about balance need to
be extended to include this issue. Currently the user mode code warns
users that unfiltered balances may take a long time, but it doesn't warn
t
> -Original Message-
> From: linux-btrfs-ow...@vger.kernel.org [mailto:linux-btrfs-
> ow...@vger.kernel.org] On Behalf Of Graham Cobb
> Sent: Thursday, 19 May 2016 8:11 PM
> To: linux-btrfs@vger.kernel.org
> Subject: Re: [Not TLS] Re: Reducing impact of periodic btrfs
On 19/05/16 05:09, Duncan wrote:
> So to Graham, are these 1.5K snapshots all of the same subvolume, or
> split into snapshots of several subvolumes? If it's all of the same
> subvolume or of only 2-3 subvolumes, you still have some work to do in
> terms of getting down to recommended snapshot
Qu Wenruo posted on Thu, 19 May 2016 09:33:19 +0800 as excerpted:
> Graham Cobb wrote on 2016/05/18 14:29 +0100:
>> Hi,
>>
>> I have a 6TB btrfs filesystem I created last year (about 60% used). It
>> is my main data disk for my home server so it gets a lot of usage
>> (particularly mail). I do
never completed, of course. I
eventually got it cancelled.
I have since managed to complete the "balance -dusage=20" by running it
repeatedly with "limit=N" (for small N). I wrote a script to automate
that process, and rerun it every week. If anyone is interested, the
script is on G
> -Original Message-
> From: linux-btrfs-ow...@vger.kernel.org [mailto:linux-btrfs-
> ow...@vger.kernel.org] On Behalf Of Graham Cobb
> Sent: Wednesday, 18 May 2016 11:30 PM
> To: linux-btrfs@vger.kernel.org
> Subject: Reducing impact of periodic btrfs balance
>
&g
t
repeatedly with "limit=N" (for small N). I wrote a script to automate
that process, and rerun it every week. If anyone is interested, the
script is on GitHub: https://github.com/GrahamCobb/btrfs-balance-slowly
Out of that experience, I have a couple of thoughts about how to
poss
. I now have this in all fstabs. On the system in questionl, I
was able to sneak in a btrfs balance cancel before the system hanged
itself.
Mar 31 08:17:42 fan kernel: [ 240.595465] INFO: task kworker/u16:0:6 blocked
for more than 120 seconds.
Mar 31 08:17:42 fan kernel: [ 240.595604]
t: How to cancel btrfs balance on unmounted filesystem
Hi,
one of my problem btrfs instances went into a hung process state
while blancing metadata. This process is recorded in the file system
somehow and the balance restarts immediately after mounting the
filesystem with no chance to issue a btrfs b
On Thu, 31 Mar 2016 08:21:12 +0200
Marc Haber wrote:
> the balance restarts immediately after mounting
You can use the skip_balance mount option to prevent that.
--
With respect,
Roman
pgpGkbeeS9Inh.pgp
Description: OpenPGP digital signature
Hi,
one of my problem btrfs instances went into a hung process state
while blancing metadata. This process is recorded in the file system
somehow and the balance restarts immediately after mounting the
filesystem with no chance to issue a btrfs balance cancel command
before the system hangs again
Am Samstag, 5. Dezember 2015, 11:17:26 schrieb Holger Hoffstätte:
> On 12/05/15 11:04, Wolfgang Rohdewald wrote:
> > Am Samstag, 5. Dezember 2015, 10:58:44 schrieb Holger Hoffstätte:
> >> Please see: http://www.spinics.net/lists/linux-btrfs/msg49766.html
> >>
> >> You should be able to apply those
Unmodified Linux 4.3 tainted with nvidia
after adding disk #4 to RAID1, I did
btrfs filesystem balance /t4
Dec 5 08:07:26 s5 kernel: [55868.756847] BTRFS info (device sdc): relocating
block group 10768619667456 flags 17
Dec 5 08:07:35 s5 kernel: [55878.297200] BTRFS info (device sdc): found
On 12/05/15 10:09, Wolfgang Rohdewald wrote:
> Unmodified Linux 4.3 tainted with nvidia
>
> after adding disk #4 to RAID1, I did
>
> btrfs filesystem balance /t4
>
> Dec 5 08:07:26 s5 kernel: [55868.756847] BTRFS info (device sdc): relocating
> block group 10768619667456 flags 17
> Dec 5
Am Samstag, 5. Dezember 2015, 10:58:44 schrieb Holger Hoffstätte:
> Please see: http://www.spinics.net/lists/linux-btrfs/msg49766.html
>
> You should be able to apply those patches manually (assuming you can/want to
> rebuild).
>
are my data safe if I just wait for a fixed official kernel and
On 12/05/15 11:04, Wolfgang Rohdewald wrote:
> Am Samstag, 5. Dezember 2015, 10:58:44 schrieb Holger Hoffstätte:
>> Please see: http://www.spinics.net/lists/linux-btrfs/msg49766.html
>>
>> You should be able to apply those patches manually (assuming you can/want to
>> rebuild).
>
> are my data
Hi,
I'm running Kernel 4.3 and Btrfs-tools 4.3 on Debian Jessie. I compiled
the tools and kernel myself.
Recently I added a new disk to my btrfs volume and wanted to proceed to
convert from single to raid1.
Unfortunately the new disk seems to be faulty and started throwing a lot
of errors.
The
Hi again,
I've been browsing through the mailing list and I came across a patch
that might solve my issue a lot easier.
Specifically "[PATCH 02/15] btrfs: Do per-chunk check for mount time
check" by Qu Wenruo
I'm a bit at a loss as to how to apply that patch. Since I'm not even
sure for which
delete some of my snapshots, balancing is working...
Maybe this is a hint for bugfixing!!
Do you think?
greez
Jakob
Am 2015-10-21 um 22:51 schrieb Kyle Manna:
> I had a number of similar btrfs balance crashes in the past few days,
> but the disk wasn't full. You should try tailing the
alance a
> data block group, and something like 4+ hours to balance some of the
> metadata block groups. While it's "stuck" like that, it is actually
> making progress, but it doesn't look like it.
I know, balancint takes a huge amount of time. So my command is:
/bin/btrfs balance start
1 - 100 of 353 matches
Mail list logo