Interesting....it's CDL. So you're saying I could add it as DASDd, 'dasdfmt' it, take it down and use VM to do the copy from DASDc to DASDd, then run the 'resize2fs', take DASDc out of the picture and come back up like that? Like I said, that's interesting and I may want to try that on my sandbox but given that it's CDL and given that you said TAR was faster, I may go with that route. However, Mark Post is probably correct that I need to look at splitting some stuff out and I may just add another files system and start splitting things out.
-----Original Message----- From: Richard Troth [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 6:19 PM To: [EMAIL PROTECTED] Subject: Re: Adding dasd space You want to use 'resize2fs'. But you've got some footwork to do before you jump into that. Is the new disk pre-blocked? If it is blocked with 4K blocks (as CMS FORMAT will give you) then you can 'dd' the old disk to the new disk, and then 'resize2fs' to enlarge the filesystem found there. I was amazed to learn that TAR-to-TAR is faster than a 'dd' copy. If the new disk was formatted by CMS, then you would simply need to run a 'resize2fs' on it. But is this using LDL or CDL? If CDL, then you'll want to run 'dasdfmt' against the new volume, not use CMS FORMAT. Once it is formatted, even a CDL disk could be handled with 'dd' plus 'resize2fs'. But ... if you think about it, it makes sense, only a 100% full filesystem would really be copied any quicker with 'dd' than with 'tar'. TAR reads only what is in the files. With the right incantation of options, it will properly handle sparse files, in case you have any. I hope this helps. -- R;
