From: Kapetanakis Giannis <bilias@edu.physics.uoc.gr>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: large filesystem corruptions
Date: Sat, 13 Mar 2010 15:19:23 +0200 [thread overview]
Message-ID: <4B9B90DB.4020809@edu.physics.uoc.gr> (raw)
In-Reply-To: <4B9B8DFC.30907@redhat.com>
On 13/03/10 15:07, Ric Wheeler wrote:
> I would agree that it would be key to try this on a newer kernel & on
> a 64 bit box. If you have an issue with a specific vendor release, you
> should open a ticket/bugzilla with that vendor so they can help you
> figure this out.
>
> ric
I will try Fedora 12/64bit on Monday when I have physical access.
Right now all tests have failed.
OS in Centos 5.4 x86 PAE so I opened a ticket both in Centos and Redhat
bugzilla.
I don't have any contract with redhat but I hope they will give a try on
this.
https://bugzilla.redhat.com/show_bug.cgi?id=573185
http://bugs.centos.org/view.php?id=4239
My feelings are that it has to do with the software raid layer and not
the filesystem (ext4, xfs, gfs all died).
The filesystem seems to not get the appropriate physical/logical
quandaries from the raid layer.
Unless the x86 kernel is not capable of addressing
large filesystems as it is documented (16TB as you said).
best regards,
Giannis
next prev parent reply other threads:[~2010-03-13 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 20:01 large filesystem corruptions Kapetanakis Giannis
2010-03-12 20:35 ` Ric Wheeler
2010-03-13 0:29 ` Kapetanakis Giannis
2010-03-13 0:55 ` Kapetanakis Giannis
2010-03-13 1:58 ` Michael Evans
2010-03-13 8:12 ` Kapetanakis Giannis
2010-03-13 9:25 ` Kapetanakis Giannis
2010-03-13 13:07 ` Ric Wheeler
2010-03-13 13:19 ` Kapetanakis Giannis [this message]
2010-03-16 10:02 ` Kapetanakis Giannis
2010-03-13 23:45 ` Bill Davidsen
2010-03-14 3:26 ` Kapetanakis Giannis
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=4B9B90DB.4020809@edu.physics.uoc.gr \
--to=bilias@edu.physics.uoc.gr \
--cc=linux-raid@vger.kernel.org \
--cc=rwheeler@redhat.com \
/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).