2 Replies Latest reply on Sep 18, 2014 8:37 PM by ezequielcarson

    Failed to probe OSFS child for device name

    ezequielcarson Novice

      Hi All,

       

      I have an issue with my Vsan Datastore.

       

      When I try to list files inside the vsan datastore i got this:

       

      /vmfs/volumes/vsan:521c3b52604c5430-a83ced64dc019f67 # ls -l

      ls: ./6b2b0e54-3199-dd02-06ab-002590f94756: No such device or address

      ls: ./Template_Win_100-20 (d7499652-fb71-4e02-a758-1be2ba1549f4): No such device or address

      ls: ./6a2b0e54-1e88-a311-f29a-002590f961ec: No such device or address


      Also i have the following errores on the vmkernel.log


      2014-09-14T17:36:00.500Z cpu20:467672)osfs: OSFS_MountChild:3541: Failed to probe OSFS child for device name '6a2b0e54-1e88-a311-f29a-002590f961ec': No filesystem on the device

      2014-09-14T17:36:01.743Z cpu20:467672)osfs: OSFS_MountChild:3541: Failed to probe OSFS child for device name '6a2b0e54-1e88-a311-f29a-002590f961ec': No filesystem on the device

      2014-09-14T17:36:02.986Z cpu20:467672)osfs: OSFS_MountChild:3541: Failed to probe OSFS child for device name '6a2b0e54-1e88-a311-f29a-002590f961ec': No filesystem on the device

      2014-09-14T17:36:04.229Z cpu20:467672)osfs: OSFS_MountChild:3541: Failed to probe OSFS child for device name '6a2b0e54-1e88-a311-f29a-002590f961ec': No filesystem on the device

      2014-09-14T17:36:04.229Z cpu31:467671)osfs: DebugDumpVmklinkResponse:843: {ID: 2e8; type:LOOKUP; pid:[    vsan]; cid:521c3b52604c5430-a83ced64dc019f67; status:No filesystem on the device; bufLen:0;

      2014-09-14T17:36:04.229Z cpu31:467671)osfs: OSFS_VmklinkLookup:543: Failure (p [    vsan], c 521c3b52604c5430-a83ced64dc019f67)

      2014-09-14T17:36:04.229Z cpu31:467671)osfs: OSFS_Lookup:2304: Lookup error: file = Template_Win_100-4 (00b3e2ed-548b-4ab4-b66e-14e3ea15e304), status = No filesystem on the device


      i have tried deleting the folder using the OSFS-RMDIR command, but im getting the same error:


      /usr/lib/vmware/osfs/bin # ./osfs-rmdir /vmfs/volumes/vsan\:521c3b52604c5430-a83ced64dc019f67/Template_Win_100*

      Deleting directory Template_Win_100 in container id 521c3b52604c5430a83ced64dc019f67 backed by vsan

      Failed.  Search vmkernel log and osfsd log for opID 'osfsIpc-1410716290.29'.


      I have the same error in any host that is part of the cluster...

       

      Any Help will be appreciated.

       

      Txs

      Ezequiel

        • 1. Re: Failed to probe OSFS child for device name
          CHogan Master
          VMware Employees

          This could be a number of things.

           

          1. Check the network configuration.

          - Can all of your hosts still ping one another over the VMkernel network

          - Any changes made that may impact the network? (VLAN, multicast)

           

          2. Check your disks.

          - From RVC, you can run vsan.disks_stats <cluster>

          - In the vSphere web client, navigate to Monitor > Virtual SAN > Physical Disks and look for disk failures

          • 2. Re: Failed to probe OSFS child for device name
            ezequielcarson Novice

            Hi Cormac,

             

            Thank you for replying my thread.

             

            I moved everything to 10G and activated IGMP snooppings on the ports and right now everything seems to be working fine.

             

            I have some "2014-09-19T03:31:27.499Z cpu26:60979 opID=c65eaa78)osfs: OSFS_MountChild:3541: Failed to probe OSFS child for device name '39851b54-684e-f7b9-0766-002590f94a56': No filesystem on the device" but i dont know how this is affecting the service.

             

            Thanks

            Ezequiel