Hi Mark, Thanks for the background info (and you too John).
I know that I can format a "new" disk in the "new" format, but is there ANY way to just rewrite the 2.2 versioned label so that 2.4 doesn't complain about it? Formatting, allocating and copying many 3390-3 spindles will take hours - but the 2.2 versioned disks are perfectly usable except that they yield the "register_disk_label: invalid character(s) in label < x8040>" messages at boot time. As this is likely to come up as others migrate from 2.2 to 2.4, might be worth "fixing", maybe have 2.4's 'fdasd' check to see if the label is in 2.2 format and if '-l' was provided just go ahead and rewrite the label in 2.4 format instead of exiting with an error. -Mike -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Thursday, May 26, 2005 4:23 PM To: [email protected] Subject: Re: Change Linux DASD Label The 2.2 kernels don't support volume labels the same way as the (later) 2.4 kernels do. 2.2 also didn't support partitioning DASD, so you could only have dasda1, dasdb1, etc., and not dasda2, dasda3. You might be better of creating a new volume using the (default) CDL format, copying the data over, and reformatting the old one. The z/OS reference is correct, since the CDL format was created specifically to be compatible with MVS-OS/390-z/OS. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Coffin Michael C Sent: Thursday, May 26, 2005 3:34 PM To: [email protected] Subject: Re: Change Linux DASD Label Hi Betsie, Thanks. Looks like that's what I need - but now I have a "new problem". I'm trying to change the label of an ext2 disk that was formatted under SuSE 2.2.16, because when I use it on Debian 2.4.17 I see the following messages during boot: /dev/dasd/0154:<4> register_disk_label: invalid character(s) in label < x8040> register_label: refusing to create devfs entry. LNX1/ x8040: p1 Ultimately the disk mounts OK, but I figured there something in the label (or perhaps NO label) that Debian doesn't like, that why I thought I'd relabel it. However, when I use fdasd on Debian I get: fdasd /dev/dasd/0154/device fdasd error: Unsupported disk format /dev/dasd/0154/device is not formatted with z/OS compatible disk layout! Any ideas? I don't want to have to format ALL of the Debian DASD and then copy the contents of the SuSE DASD over. PS: Anyone have any idea why z/OS is even mentioned in this message? Is this yet another use of "z/OS" where "z/Series" should be? There is more than one z/Series OS out there ...... :) Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6527 1111 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-6726 [EMAIL PROTECTED] ---------------------------------------------------------------------- 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
