From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH v3 2/4] ovl: use vfs_clone_file_range() for copy up if possible Date: Wed, 21 Sep 2016 22:57:24 +0100 Message-ID: <20160921215724.GV2356@ZenIV.linux.org.uk> References: <1473856994-27463-1-git-send-email-amir73il@gmail.com> <1473856994-27463-3-git-send-email-amir73il@gmail.com> <20160921214814.GC10454@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20160921214814.GC10454@dastard> Sender: linux-fsdevel-owner@vger.kernel.org To: Dave Chinner Cc: Amir Goldstein , Miklos Szeredi , "linux-unionfs@vger.kernel.org" , Christoph Hellwig , linux-xfs@vger.kernel.org, "Darrick J . Wong" , linux-fsdevel List-Id: linux-unionfs@vger.kernel.org On Thu, Sep 22, 2016 at 07:48:15AM +1000, Dave Chinner wrote: > If you get any error other than -EXDEV or -EOPNOTSUPP from a clone > operation, there's somethign seriously wrong with the metadata of > the inode or th eunderlying storage. Such as -ENOSPC?