Re: Finding the lost symlink in SLES11.1
Thanks a lot, Steffen (and Mark and Rick). This solves a lot of doubts. Happy New Year for all in this list. _ Clovis From: Steffen Maier To: LINUX-390@vm.marist.edu Date: 28/12/2010 18:43 Subject: Re: Finding the lost symlink in SLES11.1 Sent by: Linux on 390 Port On 12/28/2010 08:22 PM, Richard Troth wrote: > There are changes between the kernel shipped with SLES 10 and that > shipped with SLE 11. If you have home-grown scripts (as many of us > do), you'll have to adjust them. Looks like the link you're after > changed from > > /sys/devices/dcssblk/PERFOUT/block:dcssblk0 > > to > > /sys/devices/dcssblk/PERFOUT/block/dcssblk0 > > (if I am reading the traffic correctly). The recent distro major releases (SLES11 SP1, RHEL 6) have their kernel built without CONFIG_SYSFS_DEPRECATED_V2 [1] which seems correct and has the consequences on sysfs layout that you encountered. This applies to all kinds of device classes, e.g. block or network [3]. Indeed the former symlink was replaced with two containing directories, the name of the outer depending on the device class. There are some rules for user space tooling working with sysfs to get it future-proof [2]. Maybe they are of help. [1] http://lxr.linux.no/#linux+v2.6.32/init/Kconfig#L608 [2] http://lxr.linux.no/#linux+v2.6.32/Documentation/sysfs-rules.txt [3] https://www.redhat.com/archives/anaconda-devel-list/2010-June/msg00095.html Steffen Linux on System z Development IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Finding the lost symlink in SLES11.1
On 12/28/2010 08:22 PM, Richard Troth wrote: There are changes between the kernel shipped with SLES 10 and that shipped with SLE 11. If you have home-grown scripts (as many of us do), you'll have to adjust them. Looks like the link you're after changed from /sys/devices/dcssblk/PERFOUT/block:dcssblk0 to /sys/devices/dcssblk/PERFOUT/block/dcssblk0 (if I am reading the traffic correctly). The recent distro major releases (SLES11 SP1, RHEL 6) have their kernel built without CONFIG_SYSFS_DEPRECATED_V2 [1] which seems correct and has the consequences on sysfs layout that you encountered. This applies to all kinds of device classes, e.g. block or network [3]. Indeed the former symlink was replaced with two containing directories, the name of the outer depending on the device class. There are some rules for user space tooling working with sysfs to get it future-proof [2]. Maybe they are of help. [1] http://lxr.linux.no/#linux+v2.6.32/init/Kconfig#L608 [2] http://lxr.linux.no/#linux+v2.6.32/Documentation/sysfs-rules.txt [3] https://www.redhat.com/archives/anaconda-devel-list/2010-June/msg00095.html Steffen Linux on System z Development IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Finding the lost symlink in SLES11.1
>>> On 12/28/2010 at 02:00 PM, Clovis Pereira wrote: > Hi, Mark. > See: > > # ls -l /sys/devices/dcssblk/PERFOUT/block > total 0 > drwxr-xr-x 6 root root 0 Dec 28 14:31 dcssblk0 > > # ls -l /sys/devices/dcssblk/PERFOUT/block/dcssblk0/ > total 0 > -r--r--r-- 1 root root 4096 Dec 28 15:34 alignment_offset > lrwxrwxrwx 1 root root0 Dec 28 15:34 bdi -> > ../../../../virtual/bdi/252:0 > -r--r--r-- 1 root root 4096 Dec 28 15:34 capability > -r--r--r-- 1 root root 4096 Dec 28 14:31 dev > lrwxrwxrwx 1 root root0 Dec 28 14:31 device -> ../../../PERFOUT > -r--r--r-- 1 root root 4096 Dec 28 15:34 ext_range > drwxr-xr-x 2 root root0 Dec 28 15:34 holders So, it looks like the same information is available (if not more information), just in a different layout. Whatever product was expecting the old layout needs to be updated to use the new one. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Finding the lost symlink in SLES11.1
Clovis -- Everything under /sys is managed by the kernel, not by UDEV. So you are correct, that sym-link was not created by UDEV. There are changes between the kernel shipped with SLES 10 and that shipped with SLE 11. If you have home-grown scripts (as many of us do), you'll have to adjust them. Looks like the link you're after changed from /sys/devices/dcssblk/PERFOUT/block:dcssblk0 to /sys/devices/dcssblk/PERFOUT/block/dcssblk0 (if I am reading the traffic correctly). Off hand, I forget the expected contents, and I don't have a DCSS handy or I could confirm this for you. -- R; <>< Rick Troth Velocity Software http://www.velocitysoftware.com/ On Tue, Dec 28, 2010 at 13:49, Clovis Pereira wrote: > > Hello, friends. > There are one symlink in SLES10 used to find the PERFOUT dcss, that is > missing in SLES11 SP1. > See on SLES10: > > # ls -l /sys/devices/dcssblk/PERFOUT/ > total 0 > lrwxrwxrwx 1 clovis root 0 Dec 28 16:18 block:dcssblk0 -> > ../../../block/dcssblk0 > -rw-r--r-- 1 clovis root 4096 Dec 28 16:18 save > -rw-r--r-- 1 clovis root 4096 Dec 28 16:18 shared > --w--- 1 clovis root 4096 Dec 28 16:18 uevent > > On SLES11 SP1, the reply didn't match: > > # ls -l /sys/devices/dcssblk/PERFOUT/ > total 0 > drwxr-xr-x 3 root root 0 Dec 28 14:31 block > drwxr-xr-x 2 root root 0 Dec 28 20:19 power > -rw--- 1 root root 4096 Dec 28 20:19 save > -r 1 root root 4096 Dec 28 20:19 seglist > -rw--- 1 root root 4096 Dec 28 20:19 shared > -rw-r--r-- 1 root root 4096 Dec 28 20:19 uevent > > The SYMLINK (block:dcssblk0) is missing. I think this wasn't created by > udev, > I test one new udev.rule without success (maybe wrong, I'm not the > expert): > > # cat /etc/udev/rules.d/98-dcss.rules > > # > # Rules for dcss - Clovis - Dec/2010 > # This file should be installed in /etc/udev/rules.d > # > SUBSYSTEM!="block", KERNEL!="dcssblk*", > ACTION!="add", > SYMLINK+="../../../block:%k%c" > > This rule runs, document the Symlink into udev DB but didn't create the > real SYMLINK. > Anyone know how to create the link or bypass it? > Thanks a lot for any help... > __ > Clovis > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Finding the lost symlink in SLES11.1
Hi, Mark. See: # ls -l /sys/devices/dcssblk/PERFOUT/block total 0 drwxr-xr-x 6 root root 0 Dec 28 14:31 dcssblk0 # ls -l /sys/devices/dcssblk/PERFOUT/block/dcssblk0/ total 0 -r--r--r-- 1 root root 4096 Dec 28 15:34 alignment_offset lrwxrwxrwx 1 root root0 Dec 28 15:34 bdi -> ../../../../virtual/bdi/252:0 -r--r--r-- 1 root root 4096 Dec 28 15:34 capability -r--r--r-- 1 root root 4096 Dec 28 14:31 dev lrwxrwxrwx 1 root root0 Dec 28 14:31 device -> ../../../PERFOUT -r--r--r-- 1 root root 4096 Dec 28 15:34 ext_range drwxr-xr-x 2 root root0 Dec 28 15:34 holders -r--r--r-- 1 root root 4096 Dec 28 15:34 inflight drwxr-xr-x 2 root root0 Dec 28 15:34 power drwxr-xr-x 2 root root0 Dec 28 15:34 queue -rw-r--r-- 1 root root 4096 Dec 28 14:31 range -r--r--r-- 1 root root 4096 Dec 28 14:31 removable -r--r--r-- 1 root root 4096 Dec 28 15:34 ro -r--r--r-- 1 root root 4096 Dec 28 15:34 size drwxr-xr-x 2 root root0 Dec 28 14:31 slaves -r--r--r-- 1 root root 4096 Dec 28 15:34 stat lrwxrwxrwx 1 root root0 Dec 28 14:31 subsystem -> ../../../../../class/block -rw-r--r-- 1 root root 4096 Dec 28 15:34 uevent __ Clovis From: Mark Post To: LINUX-390@vm.marist.edu Date: 28/12/2010 16:56 Subject: Re: Finding the lost symlink in SLES11.1 Sent by: Linux on 390 Port >>> On 12/28/2010 at 01:49 PM, Clovis Pereira wrote: > Hello, friends. > There are one symlink in SLES10 used to find the PERFOUT dcss, that is > missing in SLES11 SP1. > See on SLES10: > > # ls -l /sys/devices/dcssblk/PERFOUT/ > total 0 > lrwxrwxrwx 1 clovis root0 Dec 28 16:18 block:dcssblk0 -> > ../../../block/dcssblk0 > -rw-r--r-- 1 clovis root 4096 Dec 28 16:18 save > -rw-r--r-- 1 clovis root 4096 Dec 28 16:18 shared > --w--- 1 clovis root 4096 Dec 28 16:18 uevent > > On SLES11 SP1, the reply didn't match: > > # ls -l /sys/devices/dcssblk/PERFOUT/ > total 0 > drwxr-xr-x 3 root root0 Dec 28 14:31 block > drwxr-xr-x 2 root root0 Dec 28 20:19 power > -rw--- 1 root root 4096 Dec 28 20:19 save > -r 1 root root 4096 Dec 28 20:19 seglist > -rw--- 1 root root 4096 Dec 28 20:19 shared > -rw-r--r-- 1 root root 4096 Dec 28 20:19 uevent > > The SYMLINK (block:dcssblk0) is missing. I think this wasn't created by > udev, Or, there's more information in the (apparently new) /sys/devices/dcssblk/PERFOUT/block sub-directory. What's in there? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Finding the lost symlink in SLES11.1
>>> On 12/28/2010 at 01:49 PM, Clovis Pereira wrote: > Hello, friends. > There are one symlink in SLES10 used to find the PERFOUT dcss, that is > missing in SLES11 SP1. > See on SLES10: > > # ls -l /sys/devices/dcssblk/PERFOUT/ > total 0 > lrwxrwxrwx 1 clovis root0 Dec 28 16:18 block:dcssblk0 -> > ../../../block/dcssblk0 > -rw-r--r-- 1 clovis root 4096 Dec 28 16:18 save > -rw-r--r-- 1 clovis root 4096 Dec 28 16:18 shared > --w--- 1 clovis root 4096 Dec 28 16:18 uevent > > On SLES11 SP1, the reply didn't match: > > # ls -l /sys/devices/dcssblk/PERFOUT/ > total 0 > drwxr-xr-x 3 root root0 Dec 28 14:31 block > drwxr-xr-x 2 root root0 Dec 28 20:19 power > -rw--- 1 root root 4096 Dec 28 20:19 save > -r 1 root root 4096 Dec 28 20:19 seglist > -rw--- 1 root root 4096 Dec 28 20:19 shared > -rw-r--r-- 1 root root 4096 Dec 28 20:19 uevent > > The SYMLINK (block:dcssblk0) is missing. I think this wasn't created by > udev, Or, there's more information in the (apparently new) /sys/devices/dcssblk/PERFOUT/block sub-directory. What's in there? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Finding the lost symlink in SLES11.1
Hello, friends. There are one symlink in SLES10 used to find the PERFOUT dcss, that is missing in SLES11 SP1. See on SLES10: # ls -l /sys/devices/dcssblk/PERFOUT/ total 0 lrwxrwxrwx 1 clovis root0 Dec 28 16:18 block:dcssblk0 -> ../../../block/dcssblk0 -rw-r--r-- 1 clovis root 4096 Dec 28 16:18 save -rw-r--r-- 1 clovis root 4096 Dec 28 16:18 shared --w--- 1 clovis root 4096 Dec 28 16:18 uevent On SLES11 SP1, the reply didn't match: # ls -l /sys/devices/dcssblk/PERFOUT/ total 0 drwxr-xr-x 3 root root0 Dec 28 14:31 block drwxr-xr-x 2 root root0 Dec 28 20:19 power -rw--- 1 root root 4096 Dec 28 20:19 save -r 1 root root 4096 Dec 28 20:19 seglist -rw--- 1 root root 4096 Dec 28 20:19 shared -rw-r--r-- 1 root root 4096 Dec 28 20:19 uevent The SYMLINK (block:dcssblk0) is missing. I think this wasn't created by udev, I test one new udev.rule without success (maybe wrong, I'm not the expert): # cat /etc/udev/rules.d/98-dcss.rules # # Rules for dcss - Clovis - Dec/2010 # This file should be installed in /etc/udev/rules.d # SUBSYSTEM!="block", KERNEL!="dcssblk*", ACTION!="add", SYMLINK+="../../../block:%k%c" This rule runs, document the Symlink into udev DB but didn't create the real SYMLINK. Anyone know how to create the link or bypass it? Thanks a lot for any help... __ Clovis -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
