[ALIX 2D13] 4GB image, loosing space here?



  • Hello,

    I probably should spare you with all the 'thank you for this fantastic pfSense dev & work" and so on…but I really enjoy this
    (ok, consider this done  ;) )

    Just want to know if I am doing something wrong here:
    I got this beautiful ALIX 2D13/4GB (cf) and flashed the pfSense-2.0-RELEASE-4g-i386-nanobsd.img
    But I see:

    Filesystem           Size    Used   Avail Capacity  Mounted on
    /dev/ufs/pfsense0    1.8G    548M    1.1G    32%    /
    devfs                1.0K    1.0K      0B   100%    /dev
    /dev/md0              38M    244K     35M     1%    /tmp
    /dev/md1              58M    7.8M     45M    15%    /var
    /dev/ufs/cf           49M    155K     45M     0%    /cf
    devfs                1.0K    1.0K      0B   100%    /var/dhcpd/dev
    

    Ahem…am I missing something here (swap?) or did I just lose about 2GB?  ???

    --> Pitty since I am enjoying freeBSD/pkg_add in order to add...well you probably don't want to know (a FW should remain a FW and nothing more, right?  ;) ) and during installation process, I often got 'seek failed' or 'filesystem is full' (which, I guess is a lie, cfr. the above df -h output ... :-\  )



  • When you install nanobsd, it creates 2 slices of equal size.  One slice is your boot slice and the other is a backup/upgrade slice.  So you'll always only see half the size of your cf card.



  • @onhel:

    When you install nanobsd, it creates 2 slices of equal size.  One slice is your boot slice and the other is a backup/upgrade slice.  So you'll always only see half the size of your cf card.

    Yes - just like onhel said. This feature has saved my "ass" a few times when I tryed alpha versions on my Alix. It's very easy to go back to the other working slice and try new firmware again later on. It's very usefull to have working backup ready to go when you do any changes to configurations.



  • Woah.
    How could I miss that in the documentation…
    Sorry about this.
    This is indeed very valuable and powerfull.

    What I can not really find is a way to avoid this (=use the whole CF for a single partition), just for tests purpose...



  • @blietaer:

    What I can not really find is a way to avoid this (=use the whole CF for a single partition), just for tests purpose…

    What sort of test?



  • I am glad you ask:
    This test.
    And Samba34.tbz is in the pipe.



  • Can't see any advantage to being able to use the whole disk to run some Asterix tests.

    I can understand why you might want to use the whole disk if you want to use the system as a SAMBA server. But if you want to use it as a SAMBA server are you sure the nanobsd build is the one you want? The nanobsd build is intended for use with disk devices with limited number of write cycles. Are you planning to use SAMBA as a "read only" file store?



  • Thank you very much for your concern here, you're right: the only reason I want more room is because, as explained above, during install (perl, vim, samba, asterisk, …) I could see messages about 'filesystem is full'.
    But, since 'df -h' suggests there still (at least) 1.2GB free, I do believe it is only during de-packaging (although I hardly believe any package is that big, even during installation of all dependencies candidates...right?)
    So this test is just to give a try...

    Samba would be redirected on a USB-drive share, with its own FS tuning (is UFS best for this?)



  • OK, so I found out indeed it is not the whole / partition that get full while (trying to) installing samba: it is most probably one of this weird mounted and bootly-refreshed /var or …?

    so my table here:

    Filesystem           Size    Used   Avail Capacity  Mounted on
    /dev/ufs/pfsense0    1.8G    548M    1.1G    32%    /
    devfs                1.0K    1.0K      0B   100%    /dev
    /dev/md0              38M    244K     35M     1%    /tmp
    /dev/md1              58M    7.8M     45M    15%    /var
    /dev/ufs/cf           49M    155K     45M     0%    /cf
    devfs                1.0K    1.0K      0B   100%    /var/dhcpd/dev
    

    I should find a way to inflate those tiny /var…

    ...but first I should understand what (where?) they are...
    this is not in pfSense ..is it freeBSD related?
    As linuxian, /dev/md* let me think of mdadm...thus I guess it is not (raid on CF? woah!)

    Any inputs?
    ???



  • md == memory disk. Some big packages use too much space in the md-mounted partitions, you just can't install those on embedded. Why you would want a file server on your firewall at all, much less one running from CF, is beyond me. Don't do it.


Locked