Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jlg33]

Hello,
I just installed a DNS-340L NAS with 4 disk (4TB each)
I have create the volume in RAID0 or JBOD, but each time the block size on disk is 4GB.
A simple file takes 1 byte 3,99Go disk.
I try to create 2 volumes of 8TB (with EXT4 format that normally have a 4k block size).
How to reduce this size ?
I have found no information on ShareCenter

Thanks for your help

[FurryNutz]

Were you able to get any thing on this? 

[jlg33]

Good evening,
Nobody knows how to do?
Is the drives or the NAS level ?
Thank you

[ivan]

A couple of questions.
1)  are the drives you are using on the DNS-340L comparability list?
2)  do you have any data files that are larger than 4 TB?

Regarding the questions. 
1) if they are NOT on the comparability list it could be the reason for the problem you are seeing.
2) if you don't have data files larger than 4 TB have you tried setting the disks up as STANDARD (individual disks) volumes and what are the results?
Another thing, if your data is valuable it would be wise hot to use a disk configuration that could lose all that data if there is a problem with one disk.  We never setup a clients NAS box with any RAID array other than RAID 1 even when there is a reliable backup strategy in place.

[jlg33]

thank you for your reply

The disks are in the compatibility list (Seagate ST4000VN000 4GB)
I formatted the disk to try several types of RAID. He only has a few files over a few MB and 2GB
I just formatted in standard mode. It's the same thing.
But the indication is made by Windows 10. Is it accurate?
How to know the exact NAS occupation?
Thank you

[ivan]

OK, Win10 is suspect here because the disks on the compatibility list are tested to confirm the act as they are expected to.

A possible test is to enable the FTP server on the NAS and create a user with password. 

This allows any FTP client to connect if they know the user/password.  It also means that the AndFTP client for Android will work and show actual file size.   Using FileZilla for windows should also display the actual file size (at least it does on win7).

If you can confirm the actual file sizes using any operating system other than win10 you should be in a better position to see what is going on.

There is also the marketing aspect of the disk size to consider.  Here is a comment from a technical forum concerning the new 8 TB drive announced not long ago:

Re: Is it really 8TB?

I suspect it is 8TB unformatted as drive manufacturers report sizes, ie 1TB = 1,000,000,000,000 bytes as opposed to 1099511627776 bytes that you might be expecting.

In addition to to the TB/TiB difference you will also have the usual loss of capacity due to formatting.

(yes, it annoys me too even though 1TB being 10004 is mathematically (decimal) correct, being an old fogey the binary 10244 is what would seem more logical)

Although that shouldn't be a problem it should be considered.

[jlg33]

By formatting in RAID 5 and copying files over, I realize that the information windows 10 are false.
Even though I do not see accurately the actual occupied space on the disk (not possible with FileZilla FTP, information on ShareCenter) the free space indicated globally is consistent with the file size
I stop searching

Thank you for yours responses

[FurryNutz]