Single File DB - Stalls with 2TB left of data on lvm #3369
Replies: 3 comments 2 replies
-
I have a similar setup as well, with a primary 2TB (1.819 TiB) disk, and a secondary 1TB disk in my LVM volume group, so I will probably hit the threshold on my initial sync or slightly after. @JohnSweeney85 it's been 2 weeks. Do you have any ideas how to alleviate or have you already solved this? It's interesting your exporter or prometheus instance seemed to have stopped working periodically. Maybe it's because your volume group was not set up correctly? What does your lsblk/lvs/lvdisplay output? |
Beta Was this translation helpful? Give feedback.
-
Just want to chime in here to acknowledge that the issue has been seen. I am not super familiar with LVM, my understanding is that the database file would be split onto both drives by the OS, i.e. that it shouldn't matter to us if you're using LVM or not as from our POV it is just a file system. Is that not the case? |
Beta Was this translation helpful? Give feedback.
-
UPDATE: That was fake news. LVM works. Synced. Took quite a bit longer than expected, but works now. |
Beta Was this translation helpful? Give feedback.
-
I have a 1TB SSD and 2TB SSD in one Volume group on a single logical volume. Looks like it started saving the database file on the 1TB side and basically stalled at around 850GB.
Anyone have experience with this?
Is there a better strategy to create more disk space other than buying a single 5TB disk ?
Looks like it was allocating something to the other disk but not sure.
Beta Was this translation helpful? Give feedback.
All reactions