From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 44BA8259CBF for ; Thu, 6 Nov 2025 16:31:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762446704; cv=none; b=W7T2GU+cA56P9GqRkngfRx9m/5Dg3IAYi4IW2x4bqWqlZEv5PFe4mGi01eew7VjlnyBePKZo7+CFKaA46L4Y67Fj3aDE/YuOiHlBDzfGSFBGM6j8tWgMEP5KWz5X00QOgD0CR3egRnmQLyP2Li+btrmH3ifEdVJVXNKyq8Ecg3k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762446704; c=relaxed/simple; bh=mHsw22qvoUn8BNsltylWxuUHy6Ate8i2qX8bCfUjMPY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=M0YMl91qocakGcB13LOfD0QawpI6dtY7OfL8mQdoXdYYjucz1YGWrL5MuNnQIrBJyfcaBtYic3CdA+rmgS/9AMjycRI3L/dRY7jYdzt5mElhVJ/N3ZLAMmnlnZrej4YIeospN1Gg0t8BSualB+65JM3100Q3KdEqyilxp0hZets= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=BqgaN4QW; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="BqgaN4QW" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1762446702; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wwzkm+v1gtKVPuRw/kAUlsMgFI4I+9PdJpOVJqEwSzA=; b=BqgaN4QWILOqXUUldGDxKjlqaj05rQoY4i7ef9hEtnpYZ+DGnukSxlpnmlAzQ45UkXeeiN j62AUtZ516SQKN2ybjeZKdEDgR8s11SdHMQIhfn7clwZ6l65ONj+f7DL8dr+mkR8oxdJWq RvWp/MtOtj0YA5AaeRJfW6zLSuZx8gk= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-332-8Q9rj2z3NNaU_pgt6vTISg-1; Thu, 06 Nov 2025 11:31:38 -0500 X-MC-Unique: 8Q9rj2z3NNaU_pgt6vTISg-1 X-Mimecast-MFC-AGG-ID: 8Q9rj2z3NNaU_pgt6vTISg_1762446696 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id DB9F01955E7F; Thu, 6 Nov 2025 16:31:34 +0000 (UTC) Received: from fweimer-oldenburg.csb.redhat.com (unknown [10.45.224.98]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id BB62F1800346; Thu, 6 Nov 2025 16:31:30 +0000 (UTC) From: Florian Weimer To: Matthew Wilcox Cc: Christoph Hellwig , Hans Holmberg , linux-xfs@vger.kernel.org, Carlos Maiolino , Dave Chinner , "Darrick J . Wong" , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, libc-alpha@sourceware.org Subject: Re: [RFC] xfs: fake fallocate success for always CoW inodes In-Reply-To: (Matthew Wilcox's message of "Thu, 6 Nov 2025 14:42:30 +0000") References: <20251106133530.12927-1-hans.holmberg@wdc.com> <20251106135212.GA10477@lst.de> Date: Thu, 06 Nov 2025 17:31:28 +0100 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-xfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 * Matthew Wilcox: > On Thu, Nov 06, 2025 at 02:52:12PM +0100, Christoph Hellwig wrote: >> On Thu, Nov 06, 2025 at 02:48:12PM +0100, Florian Weimer wrote: >> > * Hans Holmberg: >> > >> > > We don't support preallocations for CoW inodes and we currently fail >> > > with -EOPNOTSUPP, but this causes an issue for users of glibc's >> > > posix_fallocate[1]. If fallocate fails, posix_fallocate falls back on >> > > writing actual data into the range to try to allocate blocks that way. >> > > That does not actually gurantee anything for CoW inodes however as we >> > > write out of place. >> > >> > Why doesn't fallocate trigger the copy instead? Isn't this what the >> > user is requesting? >> >> What copy? > > I believe Florian is thinking of CoW in the sense of "share while read > only, then you have a mutable block allocation", rather than the > WAFL (or SMR) sense of "we always put writes in a new location". Ahh. That's a new aspect to the discussion that was previously lost to me. Previous discussions focused on cases where the kernel couldn't do the pre-population operation safely even though it was beneficial from an application perspective. And not cases where the operation was meaningless because of the way the file system was implemented. (Pre-allocating CoW space as part of fallocate appears to be difficult because I don't see how to surface this space usage to applications and adminstrators.) It's been a few years, I think, and maybe we should drop the allocation logic from posix_fallocate in glibc? Assuming that it's implemented everywhere it makes sense? There are more always-CoW, compressing file systems these days, so applications just have to come to terms with the fact that even after posix_fallocate, writes can still fail, and not just because of media errors. So maybe posix_fallocate isn't that meaningful anymore. Thanks, Floriana