From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (Postfix) with ESMTP id 3AA427CA3 for ; Thu, 2 Jun 2016 09:19:19 -0500 (CDT) Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by relay2.corp.sgi.com (Postfix) with ESMTP id 0C32B304067 for ; Thu, 2 Jun 2016 07:19:19 -0700 (PDT) Received: from bombadil.infradead.org ([198.137.202.9]) by cuda.sgi.com with ESMTP id 2UPRWUQXzVrL1K2C (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 02 Jun 2016 07:19:16 -0700 (PDT) From: Christoph Hellwig Subject: [RFC] allow enabling reflinks at runtime Date: Thu, 2 Jun 2016 16:19:07 +0200 Message-Id: <1464877150-20457-1-git-send-email-hch@lst.de> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: darrick.wong@oracle.com Cc: xfs@oss.sgi.com I've had some vocal user requests to allow enabling reflinks at run time, which happens to be a mostly trivial feature. The only caveat is that we need a large enough log size to support the reflink requirements, but for typical large file systems that's not an issue. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs