From: "Roy Lanek" <lanek@novenine.com>
To: reiserfs-list@namesys.com
Subject: -- warning("vs-44", "out of memory?");
Date: Thu, 06 Apr 2006 06:41:32 +0000 [thread overview]
Message-ID: <20060406064132.11477.qmail@mail.httpdnet.com> (raw)
There might be something to debug around:
warning("vs-44", "out of memory?");
line 2674 of /.../linux/fs/reiser4/plugin/file/file.c
In fact, I just have seen a long, unterminated series of
reiser4-out-of-memory warnings in my logs when my box
has started to freeze ... till it has frozen completely
several minutes later.
Unfortunately I have lost all the logs (see below) ... I
am sad for the #---- cut out --- thing that I have seen
and can't reproduce; I had to reboot and did not want to
write down by hand the few items that were visible trough
the few overlapped xterms (+ elvis).
Don't worry, it will happen again enough soon: if you say
that it makes sense, I will manage to not be caught by
surprise again, will try to save the logs immediately,
when the system starts to freeze.
OK, here a bit more context:
** kernel (... uname):
2.6.16.1-grsec #3 Wed Apr 5 22:46:36 WIT 006 i586 pentium
i386 GNU/Linux
compiled without debug support for reiser4
vanilla patches reiser4-for-2.6.16-1
+ grsecurity-2.1.9-2.6.16.1-200604041154
** runit-1.4.1 + socklog-2.1.0
** Slackware current, i.e., gcc 3.4.6
** a P166/32 Mb + non SCSI HDs. (It works, I swear, and
well too!)
Cheers,
/Roy Lanek (West Sumatra)
--
######################## tak ada gading yang tak retak
##### . slackware ###### there are no ivory that is not cracked
##### +-----linux ###### [nothing is perfect in this world]
########################
next reply other threads:[~2006-04-06 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 6:41 Roy Lanek [this message]
2006-04-06 7:12 ` -- warning("vs-44", "out of memory?"); Vladimir V. Saveliev
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=20060406064132.11477.qmail@mail.httpdnet.com \
--to=lanek@novenine.com \
--cc=reiserfs-list@namesys.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 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.