Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. 
The Basics
- Nextcloud Server version (e.g., 29.x.x):
- I can’t get this because my server won’t start due to disk being full.
- Operating system and version (e.g., Ubuntu 24.04)
- Debian 12.2
- Web server and version (e.g, Apache 2.4.25):
- Apache 2.4.62
- Reverse proxy and version _(e.g. nginx 1.27.2)
N/A
- PHP version (e.g, 8.3):
8.2.29
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
I only noticed it recently when I tried to put files in NextCloud
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Proxmox script to use turnkey
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
My server fails to start because the disk is too full. Disk usage points to /var/www/nextcloud-data which contains everything that’s on the NAS but it seems like it’s also being written locally.
I thought I could just have to entire directory live on the NAS so the VM could have minimal storage but it’s almost like it’s keeping everything in sync to the LVM storage.
Steps to replicate it (hint: details matter!):
-
Start server
-
Database fails to start because disk full
-
Nextcloud fails to start because disk full
Log entries
Nextcloud
Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.
warning: ##### write queue file: No space left on device. (this is repeated indefinitely)
Web Browser
If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.
N/A
Web server / Reverse Proxy
The output of your Apache/nginx/system log in /var/log/____:
[Fri Jan 09 00:00:33.609470 2026] [mpm_prefork:notice] [pid 634:tid 634] AH00163: Apache/2.4.62 (Debian) OpenSSL/3.0.15 configured -- resuming normal operations
[Fri Jan 09 00:00:33.609480 2026] [core:notice] [pid 634:tid 634] AH00094: Command line: '/usr/sbin/apache2'
[Fri Jan 09 02:08:49.204038 2026] [log_config:warn] [pid 102556:tid 102556] (28)No space left on device: [client 10.10.20.100:57394] AH00646: Error writing to /var/log/apache2/other_vhosts_access.log
[Fri Jan 09 04:43:44.200798 2026] [php:notice] [pid 102558:tid 102558] [client 10.10.1.102:59936] PHP Notice: fwrite(): Write of 433 bytes failed with errno=28 No space left on device in /var/www/nextcloud/lib/private/Log/File.php on line 58
[Fri Jan 09 04:43:44.200886 2026] [php:notice] [pid 102558:tid 102558] [client 10.10.1.102:59936] PHP Notice: fwrite(): Write of 433 bytes failed with errno=28 No space left on device in /var/www/nextcloud/lib/private/Log/File.php on line 58
[Fri Jan 09 04:43:44.201078 2026] [log_config:warn] [pid 102558:tid 102558] (28)No space left on device: [client 10.10.1.102:59936] AH00646: Error writing to /var/log/apache2/other_vhosts_access.log
[Fri Jan 09 06:39:30.195698 2026] [php:notice] [pid 102559:tid 102559] [client 10.10.20.100:43246] PHP Notice: fwrite(): Write of 452 bytes failed with errno=28 No space left on device in /var/www/nextcloud/lib/private/Log/File.php on line 58
[Fri Jan 09 06:39:30.207956 2026] [php:notice] [pid 102559:tid 102559] [client 10.10.20.100:43246] PHP Notice: fwrite(): Write of 452 bytes failed with errno=28 No space left on device in /var/www/nextcloud/lib/private/Log/File.php on line 58
[Fri Jan 09 06:39:30.208060 2026] [php:notice] [pid 102559:tid 102559] [client 10.10.20.100:43246] PHP Notice: fwrite(): Write of 452 bytes failed with errno=28 No space left on device in /var/www/nextcloud/lib/private/Log/File.php on line 58
[Fri Jan 09 06:39:30.208154 2026] [php:notice] [pid 102559:tid 102559] [client 10.10.20.100:43246] PHP Notice: fwrite(): Write of 451 bytes failed with errno=28 No space left on device in /var/www/nextcloud/lib/private/Log/File.php on line 58
[Fri Jan 09 06:39:30.208322 2026] [log_config:warn] [pid 102559:tid 102559] (28)No space left on device: [client 10.10.20.100:43246] AH00646: Error writing to /var/log/apache2/other_vhosts_access.log
[Fri Jan 09 06:39:32.329912 2026] [php:notice] [pid 102557:tid 102557] [client 10.10.20.100:43250] PHP Notice: fwrite(): Write of 452 bytes failed with errno=28 No space left on device in /var/www/nextcloud/lib/private/Log/File.php on line 58, referer: http://nextcloud.smoochii.dev/
[Fri Jan 09 06:39:32.330651 2026] [php:notice] [pid 102557:tid 102557] [client 10.10.20.100:43250] PHP Notice: fwrite(): W[Fri Jan 09 15:32:59.336058 2026] [mpm_prefork:notice] [pid 634:tid 634] AH00170: caught SIGWINCH, shutting down gracefully
Configuration
Nextcloud
The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):
<?php
$CONFIG = array (
'trusted_domains' =>
array (
),
'datadirectory' => '/mnt/storage/nextcloud',
'dbtype' => 'mysql',
'version' => '30.0.6.2',
'overwrite.cli.url' => 'http://localhost',
'dbname' => 'nextcloud',
'dbhost' => 'localhost',
'dbport' => '',
'dbtableprefix' => 'oc_',
'mysql.utf8mb4' => true,
'dbuser' => '',
'dbpassword' => '',
'installed' => true,
'instanceid' => '',
'memcache.local' => '\\OC\\Memcache\\Redis',
'redis' =>
array (
'host' => '/var/run/redis/redis.sock',
'port' => 0,
'timeout' => 0.0,
),
'filelocking.enabled' => true,
'memcache.locking' => '\\OC\\Memcache\\Redis',
'log_type' => 'file',
'logfile' => '/var/www/nextcloud-data/nextcloud.log',
'loglevel' => 3,
'updater.secret' => '',
'maintenance' => false,
'theme' => '',
'twofactor_enforced' =>
array (
'false' => '',
),
'twofactor_enforced_groups' =>
array (
),
'twofactor_enforced_excluded_groups' =>
array (
),
);
Apps
The output of occ app:list (if possible).
Tips for increasing the likelihood of a response
- Use the
preformatted textformatting option in the editor for all log entries and configuration output. - If screenshots are useful, feel free to include them.
- If possible, also include key error output in text form so it can be searched for.
- Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.