full disk space

GoogleGroups
1

Hello yall, sorry if i double post.
Could not find my first post before.

My beaglebone black /dev partition is almost full when having a fresh installation
Is 3.3/3.5GB full normal?

When trying to upgrade with "sudo apt-get upgrade"i get disk full errors

debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk1 179:0 0 3.6G 0 disk
└─mmcblk1p1 179:1 0 3.6G 0 part /
mmcblk1boot0 179:8 0 2M 1 disk
mmcblk1boot1 179:16 0 2M 1 disk
mmcblk1rpmb 179:24 0 128K 0 disk

debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 215M 0 215M 0% /dev
tmpfs 49M 5.5M 43M 12% /run
/dev/mmcblk1p1 3.5G 3.2G 116M 97% /
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 242M 0 242M 0% /sys/fs/cgroup
tmpfs 49M 4.0K 49M 1% /run/user/1000

Am i doing something wrong?
Erik

2

Hi Erik,

3

Hello Tarmo,

thanks for the reply, im a newby at linux. ill try to refer to it as root partition from now on.

I flashed the image found from the beaglebones website.https://beagleboard.org/latest-images

this one> Debian 9.5 2018-10-07 4GB SD IoT

Do you know any alternatives? more cleaner images?

Thanks in advance,
Erik

4

Erik:
Are you booting off the eMMc, or and SD card? If an SD card, how big is it? If it’s greater than 4G, you need to grow the partition on it. Try:

bone$ /opt/scripts/tools/grow_partition.sh

After rebooting you should see the whole SD card.

–Mark

5

From what i can see the image just takes up 96% of the entire disk.
The image determins the partition spaces, and is copied over to eMMc

The sd card i was using is 8GB, and could grow the partition on the sd card, but would like to use the eMMc for the partition(too many failed sd cards on the raspberry pi)
I just found it odd that the official image from beaglebone leaves 200mb free for the user. This means i cant even update it.

thanks for the reply, im learning allot about linux :slight_smile:

6

On Thu, 28 Feb 2019 03:15:15 -0800 (PST),
erikbozelie@gmail.com declaimed the
following:

debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk1 179:0 0 3.6G 0 disk
??mmcblk1p1 179:1 0 3.6G 0 part /
mmcblk1boot0 179:8 0 2M 1 disk
mmcblk1boot1 179:16 0 2M 1 disk
mmcblk1rpmb 179:24 0 128K 0 disk

debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 215M 0 215M 0% /dev
tmpfs 49M 5.5M 43M 12% /run
/dev/mmcblk1p1 3.5G 3.2G 116M 97% /
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 242M 0 242M 0% /sys/fs/cgroup
tmpfs 49M 4.0K 49M 1% /run/user/1000

Am i doing something wrong?

Well, the LXQT image I have installed shows

debian@beaglebone:~$ uname -a
Linux beaglebone 4.14.49-ti-r54 #1 SMP PREEMPT Fri Jun 15 22:14:13 UTC 2018
armv7l GNU/Linux
debian@beaglebone:~$

debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk1 179:0 0 3.7G 0 disk
+-mmcblk1p1 179:1 0 3.7G 0 part /
mmcblk1boot0 179:8 0 1M 1 disk
mmcblk1boot1 179:16 0 1M 1 disk
mmcblk1rpmb 179:24 0 128K 0 disk

debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 216M 0 216M 0% /dev
tmpfs 49M 5.2M 44M 11% /run
/dev/mmcblk1p1 3.6G 2.9G 455M 87% /
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 242M 0 242M 0% /sys/fs/cgroup
tmpfs 49M 0 49M 0% /run/user/1000
debian@beaglebone:~$

  I'd have expected the IoT build to have more free space than the LXQT.
After all, the compressed download IoT file is half the size of the
download LXQT file. I do note that my eMMC shows up as 3.7G, not 3.6G (so
there's 100M <G>).

  No problem running apt-get update/apt-get upgrade on this system.

  I've never tried flashing the eMMC using an expanded SD card. If that
is safe, I'd suggest writing the image to the SD card, expand the
partition, do the update/upgrade on the SD card, and THEN convert the card
to flash mode, to update the eMMC -- that might handle the situation where
the initial upgrade needs tons of files (the current cycle I'm running
fetched 102MB -- so upgrading often after the main upgrade may not pull as
many files).

7

Hi Erik,