From owner-freebsd-current@freebsd.org Sat Feb 10 19:21:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 219B1F15E08 for ; Sat, 10 Feb 2018 19:21:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 789576D134 for ; Sat, 10 Feb 2018 19:21:53 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id a204so15531466lfa.2 for ; Sat, 10 Feb 2018 11:21:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9qaQDr685zUJ24ISz4SmEC8SLh+qNWOt0leXU3BLF9w=; b=IgMd4HGgtCasMB1IaMaYJMj8Pmrv0AVO5EXFFWfD601CTptG16Jk3Yxfe4TA9gB2ML Ug1wiKJ6ELdljW2OQphIa/wYTcdFy2olEU7trf8yl6zYPxKJOgHaHCowMdBZ2WKVyP0c g+D9LaIyjgVvIDPTPuUDLCjpi+5uBlH81FNTd0frkcbsQIXI/XFuxA4qJ2HqGpyz0OEf 2Jo7zsgzA1VLmjIv+o+0JJtNagiIiYPz+ytuprH8HzycyUN1oxhjqDw/gQbdNxZvERKg zPDCvg7c4ItT1AnVwhOPMO6GIVY/x9PaKGweK2wHQid8XZQVMm+J7QcfmZozv0ulIqSL brRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9qaQDr685zUJ24ISz4SmEC8SLh+qNWOt0leXU3BLF9w=; b=JqmLwJpJPRVenVfDT0RFZikwfnkPJcfLWGoFOKlwOV0wGdb5P8pr2l+bbeq3NP3DAF DMovhCUtI0DscX4+oRRUUJDE1Y52InJKmMbmHp18tJ2q5riHrz62jvbC6boyqqX0IM2d +/HHny9id1o/JOZmlmwo8qOqE/Vkyyw56cj5xcTOMGsFoPf3nUtXnhL2VSFWY/JVaMpW D/2KBWq6SpMQd04u1yaofSBfYM88tQ775AIPExkS84+JyrDWdec8iMadhFQed5a+CihI Xs2beyDtZ7NWpiSsaUwWFI7x33OBOQZZ71SNUVEvjd6OJNKyv4FbRhJBXLXJx/qvsNQX 2J/Q== X-Gm-Message-State: APf1xPCB5VrbIYjeksgDOetpZONsSeS6B5ZCOksW0cw69p8RV9vEUyrg g35CC9Y3K4clzxol+LWBu0xXQRN/RMTimuXsYjc= X-Google-Smtp-Source: AH8x2254XmBoI8KNDg0dBr2mohfuQI1M/saVOGfLmTQOBjaLHAjDLp5X3VKWNrY4M1Z7AVzBoX+ZTV5G0Jg/r0TPND4= X-Received: by 10.46.16.1 with SMTP id j1mr4214369lje.139.1518290511926; Sat, 10 Feb 2018 11:21:51 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Sat, 10 Feb 2018 11:21:50 -0800 (PST) In-Reply-To: <985b6d77-9f27-f6f4-ea0e-165951d91048@digiware.nl> References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <985b6d77-9f27-f6f4-ea0e-165951d91048@digiware.nl> From: Alan Somers Date: Sat, 10 Feb 2018 12:21:50 -0700 X-Google-Sender-Auth: AU7nRwCQ-eMHhX5wJiGPenFa764 Message-ID: Subject: Re: posix_fallocate on ZFS To: Willem Jan Withagen Cc: freebsd current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sat, 10 Feb 2018 19:21:54 -0000 On Sat, Feb 10, 2018 at 11:50 AM, Willem Jan Withagen wrote: > On 10/02/2018 19:24, Alan Somers wrote: > >> On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > > wrote: >> >> Hi, >> >> This has been disabled on ZFS since last November. >> And I do understand the rationale on this. >> >> BUT >> >> I've now upgraded some of my HEAD Ceph test systems and they now >> fail, since Ceph uses posix_fallocate() to allocate space for the >> FileStore-journal. >> >> Is there any expectation that this is going to fixed in any near >> future? >> >> --WjW >> >> >> No. It's fundamentally impossible to support posix_fallocate on a COW >> filesystem like ZFS. Ceph should be taught to ignore an EINVAL result, >> since the system call is merely advisory. >> > > Yup, that was what I'm going to do. > But then I would like to know how to annotate it. > > And I guess that I'd get reactions submitting code to fix this, since the > journal could run out of space. > So I'd beter know what is going on. > > I seem to remember that on a pool level is is possible to reserve space > whilest creating a filesystem? And then it could/should be fixed when > building the disk-infra for an OSD. > Yes, you can easily reserve space for an entire filesystem. Just do for example "zfs create -o reservation=64GB mypool/myfs" .