ext4 filesystem does not use its badblock list

Bug #1723415 reported by Dima
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

1) Ubuntu 4.13.0-15.16-generic 4.13.4
2) Will be attached.
Always, when I have /dev/sdb2 mounted, I get an errors in the system log, such as in the file dmesg.txt (attached)(there are i/o errors and something).

Thus I ran fsck:
{
root@user:~# fsck.ext4 -fck /dev/sdb2
e2fsck 1.43.5 (04-Aug-2017)
Checking for bad blocks (read-only test): 0.24% done, 0:25done
/dev/sdb2: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Programming error? block #230376 claimed for no reason in process_bad_block.
Programming error? block #230385 claimed for no reason in process_bad_block.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sdb2: ***** FILE SYSTEM WAS MODIFIED *****
}

But the errors did not disappear and I ran "badblocks -so ./bads-sdb2.txt -b 4096 /dev/sdb2"
Then I tried "fsck.ext4 -l ./bads-sdb2.txt /dev/sdb2" and it showed, among other typical things, this:
{
Programming error? block #230376 claimed for no reason in process_bad_block.
Programming error? block #230385 claimed for no reason in process_bad_block.
}

Then I ran "dump2fs -b /dev/sdb2" and found that every block from bads-sdb2.txt is already included in there, but the errors keep appear.

And while I was searching for a solution, I found this:
https://sourceforge.net/p/e2fsprogs/bugs/187/

I think this situation can be found on Ubuntu 16.04 too.
Thank you.

1) Ubuntu Artful Aardvark (development branch) 17.10
2) 4.13.0.15.16

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-15-generic 4.13.0-15.16
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: user 2193 F.... pulseaudio
 /dev/snd/controlC1: user 2193 F.... pulseaudio
CurrentDesktop: LXDE
Date: Fri Oct 13 14:43:21 2017
HibernationDevice: RESUME=UUID=726f52b2-474f-4c2d-b220-5db2446da453
InstallationDate: Installed on 2017-10-06 (6 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
IwConfig:
 lo no wireless extensions.

 enp2s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-15-generic root=UUID=a0d2d217-37b4-4153-bb5c-c489bf5eb886 ro rootflags=subvol=@ quiet ipv6.disable=1
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-15-generic N/A
 linux-backports-modules-4.13.0-15-generic N/A
 linux-firmware 1.169
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: GA-880GM-UD2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd10/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GM-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Dima (dima2017) wrote :
Revision history for this message
Dima (dima2017) wrote :

lspci-vnvn.log

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Dima (dima2017) wrote :

I've tried to calculate somehow what block is on sector 50868652 and I got 6291509. Badblocks program successfully recognize this block as bad. And "dumpe2fs -b" shows it. But this block is touched again and again. And I think that means that messages "Programming error? block #?????? claimed for no reason in process_bad_block" are irrelevant to this issue. And that link I've mentioned is irrelevant too.

And I am going to attach full dumpe2fs output and "tune2fs -l". I hope it will help somehow. (The name of the disk is changed from sdb2 to sdc2 after reboot.)

Revision history for this message
Dima (dima2017) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc4

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
Dima (dima2017)
tags: added: kernel-bug-exists-upstream
Revision history for this message
Dima (dima2017) wrote :

Before Lubuntu 17.10 I used Lubuntu 16.04 and the bug exists there. I did "fsck.ext4 -fck" but it did not help. But I did not use "fsck.ext4 -l badblocks.txt"
I can't remember a version of kernel without this error. I thought it is normal for my hdd.
As you said, I've used 4.14.0-041400rc4.201710130854 kernel for testing and the bug exists on it too.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Dima (dima2017) wrote :

Thank you

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Dima (dima2017) wrote :

I did not use https://wiki.ubuntu.com/Bugs/Upstream/kernel, I just filled what I could on bugzilla.kernel.org. https://bugzilla.kernel.org/show_bug.cgi?id=197315

tags: added: kernel-bug-reported-upstream
Revision history for this message
Dima (dima2017) wrote :

United, unified, multi-targeted, interactive and automotive bug-tracking system is the most important thing the Universe should have.

Dima (dima2017)
tags: added: xenial
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.