From: "peng.hse" <peng.hse@xtaotech.com>
To: djwong@kernel.org, linux-fsdevel@vger.kernel.org,
darrick.wong@oracle.com
Subject: xfs wrongly report ENOSPACE
Date: Mon, 6 Feb 2017 20:37:26 +0800 [thread overview]
Message-ID: <58986E06.5050500@xtaotech.com> (raw)
Hi DJ and xfs developers,
i am ceph developer, build the OSD on top of the xfs mount point. the
kernel xfs module i used was build from the 4.9.8 kernel release from
kernel.org, that includes your recent changes in Dec, 2016.
recently, i found our cluster will get faulted due to the xfs mount
wrongly report there is no space to create the new file as
" No space left on device ", but apparently the xfs mount point only
be around 50% full.
i used the systemtap to narrow it down the the function
xfs_ialloc_ag_select which reports no free ag selected, the problem seems
still exist, not sure your recent patches will fix it or not.
i am very glad to provide more info if your like to assist you to
identify the problem.
next reply other threads:[~2017-02-06 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 12:37 peng.hse [this message]
2017-02-06 13:14 ` xfs wrongly report ENOSPACE Brian Foster
2017-02-07 12:39 ` peng.hse
2017-02-07 13:01 ` Carlos Maiolino
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=58986E06.5050500@xtaotech.com \
--to=peng.hse@xtaotech.com \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.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.