Free Space on /

[Rand]

Hey,

after having some space issues i've installed several times the last days and always saw the same (correct behaviour according to doc);
2x1 GB partition are created on the installation target regardless of total device size (tried 2-16GB), thats why 2GB is the minimum required size.

My issue is with the actual installation size - after a default installation only 26972 bytes remain on /.

Is it ensured that nothing can write to / (unless i remount rw); at least since moving all stuff to .system on a pool?

In my instance i found a smb.core on / which effectively killed my system and i'd rather not have that experience again...

Is there any way to enlarge that partition? Any plans to change partition sizes? I guess most ppl nowadays wouldn't mind using 3-4 GB to be on the safe side...

 

[cyberjock]

There's so little space on the device because the partition is so small. I asked about the partition size being expanded and the answer is "no... we have other plans in mind". So stay tuned, because you'll be blown away with 9.2.2 apparently.

 

[Rand]

Yeah i figured as much but wondered...
So whats the ETA for 9.2.2?

 

[cyberjock]

Yeah i figured as much but wondered...
So whats the ETA for 9.2.2?

There is no ETA at this time that I know of.

 

[Rand]

ok, so back to the question... anything running which can write to that filesystem if its mounted read only?
I mean the gui can to save config settings, what else can?

 

[pirateghost]

What exactly is the worry here? I don't understand. I have never had my USB drive die or fill up to the point it didn't boot

Sent from my Nexus 5

 

[cyberjock]

The GUI can because it's supposed to. You want to apply a tunable, sysctl, etc and the GUI will apply it to the USB stick.

I'm with pirateghost though. I really don't understand why you care. It's not a problem for 99.99% of users. If it were a problem they'd deal with it appropriately. This is a non-issue that you're convinced is an issue. It's a non-issue, so stop worrying about it. ;)

 

[Rand]

Well it happened to me once now and i want to be sure its not happening all the time.
So if there is little chance for it to happen then all the better.
It just caused me a lot of trouble (due to issues with various boot devices, installation, installation checksum and no idea what else) so i ws looking for reassurance its unlikely to happen all that often;)
Got that now as far i will get here so question closed, thanks :)

 

[Yatti420]

Don't use a 2GB stick.. I thought some weren't even big enough and caused problems..

 

[Rand]

It is large enough and had been working fine for 3 months before this happened (and its eUsb), i had nothing but issues with other devices ( kingston usb sticks, some old small ssds) so far, so not too keen on switching;)​

 

[cyberjock]

It is large enough and had been working fine for 3 months before this happened (and its eUsb), i had nothing but issues with other devices ( kingston usb sticks, some old small ssds) so far, so not too keen on switching;)​

Then you were doing something wrong.

If you RTFM it says not to use 2GB sticks. ;) Yatti is simply restating exactly what you should know and should have followed on day one. It may be fine, and it may not. But, you should be ruling out stupid little things like this BEFORE you come to the forum. Asking for help when you've already ignored our warnings isn't going to get you anywhere, and people will gladly never answer your posts again if you want to have that kind of behavior around here. ;)

So do yourself a favor and either listen to us or don't come here expecting us to restate everything you should already know.

 

[Rand]

I know, i read the manual.
It clearly states that a 4gb drivenis a recommendation not a requirement.The device i am using is large enough for the two partitions FreeNas is creating.
I have exactly the same amount of space left if i install on a 8Gb or 16Gb device.
If this was a business application it would be perfectly alright for me to use that 2gb device and still request support as i am not breaking requirements;) If you want to be right to bark at me for that change the docs to require 4gb instead of 2:)

On the other hand i fully understand your point and i tried;)I have no effing clue what the issue is with the three other devices i tried but that 2gb flash was the only reliable device i have at my disposal atm.
I am looking for some 4gb sticks but since the partition size is fixed they will have the same issue.

Unless o/c i have some issue with the way i am installing the system and that breaks every install i do.
So what is the official amount of free space after an installation of 9.2.1.2?
If its larger then the amount i stated i will gladly burn a cd and install from that to fix the issue

 

[cyberjock]

There's no "official" free space after install. It varies based on your configuration.

This is what mine says...

Code:

Filesystem                                                 1K-blocks        Used      Avail Capacity  Mounted on
/dev/ufs/FreeNASs2a                                           948903      611052     261938    70%    /
devfs                                                              1           1          0   100%    /dev
/dev/md0                                                        4663        3817        473    89%    /etc
/dev/md1                                                         823           2        755     0%    /mnt
/dev/md2                                                      152791       40081     100487    29%    /var
/dev/ufs/FreeNASs4                                             20263        4365      14277    23%    /data

Basically, if you aren't actually throwing files anywhere except your pool, you're doing everything right. FreeNAS is designed as an appliance setup. The USB stick is for the OS and it's single config file and that's it. As soon as you start doing things like installing software, adding drivers, or putting scripts on the USB partitions, you are taking major risks.

To be honest(and blunt) I'm clueless about this smb.core you claimed to have had a problem with. I've never heard of that file in my years on this forum, nor does that file exist for me. So I'm really confused and have to question if you are running a script on the system that has a problem, the box has been pwned due to some security problem, or something else. But I've never heard of an smb.core file. I've heard of smb.conf, and that's the CIFS settings file that's generated based on your GUI settings in FreeNAS. FreeNAS has had major problems(many revolve around smb.conf settings) in 9.2.1+. I'm still on 9.2.0 on purpose.... I don't want to deal with those problems and my system runs just fine right now.

 

[Rand]

Sorrymits probably not really named smb.core, it was a samba core file in /var/log/cores and i agree its probably from one of the issues with 9.2.1.2, maybe the 100% cpu issue i faced too.

I actually tried to use 9.2.0 but ran in to issues ( sth like zfs.ko depending on opensolaris.ko) probably b/c i got autoupdated to a current pool at some point in time.

Can i import a 9.2.1.2 configuration file into 9.2.0? Probably not...