Cleanup before Hashstore and migration to it

Node Operators
41

Here it is, can’t upload a txt-file:
– START
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-37-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Toshiba MG08ACA… Enterprise Capacity HDD
Device Model: TOSHIBA MG08ACA16TE
Serial Number:
LU WWN Device Id: 5 000039 c28c8b27a
Firmware Version: 0103
User Capacity: 16.000.900.661.248 bytes [16,0 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database 7.3/5319
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Sep 10 16:21:02 2025 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: (1456) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate PO-R-- 100 100 050 - 0
2 Throughput_Performance P-S— 100 100 050 - 0
3 Spin_Up_Time POS–K 100 100 001 - 7866
4 Start_Stop_Count -O–CK 100 100 000 - 67
5 Reallocated_Sector_Ct PO–CK 100 100 010 - 0
7 Seek_Error_Rate PO-R-- 100 100 050 - 0
8 Seek_Time_Performance P-S— 100 100 050 - 0
9 Power_On_Hours -O–CK 043 043 000 - 22854
10 Spin_Retry_Count PO–CK 100 100 030 - 0
12 Power_Cycle_Count -O–CK 100 100 000 - 67
23 Helium_Condition_Lower PO—K 100 100 075 - 0
24 Helium_Condition_Upper PO—K 100 100 075 - 0
191 G-Sense_Error_Rate -O–CK 100 100 000 - 0
192 Power-Off_Retract_Count -O–CK 100 100 000 - 34
193 Load_Cycle_Count -O–CK 100 100 000 - 78
194 Temperature_Celsius -O—K 100 100 000 - 34 (Min/Max 15/46)
196 Reallocated_Event_Count -O–CK 100 100 000 - 0
197 Current_Pending_Sector -O–CK 100 100 000 - 0
198 Offline_Uncorrectable ----CK 100 100 000 - 0
199 UDMA_CRC_Error_Count -O–CK 200 200 000 - 0
220 Disk_Shift -O---- 100 001 000 - 253624363
222 Loaded_Hours -O–CK 044 044 000 - 22786
223 Load_Retry_Count -O–CK 100 100 000 - 0
224 Load_Friction -O—K 100 100 000 - 0
226 Load-in_Time -OS–K 100 100 000 - 590
240 Head_Flying_Hours P----- 100 100 001 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 51 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x04 GPL,SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x08 GPL R/O 2 Power Conditions log
0x09 SL R/W 1 Selective self-test log
0x0c GPL R/O 513 Pending Defects log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x24 GPL R/O 53248 Current Device Internal Status Data log
0x25 GPL R/O 53248 Saved Device Internal Status Data log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version: 3
SCT Version (vendor specific): 1 (0x0001)
Device State: SMART Off-line Data Collection executing in background (4)
Current Temperature: 34 Celsius
Power Cycle Min/Max Temperature: 30/43 Celsius
Lifetime Min/Max Temperature: 15/46 Celsius
Specified Max Operating Temperature: 55 Celsius
Under/Over Temperature Limit Count: 0/0
Vendor specific:
00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 5/55 Celsius
Min/Max Temperature Limit: -40/70 Celsius
Temperature History Size (Index): 478 (245)

Index Estimated Time Temperature Celsius
246 2025-09-10 08:24 38 *******************
… ..( 35 skipped). .. *******************
282 2025-09-10 09:00 38 *******************
283 2025-09-10 09:01 37 ******************
284 2025-09-10 09:02 38 *******************
285 2025-09-10 09:03 37 ******************
… ..( 5 skipped). .. ******************
291 2025-09-10 09:09 37 ******************
292 2025-09-10 09:10 36 *****************
… ..( 22 skipped). .. *****************
315 2025-09-10 09:33 36 *****************
316 2025-09-10 09:34 35 ****************
… ..( 38 skipped). .. ****************
355 2025-09-10 10:13 35 ****************
356 2025-09-10 10:14 34 ***************
357 2025-09-10 10:15 35 ****************
358 2025-09-10 10:16 35 ****************
359 2025-09-10 10:17 34 ***************
… ..( 13 skipped). .. ***************
373 2025-09-10 10:31 34 ***************
374 2025-09-10 10:32 35 ****************
375 2025-09-10 10:33 34 ***************
… ..( 3 skipped). .. ***************
379 2025-09-10 10:37 34 ***************
380 2025-09-10 10:38 35 ****************
381 2025-09-10 10:39 34 ***************
382 2025-09-10 10:40 35 ****************
383 2025-09-10 10:41 35 ****************
384 2025-09-10 10:42 35 ****************
385 2025-09-10 10:43 34 ***************
… ..( 35 skipped). .. ***************
421 2025-09-10 11:19 34 ***************
422 2025-09-10 11:20 35 ****************
423 2025-09-10 11:21 34 ***************
424 2025-09-10 11:22 35 ****************
425 2025-09-10 11:23 34 ***************
… ..( 2 skipped). .. ***************
428 2025-09-10 11:26 34 ***************
429 2025-09-10 11:27 35 ****************
430 2025-09-10 11:28 34 ***************
431 2025-09-10 11:29 35 ****************
… ..( 4 skipped). .. ****************
436 2025-09-10 11:34 35 ****************
437 2025-09-10 11:35 34 ***************
… ..( 7 skipped). .. ***************
445 2025-09-10 11:43 34 ***************
446 2025-09-10 11:44 35 ****************
447 2025-09-10 11:45 34 ***************
448 2025-09-10 11:46 35 ****************
449 2025-09-10 11:47 34 ***************
… ..( 6 skipped). .. ***************
456 2025-09-10 11:54 34 ***************
457 2025-09-10 11:55 35 ****************
458 2025-09-10 11:56 34 ***************
… ..( 52 skipped). .. ***************
33 2025-09-10 12:49 34 ***************
34 2025-09-10 12:50 33 **************
35 2025-09-10 12:51 34 ***************
36 2025-09-10 12:52 33 **************
37 2025-09-10 12:53 34 ***************
38 2025-09-10 12:54 33 **************
39 2025-09-10 12:55 34 ***************
40 2025-09-10 12:56 34 ***************
41 2025-09-10 12:57 33 **************
… ..( 20 skipped). .. **************
62 2025-09-10 13:18 33 **************
63 2025-09-10 13:19 34 ***************
64 2025-09-10 13:20 33 **************
… ..( 8 skipped). .. **************
73 2025-09-10 13:29 33 **************
74 2025-09-10 13:30 34 ***************
… ..(148 skipped). .. ***************
223 2025-09-10 15:59 34 ***************
224 2025-09-10 16:00 35 ****************
225 2025-09-10 16:01 34 ***************
… ..( 7 skipped). .. ***************
233 2025-09-10 16:09 34 ***************
234 2025-09-10 16:10 35 ****************
235 2025-09-10 16:11 34 ***************
236 2025-09-10 16:12 35 ****************
… ..( 2 skipped). .. ****************
239 2025-09-10 16:15 35 ****************
240 2025-09-10 16:16 34 ***************
… ..( 4 skipped). .. ***************
245 2025-09-10 16:21 34 ***************

SCT Error Recovery Control:
Read: Disabled
Write: Disabled

Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 3) ==
0x01 0x008 4 67 — Lifetime Power-On Resets
0x01 0x010 4 22854 — Power-on Hours
0x01 0x018 6 229218971488 — Logical Sectors Written
0x01 0x020 6 3016825971 — Number of Write Commands
0x01 0x028 6 250377656354 — Logical Sectors Read
0x01 0x030 6 3462175140 — Number of Read Commands
0x01 0x038 6 82274400000 — Date and Time TimeStamp
0x02 ===== = = === == Free-Fall Statistics (rev 1) ==
0x02 0x010 4 0 — Overlimit Shock Events
0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
0x03 0x008 4 187 — Spindle Motor Power-on Hours
0x03 0x010 4 119 — Head Flying Hours
0x03 0x018 4 78 — Head Load Events
0x03 0x020 4 0 — Number of Reallocated Logical Sectors
0x03 0x028 4 73 — Read Recovery Attempts
0x03 0x030 4 0 — Number of Mechanical Start Failures
0x03 0x038 4 0 — Number of Realloc. Candidate Logical Sectors
0x03 0x040 4 34 — Number of High Priority Unload Events
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 0 — Number of Reported Uncorrectable Errors
0x04 0x010 4 0 — Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 34 — Current Temperature
0x05 0x010 1 35 N-- Average Short Term Temperature
0x05 0x018 1 35 N-- Average Long Term Temperature
0x05 0x020 1 46 — Highest Temperature
0x05 0x028 1 15 — Lowest Temperature
0x05 0x030 1 43 N-- Highest Average Short Term Temperature
0x05 0x038 1 25 N-- Lowest Average Short Term Temperature
0x05 0x040 1 38 N-- Highest Average Long Term Temperature
0x05 0x048 1 28 N-- Lowest Average Long Term Temperature
0x05 0x050 4 0 — Time in Over-Temperature
0x05 0x058 1 55 — Specified Maximum Operating Temperature
0x05 0x060 4 0 — Time in Under-Temperature
0x05 0x068 1 5 — Specified Minimum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 487 — Number of Hardware Resets
0x06 0x010 4 59 — Number of ASR Events
0x06 0x018 4 0 — Number of Interface CRC Errors
0x07 ===== = = === == Solid State Device Statistics (rev 1) ==
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value

