From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
mniederle-RbZlAiThDcE@public.gmane.org
Subject: Re: Data Loss
Date: Fri, 12 Jun 2009 17:58:42 +0900 (JST) [thread overview]
Message-ID: <20090612.175842.44914422.ryusuke@osrg.net> (raw)
In-Reply-To: <20090612011057.547c70c1@simplux>
Hi,
On Fri, 12 Jun 2009 01:10:57 +0200, "Dipl.-Ing. Michael Niederle" wrote:
> Hi!
>
> It's absolutely strange: nilfs seems to crash during idle times!
>
> This time everything seemed to be fine when I returned to my PC after several
> hours. Astonishingly my pen drive's LED reported heavy activity despite the
> fact that there was nothing to do. I have a script that detects recently
> changed files. This script reported that not a single file had been changed
> during the last hour!
I think the activity is created by the garbage collector. Note that
Nilfs GC works background and it wakes up after protection period of
checkpoints is expired.
Probably, the delay time you have experienced is the protection period.
> After a reboot the system got stuck when trying to pivot_root to the
> nilfs-root-file-system (no problem mounting it). An analysis showed that
> several files had been destroyed. The stat-utility showed the file type
> "weird". ^^
Grr, GC problem?
> I also mounted some elder checkpoints. They now had defect files, too.
>
> In my opinion the cleaner daemon is causing all these problems but -
> as always - I might be wrong.
>
> As to my knowledge there is currently no way to repair a nilfs-file-system?
Uum, yes. Only we can do is finding clean checkpoint.
> Greetings, Michael
Regards,
Ryusuke Konishi
prev parent reply other threads:[~2009-06-12 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.37.1244739111.2282.users@nilfs.org>
[not found] ` <mailman.37.1244739111.2282.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
2009-06-11 23:10 ` Data Loss Dipl.-Ing. Michael Niederle
2009-06-12 8:58 ` Ryusuke Konishi [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=20090612.175842.44914422.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox