Re: jbd2: don't wake kjournald unnecessarily

2013-01-23 Thread Jan Kara
On Wed 23-01-13 09:20:38, Eric Sandeen wrote: > On 1/23/13 3:44 AM, Jan Kara wrote: > > On Tue 22-01-13 19:37:46, Eric Sandeen wrote: > >> On 1/22/13 5:50 PM, Jan Kara wrote: > >>> On Mon 21-01-13 18:11:30, Ted Tso wrote: > On Tue, Jan 22, 2013 at 12:04:32AM +0100, Sedat Dilek wrote: > > >

Re: jbd2: don't wake kjournald unnecessarily

2013-01-23 Thread Eric Sandeen
On 1/23/13 3:44 AM, Jan Kara wrote: > On Tue 22-01-13 19:37:46, Eric Sandeen wrote: >> On 1/22/13 5:50 PM, Jan Kara wrote: >>> On Mon 21-01-13 18:11:30, Ted Tso wrote: On Tue, Jan 22, 2013 at 12:04:32AM +0100, Sedat Dilek wrote: > > Beyond the FUSE/LOOP fun, will you apply this patch t

Re: jbd2: don't wake kjournald unnecessarily

2013-01-23 Thread Jan Kara
On Tue 22-01-13 19:37:46, Eric Sandeen wrote: > On 1/22/13 5:50 PM, Jan Kara wrote: > > On Mon 21-01-13 18:11:30, Ted Tso wrote: > >> On Tue, Jan 22, 2013 at 12:04:32AM +0100, Sedat Dilek wrote: > >>> > >>> Beyond the FUSE/LOOP fun, will you apply this patch to your linux-next > >>> GIT tree? > >>

Re: jbd2: don't wake kjournald unnecessarily

2013-01-22 Thread Eric Sandeen
On 1/22/13 5:50 PM, Jan Kara wrote: > On Mon 21-01-13 18:11:30, Ted Tso wrote: >> On Tue, Jan 22, 2013 at 12:04:32AM +0100, Sedat Dilek wrote: >>> >>> Beyond the FUSE/LOOP fun, will you apply this patch to your linux-next GIT >>> tree? >>> >>> Feel free to add... >>> >>> Tested-by: Sedat Dile

Re: jbd2: don't wake kjournald unnecessarily

2013-01-22 Thread Jan Kara
On Mon 21-01-13 18:11:30, Ted Tso wrote: > On Tue, Jan 22, 2013 at 12:04:32AM +0100, Sedat Dilek wrote: > > > > Beyond the FUSE/LOOP fun, will you apply this patch to your linux-next GIT > > tree? > > > > Feel free to add... > > > > Tested-by: Sedat Dilek > > > > A similiar patch for JBD

Re: jbd2: don't wake kjournald unnecessarily

2013-01-21 Thread Theodore Ts'o
On Tue, Jan 22, 2013 at 12:04:32AM +0100, Sedat Dilek wrote: > > Beyond the FUSE/LOOP fun, will you apply this patch to your linux-next GIT > tree? > > Feel free to add... > > Tested-by: Sedat Dilek > > A similiar patch for JBD went through your tree into mainline (see [1] and > [2]).

Re: jbd2: don't wake kjournald unnecessarily

2013-01-21 Thread Sedat Dilek
On Mon, Jan 21, 2013 at 3:07 PM, Jan Kara wrote: > On Mon 21-01-13 13:30:26, Sedat Dilek wrote: >> On Mon, Jan 21, 2013 at 12:40 PM, Sedat Dilek wrote: >> > On Mon, Jan 21, 2013 at 11:47 AM, Jan Kara wrote: >> >> The traces don't suggest an ext4/jbd2 problem. What is happening is that >> >> jb

Re: jbd2: don't wake kjournald unnecessarily

2013-01-21 Thread Miklos Szeredi
On Mon, 2013-01-21 at 15:28 +0100, Sedat Dilek wrote: > On Mon, Jan 21, 2013 at 3:07 PM, Jan Kara wrote: > > Well, I think the outputs make it pretty clear. /dev/loop0 is a mounted > > image from fuse filesystem. Fuse daemon making filesystem accessible gets > > frozen before /dev/loop0 gets fu

