All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos E. R." <robin.listas@telefonica.net>
To: Linux-XFS mailing list <linux-xfs@vger.kernel.org>
Subject: Re: Same size drive has less usable space
Date: Thu, 20 Dec 2018 19:47:21 +0100	[thread overview]
Message-ID: <89b5b424-01a0-5369-963f-8adc044b5f2c@telefonica.net> (raw)
In-Reply-To: <20181220163943.5d8c6c2c@lud1.home>


[-- Attachment #1.1: Type: text/plain, Size: 795 bytes --]

On 20/12/2018 19.39, Luciano ES wrote:
> On Thu, 20 Dec 2018 11:32:33 -0600, Eric Sandeen wrote:
> 
>> but ok, I missed that you had 2k blocks on your backup disk.... I
>> don't really know what you're trying to do here, TBH.
> 
> Smaller blocks waste less space. In ext3/4, I've always used 2k or 
> even 1k blocks. It does save space. Doesn't it in XFS too?

Depends. Not always "smaller blocks waste less space". It depends on the
mix of filesizes. If most files are big, then no.

Consider, for instance, that in a filesystem with a fixed number of
inodes (like ext2/3/4), when using small blocks the structures that list
the blocks are larger, simply because there are more blocks.

-- 
Cheers / Saludos,

		Carlos E. R.
		(from 42.3 x86_64 "Malachite" at Telcontar)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-12-20 18:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 15:13 Same size drive has less usable space Luciano ES
2018-12-20 16:04 ` Carlos E. R.
2018-12-20 16:10 ` Eric Sandeen
2018-12-20 16:26   ` Darrick J. Wong
2018-12-20 16:59     ` Eric Sandeen
2018-12-20 16:55   ` Luciano ES
2018-12-20 17:32     ` Eric Sandeen
2018-12-20 18:39       ` Luciano ES
2018-12-20 18:47         ` Carlos E. R. [this message]
2018-12-20 17:45 ` Darrick J. Wong
2018-12-21 16:57 ` Emmanuel Florac
2018-12-22  0:49   ` Luciano ES

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89b5b424-01a0-5369-963f-8adc044b5f2c@telefonica.net \
    --to=robin.listas@telefonica.net \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.