From patchwork Fri Jul 17 04:56:43 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Chandan Rajendra X-Patchwork-Id: 6812621 Return-Path: X-Original-To: patchwork-linux-btrfs@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork1.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork1.web.kernel.org (Postfix) with ESMTP id BC5859F38B for ; Fri, 17 Jul 2015 04:57:14 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id CCBBB20770 for ; Fri, 17 Jul 2015 04:57:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9430E207A0 for ; Fri, 17 Jul 2015 04:57:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751334AbbGQE5I (ORCPT ); Fri, 17 Jul 2015 00:57:08 -0400 Received: from e28smtp06.in.ibm.com ([122.248.162.6]:48377 "EHLO e28smtp06.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750796AbbGQE5G (ORCPT ); Fri, 17 Jul 2015 00:57:06 -0400 Received: from /spool/local by e28smtp06.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 17 Jul 2015 10:27:03 +0530 Received: from d28dlp01.in.ibm.com (9.184.220.126) by e28smtp06.in.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 17 Jul 2015 10:27:00 +0530 X-Helo: d28dlp01.in.ibm.com X-MailFrom: chandan@linux.vnet.ibm.com X-RcptTo: linux-btrfs@vger.kernel.org Received: from d28relay03.in.ibm.com (d28relay03.in.ibm.com [9.184.220.60]) by d28dlp01.in.ibm.com (Postfix) with ESMTP id C84E9E0058; Fri, 17 Jul 2015 10:30:55 +0530 (IST) Received: from d28av02.in.ibm.com (d28av02.in.ibm.com [9.184.220.64]) by d28relay03.in.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id t6H4uwoe44302426; Fri, 17 Jul 2015 10:26:58 +0530 Received: from d28av02.in.ibm.com (localhost [127.0.0.1]) by d28av02.in.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id t6H3dUdP005230; Fri, 17 Jul 2015 09:09:30 +0530 Received: from localhost.localdomain.localdomain (lucca.austin.ibm.com [9.3.189.135]) by d28av02.in.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id t6H3dSpr005078; Fri, 17 Jul 2015 09:09:29 +0530 From: Chandan Rajendra To: fstests@vger.kernel.org Cc: Chandan Rajendra , linux-btrfs@vger.kernel.org, jbacik@fb.com Subject: [PATCH] generic/311: Disable dmesg check Date: Fri, 17 Jul 2015 00:56:43 -0400 Message-Id: <1437109003-2357-1-git-send-email-chandan@linux.vnet.ibm.com> X-Mailer: git-send-email 2.1.0 X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15071704-0021-0000-0000-000006517E95 Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org X-Spam-Status: No, score=-8.2 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP When running generic/311 on Btrfs' subpagesize-blocksize patchset (on ppc64 with 4k sectorsize and 16k node/leaf size) I noticed the following call trace, BTRFS (device dm-0): parent transid verify failed on 29720576 wanted 160 found 158 BTRFS (device dm-0): parent transid verify failed on 29720576 wanted 160 found 158 BTRFS: Transaction aborted (error -5) WARNING: at /root/repos/linux/fs/btrfs/super.c:260 Modules linked in: CPU: 3 PID: 30769 Comm: umount Tainted: G W L 4.0.0-rc5-11671-g8b82e73e #63 task: c000000079aaddb0 ti: c000000079a48000 task.ti: c000000079a48000 NIP: c000000000499aa0 LR: c000000000499a9c CTR: c000000000779630 REGS: c000000079a4b480 TRAP: 0700 Tainted: G W L (4.0.0-rc5-11671-g8b82e73e) MSR: 8000000100029032 CR: 28008828 XER: 20000000 CFAR: c000000000a23914 SOFTE: 1 GPR00: c000000000499a9c c000000079a4b700 c00000000103bdf8 0000000000000025 GPR04: 0000000000000001 0000000000000502 c00000000107e918 0000000000000cda GPR08: 0000000000000007 0000000000000007 0000000000000001 c0000000010f5044 GPR12: 0000000028008822 c00000000fdc0d80 0000000020000000 0000000010152e00 GPR16: 0000010002979380 0000000010140724 0000000000000000 0000000000000000 GPR20: ffffffffffffffff 0000000000000000 0000000000000000 0000000000000000 GPR24: c0000000151f61a8 0000000000000000 c000000055e5e800 c000000000aac270 GPR28: 00000000000004a4 fffffffffffffffb c000000055e5e800 c0000000679204d0 NIP [c000000000499aa0] .__btrfs_abort_transaction+0x180/0x190 LR [c000000000499a9c] .__btrfs_abort_transaction+0x17c/0x190 Call Trace: [c000000079a4b700] [c000000000499a9c] .__btrfs_abort_transaction+0x17c/0x190 (unreliable) [c000000079a4b7a0] [c000000000541678] .__btrfs_run_delayed_items+0xe8/0x220 [c000000079a4b850] [c0000000004d5b3c] .btrfs_commit_transaction+0x37c/0xca0 [c000000079a4b960] [c00000000049824c] .btrfs_sync_fs+0x6c/0x1a0 [c000000079a4ba00] [c000000000255270] .sync_filesystem+0xd0/0x100 [c000000079a4ba80] [c000000000218070] .generic_shutdown_super+0x40/0x170 [c000000079a4bb10] [c000000000218598] .kill_anon_super+0x18/0x30 [c000000079a4bb90] [c000000000498418] .btrfs_kill_super+0x18/0xc0 [c000000079a4bc10] [c000000000218ac8] .deactivate_locked_super+0x98/0xe0 [c000000079a4bc90] [c00000000023e744] .cleanup_mnt+0x54/0xa0 [c000000079a4bd10] [c0000000000b7d14] .task_work_run+0x114/0x150 [c000000079a4bdb0] [c000000000015f84] .do_notify_resume+0x74/0x80 [c000000079a4be30] [c000000000009838] .ret_from_except_lite+0x64/0x68 Instruction dump: ebc1fff0 ebe1fff8 4bfffb28 60000000 3ce2ffcd 38e7e818 4bffffbc 3c62ffd2 7fa4eb78 3863b808 48589e1d 60000000 <0fe00000> 4bfffedc 60000000 60000000 BTRFS: error (device dm-0) in __btrfs_run_delayed_items:1188: errno=-5 IO failure The call trace is seen when executing _run_test() for the 8th time. The above trace is actually a false-positive failure as indicated below, fsync-tester fsync(fd) Write delayed inode item to fs tree (assume transid to be 160) (assume tree block to start at logical address 29720576) md5sum $testfile This causes a delayed inode to be added Load flakey table i.e. drop writes that are initiated from now onwards Unmount filesystem btrfs_sync_fs is invoked Write 29720576 metadata block to disk free_extent_buffer(29720576) release_extent_buffer(29720576) Start writing delayed inode Traverse the fs tree (assume the parent tree block of 29720576 is still in memory) When reading 29720576 from disk, parent's blkptr will have generation set to 160. But the on-disk tree block will have an older generation (say, 158). Transid verification fails and hence the transaction gets aborted The test only cares about the FS instance before the unmount operation (i.e. the synced FS). Hence to get the test to pass, ignore the false-positive trace that could be generated. Signed-off-by: Chandan Rajendra --- tests/generic/311 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tests/generic/311 b/tests/generic/311 index d21b6eb..cd6391d 100755 --- a/tests/generic/311 +++ b/tests/generic/311 @@ -64,6 +64,8 @@ _require_xfs_io_command "falloc" [ -x $here/src/fsync-tester ] || _notrun "fsync-tester not built" +_disable_dmesg_check + rm -f $seqres.full SEED=1 testfile=$SCRATCH_MNT/$seq.fsync