# Database Problems

**URL:** https://forum.syncthing.net/t/database-problems/3126
**Category:** Support
**Created:** [June 26, 2015, 7:35pm UTC](https://forum.syncthing.net/t/database-problems/3126 "2015-06-26T19:35:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![sez11a](https://forum.syncthing.net/user_avatar/forum.syncthing.net/sez11a/32/968_2.png) [@sez11a](https://forum.syncthing.net/u/sez11a)
#### Post date: [June 26, 2015, 7:35pm UTC](https://forum.syncthing.net/t/database-problems/3126/1 "2015-06-26T19:35:50Z")

</div>

Here’s an interesting issue we just had. Names changed to protect the innocent. 😄

Let’s say we have three folders: files, documents, and stuff. 8 People are sharing them, and we want to add two more, but we only want to share documents. What happens instead is that one of the 8 shares all three with the two new people, and one of the new people nests the folders like this:

```
documents
     stuff 
         files

```

What’s worse, is this person drops 300,000 small files (source code) into files, which adds them to both stuff and documents on everybody else’s machine. What’s even worse, is that the person who shared the folders added him as an Introducer, which messed up everybody else’s machine.

What I’ve done so far is have everybody disconnect from this person until he can straighten out his directory structure. On my machine, I’ve deleted the folder structures that should not have synced. What I’m getting, however, is the puller stopping because of “no such file or directory” errors, since I deleted the offending files and now there’s no source for them.

Is there any way to fix this? Should I clear out the Syncthing database?

---

<div class="post-metadata">

### Author: ![sez11a](https://forum.syncthing.net/user_avatar/forum.syncthing.net/sez11a/32/968_2.png) [@sez11a](https://forum.syncthing.net/u/sez11a)
#### Post date: [June 27, 2015, 2:35am UTC](https://forum.syncthing.net/t/database-problems/3126/2 "2015-06-27T02:35:51Z")

</div>

On my node, I switched to the Boltdb version using the link from this thread:

> [@Beta test of Syncthing build with alternate database backend ("boltdb")](https://forum.syncthing.net/t/beta-test-of-syncthing-build-with-alternate-database-backend-boltdb/3070):
>
> @kahun, @Tom, any others seeing these weird corruption crashes - mind testing this snapshot? [http://build.syncthing.net/job/syncthing-bolt/](http://build.syncthing.net/job/syncthing-bolt/) It uses a different database backend, so if there’s a bug in that it ought to be fixed (per definition). If the root cause is still flaky hardware or so, you’ll probably experience some new, different funkiness… (Different database means full rescan on launch… Also means the normal database is untouched, so just reverting back to a vanilla 0.11.8 (or any …

It has fixed the issue. This tells me that if I had blown away my database, it also would have fixed the issue. I don’t, however, want to do that.

Is there any way to map the .ldb database file to the folder share, so I can just remove the file that goes with this messed up folder? That way I can get back on standard Syncthing without having to rebuild my entire database.

Thanks!

---

<div class="post-metadata">

### Author: ![AudriusButkevicius](https://forum.syncthing.net/user_avatar/forum.syncthing.net/audriusbutkevicius/32/277_2.png) [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [June 27, 2015, 8:07am UTC](https://forum.syncthing.net/t/database-problems/3126/3 "2015-06-27T08:07:06Z")

</div>

You can just remove the folder, restart, readd it, restart again.

One ldb file does not map into anything, as the whole set of files represent the database.

---

<div class="post-metadata">

### Author: ![system](https://forum-uploads.syncthingcdn.net/original/2X/0/0b50e0a202b22ae6a67190759e8c868805b8ed9f.png) [@system](https://forum.syncthing.net/u/system)
#### Post date: [May 12, 2017, 12:59pm UTC](https://forum.syncthing.net/t/database-problems/3126/4 "2017-05-12T12:59:03Z")

</div>


