I also have an overallocated /usr minidisk that I will be cloning soon. I was planning on using the procedure (using tar) in the moving part of a filesystem HOWTO (http://www.linuxvm.org/Info/HOWTOs/movefs.html). I successfully segregated several directories to their own minidisks so I figured I could use it for the initial copying of my maintenance server to what will be the production /usr minidisk.
/Thomas Kern /(301)903-2211 -----Original Message----- From: Gustavson, John (ECSS) [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 10:28 To: [EMAIL PROTECTED] Subject: How to shrink a VM mini disk file system prior to cloning? We installed the 2.4.7 kernel on 5 full pack mini disks as follows: /dev/dasda1 /dev/dasdb1 /dev/dasdc1 lvmsuse /dev/dasdd1 lvmsuse /dev/dasde1 lvmsuse Our parmfile is: dasd=0200,0100,0101,0102,0103 root=/dev/dasdb1 noinitrd so dasda1 is the swap file, and dasdb1 is the root, and dasdc1 starts our LVM, where we have /usr mounted. I know there are ways to shrink the LVM, but what would be the best way to shrink down our dasdb1 where our root is mounted? This device is a full pack mini disk(3390), and it is way over-allocated for what it is actually using. In OS/390 USS, for a similar problem, we did a pax on /, and unpaxed to a smaller file system. I don't see pax as part of our operating system, but maybe there is a better way to do this. Enterprise Central Software Services (ECSS) 570 Washington Street - 2nd floor New York, New York, 10080-6802 Telephone: 1-212-647-3793 Fax: 1-212-647-3321 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
