docs(buffers): note known restart bugs in disk buffer docs

Author: pront

website/content/en/docs/architecture/buffering-model.md

@@ -122,7 +122,10 @@ detected, to give as accurate of a view into the number of events that were lost
 
 {{< warning >}}
 Disk buffers have some unique monitoring requirements compared to in-memory buffers,
-specifically around free storage space.
+specifically around free storage space. There are also [known bugs][disk_buffer_bugs] that can
+cause disk buffers to become unreadable after a restart, resulting in data loss.
+
+[disk_buffer_bugs]: https://github.com/vectordotdev/vector/issues?q=sort%3Aupdated-desc+is%3Aissue+state%3Aopen+label%3A%22domain%3A+buffers%22+type%3ABug
 {{< /warning >}}
 
 I/O errors are notoriously hard to recover from, as it can be difficult to know what data made it to
@@ -248,7 +251,8 @@ handle higher event processing rates.
 
 **Durability is the most important factor.**
 
-You should use disk buffers.
+You should use disk buffers, but be aware of the [known bugs][disk_buffer_bugs] before committing
+to them in production.
 
 Depending on your sources, you may be fine to keep the default blocking behavior, or you may wish to
 also drop events when the buffer is full. As mentioned above, some sources are receiving data from