[U2] UniVerse Resize 30
I had an interesting call from a customer this morning - he was resizing some files, making them Dynamic using the command RESIZE FILENAME 30 * * (normally you wouldn't enter the * * after 30) But then his session was comsuming all of the CPU for over 20 minutes (until I killed it). Just curious if anyone knows what the system was trying to do? We resized using the correct command format and everything is fine. The files in question were type 18, empty and very small modulo 11. Thanks, Mark Uv 10 Windows ** This email and any files transmitted with it are confidential and may be subject to copyright. They are intended solely for the use of the individual or entity to which they are addressed. If you have received this message in error please notify AFS immediately by return email. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of AFS, except where an authorized sender specifically states them to be the views of AFS. It is your responsibility to verify this email and any attachments for the presence of viruses. AFS accepts no liability for any damage caused by any virus transmitted. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniVerse Resize 30
What's even more twisted, is I tried the same scenario on my development box (Linux uv 10.2), and the RESIZE XXX 30 * * actually corrupted my test file LIST XXX XXX... Read operation failure. Internal file corruption detected. File must be repaired. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of LeRoy Dreyfuss Sent: Friday, October 11, 2013 9:55 AM To: U2 Users List Subject: Re: [U2] UniVerse Resize 30 What resize should have done was create the dynamic file, but preserve the current modulo of 11 and the group size. Perhaps it got itself in a twist because it was coming from a static-hashed structure and somehow couldn't work out the mod and sep like it should have. I am pretty sure this used to work back in 10.1.x- we had requests to make that work correctly. Cheers, LeRoy On Fri, Oct 11, 2013 at 8:50 AM, Mark Eastwood ma...@afsi.com wrote: I had an interesting call from a customer this morning - he was resizing some files, making them Dynamic using the command RESIZE FILENAME 30 * * (normally you wouldn't enter the * * after 30) But then his session was comsuming all of the CPU for over 20 minutes (until I killed it). Just curious if anyone knows what the system was trying to do? We resized using the correct command format and everything is fine. The files in question were type 18, empty and very small modulo 11. Thanks, Mark Uv 10 Windows ** This email and any files transmitted with it are confidential and may be subject to copyright. They are intended solely for the use of the individual or entity to which they are addressed. If you have received this message in error please notify AFS immediately by return email. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of AFS, except where an authorized sender specifically states them to be the views of AFS. It is your responsibility to verify this email and any attachments for the presence of viruses. AFS accepts no liability for any damage caused by any virus transmitted. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniVerse Resize 30
My testing on an empty type 18 file: :RESIZE DUMMY 30 * * :LIST DUMMY 0 records listed. :ANALYZE.FILE DUMMY File name .. DUMMY Pathname ... DUMMY File type .. DYNAMIC File style and revision 32BIT Revision 12 NLS Character Set Mapping .. ISO8859-1+MARKS Hashing Algorithm .. GENERAL No. of groups (modulus) 3 current ( minimum 3 ) Large record size .. 809 bytes Group size . 1024 bytes Load factors ... 80% (split), 50% (merge) and 0% (actual) Total size . 5120 bytes : It kept the mod and sep. Notice that the minimum and current modulo are the same and at 3. Note the group size is 1 K, which you cannot do when you create the file initially. I tried it again with a file that had data but otherwise the same. It worked fine there two. It shouldn't matter that we use NLS here. AIX 6.1/11.1.11 On Fri, Oct 11, 2013 at 1:02 PM, Mark Eastwood ma...@afsi.com wrote: What's even more twisted, is I tried the same scenario on my development box (Linux uv 10.2), and the RESIZE XXX 30 * * actually corrupted my test file LIST XXX XXX... Read operation failure. Internal file corruption detected. File must be repaired. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto: u2-users-boun...@listserver.u2ug.org] On Behalf Of LeRoy Dreyfuss Sent: Friday, October 11, 2013 9:55 AM To: U2 Users List Subject: Re: [U2] UniVerse Resize 30 What resize should have done was create the dynamic file, but preserve the current modulo of 11 and the group size. Perhaps it got itself in a twist because it was coming from a static-hashed structure and somehow couldn't work out the mod and sep like it should have. I am pretty sure this used to work back in 10.1.x- we had requests to make that work correctly. Cheers, LeRoy On Fri, Oct 11, 2013 at 8:50 AM, Mark Eastwood ma...@afsi.com wrote: I had an interesting call from a customer this morning - he was resizing some files, making them Dynamic using the command RESIZE FILENAME 30 * * (normally you wouldn't enter the * * after 30) But then his session was comsuming all of the CPU for over 20 minutes (until I killed it). Just curious if anyone knows what the system was trying to do? We resized using the correct command format and everything is fine. The files in question were type 18, empty and very small modulo 11. Thanks, Mark Uv 10 Windows ** This email and any files transmitted with it are confidential and may be subject to copyright. They are intended solely for the use of the individual or entity to which they are addressed. If you have received this message in error please notify AFS immediately by return email. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of AFS, except where an authorized sender specifically states them to be the views of AFS. It is your responsibility to verify this email and any attachments for the presence of viruses. AFS accepts no liability for any damage caused by any virus transmitted. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
