From patchwork Thu Aug 15 15:00:31 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Josef Bacik X-Patchwork-Id: 11095835 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 39D9F912 for ; Thu, 15 Aug 2019 15:00:38 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 1F195286FB for ; Thu, 15 Aug 2019 15:00:38 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 12B361FFBD; Thu, 15 Aug 2019 15:00:38 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 9336D288F6 for ; Thu, 15 Aug 2019 15:00:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733306AbfHOPAh (ORCPT ); Thu, 15 Aug 2019 11:00:37 -0400 Received: from mail-qt1-f195.google.com ([209.85.160.195]:45355 "EHLO mail-qt1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733301AbfHOPAg (ORCPT ); Thu, 15 Aug 2019 11:00:36 -0400 Received: by mail-qt1-f195.google.com with SMTP id k13so2597017qtm.12 for ; Thu, 15 Aug 2019 08:00:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toxicpanda-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=OYSGbo2poQ0qyt6wJ+tE5Kkt4rIGLn9ysUdvvgi22no=; b=zza1nWLqebk1iLYNx5DS/OPhn1g6yu4ArIKnhwdPTCIcaeVddPkl5mfdlpd1bImjV+ w7kAzpGzt8V5DPBxk7YsF2MpoGGtQfz369QlMNyJtTG15np6SeD/drrj9jY1HDJJQbFu 74vKDJBdU6FB0WDFrpBm0FH55Ax0bwCmVl1vc2df+i0e/Fi4szGh6mEfel4CgSUnvAwD 2N95zRRPbMR3HfLht3mIMDkE9ut3736ZhH5WaBzPNqm2M2SY0WD2Vs/xeFWhQ6mN1BF5 xF35CfxVR/BfZoNDnbdJ6uqPb6oMOds56tnpJl6nryKsjaxRlrBsft4BOLv4LXFozkMu X+0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=OYSGbo2poQ0qyt6wJ+tE5Kkt4rIGLn9ysUdvvgi22no=; b=i0KR8mkDHWm6kfDqGCV3cGbnssvccQ2Z/Ir7Zm19FWMV4xKaEudGRS1FqFlOBXD49y L7pFFXsCFFSCqMiMmg8JMOELP52aPMmgv9N52n/2PRLv1cY69qV+40MG7JDRbCy/9HsW 2VqEp9Q0jMqgdvsCRNDhDCKRkRyhYrMJspL1i1Ve4lmMbh5au2ZokLasMo4Xo2OufKgc M6iwdLMJhs7YmGQQTmnrnFoIIEineQIdYWfqVN7krlqrX/j4TGYVAKQDEL7w4g5KHhPU BaNHdhmPZu6+UXb4vUdSan/gg2Xsm7q6ndMjREdYN9kb3sq2bwTEu12V7gQKoHI4L66G NUzQ== X-Gm-Message-State: APjAAAV/eny5ajGjJAguEd7/MdD68nxc6bLiInO7VDWsCavHwnQ6JTot YoJz9UjlXm2EM3x+XEnl8LLd4rVtlHJWBw== X-Google-Smtp-Source: APXvYqxi1UeJYsp7Y9vq4l18226mn7ewUonKzQ3VzvTO0TmybLaOEJbsDXkr2BZgcBh0OOVoL3TAZw== X-Received: by 2002:a05:6214:3a5:: with SMTP id m5mr3580174qvy.7.1565881234678; Thu, 15 Aug 2019 08:00:34 -0700 (PDT) Received: from localhost ([107.15.81.208]) by smtp.gmail.com with ESMTPSA id k2sm1420787qtq.84.2019.08.15.08.00.33 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 15 Aug 2019 08:00:34 -0700 (PDT) From: Josef Bacik To: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org, kernel-team@fb.com Subject: [PATCH 1/2] fstests: make generic/500 xfs+ext4 only Date: Thu, 15 Aug 2019 11:00:31 -0400 Message-Id: <20190815150033.15996-1-josef@toxicpanda.com> X-Mailer: git-send-email 2.21.0 MIME-Version: 1.0 Sender: fstests-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: fstests@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP I recently fixed some bugs in btrfs's enospc handling that made it start failing generic/500. The point of this test is to make the thin provisioned device run out of space, which results in an EIO being seen on a device from the file systems perspective. This is fine for xfs and ext4 who's metadata is being overwritten and already allocated on the thin provisioned device. They get an EIO on data writes, fstrim to free up the space, and keep it going. Btrfs however has dynamic metadata, so the rm -rf could result in metadata IO being done on the file system. Since the thin provisioned device is out of space this gives us an EIO, and we flip read only. We didn't remove the file, so the fstrim doesn't recover space anyway, so we can't even fstrim and remount. Make this test for ext4/xfs only, it just simply won't work right for btrfs in it's current form. Signed-off-by: Josef Bacik --- tests/generic/500 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/generic/500 b/tests/generic/500 index 201d8b9f..1cbd9d65 100755 --- a/tests/generic/500 +++ b/tests/generic/500 @@ -44,7 +44,7 @@ _cleanup() rm -f $seqres.full # real QA test starts here -_supported_fs generic +_supported_fs xfs ext4 _supported_os Linux _require_scratch_nocheck _require_dm_target thin-pool