From: Seiji Kihara <kihara-sG5X7nlA6pw@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: Mount memory allocation error
Date: Thu, 03 Jul 2008 20:46:48 +0900 [thread overview]
Message-ID: <lur6abjil3.wl%kihara@osrg.net> (raw)
In-Reply-To: <20080703.203027.100419265.ryusuke-sG5X7nlA6pw@public.gmane.org>
Hello Peter,
At Thu, 03 Jul 2008 20:30:27 +0900 (JST),
Ryusuke Konishi wrote:
> 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?
I had tested with our environment and no error occured.
Could you please try our binary packages, and more information
of your environment if error occurs?
my log:
% uname -r
2.6.22.5-31-bigsmp
% rpm -q nilfs-kmp-bigsmp nilfs-utils
nilfs-kmp-bigsmp-2.0.2_2.6.22.5_31-1
nilfs-utils-2.0.4-1
% head /proc/meminfo
MemTotal: 4150384 kB
MemFree: 3811844 kB
Buffers: 16608 kB
Cached: 254852 kB
SwapCached: 0 kB
Active: 119736 kB
Inactive: 180004 kB
HighTotal: 3276528 kB
HighFree: 2982592 kB
LowTotal: 873856 kB
% head /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU 5130 @ 2.00GHz
stepping : 6
cpu MHz : 2000.251
cache size : 4096 KB
physical id : 0
siblings : 2
% dd if=/dev/zero of=nilfs2.vol bs=1048576 seek=1024 count=0
0+0 records in
0+0 records out
0 bytes (0 B) copied, 1.4095e-05 s, 0.0 kB/s
% mkfs -t nilfs2 nilfs2.vol
mkfs.nilfs2 ver 2.0
Start writing file system initial data to the device
Blocksize:4096 Device:nilfs2.vol Device Size:1073741824
File system initialization succeeded !!
% sudo mount -t nilfs2 -o loop nilfs2.vol /a
% df /a
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/loop0 1048572 16380 966656 2% /a
Regards,
Seiji Kihara
NILFS Team, NTT Labs.
next prev parent reply other threads:[~2008-07-03 11:46 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
[not found] ` <20080703.203027.100419265.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-07-03 11:46 ` Seiji Kihara [this message]
[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=lur6abjil3.wl%kihara@osrg.net \
--to=kihara-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.