Pending Defects log (GP Log 0x0c)
No Defects Logged

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 4 0 Command failed due to ICRC error
0x0002 4 0 R_ERR response for data FIS
0x0003 4 0 R_ERR response for device-to-host data FIS
0x0004 4 0 R_ERR response for host-to-device data FIS
0x0005 4 0 R_ERR response for non-data FIS
0x0006 4 0 R_ERR response for device-to-host non-data FIS
0x0007 4 0 R_ERR response for host-to-device non-data FIS
0x0008 4 0 Device-to-host non-data FIS retries
0x0009 4 20 Transition from drive PhyRdy to drive PhyNRdy
0x000a 4 20 Device-to-host register FISes sent due to a COMRESET
0x000b 4 0 CRC errors within host-to-device FIS
0x000d 4 0 Non-CRC errors within host-to-device FIS
0x000f 4 0 R_ERR response for host-to-device data FIS, CRC
0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC
– END

42

Looks like the drive is resetting itself, check power cables. D(evice)R(ea)DY (5th line in first screenshot) +

0x0009 4 20 Transition from drive PhyRdy to drive PhyNRdy
0x000a 4 20 Device-to-host register FISes sent due to a COMRESET
43

Typical interaction with an assistant.

— look at the logs, identify symptoms, work step by step, figure out root cause, provide justification.
— A is broken becuse B!!
— No, this is incorrect, because C and D
— you are absolutely correct. My initial assessment ignored C and D. Actual reason is F and G.
— No, F is is not a factor because X, see line 17.
— you are absolutely correct. I apologize for repeatedly providing incorrect information. Here is final answer: its Z becuse of X.
— it cannot be X, this system does not have X, as evidenced by line 6 in the log.
— you are absolutely correct, it must be frustrating to repeatedly get misleading advice having provided full information. Here is final correct answer
— …. Ah, forget it.

