You are not logged in.

#1 2018-02-02 18:47:26

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

[Solved] Delayed block allocation failed for inode 399553

After updating to 4.14.16-1-LTS I  have this message in dmesg that was not there
in 4.9-LTS, I checked dmesg before upgrading.
I also have default kernel installed but boot the system a few times a month with it, always run LTS.
Looking back in the journal the message was only there after booting to default kernel not 4.9-LTS.
When I booted into 4.14.15-1-ARCH, I found it has the same message, and

[    2.933153] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    4.351546] EXT4-fs (sda2): re-mounted. Opts: data=ordered
[    4.590588] EXT4-fs (sda2): Delayed block allocation failed for inode 399553 at logical offset 316 with max blocks 2 with error 121
[    4.594053] EXT4-fs (sda2): This should not happen!! Data will be lost
[    5.907665] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
sudo find / -inum 399553 -print
/var/log/journal/6a4982853cd448eea9546b31bea4f1c4/system.journal

I should mention my system is upboard-z8350, the system is installed on a SSD connected trough USB3-OTG, it doesn't have SATA.
The controller is a Ewent ew7017 SATA to USB3 which is a cheap consumer model.
I have a second same setup running Debian server, swapping drive or controller yields  the same outcome.
How should I go about with this one and I take for granted 4.9-LTS was able to trace this issue?!

Last edited by qinohe (2018-05-03 15:39:02)

Offline

#2 2018-02-02 19:18:35

loqs
Member
Registered: 2014-03-06
Posts: 17,463

Re: [Solved] Delayed block allocation failed for inode 399553

If you downgrade to 4.9-lts does the error cease to be produced?  Have you run fsck on the filesystem?

Offline

#3 2018-02-02 20:48:29

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved] Delayed block allocation failed for inode 399553

Hey loqs thanks for your answer, and yes downgrading solves the issue.
The fsck is done with iso and is clean.
the used kernel & check:

Linux 4.14.14-1-ARCH x86_64
fsck from util-linux 2.31.1
/dev/sda2: clean 196598/1602496 files, 1804248/6400000 blocks

Offline

#4 2018-02-05 12:39:00

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved] Delayed block allocation failed for inode 399553

Offline

#5 2018-02-05 15:58:06

loqs
Member
Registered: 2014-03-06
Posts: 17,463

Re: [Solved] Delayed block allocation failed for inode 399553

Would suggest bisecting between 4.9 and 4.14 to find the bad commit then report the issue upstream.
Edit:
You may be able to save some time by trying prebuilt 4.10-4.13 kernels from the Arch_Linux_Archive.

Last edited by loqs (2018-02-05 21:35:40)

Offline

#6 2018-02-06 18:03:19

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved] Delayed block allocation failed for inode 399553

Hey loqs, I have build the Linux-git took me 10 hours on this hardware, without modprobed-db with ccache
should go faster the second time with modeprobed-db enabled in PKGBUILD. But,today there was a update 4.15.1-2 and this seems to have solved the problem and it also solves a kernel panic I got on LTS.
Time is always a point so if I have some I will use that archive you point at and try to figure out where it went wrong.
For now I go with default kernel. Btw. this is the message about the corrupt log file and it's nicely rotating.

systemd-journald[222]: /var/log/journal/6a4982853cd448eea9546b31bea4f1c4/system.journal: Journal file corrupted, rotating.

Offline

#7 2018-02-06 18:16:03

loqs
Member
Registered: 2014-03-06
Posts: 17,463

Re: [Solved] Delayed block allocation failed for inode 399553

That was the change for 4.15.1-2  https://git.archlinux.org/svntogit/pack … f953777688 was your device an NVME?
Edit:
Makepkg#Parallel_compilation can also reduce compile times.

Last edited by loqs (2018-02-06 18:24:56)

Offline

#8 2018-02-06 18:59:05

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved] Delayed block allocation failed for inode 399553

Could be but I am not sure, 4.15.1-1 has never been installed, could be that one too I think.
The disk is a SSD connected trough uSB3-otg adapter.
MAKEFLAGS =-j2 , I could set it to 4, it's a quad core compile would about half then, 5 hours -modprobed-db -ccache = ±3hours hmm still a lot but okay, if the calculation is about right anayway.

Offline

#9 2018-02-06 19:18:02

loqs
Member
Registered: 2014-03-06
Posts: 17,463

Re: [Solved] Delayed block allocation failed for inode 399553

Have a look in /var/log/pacman.log see if 4.15.1.-1 was installed if not it could be fixed by that instead of 4.15.1-2.  Glad to read the issue appears fixed.

Offline

#10 2018-02-06 21:43:01

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved] Delayed block allocation failed for inode 399553

No I did upgrade upgraded linux (4.14.15-1 -> 4.15.1-2) but I have installed 4.15.0-1 from the archives and the issue is solved with that one.
Really I have no idea where to start since there are a huge amount of commits for that kernel.
Thanks for the support loqs.

Offline

#11 2018-02-06 22:00:17

loqs
Member
Registered: 2014-03-06
Posts: 17,463

Re: [Solved] Delayed block allocation failed for inode 399553

So the original issue is still present on 4.14.17-1-LTS but not on 4.15.  I do not know which to suggest between continuing your current bisect or trying a reverse bisect between 4.14 and 4.15.

Offline

#12 2018-02-06 22:39:13

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved] Delayed block allocation failed for inode 399553

Correct yes thats the current situation. Ofcourse I could pretend I'm an ostrich put my head in the sand and think it will be backported for LTS too, but I guess it's better to find the commit so LTS can be patched too. What you think I can do best now?

Offline

#13 2018-02-06 22:56:16

loqs
Member
Registered: 2014-03-06
Posts: 17,463

Re: [Solved] Delayed block allocation failed for inode 399553

If the number of steps left is greater than 13 then I would do a reverse bisect between 4.14 and 4.15 but keep the previous git bisect directory as a backup.
Just doing a bisect between 4.14 and 4.15 here and that is 13 steps plus the two initial builds.
With the reverse bisect you can either report bad when the issue is not present and good when it is or see https://stackoverflow.com/questions/154 … ood-commit to change the terms.

Offline

#14 2018-05-03 15:33:43

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved] Delayed block allocation failed for inode 399553

Dear loqs,

The problem was solved after I had done an upgrade for the bios.
I am sorry for not getting back to this thread I forgot about it after having had all kind of issues with this board probably partially related to (before) the bios upgrade .
Thanks for your support
qinohe

Offline

Board footer

Powered by FluxBB