3 Replies Latest reply: Oct 26, 2012 2:37 PM by Nik RSS

    Lun copy and SVM

    raja.yogi
      Hi Guys,
      We have a solaris server (solaris 10) which attached with emc vnx 5300 box. We present two luns sizes are 400GB and 300 GB. We configure raid0 (SVM) and mounted as /prod1. Now customer want the data from the /prod1, the storage admin create two more luns sizes are 420GB and 320GB and he done the SAN copy (feature of emc lun to lun block level copy).

      My question is there any possible way to mount the new luns with data? or

      Is it possible to get the data if i create the file system first and do the SAN copy?

      Thanks
      BharathirajaP
        • 1. Re: Lun copy and SVM
          Nik
          Hi.
          Small teory.

          1. Configuration of SVM stored localy on host. In case you present lun undev SVM control from one host to another - you lost SVM configuration and lost configured devices ( If you don't use metaset).

          2. SMI label include disk geometry. So if you use SAN copy on lager LUN, Solaris will detect LUN with original size.

          3. SAN copy overwrite previos content of the disk ( it's copy just block to block). So it's dos not metter previos state of destination disk.

          4. Generaly raide0 require that all disk will be same size. All biggest block don't use. May be you use concatenation ?

          Practics.
          You can try:
          1. Present new lun to host. Check that host detect new disks.
          2. use metastat -p for found current configuration of SVM
          3. use metainit for create new device with new detected disks using same configuration as orignal.
          4. Tru mount new device.
          The size of new device will be same as original. All additional space you lost.

          Possible, more easy - not use SAN copy. Just Create new FS and copy data by host.

          Regards.
          • 2. Re: Lun copy and SVM
            raja.yogi
            Hi,
            After create the metadevice using new luns i successfully mounted the new luns. But there are some fsck issues
            Here is the output,

            ufs: [ID 879645 kern.notice] NOTICE: /mnt: unexpected free inode 97313191, run fsck(1M) -o f
            root@vtnmsbl1 # fsck /dev/md/rdsk/d200
            ** /dev/md/rdsk/d200
            BAD SUPERBLOCK AT BLOCK 16: BAD VALUES IN SUPER BLOCK

            LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? y

            calcsb: short read of superblock from mkfs

            LOOK FOR ALTERNATE SUPERBLOCKS WITH NEWFS? y

            calcsb: short read of superblock from newfs
            SEARCH FOR ALTERNATE SUPERBLOCKS FAILED.

            USE GENERIC SUPERBLOCK FROM MKFS? y

            calcsb: short read of superblock from mkfs

            USE GENERIC SUPERBLOCK FROM NEWFS? y

            calcsb: short read of superblock from newfs
            SEARCH FOR ALTERNATE SUPERBLOCKS FAILED. YOU MUST USE THE -o b OPTION
            TO FSCK TO SPECIFY THE LOCATION OF A VALID ALTERNATE SUPERBLOCK TO
            SUPPLY NEEDED INFORMATION; SEE fsck(1M).

            Thanks
            Bharathiraja
            • 3. Re: Lun copy and SVM
              Nik
              Hi.

              Many reason that can cause this result.

              1. New metadevice create with other parameters then original.
              2. Lun copy was created when FS was mounted.
              3. Copy on 1 and 2 device was created at different time.
              4. Uncorrect copy of second LUN.


              What reason use this way for copy data ?

              Regards.