From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 220288] A typo Leads to loss of all data on disk
Date: Wed, 02 Jul 2025 19:36:32 +0000 [thread overview]
Message-ID: <bug-220288-13602-vEJc5C9RSX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220288-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220288
--- Comment #6 from Martin Vahi (martin.vahi@softf1.com) ---
Thank You for the answers. I guess the issue is then my expectation about how
the fsck.ext4 is supposed to be used. At the moment it seems to me that the
solution is that people with my use case should be using a use case specific
wrapper of fsck.ext4, not the very capable tool, fsck.ext4, directly. Thank You
for reading my comment.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-07-02 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 22:22 [Bug 220288] New: A typo Leads to loss of all data on disk bugzilla-daemon
2025-06-28 2:48 ` Theodore Ts'o
2025-06-28 2:48 ` [Bug 220288] " bugzilla-daemon
2025-06-28 8:47 ` bugzilla-daemon
2025-06-28 8:57 ` bugzilla-daemon
2025-06-28 9:37 ` bugzilla-daemon
2025-06-28 21:32 ` bugzilla-daemon
2025-06-28 21:39 ` bugzilla-daemon
2025-07-02 19:36 ` bugzilla-daemon [this message]
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-220288-13602-vEJc5C9RSX@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