From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 238167F3F for ; Thu, 6 Nov 2014 04:54:47 -0600 (CST) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay1.corp.sgi.com (Postfix) with ESMTP id 1298A8F8033 for ; Thu, 6 Nov 2014 02:54:43 -0800 (PST) Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by cuda.sgi.com with ESMTP id DBY3543EuOUuLP48 (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Thu, 06 Nov 2014 02:54:39 -0800 (PST) Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id sA6Ascqc006999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 6 Nov 2014 10:54:39 GMT Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sA6AsbtC018521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 6 Nov 2014 10:54:38 GMT Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sA6AsbeH019313 for ; Thu, 6 Nov 2014 10:54:37 GMT Message-ID: <545B541A.60800@oracle.com> Date: Thu, 06 Nov 2014 13:57:30 +0300 From: alexander.tsvetkov@oracle.com MIME-Version: 1.0 Subject: scratch filesystem corruptions List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com Hello, I've noted that the enabling of scratch device post checks after xfstests commit "common: Check the file system consistency on SCRATCH_DEV" has started to show the scratch filesystem corruptions for the following tests runs: xfs/050,134,187,244,287. I have these corruptions reproduced with upstream linux kernel of version 3.15 and the latest xfsprogs/xfstests. Are these known issues? Thanks, Alexander Tsvetkov _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs