On Thu 21-03-13 17:09:40, Ted Tso wrote:
> On Thu, Mar 21, 2013 at 09:46:38PM +0100, Jan Kara wrote:
> > Good catch! But shouldn't we rather fix jbd2_log_wait_commit() instead of
> > inventing new function?
>
> In most of the places where we call jbd2_log_start_
ation routines:
> */
>
> diff --git a/include/linux/jbd2.h b/include/linux/jbd2.h
> index 50e5a5e..f028975 100644
> --- a/include/linux/jbd2.h
> +++ b/include/linux/jbd2.h
> @@ -1200,6 +1200,7 @@ int __jbd2_log_start_commit(journal_t *journal, tid_t
> tid);
> i
pos_ratio);
> + }
> +
> /*
> * In the case of an unresponding NFS server and the NFS dirty
>* pages exceeds dirty_thresh, give the other good bdi's a pipe
--
Jan Kara
SUSE Labs, CR
--
To U
ot solve the PAE OOM issue.)
>
> Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
> School of Mathematics and Statistics University of SydneyAustralia
>
> Reported-by: Paul Szabo
> Reference: http://bugs.debian.org/695182
> Signed-off-by: Paul Szabo
Ah,
s list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Jan Kara
SUSE Labs, CR
--
To UNSUBSCRIBE, e
On Tue 30-08-11 19:26:22, Moffett, Kyle D wrote:
> On Aug 30, 2011, at 18:12, Jan Kara wrote:
> >> I can still trigger it on my VM snapshot very easily, so if you have
> >> anything
> >> you think I should test I would be very happy to give it a shot.
> >
&
debugging patch to
you. We spoke with Josef Bacik how errors like yours could happen so I have
some places to watch...
Honza
> On Jun 24, 2011, at 16:51, Kyle Moffett wrote:
> > On Jun 24, 2011, at 16:02, Jan Kara wrote:
>
or a while but so far I have no idea...
> Further discussion of the exact behavior of data-journalling below:
> On Jun 28, 2011, at 05:36, Jan Kara wrote:
> > On Mon 27-06-11 23:21:17, Moffett, Kyle D wrote:
>
> > Actually, normal desktop might be quite happy with non-journal
t; - This writes all data to the block device twice (once to the FS
> journal and once to the data blocks). This may be especially bad
> for write-limited Flash-backed devices.
Correct.
To sum up, the only additional guarantee data=journal offers against
data=ordered is a total or
ke
> this by saying, "oh, that feature should be deprecated".
No, I didn't want to dispense the bug report - we should definitely fix
the bug. I just remarked that data=journal is currently not well tested and
thus using it in production has its problems.
On Mon 27-06-11 13:16:50, Lukas Czerner wrote:
> On Fri, 24 Jun 2011, Jan Kara wrote:
>
> > On Fri 24-06-11 11:03:52, Moffett, Kyle D wrote:
> > > On Jun 24, 2011, at 09:46, Jan Kara wrote:
> > > > On Thu 23-06-11 16:19:08, Moffett, Kyle D wrote:
> > >
On Fri 24-06-11 11:03:52, Moffett, Kyle D wrote:
> On Jun 24, 2011, at 09:46, Jan Kara wrote:
> > On Thu 23-06-11 16:19:08, Moffett, Kyle D wrote:
> >> Besides which, line 534 in the Debian 2.6.32 kernel I am using is this
> >> one:
> >>
> >&g
s > 0);
The patch below might catch the problem closer to the place where it
happens...
Also possibly you can try current kernel whether the bug happens with it or
not.
Honza
--
Jan Kara
SUSE Labs, CR
diff -rupX /crypted/home/jack/.kerndiffexclude linux-2.6.32-SLE11-SP1
ix all the problems? So if you run fsck
-f -y several times in a row is keeps reporting problems? What kind of
problems is it?
Honza
> > -Original Message-
> > From: Jan Kara [mailto:j...@suse.cz]
> > Sent: T
14 matches
Mail list logo
