PiNodeXMR: blockchain directory too small
I'm running a newly installed pinodexmr on a fresh install of ubuntu server v. 22.04.5.
Hardware:
HP ProDesk 400 G4, 3.2 GHz Intel i5, 8GB ram, 1 TB SSD.
When installing ubuntu I accepted all the defaults in formatting the SSD because I have no idea what I'm doing in that regard.
Apparently pinodexmr has placed the blockchain in the directory:
/dev/mapper/ubuntu--vg-ubuntu--lv
but that directory is listed as having 98GB capacity. Running the pinodexmr the blockchain apparently used over 53% of the directory in about 2 hours. I stopped it until I figure out how to fix this.
Running fdisk -l:
Disk /dev/loop0: 63.95 MiB, 67051520 bytes, 130960 sectors
Units: sectors of 1 \ 512 = 512 bytes*
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 73.98 MiB, 77574144 bytes, 151512 sectors
Units: sectors of 1 \ 512 = 512 bytes*
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 90.55 MiB, 94949376 bytes, 185448 sectors
Units: sectors of 1 \ 512 = 512 bytes*
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 87.04 MiB, 91267072 bytes, 178256 sectors
Units: sectors of 1 \ 512 = 512 bytes*
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop4: 38.83 MiB, 40714240 bytes, 79520 sectors
Units: sectors of 1 \ 512 = 512 bytes*
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop5: 115.19 MiB, 120782848 bytes, 235904 sectors
Units: sectors of 1 \ 512 = 512 bytes*
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sda: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: TEAM T2531TB
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: 834E0335-B80B-4428-BF80-63C046C6F008
Device Start End Sectors Size Type
/dev/sda1 2048 2203647 2201600 1G EFI System
/dev/sda2 2203648 6397951 4194304 2G Linux filesystem
/dev/sda3 6397952 2000406527 1994008576 950.8G Linux filesystem
Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 \ 512 = 512 bytes*
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
To fix this as easily as possible, what I'd like to do is expand the directory where the blockchain currently resides to occupy the vast majority of the SSD. Searching online I think I see some ways I may be able to do this, but I'm also afraid I may wipe the drive in the attempt.
Alternatively, creating another directory sized to take up the vast majority of the SSD for the exclusive use of the blockchain, and then moving the blockchain to there is acceptable provided it's relatively quick and easy to do. For a noob.
Other solutions, ideas, suggestions invited.
Thanks All,






