From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: Other strange things
Date: Tue, 29 Jan 2008 16:53:37 +0900 [thread overview]
Message-ID: <1201593217.3629.102.camel@localhost.localdomain> (raw)
In-Reply-To: <20080125124652.5899a66b@vosztok>
Hi,
On Fri, 2008-01-25 at 12:46 +0100, Gergely Gábor wrote:
> On Thu, 17 Jan 2008 20:10:46 +0100
> Gergely Gábor <elentirmo.gilgalad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Hello!
>
> I have made a massuve uptime of 4 days by now, altough i didn't
> run rtorrent. yesterday (early today) i noticed that the garbage
> collector might have not honoured the 3 day protection interval,
> but i'm not sure... if it will be repeated, I'll send you lots
> of logs.
>
> So, tried to start rtorrent now, dut it instantly quit, and the
> console was flooded with nice traces and stuff... I attach a
> slabinfo and a kern.log. They are big, so i bzip them.
>
> ... one other idea. i save this letter now, and sent it after
> a restart, with some status report then...
>
> rtorrent escapes during the hash check... so it is a filesystem
> corruption or similiar. too bad there is no fsck yet. well, I
> make a snapshot, and delete the affected files, and see if the
> problem arises even after that.
>
> Best regards:
That's too bad.
But thanks for reporting the problem.
Your report told us that NILFS still has a potential BUG which may
lead to an FS-corruption.
Unfortunately, the BUG point printed in your log was a very general
one in a common b-tree lookup routine, so it's hard to identify
the cause from that.
There are many possibilities. In the worst case, the cleaner may
degenerate the corruption.
So, I recommend you to make backups of the current mount and
important snapshots while you can.
It should be done through ro-mounts or with -i mount option
for a rw-mount to turn off the cleaner (see example below).
# mount -t nilfs2 -i /dev/xxx /mount-point
Though removal of broken files may remedy the problem,
it also has a possibility to mark blocks terminated which is still
in use. In the latter case, the cleaner might reclaim the in-use
blocks wrongly.
Sorry for not supporting fsck.
At least for the present, please make do with means of backup or
others.
Best regards.
--
Ryusuke Konishi
NILFS team NTT
http://www.nilfs.org/
prev parent reply other threads:[~2008-01-29 7:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 21:25 Deadlocks! help, please! Gergely Gábor
2008-01-17 7:58 ` Ryusuke Konishi
[not found] ` <1200556717.3085.94.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-17 9:14 ` Ryusuke Konishi
[not found] ` <1200561294.3085.131.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-17 17:33 ` Gergely Gábor
2008-01-18 3:58 ` Ryusuke Konishi
[not found] ` <1200628693.2931.54.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-18 10:11 ` Ryusuke Konishi
[not found] ` <1200651072.2931.112.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-21 5:01 ` Ryusuke Konishi
[not found] ` <20080121.140129.01311807.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-01-21 23:00 ` Gergely Gábor
2008-01-22 3:02 ` Ryusuke Konishi
[not found] ` <1200970920.2844.59.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-02-05 9:28 ` Ryusuke Konishi
[not found] ` <20080205.182829.44149266.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-02-05 12:18 ` Gergely Gábor
2008-02-07 10:09 ` Gergely Gábor
2008-02-12 12:57 ` Ryusuke Konishi
[not found] ` <1202821077.9432.99.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-02-19 12:54 ` NILFS2 git repositories Ryusuke Konishi
2008-01-17 19:10 ` Deadlocks! help, please! Gergely Gábor
2008-01-25 11:46 ` Other strange things Gergely Gábor
2008-01-29 7:53 ` 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=1201593217.3629.102.camel@localhost.localdomain \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox