Hello,

I do have a question about the space that unraid is taking for the array functionality on the disks when creating new shares.

Wanted to ask because on my two backup-servers I did manage somehow to have different disk-space occupied by unraid array.

After adding some more disks I was rebuilding my shares.

Now I created a normal samba share with 6 disks, no auto splitting, high water, all is working fine until now.

The first server tooked 150...GB something per disk. The second server only 55,8GB per disk. The disk have all the same size with 8TB, but are different brands. As well some SMR but the most are CMR type.

Why did this happen? Is there a logic that could explain to me, what I did different or wrong?

Assuming XFS, it will be different depending on the kernel version they were formatted with; more recent kernels cause XFS to have higher overhead.

Yes its formated with XFS, thanks for this information.

Higher overhead means that its using more space, right?

Is there any benefit or recommendation to reformat with the newer kernel?

3 hours ago, NoRaid99 said:

Higher overhead means that its using more space, right?

Yes

3 hours ago, NoRaid99 said:

Is there any benefit or recommendation to reformat with the newer kernel?

Newer kernels should have additional metadata that may help in case of issues, but it's difficult to say if it's worth the reformat

Allright, thanks again for your brillhant support.

wish you a good time!

https://forums.unraid.net/topic/195008-format-xfsv4-to-xfsv5/

also

https://docs.unraid.net/unraid-os/release-notes/7.2.0/#storage

it will warn if there are drives formatted in a deprecated version of XFS; those need to be migrated before 2030

Thanks for this additional info. I never have seen any warning about this after any update from v6 until now v7.2.4

(Great, since a few days I'm copying files to that server with the older XFS format.)

Where can I find the XFS version running atm?

You can check the syslog after the disks are mounted, e.g.:

Apr 14 08:39:29 MM kernel: XFS (md3p1): Mounting V5 Filesystem 3b00e006-84a3-4144-a8ed-6ac27d9cbf84

Yes, I found it meanwhile.

But it is on both servers at v5 but different amount of space used, like I did say before.

So v4 and v5 don't say anything about the 153GB or the 58,3GB used space for format. Is this right?

UnRaidNAS1 kernel: XFS (dm-0): Mounting V5 Filesystem 9a346960-a059-4818-afd2-97237eba549e  (on all disks from the array)
UnRaidNAS2 kernel: XFS (dm-0): Mounting V5 Filesystem 6861d2fc-c353-46e8-be0e-1ecaa666d216  (on all disks from the array)

seems that I am lucky.

Edited April 14Apr 14 by NoRaid99

The difference in overhead is not just v4 vs v5, early v5 with older kernels will use less space.

P.S. Any v4 should be convert, those are much worse for consistency vs. v5. Early v5 vs. current v5 is not so different.