From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12151] Unexplained fsck errors on a ext4 filesystem
Date: Thu, 30 Apr 2009 09:10:42 GMT [thread overview]
Message-ID: <200904300910.n3U9AgV0000783@demeter.kernel.org> (raw)
In-Reply-To: <bug-12151-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12151
Florian Engelhardt <flo@dotbox.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |flo@dotbox.org
--- Comment #6 from Florian Engelhardt <flo@dotbox.org> 2009-04-30 09:10:41 ---
Same problem here with 2.6.29.2
I have tried ext4 on a linux software raid 0, it was working flawlessly for
about a week. I booted the computer yesterday and hat exactly the same errors
as described above. Running e2fsck from a archlinux bootstick took about one
hour and left me with a mountable, but free of every kind of directory
structur, ext4 filesystem.
I am running that raid 0 on two 500GB Sata Disks. I can provide you with more
information on that this evening.
--
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-04-30 9:10 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 [this message]
2009-04-30 20:56 ` bugzilla-daemon
2009-05-01 13:52 ` bugzilla-daemon
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=200904300910.n3U9AgV0000783@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).