Autoexpand is on but not expanding

[jgreco]

For a quick fix to get all the available, would backing it up and then recreating the iSCSI then copying it back onto the system. Then later on start on a system that uses the CIFS on FreeNAS for all the students and staff? Would that work better for the purpose of the NAS system?

That'd be a ton better. You're doing it the most inefficient way I can think of, see https://forums.freenas.org/index.ph...res-more-resources-for-the-same-result.28178/

EDIT:
I know you keep on going on about multiple iSCSI attachments. What I am doing is a iSCSI to the server and then shares from that one connection. This shouldn't create the issues that would of been caused by the block level write. Would it not?

Correct. One less hazard.

 

[Adrien Clark]

Sorry replacing the 500GB with the Terabyte.

 

[gpsguy]

You originally told us that you replace 2x500GB disks with 2x1TB disks. And that they are mirrored. If you only have the two new hard disks in the server, you only have ~900GiB in total.

50% of that is about 450GiB.


Sent from my iPhone using Tapatalk

 

[rogerh]

You originally told us that you replace 2x500GB disks with 2x1TB disks. And that they are mirrored. If you only have the two new hard disks in the server, you only have ~900GiB in total.

50% of that is about 450GiB.

But AIUI he is now going to abandon iSCSI and use CIFS on FreeNAS, which should give him a few hundred GB to use safely?

 

[gpsguy]

I thought his quick fix was to expand his iSCSI LUN ( backup, recreate,restore).

And down the road switch to CIFS directly from FreeNAS.

But AIUI he is now going to abandon iSCSI and use CIFS on FreeNAS, which should give him a few hundred GB to use safely?

 

[rogerh]

Perhaps - in which case you are right and he should have got 2TB drives!

 

[maglin]

This threes made my head hurt. iSCSI with 4GB of ram and then using all available space for the vDev. Using that config for anything more important than snapchat is asking for trouble.

Really it sounds like just using a Windows server box would be better and use less power. Get 8GB of ram and run a cifs share and at least it won't be an accident waiting to happen with FreeNAS. I think open filer can run on 4 GB of ram but I maybe wrong. I hope you don't the blame when this data disappears.


Sent from my iPhone using Tapatalk

 

[Pheran]

This threes made my head hurt. iSCSI with 4GB of ram and then using all available space for the vDev. Using that config for anything more important than snapchat is asking for trouble.

Really it sounds like just using a Windows server box would be better and use less power. Get 8GB of ram and run a cifs share and at least it won't be an accident waiting to happen with FreeNAS. I think open filer can run on 4 GB of ram but I maybe wrong. I hope you don't the blame when this data disappears.

I have to agree with maglin, in this broken setup I don't see that FreeNAS is buying you anything at all. You might as well just back up all the data, install the new 1TB drives right onto the Windows machine that's doing the sharing, mirror them with software, and share out from there.

Or, at a minimum, get rid of iSCSI and do an SMB share straight from the FreeNAS box - but then you're still running FreeNAS on completely unsupported hardware.

 

[jgreco]

Yes, there are no ideal FreeNAS-oriented solutions here, but the OP inherited this situation.