Jump to content
Welcome to our new Citrix community!
  • 0

tapdisk experienced an error


masud parvez1709159346

Question

my xen version 7.2.  But my VM cannot boot and I saw the "tapdisk experienced an error"  please give me a solution. And also see that "/dev/sda5                                                                                                  3.9G  3.9G     0 100% /var/log" I can't reduce this log after proceed  rm -rf *.gz. what can I do?

Link to comment

19 answers to this question

Recommended Posts

  • 0

Without any free space to log, pretty much everything will come to a halt. Are there any crash dumps? You can also get rid of some of the older log files selectively, but in any case, you need some free space. It is not normal for the log area to completely fill up and this is an indication of another problem and the first step is to get the system running again.

 

-=Tobias

Link to comment
  • 0

Here is my /var/log files detail

 

 

-rw------- 1 root   root    2195456 Mar  5 11:14 audit.log
-rw------- 1 root   root    4313035 Feb  3 04:01 audit.log.1
drwxr-xr-x 2 root   root      16384 Mar  4 18:42 blktap
-rw-r--r-- 1 root   root          0 Feb 12 11:53 boot.log
-rw-r--r-- 1 root   root          0 Feb  2 04:02 boot.log.1
-rw------- 1 root   utmp       4096 Feb 26 07:17 btmp
-rw------- 1 root   utmp      34944 Feb  1 03:13 btmp.1
drwxr-xr-x 2 root   root       4096 Nov 21  2015 cluster
-rw------- 1 root   root          0 Feb 12 11:54 crit.log
-rw------- 1 root   root      77824 Mar  5 11:10 cron
-rw------- 1 root   root      42677 Feb  3 04:02 cron.1
-rw------- 1 root   root    1150976 Mar  5 11:14 daemon.log
-rw------- 1 root   root    2093355 Feb  3 04:02 daemon.log.1
-rw-r--r-- 1 root   root      61440 Feb 12 11:53 dmesg
-rw-r--r-- 1 root   root      75191 Feb  1 14:46 dmesg.old
drwxr-xr-x 2 root   root       4096 Jan 16 15:22 installer
-rw-r--r-- 1 root   root          0 Feb 12 11:53 interface-rename.log
-rw-r--r-- 1 root   root          0 Feb  2 04:02 interface-rename.log.1
-rw------- 1 root   root       8192 Mar  4 19:21 kern.log
-rw------- 1 root   root      29345 Feb  3 04:01 kern.log.1
-rw-r--r-- 1 root   root   38273316 Mar  5 11:14 lastlog
drwx------ 2 root   root      16384 Jan 16 15:10 lost+found
-rw------- 1 root   root      69632 Mar  5 11:10 maillog
-rw------- 1 root   root        132 Feb  2 19:30 maillog.1
-rw------- 1 root   root          0 Feb  3 04:02 messages
-rw------- 1 root   root          0 Feb  2 04:02 messages.1
drwxr-xr-x 2 ntp    ntp        4096 Nov 20  2015 ntpstats
drwxr-xr-x 2 root   root       4096 May 11  2017 openvswitch
-rw-r--r-- 1 root   root       2019 Feb 12 11:53 ovs-ctl.log
-rw-r--r-- 1 root   root       8192 Mar  4 18:42 ovsdb-server.log
-rw-r--r-- 1 root   root     159744 Mar  4 18:42 ovs-vswitchd.log
-rw-r--r-- 1 root   root        594 Feb 12 11:54 ovs-xapi-sync.log
-rw-r--r-- 1 root   root       5083 Jan 16 15:56 pbis-open-install.log
-rw-r--r-- 1 root   root       1338 Feb 12 11:53 restoreeswitchcfg.log
drwxr-xr-x 2 root   root       4096 Mar  2 23:53 sa
drwx------ 3 root   root       4096 Jan 16 15:15 samba
-rw------- 1 root   root      12288 Mar  5 11:14 secure
-rw------- 1 root   root    1147058 Feb  2 20:06 secure.1
-rw------- 1 root   root    1118208 Mar  5 11:14 SMlog
-rw------- 1 root   root    5948172 Feb  3 04:01 SMlog.1
-rw------- 1 root   root          0 Feb  3 04:02 spooler
-rw------- 1 root   root          0 Feb  2 04:02 spooler.1
-rw------- 1 root   root          0 Jan 16 15:14 tallylog
-rw------- 1 root   root      28672 Mar  5 10:17 user.log
-rw------- 1 root   root        743 Feb  3 04:02 user.log.1
-rw------- 1 root   root      69632 Mar  5 11:00 VMSSlog
-rw------- 1 root   root      17124 Feb  3 04:00 VMSSlog.1
-rw-rw-r-- 1 root   utmp      28416 Mar  5 11:14 wtmp
-rw------- 1 root   root    6959104 Mar  5 11:14 xcp-rrdd-plugins.log
-rw------- 1 root   root        204 Feb  2 19:08 xcp-rrdd-plugins.log.1
drwxr-xr-x 2 root   root       4096 Feb 13 04:02 xen
-rw------- 1 root   root   65769472 Mar  5 11:14 xensource.log
-rw------- 1 root   root   49809457 Feb  3 00:40 xensource.log.1
-rw------- 1 root   root    5623808 Mar  5 11:14 xenstored-access.log
-rw------- 1 root   root    8740255 Feb  3 04:01 xenstored-access.log.1
-rw------- 1 root   root      30156 Jan 16 17:29 yum.log
drwxr-xr-x 2 zabbix zabbix     4096 Feb  4 04:02 zabbix
 

