AIXThis forum is for the discussion of IBM AIX.
eserver and other IBM related questions are also on topic.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
When trying to rsynch a 1.2TB volume over to our new 12TB volume and getting the error below. We can copy files to the volume using other tools without issue, but we really need rsync to minimize the outage when we put the new volume into production use. Could it be due to the size of the new volume, a security issue, or is there something else going on? If rsynch isn't going to work is there another tool we could use to do the initial copy, then cleanup the delta during our maintenance window?
- ULIMIT is Unlimited, so thats not the issue.
Code:
servername username > /busobjdata/do/temp /opt/apps/busobj/busobjdata/do/frs/input < sending incremental file list
rsync: opendir "/opt/apps/busobj/busobjdata/do/temp" failed: Value too large to be stored in data type (127)
temp/
rsync: opendir "/opt/apps/busobj/busobjdata/do/frs/input/temp" failed: Value too large to be stored in data type (127)
sent 46 bytes received 16 bytes 124.00 bytes/sec
total size is 0 speedup is 0.00
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]
cd /path/to/sourcedir
tar -cf - . | (cd /path/to/targetdir ; tar -vxf - )
dd would also probably work.
We have a 4hr window to move 1tb, our initial tests show a copy is going to take around 11hrs. Even if tar reduced the time by 50% (doubtful) its still not enough. The only option seems to be a full copy, followed by a 2nd pass to synch the Delta we created during the live copy. We create about 10gb/day, and cleanup 2-3gb, something we can easily manage in our window
We have a 4hr window to move 1tb, our initial tests show a copy is going to take around 11hrs. Even if tar reduced the time by 50% (doubtful) its still not enough. The only option seems to be a full copy, followed by a 2nd pass to synch the Delta we created during the live copy. We create about 10gb/day, and cleanup 2-3gb, something we can easily manage in our window
Didn't really pick up on a time constraint from the OP. Thought it was more of a "what would work" question.
Is this on the same box? Why not extendvg with the new disk, then migratepv the data from the old disk to the new disk, and then reducevg the old disk out of the vg?
Didn't really pick up on a time constraint from the OP. Thought it was more of a "what would work" question.
Is this on the same box? Why not extendvg with the new disk, then migratepv the data from the old disk to the new disk, and then reducevg the old disk out of the vg?
Old volume is a HACMP volume (seen as a local disk when active), new is an isilon NAS. I don't think we could extend like that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
