Hi Harry, I don't know it is the case here, but often a difference of size after cp or rsync is caused by hardlinks not being preserved. Try to add the -H option to rsync to see if that changes something.
Yann 2013/8/31 Laurent Blume <[email protected]> > On 2013-08-29 10:17 PM, Harry Putnam wrote: > > Running Openindiana (solaris branch) and using some csw tools too. > > > > csw stuff is installed at /opt/csw. Since my root pool space is > > shrinking I thought I might move all of /opt off on a different zpool > > on a different disc. Then just put a symlink in place at /opt. > > Using a symlink is a terrible idea, and furthermore - why? You can just > set your new dataset mountpoint to be /opt. > > To be clear: if you use symlinks, updates expecting it to be a directory > can just remove the symlink and recreate as an empty directory. This was > particularly true in S10; on IPS, I expect that "pkg fix" would not be > happy about them either. > > > I decided to do it with rsync and after rsyncing everything to /t1/opt > > (rsync -avv /opt/ /t1/opt/ ) > > > > But when I check the result with du I find a huge difference in size. > > > > the original /opt shows 355 MB but the copied opt shows only 173 MB > > > > I thing tried with copy using gnu copy and did 'cp -a' /opt/t1/ > > > > Again it comes up with the big difference in size.. > > > > Any ideas what could explain that? > > Posting exactly what you did would help understand. Also, you can do a > "find . | sort > file" in each directory and compare the files. > > Laurent > > > _______________________________________________ > users mailing list > [email protected] > https://lists.opencsw.org/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/users
