From owner-freebsd-current@freebsd.org Tue Nov 7 18:12:25 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CC8CE608D2; Tue, 7 Nov 2017 18:12:25 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f65.google.com (mail-lf0-f65.google.com [209.85.215.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1818C7CC5A; Tue, 7 Nov 2017 18:12:24 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f65.google.com with SMTP id l23so96038lfk.10; Tue, 07 Nov 2017 10:12:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=2J8zeNUQz37Uoa7k+F5SIaZIhmG9fvH9PbGYYmS05JQ=; b=J9WK30dGRAzOvapDd2ydKi3CRkLJ93pBs2APkEfZ3i+ZoKUB6ohl5yKLbMGWqKvdpx 4ZgzTGEyyiZTWWFnHGr1bZOQQC3fFWGj3wRKJkH1Jz3pifLylAYxrG5l+xc79GRo7Q6S WiwyX5s5tbLNdbXLbG/RaugbDEgd4wtBFUgfqaZVolC9fTmBAIhRYywyTbPdJ+ooqIFh 2KgPnXcNmehzZ2gTNJ3fqW2aXl+qlCRMr3xwLrBpgEmKjcc7L9m/BVbTMJMffhda21yU YNxG9tCc8WfqFtL+PiJM8K5krdQVcFB/5LTi145XBqu0WrYi/Xqi3EuLbGRMPdNFFrRA tHsQ== X-Gm-Message-State: AJaThX6udWuZ3BG0GmlhPzI3U8SplHD0jVyeVjVWopXFsdhj/Nt6JedG urnz1MDv4Dta84XrX+v082oBfa4T X-Google-Smtp-Source: ABhQp+Q44G+eZtFci0M8z32UdMOViVGibX0kL5Aa92W2XPdl1HYn25GPn/HDdh1KS9e1I4tipsvQOg== X-Received: by 10.25.204.211 with SMTP id c202mr6720280lfg.220.1510078336693; Tue, 07 Nov 2017 10:12:16 -0800 (PST) Received: from [192.168.0.197] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id r125sm325317lfr.46.2017.11.07.10.12.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Nov 2017 10:12:15 -0800 (PST) Subject: Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected To: Ian Lepore , freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: <7e5599e4-2faa-29b6-4fb2-a0744a12681a@FreeBSD.org> <1509989176.99235.79.camel@freebsd.org> From: Andriy Gapon Message-ID: <153bfe2b-e65e-2036-3391-984c6ba00ffe@FreeBSD.org> Date: Tue, 7 Nov 2017 20:12:13 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <1509989176.99235.79.camel@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2017 18:12:25 -0000 On 06/11/2017 19:26, Ian Lepore wrote: > On Mon, 2017-11-06 at 17:40 +0200, Andriy Gapon wrote: >> From UPDATING: >> The naive and non-compliant support of posix_fallocate(2) in ZFS >> has been removed as of r325320.  The system call now returns EINVAL >> when used on a ZFS file.  Although the new behavior complies with the >> standard, some consumers are not prepared to cope with it. >> One known victim is lld prior to r325420. >> > > It just popped into my head... does this mean that kernels running > r325320+ on systems using ZFS will be unable to host build jails for > earlier versions / branches because lld will fail in the jail? I am afraid that this is true. > I think that will be a big problem for the ports team's package > building process, and for anyone using poudriere. I hope that lld is not that widely used now. But I admit that I put the cart before the horse. I didn't expect that posix_fallocate is used in the development toolchain and I didn't try to check for it. -- Andriy Gapon