From: Viacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Brian Cottingham <spiffytech-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Cleaner crashes, can't read source blocks, error=-5
Date: Mon, 14 Dec 2015 11:00:11 -0800 [thread overview]
Message-ID: <1450119611.2617.2.camel@slavad-ubuntu-14.04> (raw)
In-Reply-To: <CAJEMKXOZuojpXq7T4iAN5101AADe1XbbrCUt1L66PM5w6POg6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Brian,
On Mon, 2015-12-14 at 10:11 -0500, Brian Cottingham wrote:
> My nilfs2 partition has filled up, and I can't free up space because
> nilfs_cleanerd crashes. This is what I get in syslog:
>
> ----
> Dec 14 09:49:38 spiffyhome nilfs_cleanerd[1580]: start
> Dec 14 09:49:38 spiffyhome nilfs_cleanerd[1580]: pause (clean check)
> Dec 14 09:49:38 spiffyhome nilfs_cleanerd[1580]: resume (clean check)
> Dec 14 09:50:45 spiffyhome kernel: [ 149.008559] NILFS: GC failed
> during preparation: cannot read source blocks: err=-5
> Dec 14 09:50:45 spiffyhome nilfs_cleanerd[1580]: cannot clean
> segments: Input/output error
> Dec 14 09:50:45 spiffyhome nilfs_cleanerd[1580]: shutdown
Could you please share version of Linux kernel and version nilfs utils
on your side at first? Do you use some special configuration options for
GC?
Thanks,
Vyacheslav Dubeyko.
--
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
prev parent reply other threads:[~2015-12-14 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 15:11 Cleaner crashes, can't read source blocks, error=-5 Brian Cottingham
[not found] ` <CAJEMKXOZuojpXq7T4iAN5101AADe1XbbrCUt1L66PM5w6POg6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-14 19:00 ` Viacheslav Dubeyko [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=1450119611.2617.2.camel@slavad-ubuntu-14.04 \
--to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spiffytech-Re5JQEeQqe8AvxtiuMwx3w@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).