From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?UMOhZHJhaWcgQnJhZHk=?= Subject: Re: fallocate vs ENOSPC Date: Mon, 28 Nov 2011 12:02:14 +0000 Message-ID: <4ED37846.3090208@draigBrady.com> References: <4ECF6D41.2040801@draigBrady.com> <20111125104050.GA26729@infradead.org> <20111127031455.GK5167@thunk.org> <20111127234331.GW2386@dastard> <20111128051054.GZ2386@dastard> <4ED34C66.8050300@draigBrady.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: david@fromorbit.com, tytso@MIT.EDU, hch@infradead.org, linux-fsdevel@vger.kernel.org To: tao.peng@emc.com Return-path: Received: from mail1.vodafone.ie ([213.233.128.43]:16078 "EHLO mail1.vodafone.ie" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752190Ab1K1MCQ (ORCPT ); Mon, 28 Nov 2011 07:02:16 -0500 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 11/28/2011 10:41 AM, tao.peng@emc.com wrote: > Just out of curiosity, how is it going to work with sparse files? By = default, cp uses --sparse=3Dauto. And for sparse files, it avoids some = disk allocation automatically. With fallocate(), do you plan to change = the semantics? With sparse files, coreutils currently uses fiemap (with a sync), and thus has full details of what is sparse or empty etc. So as detailed=C2=B9 on the coreutils list, the conversions would be: --sparse=3Dauto =3D> 'Empty' -> 'Empty' --sparse=3Dalways =3D> 'Empty' -> 'Hole' --sparse=3Dnever =3D> 'Hole' -> 'Empty' cheers, P=C3=A1draig. =C2=B9 http://debbugs.gnu.org/9500#14 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html