:person_facepalming:

You totally can use them. You just can’t agree with the indeterminate number of first things it tells you; you must be the one with the domain knowledge. It will lie to you, beсause of some unknown metrics it’s trying to optimize. They are not smart. Not yet. In other words, use AI for tasks you could have done yourself but can’t be arsed to. The productivity boost is expected to come from replacing slow “doing” with faster “verifying”.

44

WOW i had very similar messages recently.

HDD failure, partial file loss, a way to trigger an audit/repair? - Node Operators - Storj Community Forum (official)

My problem was a faulty SATA power cable. Please check power cabling, interface cabling. If that doesn’t help then the power supply and controller card. You can also maybe move drives around in their cabling position. if the problem “migrates” to a new drive it’s the cables. If it stays on the drive then it could be the drive itself.

45

LOL - it feels like writing an essay over and over again with AI Models for more advanced troubleshooting :wink: I guess we won’t be out of work anytime soon afterall :rofl:

46

So, migration completed few days ago, and yet I have a bunch of stuck files in piecestore.

What do I do with them? They look to be from the same date, probably from when the migration started. Are they missed? Are they in limbo? I kept the migrate chore enabled for a few days, but it did nothing. These are the only files that are left.

root@storagenode-seven:/mnt/storagenode-seven/blobs # ls -alt **/*(.)
-rw-r--r--  1 storagenode  storagenode   131072 Sep  4 18:17 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/2c/4xpnzv2qbs6eoazkva5pr2ldf7cepmxf34i62s4u6kq5fbdd2q.sj1
-rw-r--r--  1 storagenode  storagenode  1048576 Sep  4 11:49 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/4e/2sszrjn2hsgbqunxtosbhgkh3n5dclmgrdnzzkrivmjwn5a2ua.sj1
-rw-r--r--  1 storagenode  storagenode  1048576 Sep  4 11:49 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/45/zo5f3prknk2f2xrzj6btijrczspzdpxfd6tjsgtknaf4z2f3hq.sj1
-rw-r--r--  1 storagenode  storagenode  1310720 Sep  4 10:42 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/cp/jozxyedsalempwqqwf6ryzfpqqj3hfchtvn6yh3pv7rh7ndrkq.sj1
-rw-r--r--  1 storagenode  storagenode  1048576 Sep  3 21:21 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/3t/r3kax4rk7ldenqommhol6wbb4qcft6nmzawlsnvpzlsplurxdq.sj1
-rw-r--r--  1 storagenode  storagenode   131072 Sep  3 20:36 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/ox/6vpng7w5sxxuazw7smp7wjzya3vpffoqozc7j4kfd7ooafcttq.sj1
-rw-r--r--  1 storagenode  storagenode   262144 Sep  3 19:52 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/qh/rvvwqk5umhrrou64sqgxzvj5brzposopqiqrrl2xoxo6burpma.sj1
-rw-r--r--  1 storagenode  storagenode  1048576 Sep  3 19:51 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/bd/wxn54cvohbx6oz3gg6uyhgyp6jtcomfxzgrds66xktnhm7dbea.sj1
-rw-r--r--  1 storagenode  storagenode  1441792 Sep  3 19:07 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/jq/lennipqtimp2nqhsqzfrowmkps7eu5yg5g57elj75okobj7e2q.sj1
-rw-r--r--  1 storagenode  storagenode  1179648 Sep  3 19:07 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/vh/ofxcezvzzl5f2aw3qjkajoorh4hlzsgzc3xoznnipjh2qhm4kq.sj1
-rw-r--r--  1 storagenode  storagenode   131072 Sep  3 18:51 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/oo/qwitspasfn5z36y5bekyjnjy5xruwjwttjvejnrvc6dw4xtuhq.sj1
-rw-r--r--  1 storagenode  storagenode   917504 Sep  3 18:37 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/fl/lmlngijrr32i2bi6mfjc5d7yhokzpyayj52pjg4q2snlgmtjaq.sj1
-rw-r--r--  1 storagenode  storagenode  2228224 Sep  3 18:37 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/ga/isokuix4wfu4xp6def335ctxfsxdkf7dp3u256gc6ejuayauha.sj1
-rw-r--r--  1 storagenode  storagenode   262144 Sep  3 17:51 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/kz/7zmsx2im3ket67l2qksz3ivbgw66yj347xx6vrwsjtqd5l3u6q.sj1
-rw-r--r--  1 storagenode  storagenode   131072 Sep  3 17:21 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/2f/ptoolbk6fv33bgi672bbtxbctotmf744snpu46irvlvbfnk4sa.sj1
-rw-r--r--  1 storagenode  storagenode   393216 Sep  3 17:06 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/r4/3dkmszfn62nralvmlm3z7czc6pmwzweirgvka6a4rmymeg4wfa.sj1
-rw-r--r--  1 storagenode  storagenode   655360 Sep  3 16:36 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/53/dtmvt7bws6sxczyj3tiuf5lpx3swa4ugf6hqgcc4wbdvu7mumq.sj1
-rw-r--r--  1 storagenode  storagenode   131072 Sep  3 16:06 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/zf/y4manhrv3ookxjcecsvqs2yokeinzp2w6rxtxtrtz6ti75mcpa.sj1
-rw-r--r--  1 storagenode  storagenode  1835008 Sep  3 15:51 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/fy/wxwf4jmfo76kfx43iqcw4nck5i63zsvngkba3b5z5mhpua6atq.sj1
-rw-r--r--  1 storagenode  storagenode   131072 Sep  3 15:36 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/o2/nlornpgt5x3vm5hwkvrcwi56mfa3bnt33o4cuczcenewg6d53a.sj1
-rw-r--r--  1 storagenode  storagenode   917504 Sep  3 15:21 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/bx/t4cani5tvycyg2qbuwnlp7tng3oexv7i7ldb6m5qpbixvrhnha.sj1
-rw-r--r--  1 storagenode  storagenode   655360 Sep  3 15:06 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/2k/nz36ifmn54g2aqkff2pw6pxwarhj5nyxx4crtix6v63utb6ina.sj1
-rw-r--r--  1 storagenode  storagenode   131072 Sep  3 15:06 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/pn/nqvylhfdn5prawcnkrbhk33njhvv3zi5mpfxfd2zx6upzzk7hq.sj1
-rw-r--r--  1 storagenode  storagenode   917504 Sep  3 15:06 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/pk/cm2vtggpi4f2zf4iqbpzbbb2x35wo2hefmentw2eqz66yjwsqq.sj1
-rw-r--r--  1 storagenode  storagenode   655360 Sep  3 14:51 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/4h/pp7mnz3ntsr3ysjo4z7ltmr3fshkdvlazbcr2dh46dwzdqdjcq.sj1
-rw-r--r--  1 storagenode  storagenode  1048576 Sep  3 14:06 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/5a/quboctgv5qbqfnt7dvrexmmkisu5zqvujddp2az54e6wtprmrq.sj1
-rw-r--r--  1 storagenode  storagenode   131072 Sep  3 12:45 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/d3/f37luo3uhdvyjylyrru7byvmitxrb6tznxzy7h223bg4djefcq.sj1
-rw-r--r--  1 storagenode  storagenode   917504 Sep  3 12:21 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/zu/venba5abotgftk6iughpmszohlnijaq763sgtapkrgbtbk64ka.sj1
-rw-r--r--  1 storagenode  storagenode  1310720 Sep  3 12:06 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/ld/vdzlg6lylppmvdidlr53w4kqjziiffc3knlqtry2kiknxmxtca.sj1
-rw-r--r--  1 storagenode  storagenode   655360 Sep  3 11:06 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/fs/rxwesj4fh2bmoq7kfhtgdehhqo6dn2lno67jnedoeyfppdz66q.sj1
-rw-r--r--  1 storagenode  storagenode   131072 Sep  3 10:51 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/mt/7qtajr737bmoutybq6znqcksxe3k7q3venovvjgixw4doagdgq.sj1
-rw-r--r--  1 storagenode  storagenode   917504 Sep  3 10:21 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/hi/tghg5hpdtqdk45blx5x2w7x4ycdngaxa474gsrcmp4fmzopxza.sj1
-rw-r--r--  1 storagenode  storagenode   262144 Sep  3 10:06 v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/lc/unfdakfp75zry5lago4nleviwgwqyekupz45szqr4jsm7o6x6a.sj1

