[447318.343158] [] ret_from_fork+0x42/0x70
[447318.343160] [] ? kthread_create_on_node+0x1a0/0x1a0
[447318.343161] ---[ end trace 3ba8d8d0d3b0be66 ]---
[447318.343166] BTRFS warning (device md50):
btrfs_run_delayed_refs:2821: Aborting unused transaction(No space left).
[447318.343187] BTRFS warning (device
(resending,... seems this hasn't gotten through to the list, when I've
sent it the first time)
Hi.
On Debian's 4.19.28-2 kernel (which includes the recent read-
corruption
on compression fix) the following happens:
As a consequence of the bug from the "Reproducer for "compressed data +
hole da
Anything I should do with respect to this?
I.e. is further debug info needed for an interested developer? or can I
simply scrap that particular image (which is not an important one)?
Cheers,
Chris.
On Sun, 2019-03-17 at 04:42 +0100, Christoph Anton Mitterer wrote:
> (resending,... seems this h
On 20/03/2019 01:59, Christoph Anton Mitterer wrote:
> Anything I should do with respect to this?
>
> I.e. is further debug info needed for an interested developer? or can I
> simply scrap that particular image (which is not an important one)?
OK, I can give it a shot, but please be aware I'm st
On Wed, 2019-03-20 at 10:59 +0100, Johannes Thumshirn wrote:
> First of all, have you tried a more recent kernel than the Debian
> kernels you referenced? E.g. Linus' current master or David's misc-
> next
> branch? Just so we don't try to hunt down a bug that's already fixed.
I haven't and that's
On Sat, 2019-04-13 at 00:46 +0200, Christoph Anton Mitterer wrote:
> If you repeat the above from the losetup point, but with -r ...
s/with -r/without -r/
On Sat, Apr 13, 2019 at 12:46:28AM +0200, Christoph Anton Mitterer wrote:
> On Wed, 2019-03-20 at 10:59 +0100, Johannes Thumshirn wrote:
> > First of all, have you tried a more recent kernel than the Debian
> > kernels you referenced? E.g. Linus' current master or David's misc-
> > next
> > branch?
Hey.
Just asking... was anyone able to reproduce these errors (as described
below)?
Cheers,
Chris.
On Sat, 2019-04-13 at 00:46 +0200, Christoph Anton Mitterer wrote:
> On Wed, 2019-03-20 at 10:59 +0100, Johannes Thumshirn wrote:
> > First of all, have you tried a more recent kernel than the Deb
Since no one seems to show any big interest in this issues, I've added
it for the records in https://bugzilla.kernel.org/show_bug.cgi?id=203621
Cheers,
Chris.
CPU):
6076 root 20 0 000 R 86 0.0 29:40.11 btrfs-delalloc-
How bad is it, doctor? I think I'll be going back to 3.2.16 for now though.
[100415.369301] BTRFS warning (device dm-0): Aborting unused transaction.
[100415.739337] BTRFS warning (device dm-0): Aborting u
On Tue, Jun 26, 2012 at 06:38:18PM -0700, Marc MERLIN wrote:
> Now, I'm also seeing these below and I have this again (86% CPU):
> 6076 root 20 0 000 R 86 0.0 29:40.11 btrfs-delalloc-
>
>
> How bad is it, doctor? I think I'll be going back to 3.2.16 for now though.
B
On Tue, Jun 26, 2012 at 10:20:12PM -0700, Marc MERLIN wrote:
> On Tue, Jun 26, 2012 at 06:38:18PM -0700, Marc MERLIN wrote:
> > Now, I'm also seeing these below and I have this again (86% CPU):
> > 6076 root 20 0 000 R 86 0.0 29:40.11
> > btrfs-delalloc-
> >
> > How ba
On Fri, Jun 29, 2012 at 05:36:24AM -0700, Marc MERLIN wrote:
> On Tue, Jun 26, 2012 at 10:20:12PM -0700, Marc MERLIN wrote:
> > On Tue, Jun 26, 2012 at 06:38:18PM -0700, Marc MERLIN wrote:
> > > Now, I'm also seeing these below and I have this again (86% CPU):
> > > 6076 root 20 0 0
On 07/03/2012 03:58 AM, Marc MERLIN wrote:
> On Fri, Jun 29, 2012 at 05:36:24AM -0700, Marc MERLIN wrote:
>> On Tue, Jun 26, 2012 at 10:20:12PM -0700, Marc MERLIN wrote:
>>> On Tue, Jun 26, 2012 at 06:38:18PM -0700, Marc MERLIN wrote:
Now, I'm also seeing these below and I have this again (86
745
> [84959.028005] .se->exec_start : 84959061.053899
> [84959.028005] .se->vruntime : 71921559.096778
> [84959.028005] .se->sum_exec_runtime : 2566083.226405
> [84959.028005] .se->load.weight : 2
> [84959.02
On 07/04/2012 11:15 PM, Marc MERLIN wrote:
> On Wed, Jul 04, 2012 at 01:58:31PM +0800, Liu Bo wrote:
>> > The dmesg log, sysrq log and stack dump info can usually be very helpful.
>> >
>> > From your report, we can see the csum error and hang on log,
>> > 'no csum' is not that bad while hanging-o
art 393216
[102232.968939] BTRFS warning (device dm-0): Aborting unused transaction.
[102234.107914] BTRFS warning (device dm-0): Aborting unused transaction.
[102235.218139] BTRFS warning (device dm-0): Aborting unused transaction.
I know I got corruption since I saw some of my files being dama
17 matches
Mail list logo
