From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 7/9] xfstests: add a new quota test that runs fsstress under ENOSPC conditions Date: Thu, 3 Nov 2011 15:39:35 -0400 Message-ID: <20111103193935.GA23014@infradead.org> References: <1320342953-7973-1-git-send-email-dmonakhov@openvz.org> <1320342953-7973-7-git-send-email-dmonakhov@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, aelder@sgi.com, tytso@mit.edu, hch@lst.de, xfs@oss.sgi.com To: Dmitry Monakhov Return-path: Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:58904 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750952Ab1KCTjh (ORCPT ); Thu, 3 Nov 2011 15:39:37 -0400 Content-Disposition: inline In-Reply-To: <1320342953-7973-7-git-send-email-dmonakhov@openvz.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Nov 03, 2011 at 09:55:51PM +0400, Dmitry Monakhov wrote: > - Same as 264 but with quota enabled. 269 is the new 270 > - IO performed from $qa_user user > - fsstress granted with CAP_CHOWN capability. This fails in my test VM because it doesn't have setcap. If you want to use additional non-standard tools please do a _notrun if they aren't present. I don't quite understand why it would need CAP_CHOWN - chowns from owned files do not require it, and the test runs fine with the setcap line commented out. I'll commit it as-is for now, but unless I get some feedback on why the setcap is require I'll add another commit to remove it ASAP.