[Hurb]

Moving on ...!

t3.medium 4GB instance worked fine... insanely fast.. built a lot of stuff, had some error to report but otherwise seemed great!

sudo cmake CMakeLists.txt in the server_source folder was a big task!



so now, wondering what to do and ignoring advice to just be patient and look, i tried to

sudo cmake CMakeLists.txt

in the server_source/zone folder

then

sudo make

threw the same error

admin@ip-x-x-x-x:/home/eqemu/server_source/zone$ sudo make
Scanning dependencies of target zone
[ 0%] Building CXX object CMakeFiles/zone.dir/aa.cpp.o
In file included from /home/eqemu/server_source/zone/aa.cpp:21:
/home/eqemu/server_source/zone/../common/eqemu_logsys.h:36:10: fatal error: fmt/format.h: No such file or directory
#include <fmt/format.h>
^~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/zone.dir/build.make:63: CMakeFiles/zone.dir/aa.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/zone.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

ill go check the "server" folder and "server_build" folders and related /bin to see ... if i see something new

... well sudo make in the server_build folder threw an error that i think is interesting

admin@ip-x-x-x-x:/home/eqemu/server_build$ ls
CMakeCache.txt Makefile client_files common libs queryserv submodules world
CMakeFiles bin cmake_install.cmake eqlaunch loginserver shared_memory ucs zone
admin@ip-x-x-x-x:/home/eqemu/server_build$ sudo make
[ 21%] Built target common
[ 22%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/class.cpp.o
[ 22%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/class_info.cpp.o
[ 22%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/class_registry.cpp.o
[ 22%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/class_rep.cpp.o
[ 22%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/create_class.cpp.o
[ 23%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/error.cpp.o
[ 23%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/exception_handler.cpp.o
[ 23%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/function.cpp.o
[ 23%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/inheritance.cpp.o
[ 23%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/link_compatibility.cpp.o
[ 24%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/object_rep.cpp.o
[ 24%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/open.cpp.o
[ 24%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/pcall.cpp.o
[ 24%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/scope.cpp.o
[ 24%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/stack_content_by_name.cpp.o
[ 24%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/weak_ref.cpp.o
[ 25%] Building CXX object libs/luabind/CMakeFiles/luabind.dir/src/wrapper_base.cpp.o
[ 25%] Linking CXX static library ../../bin/libluabind.a
[ 25%] Built target luabind
Scanning dependencies of target fmt
[ 26%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
/tmp/ccYumGUK.s: Assembler messages:
/tmp/ccYumGUK.s: Fatal error: can't close CMakeFiles/fmt.dir/src/format.cc.o: No space left on device
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

No space left on device?? cmon now .. i put 8 gb of storage space ... uh it cant be full... can it.. all i see is that its Up



well lets try sudo make in the zone folder..

admin@ip-x-x-x-x:/home/eqemu/server_build/zone$ ls
CMakeFiles Makefile cmake_install.cmake
admin@ip-x-x-x-x:/home/eqemu/server_build/zone$ sudo make
Scanning dependencies of target Detour
[ 1%] Building CXX object submodules/recastnavigation/Detour/CMakeFiles/Detour.dir/Source/DetourAlloc.cpp.o
[ 1%] Building CXX object submodules/recastnavigation/Detour/CMakeFiles/Detour.dir/Source/DetourAssert.cpp.o
[ 1%] Building CXX object submodules/recastnavigation/Detour/CMakeFiles/Detour.dir/Source/DetourCommon.cpp.o
[ 1%] Building CXX object submodules/recastnavigation/Detour/CMakeFiles/Detour.dir/Source/DetourNavMesh.cpp.o
[ 1%] Building CXX object submodules/recastnavigation/Detour/CMakeFiles/Detour.dir/Source/DetourNavMeshBuilder.cpp.o
[ 2%] Building CXX object submodules/recastnavigation/Detour/CMakeFiles/Detour.dir/Source/DetourNavMeshQuery.cpp.o
[ 2%] Building CXX object submodules/recastnavigation/Detour/CMakeFiles/Detour.dir/Source/DetourNode.cpp.o
[ 2%] Linking CXX static library libDetour.a
[ 2%] Built target Detour
[ 32%] Built target common
[ 38%] Built target luabind
[ 40%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
/tmp/ccZSaxx1.s: Assembler messages:
/tmp/ccZSaxx1.s: Fatal error: can't write 84 bytes to section .debug_loc of CMakeFiles/fmt.dir/src/format.cc.o: 'No space left on device'
/tmp/ccZSaxx1.s: Fatal error: can't close CMakeFiles/fmt.dir/src/format.cc.o: No space left on device
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

Ok, is my .. compiler needing to be updated or .. can't write 84 bytes... to a section... format.cc.o .. OK let's research this error after dinner ..

brother picking up pizza .. ok lets see what more "sudo make" does inside the server_build "world" and "queryserv" folders...

admin@ip-x-x-x-x:/home/eqemu/server_build/world$ ls
CMakeFiles Makefile cmake_install.cmake
admin@ip-x-x-x-x:/home/eqemu/server_build/world$ sudo make
[ 4%] Built target Detour
[ 53%] Built target common
[ 55%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
/tmp/ccU1FkX0.s: Assembler messages:
/tmp/ccU1FkX0.s: Fatal error: can't write 36 bytes to section .debug_loc of CMakeFiles/fmt.dir/src/format.cc.o: 'No space left on device'
/tmp/ccU1FkX0.s: Fatal error: can't close CMakeFiles/fmt.dir/src/format.cc.o: No space left on device
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
admin@ip-x-x-x-x:/home/eqemu/server_build/world$ cd ..
admin@ip-x-x-x-x:/home/eqemu/server_build$ ls
CMakeCache.txt Makefile client_files common libs queryserv submodules world
CMakeFiles bin cmake_install.cmake eqlaunch loginserver shared_memory ucs zone
admin@ip-x-x-x-x:/home/eqemu/server_build$ cd queryserv
admin@ip-x-x-x-x:/home/eqemu/server_build/queryserv$ sudo make
[ 5%] Built target Detour
[ 60%] Built target common
[ 63%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
/tmp/ccr3p4B2.s: Assembler messages:
/tmp/ccr3p4B2.s: Fatal error: can't write 36 bytes to section .debug_loc of CMakeFiles/fmt.dir/src/format.cc.o: 'No space left on device'
/tmp/ccr3p4B2.s: Fatal error: can't close CMakeFiles/fmt.dir/src/format.cc.o: No space left on device
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

ASSEMBLER MESSAGE:
Fatal error: can't write 36 bytes to section .debug_loc of CMakeFiles/fmt.dir/src/format.cc.o:
can't write 36 bytes to section .debug_loc of CMakeFiles/fmt.dir/src/format.cc.o: 'No space left on device

ok so the assembler is ... needing to be updated? or something hmm there definitely space on the device for 38 bytes... thats not what it means, that it needs more room really... assembler just being picky...?

and i think i dont need to run CMakeLists.txt outside of the main folders for server_build and server_source ... the subfolders clearly run in order as needed... im just curious ...

google says:

The partition containing the root folder (/) is 100% full. The root folder currently also contains the /tmp folder, which is used during compilation to store temporary files. As the root folder and with this the tmp folder is full, this fails.

To get around this either add more space, or reorganise the existing one.

As a workaround do

mkdir ~/tmp
export TMPDIR=~/tmp
and retry compilation.

hmmm but is amazon web service hogging space or something ..

admin@ip-x-x-x-x:/$ ls
bin dev home lib lib64 lost+found mnt proc run srv tmp var
boot etc install.sh lib32 libx32 media opt root sbin sys usr
admin@ip-x-x-x-x:/$ cd tmp
admin@ip-x-x-x-x:/tmp$ ls
systemd-private-024147cc0a3941908b4200ba562dad43-chrony.service-qrBrBs

admin@ip-x-x-x-x:/$ cd root
-bash: cd: root: Permission denied
admin@ip-x-x-x-x:/$ tree root
root [error opening dir]
0 directories, 0 files
admin@ip-x-x-x-x:/$ sudo tree root
root
0 directories, 0 files

that shouldn't be causing an error...clearly other stuff compiled, way bigger stuff... over a few bytes... it must be the assembler somehow...? i need to check the disk space to eliminate that reason..

---

The next day:

Easily modified the SSD storage, can be done ANY time up to ... a massive amount... so I'll increase when needed but lets see if a mere 250 gb lets this process continue, or I'll find out it wont... and it was something else like the assembler after all? Or something else entirely.. let's google

These are not entirely unrelated but .. it appears there may be an issue to fix regarding sectioning file output/input correctly.. is it the hardware i'm using + the software i'm using + a line of code in the makefile? Seems complicated! Let's figure it out...

When building with MinGW x64 when compilling Importer/IFC/IFCReaderGen1_2x3.cpp I get error:

too many sections (6135
D:\Programming\tools\msys2\tmp\cccuSdER.s: Assembler messages:
D:\Programming\tools\msys2\tmp\cccuSdER.s: Fatal error: can't write 171 bytes to section .text of CMakeFiles/assimp.dir/Importer/ IFC/IFCReaderGen1_2x3.cpp.obj because: 'File too big'

To fix this I add -DCMAKE_CXX_FLAGS=-Wa,-mbig-obj to cmake call. https://github.com/assimp/assimp/issues/2067

I found this discussion about the issue: [stackoverflow] Object file has too many sections
Passing the option -mbig-obj to gas through GCC with -Wa allows GCC to build the object file but in return, highly increases the build time of the target (I would say by 2 or 3 minutes depending on the CPU of your machine).

-mbig-obj
On x86-64 PE/COFF target this option forces the use of big object file format, which allows more than 32768 sections.

This patch solves the issue https://github.com/google/googletest/issues/1841

Welp, the storage device is almost updated to 500 gb, that alone shouldn't fix the issue if its related to a line in the makefile.txt ...? related to file sectioning ... however people say Linux x64 doesn't HAVE such issue? i need to verify my builds/tools i guess to make sure.. when the SSD is up ill run the sudo make again to see the error again!~

Oh that's interesting, another error similar but not about bytes:

admin@ip-x-x-x-x:/home/eqemu/server_build$ sudo make
[ 21%] Built target common
[ 25%] Built target luabind
[ 26%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
In file included from /home/eqemu/server_source/submodules/fmt/include/fmt/forma t.h:60,
from /home/eqemu/server_source/submodules/fmt/include/fmt/forma t-inl.h:11,
from /home/eqemu/server_source/submodules/fmt/src/format.cc:8:
/home/eqemu/server_source/submodules/fmt/src/format.cc:59:1: fatal error: error writing to /tmp/cc5bUaaU.s: No space left on device
FMT_END_NAMESPACE
^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CM akeFiles/fmt.dir/src/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] E rror 2
make: *** [Makefile:130: all] Error 2

fatal error: error writing to /tmp/cc5bUaaU.s: No space left on device

well, clearly this is related to the tmp folder ... kind of an easy fix, wouldn't that be nice??? lets see if it will fix that section byte error too?

https://unix.stackexchange.com/quest...-device/367318 “No space left on device” means that the disk is full. You need to make some space on the disk (partition) that contains /tmp, or more precisely on the filesystem that contains /tmp.

This has nothing to do with the content of the program (unless you managed to write a program that compiles to a multi-gigabyte binary).

Check where /tmp is located and how much space there is:

df /tmp
If /tmp is its own filesystem (it says /tmp in the “Mounted on” column) then check where the space is being used:

du /tmp | sort -n
Look at the directories at the end of the list. To see the biggest files in a directory, run e.g.

ls -lrS /tmp
If /tmp is on the root filesystem (it says / in the “Mounted on” column in the output of df /tmp) then you need to make some space on your disk. See How to understand what's taking up disk space?

Ok well lets see what that tells me about my system here

admin@ip-x-x-x-x:/$ df /tmp
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nvme0n1p1 8062380 8045680 0 100% /

admin@ip-x-x-x-x:/$ sudo du /tmp | sort -n
4 /tmp/.ICE-unix
4 /tmp/.Test-unix
4 /tmp/.X11-unix
4 /tmp/.XIM-unix
4 /tmp/.font-unix
4 /tmp/systemd-private-024147cc0a3941908b4200ba562dad43-chrony.service-qrBrBs/tmp
8 /tmp/systemd-private-024147cc0a3941908b4200ba562dad43-chrony.service-qrBrBs
32 /tmp

admin@ip-x-x-x-x:/$ ls -lrS /tmp
total 4
drwx------ 3 root root 4096 Nov 13 05:06 systemd-private-024147cc0a3941908b4200ba562dad43-chrony.service-qrBrBs

Ok well that's full somehow even though I just expanded it to 500gb overall the /tmp folder is full? or the file size sections were cause an error anyway and nothing I do will fix it? lets try to see..

clearly i can move stuff out of the tmp folder but ... to do it as the compile happens... im not Zero Cool

Ok so referring to this https://codedecoder.wordpress.com/20...eft-on-device/

Since the error clearing saying that No space left on device, I checked the space on server.

$df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 35G 6.1G 27G 19% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 1.9G 12K 1.9G 1% /dev
tmpfs 375M 304K 375M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1.9G 0 1.9G 0% /run/shm
none 100M 4.0K 100M 1% /run/user
overflow 1.0M 0 1.0M 0% /tmp
But I see there is a lot of space on the disk

Since, the error say problem while writing to tmp folder, I checked permission of temp folder, thinking may we it causing problem.

$ ls -l / | grep tmp
drwxrwxrwt 3 root root 4096 Nov 19 13:51 tmp
But it also showing all the permissions of read and write.

Then I tried to remove all the content of tmp folder thinking , may be something is there which taking all the space

$ rm -fr /tmp/*
But again got the same error.

Now googling for some time on space distribution and partitioning on linux, came to know about overflow partition .

And I got the problem, you can see that the in the df -h command output above, the tmp is mounted on overflow . This will happen if your server continuously keep writing to tmp folder, and if you have not given a separate partition to tmp . When system deduct some partition or memory issue it automatically mount the tmp folder to overflow partition with size of 1 MB, so that things keep working. But there is no automatic reversal i,e bringing back the tmp to root partition.

Now this could be happened on our server over the time. We have consumed our disk space, system moved tmp folder to overflow, later on we free the space by deleting unused file or increasing space, thus having free space as shown above in df -h command. But tmp folder didn’t moved back from overflow partition and having size of 1 MB. Since amatch need more then 1 MB, it is failing with space issue.

So solution is simple, unmount the tmp folder and mount it again.

# umount /tmp
umount: /tmp: device is busy.
(In some cases useful info about processes that use
the device is found by lsof( or fuser(1))
You need to kill the process using tmp folder, get the list of those process, with below command:

# lsof /tmp
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Passenger 6730 root 13rW REG 0,23 0 14247683 /tmp/passenger
Kill the running process 6730 and try to unmount again.

# kill -9 6730
# umount /tmp
Mount tmp folder again and see the disk space again.

# mount -a
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 35G 6.1G 27G 19% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 1.9G 12K 1.9G 1% /dev
tmpfs 375M 308K 375M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1.9G 0 1.9G 0% /run/shm
none 100M 4.0K 100M 1% /run/user
You can see that, there is no separate overflow partition for tmp folder as it now mounted on the root partition, thus it can use all the available memory in the main partition.

This time amatch didn’t reported any issue and installed successfully.

CHECKLIST IF YOU FACE THIS PROBLEM:

Check permission of folder
Check available space.Free space and see if solve your problem
If on overflow partition unmount and mount it again.
Resources:
http://unix.stackexchange.com/questi...ce-is-busy-why
http://www.tldp.org/LDP/intro-linux/...ect_03_01.html

I am going to issue commands as above and see what i learn.. my problem seems to be related to: increasing the disk size from the meager 8gb to 500gb and not unmounting/mounting the tmp folder... perhaps... but really..

isn't my issue still the system only partitioning 8gb of the new disk space? that's the issue isn't it ..

After resizing the logical volume, i still need to resize the contained filesystem.. possibly with some alterations

admin@ip-x-x-x-x:/$ ls -lrS /tmp
total 4
drwx------ 3 root root 4096 Nov 13 05:06 systemd-private-024147cc0a3941908b4200ba562dad43-chrony.service-qrBrBs
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nvme0n1p1 8062380 8045680 0 100% /

admin@ip-x-x-x-x:/$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 389M 5.3M 384M 2% /run
/dev/nvme0n1p1 7.7G 7.7G 0 100% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/nvme0n1p15 124M 278K 124M 1% /boot/efi
tmpfs 389M 0 389M 0% /run/user/1000

admin@ip-x-x-x-x:/$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 500G 0 disk
├─nvme0n1p1 259:1 0 7.9G 0 part /
├─nvme0n1p14 259:2 0 3M 0 part
└─nvme0n1p15 259:3 0 124M 0 part /boot/efi

admin@ip-x-x-x-x:/$ sudo fdisk -l
GPT PMBR size mismatch (16777215 != 1048575999) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/nvme0n1: 500 GiB, 536870912000 bytes, 1048576000 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 56507B41-5D22-1349-81AD-C628BA074922

Device Start End Sectors Size Type
/dev/nvme0n1p1 262144 16777182 16515039 7.9G Linux filesystem
/dev/nvme0n1p14 2048 8191 6144 3M BIOS boot
/dev/nvme0n1p15 8192 262143 253952 124M EFI System

Partition table entries are not in disk order.

admin@ip-x-x-x-x:/$ cat /etc/fstab
# /etc/fstab: static file system information
UUID=5db68868-2d70-449f-8b1d-f3c769ec01c7 / ext4 rw,discard,errors=remount-ro,x-systemd.growfs 0 1
UUID=72C9-F191 /boot/efi vfat defaults 0 0

SOLUTION:
https://aws.amazon.com/premiumsuppor...size-increase/

To avoid a No space left on the block device error, mount the temporary file system tmpfs to the /tmp mount point. This creates a 10 M tmpfs mounted to /tmp.

$ sudo mount -o size=10M,rw,nodev,nosuid -t tmpfs tmpfs /tmp

Run the growpart command to grow the size of the root partition or partition 1. Replace /dev/nvme0n1 with your root partition.

$ sudo growpart /dev/nvme0n1 1

admin@ip-x-x-x-x:/$ sudo mount -o size=10M,rw,nodev,nosuid -t tmpfs tmpfs /tmp

admin@ip-x-x-x-x:/$ sudo growpart /dev/nvme0n1 1
CHANGED: partition=1 start=262144 old: size=16515039 end=16777183 new: size=1048313823,end=1048575967

admin@ip-x-x-x-x:/$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 500G 0 disk
├─nvme0n1p1 259:1 0 499.9G 0 part /
├─nvme0n1p14 259:2 0 3M 0 part
└─nvme0n1p15 259:3 0 124M 0 part /boot/efi

let's sudo make on the server_build and seee....

admin@ip-x-x-x-x:/home/eqemu/server_build$ sudo make
[ 21%] Built target common
[ 25%] Built target luabind
[ 26%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
In file included from /home/eqemu/server_source/submodules/fmt/include/fmt/format.h:60,
from /home/eqemu/server_source/submodules/fmt/include/fmt/format-inl.h:11,
from /home/eqemu/server_source/submodules/fmt/src/format.cc:8:
/home/eqemu/server_source/submodules/fmt/src/format.cc:59:1: fatal error: error writing to /tmp/cc 9VW80Y.s: No space left on device
FMT_END_NAMESPACE
^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CMakeFiles/fmt.dir/s rc/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

ok so .. maybe... there is something thats not providing the space needed during the build, but .. didn't i give it room

need some increased size from 512 bytes? or am i just going overboard and missing something entirely... likeley so!

um what if i do 100M chunks instead of 10M in the temporary space..

$ sudo mount -o size=100M,rw,nodev,nosuid -t tmpfs tmpfs /tmp

well that changed something didn't it?? is 100M not enough either or am i going wrong way again ...

admin@ip-x-x-x-x:/home/eqemu/server_build$ sudo make
[ 21%] Built target common
[ 25%] Built target luabind
[ 26%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
/tmp/ccR36wdX.s: Assembler messages:
/tmp/ccR36wdX.s: Fatal error: can't write 3920 bytes to section .debug_info of CMakeFiles/fmt.dir/src/format.cc.o: 'No space left on device'
/tmp/ccR36wdX.s: Fatal error: can't close CMakeFiles/fmt.dir/src/format.cc.o: No space left on device
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

so ill give it 750M for a virtual tmp expansion... and see what happens...

admin@ip-x-x-x-x:/$ sudo mount -o size=750M,rw,nodev,nosuid -t tmpfs tmpfs /tmp
admin@ip-x-x-x-x:/$ cd home/eqemu/server_build
admin@ip-x-x-x-x:/home/eqemu/server_build$ sudo make
[ 21%] Built target common
[ 25%] Built target luabind
[ 26%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
/tmp/ccs27zIb.s: Assembler messages:
/tmp/ccs27zIb.s: Fatal error: can't write 3913 bytes to section .debug_info of CMakeFiles/fmt.dir/src/format.cc.o: 'No space left on device'
/tmp/ccs27zIb.s: Fatal error: can't close CMakeFiles/fmt.dir/src/format.cc.o: No space left on device
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

nope that didn't do it, but i think im getting close here... something is getting in the way, the script is fine the build would work ... IF ONLY .. X

and what happens now if i go to server_source and do a sudo make now?

admin@ip-x-x-x-x:/home/eqemu/server_source$ sudo make
[ 21%] Built target common
[ 25%] Built target luabind
[ 26%] Built target fmt
[ 33%] Built target uv_a
[ 39%] Built target uv
[ 45%] Built target zlibstatic
[ 52%] Built target zlib
[ 54%] Built target Recast
[ 56%] Built target Detour
[ 57%] Built target DetourTileCache
[ 57%] Built target DebugUtils
[ 58%] Built target DetourCrowd
[ 59%] Built target shared_memory
[ 65%] Built target world
zone/CMakeFiles/zone.dir/build.make:58: CMakeFiles/zone.dir/flags.make: No such file or directory
make[2]: *** No rule to make target 'CMakeFiles/zone.dir/flags.make'. Stop.
make[1]: *** [CMakeFiles/Makefile2:891: zone/CMakeFiles/zone.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

hmmm seems like a different issue

maybe i could launch a whole new Instance..

naw could do that anytime lets BREAK this or FIX it ...or both.. and use that knowledge for good?

lets do the umount /tmp .. sudo umount /tmp .. and then sudo mount -a ... then df -h

admin@ip-x-x-x-x:/$ sudo umount /tmp
admin@ip-x-x-x-x:/$ sudo mount -a
admin@ip-x-x-x-x:/$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 389M 5.3M 384M 2% /run
/dev/nvme0n1p1 7.7G 7.7G 0 100% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/nvme0n1p15 124M 278K 124M 1% /boot/efi
tmpfs 389M 0 389M 0% /run/user/1000
tmpfs 100M 0 100M 0% /tmp

well thats different but .. did i just change it for the better , worse, or halfway to either .. i forgot to df -h after i did the partition increase and added the 750M tmpfs.. ug oops.. well at least i "know" how to google a bit...

hey this is different now than when i issued these commands before ... now after volume allocated and partition expanded to size ... this is good i think? or just... data to consider..

admin@ip-x-x-x-x:/$ sudo du /tmp | sort -n
0 /tmp
admin@ip-x-x-x-x:/$ df /tmp
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 102400 0 102400 0% /tmp

kinda think im ok on space, but still need to see why things are going wrong

.. something else is happening when i sudo make in server_source...

is there an issue inside the make file? and not something i can fix with system changes...

[ 65%] Built target world
zone/CMakeFiles/zone.dir/build.make:58: CMakeFiles/zone.dir/flags.make: No such file or directory
make[2]: *** No rule to make target 'CMakeFiles/zone.dir/flags.make'. Stop.
make[1]: *** [CMakeFiles/Makefile2:891: zone/CMakeFiles/zone.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

ok well what if we try and sudo make in the server_build/zone directory itself ..

[ 40%] Building CXX object submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o
/tmp/ccrgv4do.s: Assembler messages:
/tmp/ccrgv4do.s: Fatal error: can't write 3920 bytes to section .debug_info of CMakeFiles/fmt.dir/src/format.cc.o: 'No space left on device'
/tmp/ccrgv4do.s: Fatal error: can't close CMakeFiles/fmt.dir/src/format.cc.o: No space left on device
make[2]: *** [submodules/fmt/CMakeFiles/fmt.dir/build.make:63: submodules/fmt/CMakeFiles/fmt.dir/src/format.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:219: submodules/fmt/CMakeFiles/fmt.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

ok so its STILL mad at space and wont complete the task which probably included making the right directory needed? hmmm ... instead of not writing 30 - 84 bytes, now it cant write 3920 bytes ...?

oooh i feel like the answer is here.

uuuh i forgot to really read that last df -h ... this doesn't seem like there is an improvement in space after all ? /dev/nvme0n1p1 7.7G 7.7G 0 100%

admin@ip-x-x-x-x:/$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 389M 5.3M 384M 2% /run
/dev/nvme0n1p1 7.7G 7.7G 0 100% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/nvme0n1p15 124M 278K 124M 1% /boot/efi
tmpfs 389M 0 389M 0% /run/user/1000
tmpfs 100M 0 100M 0% /tmp

so i need to increase that particular partition... i thought i did .. oh wait i did the root partition not nvme0n1p1 .. i thought 1 was that partition and i told it to expand to the 500gb?

sudo growpart /dev/nvme0n1 1

so .. i also need to growpart /dev/nvme0n1p1 ? something needs to increase there... maybe i run install.sh again?

also ..regarding allocation of inodes ...here is a sudo df -i /

admin@ip-x-x-x-x:/$ sudo df -i /
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/nvme0n1p1 516096 98665 417431 20% /

ok i did the part where i increased the thing inside the other thing ...

previous:

admin@ip-x-x-x-x:/$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs tmpfs 389M 5.3M 384M 2% /run
/dev/nvme0n1p1 ext4 7.7G 7.7G 0 100% /
tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/nvme0n1p15 vfat 124M 278K 124M 1% /boot/efi
tmpfs tmpfs 389M 0 389M 0% /run/user/1000
tmpfs tmpfs 100M 0 100M 0% /tmp
admin@ip-x-x-x-x:/$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 500G 0 disk
├─nvme0n1p1 259:1 0 499.9G 0 part /
├─nvme0n1p14 259:2 0 3M 0 part
└─nvme0n1p15 259:3 0 124M 0 part /boot/efi

admin@ip-x-x-x-x:/$ sudo resize2fs /dev/nvme0n1p1
resize2fs 1.44.5 (15-Dec-201
Filesystem at /dev/nvme0n1p1 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 63
The filesystem on /dev/nvme0n1p1 is now 131039227 (4k) blocks long.

now:

admin@ip-x-x-x-x:/$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs tmpfs 389M 5.3M 384M 2% /run
/dev/nvme0n1p1 ext4 492G 7.8G 465G 2% /
tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/nvme0n1p15 vfat 124M 278K 124M 1% /boot/efi
tmpfs tmpfs 389M 0 389M 0% /run/user/1000
tmpfs tmpfs 100M 0 100M 0% /tmp

admin@ip-x-x-x-x:/$ sudo df -i /
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/nvme0n1p1 32759808 98665 32661143 1% /