Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 232869

LUN Expansion issues : No filesystem on the device

$
0
0

Hi  Guys ,

 

I have two Fibre Channel LUN provision from VNX Storage Array  Both are represented to the ESX host. But   I am facing an issue in LUN expansion.

 

Previously this LUNs were under the protection of Recover Point:  So I removed the Recover Point protection as per mentioned in blog .  Refer URL http://vblog.matt-taylor.org/2010/10/24/resizing-luns-replicated-by-recoverpoint/. So now the recover point is out of picture.

 

Now  I have increase the size of LUN on VNX Storage array . The LUNS was expanded but VMware ESX now cannot recognise the new free space.                                             

 

Data store                                                                        Devices    

Data2                                   ds:///vmfs/volumes/50538a16-f1ad0570-5dec-0025b501a005/                     

Data4                                   ds:///vmfs/volumes/50e4daed-dab1e806-c6fd-0025b501a007/

 

After reviewing Vmkernal logs I found Warning for the devices mentioned below.

 

2013-01-31T23:56:45.141Z cpu37:7529680)WARNING: Vol3: 1605: Failed to refresh FS 50538a16-f1ad0570-5dec-0025b501a005 descriptor: No filesystem on the device

2013-01-31T23:56:45.232Z cpu27:7529680)WARNING: Vol3: 1605: Failed to refresh FS 50538a16-f1ad0570-5dec-0025b501a005 descriptor: No filesystem on the device

 

2013-01-31T23:56:45.140Z cpu37:7529680)WARNING: Vol3: 1605: Failed to refresh FS 5074848b-00e971f0-fb21-0025b501a005 descriptor: No filesystem on the device

2013-01-31T23:56:45.232Z cpu27:7529680)WARNING: Vol3: 1605: Failed to refresh FS 5074848b-00e971f0-fb21-0025b501a005 descriptor: No filesystem on the device

 

Observations

 

-           There is no any performance issue are observed on this datastore. Virtual machines on this datastores are running with no issue.

-           The message is clearly state that something is wrong with VMFS FS

-           As per my observation this LUN were part of Recover point appliance, though we removed this datastore from Recover point appliance

-           In the same ESX cluster I can able to extended other LUN which were not part of the recover point appliance

 

Questions :

 

-           After reviewing the vmkearnal logs it seem to be that.. it is clearly something wrong with VMFS FS. So can we repair it rather than destroying LUN and re-create again ?

-           What configuration  of Recovery Point tampering the VMFS File  structure on datastore ?


Viewing all articles
Browse latest Browse all 232869

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>