Re: jbd2: don't wake kjournald unnecessarily

2013-01-21 Thread Sedat Dilek
On Mon, Jan 21, 2013 at 3:07 PM, Jan Kara wrote: > On Mon 21-01-13 13:30:26, Sedat Dilek wrote: >> On Mon, Jan 21, 2013 at 12:40 PM, Sedat Dilek wrote: >> > On Mon, Jan 21, 2013 at 11:47 AM, Jan Kara wrote: >> >> The traces don't suggest an ext4/jbd2 problem. What is happening is that >> >> jb

Re: jbd2: don't wake kjournald unnecessarily

2013-01-21 Thread Jan Kara
On Mon 21-01-13 13:30:26, Sedat Dilek wrote: > On Mon, Jan 21, 2013 at 12:40 PM, Sedat Dilek wrote: > > On Mon, Jan 21, 2013 at 11:47 AM, Jan Kara wrote: > >> The traces don't suggest an ext4/jbd2 problem. What is happening is that > >> jbd2 is waiting for IO to finish and that never happens. S

Re: jbd2: don't wake kjournald unnecessarily

2013-01-21 Thread Sedat Dilek
On Mon, Jan 21, 2013 at 12:40 PM, Sedat Dilek wrote: > On Mon, Jan 21, 2013 at 11:47 AM, Jan Kara wrote: >> On Sun 20-01-13 01:06:40, Sedat Dilek wrote: >>> On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote: >>> > Hi, >>> > >>> > I and some others hit a similiar problem in Linux-Next >>> > (ne

Re: jbd2: don't wake kjournald unnecessarily

2013-01-21 Thread Carlos Maiolino
On Mon, Jan 21, 2013 at 11:47:33AM +0100, Jan Kara wrote: > On Sun 20-01-13 01:06:40, Sedat Dilek wrote: > > On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote: > > > Hi, > > > > > > I and some others hit a similiar problem in Linux-Next > > > (next-20130118), please see [1] and [2]. > > > > > >

Re: jbd2: don't wake kjournald unnecessarily

2013-01-21 Thread Jan Kara
On Sun 20-01-13 01:06:40, Sedat Dilek wrote: > On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote: > > Hi, > > > > I and some others hit a similiar problem in Linux-Next > > (next-20130118), please see [1] and [2]. > > > > [3] has a interim analyze of my problems. > > > > After suspecting the pro

Re: jbd2: don't wake kjournald unnecessarily

2013-01-19 Thread Sedat Dilek
On Sun, Jan 20, 2013 at 1:35 AM, Sedat Dilek wrote: > On Sun, Jan 20, 2013 at 1:06 AM, Sedat Dilek wrote: >> On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote: >>> Hi, >>> >>> I and some others hit a similiar problem in Linux-Next >>> (next-20130118), please see [1] and [2]. >>> >>> [3] has a

Re: jbd2: don't wake kjournald unnecessarily

2013-01-19 Thread Sedat Dilek
On Sun, Jan 20, 2013 at 1:06 AM, Sedat Dilek wrote: > On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote: >> Hi, >> >> I and some others hit a similiar problem in Linux-Next >> (next-20130118), please see [1] and [2]. >> >> [3] has a interim analyze of my problems. >> >> After suspecting the pro

Re: jbd2: don't wake kjournald unnecessarily

2013-01-19 Thread Sedat Dilek
On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote: > Hi, > > I and some others hit a similiar problem in Linux-Next > (next-20130118), please see [1] and [2]. > > [3] has a interim analyze of my problems. > > After suspecting the problem was caused by TTY-NEXT, it turned out to > be a JBD2 probl

Re: jbd2: don't wake kjournald unnecessarily

2013-01-19 Thread Sedat Dilek
Hi, I and some others hit a similiar problem in Linux-Next (next-20130118), please see [1] and [2]. [3] has a interim analyze of my problems. After suspecting the problem was caused by TTY-NEXT, it turned out to be a JBD2 problem finally. The freezer/pm_test was helpful to hit the issue (Thanks