The rest of directories are still in place albeit empty

root@storagenode-seven:/mnt/storagenode-seven/blobs # ls -d **/*(/) | wc -l'
    4100
47

I would just delete them. Delete everything in blobs, temp and trash. Often the trash folder is also filled with files. But make sure the migration is to 100% complete. In the info logs it must be statet enqueued for migration for all sattelites.

48

Don’t delete anything in trash. If an audit request comes for something that should have been in the trash (ie not “expired for complete deletion”) you’ll get a missed audit. Shouldn’t happen, but it’s not the first time. Let the node clean the trash completely on its own first.

49

My experience was 50-100 0-byte files randomly throughout each sat. I deleted them and the [2-7]* and [a-z]* folders as well. This also helps monitor if the node for some reason (hint: automated migration settings causing issues in the future..) starts using piecestore by mistake in the future :wink:

On a couple of nodes, that previously experienced hard power failures in the past, I’ve seen a few (5-10) corrupted piece files and also some files without extension. Those I’ve deleted as well - in the faith that ~100 files out of 30-50 million would neither hard my audit score or the network.

50

They also can generate a proper prompts for AI… :person_facepalming:

51

Yeah :slight_smile: And then you have to prompt-engieer the shit out of prompt generation, because they sometimes are carried away and transform your request into something else. (RooCode does it sometimes). It’s prompts all the way down..

