UNSOLVED

Raphlou

updated

15 years ago

R

Raphlou

1 Rookie

•

40 Posts

0

10796

January 8th, 2012 10:00

File system unavailable

Hello EMC gurus,

I request your help for a typical problem on file systems.

I am on a NS702G connected to a CX4-240F.

All the harware is fine.

My problem is only on a specific File System, which is unavailable under explorer.

With domain admin rights :

Under Windows explorer, I see all the shares.

If I click on a specific share named backup, I get : device not ready.

The File System concerned is supposed to be full.

It is not possible to get the used capacity :

[nasadmin@nas_cs0 ~]$ nas_fs -size fs_backup

total = 1915964 (sizes in MB) ( blockcount = 3923897600 )

[nasadmin@nas_cs0 ~]$

If I use the same command on another fs operational :

[nasadmin@nas_cs0 ~]$ nas_fs -size fs_tape4fc

total = 521035 avail = 20756 used = 500278 ( 96% ) (sizes in MB) ( blockcount = 1083615232 )

volume: total = 529109 (sizes in MB) ( blockcount = 1083615232 )

[nasadmin@nas_cs0 ~]$

I get more details.

In Celerra Manager - File Systems - on the line fs_backup the bar shows that the fs is blank

fs_backup properties : Updated data not available.

I tried to check the fs :

[nasadmin@nas_cs0 ~]$ nas_fsck -start fs_backup -monitor

id                          = 287

name                        = fs_backup

volume                      = meta_backup

fsck_server                 = server_2

inode_check_percent         = 0..10..20..30..30..40..50..50..60..70..80..80..Done

[nasadmin@nas_cs0 ~]$

No update with that command.

Could you give me any idea to investigate ?

Thank you for your help.

Best regards

Raphlou

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    5976

    0

    Posted January 8th, 2012 10:00

    is the file system mounted ?

  • Raphlou

    1 Rookie

    •

    40 Posts

    5977

    0

    Posted January 8th, 2012 13:00

    Hello Dynamox,

    Here are some other outputs :

    Following your comment, I consider the fs unmounted :

    [nasadmin@nas_cs0 ~]$ server_mount server_2 fs_backup /backup

    server_2 :

    Error 4109: server_2 : fs_backup : is mounted on /fs_backup

    [nasadmin@nas_cs0 ~]$

    [nasadmin@nas_cs0 ~]$ server_umount server_2 fs_backup

    server_2 : done

    [nasadmin@nas_cs0 ~]$

    After :

    [nasadmin@nas_cs0 ~]$ server_mount server_2 fs_backup

    server_2 :

    Error 16: server_2 : Device or resource busy

    mount uxfs rw /fs_backup 961=287 rw noscan triggerlevel=512 accesspolicy=NATIVE nolock

    [nasadmin@nas_cs0 ~]$

    With another fs :

    [nasadmin@nas_cs0 ~]$ server_umount server_2 test01

    server_2 : done

    [nasadmin@nas_cs0 ~]$ server_mount server_2 test01

    server_2 : done

    [nasadmin@nas_cs0 ~]$

    It works fine.

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    5977

    1

    Posted January 8th, 2012 13:00

    considering you already tried fsck , i would open a ticket with support.

  • Raphlou

    1 Rookie

    •

    40 Posts

    5977

    0

    Posted January 8th, 2012 13:00

    Dear Sir,

    Here is some details :

    Could you suggest a solution ?

    Best regards.

    Raphlou

    [nasadmin@nas_cs0 ~]$ server_mount server_2
    server_2 :
    root_fs_2 on / uxfs,perm,rw
    ... ...

    fs_backup on /fs_backup uxfs,perm,rw,noscan,triggerlevel=512,accesspolicy=NATIVE,nolock, ,
    root_fs_common on /.etc_common uxfs,perm,ro
    ... ...

    [nasadmin@nas_cs0 ~]$

    [nasadmin@nas_cs0 ~]$ server_df server_2 -inode fs_backup

    server_2 :

    Error 5: server_2 : Input/output error

    failed to complete command

    [nasadmin@nas_cs0 ~]$ server_df server_2 -inode test01       (another fs)

    server_2 :

    Filesystem          inodes         used        avail capacity Mounted on

    test01              251902           15       251887    0%    /test01

    [nasadmin@nas_cs0 ~]$

    [nasadmin@nas_cs0 ~]$ nas_fs -info fs_backup

    id        = 287

    name      = fs_backup

    acl       = 0

    in_use    = True

    type      = uxfs

    worm      = off

    volume    = meta_backup

    pool      = clar_r5_economy

    member_of = root_avm_fs_group_4

    rw_servers= server_2

    ro_servers=

    rw_vdms   =

    ro_vdms   =

    auto_ext  = no,virtual_provision=no

    deduplication   = Off

    stor_devs = CK200051700389-005E,CK200051700389-0060,CK200051700389-005C,CK200051700389-0009,CK200051700389-000A

    disks     = d75,d76,d77,d16,d12

    disk=d75   stor_dev=CK200051700389-005E addr=c0t2l3         server=server_2

    disk=d75   stor_dev=CK200051700389-005E addr=c32t2l3        server=server_2

    disk=d75   stor_dev=CK200051700389-005E addr=c16t2l3        server=server_2

    disk=d75   stor_dev=CK200051700389-005E addr=c48t2l3        server=server_2

    disk=d76   stor_dev=CK200051700389-0060 addr=c16t2l1        server=server_2

    disk=d76   stor_dev=CK200051700389-0060 addr=c48t2l1        server=server_2

    disk=d76   stor_dev=CK200051700389-0060 addr=c0t2l1         server=server_2

    disk=d76   stor_dev=CK200051700389-0060 addr=c32t2l1        server=server_2

    disk=d77   stor_dev=CK200051700389-005C addr=c16t2l5        server=server_2

    disk=d77   stor_dev=CK200051700389-005C addr=c48t2l5        server=server_2

    disk=d77   stor_dev=CK200051700389-005C addr=c0t2l5         server=server_2

    disk=d77   stor_dev=CK200051700389-005C addr=c32t2l5        server=server_2

    disk=d16   stor_dev=CK200051700389-0009 addr=c16t1l3        server=server_2

    disk=d16   stor_dev=CK200051700389-0009 addr=c48t1l3        server=server_2

    disk=d16   stor_dev=CK200051700389-0009 addr=c0t1l3         server=server_2

    disk=d16   stor_dev=CK200051700389-0009 addr=c32t1l3        server=server_2

    disk=d12   stor_dev=CK200051700389-000A addr=c0t1l4         server=server_2

    disk=d12   stor_dev=CK200051700389-000A addr=c32t1l4        server=server_2

    disk=d12   stor_dev=CK200051700389-000A addr=c16t1l4        server=server_2

    disk=d12   stor_dev=CK200051700389-000A addr=c48t1l4        server=server_2

    [nasadmin@nas_cs0 ~]$

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    5977

    1

    Posted January 8th, 2012 14:00

    datamover failover/failback might fix it but i would first consult with support

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    5977

    1

    Posted January 8th, 2012 19:00

    I suggest to work directly with support on this

  • VivekSoni

    24 Posts

    5977

    0

    Posted October 14th, 2014 04:00

    Hello raphlou 

     

    The file system is not a multipath fs to mount it on various mountpoints. As for your issue while mounting the fs again, as rightfully suggested by dynamox , I would do a quick reboot of the DM and check or even failover/failback (same downtime needed for both).

     

    Let me know how that works.

  • nekkantiv

    6 Posts

    5977

    0

    Posted October 4th, 2018 11:00

    Hi Everyone,

    I have similar kind of issue, Please share if you have any resolution for this

  • Raphlou

    1 Rookie

    •

    40 Posts

    5977

    0

    Posted October 4th, 2018 12:00

    Dear Sir,

    I didn't get any solution.

    The system was out of warranty, but also end of support for DELL-EMC. (NS-80)

    To call support and to open an out of warranty Service Request would have been too dangerous, without any idea of the total price, with no idea on the success.

    I have sold to my customer 4 additional DAEs with 60 disks 600 GB 10K, and I have added these drives into the clar_r5_performance Pool.

    Then the customer has restored all the data needed, in a separate File System declared for that.

    A very long maintenance operation, but I have got the customer satisfaction, and also nobody was fired monday morning. :-)

    Try the different commands specified in this post, I hope that you will get a solution.

    Good luck.

    Best regards.

    Raphlou.

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    1456

    0

    Posted October 5th, 2018 02:00

    please open a service request and have support troubleshoot and fix