Don't worry about that change.  It won't have any impact on what you're
doing.

Doing the commands manually, there is only one difference:
ext2: mke2fs -b 4096
ext3: mke2fs -b 4096 -j


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hugo
Rivera
Sent: Wednesday, May 19, 2004 4:04 PM
To: [EMAIL PROTECTED]
Subject: Re: Adding a new DASD


Daniel thank you for your help.
Now I'm trying to format the partition /dev/dasdd1 using YaST2. I selected
EXT3 and when I click OK the partition type turns from S390 DASD to FLinux
Native (Ext3). How can I keep the type S390 DASD for my partition using
ext3. Is there some way to manually make an ext3 file???...I only see
examples for ext2. There is not a kind of mke2fs command for ext3. Thanks.



Hugo Rivera





                      Daniel Jarboe
                      <[EMAIL PROTECTED]        To:
[EMAIL PROTECTED]
                      stserv.com>              cc:
                      Sent by: Linux on        Subject:  Re: Adding a new
DASD
                      390 Port
                      <[EMAIL PROTECTED]
                      IST.EDU>


                      05/19/2004 12:06
                      PM
                      Please respond to
                      Linux on 390 Port






> -add the line : MDISK 0204 3390 0001 3338 VMLX05 MR ALL SOME FEW
>   into my Linux CMS user's USER DIRECT definition.
>
> - Format the device using cpfmtxa z/VM utility.
>
> - CMS format 204 c
>
> - IPL my Linux system.
>
> - check the devices:
>
> cat /proc/dasd/devices

Does it show up in /proc/subchannels?  If so, add it to the dasd device
driver with: "echo add range=204 > /proc/dasd/devices"

If not, the guest can't see it for some reason (did it get detached?)

>
> 0201(ECKD) at ( 94:  0) is dasda      : active at blocksize: 4096,
581040
> blocks
> , 2269 MB
> 0202(ECKD) at ( 94:  4) is dasdb      : active at blocksize: 4096,
600840
> blocks
> , 2347 MB
> 0203(none) at ( 94:  8) is dasdc      : unknown

After the add range to /proc/dasd/devices you should see a dasdd entry here.
Pick up where you left off with the dasdfmt, then fdasd, then make the
filesystem on /dev/dasdd1 (or whichever partition) and you should be golden.

Don't forget to add the address to your dasd= parameters in your zipl.conf,
cd /boot and run zipl so the dasd device is "automatically" enabled the next
time you ipl.


~ Daniel












-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use of
the addressee(s). No addressee should forward, print, copy, or otherwise
reproduce this message in any manner that would allow it to be viewed by any
individual not originally listed as a recipient. If the reader of this
message is not the intended recipient, you are hereby notified that any
unauthorized disclosure, dissemination, distribution, copying or the taking
of any action in reliance on the information herein is strictly prohibited.
If you have received this communication in error, please immediately notify
the sender and delete this message. Thank you.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to