To further explain..... LVM when it loads up it sees duplicate PVs, because of the /dev/sda disks and your /dev/mapper multipath device. It uses the /dev/sd** disk instead of the /dev/mapper. By changing the filter to ignore /dev/sd* you prevent that from happening.
Sorry, got a call and didn't finish my reply. Deric >>> "Sollenberger, Justin W Mr CIV US DISA CDB24" >>> <justin.sollenber...@csd.disa.mil> 6/11/2009 12:06 PM >>> We have several SLES 10 SP2 guests that are using FCP LUNS. The OS is installed on 3390's and the LUNS are used to store the customer's data. Early this morning we lost one of the paths. Some of our systems reacted as I would have expected but others did not. The ones that reacted oddly would be the ones that I would assume to be busy at that time. Those systems show I/O errors, followed by filesystem errors, and then the filesystems all remount as read-only. I've include output for both scenarios. Reacted Correctly: Jun 11 03:44:34 system_a multipathd: sdb: tur checker reports path is down Jun 11 03:44:34 system_a kernel: device-mapper: multipath: Failing path 8:16. Jun 11 03:44:39 system_a multipathd: sdb: tur checker reports path is up Reacted Oddly: Jun 11 03:44:34 system_b multipathd: sdb: tur checker reports path is down Jun 11 03:44:34 system_b kernel: end_request: I/O error, dev sdb, sector 37486992 Jun 11 03:44:34 system_b kernel: Buffer I/O error on device dm-0, logical block 4685826 Jun 11 03:44:34 system_b kernel: lost page write due to I/O error on dm-0 Jun 11 03:44:34 system_b kernel: end_request: I/O error, dev sdb, sector 42200120 Jun 11 03:44:34 system_b kernel: end_request: I/O error, dev sdb, sector 47170040 Jun 11 03:44:34 system_b kernel: Buffer I/O error on device dm-1, logical block 653327 Jun 11 03:44:34 system_b kernel: lost page write due to I/O error on dm-1 Jun 11 03:44:34 system_b kernel: Buffer I/O error on device dm-1, logical block 653328 Jun 11 03:44:34 system_b kernel: lost page write due to I/O error on dm-1 Jun 11 03:44:34 system_b kernel: Buffer I/O error on device dm-1, logical block 653329 Jun 11 03:44:34 system_b kernel: lost page write due to I/O error on dm-1 Jun 11 03:44:34 system_b kernel: Buffer I/O error on device dm-1, logical block 653330 Jun 11 03:44:35 system_b kernel: lost page write due to I/O error on dm-1 Jun 11 03:44:35 system_b kernel: end_request: I/O error, dev sdb, sector 50598296 Jun 11 03:44:35 system_b kernel: Buffer I/O error on device dm-1, logical block 1081859 Jun 11 03:44:35 system_b kernel: lost page write due to I/O error on dm-1 Jun 11 03:44:35 system_b kernel: Buffer I/O error on device dm-1, logical block 1081860 Jun 11 03:44:35 system_b kernel: lost page write due to I/O error on dm-1 Jun 11 03:44:35 system_b kernel: Buffer I/O error on device dm-1, logical block 1081861 Jun 11 03:44:35 system_b kernel: lost page write due to I/O error on dm-1 Jun 11 03:44:35 system_b kernel: Buffer I/O error on device dm-1, logical block 1081862 Jun 11 03:44:35 system_b kernel: lost page write due to I/O error on dm-1 Jun 11 03:44:35 system_b kernel: end_request: I/O error, dev sdb, sector 69213616 Jun 11 03:44:35 system_b kernel: end_request: I/O error, dev sdb, sector 58947168 Jun 11 03:44:35 system_b kernel: end_request: I/O error, dev sdb, sector 37337552 Jun 11 03:44:35 system_b kernel: Buffer I/O error on device dm-0, logical block 4667146 Jun 11 03:44:35 system_b kernel: lost page write due to I/O error on dm-0 Jun 11 03:44:35 system_b kernel: device-mapper: multipath: Failing path 8:16. Jun 11 03:44:35 system_b kernel: Aborting journal on device dm-0. Jun 11 03:44:35 system_b kernel: end_request: I/O error, dev sdb, sector 42200136 Jun 11 03:44:35 system_b kernel: end_request: I/O error, dev sdb, sector 69213640 Jun 11 03:44:35 system_b kernel: end_request: I/O error, dev sdb, sector 58947184 Jun 11 03:44:35 system_b kernel: Aborting journal on device dm-1. Jun 11 03:44:35 system_b kernel: Aborting journal on device dm-3. Jun 11 03:44:35 system_b kernel: Aborting journal on device dm-2. Jun 11 03:44:35 system_b kernel: ext3_abort called. Jun 11 03:44:35 system_b kernel: EXT3-fs error (device dm-2): ext3_journal_start_sb: Detected aborted journal Jun 11 03:44:35 system_b kernel: Remounting filesystem read-only Jun 11 03:44:35 system_b kernel: ext3_abort called. Jun 11 03:44:35 system_b kernel: EXT3-fs error (device dm-3): ext3_journal_start_sb: Detected aborted journal Jun 11 03:44:35 system_b kernel: Remounting filesystem read-only Jun 11 03:44:35 system_b kernel: ext3_abort called. Jun 11 03:44:35 system_b kernel: EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal Jun 11 03:44:35 system_b kernel: Remounting filesystem read-only Jun 11 03:44:35 system_b kernel: EXT3-fs error (device dm-1) in ext3_reserve_inode_write: Journal has aborted Jun 11 03:44:35 system_b kernel: EXT3-fs error (device dm-1) in ext3_dirty_inode: Journal has aborted Jun 11 03:44:35 system_b kernel: ext3_abort called. Jun 11 03:44:35 system_b kernel: EXT3-fs error (device dm-1): ext3_journal_start_sb: Detected aborted journal Jun 11 03:44:35 system_b kernel: Remounting filesystem read-only Jun 11 03:44:39 system_b multipathd: sdb: tur checker reports path is up Any advice or direction would be greatly appreciated. Thanks in advance. VR, Justin Sollenberger ---------------------------------------------------------------------- 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 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
