Solved How much space do I need to run portsnap fetch extract?

Snurg said:
and use a real disk drive for building etc on my new BBB
Click to expand...
I would say it depends on what your building.
If just kernel rebuild a 32GB microSD card will work. It takes more that 16GB unless you slim it down.
For buildworld I would say use some other medium.
 
tobik@ said:
First what does df -h / say? How did you install the system? If this was a simple dd then make sure to run service growfs onestart to actually grow your filesystem to fit the card. I'm not sure if RaspBSD is configured to do this on its own.
Click to expand...

clawhammer said:
I did df -h

Filesystem_______Size_______Used____ Avail____Capacity_____Mounted on
/dev/mmcsd0s2a__1.7g_______1.7g ____-138m_____109%__________/
devfs___________1.0k_______1.0k______0B_______100%__________/dev
/dev/mmcsd0s1___50M________7.5M_____42M________15%__________/boot/efi
/dev/md0________48M________24K______44M________0%__________/temp
/dev/md1________14M________72K______13M________1%__________/var/log
/dev/md2________11M________12K______10M________0%__________/var/tmp


Why is this like this? I did what the tutorial said and DD the raspbsd.img onto the sd card. why isnt it letting all 32GB be available for use?
Click to expand...

It seems that:
  1. /usr/ports (where the ports tree is stored) is part of / (root filesystem).
  2. / is only 1.7 GB, but should be 32. Please, read tobik@'s comment carefully.
  3. The /dev/mdx filesystems are nearly empty and probably not being used.
So, this is why you're out of space. growfs!
 
You might want to post output to make sure my commands are right:
gpart show da0

growfs won't do squat if there is no where to grow. Partition has to be grown first.
That is my guess without more info.
 
Code: 
gpart show mmcsd0
63                61120449 mmc2d0     MBR                      (29G)
63                102375     1        !12    [active]          (50M)
102438            986              -  free -                   (493k)
103424            3704832    2        freebsd                  (1.8G)
3808256           57312256         -  free  -                  (27G)

gpart resize -i s -a 4k -s 26G mmcsd0
mmcsd0s2 resized

gpart show mmcsd0
63                 61120449      mmc2d0        MBR                      (29G)
63                 102375            1          !12    [active]         (50M)
102438             986                       -  free  -                 (493k)
103424             54525952          2          freebsd                 (26G)
54629376           6491136                   -  free  -                 (3.1G)

Thanks for everyones help in understanding this.
 
Nevermind. now when I run pkg-static update I get a /: write failed filesystem is full. and then it gives a sqlite error while insert or replace into packages. I do a pkg-static cleanand it says nothing to do.

When I do a growfs /dev/mmcsd0s2a it says growfs: requested size 1.8GB is not larger than the current filesystem size 1.8GB.
 
I did exactly that.

Code: 
growfs -s 54525952 /dev/mmcsd0s2a
growfs: requested size 26GB is larger than the available 1.8GB

It also said I need to change the label is bsdlabel but it keep getting command not found.
 
You apparently forgot to reload the partition table (in doubt, just reboot to do this), so it is clear that the growfs command failed.
 
Then maybe the partition size change didn't get written to the "disk" for some reason.
Can you please re-check gpart show?
 
I think he wrote to wrong index. Unsure though. I do notice /boot/EFI in fstab so that would mean the partition table is different than armv6/7.

"mmcsd0s2 resized"
That line on my Arm v6/7 read's "mmcsd0s2a resized".

So maybe his slice layout is different with aarch64 and EFI.
Probably on RPi3 I guess.
 
clawhammer said:
But how would my system be full? I just did a fresh install on a 32gb sdcard and this is the first thing im installing.
Click to expand...

Well....

Code: 
unicron:/usr/ports/editors/emacs-devel $ make all-depends-list | wc -l
     322
That would sure do the trick. Amongst those dependency ports are even parts of X11.
 
Snurg said:
Then maybe the partition size change didn't get written to the "disk" for some reason.
Can you please re-check gpart show?
Click to expand...
Code: 
gpart show
=>63              61120449    mmcsd0    MBR                  (29G)
  63              102375          1     !12    [active]      (50M)
  102438          986                   - free -             ( 493k )
  103424          54525952        2     freebsd              ( 26G )
  54629376        6491136               - free -             ( 3.1G )



=>        0      54525952    mmcsd0s2    BSD           ( 26G )
          0       3704704         1      freebsd-ufs   ( 1.86G )
    3704704      50821248                - free -      ( 24G )
 
ShelLuser said:
Well....

Code: 
unicron:/usr/ports/editors/emacs-devel $ make all-depends-list | wc -l
     322
That would sure do the trick. Amongst those dependency ports are even parts of X11.
Click to expand...
Since the Emacs pkg install failed because of space did the things it installed before it became full get removed or do I need to go back and uninstall those?
 
Phishfry said:
Pi3 might even use GPT.
Look at the layout with file -s /dev/mmcsd0
Click to expand...
Code: 
file -s /dev/mmcsd0
/dev/mmcsd0: DOS/MBR boot sector; partition 1 : ID=0xc, active, start-CHS (0x0,1,1), end-CH5 (0x6,95,63), startsector 63, 102375 sectors; partition 2 : ID-0xa5, start-CHS (0x6,111,42), end-CH5 (ox3ff,255,63), startsector 103424, 54525952 sectors
 
Code: 
growfs mmcsd0s2
It's strongly recommended to make a backup before growing the file system. OK to grow filesystem on/dev/mmcsd0s2 from 1.8GB to 29GB [yes/no] yes
growfs: /dev/mmcsd0s2: Operation not permitted
 
This is consistent with output of Post #29, it's MBR.
Please do gpart show mmcsd0 again to verify that the resized MBR partition has actually been written to the "disk".
If it is, you indeed might need to use bsdlabel to fix it (but I am not sure whether this is really necessary. On the other hand, bsd label seems to contain size information, so this seems plausible to me).
Or just delete it and re-create with correct size.
 
You must log in or register to reply here.
Back
Top