From: Paul Fertser <fercerpav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: New experience with the odd problem starting nilfs_cleanerd due to an eMMC misbehaviour
Date: Sun, 30 Jun 2013 11:56:26 +0400 [thread overview]
Message-ID: <20130630075626.GJ22224@home.lan> (raw)
In-Reply-To: <20130630074404.GI22224-0MSThuzptbI@public.gmane.org>
On Sun, Jun 30, 2013 at 11:44:04AM +0400, Paul Fertser wrote:
> Attaching dumpseg output for segment 2713, strace for nilfs_cleanerd,
> etc, HTH.
But now zeroing out the eMMC sectors that lead to errors didn't help,
I get
[ 81.903509] nilfs_cpfile_delete_checkpoints: invalid range of checkpoint numbers: [0, 436896)
[ 81.912342] NILFS: GC failed during preparation: cannot delete checkpoints: err=-22
Jun 30 11:51:43 ac100-debian nilfs_cleanerd[1553]: start
Jun 30 11:51:43 ac100-debian nilfs_cleanerd[1553]: pause (clean check)
Jun 30 11:51:43 ac100-debian nilfs_cleanerd[1553]: resume (clean check)
Jun 30 11:51:43 ac100-debian nilfs_cleanerd[1553]: ncleansegs = 464
Jun 30 11:51:43 ac100-debian nilfs_cleanerd[1553]: 4 segments selected to be cleaned
Jun 30 11:51:43 ac100-debian nilfs_cleanerd[1553]: cannot clean segments: Invalid argument
Jun 30 11:51:43 ac100-debian nilfs_cleanerd[1553]: shutdown
I've no backups for this volume which is a rootfs on my netbook, not
that it has something very important but I'd like to keep it
functional... Any ideas how to proceed?
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
--
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-06-30 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 13:52 Odd problem starting nilfs_cleanerd due to an eMMC misbehaviour Paul Fertser
[not found] ` <20120126135203.GM2267-0MSThuzptbI@public.gmane.org>
2012-01-27 16:19 ` Christian Smith
[not found] ` <20120127161921.GL750-Ng8wz+J301SNY5Lh21HnMTHS2PGA244I9dF7HbQ/qKg@public.gmane.org>
2012-01-27 16:29 ` Gordan Bobic
2012-01-28 12:53 ` Martin Steigerwald
[not found] ` <201201281353.00537.Martin-3kZCPVa5dk2azgQtNeiOUg@public.gmane.org>
2012-02-01 6:06 ` Paul Fertser
2013-01-10 13:16 ` New experience with the odd " Paul Fertser
[not found] ` <20130110131659.GA29689-0MSThuzptbI@public.gmane.org>
2013-01-10 13:34 ` Vyacheslav Dubeyko
2013-01-10 13:49 ` Paul Fertser
[not found] ` <20130110134907.GB29689-0MSThuzptbI@public.gmane.org>
2013-01-10 14:00 ` Vyacheslav Dubeyko
2013-01-10 14:12 ` Paul Fertser
2013-06-30 7:44 ` Paul Fertser
[not found] ` <20130630074404.GI22224-0MSThuzptbI@public.gmane.org>
2013-06-30 7:56 ` Paul Fertser [this message]
[not found] ` <20130630075626.GJ22224-0MSThuzptbI@public.gmane.org>
2013-06-30 11:49 ` 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=20130630075626.GJ22224@home.lan \
--to=fercerpav-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=slava-yeENwD64cLxBDgjK7y7TUQ@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;
as well as URLs for NNTP newsgroup(s).