From: Wayne Walker <wwalker@crossroads.com>
To: xfs@oss.sgi.com
Subject: Re: Usage bigger after copy?
Date: Mon, 15 Oct 2012 14:52:43 -0500 [thread overview]
Message-ID: <507C698B.1020801@crossroads.com> (raw)
In-Reply-To: <2368408.eSeMIOhpGu@saturn>
[-- Attachment #1.1: Type: text/plain, Size: 2055 bytes --]
Michael,
My guess is that you used rsync but did not use H.
retry your rsync with:
rsync -aHx /usr /1/
H will preseve hard links for you and probably make most of your
directory size differences go away.
Wayne
On 10/15/2012 01:07 PM, Michael Monnerie wrote:
> I know that the speculative prealloc of xfs can make files bigger on a
> destination, but I thought an "echo 3 >/proc/sys/vm/drop_caches" would
> help. I even umounted both filesystems, but the destination is bigger:
>
> sys1 Blocks 8378368 Used 2631368 Avail 5747000
> sys2 Blocks 8378368 Used 2966566 Avail 5411812
>
> Both are VMs, have a 16G disk, partitioned same size, both on LVM,
> copied with rsync. xfs_info show the same for both:
>
> meta-data=/dev/mapper/dns1--system-root isize=256 agcount=4,
> agsize=524288 blks
> = sectsz=512 attr=2
> data = bsize=4096 blocks=2097152, imaxpct=25
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=2560, version=2
> = sectsz=512 sunit=0 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
> So why is there such a huge diff in size? 300M, 2.6G:2.9G, is a big
> number. I found these dirs to be very different:
>
> ( I rebooted here compared to results before, but same strangeness )
> # du -s /1/usr/lib/locale/* /usr/lib/locale/*|sort -n|grep YU
> 20 /usr/lib/locale/sh_YU.utf8
> 1760 /1/usr/lib/locale/sh_YU.utf8
>
> But comparing them directly, they are the same:
>
> # du -s /1/usr/lib/locale/sh_YU.utf8 /usr/lib/locale/sh_YU.utf8
> 1760 /1/usr/lib/locale/sh_YU.utf8
> 1760 /usr/lib/locale/sh_YU.utf8
>
> So what makes "du" show a huge different when the dir above gets
> scanned, versus when you compare dirs directly?
>
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
[-- Attachment #1.2: Type: text/html, Size: 2703 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-10-15 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 18:07 Usage bigger after copy? Michael Monnerie
2012-10-15 19:52 ` Wayne Walker [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=507C698B.1020801@crossroads.com \
--to=wwalker@crossroads.com \
--cc=xfs@oss.sgi.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 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.