All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dipl.-Ing. Michael Niederle" <mniederle-RbZlAiThDcE@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: More test results
Date: Mon, 15 Jun 2009 12:43:59 +0200	[thread overview]
Message-ID: <20090615124359.536e8685@simplux> (raw)
In-Reply-To: <mailman.1.1245034801.3147.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>

Hi!

I reinstalled my pen drive and continued testing just doing my regular work. (I
always work on a pen drive based system.)

I did *not* start the gc-daemon and worked without any problems for several
hours. Free space was reduced by several GBs - but I started with plenty of free
space left.

During the night I run the gc to claim back unused space. In the morning
the gc seemed to have crashed again. The PC still worked but essential parts of
the system were frozen - so no clean shutdown was possible.

This time the system was severely damaged. The next reboot failed with an
error message (failed mount). (Sorry, I was in a hurry and did not memoize the
exact reading of the message.)

Another issue: Sometimes the gc stops after some time leaving the following
message in the kernel log. (The message seems to stem from another part of the
kernel, but I'm sure it is connected to the gc-daemon.)

vmap() failed while attempting to map about 256 MB of memory

(Sorry, once more - I had stored the exact message on the crashed file system
and had to repeat it from memory.)

I'm using an unmodified 2.6.30 kernel with builtin nilfs (no module).

Greetings, Michael

       reply	other threads:[~2009-06-15 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1245034801.3147.users@nilfs.org>
     [not found] ` <mailman.1.1245034801.3147.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
2009-06-15 10:43   ` Dipl.-Ing. Michael Niederle [this message]
2009-06-19  3:01     ` More test results Ryusuke Konishi

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=20090615124359.536e8685@simplux \
    --to=mniederle-rbzlaithdce@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.