# File system write error, workspace layout reset, current file truncated to zero size

**URL:** <https://forum.obsidian.md/t/file-system-write-error-workspace-layout-reset-current-file-truncated-to-zero-size/22716>\
**Category:** Bug graveyard\
**Tags:** data-loss\
**Created:** [August 17, 2021, 1:05pm UTC](https://forum.obsidian.md/t/file-system-write-error-workspace-layout-reset-current-file-truncated-to-zero-size/22716 "2021-08-17T13:05:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarkDown](https://forum.obsidian.md/user_avatar/forum.obsidian.md/markdown/32/10585_2.png) [@MarkDown](https://forum.obsidian.md/u/MarkDown)\
**Post date:** [August 17, 2021, 1:05pm UTC](https://forum.obsidian.md/t/file-system-write-error-workspace-layout-reset-current-file-truncated-to-zero-size/22716/1 "2021-08-17T13:05:52Z")

</div>

### Steps to reproduce

Unfortunately, this was a singular occurrence so far. No repro steps available.

I was editing a file when I got an error message saying something like, writing to the file system is not possible. (I do not remember the exact wording.)

I chose to reload the workspace, and as a result, all open panes were closed and the custom workspace layout was gone. Restarting Obsidian completely did not help.

I then restored the `workspace` file from my Time Machine backup and started Obsidian. The layout was back but the document I edited last had zero bytes. Obsidian’s recovery feature helped restoring the contents.

### Expected result

No file system write errors.

### Actual result

File system write error, workspace file reset, currently edited file truncated to zero bytes.

### Environment

- Operating system: macOS 11.5.2

- Obsidian version: 0.12.12

I am aware that this info does not help much with tracking down a bug in Obsidian or a plugin, so my question would be, how to collect more info next time?

* * *

### Additional information

---

<div class="post-metadata">

**Author:** ![WhiteNoise](https://forum.obsidian.md/user_avatar/forum.obsidian.md/whitenoise/32/11_2.png) [@WhiteNoise](https://forum.obsidian.md/u/WhiteNoise)\
**Post date:** [August 17, 2021, 1:24pm UTC](https://forum.obsidian.md/t/file-system-write-error-workspace-layout-reset-current-file-truncated-to-zero-size/22716/2 "2021-08-17T13:24:09Z")

</div>

We are aware that there is an issue between macos and node.js fs api. Sometimes, it can get stuck. The error you saw is us trying to catch that situation and warn you.  
There’s not much we can do about it, other than point you to File Recovery plugin (and or whatever else you use) to recover your files.

---

<div class="post-metadata">

**Author:** ![WhiteNoise](https://forum.obsidian.md/user_avatar/forum.obsidian.md/whitenoise/32/11_2.png) [@WhiteNoise](https://forum.obsidian.md/u/WhiteNoise)\
**Post date:** [August 17, 2021, 1:25pm UTC](https://forum.obsidian.md/t/file-system-write-error-workspace-layout-reset-current-file-truncated-to-zero-size/22716/3 "2021-08-17T13:25:18Z")

</div>

> [@\[MacOS\]: Obsidian does not save and get stuck in a limbo state (failed to save - Timed out)](https://forum.obsidian.md/t/obsidian-does-not-save-and-get-stuck-in-a-limbo-state/18947):
>
> I just experienced this and lost several hours worth of writing. Here’s what happened: I committed my changes to a file called set-for-life-2 to Github via Github Desktop. I continued writing for about 2 hours in that file. With set-for-life-2 still open in Obsidian, I tried to open a different file (set-for-life) in Obsidian from the file tree. I clicked set-for-life and nothing happened. I CMD-clicked it and it opened in a new pane with “No File” or something like that in the title bar. I c…

---

<div class="post-metadata">

**Author:** ![MarkDown](https://forum.obsidian.md/user_avatar/forum.obsidian.md/markdown/32/10585_2.png) [@MarkDown](https://forum.obsidian.md/u/MarkDown)\
**Post date:** [August 17, 2021, 1:45pm UTC](https://forum.obsidian.md/t/file-system-write-error-workspace-layout-reset-current-file-truncated-to-zero-size/22716/4 "2021-08-17T13:45:57Z")

</div>

Thank you @WhiteNoise for the quick reply. Glad to hear that the issue is known. Yes, file recovery is an option here and it worked well for me! 👍

---

<div class="post-metadata">

**Author:** ![system](https://forum.obsidian.md/uploads/default/original/3X/b/e/bec35fbd23ab28909bb6bfe62cb32eb82dd34019.png) [@system](https://forum.obsidian.md/u/system)\
**Post date:** [August 18, 2021, 1:46pm UTC](https://forum.obsidian.md/t/file-system-write-error-workspace-layout-reset-current-file-truncated-to-zero-size/22716/5 "2021-08-18T13:46:01Z")

</div>

Closed on August 18, 2021, 1:46pm UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![WhiteNoise](https://forum.obsidian.md/user_avatar/forum.obsidian.md/whitenoise/32/11_2.png) [@WhiteNoise](https://forum.obsidian.md/u/WhiteNoise)\
**Post date:** [October 13, 2022, 4:07pm UTC](https://forum.obsidian.md/t/file-system-write-error-workspace-layout-reset-current-file-truncated-to-zero-size/22716/6 "2022-10-13T16:07:33Z")

</div>

Archived on October 13, 2022, 4:07pm UTC


