On 10.08.2011 21:40, Patrick Spinler wrote:
Okay, please accept an 'I'm stupid' retraction, as Bob N. across the
wall got me. Running 'lsdasd' as root returns the full information
about the device in a nicely parsable format. (Curious it doesn't as
non-root, but there you go).
newer versions
Okay, so this just reached an annoyance point with me, so please forgive
me kvetching a bit. BTW -- this is specific to RHEL 5, s390utils 1.8,
so all you more modern folks or SuSE users can just laugh at me.
The contents of /proc/dasd/devices is very complete, but a PITA to
parse. You can't
modern folks or SuSE users can just laugh at me.
The contents of /proc/dasd/devices is very complete, but a PITA to
parse. You can't parse it based on character position, it has varying
length fields, and you can't parse it based on a simple fixed field
separator, either:
0.0.0391(ECKD
I'm pretty sure /proc/dasd/devices is deprecated too.. need to do some
fancy reading of things out of /sys now. I actually preferred
/proc/dasd/devices over lsdasd - because lsdasd output is different
depending on the distro/release.. /proc was the same no matter where you
were.. still use
Hi,
How can I change dinamically the /proc/dasd/devices to add a new
dasd without reboot my machine.
I tried the following command, but it didn't work
echo 0bb2(ECKD) at ( 94: 36) is dasdj : active at blocksize: 4096,
601020 blocks, 2347 MB /proc/dasd/devices
thanks in advanced
echo add device range=0bb2 /proc/dasd/devices
WBR, Sergey
Antônio Pires de Castro Jr. [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
03.11.2003 15:32
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject
Sergey Korzhevsky wrote:
echo add device range=0bb2 /proc/dasd/devices
WBR, Sergey
Anttnio Pires de Castro Jr. [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
03.11.2003 15:32
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc
Pires de Castro Jr. [SMTP:[EMAIL PROTECTED]
Sent: Monday, November 03, 2003 7:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Change dinamically the /proc/dasd/devices.
thanks for your reply, it works, but I can't format it:
[EMAIL PROTECTED] root]# more /proc/dasd/devices
...
0bb2(none
Try
echo set device range=0bb2 on /proc/dasd/devices
If it isn't help, that's mean that this device hasn't been attached to
your linux.
WBR, Sergey
Antônio Pires de Castro Jr. [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
03.11.2003 15:43
Please respond to Linux
tnio Pires de Castro Jr. [SMTP:[EMAIL PROTECTED]
Sent: Monday, November 03, 2003 7:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Change dinamically the /proc/dasd/devices.
thanks for your reply, it works, but I can't format it:
[EMAIL PROTECTED] root]# more /proc/dasd/devices
...
0bb2(none
Can anyone refresh my memory? What do I echo to /proc/dasd/devices to
get the kernel to find a new DASD pack? Thanks.
- Jason Herne ([EMAIL PROTECTED])
Can anyone refresh my memory? What do I echo to /proc/dasd/devices to
get the kernel to find a new DASD pack? Thanks.
Yes, just echo add range=xxx-yyy /proc/dasd/devices.
--
Guillaume Morin [EMAIL PROTECTED]
IBM Poughkeepsie
SAK Kernel Development
I can never remember either, that's why I like the script, dasd, that's in
the Large Scale Deployment redbook:
#!/bin/sh
# dasd - simple utility for dynamic DASD management
if [ $1 = add -a $2 != ]; then
echo add range=$2 /proc/dasd/devices
elif [ $1 = on -a $2
This is going to sound silly, but I use the following add dasd devices:
echo add device range= /proc/dasd/devices
but can't remember where I learned it.
Anyone point me to docs describing this process?
Thanks,Craig
.
-Original Message-
From: Kittendorf, Craig [SMTP:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 1:13 PM
To: [EMAIL PROTECTED]
Subject: Changing /proc/dasd/devices
This is going to sound silly, but I use the following add dasd devices:
echo add device range=
PROTECTED]
Subject: Re: Changing /proc/dasd/devices
Funny you should ask this; I was just in the book looking for the same
command.
Try Linux for S/390 - Device Drivers and Installation Commands. Mine says
14 September, Linux kernel 2.4 on the cover. (Well, it's a .pdf file, so
cover may
of
must-see-TV. And so on.
Scott Ledbetter
StorageTek
-Original Message-
From: Kittendorf, Craig [mailto:[EMAIL PROTECTED]
Sent: February 25, 2003 12:13 PM
To: [EMAIL PROTECTED]
Subject: Changing /proc/dasd/devices
This is going to sound silly, but I use the following add dasd devices
At 17:08 08-10-02, Rick Troth wrote:
And while we're at it, it would be helpful to have a userspace
program to do it and return a completion code (and maybe even do
the CP LINK as well).
I would disagree about the CP LINK part.
More significantly, this may be an ioctl() type of call.
And while we're at it, it would be helpful to have a userspace
program to do it and return a completion code (and maybe even do
the CP LINK as well).
I would disagree about the CP LINK part.
More significantly, this may be an ioctl() type of call.
Punching strings to /proc pseudo
-Ursprüngliche Nachricht-
Von: Rob van der Heij [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 24. September 2002 22:54
The designer of the code feels that this would disturb the mapping of
virtual address to minor number and make it unpredictable. I would
immediately agree that
At 22:18 25-09-02, Nix, Robert P. wrote:
Am I understanding correctly that you could not define a new single address, build
the dasd there, set it off, detach it and attach another new device at the same
address, and then set the address back on?
That way it works. One point is you have to
On Thu, 26 Sep 2002 11:32, you wrote:
'dead penguin'? How so? Can any of you define that term? Do you mean
Just a while ago, didn't we have someone reporting their install fell over
near the end? One dead penguin.
Stuffing up a kernel upgrade could result in one too.
--
Cheers
John
not
sure why, it just seems right to me. Perhaps a little bit of professional
paranoia.
Mark Post
-Original Message-
From: ZIEGENBEIN, Kurt [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 24, 2002 5:18 AM
To: [EMAIL PROTECTED]
Subject: /proc/dasd/devices
Hi!
I'm searching for a complete
I notice a few inconsistencies in the dynamic attach/detach
stuff through /proc/dasd/devices, and I'm wondering if this
is going to be changed or that it stays like this.
- there appears to be only a way to *add* devices to the
range of addresses the dasd driver likes. I think you want
Rob van der Heij
I notice a few inconsistencies in the dynamic attach/detach ...
Out of curiosity, which distribution are you working from?
Regards, Jim
Linux S/390-zSeries Support, SEEL, IBM Silicon Valley Labs
t/l 543-4021, 408-463-4021, [EMAIL PROTECTED]
** Grace Happens **
25 matches
Mail list logo
