Jail Size

[Yummiesttag]

I have 11.2 installed and the server is 80% full, so I was looking at what could be deleted and jails and releases are pretty big. Are they really those sizes or do they share data that makes it think there are two copies? All I have is plex installed and 350gb for just a plex install is a bit much right?

 

[SweetAndLow]

1. You should never share the root of your pool like this. You will destroy all the permission in your jails and destroy your jails in general. Especially over smb.
2. What the heck is using all the space for 'releases'? How many of the older releases do you have?
3. Plex jails can get pretty darn large if you enable the thumbnail feature. My plex jail is 104GB for example.

 

[Yummiesttag]

I had issues with getting sharing to work, a long time ago and that’s how it ended up and then worked.

I have all the releases saved from r2 of 11 it’s like 5-7 I think, but I thought they were saved on my drive the OS is installed on.

 

[SweetAndLow]

I had issues with getting sharing to work, a long time ago and that’s how it ended up and then worked.

I have all the releases saved from r2 of 11 it’s like 5-7 I think, but I thought they were saved on my drive the OS is installed on.

So you couldn't setup a network share correctly so you got it working by not setting it up correctly. I'm just saying you need to fix that, I'm surprised your jails still work.

Nothing is stored on your boot device, that is for the OS only and the system dataset if you configure it that way.

 

[Yummiesttag]

It’s worked perfectly fine for over a year but how would I go about correcting the issue?
Just removing my c share and keep plex and windows?

 

[Yummiesttag]

I deleted all the old boot environments and it's still huge.

 

[SweetAndLow]

snapshots? My 11.2 Release jail is 398MB

 

[Heracles]

Hi Yummies,

One thing to look at is the spaced used versus the space reserved. In each dataset, you can configure a minimum space to be reserved for that dataset (or dataset + children). When you do reserve space that way, the pool will indicate this space as used when it is not really.

Say you create a new dataset and reserve 500 Gig for it. It will be create empty (of course...) but still will use 500 Gig. If you remove the reservation, the used space will drop to 0 (or almost 0, every datasets use a few bits...).

Other than that, I have to agree that sharing the root of your pool is asking for trouble. It would be much safer to debug your shares. The root cause for your problems was probably simple file level ownership / permissions.

Good luck,

 

[Yummiesttag]

Just one

 

[Yummiesttag]

Hi Yummies,

One thing to look at is the spaced used versus the space reserved. In each dataset, you can configure a minimum space to be reserved for that dataset (or dataset + children). When you do reserve space that way, the pool will indicate this space as used when it is not really.

Say you create a new dataset and reserve 500 Gig for it. It will be create empty (of course...) but still will use 500 Gig. If you remove the reservation, the used space will drop to 0 (or almost 0, every datasets use a few bits...).

Other than that, I have to agree that sharing the root of your pool is asking for trouble. It would be much safer to debug your shares. The root cause for your problems was probably simple file level ownership / permissions.

Good luck,

Is the reserve to just keep it from maxing out the drive? And from what can tell it's set to unlimited but I can't seem to find where it would show what the current reserve is.

Could this be the reserve?

 

[Heracles]

Hi again,

Reserved space and Quotas are different. Reserved space is space that is... reserved, so no other can use it. As such, this space is guaranteed to be available to that dataset. It is a minimum space that this dataset is sure to have.

Quotas are maximums instead of minimum. A dataset will be prevented from using more space than this quotas, so as you said, it will not fill the drive.

From your screenshot, Plex is definitely a big user, with 1.58 TB of data. Your Windows share is next, with 610 Gb, or 0.61 TB. Just add these 2 and you have the 2.19 TB of space used over the pool. Everything else, including the jails, is not significant.

Either you clean up your Plex, your Windows share or go get more storage if you need everything you have as of now.

Adding more drives will allow for the creation of new vDevs or replacing your actual drives one at a time with bigger ones and re-silvering between each change will auto-expand your pool once the last drive will be activated.

 

[Yummiesttag]

Hi again,

Reserved space and Quotas are different. Reserved space is space that is... reserved, so no other can use it. As such, this space is guaranteed to be available to that dataset. It is a minimum space that this dataset is sure to have.

Quotas are maximums instead of minimum. A dataset will be prevented from using more space than this quotas, so as you said, it will not fill the drive.

From your screenshot, Plex is definitely a big user, with 1.58 TB of data. Your Windows share is next, with 610 Gb, or 0.61 TB. Just add these 2 and you have the 2.19 TB of space used over the pool. Everything else, including the jails, is not significant.

Either you clean up your Plex, your Windows share or go get more storage if you need everything you have as of now.

Adding more drives will allow for the creation of new vDevs or replacing your actual drives one at a time with bigger ones and re-silvering between each change will auto-expand your pool once the last drive will be activated.

Alright, I'll try and snag an easystore and shuck it once they go on sale. Thank you!