From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 215879] EXT4-fs error - __ext4_find_entry:1612: inode #2: comm systemd: reading directory lblock 0
Date: Sun, 24 Apr 2022 15:31:58 +0000 [thread overview]
Message-ID: <bug-215879-13602-CFoIpUrRYA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215879-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215879
--- Comment #2 from sander44 (ionut_n2001@yahoo.com) ---
Created attachment 300796
--> https://bugzilla.kernel.org/attachment.cgi?id=300796&action=edit
photo bug
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent 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 [Bug 215879] New: EXT4-fs error - __ext4_find_entry:1612: inode #2: comm systemd: reading directory lblock 0 bugzilla-daemon
2022-04-24 15:23 ` [Bug 215879] " bugzilla-daemon
2022-04-24 15:31 ` bugzilla-daemon [this message]
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-CFoIpUrRYA@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;
as well as URLs for NNTP newsgroup(s).