linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Luciano ES <lucmove@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Same size drive has less usable space
Date: Thu, 20 Dec 2018 09:45:52 -0800	[thread overview]
Message-ID: <20181220174552.GC27208@magnolia> (raw)
In-Reply-To: <20181220131305.2a84b717@lud1.home>

On Thu, Dec 20, 2018 at 01:13:05PM -0200, Luciano ES wrote:
> I have a new drive for backups. 
> I copied everything over and now I have this problem:
> 
> Filesystem      Size  Used 	 Avail 	Use% 	Mounted on
> /dev/sda1   	931G  914G   18G  	99% 	/xx
> /dev/sdb1   	931G  920G   11G  	99% 	/xxbkp
> 
> So 914GB from the old drive expand and become 920GB. The new drive 
> is supposed to be the same size, but for some reason it can't 
> really hold it all. I will be forced to waste precious gigabytes.
> 
> I tried to format the new one exactly like the old one, but 
> it was not possible:
> 
> $ xfs_info /xx
> meta-data=/dev/sda1     isize=256    agcount=8, agsize=30506944 blks
>          =              sectsz=4096  attr=2, projid32bit=1
>          =              crc=0        finobt=0 spinodes=0 rmapbt=0
>          =              reflink=0
> data     =              bsize=4096   blocks=244055552, imaxpct=25
>          =              sunit=0      swidth=0 blks
> naming   =version 2     bsize=4096   ascii-ci=0 ftype=0
> log      =internal      bsize=4096   blocks=119167, version=2
>          =              sectsz=4096  sunit=1 blks, lazy-count=1
> realtime =none          extsz=4096   blocks=0, rtextents=0
> 
> 
> $ xfs_info /xxbkp
> meta-data=/dev/sdb1     isize=512    agcount=8, agsize=61013888 blks
>          =              sectsz=512   attr=2, projid32bit=1
>          =              crc=1        finobt=1 spinodes=1 rmapbt=0
>          =              reflink=0
> data     =              bsize=2048   blocks=488111104, imaxpct=25

Just FYI you'll get a lot better performance from the filesystem if the
blocksize is the same as cpu page size (4k I think) and if the
filesystem isn't totally full.

But yeah, either unmount /xx and use xfs_copy one disk to the other, or
format the backup drive with the same parameters (I'll leave that to the
other parts of this thread).

--D

>          =              sunit=0      swidth=0 blks
> naming   =version 2     bsize=4096   ascii-ci=0 ftype=1
> log      =internal      bsize=2048   blocks=238335, version=2
>          =              sectsz=512   sunit=0 blks, lazy-count=1
> realtime =none          extsz=4096   blocks=0, rtextents=0
> 
> 
> I guess at least part of the problem is CRC enabled in the second 
> one. So, is there anything I can do to make all the data fit in the 
> new drive?
> 
> TIA
> 
> -- 
> Luciano ES
> >>

  parent reply	other threads:[~2018-12-20 17:45 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.
2018-12-20 17:45 ` Darrick J. Wong [this message]
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=20181220174552.GC27208@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lucmove@gmail.com \
    /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).