From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mr213138.mail.yeah.net ([223.252.213.138]:37334 "EHLO mr213138.mail.yeah.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751754AbdBFNAQ (ORCPT ); Mon, 6 Feb 2017 08:00:16 -0500 To: djwong@kernel.org, linux-fsdevel@vger.kernel.org, darrick.wong@oracle.com From: "peng.hse" Subject: xfs wrongly report ENOSPACE Message-ID: <58986E06.5050500@xtaotech.com> Date: Mon, 6 Feb 2017 20:37:26 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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.