From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: debian-qVUaBahCJu5n68oJJulU0Q@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs_sufile_do_cancel_free: segment 0 must be clean
Date: Mon, 22 Mar 2010 15:04:20 +0900 (JST) [thread overview]
Message-ID: <20100322.150420.179960388.ryusuke@osrg.net> (raw)
In-Reply-To: <4BA54677.3090902-qVUaBahCJu5n68oJJulU0Q@public.gmane.org>
Hi,
On Sat, 20 Mar 2010 23:04:39 +0100, Andreas Beckmann wrote:
> Hi,
>
> I just tried to benchmark nilfs and then the file system and benchmark
> process got stuck. dmesg output is attached. The problems start with
>
> nilfs_sufile_do_cancel_free: segment 0 must be clean
> nilfs_sufile_do_cancel_free: segment 1 must be clean
> NILFS warning (device sdb1): nilfs_clean_segments: segment construction
> failed. (err=-28)
>
> I'm using
>
> Kernel 2.6.33 (Debian 2.6.33-1~experimental.2)
> nilfs-tools 2.0.16 (Debian 2.0.16-1)
>
> The processes are unkillable and the file system cannot be unmounted.
> The machine will be reset when I get back in physical range on Wednesday
> and the stuck file system will be removed. If there is anything I can do
> remotely to help you debug that problem before the file system is gone,
> let me know.
>
> The file system got into this state after writing several times the
> capacity of the file system, creating a single file until the file
> cannot be extended any more.
>
> # df -k /dev/sdb1
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sdb1 136716284 136372220 0 100% /stxxl/sdb
>
> Can't do a ls on the file systen, gets stuck as well.
>
>
> Please keep me CCed, I'm not on the list.
>
>
> Andreas
Thank you for the detail report!
I could reproduce the both problems (i.e. the warnings on
"nilfs_sufile_do_cancel_free" and the hang of cleaner process) by a
manual fault injection test.
Will look into these issues.
Ryusuke Konishi
--
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:[~2010-03-22 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 22:04 nilfs_sufile_do_cancel_free: segment 0 must be clean Andreas Beckmann
[not found] ` <4BA54677.3090902-qVUaBahCJu5n68oJJulU0Q@public.gmane.org>
2010-03-22 6:04 ` Ryusuke Konishi [this message]
[not found] ` <20100322.150420.179960388.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-03-22 6:34 ` Ryusuke Konishi
[not found] ` <20100322.153446.180039371.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-03-22 13:48 ` 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=20100322.150420.179960388.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=debian-qVUaBahCJu5n68oJJulU0Q@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