From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 121371] fsck created undeletable directory
Date: Sun, 10 Jul 2016 13:58:56 +0000 [thread overview]
Message-ID: <bug-121371-13602-sRliJaaQ5g@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-121371-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=121371
Grief <iamgrief@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Grief <iamgrief@gmail.com> ---
Navin, thank you for finding the time to look and answer! I'll follow your
advice and close this. But in this case, I'd like to understand, isn't it the
bug of fsck that it didn't fix that?
Also, I'll give debugfs a try, however, I've never used it before.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-07-10 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 15:41 [Bug 121371] New: fsck created undeletable directory bugzilla-daemon
2016-07-03 15:45 ` [Bug 121371] " bugzilla-daemon
2016-07-03 16:03 ` bugzilla-daemon
2016-07-03 18:38 ` bugzilla-daemon
2016-07-03 18:43 ` bugzilla-daemon
2016-07-04 10:46 ` bugzilla-daemon
2016-07-07 17:13 ` bugzilla-daemon
2016-07-10 13:58 ` bugzilla-daemon [this message]
2016-07-12 4:42 ` 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-121371-13602-sRliJaaQ5g@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).