-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
How to avoid wasting space on already redundant volume ?
- Thread starter Andre-K
- Start date
- Status
All you would do, is create a disk for freenas to install too (3gb or so) and then a large one for your data (500gb for ex)
then create a ZFS volume using the 500gb drive you made.
There won't be an option for any type of 'raid', but this will allow you to add additional storage in the future
for ex, you create a new 250gb drive in esx, present to freenas. Then use volume manager to expand the current ZFS pool, select the new drive, and its that easy.
However this may slow down your freenas, as it will stripe the two together (write/read from both at same time) so it would be ideal if when you expanded it later if they were on a different Datastore.
then create a ZFS volume using the 500gb drive you made.
There won't be an option for any type of 'raid', but this will allow you to add additional storage in the future
for ex, you create a new 250gb drive in esx, present to freenas. Then use volume manager to expand the current ZFS pool, select the new drive, and its that easy.
However this may slow down your freenas, as it will stripe the two together (write/read from both at same time) so it would be ideal if when you expanded it later if they were on a different Datastore.
Let me rephrase:
If I have 5x3TB SAS drives, in RAID5 (hardware controller) , I already have redundancy.
Is there a method to make Freenas work with EXT4 or similar file system, so no matter how many TB it gets, it won't spend much of if on additional redundancy ?
If I have 5x3TB SAS drives, in RAID5 (hardware controller) , I already have redundancy.
Is there a method to make Freenas work with EXT4 or similar file system, so no matter how many TB it gets, it won't spend much of if on additional redundancy ?
I get what you are saying, but if I assign a virtual 3TB to Freenas , it'll use ZFS and I am able to pit 1TB of data on those 3TB.
This is my problem, because the 3TB virtual disk, is already protected by RAID5 - so while ZFS is very nice, I am not willing to be able to use only 1/3 of the assigned space)
I am very much aware that ZFS is not RAID5 - and has lots of neat features. I am just referring to the fact that it is displaying 1/3 of the drive space assigned as free. resembling a parity or mirror feature.
This is my problem, because the 3TB virtual disk, is already protected by RAID5 - so while ZFS is very nice, I am not willing to be able to use only 1/3 of the assigned space)
I am very much aware that ZFS is not RAID5 - and has lots of neat features. I am just referring to the fact that it is displaying 1/3 of the drive space assigned as free. resembling a parity or mirror feature.
When I said 1GB , I was speaking about the available space on the share made on FreeNAS - while it was using 3GB disk
sorry for talking about 3TiB and 3GiB ,
The Terabyte examples are from a Dell T420 server with ESXi 5.1 and FreeNAS as guest (latest version, fresh downloaded),
Gigabyte examples are on my workstation (Ubuntu) , running same, fresh FreeNAS as guest on a VMWare workstation 9 host.
The reason I started testing on workstation and right now are only testing that - is because I thought there could be something strange with multi terabyte drives.. that's also why I limited the virtual drive size to 3TiB - because it's no bigger then than a single drive.
From now on, I promise to stick to speaking of Gigabytes for the rest of the testing.
I never mixed up Giga*bits* into this.
I am glad to hear that you think this behavior is strange.
My backup plan is to skip FreeNAS, and run a Ubuntu server as file server on plain EXT4. - , but it would be sweet to get FreeNAS to doi the job,
- Status
