00:35:14 https://i.imgur.com/hU2Fi48.mp4 00:35:14 This is cool 12:49:38 no community meeting here today, next week. but there is a #monero-events:monero.social meeting at 18:00UTC 👍️ 13:12:20 If you're at FOSDEM feel free to ping or DM me 13:12:25 We're having a small meetup 15:56:24 here the monero community matrix room https://matrix.to/#/#monero-community:monero.social 15:57:07 * posted in the wrong room, sorry 16:24:11 it's true, HAL does have a bug 17:55:38 monerokon meeting in 5 minutes in #monero-events:monero.social 19:36:57 * Stnby[m] uploaded an image: (124KiB) < https://libera.ems.host/_matrix/media/v3/download/kernal.eu/yMGfZHkZspnzuKKhRMDaPvNX/PXL_20230204_193623183.MP.jpg > 19:36:58 Todays loot an FOSDEM 19:46:30 Those matrix t-shirts are cool 19:46:34 "Todays loot an FOSDEM" <- 50% of what you collected 19:47:02 Gamescom loot is on another level though 19:47:03 * Siren[m] uploaded an image: (123KiB) < https://libera.ems.host/_matrix/media/v3/download/kernal.eu/lZqhPnJaYqsTZWsHwhIFbrYI/PXL_20230204_194259751.MP_20230204204649.jpg > 19:47:49 monerobull[m]1: I got 4 beers and a baked potato last time 19:48:08 monerobull[m]1: I really tried them to accept Monero, sadly aint working 20:48:30 "PXL_20230204_193623183.MP.jpg" <- Curl stickers are pretty cool 20:53:08 I did not expect to see the Curl man there, they were advertising WolfSSL, just because how shit OpenSSL is 20:56:39 Wireguard 20:56:51 (or is this unrelated?) 21:29:40 I unmounted an external SSD with the block chain forgetting that monerod is running. 21:29:51 Now it says that DB is corrupted 21:31:10 --db-salvage doesn't seem to do anything 21:31:12 How can I forget last 100 blocks? 21:31:31 pop_blocks 100 21:45:42 I can't start the daemon because it fails to parse the DB and pop_blocks requires the daemon running 21:46:08 Are there any tools that operate directly on the DB? 21:47:54 Yes 21:49:20 ./monero-blockchain-import --pop-blocks 100 21:52:07 you will likely have to resync 21:52:20 or restore from backup if you have one 21:55:55 It looks like block chain import tries to start the daemon too and fails with "can't parse a blob" error 22:01:23 But there is like 149GiB of the valid data and only the recent one is corrupted. There should be a way to truncate the DB without resyncing everything. 22:06:13 so we cant start monerod at all hm 22:07:03 Don't worry, i can't start bitcoind either 22:07:09 lol 22:08:28 Or at least my ord.exe can't 22:08:34 Will have to fix that 22:10:58 esac212[m]: the db isn't sequential where you can just take the top away to remove corruption 22:15:41 https://github.com/monero-project/monero/blob/31bdf7bd113c2576fe579ef3a25a2d8fef419ffc/src/blockchain_db/lmdb/db_lmdb.cpp#L3092 22:15:41 But it looks like I can fix it by just truncating this range 22:28:10 like a reverse pruning 22:50:39 It looks like I actually need to find the first corrupted node then discard it and then discard all nodes that contain data about blocks which are not present in the valid part of the DB, and there are no tools to manipulate LMDB so this must be coded from scratch 🥴 22:56:25 https://github.com/kriszyp/lmdb-js 22:56:25 ? 22:56:29 fyi never tried it 23:05:53 did you check the mdb_* tools? not sure if they are helpful for what you want to do 23:49:21 Yep, maybe with combination of mdb_dump + mdb_load I can achieve this but I'm not sure. I will play with the BlockchainDB class first.