what should will remove?

 

and is it possible to increase log file storage from 4 GB to 8 GB before xen setup?

Link to comment
  • 0

No, the partitions cannot be increased. But it should never be this full to begin with, not even close so something is going on to cause this issue.

 

Let's see what your largest files really are in that entire partition. Run this:

 

cd /var/log

ls -lR|sort -r -n -k 5,5| head -200

 

and please paste the output into here. This will show the largest files in descending order starting with the very largest.

 

-=Tobias

Link to comment
  • 0

This is the output

 

-rw-r--r-- 1 root root 3507412002 Feb  3 04:02 tapdisk.7274.log.1
-rw-r--r-- 1 root root  414531584 Feb 12 11:45 tapdisk.7274.log
-rw------- 1 root   root   65769472 Mar  5 13:35 xensource.log
-rw------- 1 root   root   49809457 Feb  3 00:40 xensource.log.1
-rw-r--r-- 1 root   root   38273316 Mar  5 13:35 lastlog
-rw------- 1 root   root    8740255 Feb  3 04:01 xenstored-access.log.1
-rw------- 1 root   root    6959104 Mar  5 13:35 xcp-rrdd-plugins.log
-rw------- 1 root   root    5948172 Feb  3 04:01 SMlog.1
-rw------- 1 root   root    5623808 Mar  5 13:35 xenstored-access.log
-rw------- 1 root   root    4313035 Feb  3 04:01 audit.log.1
-rw------- 1 root   root    2195456 Mar  5 13:35 audit.log
-rw------- 1 root   root    2093355 Feb  3 04:02 daemon.log.1
-rw------- 1 root   root    1150976 Mar  5 13:35 daemon.log
-rw------- 1 root   root    1147058 Feb  2 20:06 secure.1
-rw------- 1 root   root    1118208 Mar  5 13:35 SMlog
-rw-r--r-- 1 root root 490925 Jan 16 15:23 install-log
-rw-r--r-- 1 root root     193403 Jan 29 04:02 tapdisk.17489.log.2.gz
-rw-r--r-- 1 root root     163007 Jan 24 04:02 tapdisk.17489.log.7.gz
-rw-r--r-- 1 root   root     159744 Mar  4 18:42 ovs-vswitchd.log
-rw-r--r-- 1 root root 108461 Jan 16 15:23 lspci-log
-rw-r--r-- 1 root root  78971 Jan 16 15:23 dmesg-log
-rw------- 1 root   root      77824 Mar  5 13:30 cron
-rw-r--r-- 1 root   root      75191 Feb  1 14:46 dmesg.old
-rw------- 1 root   root      69632 Mar  5 13:30 VMSSlog
-rw------- 1 root   root      69632 Mar  5 13:30 maillog
-rw-r--r-- 1 root root 65536 Feb 28 23:50 sa28
-rw-r--r-- 1 root root 65536 Feb 21 23:50 sa21
-rw-r--r-- 1 root   root      61440 Feb 12 11:53 dmesg
-rw-r--r-- 1 root root      60113 Feb  1 14:15 tapdisk.26540.log.1
-rw-r--r-- 1 root root 45056 Mar  2 23:50 sa02
-rw-r--r-- 1 root root 45056 Feb 27 23:50 sa27
-rw-r--r-- 1 root root 45056 Feb 26 23:50 sa26
-rw-r--r-- 1 root root 45056 Feb 25 23:50 sa25
-rw-r--r-- 1 root root 45056 Feb 24 23:50 sa24
-rw-r--r-- 1 root root 45056 Feb 22 23:50 sa22
-rw-r--r-- 1 root root 45056 Feb 20 23:50 sa20
-rw-r--r-- 1 root root 45056 Feb 19 23:50 sa19
-rw------- 1 root   root      42677 Feb  3 04:02 cron.1
-rw-r--r-- 1 root root 40960 Feb 18 23:50 sa18
-rw-r--r-- 1 root root      40688 Jan 26 04:02 tapdisk.17489.log.5.gz
-rw------- 1 root   utmp      34944 Feb  1 03:13 btmp.1
-rw-r--r-- 1 root root  30759 Jan 16 15:23 devcontents-log
-rw-r--r-- 1 root root  30496 Jan 16 15:23 pci-log
-rw------- 1 root   root      30156 Jan 16 17:29 yum.log
-rw------- 1 root   root      29345 Feb  3 04:01 kern.log.1
-rw------- 1 root   root      28672 Mar  5 13:21 user.log
-rw-rw-r-- 1 root   utmp      28416 Mar  5 13:35 wtmp
-rw-r--r-- 1 root root 24576 Mar  3 23:50 sa03
-rw-r--r-- 1 root root 24576 Mar  1 23:50 sa01
-rw-r--r-- 1 root root 24576 Feb 23 23:50 sa23
-rw-r--r-- 1 root root  23668 Jan 16 15:23 xl-dmesg-log
-rw-r--r-- 1 root root 20480 Feb 17 23:50 sa17
-rw-r--r-- 1 root root 20480 Feb 16 23:50 sa16
-rw------- 1 root   root      17124 Feb  3 04:00 VMSSlog.1
-rw-rw-r-- 1 zabbix zabbix 16457 Jan 25 21:56 zabbix_agentd.log.1
-rw-r--r-- 1 root root      16384 Mar  5 12:02 tapdisk.8418.log
drwxr-xr-x 2 root   root      16384 Mar  4 18:42 blktap
drwx------ 2 root   root      16384 Jan 16 15:10 lost+found
-rw-r--r-- 1 root root      12530 Jan 27 04:02 tapdisk.17489.log.4.gz
-rw------- 1 root   root      12288 Mar  5 13:35 secure
-rw-r--r-- 1 root   root       8192 Mar  4 18:42 ovsdb-server.log
-rw------- 1 root   root       8192 Mar  4 19:21 kern.log
-rw-r--r-- 1 root root       6978 Jan 28 04:02 tapdisk.17489.log.3.gz
-rw-r--r-- 1 root root   5685 Jan 16 15:23 processes-log
-rw-r--r-- 1 root root       5340 Jan 20 04:02 tapdisk.17489.log.11.gz
-rw-r--r-- 1 root   root       5083 Jan 16 15:56 pbis-open-install.log
-rw-rw-r-- 1 zabbix zabbix  4096 Mar  4 22:16 zabbix_agentd.log
-rw-r--r-- 1 root root  4096 Feb 12 23:50 sa12
-rw-r--r-- 1 root root 4096 Feb 12 11:53 hypervisor.log
-rw------- 1 root   utmp       4096 Feb 26 07:17 btmp
drwxr-xr-x 2 zabbix zabbix     4096 Feb  4 04:02 zabbix
drwxr-xr-x 2 root   root       4096 Nov 21  2015 cluster
drwxr-xr-x 2 root   root       4096 May 11  2017 openvswitch
drwxr-xr-x 2 root   root       4096 Mar  2 23:53 sa
drwxr-xr-x 2 root   root       4096 Jan 16 15:22 installer
drwxr-xr-x 2 root   root       4096 Feb 13 04:02 xen
drwxr-xr-x 2 ntp    ntp        4096 Nov 20  2015 ntpstats
drwx------ 3 root   root       4096 Jan 16 15:15 samba
drwx------ 2 root root 4096 Nov 21  2015 old
-rw-r--r-- 1 root root   3927 Jan 16 15:23 lspcin-log
-rw-r--r-- 1 root root       2757 Jan 31 04:02 tapdisk.26540.log.3.gz
-rw-r--r-- 1 root root   2667 Jan 16 15:23 interrupts-log
-rw-r--r-- 1 root root   2470 Jan 16 15:23 modules-log
-rw-r--r-- 1 root root  2224 Mar  2 23:53 sar02
-rw-r--r-- 1 root root       2222 Jan 22 04:02 tapdisk.17489.log.9.gz
-rw-r--r-- 1 root   root       2019 Feb 12 11:53 ovs-ctl.log
-rw-r--r-- 1 root root       1783 Jan 21 04:02 tapdisk.17489.log.10.gz
-rw-r--r-- 1 root root       1653 Jan 23 04:02 tapdisk.17489.log.8.gz
-rw-r--r-- 1 root   root       1338 Feb 12 11:53 restoreeswitchcfg.log
-rw-r--r-- 1 root root        852 Feb  1 04:02 tapdisk.26540.log.2.gz
-rw------- 1 root   root        743 Feb  3 04:02 user.log.1
-rw-rw-r-- 1 zabbix zabbix   697 Jan 17 12:00 zabbix_agentd.log.2.gz
-rw-r--r-- 1 root   root        594 Feb 12 11:54 ovs-xapi-sync.log
-rw-r--r-- 1 root root    299 Jan 16 15:23 vgscan-log
-rw-r--r-- 1 root root        249 Jan 18 04:02 tapdisk.6587.log.11.gz
-rw-r--r-- 1 root root        246 Jan 29 13:18 tapdisk.17489.log.1
-rw------- 1 root   root        204 Feb  2 19:08 xcp-rrdd-plugins.log.1
-rw-r--r-- 1 root root        200 Jan 18 04:02 tapdisk.5848.log.15.gz
-rw-r--r-- 1 root root        193 Jan 19 04:02 tapdisk.6587.log.10.gz
-rw-r--r-- 1 root root        186 Jan 18 04:02 tapdisk.22042.log.15.gz
-rw-r--r-- 1 root root        178 Jan 18 04:02 tapdisk.5185.log.15.gz
-rw-r--r-- 1 root root        176 Jan 24 04:02 tapdisk.6587.log.5.gz
-rw-r--r-- 1 root root        151 Jan 22 04:02 tapdisk.6587.log.7.gz
-rw-r--r-- 1 root root    146 Jan 16 15:23 blockdevs-log
-rw-r--r-- 1 root root        144 Jan 18 04:02 tapdisk.16650.log.13.gz
-rw-r--r-- 1 root root        141 Jan 19 04:02 tapdisk.21014.log.14.gz
-rw-r--r-- 1 root root        137 Jan 30 04:02 tapdisk.30554.log.1
-rw-r--r-- 1 root root        137 Jan 30 04:02 tapdisk.17558.log.1
-rw-r--r-- 1 root root        137 Jan 30 04:02 tapdisk.16650.log.1
-rw-r--r-- 1 root root        137 Jan 30 04:02 tapdisk.14533.log.1
-rw-r--r-- 1 root root        137 Jan 29 04:02 tapdisk.17485.log.1
-rw-r--r-- 1 root root        137 Jan 28 04:02 tapdisk.28787.log.1
-rw-r--r-- 1 root root        137 Jan 21 04:02 tapdisk.19731.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.30461.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.26886.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.26537.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.22042.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.21014.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.20108.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.19715.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.18982.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.15501.log.1
-rw-r--r-- 1 root root        137 Feb  1 04:02 tapdisk.10469.log.1
-rw-r--r-- 1 root root        135 Jan 28 04:02 tapdisk.7518.log.1
-rw-r--r-- 1 root root        135 Jan 28 04:02 tapdisk.6587.log.1
-rw-r--r-- 1 root root        135 Jan 28 04:02 tapdisk.1011.log.1
-rw-r--r-- 1 root root        135 Feb  3 04:02 tapdisk.9383.log.1
-rw-r--r-- 1 root root        135 Feb  3 04:02 tapdisk.9198.log.1
-rw-r--r-- 1 root root        135 Feb  3 04:02 tapdisk.8918.log.1
-rw-r--r-- 1 root root        135 Feb  3 04:02 tapdisk.8194.log.1
-rw-r--r-- 1 root root        135 Feb  3 04:02 tapdisk.7331.log.1
-rw-r--r-- 1 root root        135 Feb  3 04:02 tapdisk.6591.log.1
-rw-r--r-- 1 root root        135 Feb  3 04:02 tapdisk.5377.log.1
-rw-r--r-- 1 root root        135 Feb  3 04:02 tapdisk.4970.log.1
-rw-r--r-- 1 root root        135 Feb  1 04:02 tapdisk.6437.log.1
-rw-r--r-- 1 root root        135 Feb  1 04:02 tapdisk.5848.log.1
-rw-r--r-- 1 root root        135 Feb  1 04:02 tapdisk.5185.log.1
-rw-r--r-- 1 root root        135 Feb  1 04:02 tapdisk.4937.log.1
-rw------- 1 root   root        132 Feb  2 19:30 maillog.1
-rw-r--r-- 1 root root        117 Jan 30 04:02 tapdisk.5185.log.3.gz
-rw-r--r-- 1 root root        117 Jan 30 04:02 tapdisk.18982.log.3.gz
-rw-r--r-- 1 root root        117 Jan 27 04:02 tapdisk.15501.log.6.gz
-rw-r--r-- 1 root root        116 Jan 30 04:02 tapdisk.5848.log.3.gz
-rw-r--r-- 1 root root        116 Jan 30 04:02 tapdisk.4937.log.3.gz
-rw-r--r-- 1 root root        116 Jan 30 04:02 tapdisk.20108.log.3.gz
-rw-r--r-- 1 root root        116 Jan 30 04:02 tapdisk.15501.log.3.gz
-rw-r--r-- 1 root root        116 Jan 30 04:02 tapdisk.10469.log.3.gz
-rw-r--r-- 1 root root        116 Jan 29 04:02 tapdisk.15501.log.4.gz
-rw-r--r-- 1 root root        116 Jan 28 04:02 tapdisk.16650.log.3.gz
-rw-r--r-- 1 root root        116 Jan 28 04:02 tapdisk.14533.log.3.gz
-rw-r--r-- 1 root root        116 Jan 27 04:02 tapdisk.30554.log.4.gz
-rw-r--r-- 1 root root        116 Jan 27 04:02 tapdisk.21014.log.6.gz
-rw-r--r-- 1 root root        116 Jan 27 04:02 tapdisk.17558.log.4.gz
-rw-r--r-- 1 root root        116 Jan 27 04:02 tapdisk.17485.log.3.gz
-rw-r--r-- 1 root root        116 Jan 27 04:02 tapdisk.16650.log.4.gz
-rw-r--r-- 1 root root        116 Jan 26 04:02 tapdisk.20108.log.7.gz
-rw-r--r-- 1 root root        116 Jan 26 04:02 tapdisk.16650.log.5.gz
-rw-r--r-- 1 root root        116 Jan 26 04:02 tapdisk.15501.log.7.gz
-rw-r--r-- 1 root root        116 Jan 25 04:02 tapdisk.18982.log.8.gz
-rw-r--r-- 1 root root        116 Jan 24 04:02 tapdisk.18982.log.9.gz
-rw-r--r-- 1 root root        116 Jan 24 04:02 tapdisk.17485.log.6.gz
-rw-r--r-- 1 root root        116 Jan 23 04:02 tapdisk.26886.log.10.gz
-rw-r--r-- 1 root root        116 Jan 23 04:02 tapdisk.18982.log.10.gz
-rw-r--r-- 1 root root        116 Jan 23 04:02 tapdisk.16650.log.8.gz
-rw-r--r-- 1 root root        116 Jan 20 04:02 tapdisk.26886.log.13.gz
-rw-r--r-- 1 root root        116 Jan 20 04:02 tapdisk.21014.log.13.gz
-rw-r--r-- 1 root root        116 Jan 20 04:02 tapdisk.20108.log.13.gz
-rw-r--r-- 1 root root        116 Jan 20 04:02 tapdisk.19731.log.2.gz
-rw-r--r-- 1 root root        116 Jan 20 04:02 tapdisk.18982.log.13.gz
-rw-r--r-- 1 root root        116 Jan 20 04:02 tapdisk.17485.log.10.gz
-rw-r--r-- 1 root root        116 Jan 19 04:02 tapdisk.4937.log.14.gz
-rw-r--r-- 1 root root        115 Jan 31 04:02 tapdisk.30461.log.2.gz
-rw-r--r-- 1 root root        115 Jan 31 04:02 tapdisk.26886.log.2.gz
-rw-r--r-- 1 root root        115 Jan 31 04:02 tapdisk.26537.log.2.gz
-rw-r--r-- 1 root root        115 Jan 31 04:02 tapdisk.22042.log.2.gz
-rw-r--r-- 1 root root        115 Jan 31 04:02 tapdisk.20108.log.2.gz
-rw-r--r-- 1 root root        115 Jan 31 04:02 tapdisk.18982.log.2.gz
-rw-r--r-- 1 root root        115 Jan 31 04:02 tapdisk.15501.log.2.gz
-rw-r--r-- 1 root root        115 Jan 31 04:02 tapdisk.10469.log.2.gz
-rw-r--r-- 1 root root        115 Jan 30 04:02 tapdisk.6437.log.3.gz
-rw-r--r-- 1 root root        115 Jan 30 04:02 tapdisk.30461.log.3.gz
-rw-r--r-- 1 root root        115 Jan 30 04:02 tapdisk.22042.log.3.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.6437.log.4.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.5185.log.4.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.4937.log.4.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.30554.log.2.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.20108.log.4.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.18982.log.4.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.17558.log.2.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.16650.log.2.gz
-rw-r--r-- 1 root root        115 Jan 29 04:02 tapdisk.14533.log.2.gz
-rw-r--r-- 1 root root        115 Jan 28 04:02 tapdisk.22042.log.5.gz
-rw-r--r-- 1 root root        115 Jan 28 04:02 tapdisk.21014.log.5.gz
-rw-r--r-- 1 root root        115 Jan 28 04:02 tapdisk.17485.log.2.gz
-rw-r--r-- 1 root root        115 Jan 27 04:02 tapdisk.7518.log.2.gz
-rw-r--r-- 1 root root        115 Jan 27 04:02 tapdisk.5848.log.6.gz
-rw-r--r-- 1 root root        115 Jan 27 04:02 tapdisk.5185.log.6.gz
-rw-r--r-- 1 root root        115 Jan 27 04:02 tapdisk.4937.log.6.gz
-rw-r--r-- 1 root root        115 Jan 27 04:02 tapdisk.22042.log.6.gz
-rw-r--r-- 1 root root        115 Jan 27 04:02 tapdisk.20108.log.6.gz
 

