From: Alexander Bezrukov <nilfs-issues-tvrqcU/I3+LBxmVkcvZ8vQ@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Corrupted nilfs2 volume
Date: Sat, 16 Mar 2013 03:21:57 +0400 [thread overview]
Message-ID: <20130315232157.GC1542@black> (raw)
In-Reply-To: <1363328491.2078.21.camel@slavad-ubuntu>
Hi Vyacheslav,
> Had you any snapshots on this volume?
Unfortunately no. I had had one but have recently converted
t to an ordinary cp.
> It needs to investigate the issue more deeply. Could you
> try to mount this volume under another system? I hope that
> it gives opportunity to get more details about the issue
> from system log. So, could you share NILFS2 related messages
> for such try?
This is what I've indeed done in the first place.
>> NILFS: Invalid checkpoint (checkpoint number=5439464)
>> NILFS: error loading last checkpoint (checkpoint number=5439464)
In fact, these lines I have copied from the system log of another
system (with some some debian distro kernel 3.2.0). But this is
exactly how my original kernel complains too.
> > To my best knowledge there is no "official" fsck tool for nilfs2
> > but at times nilfs2 has just been added to the mainline kernel I
> > read somewhere about some "unofficial" version at some developer
> > branch.
>
> I send you personally archive with actual state of fsck.nilfs2.
> I need in debug output of the fsck.nilfs2 for analysis of situation
> on the volume.
I am sorry, I didn't receive any archive.
> I hope that we can recover your volume. But, anyway, we need to analyze
> the issue and try to cure the volume.
For me the latter is even more important.
Best regards.
Alexander Bezrukov
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-03-15 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130315024019.7DC1BD00@mail.dragonworks.ru>
[not found] ` <20130315024019.7DC1BD00-foQFVU7ZUqen8/iIaQqUdCjHesifYMBh@public.gmane.org>
2013-03-15 6:21 ` Corrupted nilfs2 volume Vyacheslav Dubeyko
2013-03-15 23:21 ` Alexander Bezrukov [this message]
2013-03-16 15:11 ` Vyacheslav Dubeyko
[not found] ` <70219EF1-8083-4DD5-BA18-84CD1914DC3E-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-03-18 14:23 ` Alexander Bezrukov
2013-03-18 20:44 ` Vyacheslav Dubeyko
[not found] ` <4E5BDA60-7615-4F82-AC0F-4459DD9EF544-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-03-18 22:31 ` Alexander Bezrukov
2013-03-19 8:06 ` Vyacheslav Dubeyko
2013-03-19 8:30 ` ARAI Shun-ichi
[not found] ` <20130319.173020.3478740326553917.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2013-03-19 9:15 ` Vyacheslav Dubeyko
[not found] ` <20121130.164616.1703426007244850753.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2013-03-19 11:17 ` ARAI Shun-ichi
[not found] ` <20130319.201730.1543938923107719972.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2013-03-19 11:42 ` Vyacheslav Dubeyko
2013-03-19 12:52 ` ARAI Shun-ichi
2013-03-19 17:35 ` Alexander Bezrukov
2013-03-21 6:31 ` Vyacheslav Dubeyko
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=20130315232157.GC1542@black \
--to=nilfs-issues-tvrqcu/i3+lbxmvkcvz8vq@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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.