public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 215879] New: EXT4-fs error - __ext4_find_entry:1612: inode #2: comm systemd: reading directory lblock 0
Date: Sun, 24 Apr 2022 15:20:35 +0000	[thread overview]
Message-ID: <bug-215879-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=215879

            Bug ID: 215879
           Summary: EXT4-fs error - __ext4_find_entry:1612: inode #2: comm
                    systemd: reading directory lblock 0
           Product: File System
           Version: 2.5
    Kernel Version: 5.18.0-rc3
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: ionut_n2001@yahoo.com
        Regression: No

Hi Kernel Team,

I notice this issue:

EXT4-fs error - __ext4_find_entry:1612: inode #2: comm systemd: reading
directory lblock 0


I think this error is sporadic.


Drives:    Local Storage: total: 953.87 GiB used: 45.04 GiB (4.7%) 
           ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNU010TZ size: 953.87
GiB temp: 52.9 C 
Partition: ID-1: / size: 250.25 GiB used: 40.4 GiB (16.1%) fs: ext4 dev:
/dev/nvme0n1p2 
           ID-2: /boot/efi size: 252 MiB used: 274 KiB (0.1%) fs: vfat dev:
/dev/nvme0n1p1 
           ID-3: /home size: 678.39 GiB used: 4.65 GiB (0.7%) fs: ext4 dev:
/dev/nvme0n1p4 
Swap:      ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev:
/dev/nvme0n1p3 

OS: Debian 11/MXLinux KDE
Kernel: 5.18.0-rc3 vanilla

cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-5.18.0-1-generic
root=UUID=166304ea-bc80-458b-99a1-8a39a4e71a09 ro quiet splash clocksource=hpet
init=/lib/systemd/systemd

dpkg -l | grep -E "systemd|preload"
ii  libpam-systemd:amd64                          1:247.3-6mx21                
         amd64        system and service manager - PAM module
ii  libsystemd0:amd64                             1:247.3-6mx21                
         amd64        systemd utility library
ii  preload                                       0.6.4-5+b1                   
         amd64        adaptive readahead daemon
ii  systemd                                       1:247.3-6mx21                
         amd64        system and service manager
ii  systemd-shim                                  10-5                         
         amd64        shim for systemd

lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root
Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP
Bridge
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP
Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP
Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166a
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166b
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166c
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166d
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166e
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166f
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1670
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1671
01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060
Mobile / Max-Q] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1)
02:00.0 Network controller: MEDIATEK Corp. Device 7961
03:00.0 Non-Volatile memory controller: Intel Corporation Device f1aa (rev 03)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Cezanne (rev c4)
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High
Definition Audio Controller
04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h
(Models 10h-1fh) Platform Security Processor
04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB
3.1
04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB
3.1
04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD]
Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
10h-1fh) HD Audio Controller

CPU Model name:                      AMD Ryzen 9 5900HS with Radeon Graphics

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-04-24 15:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 15:20 bugzilla-daemon [this message]
2022-04-24 15:23 ` [Bug 215879] EXT4-fs error - __ext4_find_entry:1612: inode #2: comm systemd: reading directory lblock 0 bugzilla-daemon
2022-04-24 15:31 ` bugzilla-daemon
2022-04-25  4:12 ` bugzilla-daemon
2022-05-26 19:18 ` bugzilla-daemon
2023-02-19 14:30 ` bugzilla-daemon
2023-02-19 23:16 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-215879-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox