UNSOLVED

liewy

updated

14 years ago

L

liewy

9 Posts

1

3454

April 15th, 2013 22:00

Filesystem Explorer in OneFS v7.0.1.2 showing files and directories as RED status "Protection is not active".

To anyone who has upgraded from OneFS v6.5.412 to v7.0.1.2,

When browsing folders using OneFS Filesystem Explorer, folders and files have a red round dot under the column labelled as "Protected". When you hover the mouse over the red dot, it displays "Proctection is not active". However, using command line to check the status of the file/directory, the protection is valid.

New Folders/Files created since the upgrade are showing as "Green" which is Protected.

I am curious if anyone has experienced or observed this?

Kind regards,

Liewy

  • jdpal

    4 Posts

    1195

    0

    Posted April 20th, 2013 10:00

    I have seen this behavior before, although I never got an answer as to what happened. You should open a case with support immediately.

    Also, the latest version of OneFS is 7.0.1.4, is there a particular reason why you did not go to that version?

    Good luck!

  • liewy

    9 Posts

    1195

    0

    Posted April 22nd, 2013 22:00

    Thanks for the reply jdpal_ccs.

    We went to 7.0.1.2 as it was the latest version at that time. We just patched to 7.0.1.4 yesterday. Yes I have logged a support case with EMC. They have determined it is a display issue from the upgrade. The files are still protected. The patch to 7.0.1.4 did not make any difference relating to this issue nor we were expecting it to.

    Liewy

  • AndrewChung

    132 Posts

    1195

    0

    Posted May 17th, 2013 13:00

    There is a bug where if you have more than 999 files in a directory, the File Explorer in the WebUI does not enumerate the properties of the files correctly.  I do not know of an expected release that this will get fixed.

  • liewy

    9 Posts

    1195

    0

    Posted May 19th, 2013 19:00

    Hi AndrewChung,

    Thanks for your reply. Yes I have learnt that 999 files in a directory will display with a "red dot" in the WebUI.

    Since we have updated to 7.0.1.4, for some unknown reason, my original issue has gone away. Everything is showing up as green and protected now.

    Liewy

  • jdpal

    4 Posts

    1195

    0

    Posted May 30th, 2013 08:00

    It's worth noting that when I observed the behavior, the files showed as unprotected via the CLI as well.

  • 1195

    0

    Posted May 30th, 2013 08:00

    This is referenced in emc14003257.


    Polling the metadata for large numbers of files can take a long time, which would cause the webui to appear to hang while waiting for that data.  The webui doesn't poll all of the data when there are a large number of files to try and keep everything responsive.   If you check the files from the CLI, you will likely see that they are indeed protected.

    As a test, create a directory, and put 1001 files in it.  Observe the lack of metadata when browsing to that directory in the file system explorer.  Then, from the CLI, remove 3 files (should be 998 left, the [ .. ] 'this directory' counts too).  With 998 files, you will again see the metadata.

  • csohryu2

    1 Message

    1195

    0

    Posted October 11th, 2013 12:00

    I had a client that is seeing this in 6.5.5.23 as well. Though he has more than 999 files/folders in multiple dirs, it is only showing in one dir. This is the only reference to this error that I can find on support.emc.com. Does anyone have any further information on how to clear this error or have it show protected as it should?

  • MRWA

    1 Rookie

    •

    83 Posts

    1195

    0

    Posted October 14th, 2013 08:00

    csohryu2 @jdpal_css go ahead and open up a ticket for support and keep us informed on what you find.

  • jimgossett

    26 Posts

    1195

    1

    Posted October 14th, 2013 10:00

    Another possibility here is that, after an upgrade from 6.5.x to 7.x, the Isilon filesystem moves from SmartPools v1 to SmartPools v2. This internally involves dividing up node pools into sets of disk pools for greater overall protection; it doesn't really matter much to end users, but until a SmartPools/SetProtectPlus job has run post-upgrade, the system will show files as "red" because they aren't laid out "correctly." You still have the same level of protection that you did pre-upgrade, but the filesystem wants to re-layout those files according to the new SmartPools v2 rules.

    That would potentially explain why the symptom "went away", as well. The system, by default, kicks off these jobs automatically every night at 22:00, but the job could have been pre-empted by another higher priority job or have taken some time to finish the first time post-upgrade.

    Jim