From: Luciano ES <lucmove@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: Re: Same size drive has less usable space
Date: Fri, 21 Dec 2018 22:49:50 -0200 [thread overview]
Message-ID: <20181221224950.45950329@lud1.home> (raw)
In-Reply-To: <20181221175737.1a6022b8@harpe.intellique.com>
On Fri, 21 Dec 2018 17:57:37 +0100, Emmanuel Florac wrote:
> Le Thu, 20 Dec 2018 13:13:05 -0200
> Luciano ES écrivait:
>
> > 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?
>
> Your new drive is using 4K blocks, while the old one uses 512b blocks.
> That's why they can't match.
**************************
What 512b? There is no 512 in the old drive.
$ 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
= 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
--
Luciano ES
>>
prev parent reply other threads:[~2018-12-22 0:49 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
2018-12-21 16:57 ` Emmanuel Florac
2018-12-22 0:49 ` Luciano ES [this message]
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=20181221224950.45950329@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 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.