Re: lun multipathing / file system
On 3/17/2011 at 12:49 PM, Rogério Soaresrogerio.soa...@gmail.com wrote: People, Apparently, i have the same problem describe in this old thread ( http://www.opensubscriber.com/message/linux-390@vm.marist.edu/12394163.html ) i have try setting up lvm.conf like suggest to use filter like : filter = [ a|/dev/mapper/*|,r|/dev/sd*|,r|/dev/.*/by-path/.*|, r|/dev/.*/by-id/.*|, a/.*/ ] but, this way, lvm mount points not come back automaticaly... i need do vgscan, vgchange e mont -a to remount it... change filter to default, mount points are all remounts automaticaly on boot.. filter = [r|/dev/.*/by-path/.*|, r|/dev/.*/by-id/.*|, a/.*/ ] any help? :-/ Try running vgscan -vvv. The output will tell you which devices are being ignored by the filter: Skipping (regex) That can help you figure out what changes might be needed to your filter. 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: lun multipathing / file system
Mark, sorry for long post, but, i modify the filter to: filter = [ r|/dev/.*/by-path/.*|, r|/dev/.*/by-id/.*|, a|/dev/mapper/*|, a/.*/ ] this way, all file systems are remount ok after boot.. but i confess, i can't understand the output from vgscan -vvv , appears all the same to be... dtsh101:~ # vgscan -vvv Processing: vgscan -vvv O_DIRECT will be used Setting global/locking_type to 1 File-based locking selected. Setting global/locking_dir to /var/lock/lvm Wiping cache of LVM-capable devices /dev/blog: Not a block device /dev/console: Not a block device /dev/core: Not a block device /dev/dasda: Already in device cache /dev/dasda1: Already in device cache /dev/dasdb: Already in device cache /dev/dasdb1: Already in device cache /dev/dasd_eer: Not a block device /dev/device-mapper: Not a block device /dev/disk/by-id/ccw-0X0100: Already in device cache /dev/disk/by-id/ccw-0X0100-part1: Already in device cache /dev/disk/by-id/ccw-IBM.82000VW001.000d.1a: Already in device cache /dev/disk/by-id/ccw-IBM.82000VW001.000d.1a.00012720: Already in device cache /dev/disk/by-id/ccw-IBM.82000VW001.000d.1a.00012720-part1: Already in device cache /dev/disk/by-id/ccw-IBM.82000VW001.000d.1a-part1: Already in device cache /dev/disk/by-id/scsi-3600507630affc485706c: Already in device cache /dev/disk/by-id/scsi-3600507630affc4857164: Already in device cache /dev/disk/by-id/scsi-mpatha: Already in device cache /dev/disk/by-id/scsi-mpathb: Already in device cache /dev/disk/by-name/mpatha: Already in device cache /dev/disk/by-name/mpathb: Already in device cache /dev/disk/by-path/ccw-0.0.0100: Already in device cache /dev/disk/by-path/ccw-0.0.0100-part1: Already in device cache /dev/disk/by-path/ccw-0.0.0501: Already in device cache /dev/disk/by-path/ccw-0.0.0501-part1: Already in device cache /dev/disk/by-path/ccw-0.0.0b23-zfcp-0x500507630a3b0485:0x4070406c: Already in device cache /dev/disk/by-path/ccw-0.0.0b23-zfcp-0x500507630a3b0485:0x40714064: Already in device cache /dev/disk/by-path/ccw-0.0.0f23-zfcp-0x500507630a200485:0x4070406c: Already in device cache /dev/disk/by-path/ccw-0.0.0f23-zfcp-0x500507630a200485:0x40714064: Already in device cache /dev/disk/by-uuid/09b790c5-9948-4561-bd3c-c01e07726e8c: Already in device cache /dev/disk/by-uuid/2118c2c8-f7be-4772-a43b-3a8da7209eae: Already in device cache /dev/disk/by-uuid/21d68996-05ad-4b67-ba8b-e11035327afe: Already in device cache /dev/disk/by-uuid/86383af5-6264-49a3-84a3-7a17880c3fea: Already in device cache /dev/dm-0: Already in device cache /dev/dm-1: Already in device cache /dev/dm-2: Already in device cache /dev/dm-3: Already in device cache /dev/dm-4: Already in device cache /dev/fd: Symbolic link to directory /dev/full: Not a block device /dev/fwmonitor: Not a block device /dev/i2c-0: Not a block device /dev/initctl: Not a block device /dev/kmem: Not a block device /dev/kmsg: Not a block device /dev/log: Not a block device /dev/loop0: Added to device cache /dev/loop1: Added to device cache /dev/loop2: Added to device cache /dev/loop3: Added to device cache /dev/loop4: Added to device cache /dev/loop5: Added to device cache /dev/loop6: Added to device cache /dev/loop7: Added to device cache /dev/mapper/control: Not a block device /dev/mapper/mpatha: Already in device cache /dev/mapper/mpathb: Already in device cache /dev/mapper/vg_dts_data-lv_dts_data_geral: Already in device cache /dev/mapper/vg_dts_data-lv_dts_data_temp: Already in device cache /dev/mapper/vg_dts-lv_dts: Already in device cache /dev/md0: Added to device cache /dev/md1: Added to device cache /dev/md10: Added to device cache /dev/md11: Added to device cache /dev/md12: Added to device cache /dev/md13: Added to device cache /dev/md14: Added to device cache /dev/md15: Added to device cache /dev/md16: Added to device cache /dev/md17: Added to device cache /dev/md18: Added to device cache /dev/md19: Added to device cache /dev/md2: Added to device cache /dev/md20: Added to device cache /dev/md21: Added to device cache /dev/md22: Added to device cache /dev/md23: Added to device cache /dev/md24: Added to device cache /dev/md25: Added to device cache /dev/md26: Added to device cache /dev/md27: Added to device cache /dev/md28: Added to
Re: lun multipathing / file system
On 3/17/2011 at 01:43 PM, Rogério Soaresrogerio.soa...@gmail.com wrote: Mark, sorry for long post, but, i modify the filter to: filter = [ r|/dev/.*/by-path/.*|, r|/dev/.*/by-id/.*|, a|/dev/mapper/*|, a/.*/ ] this way, all file systems are remount ok after boot.. but i confess, i can't understand the output from vgscan -vvv , appears all the same to be... I was thinking more that you would run this when using the filter that you say _doesn't_ work right. 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: lun multipathing / file system
here is output with de filter suggest by Deric.. dtsh101:~ # vgscan -vvv Processing: vgscan -vvv O_DIRECT will be used Setting global/locking_type to 1 File-based locking selected. Setting global/locking_dir to /var/lock/lvm Wiping cache of LVM-capable devices /dev/blog: Not a block device /dev/console: Not a block device /dev/core: Not a block device /dev/dasda: Already in device cache /dev/dasda1: Already in device cache /dev/dasdb: Already in device cache /dev/dasdb1: Already in device cache /dev/dasd_eer: Not a block device /dev/device-mapper: Not a block device /dev/disk/by-id/ccw-0X0100: Already in device cache /dev/disk/by-id/ccw-0X0100-part1: Already in device cache /dev/disk/by-id/ccw-IBM.82000VW001.000d.1a: Already in device cache /dev/disk/by-id/ccw-IBM.82000VW001.000d.1a.00012720: Already in device cache /dev/disk/by-id/ccw-IBM.82000VW001.000d.1a.00012720-part1: Already in device cache /dev/disk/by-id/ccw-IBM.82000VW001.000d.1a-part1: Already in device cache /dev/disk/by-id/scsi-3600507630affc485706c: Added to device cache /dev/disk/by-id/scsi-3600507630affc4857164: Added to device cache /dev/disk/by-id/scsi-mpatha: Added to device cache /dev/disk/by-id/scsi-mpathb: Added to device cache /dev/disk/by-name/mpatha: Aliased to /dev/disk/by-id/scsi-mpatha in device cache /dev/disk/by-name/mpathb: Aliased to /dev/disk/by-id/scsi-mpathb in device cache /dev/disk/by-path/ccw-0.0.0100: Already in device cache /dev/disk/by-path/ccw-0.0.0100-part1: Already in device cache /dev/disk/by-path/ccw-0.0.0501: Already in device cache /dev/disk/by-path/ccw-0.0.0501-part1: Already in device cache /dev/disk/by-path/ccw-0.0.0b23-zfcp-0x500507630a3b0485:0x4070406c: Aliased to /dev/disk/by-id/scsi-3600507630affc485706c in device cache /dev/disk/by-path/ccw-0.0.0b23-zfcp-0x500507630a3b0485:0x40714064: Aliased to /dev/disk/by-id/scsi-3600507630affc4857164 in device cache /dev/disk/by-path/ccw-0.0.0f23-zfcp-0x500507630a200485:0x4070406c: Added to device cache /dev/disk/by-path/ccw-0.0.0f23-zfcp-0x500507630a200485:0x40714064: Added to device cache /dev/disk/by-uuid/86383af5-6264-49a3-84a3-7a17880c3fea: Already in device cache /dev/dm-0: Aliased to /dev/disk/by-id/scsi-mpatha in device cache (preferred name) /dev/dm-1: Aliased to /dev/disk/by-id/scsi-mpathb in device cache (preferred name) /dev/fd: Symbolic link to directory /dev/full: Not a block device /dev/fwmonitor: Not a block device /dev/i2c-0: Not a block device /dev/initctl: Not a block device /dev/kmem: Not a block device /dev/kmsg: Not a block device /dev/log: Not a block device /dev/loop0: Added to device cache /dev/loop1: Added to device cache /dev/loop2: Added to device cache /dev/loop3: Added to device cache /dev/loop4: Added to device cache /dev/loop5: Added to device cache /dev/loop6: Added to device cache /dev/loop7: Added to device cache /dev/mapper/control: Not a block device /dev/mapper/mpatha: Aliased to /dev/dm-0 in device cache /dev/mapper/mpathb: Aliased to /dev/dm-1 in device cache /dev/md0: Added to device cache /dev/md1: Added to device cache /dev/md10: Added to device cache /dev/md11: Added to device cache /dev/md12: Added to device cache /dev/md13: Added to device cache /dev/md14: Added to device cache /dev/md15: Added to device cache /dev/md16: Added to device cache /dev/md17: Added to device cache /dev/md18: Added to device cache /dev/md19: Added to device cache /dev/md2: Added to device cache /dev/md20: Added to device cache /dev/md21: Added to device cache /dev/md22: Added to device cache /dev/md23: Added to device cache /dev/md24: Added to device cache /dev/md25: Added to device cache /dev/md26: Added to device cache /dev/md27: Added to device cache /dev/md28: Added to device cache /dev/md29: Added to device cache /dev/md3: Added to device cache /dev/md30: Added to device cache /dev/md31: Added to device cache /dev/md4: Added to device cache /dev/md5: Added to device cache /dev/md6: Added to device cache /dev/md7: Added to device cache /dev/md8: Added to device cache /dev/md9: Added to device cache /dev/mem: Not a block device /dev/net/tun: Not a block device /dev/null: Not a block device /dev/port: Not a
Re: lun multipathing / file system
On 3/17/2011 at 02:09 PM, Rogério Soaresrogerio.soa...@gmail.com wrote: here is output with de filter suggest by Deric.. From the looks of this, you didn't modify the scan parameter in /etc/lvm/lvm.conf as he did. Personally, I don't think what he did was strictly necessary, although it clearly works for him. If you look at http://www.novell.com/documentation/sles10/stor_admin/?page=/documentation/sles10/stor_admin/data/be5rvii.html what we recommend is changing the filter command to this: filter = [ a|/dev/disk/by-id/.*|, r|.*| ] If you're also using LVM to manage non-multipathed devices, then you'll need to add those back in to the filter. For example, if you're using this setup: FilesystemSize Used Avail Use% Mounted on /dev/dasda1 388M 96M 273M 26% / devtmpfs 248M 112K 247M 1% /dev tmpfs 248M 0 248M 0% /dev/shm /dev/mapper/vg1-home 97M 4.1M 88M 5% /home /dev/mapper/vg1-opt74M 4.1M 66M 6% /opt /dev/mapper/vg1-tmp 291M 48M 229M 18% /tmp /dev/mapper/vg1-usr 1.3G 1.1G 69M 95% /usr /dev/mapper/vg1-var 295M 82M 198M 30% /var # pvs PV VG Fmt Attr PSize PFree /dev/dasda3 vg1 lvm2 a- 5.98G0 Then your filter would also need to include a scan of /dev/dasd*: filter = [ a|/dev/disk/by-id/.*|, a|/dev/dasd.*/.*|, r|.*| ] types = [ device-mapper, 253 ] Since your case seems to only be using LVM for the SCSI devices, then the first filter I show should be enough: filter = [ a|/dev/disk/by-id/.*|, r|.*| ] 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: lun multipathing / file system
Mark, i set up the filter recommend, add dm-multipath on /etc/sysconfig/kernel INITRD_MODULES section.. made mkinitrd -f mpath and reboote... but now my server dead :) we are using / on dasd disk any tips? thanks again sdc: Write Protect is off SCSI device sdc: drive cache: write back SCSI device sdc: 83886080 512-byte hdwr sectors (42950 MB) sdc: Write Protect is off SCSI device sdc: drive cache: write back sdc: unknown partition table sd 1:0:0:1080836208: Attached scsi disk sdc No configuration file for adapter 0.0.0f23 Configuring FCP disk 500507630a200485:40714064 Vendor: IBM Model: 2107900 Rev: 5.78 Type: Direct-Access ANSI SCSI revision: 05 1:0:0:1080311921: alua: supports implicit TPGS Waiting for /dev/mapper/control to appear: ok 1:0:0:1080311921: alua: port group 00 rel port 400 1:0:0:1080311921: alua: rtpg failed with 802 1:0:0:1080311921: alua: port group 00 state A supports tousnA SCSI device sdd: 83886080 512-byte hdwr sectors (42950 MB) sdd: Write Protect is off SCSI device sdd: drive cache: write back SCSI device sdd: 83886080 512-byte hdwr sectors (42950 MB) sdd: Write Protect is off SCSI device sdd: drive cache: write back sdd: unknown partition table sd 1:0:0:1080311921: Attached scsi disk sdd sd 0:0:0:1080836208: Attached scsi generic sg0 type 0 sd 0:0:0:1080311921: Attached scsi generic sg1 type 0 sd 1:0:0:1080836208: Attached scsi generic sg2 type 0 sd 1:0:0:1080311921: Attached scsi generic sg3 type 0 Loading jbd Loading ext3 Setup multipath devices: ok. Waiting for device /dev/disk/by-path/ccw-0.0.0100-part1 to appear: !.!.!.!.!.!.! .!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.not found -- exiting to /bin/sh $ $ On Thu, Mar 17, 2011 at 3:41 PM, Mark Post mp...@novell.com wrote: On 3/17/2011 at 02:09 PM, Rogério Soaresrogerio.soa...@gmail.com wrote: here is output with de filter suggest by Deric.. From the looks of this, you didn't modify the scan parameter in /etc/lvm/lvm.conf as he did. Personally, I don't think what he did was strictly necessary, although it clearly works for him. If you look at http://www.novell.com/documentation/sles10/stor_admin/?page=/documentation/sles10/stor_admin/data/be5rvii.htmlwhat we recommend is changing the filter command to this: filter = [ a|/dev/disk/by-id/.*|, r|.*| ] If you're also using LVM to manage non-multipathed devices, then you'll need to add those back in to the filter. For example, if you're using this setup: FilesystemSize Used Avail Use% Mounted on /dev/dasda1 388M 96M 273M 26% / devtmpfs 248M 112K 247M 1% /dev tmpfs 248M 0 248M 0% /dev/shm /dev/mapper/vg1-home 97M 4.1M 88M 5% /home /dev/mapper/vg1-opt74M 4.1M 66M 6% /opt /dev/mapper/vg1-tmp 291M 48M 229M 18% /tmp /dev/mapper/vg1-usr 1.3G 1.1G 69M 95% /usr /dev/mapper/vg1-var 295M 82M 198M 30% /var # pvs PV VG Fmt Attr PSize PFree /dev/dasda3 vg1 lvm2 a- 5.98G0 Then your filter would also need to include a scan of /dev/dasd*: filter = [ a|/dev/disk/by-id/.*|, a|/dev/dasd.*/.*|, r|.*| ] types = [ device-mapper, 253 ] Since your case seems to only be using LVM for the SCSI devices, then the first filter I show should be enough: filter = [ a|/dev/disk/by-id/.*|, r|.*| ] 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: lun multipathing / file system
On 3/17/2011 at 03:33 PM, Rogério Soaresrogerio.soa...@gmail.com wrote: Mark, i set up the filter recommend, add dm-multipath on /etc/sysconfig/kernel INITRD_MODULES section.. made mkinitrd -f mpath and reboote... but now my server dead :) we are using / on dasd disk any tips? Yeah, remove dm-multipath from the initrd and don't use -f mpath on the mkinitrd command. Unless your root file system is on a mulipathed device, you don't need it, and it will cause problems such as this. You also do _not_ need boot.multipath enabled. 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: lun multipathing / file system
Mark, just to learn something new today, except how to kill a server hehehe, i can recover this without reinstall? i have tried boot with kernel failsafe, but don't work too... On Thu, Mar 17, 2011 at 4:38 PM, Mark Post mp...@novell.com wrote: On 3/17/2011 at 03:33 PM, Rogério Soaresrogerio.soa...@gmail.com wrote: Mark, i set up the filter recommend, add dm-multipath on /etc/sysconfig/kernel INITRD_MODULES section.. made mkinitrd -f mpath and reboote... but now my server dead :) we are using / on dasd disk any tips? Yeah, remove dm-multipath from the initrd and don't use -f mpath on the mkinitrd command. Unless your root file system is on a mulipathed device, you don't need it, and it will cause problems such as this. You also do _not_ need boot.multipath enabled. 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: lun multipathing / file system
On 3/17/2011 at 03:54 PM, Rogério Soaresrogerio.soa...@gmail.com wrote: Mark, just to learn something new today, except how to kill a server hehehe, i can recover this without reinstall? i have tried boot with kernel failsafe, but don't work too... Boot the system with the installation kernel and intitrd, activate your DASD volume(s) mount it/them, chroot, rebuild the initrd. If on z/VM, you could LINK read-write to it/them from another guest. 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/
