From: dE <de.techno-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: nilfs_clean_segments: segment construction failed. (err=-2)
Date: Thu, 26 Jun 2014 10:30:35 +0530 [thread overview]
Message-ID: <53ABA8F3.3010606@gmail.com> (raw)
Hi!
I'm using nilfs on thumb drives to sync Bitcoin wallets and it's forks.
Sometimes, when I quit the bitcoin-qt application, this is what happens
(in dmesg)
[159141.505498] nilfs_btree_propagate: key = 10, level == 0
[159141.715622] nilfs_btree_propagate: key = 10, level == 0
[159141.716134] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
[159146.715145] nilfs_btree_propagate: key = 10, level == 0
[159146.715152] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
[159151.715018] nilfs_btree_propagate: key = 10, level == 0
[159151.715026] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
[159156.714892] nilfs_btree_propagate: key = 10, level == 0
...
...
...
[160276.691089] nilfs_btree_propagate: key = 10, level == 0
[160276.691096] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
[160281.690959] nilfs_btree_propagate: key = 10, level == 0
[160281.690967] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
I can still access the thumbdrive and it's contents. In the mean time
many processes remain at D state and I have to force restart.
The devices used are perfectly fine. I've 3 of them, 2 of them are used
as a single LVM volume and another one uses the whole device as a nilfs
FS (no partition table).
--
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 reply other threads:[~2014-06-26 5:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 5:00 dE [this message]
[not found] ` <53ABA8F3.3010606-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-26 5:35 ` nilfs_clean_segments: segment construction failed. (err=-2) Vyacheslav Dubeyko
[not found] ` <A863805F-8398-42B1-9BEA-35D4425E2404-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2014-06-26 6:00 ` dE
[not found] ` <53ABB6F4.5050508-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-26 13:34 ` Vyacheslav Dubeyko
2014-06-27 4:44 ` dE
[not found] ` <53ACF691.5090203-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-27 6:30 ` Vyacheslav Dubeyko
2014-06-27 7:21 ` dE
2014-07-07 15:34 ` dE
2014-07-08 1:38 ` dE
[not found] ` <53BB4B8B.4060902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-08 8:03 ` Vyacheslav Dubeyko
2014-07-10 15:43 ` dE
[not found] ` <53BEB4B3.7000002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-18 7:38 ` dE
[not found] ` <53C8CEFB.2010202-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-18 7:58 ` Vyacheslav Dubeyko
2014-07-21 16:54 ` dE
2014-06-27 4:52 ` dE
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=53ABA8F3.3010606@gmail.com \
--to=de.techno-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 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.