Login or Register to Ask a Question and Join Our Community


Red Hat

Cannot remove root Filesystem from the Multipath configuration

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Cannot remove root Filesystem from the Multipath configuration
# 1  
Old 01-23-2014
Cannot remove root Filesystem from the Multipath configuration
Hello all,

I am running "Red Hat Enterprise Linux Server release 6.4 (Santiago)"
The root Filesystem is currently part of the Multipath configuration and I need to remove it without rebooting the production Server.
The wwid I want to remove from Multipathing is the last one i the list of wwid's below, i.e. 3600508b1001c5c8ef3f93243d9a1bd41
I'll provide the files I think might be required. Any help would be great.
Code:
#cat /etc/fstab
/dev/mapper/vgroot-lvroot /                       ext4    defaults        1 1
UUID=4562a55c-c3ab-436a-a222-e82df753c756 /boot                   ext4    defaults        1 2
/dev/mapper/vgroot-lvoracle /bt/oracle              ext4    defaults        1 2
/dev/mapper/vgroot-lvmigration  /bt/migration      ext4    defaults        1 2
/dev/mapper/vgbackup-lvbackup    /bt/backup      ext4    defaults        1 2
/dev/mapper/vgroot-lvhome /home                   ext4    defaults        1 2
/dev/mapper/vgroot-lvopt /opt                    ext4    defaults        1 2
/dev/mapper/vgroot-lvtmp /tmp                    ext4    defaults        1 2
/dev/mapper/vgroot-lvusr /usr                    ext4    defaults        1 2
/dev/mapper/vgroot-lvvar /var                    ext4    defaults        1 2
/dev/mapper/vgroot-lvswap swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0

# ll /dev/mapper
total 0
lrwxrwxrwx. 1 root root      7 Jan 23 16:37 asm-data -> ../dm-3
lrwxrwxrwx. 1 root root      7 Jan 23 16:37 asm-data1 -> ../dm-8
lrwxrwxrwx. 1 root root      7 Jan 23 16:37 asm-data2 -> ../dm-1
lrwxrwxrwx. 1 root root      7 Jan 23 16:37 asm-data3 -> ../dm-7
lrwxrwxrwx. 1 root root      7 Jan 23 16:37 asm-log -> ../dm-0
lrwxrwxrwx. 1 root root      7 Jan 23 16:37 asm-stdby-data -> ../dm-9
lrwxrwxrwx. 1 root root      7 Jan 23 16:37 backup01 -> ../dm-2
crw-rw----. 1 root root 10, 58 Jan 23 14:34 control
lrwxrwxrwx. 1 root root      7 Jan 23 14:34 mpatha -> ../dm-4
lrwxrwxrwx. 1 root root      7 Jan 23 14:34 mpathap1 -> ../dm-5
lrwxrwxrwx. 1 root root      7 Jan 23 14:34 mpathap2 -> ../dm-6
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgbackup-lvbackup -> ../dm-19
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvhome -> ../dm-15
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvmigration -> ../dm-18
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvopt -> ../dm-13
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvoracle -> ../dm-17
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvroot -> ../dm-10
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvswap -> ../dm-11
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvtmp -> ../dm-14
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvusr -> ../dm-16
lrwxrwxrwx. 1 root root      8 Jan 23 14:34 vgroot-lvvar -> ../dm-12

#cat /etc/multipath/wwids
/360a98000424a414b453f443548503642/
/360a98000424a414b453f443548503644/
/360a98000424a414b453f443548503646/
/360a980004246534a342b444739665568/
/360a980004246534a342b44473966556a/
/360a980004246534a342b444739665566/
/360a980004246534a342b44473966556c/
/360a980004246534a342b444739665572/
/360a980004246534a342b444739665570/
/360a980004246534a342b444739665574/
/360a980004246534a342b44473966556e/
/360a98000424a414b453f44354850364a/
/360a980004246534a342b444739665576/
/360a980004246534a342b444739665578/
/360a980004246534a342b44473966557a/
/3600508b1001c5c8ef3f93243d9a1bd41/

