NFS Mount :- sharing a partition on a different host

On nfsserver (192.168.10.5)


# cat /etc/exports
/home 192.168.10.4/24(rw,sync)

Note:-192.168.10.4 is the NFS client where you want to see /home

restart nfs server or restart below services.
#service rpcbind restart
#service nfs restart
#service nfslock restart

On nfsclient (192.168.10.4)

[root@nfsclient /]# mount 192.168.10.5:/home/ /test/

[root@nfsclient /]# cd /test/

[root@nfsclient test]# ls

1         backup_plan    idmcerts.jks  lost+found        oraInventory

APP_home  env_sriram.sh  logs          oraInst.loc.orig  repos

For permanent Mount:

Edit /etc/fstab:

192.168.10.5:/home /test nfs defaults 0 0

Reload the fstab file by:

#mount -a


FYI: 


Some of the important nfs daemons are:
.rpcbind
.nfs
.netfs
.nfslock
.portmapper

Using kpartx to Mount VM Disk Images

If you are using a full disk image for your VM, instead of using a file system, you cannot simply mount it directly using

mount -o loop d0.img

Use the following commands to see the partitions in your disk, and then mount them.

# kpartx -av d0.img

add map loop0p1 : 0 29333504 linear /dev/loop0 2048

add map loop0p5 : 0 1380352 linear /dev/loop0 29337600

# mount /dev/mapper/loop0p1 /mnt

# ls /mnt

bin   cdrom  etc   initrd.img      lib         media  opt   root  selinux  sys  usr  vmlinuz

boot  dev    home  initrd.img.old  lost+found  mnt    proc  sbin  srv      tmp  var

# unmount /mnt

# kpartx -d d0.img

The last two commands are to unmount and delete the partition mappings.

I referred this link: http://ppadala.net/blog/2010/09/kpartx-to-mount-vm-disk-images/

Reducing and Creating a New Volume on LVM

From the previous post we have added 70G free space as below by reducing
the Volume of xen-vm1:

# vgs
  VG      #PV #LV #SN Attr   VSize   VFree
  DomUVol   1   1   0 wz--n- 267.66G   67.66G
  xen-vm1   1   1   0 wz--n- 500.00G   70.00G
  xen-vm2   1   1   0 wz--n- 498.00G 1020.00M
#

Now adding a new volume of 40G


Checking existing Volumes
# lvscan
  ACTIVE            '/dev/DomUVol/lvol0' [200.00 GB] inherit
  ACTIVE            '/dev/xen-vm2/xen_prov2' [497.00 GB] inherit
  ACTIVE            '/dev/xen-vm1/xen_prov1' [430.00 GB] inherit



Create a New volume of 40G on xen-vm1 VolumeGroup which we reduced 
on previous post:


[root@Linux ~]# lvcreate -L40G -n xen-vm3 xen-vm1
  Logical volume "xen-vm3" created

Now check the newly created Volume:


[root@Linux ~]# lvscan
  ACTIVE            '/dev/DomUVol/lvol0' [200.00 GB] inherit
  ACTIVE            '/dev/xen-vm2/xen_prov2' [497.00 GB] inherit
  ACTIVE            '/dev/xen-vm1/xen_prov1' [430.00 GB] inherit
  ACTIVE            '/dev/xen-vm1/xen-vm3' [40.00 GB] inherit

Create a Filesystem ext3 for newly added Logical Volume




[root@Linux ~]# mkfs.ext3 /dev/xen-vm1/xen-vm3
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
5242880 inodes, 10485760 blocks
524288 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
320 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.


Now Mounting the new file system:

[root@Linux]# ls
lost+found  vms  xen_vm1  xen_vm2  zipdb

[root@Linux]# mkdir xen_vm3

[root@Linux]# mount /dev/xen-vm1/xen-vm3 /FMW/xen_vm3


For Permanent Mount add to /etc/fstab: 


/dev/mapper/xen--vm1-xen--vm3    /FMW/xen_vm3  ext3    defaults        0 0