linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano ES <lucmove@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: Re: Same size drive has less usable space
Date: Thu, 20 Dec 2018 14:55:29 -0200	[thread overview]
Message-ID: <20181220145529.1292ec61@lud1.home> (raw)
In-Reply-To: <6ab0a568-4732-905a-d45d-209f4bb0cfb0@sandeen.net>

On Thu, 20 Dec 2018 10:10:42 -0600, Eric Sandeen wrote:

> Well, you have larger inodes on xxbkp for starters.

I can't make smaller inodes on this disk.

"specified blocksize 2048 is less than device physical sector size 4096
switching to logical sector size 512"

another attempt:

"specified blocksize 2048 is less than device physical sector size 4096
switching to logical sector size 512
Minimum inode size for CRCs is 512 bytes"

So yes, it's the CRC feature.


On Thu, 20 Dec 2018 10:10:42 -0600, Eric Sandeen wrote:

> # mkfs.xfs -m crc=0,finobt=1 -i sparse=0 -n ftype=0

Your command line doesn't work. It says:

finobt not supported without CRC support

I have confirmed that disabling CRC allows me to have smaller inodes, 
but I wish I could keep that feature. It sounds like something I want 
to have, to improve reliability.

Is there another way?


On Thu, 20 Dec 2018 08:26:41 -0800, Darrick J. Wong wrote:

> Why not xfs_copy?

Good question. But then the copy would not have CRC enabled either 
because the original doesn't. 

Looks like I an going to have to commit to having CRC always on 
from now on. And I am going to lose about 7GB of space for that.

Is it worth it?


-- 
Luciano ES
>>

  parent reply	other threads:[~2018-12-20 16:55 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 [this message]
2018-12-20 17:32     ` Eric Sandeen
2018-12-20 18:39       ` Luciano ES
2018-12-20 18:47         ` Carlos E. R.
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=20181220145529.1292ec61@lud1.home \
    --to=lucmove@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).