From: Ivan Telichko <itelichko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Regarding ``problem with nilfs_cleanerd - part 2'' and ``Nilfs_cleanerd err=-17''
Date: Mon, 25 Apr 2011 05:28:10 +0000 (UTC) [thread overview]
Message-ID: <loom.20110425T072626-629@post.gmane.org> (raw)
In-Reply-To: 20110425.103542.66626035.ryusuke@osrg.net
> If you are still keeping the partition, could you test if the
> following patch makes a difference ?
No observable difference, patched cleanerd still dies the same way.
There are more messages in the log if I start nilfs_cleanerd by hand:
Apr 26 02:54:21 nilfs_cleanerd[4734]: start
Apr 26 02:54:21 nilfs_cleanerd[4734]: pause (clean check)
Apr 26 02:54:21 nilfs_cleanerd[4734]: resume (clean check)
Apr 26 02:54:21 nilfs_cleanerd[4734]: ncleansegs = 244
Apr 26 02:54:21 nilfs_cleanerd[4734]: 4 segments selected to be cleaned
Apr 26 02:54:21 nilfs_cleanerd[4734]: protected checkpoints = [69325,69425]
(protection period >= 1303760661)
Apr 26 02:54:22 kernel: nilfs_ioctl_move_inode_block: conflicting data buffer:
ino=97606, cno=281, offset=14, blocknr=3526535, vblocknr=1555981
Apr 26 02:54:22 kernel: NILFS: GC failed during preparation: cannot read
source blocks: err=-17
Apr 26 02:54:23 nilfs_cleanerd[4734]: cannot clean segments: File exists
Apr 26 02:54:23 nilfs_cleanerd[4734]: shutdown
---
Regards,
Ivan Telichko
--
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:[~2011-04-25 5:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 19:04 Regarding ``problem with nilfs_cleanerd - part 2'' and ``Nilfs_cleanerd err=-17'' dexen deVries
2011-04-22 18:27 ` Ivan Telichko
[not found] ` <loom.20110422T201841-92-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-04-25 1:35 ` Ryusuke Konishi
2011-04-25 5:28 ` Ivan Telichko [this message]
[not found] ` <loom.20110425T072626-629-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-04-25 7:34 ` Ryusuke Konishi
2011-04-26 21:21 ` Ivan Telichko
[not found] ` <loom.20110426T231606-740-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-04-27 6:40 ` Ryusuke Konishi
2011-04-27 9:27 ` Ivan Telichko
[not found] ` <loom.20110427T111017-105-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-04-27 11:40 ` Ryusuke Konishi
2011-04-27 12:29 ` Ivan Telichko
[not found] ` <loom.20110427T140022-700-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-04-28 1:36 ` 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=loom.20110425T072626-629@post.gmane.org \
--to=itelichko-re5jqeeqqe8avxtiumwx3w@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 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).