From: Theodore Tso <tytso@mit.edu>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH]: ext4: fix big endian (was: not enough memory for 522250 flex groups)
Date: Thu, 6 Nov 2008 11:59:00 -0500 [thread overview]
Message-ID: <20081106165900.GC18939@mit.edu> (raw)
In-Reply-To: <200811061651.49602.borntraeger@de.ibm.com>
On Thu, Nov 06, 2008 at 04:51:49PM +0100, Christian Borntraeger wrote:
> Ok, I think I found it:
>
> On big endianess plattforms newly created ext4 file systems cannot be mounted
> and show messages like:
> [6923911.715968] EXT4-fs: not enough memory for 522250 flex groups
> [6923911.715973] EXT4-fs: unable to initialize flex_bg meta info!
>
> We have to access s_reserved_gdb_blocks with le16_to_cpu.
Aneesh has already submitted a patch to fix this; I'll be pushing it
to Linus shortly.
- Ted
prev parent reply other threads:[~2008-11-06 16:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 15:00 EXT4-fs: not enough memory for 522250 flex groups Christian Borntraeger
2008-11-06 15:51 ` [PATCH]: ext4: fix big endian (was: not enough memory for 522250 flex groups) Christian Borntraeger
2008-11-06 16:06 ` [PATCH]: ext4: fix big endian Peter Staubach
2008-11-06 16:15 ` Christian Borntraeger
2008-11-06 16:32 ` Aneesh Kumar K.V
2008-11-06 16:38 ` Christoph Hellwig
2008-11-06 17:11 ` Christian Borntraeger
2008-11-06 17:33 ` Theodore Tso
2008-11-06 17:39 ` Christoph Hellwig
2008-11-06 17:39 ` Christoph Hellwig
2008-11-06 17:48 ` Alexey Dobriyan
2008-11-08 22:35 ` Jörn Engel
2008-11-08 22:35 ` Jörn Engel
2008-11-10 18:09 ` Harvey Harrison
2008-11-10 18:09 ` Harvey Harrison
2008-11-10 19:31 ` Jörn Engel
2008-11-10 19:31 ` Jörn Engel
2008-11-06 17:39 ` Christoph Hellwig
2008-11-06 16:06 ` [PATCH]: ext4: fix big endian (was: not enough memory for 522250 flex groups) Andreas Schwab
2008-11-06 16:06 ` Andreas Schwab
2008-11-06 16:59 ` Theodore Tso [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=20081106165900.GC18939@mit.edu \
--to=tytso@mit.edu \
--cc=borntraeger@de.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.