From: Jan de Kruyf <jan.de.kruyf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: cleanerd
Date: Sun, 11 Oct 2009 00:18:10 +0200 [thread overview]
Message-ID: <ee5afd760910101518u4a85fd0fn6e5539a327b2a876@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2196 bytes --]
Hallo,
Here is an interesting disaster with nilfs2. Lightening went down the
chimney on the other side of the wall. Computer was off, but plugged in.
Motherboard died.
So I now try to fix partitions. at the moment it is /var. /home will come
later.
Here is the problem:
/var data is readable but the cleanerd has become confused after the
disaster and has filled up the partition
partition size 5.8 Gig, data size 2.56 Gig, but usage is now 100%
Normal mounting:
cleanerd cannot be stopped anymore, neither with TERM or KILL signals.
lscp shows only cleaner checkpoints now.
When mounting without the cleanerd running there are no dmesg's of interest
on mounting or on execution of any command
To rescue the partition do I copy the data to another disk and reformat? Or
is there a simpler solution?
Best Regard,
Jan de Kruyf.
------------------
ps.
running debian lenny, kernel 2.6.26-1-686
branch 'master' of http://git.nilfs.org/nilfs2-utils dd. 11 july 2009
branch 'master' of http://git.nilfs.org/nilfs2-module dd. 11 july 2009
tag 'v2.0.15'
and here is the superblock of the partition:
00000000: 0200 0000 0000 3434 0001 0000 8422 95d1 ......44....."..
00000010: 80b7 90e7 0200 0000 ca02 0000 0000 0000 ................
00000020: 00b4 6665 0100 0000 0100 0000 0000 0000 ..fe............
00000030: 0008 0000 0500 0000 e1e6 1400 0000 0000 ................
00000040: d69f 0d00 0000 0000 c181 0900 0000 0000 ................
00000050: 0000 0000 0000 0000 4815 5a4a 0000 0000 ........H.ZJ....
00000060: 3713 d04a 0000 0000 3713 d04a 0000 0000 7..J....7..J....
00000070: 4000 3200 0000 0100 4815 5a4a 0000 0000 @.2.....H.ZJ....
00000080: 004e ed00 0000 0000 0000 0000 0b00 0000 .N..............
00000090: 8000 2000 c000 1000 470b 1351 09a6 4016 .. .....G..Q..@.
000000a0: 9397 70f2 82f5 d61b 7661 7200 0000 0000 ..p.....var.....
000000b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
[-- Attachment #1.2: Type: text/html, Size: 2534 bytes --]
[-- Attachment #2: Type: text/plain, Size: 158 bytes --]
_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users
next reply other threads:[~2009-10-10 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 22:18 Jan de Kruyf [this message]
[not found] ` <ee5afd760910101518u4a85fd0fn6e5539a327b2a876-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-11 3:29 ` cleanerd Ryusuke Konishi
[not found] ` <20091011.122911.131278678.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-10-11 5:32 ` cleanerd Jan de Kruyf
[not found] ` <ee5afd760910102232o5f17c50cxb5024f6f76ecbcf5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-11 6:49 ` cleanerd Ryusuke Konishi
[not found] ` <20091011.154916.07997858.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-10-13 19:57 ` cleanerd Jan de Kruyf
2009-10-17 20:47 ` cleanerd Jan de Kruyf
[not found] ` <ee5afd760910171347x4ad27199ka59d0e76f3271050-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-19 2:07 ` cleanerd Ryusuke Konishi
-- strict thread matches above, loose matches on Subject: below --
2008-11-05 21:45 cleanerd John Huttley
[not found] ` <491213E2.4010905-jE24nFfhqzU3hwNNidygWXTaI6DYlTYJ@public.gmane.org>
2008-11-06 2:50 ` cleanerd 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=ee5afd760910101518u4a85fd0fn6e5539a327b2a876@mail.gmail.com \
--to=jan.de.kruyf-re5jqeeqqe8avxtiumwx3w@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