A few years ago, I modified dasdfmt to allow specification of the
start and end track for formatting. I was using LDL formatted volumes
do I didn't have to worry about the VTOC.
Usage: ./dasdfmt [-htvyLVFk]
[-l <volser> | --label=<volser>]
[-b <blocksize> | --blocksize=<blocksize>]
[-d <disk layout> | --disk_layout=<disk layout>]
[-s <track> | --start=<track>]
[-e <track> | --end=<track>]
<diskspec>
-t or --test means testmode
-c or --changeonly change disk layout only...no formatting
-V or --version means print version
-L or --no_label means don't write disk label
-w x or --wait=x means wait x seconds at 1 percent intervals
-s or --start means to start formatting at the specified track
-e or --end means to stop formatting at (and including) the
specified track
-p or --progressbar means show a progress bar
-m x or --hashmarks=x means show a hashmark every x cylinders
-v means verbose mode
-F means don't check if the device is in use
-k means keep volume serial
<volser> is the volume identifier, which is converted
to EBCDIC and written to disk.
(6 characters, e.g. LNX001
<blocksize> has to be power of 2 and at least 512
<disk layout> is either
'cdl' for compatible disk layout (default) or
'ldl' for linux disk layout
and <diskspec> is either
-f /dev/dasdX or --device=/dev/dasdX
if you do not use devfs
or
-f /dev/dasd/xxxx/device or --device=/dev/dasd/xxxx/device
and alternatively
-n xxxx or --devno=xxxx
in case you are using devfs.
xxxx is your hexadecimal device number.
Please report bugs to: linux...@de.ibm.com
On Mon, Jun 27, 2011 at 4:23 PM, Tom Huegel <tehue...@gmail.com> wrote:
> Maybe I left something out.
> Since this is CDL format there is a VTOC with an entry for the partition
> extent.
> I can use a free CMS program LXFMT to update that label without destroying
> any data.
> The gotcha is that I (LINUX) cannot use the additional DASD because it is
> not in a 4K format.
>
> Another solution I thought of would be to define the mdisk to VSE (I suppose
> z/OS would work too) then I could use JCL to create a file appending the
> current LINUX partition and write a program (any language) to open the file,
> write 4K records to the end. and close the file.
>
> Then go back to CMS for LXFMT to update the partition label.. and then
> to LINUX to expand the file system..
>
> Safer than me calculating where to DDR copy to, but still a mess...
>
> On Mon, Jun 27, 2011 at 1:57 PM, Jonathan Quay <jonathan.q...@ihg.com>
> wrote:
>>
>> I don't think you can do what you want to do because the linux partition
>> table won't see the extra cylinders. Nothing jumps off the page on the
>> s390tools site. I think you are stuck with defining a bigger minidisk and
>> copying the data over. LVM's are easy to extend and that is what I use for
>> almost all my filesystems.
>>
>> On Mon, Jun 27, 2011 at 4:44 PM, Thomas Kern <tlk_sysp...@yahoo.com>
>> wrote:
>>>
>>> CPFMTXA can do that cylinder range formatting, but I don't know if Linux
>>> will then allow you to do the resize2fs to enlarge the filesystem control
>>> blocks. It would be worth a try on a TEST MINIDISK.
>>>
>>> /Tom Kern
>>>
>>>
>>> On Mon, 27 Jun 2011 13:28:49 -0700, Tom Huegel <tehue...@gmail.com>
>>> wrote:
>>>
>>> >Tom,
>>> >Yea that would work too.
>>> >It just seems so simple to be able to format a cylinder range (either in
>>> >LINUX or CMS) ie FORMAT A10 4K cyl 100:199.. It would just write 4K
>>> > blocks
>>> >x'00's and be almost done with it. Then LINUX could expand the
>>> > filesystem
>>> >and away we go.
>>> >
>>> >At least it sounds simple.
>>> >
>>> >
>>> >
>>> >On Mon, Jun 27, 2011 at 1:11 PM, Thomas Kern <tlk_sysp...@yahoo.com>
>>> > wrote:
>>> >
>>> >> I always did it the old-fashioned way:
>>> >> 1) allocate a new 200 cyl minidisk
>>> >> 2) format it in linux
>>> >> 3) use linux tools to copy data from old to new
>>> >> 4) mount new instead of old
>>> >> 5) remove old from linux configuration
>>> >>
>>> >> /Tom Kern
>>> >>
>>> >>
>>> >> On Mon, 27 Jun 2011 10:35:46 -0700, Tom Huegel <tehue...@gmail.com>
>>> >> wrote:
>>> >>
>>> >> >I have a minidisk that LINUX uses. It is defined and formatted h use
>>> >> > CDL
>>> >> >format.
>>> >> >The MDISK is 100 cylinders but I want to expand it to 200 cylinders.
>>> >> >
>>> >> >How can I write the proper format on cylinders 99 to 199?
>>> >> >
>>> >> >The only way I found was to create another mdisk with 200 cylinders
>>> >> > and
>>> >> >format it, then DDR copy cyl 99 to 199 to my old disk.
>>> >> >There must be a better way.
>>> >> >
>>> >> >Does anyone know of a utility that will format specific cylinders on
>>> >> > a
>>> >> disk?
>>> >> >
>>> >> >Thanks
>>> >> >
>>> >>
>>> >
>>
>>
>>
>> --
>>
>> Jonathan Quay
>>
>> Systems Engineer - Enterprise Servers and Virtualization
>>
>> Global Technology
>>
>>
>> Direct Line: 770-442-7026
>> Fax: 770-442-7191
>>
>> http://www.ihg.com
>>
>>
>
>
