From owner-freebsd-questions@freebsd.org Fri Oct 12 18:36:39 2018 Return-Path: Delivered-To: freebsd-questions@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 61DAA10C66DF for ; Fri, 12 Oct 2018 18:36:39 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E1A808FD91 for ; Fri, 12 Oct 2018 18:36:38 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr1-x441.google.com with SMTP id 61-v6so14445369wrb.6 for ; Fri, 12 Oct 2018 11:36:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=ekUHzb52rmxmz6PS0cLq7NXLn8f9Zyip23QTzk3ffG4=; b=IL8US42J0DfwvOYTpj1X4rXhlstHwTvzaMy4fFECePW6SlZPNjSFoejY3PGeKH0gMo efE/7C3GqoVuKQPHkgKStVnv1w9lHfj2oRHX4QvGyDbSwlvHJAdurmbpqpPBQZst+tUL UE0ChQV4bm4MSMvwg3586Cc8v5pZ0o8uoOt9JPD0Mm1C/6KCVkWKlTx8fbZCnD+HOhmj JqIsAKpDcXQ+BDzEqulStBqD+P0sXOErhtZ9lzFzB8WcZj6pRZ33mcaXCnEIjDL8dowF oG6g8cWmPvcZqEEUKAAyUrtT7lVxm1W3CumCKEqf/bUuPfMHRt4TZoCluz5NBWY6tQgb nMXQ== X-Gm-Message-State: ABuFfohHZRo8HtHVD339+/Vn6BxM9R9OCbhsKRHPwacG8nAQaJuay85Q wFqCtGmwvmft+/qZKneaSIZp/TQjpKg= X-Google-Smtp-Source: ACcGV60tIuTddbFqsmzMyZcwxq4z0oFVKUIIqwUFkfBXHvay0nAPtLxlQ8M9Rt5VLTrj9gkwRYqdBw== X-Received: by 2002:adf:ea42:: with SMTP id j2-v6mr6609824wrn.224.1539369397432; Fri, 12 Oct 2018 11:36:37 -0700 (PDT) Received: from gumby.homeunix.com ([90.209.155.76]) by smtp.gmail.com with ESMTPSA id 18-v6sm3049862wmw.26.2018.10.12.11.36.35 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 12 Oct 2018 11:36:36 -0700 (PDT) Date: Fri, 12 Oct 2018 19:36:33 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: swap to a sparse file Message-ID: <20181012193633.7dc32f86@gumby.homeunix.com> In-Reply-To: <20181011085114.bfcdb701b3644728a71eaa38@sohara.org> References: <20181011014705.GA17798@admin.sibptus.ru> <20181011085114.bfcdb701b3644728a71eaa38@sohara.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 18:36:39 -0000 On Thu, 11 Oct 2018 08:51:14 +0100 Steve O'Hara-Smith wrote: > On Thu, 11 Oct 2018 08:47:05 +0700 > Victor Sudakov wrote: > > > Is there any good reason I can't just "truncate -s2G /swap0" and > > make the swap a sparse file? > > Just one - if the space isn't there when the system needs it > there will be a panic. Is that really the only reason? I've not paid much attention, but the warnings I've heard about this have made it sound a lot worse.