From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14422] EXT4 is corrupted after clean shutdown
Date: Fri, 16 Oct 2009 23:44:13 GMT [thread overview]
Message-ID: <200910162344.n9GNiDX9023928@demeter.kernel.org> (raw)
In-Reply-To: <bug-14422-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14422
Eric Sandeen <sandeen@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@redhat.com
--- Comment #3 from Eric Sandeen <sandeen@redhat.com> 2009-10-16 23:44:12 ---
When stating that a filesystem is corrupted, please offer some indication of
why you believe this to be true; kernel messages indicating on-disk problems,
fsck output, or at least the behavior you see which indicates corruption.
Otherwise there is simply not enough information to begin any investigation.
If those latest used files are corrupted - how are they corrupted? missing?
short? full of junk? unreadable? or what?
Thanks,
-Eric
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-10-16 23:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 18:31 [Bug 14422] New: EXT4 is corrupted after clean shutdown bugzilla-daemon
2009-10-16 18:33 ` [Bug 14422] " bugzilla-daemon
2009-10-16 18:33 ` bugzilla-daemon
2009-10-16 23:44 ` bugzilla-daemon [this message]
2009-10-17 7:03 ` bugzilla-daemon
2009-10-22 13:01 ` bugzilla-daemon
2009-10-22 14:54 ` bugzilla-daemon
2009-10-23 9:11 ` bugzilla-daemon
2009-10-27 10:01 ` bugzilla-daemon
2009-10-27 10:16 ` [Bug 14422] New: " Aneesh Kumar K.V
2009-10-27 11:47 ` [Bug 14422] " 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=200910162344.n9GNiDX9023928@demeter.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).