On Fri, 30 Nov 2007 10:55:18 -0500, Stracka, James (GTI) <[EMAIL PROTECTED]> wrote:
> EXACTLY! > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Dave Jones > Sent: Friday, November 30, 2007 10:50 AM > To: [email protected] > Subject: Re: Formatter for/Linux Minidisk from CMS > > I think the problem Jim is trying to avoid is the fact that Linux at > boot time will generate a ton of less than useful console messages if i t > > finds that some of it's dasd devices don't have at least some low level > format already in place....lots and lots of "CCW command rejects" and > i/o errors. If you have a number of Linux images all generating these > console messages at boot time, your automated VM console management can > become overwhelmed..... Ok, so to me, this raises the question of why so many unformatted volumes are being given to a (or many) Linux system(s)? When I do an install, I want it to be over with as quickly as possible. I give the guest as many disks as needed for the OS, script the install with AutoYaST, and once I have a usable system, go in and add/format whatever other disks are neede d. If I attach a new volume to a guest, I run dasdfmt on it and add it to t he appropriate LVM volume group. The next time I IPL the guest, no error me ssages. I've seen the messages everyone is talking about. There aren't _that_ ma ny that come out for a handful of volumes, so it's never caused any z/VM problems. Mark Wheeler's method is certainly a good one, if you have standard volume sizes you hand out to all your guests. I imagine not everyone is doing that, but for those that do, it can certainly save time and I/Os. Mark Post
