Fatal Error: Filename too long. #34592

1. 
   JPPinto-SS commented at 3:00 pm on February 14, 2026: none

   Is there an existing issue for this?

   • I have searched the existing issues

   Current behaviour

   Dir path cannot get any shorter but I think its misleading, there are no files even close to 256 char, might be an issue because its on E:\ ? Nothing useful in debug.log. Fix the data for core as well, it’s still showing 2009-2024.

   Expected behaviour

   Expected behavior is that it should continue to write the blocks.

   Steps to reproduce

   Install Bitcoin core 28.1.0.

   Relevant log output

   debug.zip

   How did you obtain Bitcoin Core

   Compiled from source

   What version of Bitcoin Core are you using?

   28.1.0

   Operating system and version

   Windows 10

   Machine specifications

   8core i7 16gb ram, 14TB ssd

2. 
   hebasto commented at 3:27 pm on February 14, 2026: member

   What version of Bitcoin Core are you using?

   28.1.0

   Operating system and version

   Windows 10

   Have you tried the most recent release v30.2?

3. willcl-ark added the label Windows on Feb 17, 2026
4. willcl-ark added the label Questions and Help on Feb 17, 2026
5. 
   maflcko commented at 12:28 pm on February 17, 2026: member

   Is this still an issue with a recent version of Bitcoin Core? If yes, what are the steps to reproduce? That is, what is your config + settings + command line args (etc). Also, what is the relevant section of the debug log? No need to zip it up, you can just share it here directly, possibly wrapped in a

   0<details><summary>debug log</summary>
   1
   2\```
   3 content
   4\```
   5
   6</details>
   

6. 
   JPPinto-SS commented at 3:42 pm on February 17, 2026: none

   I have installed 30.2 and its still synchronizing with network, it usually throws the error when there is ~1 year left to sync. I will report back if it completes or not.

7. 
   maflcko commented at 3:55 pm on February 17, 2026: member

   What is the filesystem? FAT32?

   I presume the exception comes from src/flatfile.cpp: fs::create_directories(path.parent_path());, which is confusing, because some errors are handled locally in the function and a failure is returned, and other errors are thrown.

8. 
   JPPinto-SS commented at 4:05 pm on February 17, 2026: none
9. maflcko removed the label Questions and Help on Feb 17, 2026
10. maflcko added the label Block storage on Feb 17, 2026
11. 
    maflcko commented at 8:06 am on February 23, 2026: member

    I have installed 30.2 and its still synchronizing with network, it usually throws the error when there is ~1 year left to sync. I will report back if it completes or not.

    Any update on this? Also, once the issue happens again, it should not be needed to re-sync from scratch and it should be possible to test if the same error message happens on every re-start.

12. 
    JPPinto-SS commented at 12:57 pm on February 23, 2026: none

    Its still going… no issues yet.

13. 
    maflcko commented at 11:52 am on March 2, 2026: member

    Well, but it looks like the last crash was for a block time of March 2024, but the last screenshot already shows a block time of June 2024, so it doesn’t seem to be deterministic?

    Maybe a cosmic ray or hardware corruption?

14. maflcko added the label Data corruption on Mar 2, 2026
15. 
    maflcko commented at 11:59 am on March 2, 2026: member

    14TB ssd

    Also, an 14TB external ssd seems a bit fragile to put the leveldb on. At a minimum, it will slow down the IBD.

    My recommendation would be to at most put the blocksdir on the external drive.

16. 
    willcl-ark commented at 8:18 pm on March 2, 2026: member

    Also, an 14TB external ssd seems a bit fragile to put the leveldb on. At a minimum, it will slow down the IBD.

    I presume this is actualy a spinning disk HDD too. In which case using it for chainstate will be doubly-dodgy.

    Should we close for now, seeing as this seems to not be reproducible? We can re-open if @JPPinto-SS reports another failure.

17. 
    JPPinto-SS commented at 11:35 pm on March 2, 2026: none

    Its still running, I did pull the USB as a test and to ensure it was on a 3.0 port. It resumed with no issues. Is there not a way to backfill the files? like via FTP? When I use this machine at all, it slows the download to a crawl.

    Current status:

18. 
    JPPinto-SS commented at 11:37 pm on March 2, 2026: none

    ok to close
19. JPPinto-SS closed this on Mar 2, 2026

    ---

Contributors
JPPinto-SS hebasto maflcko willcl-ark

Labels
Windows Block storage Data corruption