G'day Mark,
No, we don't have device nodes for /dev/dasd{ etc. How we noticed it was
that we had an LVM group made up of /dev/dasds1 and
/dev/dasdaa1,/dev/dasdab1
Unfortunately, this means that LVM is broken after the boot of 2.4.19. I
know I can create the dev entries, fix the LVM group to use the /dev/dasd{
etc but from what I read in the doco there shouldn't be a /dev/dasd{ in the
first place.
At the moment I'm guessing it's a bug but I haven't had the time to prove
it yet. I'm more than willing to accept 'user error' playing a big role
here.
Thanks
Geoff
"Post, Mark K"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
m> cc:
Sent by: Linux on Subject: Re: quick check on potential
2.4.19 problem
390 Port
<[EMAIL PROTECTED]
IST.EDU>
24/10/2002 01:16
am
Please respond to
Linux on 390 Port
Geoff,
I haven't seen that reported before. The characters displayed are next in
the collating sequence, so that seems OK. I guess the main question is,
when the system comes up, are the device nodes defined in /dev, and do they
work? If so, then I wouldn't worry about it much.
Mark Post
[snip]
Partition check:
dasda:VOL1/ 0X0101: dasda1
dasdb:VOL1/ 0X0201: dasdb1
dasdc:VOL1/ 0X0202: dasdc1
.
.
.
dasds:VOL1/ 0X0401: dasds1
dasd{:VOL1/ 0X0501: dasd{1
dasd|:VOL1/ 0X0502: dasd|1
dasd}:VOL1/ 0X0503: dasd}1
Note the '{' where it should be /dev/dasdaa1 etc etc.
Anyone else seen this?
Cheers
Geoff
