Page 3 of 3

Re: Problem Multipath Centos 6.5 - Help Me

Posted: 2018/06/12 13:29:57
by dcantos
tunk wrote:
2018/06/06 17:00:30
You said you tested it with a windows server, so you must have defined that second host and mapped it to the volume.
I guess you can remove the mapping from some V3700 menu.
Sorry, I've run out of ideas - the only thing I can suggest is to create a partition, format and mount it, and then test it.
tunk.

I commented, I could already set the multipath route I attached a photo, as you can see I have the "8 disk" mapped in one, I guess I have to use the mapped disk as you can see, but when it comes to mounting it I get that this superblock, as I read I have to create the file system I have in this case the ext4 but when I run the command mkfs.ext4 the server hangs up and I reboot all the processes I do not know if something else I need to do?

Image

Re: Problem Multipath Centos 6.5 - Help Me

Posted: 2018/06/12 14:22:12
by tunk
How did you create the partition, and what's the output of: fdisk -l /dev/mapper/mpathd
Don't think it will make any difference; could you try XFS instead of ext4?
I don't think this will work either, but it may be worth a try:
- shut down the server
- disconnect the FC cables
- start the server and check if all is well
- shut down the server
- reconnect the FC cables
- start the server and see if you lost the six of the eight disks

BTW: there's no image.

Re: Problem Multipath Centos 6.5 - Help Me

Posted: 2018/06/13 13:53:16
by dcantos
tunk wrote:
2018/06/12 14:22:12
How did you create the partition, and what's the output of: fdisk -l /dev/mapper/mpathd
Don't think it will make any difference; could you try XFS instead of ext4?
I don't think this will work either, but it may be worth a try:
- shut down the server
- disconnect the FC cables
- start the server and check if all is well
- shut down the server
- reconnect the FC cables
- start the server and see if you lost the six of the eight disks

BTW: there's no image.
Image

fdisk -l /dev/mapper/

Disk /dev/mapper/Storwize_Zimbra: 2199.0 GB, 2199023255552 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000



Hi, tunk,

I attached the details, in addition to that to see if more then I do those steps I tell you that when I restarted all the processes trying to give the ext4 file system to the partition / dev / mapper / I was alarmed by the server with an error in the PCI but I think it was the same error that tried to force the file system.