From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Mount memory allocation error
Date: Thu, 03 Jul 2008 20:30:27 +0900 (JST) [thread overview]
Message-ID: <20080703.203027.100419265.ryusuke@osrg.net> (raw)
In-Reply-To: <474dca090807030319w7ff440b0w1315c60fb7d56756-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Peter,
On Thu, 3 Jul 2008 12:19:53 +0200, "Peter Smith" wrote:
> Hi,
> I recently upgraded my memory from 2G to 4G and this made it necessary to
> change my kernel
> from
> 2.6.22.5-31-default
> to
> 2.6.22.5-31-bigsmp
>
> Now I cannot mount nilfs2 partitions.
> I get the error message: mount.nilf2: ... ... Cannot allocate memory
>
> My environment is
> OpenSuse 10.3
> nilfs 2.02
> nilfs-utils 2.04
>
> Yes, I did recompile/install nilfs and nilfs-utils while using the bigsmp
> kernel.
> When I switch back to the default kernel mount.nilfs2 works normally,
> as does everything else.(but of course I don't have access to the full 4G
> memory)
>
> Your help would be greatly appreciated
> Peter
Thank you for reporting this.
We are now trying to catch the problem.
BTW, did you try our binary package for OpenSuse?
It is available on http://www.nilfs.org/pub/opensuse/.
Does it incur the same problem?
Cheers,
Ryusuke Konishi
next prev parent reply other threads:[~2008-07-03 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 10:19 Mount memory allocation error Peter Smith
[not found] ` <474dca090807030319w7ff440b0w1315c60fb7d56756-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-03 11:30 ` Ryusuke Konishi [this message]
[not found] ` <20080703.203027.100419265.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-07-03 11:46 ` Seiji Kihara
[not found] ` <lur6abjil3.wl%kihara-sG5X7nlA6pw@public.gmane.org>
2008-07-03 11:57 ` Peter Smith
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=20080703.203027.100419265.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@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 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.