public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Valerie Clement <valerie.clement@bull.net>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Andre Noll <maan@systemlinux.org>, Theodore Tso <tytso@mit.edu>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: qla2xxx BUG: workqueue leaked lock or atomic
Date: Tue, 13 Mar 2007 09:23:28 +0100	[thread overview]
Message-ID: <45F65F80.7050202@bull.net> (raw)
In-Reply-To: <20070313070134.GK5266@schatzie.adilger.int>

Andreas Dilger wrote:
> On Mar 12, 2007  16:22 +0100, Valerie Clement wrote:
>> Mingming Cao wrote:
>>> IBM has done some testing (dbench, fsstress, fsx, tiobench, iozone etc)
>>> on 10TB ext3, I think RedHat and BULL have done similar test on >8TB
>>> ext3 too.
>> Is there not a problem of backward-compatibility with old kernels?
>> Doesn't we need to handle a new INCOMPAT flag in e2fsprogs and kernel
>> before allowing ext3 filesystems greater than 8T?
> 
> No, it really depends on the kernel.  There were some bugs that caused
> problems with > 8TB because of signed 32-bit int problems, so it isn't
> really recommended to use > 8TB unless you know this is fixed in your
> kernel (and any older kernel you might have to downgrade to).
> 

OK. Thanks.
As Andre mentions it, it seems that the option "-F" for mkfs is 
necessary to create an ext3 FS > 8T.
(I've got the same behavior but I didn't apply the latest patches 
against my current version of e2fsprogs, so I can't check if that has 
changed since).
Is it the right way?

     Valérie

      reply	other threads:[~2007-03-13  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070226133153.GC4095@skl-net.de>
     [not found] ` <20070226182617.GC9968@andrew-vasquezs-computer.local>
     [not found]   ` <20070227101100.GA22572@skl-net.de>
     [not found]     ` <20070227185134.GJ20397@andrew-vasquezs-computer.local>
     [not found]       ` <20070228151829.GI22572@skl-net.de>
     [not found]         ` <20070228153722.GJ22572@skl-net.de>
     [not found]           ` <20070306203952.471218df.akpm@linux-foundation.org>
     [not found]             ` <20070307170955.GA4252@skl-net.de>
2007-03-07 19:45               ` qla2xxx BUG: workqueue leaked lock or atomic Andrew Morton
2007-03-07 20:05                 ` Mingming Cao
2007-03-09  9:36                   ` Andre Noll
2007-03-12 15:22                   ` Valerie Clement
2007-03-13  7:01                     ` Andreas Dilger
2007-03-13  8:23                       ` Valerie Clement [this message]

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=45F65F80.7050202@bull.net \
    --to=valerie.clement@bull.net \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=maan@systemlinux.org \
    --cc=tytso@mit.edu \
    /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