From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q5JDqaLl098948 for ; Tue, 19 Jun 2012 08:52:36 -0500 Received: from blade3.isti.cnr.it (blade3.isti.cnr.it [194.119.192.19]) by cuda.sgi.com with ESMTP id KT5P4gD8pJAyrJfc (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 19 Jun 2012 06:52:35 -0700 (PDT) Received: from [192.168.6.232] ([155.253.6.254]) by mx.isti.cnr.it (PMDF V6.5-x6 #31988) with ESMTPSA id <01OGVIYF00W4ODSR3C@mx.isti.cnr.it> for xfs@oss.sgi.com; Tue, 19 Jun 2012 15:51:39 +0200 (MEST) Date: Tue, 19 Jun 2012 15:52:15 +0200 From: Spelic Subject: Re: Ext4 and xfs problems in dm-thin on allocation and discard In-reply-to: <20120619133041.GB6811@redhat.com> Message-id: <4FE0840F.2050704@shiftmail.org> MIME-version: 1.0 References: <4FDF9EBE.2030809@shiftmail.org> <20120619015745.GJ25389@dastard> <20120619031241.GA3884@redhat.com> <20120619131649.GA6811@redhat.com> <20120619133041.GB6811@redhat.com> 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" Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Mike Snitzer Cc: xfs@oss.sgi.com, device-mapper development , Spelic , =?UTF-8?B?THVrw6HFoSBDemVybmVy?= , linux-ext4@vger.kernel.org On 06/19/12 15:30, Mike Snitzer wrote: > I don't recall Spelic saying anything about EOPNOTSUPP. So what has > made you zero in on an -EOPNOTSUPP return (which should not be > happening)? Exactly: I do not know if EOPNOTSUPP is being returned or not. If this helps, I have configured dm-thin via lvm2 LVM version: 2.02.95(2) (2012-03-06) Library version: 1.02.74 (2012-03-06) Driver version: 4.22.0 from dmsetup table I only see one option : "skip_block_zeroing", if and only if I configure it with -Zn . I do not see anything regarding ignore_discard vg1-pooltry1-tpool: 0 20971520 thin-pool 252:1 252:2 2048 0 1 skip_block_zeroing vg1-pooltry1_tdata: 0 20971520 linear 9:20 62922752 vg1-pooltry1_tmeta: 0 8192 linear 9:20 83894272 vg1-thinlv1: 0 31457280 thin 252:3 1 and in dmesg: [ 33.685200] device-mapper: thin: Discard unsupported by data device (dm-2): Disabling discard passdown. [ 33.709586] device-mapper: thin: Discard unsupported by data device (dm-6): Disabling discard passdown. I do not know what is the mechanism for which xfs cannot unmap blocks from dm-thin, but it really can't. If anyone has dm-thin installed he can try. This is 100% reproducible for me. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs