still kworker at 100% cpu in all of device size allocated with chunks situations with write load

First: Happy New Year to you! Second: Take your time. I know its holidays for many. For me it means I easily have time to follow-up on this. Am Mittwoch, 16. Dezember 2015, 09:20:45 CET schrieb Qu Wenruo: > Chris Mason wrote on 2015/12/15 16:59 -0500: > > On Mon, Dec 14, 2015 at 10:08:16AM

still kworker at 100% cpu in all of device size allocated with chunks situations with write load (was: Re: Still not production ready)

Am Sonntag, 13. Dezember 2015, 15:19:14 CET schrieb Marc MERLIN: > On Sun, Dec 13, 2015 at 11:35:08PM +0100, Martin Steigerwald wrote: > > Hi! > > > > For me it is still not production ready. Again I ran into: > > > > btrfs kworker thread uses up 100% of a Sandybridge core for minutes on > >

still kworker at 100% cpu in all of device size allocated with chunks situations with write load (was: Re: Still not production ready)

Am Montag, 14. Dezember 2015, 10:08:16 CET schrieb Qu Wenruo: > Martin Steigerwald wrote on 2015/12/13 23:35 +0100: > > Hi! > > > > For me it is still not production ready. > > Yes, this is the *FACT* and not everyone has a good reason to deny it. > > > Again I ran into: > > > > btrfs kworker

Re: still kworker at 100% cpu in all of device size allocated with chunks situations with write load

Martin Steigerwald wrote on 2015/12/14 09:18 +0100: Am Montag, 14. Dezember 2015, 10:08:16 CET schrieb Qu Wenruo: Martin Steigerwald wrote on 2015/12/13 23:35 +0100: Hi! For me it is still not production ready. Yes, this is the *FACT* and not everyone has a good reason to deny it. Again

Re: still kworker at 100% cpu in all of device size allocated with chunks situations with write load

Hi Qu. I reply to the journal fs things in a mail with a different subject. Am Montag, 14. Dezember 2015, 16:48:58 CET schrieb Qu Wenruo: > Martin Steigerwald wrote on 2015/12/14 09:18 +0100: > > Am Montag, 14. Dezember 2015, 10:08:16 CET schrieb Qu Wenruo: > >> Martin Steigerwald wrote on