From: Bill Davidsen <davidsen@tmr.com>
To: Kapetanakis Giannis <bilias@edu.physics.uoc.gr>
Cc: Ric Wheeler <rwheeler@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: large filesystem corruptions
Date: Sat, 13 Mar 2010 18:45:48 -0500 [thread overview]
Message-ID: <4B9C23AC.5010404@tmr.com> (raw)
In-Reply-To: <4B9ADC61.7080007@edu.physics.uoc.gr>
Kapetanakis Giannis wrote:
> On 12/03/10 22:35, Ric Wheeler wrote:
>
>> This is probably an issue with the early version of ext4 you are using -
>> note that the support for ext4 > 16TB is still gated by some work done
>> up in the tools chain.
>>
>> Have you tried xfs?
>>
>> regards,
>>
>> Ric
>
> Thanks for answering,
>
> My filesystem would be 15 TB < 16 TB.
> GFS also crashed and burned so are you sure that this
> this is a problem with ext4?
> Would Fedora and newer kernel be better?
>
> On my tests the crashing filesystem was 7TB.
> When I added a second fs of 2 TB on lvm, so total > 8TB
> I had the crash.
>
> I did a new test now and didn't use GFT partitions
> but the whole physical/logical drives
>
> sdb -
> | ---> md0 ---> LVM ---> ext4 filesystems
> sdc -
>
> all sdb, sdc, md0 are gpt labeled without gpt partitions
> inside. No crash so far but without any data written.
>
> Maybe the gpt partitions did the bad thing?
> Can md0 use large gpt drives with no partitions?
> can lvm2 use large raid device with no partition pv?
I did not notice the LVM on your first post, it's far enough down that I
missed it. I would be suspicious that the problem is in LVM rather than
md, but if you're going for a new install soon it's probably not worth
checking.
If you have video issues with FC12 you may need to run the vesa driver
as a quick solution. There have been learning experiences in the video
drivers in recent kernels, not just Fedora.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
next prev parent reply other threads:[~2010-03-13 23:45 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
2010-03-16 10:02 ` Kapetanakis Giannis
2010-03-13 23:45 ` Bill Davidsen [this message]
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=4B9C23AC.5010404@tmr.com \
--to=davidsen@tmr.com \
--cc=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).