Re: Extending DASD format?
Several have said ... create a new disk. That's your safest bet. To actually enlarge the existing filesystem, you still have want a new minidisk. Two things are then needed: 4K blocks on the new space (the extension), and a fixup of the CDL partition table. If both of those could be had, then a DDR would handle the copying. That's in CMS space. If doing it from Linux land, you would 'dd' old to new. In either case, you would then 'resize2fs' the filesys. I will, no doubt, annoy several, but I have to say it: This is why I recommend LDL (misnomer) and don't partition. If you have an LDL minidisk (only in the sense that it is *not* CDL), and you use the whole disk instead of the partition, then let VM enlarge it (with the aforementioned 4K blocking) and simply ... resize2fs done! The process then becomes exactly like enlarging the filesystem of an enlarged logical volume. Easy. -- R; On Mon, Jun 27, 2011 at 13:35, 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
Re: Extending DASD format?
On 6/28/11 9:45 AM, Richard Troth wrote: I will, no doubt, annoy several, but I have to say it: This is why I recommend LDL (misnomer) and don't partition. Agreed. The only CDL formatted volumes we use are for the root disk and we might even do away with those during our SLES11 upgrade. We've always used LDL disks for everything else. I just never saw the benefit. Leland
Re: Extending DASD format?
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 d isk? Thanks
Re: Extending DASD format?
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
Re: Extending DASD format?
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 bloc ks x'00's and be almost done with it. Then LINUX could expand the filesyste m and away we go. At least it sounds simple. On Mon, Jun 27, 2011 at 1:11 PM, Thomas Kern tlk_sysp...@yahoo.com wro te: 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 wr ote: 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 a nd 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
Re: Extending DASD format?
You could use ICKDSF to format e.g. a 101 cylinder work MDISK, then use DDR to copy that work Mdisk from *cyl 1 to 101 reorder to 100* onto the extended Linux MDISK. Notes: - We do not copy cylinder 0 of that work mdisk: cylinder 0 contains not all 4K records - Beware: destroying the target Linux MDISK is very easy: in your example you tell to format cyl 99 to 199. you would have destroyed the last cylinder of the old linux disk. - If you extend by more than 100 cylinders, the work mdisk doesn't need to be bigger, you can repeat the DDR and change the reorder every iteration. 2011/6/27 Tom Huegel tehue...@gmail.com 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.comwrote: 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 -- Kris Buelens, IBM Belgium, VM customer support
Re: Extending DASD format?
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 *
Re: Extending DASD format?
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.comwrote: 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.comwrote: 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 *
Re: Extending DASD format?
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//device or --device=/dev/dasd//device
and alternatively
-n or --devno=
in case you are using devfs.
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
Re: Extending DASD format?
Leland,
Is your updated version generally available?
Thanks
Tom
On Mon, Jun 27, 2011 at 2:35 PM, Leland Lucius lluc...@homerow.net wrote:
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//device or --device=/dev/dasd//device
and alternatively
-n or --devno=
in case you are using devfs.
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 -
Re: Extending DASD format?
On Mon, Jun 27, 2011 at 11:35 PM, Leland Lucius lluc...@homerow.net wrote: 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. A few more years ago, dasdfmt allowed the user to format only a range of cylinders. I believe that support was removed because they got too many support calls from customers who incorrectly only formatted part of the volume. ;-) IIRC that broke our process using flashcopy to format a new mini disk using another (very large) empty disk and run dasdfmt to initialize the part that depends on the size of the disk... | Rob
Re: Extending DASD format?
On 6/27/2011 at 05:23 PM, Tom Huegel tehue...@gmail.com wrote: 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... And costing you far more of your time and machine resources than simply copying the data. Don't do it. It's almost guaranteed to fail due to the many layers of things you're trying to circumvent. (ICKDSF, dasdfmt, fdasd, $DIETY knows what else I'm forgetting...) Mark Post
Re: Extending DASD format?
There is always more than one way to get to the otherside of a mountain... I like to explore them all. On Mon, Jun 27, 2011 at 7:24 PM, Mark Post mp...@novell.com wrote: On 6/27/2011 at 05:23 PM, Tom Huegel tehue...@gmail.com wrote: 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... And costing you far more of your time and machine resources than simply copying the data. Don't do it. It's almost guaranteed to fail due to the many layers of things you're trying to circumvent. (ICKDSF, dasdfmt, fdasd, $DIETY knows what else I'm forgetting...) Mark Post
Re: Extending DASD format?
Here's my old patch for it. This was against 1.5.1, but shouldn't be
too difficult to bring up to date. IOW, I longer use it...
Leland
On 6/27/11 5:17 PM, Tom Huegel wrote:
Leland,
Is your updated version generally available?
Thanks
Tom
On Mon, Jun 27, 2011 at 2:35 PM, Leland Lucius lluc...@homerow.net
mailto:lluc...@homerow.net wrote:
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//device or --device=/dev/dasd//device
and alternatively
-n or --devno=
in case you are using devfs.
is your hexadecimal device number.
Please report bugs to: linux...@de.ibm.com mailto:linux...@de.ibm.com
On Mon, Jun 27, 2011 at 4:23 PM, Tom Huegel tehue...@gmail.com
mailto: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 mailto: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 mailto: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 mailto: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 mailto: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
Re: Extending DASD format?
Thanks Leland I appreciate it.
On Mon, Jun 27, 2011 at 8:44 PM, Leland Lucius lluc...@homerow.net wrote:
Here's my old patch for it. This was against 1.5.1, but shouldn't be too
difficult to bring up to date. IOW, I longer use it...
Leland
On 6/27/11 5:17 PM, Tom Huegel wrote:
Leland,
Is your updated version generally available?
Thanks
Tom
On Mon, Jun 27, 2011 at 2:35 PM, Leland Lucius lluc...@homerow.net
mailto:lluc...@homerow.net wrote:
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//device or --device=/dev/dasd//device
and alternatively
-n or --devno=
in case you are using devfs.
is your hexadecimal device number.
Please report bugs to: linux...@de.ibm.com mailto:linux...@de.ibm.com
On Mon, Jun 27, 2011 at 4:23 PM, Tom Huegel tehue...@gmail.com
mailto: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 mailto: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 mailto: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 mailto: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 mailto:tlk_sysp...@yahoo.com**
wrote:
I
