Hi Mark,

Its show as size on disk, all looks good from OneFs but windows explorer properties shows as 1.22MB on disk, dont believe its related to snaps as believe the snaps are meta data so just pointers back to the source unless I'm mistaken with that. ?

Is it a difference of "Size" and "Size on Disk" which accounts for snapshotting?

If the data has changed,  you'll see an increased "Size on Disk" to account for the snapshots delta..

But I think this has more to do with the protection (N+M) the cluster is running..  Also you have two options for protection the data: Erasure Codes and Data Mirroring.. Data Mirroring takes up more space..

The Isilon Admin Guide has a nice table on the overhead caused by each protection level based on number of nodes... Its on page 144..

Hi all

When looking at the file in Windows Explorer, should the file not be reported at the size the file actually has, and not as  a total sum of what capacity OneFS is using to store all the copies of the file due to the Flex Protection settings for the file/ cluster ???

Jim Ekberg-Hegner

Correct, this is related to he overhead of the file. However, that seems really large. Can you do an "isi get -DD /ifs/pathtofile" on the cluster and attach the output. This will be a lot of details about how the cluster is storing and protecting the file.

Thanks,

Jason Sturgeon

Isilon Corporate Systems Engineer

EMC²| Isilon Storage Division

Here is the isi get results

POLICY  W  LEVEL PERFORMANCE COAL  ENCODING      FILE              IADDRS
default   16+2 concurrency on    UTF-8         SCOM_Template.tpl <1,35,280930304:512>, <6,33,1924032000:512>, <7,34,237381120:512> ct: 1354270819 rt: 0
*************************************************
* IFS inode: [ 1,35,280930304:512, 6,33,1924032000:512, 7,34,237381120:512 ]
*************************************************
*
*  Inode Version:      6
*  Dir Version:        2
*  Inode Revision:     5
*  Inode Mirror Count: 3
*  Recovered Flag:     0
*  Recovered Groups:   0
*  Link Count:         1
*  Size:               346
*  Mode:               0100770
*  Flags:              0x130000e0
*  Physical Blocks:    3
*  LIN:                1:15cd:1a74
*  Logical Size:       8192
*  Shadow refs:        0
*  Restripe Cursor:    None
*  Abort Cursor:       None
*  Layout cursor:      None
*  Last Modified:      1354270819.805201300
*  Last Inode Change:  1372167284.939138070
*  Create Time:        1354270819.633328500
*  Rename Time:        0
*  Write Caching:      Enabled
*  Parent Lin          1:162e:0249
*  Parent Hash:        199619
*  Snapshot IDs:       None
*  Last Paint ID:          2329
*  Domain IDs:         { 65542 }
*  LIN needs repair:   False
*  Manually Manage:
*       Access         False
*       Protection     False
*  Protection Policy:  Diskpool default
*  Current Protection: 16+2
*  Future Protection:  0x
*  Disk pools:         policy x400_66tb_1.2tb-ssd_48gb(2) -> data target x400_66tb_1.2tb-ssd_48gb:4(4), metadata target x400_66tb_1.2tb-ssd_48gb:1(1)
*  SSD Strategy:       metadata-write
*  SSD Status:         complete
*  Layout drive count: 0
*  Access pattern: 0
*  Data Width Device List:
*  (d: 11, mar:00001000
*  (d: 16, mar:80000000
*  (d: 19, mar:00001000
*  Meta Width Device List:
*
*  File Data (77 bytes):
*    Metatree Depth: 1
*
*  Dynamic Attributes (91 bytes):
*
        ATTRIBUTE                OFFSET SIZE
        Domains                  0      11
        NTFS ACL entries         11     15
        NTFS Extended Owner/Group26     36
        Disk pool policy ID      62     5
        Last snapshot paint time 67     9
        v5 Data wdl              76     15

PROTECTION GROUPS

        lbn 0: 16+2
                19,12,164405248:8192#1
                0,0,0:8192#255
                11,12,10672193536:8192#1
                0,0,0:8192#15
                16,31,9874186240:8192#1
                0,0,0:8192#15

Metatree logical blocks:
         zero=255 shadow=0 ditto=0 prealloc=0 block=1
3 allocated blocks
0/0 (0%) of possible blocks contiguous

*************************************************

SECURITY DESCRIPTOR OWNER/GROUP

*  Owner - SID:S-1-5-21-2414399092-292161696-3476272628-23394
*  Group - SID:S-1-5-21-2414399092-292161696-3476272628-513

*************************************************

*
*************************************************

Well,  he said files of 1k are showing up as 1.22 mb...  that is what a 98x mirror data protection?

I would be interested in interpreting the isi get -DD output, too. Nowhere it explicitly says 3x...

Peter

Hi Gents,

Thanks for the interest in this we just to confirm all looks good on the ofs side however when we look at the file properties from windows is shows as 1.22mb on the disk. So have raised an incident with EMC and they are saying its a possible bug between windows and samba which was seen in previous versions of ofs. So once I get confirmation of this will also be testing if the quota has any issues with this as assuming this is done from the ofs side.

Thanks again for the interest and discussions so far

What version of 1fs and windows client?

Sent from my iPad