K2000 No space left on device message despite being 84% free
Hi so today i've gone to deploy a image to a new device but it gets stuck on the launching deployment client and nothing actually happens. the server has about 84% free space but when i checked the appliance log files i get the following messages:
Feb 19 14:20:01 k2000 sendmail[1859]: 01JEK1ls001859: SYSERR(munin):
Error writing control file qf01JEK1ls001859: No space left on device
Feb 19
14:20:01 k2000 sendmail[1859]: 01JEK1ls001859: SYSERR(munin): putbody:
write error: No space left on device
Feb 19 14:20:01 k2000 last message repeated 4 times
Feb 19
14:20:01 k2000 sendmail[1859]: 01JEK1ls001859: low on space (SMTP-DAEMON
needs 489 bytes + 100 blocks in /var/spool/clientmqueue), max avail: 0
Feb 19
14:20:01 k2000 sendmail[1859]: 01JEK1ls001859: SYSERR(munin):
returntosender: cannot select queue for postmaster
Feb 19
14:20:01 k2000 sendmail[1859]: 01JEK1lu001859: low on space (SMTP-DAEMON
needs 0 bytes + 100 blocks in /var/spool/clientmqueue), max avail: 0
Feb 19
14:20:01 k2000 sendmail[1859]: 01JEK1ls001859: SYSERR(munin):
returntosender: cannot select queue for munin
Feb 19
14:20:01 k2000 sendmail[1859]: 01JEK1lt001859: low on space (SMTP-DAEMON
needs 0 bytes + 100 blocks in /var/spool/clientmqueue), max avail: 0
Feb 19
14:20:01 k2000 sendmail[1859]: 01JEK1ls001859: low on space (SMTP-DAEMON
needs 340 bytes + 100 blocks in /var/spool/clientmqueue), max avail: 0
Feb 19
14:20:01 k2000 kernel: pid 1790 (perl), uid 842 inumber 211994 on /var:
filesystem full
Feb 19
14:20:01 k2000 kernel: pid 1790 (perl), uid 842 inumber 94254 on /var:
filesystem full
Feb 19
14:19:56 k2000 kernel: pid 1772 (smbd), uid 80 inumber 141770 on /var:
filesystem full
Feb 19
14:18:57 k2000 kernel: pid 1064 (perl), uid 842 inumber 211991 on /var:
filesystem full
Feb 19
14:18:56 k2000 kernel: VMware Tools is installed, but it has not been
Feb 19
14:18:56 k2000 kernel: pid 1064 (perl), uid 842 inumber 221266 on /var:
filesystem full
Feb 19
14:18:54 k2000 root: /etc/rc: WARNING: failed to start munin_node
Feb 19
14:18:52 k2000 root: /etc/rc: WARNING: failed to start pxeboot_watcher
Feb 19 14:18:52 k2000 kernel: (da0:mpt0:0:0:0): Retrying command
Feb 19
14:18:52 k2000 kernel: (da0:mpt0:0:0:0): CAM status: CCB request
terminated by the host
Feb 19
14:18:52 k2000 kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 00 05 14 3e
40 00 00 20 00
Feb 19 14:18:51 k2000 root: /etc/rc: WARNING: failed to start tftpd
Feb 19
14:18:51 k2000 in.tftpd[985]: /usr/local/tftp: No such file or directory
Feb 19
14:18:37 k2000 ntpd[585]: switching logging to file /var/log/ntp.log
Feb 19 14:18:36 k2000 kernel: .
I've rebooted the appliance and i'm having no luck does anyone have any idea?
Answers (1)
You might want to contact Support, and review this:
https://support.quest.com/kb/313329/a-partition-size-too-small-var-may-prevent-version-upgrades
Confirm this from the SDA Status Overview Report.
There is a table next to a pie chart, with a detailed storage output.
Audit Log › Reports > SDA Status Overview. - Channeler 4 years ago
After they clear that, I would watch out for those CAM Status Errors you have.
UNIX print those errors, when it has issues reading or writing to your storage.
If you are running on a Physical PowerEdge Server, I suggest checking for a degraded Array.
If it's a VM, check how busy your dataStore is, and if the same thing keeps happening if you were to move the VM to a less busy host.
See the answers here:
https://www.reddit.com/r/freebsd/comments/7hb1jp/cam_status_ccb_request_aborted_by_the_host/
https://forums.freebsd.org/threads/solved-cam-status-ccb-request-aborted-by-the-host.63512/
https://www.ixsystems.com/community/threads/cam-status-ccb-request-completed-with-an-error.44800/ - Channeler 4 years ago
Guess this speeds up the process of looking for a new imaging solution.
Thanks for your help. - terryj 4 years ago