52

I have a prompt to optimize my prompts.

53

Unfortunately even with hashstore there is a big amount of trash. Like 33%, 1/3, on one of my newer nodes.

grafik
grafik602×631 22.5 KB

But the trash get’t now paid right? As it is in the log files and can’t be distinguished apart from regular storage so easily.

54

:joy::rofl::joy::rofl::joy::rofl::joy::rofl::joy::joy::joy:

55

No. It is not paid, despite to use of any storage backend. I suspect that your node has a permanent issue with the trash, either because it’s failed any trash cleanup or/and any TTL worker, which may didn’t clean something due to a bad/limited setup.

57

It’s pure hashstore on a fast 2 TB SSD. The compaction does not clean enough. Are there some tweaks to increase the “compaction-rate”?

58

What you see is about right.
Almost 3 PB of data was removed from the network now in September.
What you see is about a third of the space being trash. Some of the nodes I see have over 30% of trash, combined about 15%, so it looks about right.
It will get deleted, but only after a retention period, which I believe is currently set to 14 days.
So give it a time.

59

Usually you should do nothing. Hashstore works better with the trash than piecestore.
However, if the migration is completed, you shouldn’t have anything in the trash subfolder what’s older than 7 days. Hashstore doesn’t use this folder anymore - trash is inside logs, but it doesn’t migrate the piecestore trash to hashstore.

60

zip
I believe is currently set to 14 days.

Alexey
older than 7 days.

So zip’s comment about the trash folder currently use 14 days retention is wrong?

61

For Piecestore which stores in /storage/trash/[SAT-ID]/[DATE], trash has a 7 day retention period, and gets purged on the 8th day.