ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop struggling with slow file I/O in Vagrant. Learn how to implement NFS synced folders on macOS and Linux to achieve near-native performance for your development environment.
Learn how to enable Vagrant NFS synced folders for faster host‑guest file synchronization, with a sample Vagrantfile, performance notes, and pitfalls to avoid.
Learn how to choose and configure Vagrant synced folders, comparing NFS, SMB, and VirtualBox shared folders to optimize I/O performance and security.
Goal: Determine whether an inotify watch placed on a directory mounted via NFS can reliably receive filesystem change events that occur on the NFS server or from other NFS clients. The VFS allows the inotify_add_watch system call to succeed on many network filesystems, but the NFS client does not implement remote change notification, so watches often fire ne
Goal: Ensure that Vagrant notifies users when the automatically selected synced folder implementation cannot be used because required host‑side dependencies (e.g., NFS client, SMB services) are absent, causing a silent fallback to VirtualBox shared folders and potential performance loss. Constraints: Vagrant’s built‑in selection chooses NFS on macOS/Linux, S
I'm transferring big files (78GB) through network, with NFS, but the transfer is finally limited to 6 Gbps (on a 2x10Gb NIC). I cannot find the bottleneck for now. Here my setup: 1 Server MB: Supermicro X10DRH-C (pcie 3.0), only one cpu NIC: 2 x 10Gb (intel X710-T2L) 64GB of DDR4 (2400Mhz) HBA: LSI 9311-8i => 2 mini SAS hd connected to SAS 12Gb backplane
The documented quota_rule capability sets mailbox size limits that Dovecot evaluates using file-system metadata. On a local ext4 volume the check is reliable and deliveries are rejected once the limit is reached. When the same mail directory is hosted on an NFS share the metadata can become stale or unsupported, causing the quota plugin to silently skip the
Context A development team uses Vagrant with VirtualBox across macOS, Linux, and Windows hosts. The project involves a codebase with many small files where I/O latency directly affects test suite runtime. VirtualBox shared folders work everywhere without extra setup but exhibit high latency on large directory trees. NFS delivers lower latency on Unix-like ho
Goal: Clarify whether Neo4j’s storage layer should automatically retry obtaining an exclusive lock on its data directory when a transient NFS latency causes the initial lock attempt to fail, or whether it should treat the failure as fatal and shut down immediately. Constraints: The behavior varies between Neo4j 3.x, 4.x, and 5.x releases and can be influence
dovecot
neo4j