Buffalo Forums

Products => Storage => Topic started by: kan on February 20, 2018, 07:03:47 PM

Title: Actual File Size differs big time to allocated size
Post by: kan on February 20, 2018, 07:03:47 PM
I have a LinkStation 200 Series NAS with two 1Tb drives mirrorred. It is mapped  onto our peer to peer network for all Windows 10 PC's to access. When accessing through Windows Explorer, the allocated size is 1000% more than the actual file size -  ie.  1Mb file is allocated 100Mb .   Nas Navigator shows the drive 65% of the total 919MB available.
When trying to backup the NAS to an external usb 2Tb Drive, get an error out of space.  Any ideas?  Thx
Title: Re: Actual File Size differs big time to allocated size
Post by: mc2 on February 24, 2018, 11:25:22 AM
The LS220 has a cluster size of 128MB, i.e. the space any file takes is a multiple of 128MB, which makes the LinkStation unsuitable for storing lots of "small" (much less than128MB!) files.

However, it also seems to sometimes greatly over-allocate larger files.  I put in a report about that a month ago, but have had no response ... http://forums.buffalotech.com/index.php?topic=24915
Title: Re: Actual File Size differs big time to allocated size
Post by: oxygen8 on March 03, 2018, 04:36:28 AM
All Linkstations have a cluster size of 4kB, i.e. the space any file takes is a multiple of 4kB
Only the allocaded space message from samba is buggy.
All programms who use this message will show wrong values.
The drive summary will reported correct.
Browser ID: smf (is_webkit)
Templates: 1: Printpage (default).
Sub templates: 4: init, print_above, main, print_below.
Language files: 1: index+Modifications.english (default).
Style sheets: 0: .
Hooks called: 55 (show)
Files included: 27 - 1055KB. (show)
Memory used: 734KB.
Tokens: post-login.
Queries used: 10.

[Show Queries]