Hi Ted,
On Mon, Jul 1, 2019 at 3:56 PM Theodore Ts'o wrote:
> On Mon, Jul 01, 2019 at 02:43:14PM +0200, Geert Uytterhoeven wrote:
> > Despite this fix having been applied upstream, the kernel prints from
> > time to time:
> >
> > EXT4-fs (sda1): error count since last fsck: 5
> > EXT4-fs
On Mon, Jul 01, 2019 at 02:43:14PM +0200, Geert Uytterhoeven wrote:
> Hi Ted,
>
> Despite this fix having been applied upstream, the kernel prints from
> time to time:
>
> EXT4-fs (sda1): error count since last fsck: 5
> EXT4-fs (sda1): initial error at time 1557931133:
> ext4_get_branch
Hi Ted,
On Fri, May 17, 2019 at 6:44 PM Geert Uytterhoeven wrote:
> On Wed, May 15, 2019 at 6:57 AM Theodore Ts'o wrote:
> > Ah, I think I see the problem. Sorry, this one was my fault. Does
> > this fix things for you?
>
> Thanks!
> Sorry for missing this patch in the thread before.
>
> > Fro
Hi Ted,
On Wed, May 15, 2019 at 6:57 AM Theodore Ts'o wrote:
> Ah, I think I see the problem. Sorry, this one was my fault. Does
> this fix things for you?
Thanks!
Sorry for missing this patch in the thread before.
> From 0c72924ef346d54e8627440e6d71257aa5b56105 Mon Sep 17 00:00:00 2001
> Fro
Hi Ted,
On Sun, May 12, 2019 at 12:07 AM Theodore Ts'o wrote:
> On Sat, May 11, 2019 at 02:43:16PM +0200, Richard Weinberger wrote:
> > [CC'in linux-ext4]
> >
> > On Sat, May 11, 2019 at 1:47 PM Arthur Marsh
> > wrote:
> > >
> > >
> > > The filesystem with the kernel source tree is the root file
On Wed, May 15, 2019 at 09:42:11PM +0930, Arthur Marsh wrote:
> I have built kernels with the attached patch applied and run git gc
> on the patched kernels (both the 32 bit kernel on the Pentium-D and
> the 64 bit kernel on the Athlon II X4 640).
>
> There were a couple of warnings from other pro
On 15 May 2019 2:27:17 pm ACST, Theodore Ts'o wrote:
>Ah, I think I see the problem. Sorry, this one was my fault. Does
>this fix things for you?
>
> - Ted
>
>From 0c72924ef346d54e8627440e6d71257aa5b56105 Mon Sep 17 00:00:00 2001
>From: Theodore Ts
Ah, I think I see the problem. Sorry, this one was my fault. Does
this fix things for you?
- Ted
>From 0c72924ef346d54e8627440e6d71257aa5b56105 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o
Date: Wed, 15 May 2019 00:51:19 -0400
Subject: [PATCH] ex
On 14 May 2019 11:29:37 am ACST, Arthur Marsh
wrote:
>Apologies, I had forgotten to
>
>git bisect - - hard origin/master
>
>I am still seeing the corruption leading to the invalid block error on
>5.1.0+ kernels on both my machines.
>
>Arthur.
After the mm commits, the 32 bit kernel on Pentiu
On Tuesday 14 May 2019, Arthur Marsh wrote:
> Apologies, I had forgotten to
>
> got bisect - - hard origin/master
>
> I am still seeing the corruption leading to the invalid block error on 5.1.0+
> kernels on both my machines.
>
> Arthur.
I've been probably hit by the same bug. ext3 filesyste
Apologies, I had forgotten to
got bisect - - hard origin/master
I am still seeing the corruption leading to the invalid block error on 5.1.0+
kernels on both my machines.
Arthur.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
After a git bisect reset and updating to the current Linus git head, the
problem no longer occurs.
Thanks for the feedback on the problem that I experienced.
Arthur.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Sat, May 11, 2019 at 02:43:16PM +0200, Richard Weinberger wrote:
> [CC'in linux-ext4]
>
> On Sat, May 11, 2019 at 1:47 PM Arthur Marsh
> wrote:
> >
> >
> > The filesystem with the kernel source tree is the root file system, ext3,
> > mounted as:
> >
> > /dev/sdb7 on / type ext3 (rw,relatime,e
[CC'in linux-ext4]
On Sat, May 11, 2019 at 1:47 PM Arthur Marsh
wrote:
>
> I have yet to bisect, but have had trouble with recent, post 5.1.0 kernels
> built from Linus' git head on both i386 (Pentium 4 pc) and amd64 (Athlon II
> X4 640).
>
> The easiest way to trigger the problem is:
>
> git g
I have yet to bisect, but have had trouble with recent, post 5.1.0 kernels
built from Linus' git head on both i386 (Pentium 4 pc) and amd64 (Athlon II X4
640).
The easiest way to trigger the problem is:
git gc
on the kernel source tree, although the problem can occur without doing a git
gc.
15 matches
Mail list logo