# multipath -F
Jan 23 17:27:37 | asm-data: map in use
Jan 23 17:27:37 | mpatha: map in use
Jan 23 17:27:37 | backup01: map in use
Jan 23 17:27:37 | asm-log: map in use
Jan 23 17:27:37 | asm-stdby-data: map in use
Jan 23 17:27:37 | asm-data3: map in use
Jan 23 17:27:37 | asm-data1: map in use

#cat /etc/multipath.conf | grep -v ^#
defaults {
        user_friendly_names yes
        path_grouping_policy multipath
        find_multipaths yes
}

multipaths {
   multipath {
      wwid     360a980004246534a342b44473966556e
      alias    backup01
      }
   multipath {
      wwid      360a98000424a414b453f443548503644 
      alias     asm-data
      }
   multipath {
      wwid      360a98000424a414b453f443548503642 
      alias     asm-log
      }
   multipath {
      wwid     360a980004246534a342b444739665576
      alias    asm-data1
      }
   multipath {
      wwid     360a98000424a414b453f44354850364a
      alias    asm-data2
      }
   multipath {
      wwid     360a980004246534a342b44473966557a 
      alias    asm-data3
      }
   multipath {
      wwid     360a980004246534a342b444739665578 
      alias    asm-stdby-data
      }
   }

===========================================================

Thanks in advance for any help!
Last edited by vbe; 01-23-2014 at 03:22 PM.. Reason: code tags
# 2  
Old 01-24-2014
Have you tried. Removing the wwid from /etc/multipath.conf
And reload multipathd

Not sure if /etc/multipath/wwid is updated automatically. But when we had to bring a new LUN into multipath. The steps were to add WWID to multipath.conf and reload multipathd. This was in RHEL 5.5 though. Now if we consider going backwards the earlier steps would work. Not tried and tested
# 3  
Old 01-27-2014
Hi, many thanks for the reply.
We have tried that already, no success.
I have also blacklisted the WWID in the multipath.conf and still no success.
There is one curious thing however. When we re-read the new configuration, although the root filesystem is still listed, it only appears to have one path now.
I wonder if this is a red herring.
See output from 'multipath -ll' below.
The root filesystem is labelled 'mpatha'
Code:
asm-data (360a98000424a414b453f443548503644) dm-3 NETAPP,LUN
size=768G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 2:0:0:11 sdc  8:32   active ready running
| `- 3:0:0:11 sdd  8:48   active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 2:0:1:11 sdq  65:0   active ready running
  `- 3:0:1:11 sdx  65:112 active ready running
mpatha (3600508b1001c5c8ef3f93243d9a1bd41) dm-4 HP,LOGICAL VOLUME
size=279G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 4:0:0:0  sdo  8:224  active ready running
backup01 (360a980004246534a342b44473966556e) dm-2 NETAPP,LUN
size=250G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 2:0:1:22 sds  65:32  active ready running
| `- 3:0:1:22 sdz  65:144 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 3:0:0:22 sdh  8:112  active ready running
  `- 2:0:0:22 sdg  8:96   active ready running
asm-log (360a98000424a414b453f443548503642) dm-0 NETAPP,LUN
size=256G features='3 pg_init_retries 50 retain_attached_hw_handler' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 2:0:0:10 sda  8:0    active ready running
| `- 3:0:0:10 sdb  8:16   active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 2:0:1:10 sdp  8:240  active ready running
  `- 3:0:1:10 sdw  65:96  active ready running
asm-stdby-data (360a980004246534a342b444739665578) dm-9 NETAPP,LUN
size=250G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 2:0:1:24 sdu  65:64  active ready running
| `- 3:0:1:24 sdab 65:176 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 2:0:0:24 sdk  8:160  active ready running
  `- 3:0:0:24 sdl  8:176  active ready running