Link to comment
  • 0

I know of no ill effects of removing any files from /var/log. Also /var/patch remove all files (leave /var/patch/applied alone). 

You may have to reboot the host before you can delete some files and it may not show space being freed up unitl you do so.

Things get goofy with there is no free space available on XenServer.  Make sure on all of your VM's that the DVD drives are 

ejected. xe vm-cd-eject multiple should do that for you as well. You need to find the root cause of why your log files are 

getting so large, especially on the 4Gb partition scheme.

 

--Alan--

 

 

Link to comment
  • 0

IMHO, XS should be able to handle this instead of having to do it manually when things break. 

These are the kinds of things that get me really angry - because a product should be resilient. You invest in clusters and pools and high availability and eventually some stupid log folder fills up because some dev or product manager was too lazy to insert some automated cleanup or warning and presto - you've got a stupid point of failure.

Link to comment
  • 0

We didn't turn on any extreme logging or anything like that. XS 7.x should have introduced a new layout that should have handled it - but it's not related to the space but rather to the monitoring that this space is not filled. It's the ABC of developing a resilient system

Link to comment
  • 0

I know, this thread is very old, but I have some usefull input for other xenserver admins.

I got the same error in XenServer 7.1, but my logfile size looked well (8% used space).

I scanned my vdi(is on NFS SR) with the "vhd-util check -n /path to SR-UUID/UUID-vhd file

In my case I got the error "failed to get batmap header"(please look at the end of the picture). The vhd-util check command sould return a "....vhd is valid".

What did I do? I copied a new created vhd file (415 kib)  from NFS SR to my notebook. I attached the empty vhd in a new HyperV VM and installed an exotic network security appliance, because the setup doesn't  run under XenServer. After installation finished, I copied the vhd back to NFS SR. After VM  start, I got the error "tapdisk experienced an error". 

I solved it with not using a fresh, empty dynamic vhd. I copied a used vhd from old Maschine to my notebook, cleaned it with Windows diskpart, installed the alliance, renamed the vhd (https://www.uuidgenerator.net/), copied back to NFS SR and rescaned it to find the new vdi…..

 

I hope this information is useful for anyone.

bad vhd.PNG

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...