From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217605] unttached inode after power cut with orphan file feature enabled
Date: Wed, 28 Jun 2023 13:19:44 +0000 [thread overview]
Message-ID: <bug-217605-13602-rkNLihvqrQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217605-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217605
--- Comment #1 from Zhihao Cheng (chengzhihao1@huawei.com) ---
reproducer:
1. ./test.sh
[ 73.704796] inject err for ino 13 creation
[ 73.705523] wait commit journal
[ 75.741472] commit trans
[ 76.550550] reboot: Restarting system
2. mount /dev/sda temp
umount temp
[ 82.683096] orphan replay: reserve 13
3. fsck.ext4 -fn /dev/sda
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached zero-length inode 13. Clear? no
Unattached inode 13
Connect to /lost+found? no
Pass 5: Checking group summary information
/dev/sda: ********** WARNING: Filesystem still has errors **********
/dev/sda: 13/25584 files (0.0% non-contiguous), 12113/102400 block
--
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:[~2023-06-28 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 13:19 [Bug 217605] New: unttached inode after power cut with orphan file feature enabled bugzilla-daemon
2023-06-28 13:19 ` bugzilla-daemon [this message]
2023-06-28 13:20 ` [Bug 217605] " bugzilla-daemon
2023-06-28 13:20 ` bugzilla-daemon
2023-06-28 13:20 ` 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-217605-13602-rkNLihvqrQ@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).