org/g/wg-linux-distros/message/59
[3]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/s390/char/vmur.c?id=bf18140d30541c2c1e5c0f57879634f3d0d04912
[4]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/s390/char/vmur.c?id=f3e59ff348
On 04.07.2022 06:13, Jake Anderson wrote:
> Is it possible to know the LUN ID where a specific filesystem is residing?
You can use 'lszdev --by-path ' to display information about the
device that provides a specific filesystem path.
Regards,
Peter
--
Peter Oberparleiter
Linux on IB
On 08.10.2021 18:08, Aria Bamdad wrote:
> Quoting Peter Oberparleiter :
>
> Peter, thank you for your excellent analysis and clarification of how
> this works. It now makes perfect sense to me.
I'm glad that you found the information I provided to be helpful.
[...]
> I tested th
chzdev was specifically added to
support correct handling of multi-disk btrfs file systems. Also given
that a file system UUID is supposed to uniquely identify a file system,
I don't consider the current behavior a problem in chzdev.
Regards,
Peter
--
Peter Oberparleiter
Linux on Z Development - IBM Germa
The Integrated ASCII console HMC task does not provide a scroll-back
> function.
I need to correct my statement here - the Integrated ASCII console HMC
task does indeed provide a scrolling capability that can be accessed by
using the Shift+PageUp/PageDown keys.
Thanks to Alan Altmark and the HMC t
bm.com/docs/pl/linux-on-systems?topic=shutdown-snipl-control-virtual-hardware
or zhmcclient
https://github.com/zhmcclient/zhmccli
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on Z Development - IBM Germany
---
On 03.03.2021 16:36, Alan Altmark wrote:
> On Wednesday, 03/03/2021 at 02:25 GMT, Peter Oberparleiter
> wrote:
>> 3. Use the ASCII Console as Linux console
>>
>> - add "console=ttyS1" to kernel parameters in /etc/zipl.conf
>> (mind the upper-case S)
>
II Console
$ systemctl start serial-getty@ttysclp0.service
When this command completes, there should be a login prompt shown on the
ASCII Console.
You can also check the status of this systemctl unit using:
$ systemctl status serial-getty@ttysclp0
effect in the z/VM guest
where the device in subchannel set 1 is missing.
Something like the following should do the trick:
$ chzdev -ep dasd-eckd 0.1.0f57
--
Peter Oberparleiter
Linux on Z Development - IBM Germany
--
For LINUX
solve the problem, could you share the installation
parmfile contents (minus the sensitive data).
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on Z Development - IBM Germany
--
For LINUX-390 subscribe / signoff / archi
You need to perform these steps TWICE, or fdasd will terminate with a
"BUG..." statement when you try to create/change partitions afterwards.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on Z Development - IBM Germany
gt; looked at the version that will be going into SLES12 SP2 to know if
> it's worth using or not.
Please note that the zdev tools (chzdev, lszdev) included in s390-tools
1.33 are the result of a full rework. I'm confident that all major
issues of earlier versions have been resolved by this new ver
and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on z Systems
) and therefore incorrectly assumes
that the hardware is missing. I've added a fix to our code repository.
It will be included in the next release. Thanks for pointing out this issue!
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
will be made available with
the next release. Again thanks for pointing this out!
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
--
For LINUX-390 subscribe / signoff / archive
access) and with
lower CPU overhead than traditional NFS or FTP transfer methods.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
--
For LINUX-390 subscribe / signoff / archive
takes about 19 minutes to fill it up with zeros by cat /dev/zero to
it.
Why does dasdfmt take so long?
This is a known problem which is currently being investigated.
Regards,
Peter Oberparleiter
Any progress in this area?
Yes: Improvements have been made to both
that CHPID.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu
DASDs (/dev/dasdx1 instead of /dev/dasdx). By not using a partition, the
filesystem on the DASD will get corrupted, which can also result in it
being re-mounted read-only.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
=autodetect should achieve
the same result.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists
dasdfmt take so long?
This is a known problem which is currently being investigated.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
--
For LINUX-390 subscribe / signoff / archive
it be that you are using LVM which adds its own block devices
which are not affected by DASD's elevator defaults?
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
--
For LINUX-390 subscribe
NAME MAJ:MIN RM SIZE RO MOUNTPOINT
sda8:0010G 0
└─sda1 8:1010G 0 /
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
--
For LINUX-390 subscribe
on the bare disk (no LVM) and see if that works.
Regards,
Peter Oberparleiter
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http
:
- Attach + set online
- Check if the partition is recognized
- Dump VTOC data:
dasdview -t all /dev/dasd... sles11.txt
- Compare the VTOC data:
diff -u sles10.txt sles11.txt
If there is a difference, please send the output of the diff command.
Regards,
Peter Oberparleiter
for this is that
lsdasd requires read access for the device nodes (e.g. /dev/dasda) to
obtain this information and this type of access is usually restricted to
certain users/groups.
Regards,
Peter Oberparleiter
--
For LINUX
by the memory map that Linux creates at boot time. Try
increasing the ramdisk load address in your zipl.conf file (see chapter
37 in * for instructions).
Regards,
Peter Oberparleiter
[*] http://public.dhe.ibm.com/software/dw/linux390/docu/lk37dd09.pdf
the PA1 key will generate Control-C,
PA2 Control-D and PA3 Control-Z. Have you tried using these keys instead
of the ^C sequence?
Regards,
Peter Oberparleiter
--
For LINUX-390 subscribe / signoff / archive access instructions
they decided to keep it similar to the Intel world.
Regards,
Peter Oberparleiter
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http
show up, make sure they are correctly attached to your z/VM guest/LPAR.
For 3 see if a directory named 0.0.0400 exists in
/sys/bus/ccwgroup/devices. If so, set it offline and ungroup it.
Regards,
Peter Oberparleiter
--
For LINUX
required ccw devices available to Linux?
(post the output of lscss).
Regards,
Peter Oberparleiter
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO
of a number. Is this a bug (or a feature ;) )?
Feature, it seems. See
https://bugzilla.novell.com/show_bug.cgi?id=146656 (requires a Novell
user ID to access).
Regards,
Peter Oberparleiter
--
For LINUX-390 subscribe
response. There are two reasons why the kernel function wouldn't finish
by itself: hardware error or kernel programming error.
Are there any messages in the output of 'dmesg' that indicate that
device 21b7 may have a problem? What is the output of 'lscss -d 0.0.21b7
--avail'?
Regards,
Peter
is tracked in Novell Bugzilla
494301 (https://bugzilla.novell.com/show_bug.cgi?id=494301).
Unfortunately the entry does not mention a fix.
Regards,
Peter Oberparleiter
--
For LINUX-390 subscribe / signoff / archive access
. Now it will only
fail when it encounters an IFCC on the path that worked before :)
Note that there is more work currently being done in zipl and Linux to
improve I/O error recovery during the boot phase.
Regards,
Peter Oberparleiter
to support writing IPL records to multipath devices.
Consequently zipl should abort with the same message as in SLES10. I'll
have a look into this.
As for the actual multipath/logical volume support for zipl: that code
has not yet been released as it is currently in testing stage.
Regards,
Peter
prompt input with
'#cp vinput vmsg' (see man zipl.conf)?
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX-390 subscribe / signoff / archive access
vi vmsg 0
?
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL
250 access to dasd devices for 64 bit kernels.
(http://www.ussg.iu.edu/hypermail/linux/kernel/0508.3/1218.html)
SLES9 (including latest service packs) does not include this Linux support
though.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development
)
system to dump 31 bit (s390) systems. The other way around is not possible
though, i.e. trying to dump a 64 bit system on a dasd on which the dump
record from a 31 bit system is installed will produce unreadable dumps.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries
SUSE and Red Hat iso images mounted using 52 loop devices.
Wow, I totally missed this option. Thanks for pointing this out!
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
-screen
mode
terminal.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL
,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED
of authorized keys for user on remote
cat .ssh/id_dsa.pub | ssh [EMAIL PROTECTED] ( mkdir -p .ssh ; cat
.ssh/authorized_keys )`
3. Log in/execute commands without password prompt
ssh [EMAIL PROTECTED] ls
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
which
could cause such behavior (see
http://www10.software.ibm.com/developerworks/opensource/linux390/linux-2.4.21-s390-07-june2003.shtml).
Depending on the kernel level you are using this may be the source of your
problem.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries
to find out why a process is generating so much data
(check error logs, etc.).
Hope this helps.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX
of the other services running on your system.
That's all the advice I can think of at the moment.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
). It should work if you retry the test using the following
command line:
ro foo=bar init=/bin/bash
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX
by setting 'prompt' to zero or by installing only a single con-
figuration. The menu can then be temporarily activated by passing the
string 'prompt' via the loadparm function:
#cp ipl 0192 loadparm prompt
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries
an unknown keyword, and won't run.
So, any advice as to how to get this to work with 1.2.4?
Unfortunately not. Boot menu support was only added in s390-tools version
1.3.0.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
in the future).
Anyway, I hope that with the new version, the feature works as expected
for you.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX-390
of A) on C.
As a downside, the HTTPD logs would show C as the source for requests
which
are forwarded by C. Maybe have a look at the book that Adam Thornton
suggested if you want a more sophisticated solution.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM
that matched - this way you can try to
understand what is happening within netfilter:
iptables -L -v
iptables -t nat -L -v
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
what
will happen if keywords on the kernel command line provide conflicting
information.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX-390
of the internal bootmap file.
I think the most reasonable solution for scenarios where configuration
management tools are used would be to impose a policy, only to use
configurations supplied in the zipl.conf file.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries
back to the
working configuration if anything bad happens.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX-390 subscribe / signoff
access this file, there's
no way to change the file format without causing chaos with users of
that tool.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
that was -t 0 (the default). -t 2 was the opposite,
i.e. something like '--now-for-real'.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX
this helps.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on zSeries Development
IBM Development Lab, Boeblingen/Germany
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED
:
mknod /dev/console c 5 1
Regards,
Peter Oberparleiter
--
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
or to append additional parameters to
the kernel command line at boot time (see respective zipl man pages).
Regards,
Peter Oberparleiter
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL
Adam Thornton wrote:
Which version of zipl is required in order to get the -s parameter?
Support for segment load through zipl's -s parameter was first included
in s390-tools version 1.2.0. Online documentation was added in version
1.2.4 (current).
Regards,
Peter Oberparleiter
the init scripts as this will prevent the kernel from
signalling completion of 'signal shutdown' processing
3) do not specify 'vmpoff' or 'vmhalt' commands as these will be ignored
Hope this helps.
Regards,
Peter Oberparleiter
. Thanks for pointing it out!
Regards,
Peter Oberparleiter
64 matches
Mail list logo