asm-data3 (360a980004246534a342b44473966557a) dm-7 NETAPP,LUN
size=250G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 2:0:1:25 sdv  65:80  active ready running
| `- 3:0:1:25 sdac 65:192 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 2:0:0:25 sdn  8:208  active ready running
  `- 3:0:0:25 sdm  8:192  active ready running
asm-data2 (360a98000424a414b453f44354850364a) dm-1 NETAPP,LUN
size=250G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 2:0:0:12 sde  8:64   active ready running
| `- 3:0:0:12 sdf  8:80   active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 2:0:1:12 sdr  65:16  active ready running
  `- 3:0:1:12 sdy  65:128 active ready running
asm-data1 (360a980004246534a342b444739665576) dm-8 NETAPP,LUN
size=250G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 2:0:1:23 sdt  65:48  active ready running
| `- 3:0:1:23 sdaa 65:160 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 2:0:0:23 sdi  8:128  active ready running
  `- 3:0:0:23 sdj  8:144  active ready running

Last edited by Franklin52; 01-27-2014 at 07:27 AM.. Reason: Please use code tags
# 4  
Old 01-29-2014
I am not understanding what you wanted to achieve.
Are you planning to migrate to new environment or something?
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Red Hat

Multipath configuration not being detected

Hi, In a RHEL 5 box, I have just added new multipath configurations in /etc/multipath.conf : blacklist_exceptions { wwid "360002ac0000000000000008e0001ee00" wwid "360002ac0000000000000008f0001ee00" wwid "360002ac000000000000000900001ee00" wwid... (0 Replies)
Discussion started by: anaigini45
0 Replies

2. Solaris

Multipath address configuration in Solaris 10.

Hi all, I'm wondering if anyone knows whether Solaris IPMP can be configured such that the IPs of the physical NICs are not available to applications when using IP4 or if the group address and the underlying physical address are always present? Thanks. (3 Replies)
Discussion started by: Skrynesaver
3 Replies

3. Red Hat

Multipath.conf configuration max_fds

Hi all, I am looking at the specific configuration settings for multipath.conf on RHEL5.5. In particular i was looking at the max_fds setting. Can anyone tell me the max number of open file descriptors that the RHEL5.5 system can have? It has been set previously to 8192, and i was... (4 Replies)
Discussion started by: Tommyk
4 Replies

4. Linux

root filesystem goes readonly

I see this when tried to create a dir using root fstab entries are pretty normal tried to remount with rw but it is still the same block device /dev/sda2 is write-protected ---------- Post updated at 04:57 PM ---------- Previous update was at 03:51 PM ---------- fstab entry ... (4 Replies)
Discussion started by: robo
4 Replies

5. Solaris

Resizing the Root Filesystem

Is it possible to increase the root filesystem size without reboot ?? (4 Replies)
Discussion started by: gowthamakanthan
4 Replies

6. UNIX for Dummies Questions & Answers

Root filesystem filling up!

Hi all. New to the forum and new to Unix admin... / filesystem filled up and I can't find where the large files are. Any help will be apppreciated: # df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 8063580 7941745 41200 100% / /proc ... (4 Replies)
Discussion started by: jamie_collins
4 Replies

7. Solaris

Root Filesystem

Hi, Can we install root file system on other than 0th slice???? (5 Replies)
Discussion started by: tirupathiraju_t
5 Replies

8. UNIX for Advanced & Expert Users

Mounted Root Filesystem

In my Solaris 10 based server, I have noticed the following mounts when a use DF -K /dev/dsk/c0t0d0s0 5062414 3213876 1797914 65% / / 5062414 3213876 1797914 65% /net/se420 I understand the first mount because it appears in my vfstab file and is the mount of root that I would expect.... (1 Reply)
Discussion started by: jimthompson
1 Replies
Login or Register to Ask a Question