Solved!
Go to SolutionDeduped files and blue color
I just upgraded from 5.6.45 to 5.6.49 and noticed that compressed and/or deduped files are now displayed in blue color. If dedupe was introduced in 5.6.43 why did we not see this color coding before ?
if i run this command, do i disable color coding or do i actually disable compression functionality (and dedupe is still enabled ? )
fs_dedupe -default -set server_2 -cifs_compression_enabled no
Thanks
649
0
Posted July 21st, 2010 08:00
Thank you Peter
649
0
Posted July 23rd, 2010 07:00
If you just dont like the blue color - you can change that via Windows registry
i am not going to monkey around with registry, deploying active directory policy ..etc. They are getting used to blue color, wether they like it or not
.
649
0
Posted July 23rd, 2010 07:00
to be clear - turning this off only affects the "manual" compression done via Windows explorer - it does not disable the regular dedupe runs scheduled by the Celerra that are configured via fs_dedupe or Celerra Manager
If you just dont like the blue color - you can change that via Windows registry
Rainer
649
0
Posted July 27th, 2010 16:00
I've actually had a customer where we had to turn off the CIFS compression since their "security" people didnt like that the files had "changed" even if it was just the colour :-)
649
0
Posted July 27th, 2010 17:00
hahah ...brilliant !!!
. You need to send this to Black Hat conference that starts in Vegas tomorrow, they will get a kick out of that.
649
0
Posted July 28th, 2010 12:00
The filename coloring is done by windows explorer and can be disabled. Reference Microsoft knowledgebase article ID 307987.
649
0
Posted June 13th, 2013 20:00
Just a question
[-cifs_compression_enabled {yes|no}]
This option controls whether CIFS compression is allowed. The default is yes,
enable CIFS compression. When set to yes and the deduplication state of the
filesystem is either on or suspended, then CIFS compression is allowed. If
the deduplication state is either off or in the process of being turned off,
then CIFS compression is not allowed, regardless of whether this option is set
to yes.
this flag just allows to set the compression from windows right ?
That is to a granularity level .
Which means I can set compress on a folder by folder basis .
Turning this on will turnoff for the entire filesystem. What will happen to the existing compressed folders
when i turn it off.will it decompress from the Dart or will do nothing and uncompress when the file or folder is accessed ?
for example
I have filesystem fs1 with dedupe turned one and cifs compression is enabled .
fs1 has folders /fs1/dira/dirb
dirb has compression turned on but /fs1 and /fs1/dira does not have this turned on
if i turn off compression
-cifs_compression_enabled no i understand that the further enabling of compression in future is disallowed .
what will happen to the existing compressed data.
649
0
Posted June 14th, 2013 13:00
Nothing will change in regards to already compressed data – just like the man page says
Peter_EMC
674 Posts
649
0
Posted July 20th, 2010 23:00
This is dedupe phase II which was introduced in 5.6.47
Now windows is aware of deduped (compressed) files and explorer is displaying them in blue.
In Phase II, if you use windows explorer compressing a single file on a deduped enabled FS, it will be compressed using the DART dedupe functionality ...
If you set -cifs_compression_enabled no all files in the FS will be decompressed. This is why the color is changing.
Then you can no longer apply the compression for files of this FS in Windows explorer, the error message is:
An error occurred applying attributes to this file:
Pathname
Compression is disabled for this volume.
Regards
Peter