Bug 5373 - rsync uses more space in destination even with -S specified
rsync uses more space in destination even with -S specified
Status: NEW
Product: rsync
Classification: Unclassified
Component: core
2.6.2
PA-RISC AIX
: P3 major
: ---
Assigned To: Wayne Davison
Rsync QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-04 01:50 UTC by Scott Bromley
Modified: 2008-04-04 09:13 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Bromley 2008-04-04 01:50:22 UTC
+++ This bug was initially created as a clone of Bug #3485 +++


I have a similar issue as Bug #3485 but on 2 AIX servers. The target filesystems continually run out of free space even though they are larger in size.

I am unable to use the sparse flag on rsync as the application relies on this fact. I am unsure if the following highlights the possible problem but I have attached an example of the AIX fileplace command showing an application file and the first time I have copied this file using rsync.

Source server
 # fileplace -v ALACTCP

File: ALACTCP  Size: 19724 bytes  Vol: /dev/cslv
Blk Size: 4096  Frag Size: 4096  Nfrags: 5
Inode: 6707  Mode: -rwxrwxrwx  Owner: root  Group: system

  Logical Extent
  --------------
  00894164-00894167              4 frags        16384 Bytes,  80.0%
  00894175                       1 frags         4096 Bytes,  20.0%

  5 frags over space of 12 frags:   space efficiency = 41.7%
  2 extents out of 5 possible:   sequentiality = 75.0%


Target Server
# fileplace -v ALACTCP

File: ALACTCP  Size: 19724 bytes  Vol: /dev/cslv
Blk Size: 4096  Frag Size: 4096  Nfrags: 5
Inode: 4  Mode: -rwxrwxrwx  Owner: root  Group: system

  Logical Extent
  --------------
  00000512-00000516              5 frags        20480 Bytes,  100.0%

  5 frags over space of 5 frags:   space efficiency = 100.0%
  1 extent out of 5 possible:   sequentiality = 100.0%
Comment 1 Matt McCutchen 2008-04-04 09:13:28 UTC
(In reply to comment #0)
> The target
> filesystems continually run out of free space even though they are larger in
> size.

Do I understand you correctly: you are copying a source filesystem to a destination filesystem that is larger and contains nothing but the copied data, so you expect the data to fit, but it doesn't?

Be sure to use --delete to delete any extraneous files from the destination, and if the source contains hard-linked files, use -H to preserve the hard links.  If the problem persists, you'll have to work a bit harder to figure out where the expansion is occuring; follow Wayne's procedure in "thing to check" #3 in bug 3485 comment 3 to generate and compare listings of the source and destination filesystems.

> I am unable to use the sparse flag on rsync as the application relies on this
> fact.

What "fact" are you referring to?  Sparse source files will take up more space on the destination unless you use the -S option.  If you have sparse source files but your application won't let you preserve their sparsity, you need more space on the destination; there is nothing rsync can do about that.  If none of the source files are sparse, -S shouldn't matter.

> I am unsure if the following highlights the possible problem but I have
> attached an example of the AIX fileplace command showing an application file
> and the first time I have copied this file using rsync.

I'm not familiar with fileplace, but just looking at the output I see no evidence of expansion of any kind.