From: Alexey Fisher <bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
To: Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: ext4 corruptions
Date: Fri, 09 Oct 2009 21:20:13 +0200 [thread overview]
Message-ID: <1255116014.3014.8.camel@mini> (raw)
I have really bad ext4 corruptions, i needed to reinstall 3 of my test
systems.
The symptoms:
is use karmic beta for this with ubuntu supplied kernel 2.6.31 ... after
testing 2.6.32-rc[1-3] and booting again to 2.6.31 fsck will find some
bad things and will try to fix it. After this action is the system
unusable.
Do any one had same problem? The is no sans to bisect it, after some
jumps between 2.6.31 and 2.6.32 the system will be broken. Is it kernel
or fsck problem?
next reply other threads:[~2009-10-09 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 19:20 Alexey Fisher [this message]
2009-10-09 21:53 ` ext4 corruptions Jiri Kosina
2009-10-09 22:03 ` Eric Sandeen
[not found] ` <4ACFB337.8040109-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-10-10 7:29 ` Alexey Fisher
2009-10-10 0:33 ` Theodore Tso
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=1255116014.3014.8.camel@mini \
--to=bug-track-m18mab7tlt0ycq4ww13eyl6hyfs7nttn@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).