From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12151] Unexplained fsck errors on a ext4 filesystem
Date: Fri, 1 May 2009 13:52:35 GMT [thread overview]
Message-ID: <200905011352.n41DqZqj014119@demeter.kernel.org> (raw)
In-Reply-To: <bug-12151-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12151
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #8 from Theodore Tso <tytso@mit.edu> 2009-05-01 13:52:35 ---
We're desperately looking for a reliable reproduction case for this problem.
My suggestion at this point is if you have a large filesystem (the reports for
this seem to come from users with > 1TB filesystems) to take a periodic e2image
backup of your filesystem before the corruption, and save it on some other
filesystem so there is a backup of your filesystem metadata. This will help
recover the filesystem after the corruption.
If you can reproduce this reliably, please let us know. We haven't been able
to get this problem reproduced yet.
--
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-05-01 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 21:38 [Bug 12151] New: Unexplained fsck errors on a ext4 filesystem bugme-daemon
2008-12-11 2:33 ` [Bug 12151] " bugme-daemon
2009-01-18 2:24 ` bugme-daemon
2009-01-18 21:30 ` bugme-daemon
2009-03-04 5:41 ` bugme-daemon
2009-03-04 5:43 ` bugme-daemon
2009-04-27 13:40 ` bugzilla-daemon
2009-04-30 9:10 ` bugzilla-daemon
2009-04-30 20:56 ` bugzilla-daemon
2009-05-01 13:52 ` bugzilla-daemon [this message]
2009-05-01 15:19 ` bugzilla-daemon
2009-05-02 16:29 ` bugzilla-daemon
2009-05-02 20:24 ` bugzilla-daemon
2009-05-02 22:14 ` 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=200905011352.n41DqZqj014119@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).