mptscsih problem in Debian5 (Lenny) with VMWare ESX3.5
DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
According to our VMWare administrator there were no updates done at all so I guess we can rule that out for now.
Here a description of one of the problem-systems
athene:~# uname -a
Linux athene 2.6.26-2-686 #1 SMP Thu May 28 15:39:35 UTC 2009 i686 GNU/Linux
VMWare tools version 3.5.0 build 153875
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda9 on /home type ext3 (rw)
/dev/sda8 on /tmp type ext3 (rw)
/dev/sda5 on /usr type ext3 (rw)
/dev/sda6 on /var type ext3 (rw)
nas01:/vol/backup on /backup type nfs (rw,addr=xxx.xxx.xxx.xxx)
/dev/hda on /media/cdrom0 type iso9660 (ro,noexec,nosuid,nodev)
Our Windows systems on the same ESX cluster (yes it's an ESX HA cluster) don't seem have a problem. The Windows hosts report however that they can't find their disk, but don't see that a a problem :-/ .
The debian servers are all based on the same VMWare template!
Even with the forums on the internet I haven't been able to figure out what's causing this.
Can anyone help me with this issue or point me in good direction?
Thanks in advance.
Tim van Dijk
Last edited by timvandijk039; 07-29-2009 at 04:31 AM.
Reason: Further research
It seems that we found the solution to this problem. Hopefully this solution is helpfull to someone with a similar problem.
The problem was found within our NetAPP. On our NetAPP we had several scheduled processes. The scheduled snapshots were however the cause of our problem.
1. Aggregate snapshots
2. Volume snapshot of Datastore-volume
We disabled the aggregate snapshots and the datastore volume snapshot. After this we enabled the snapmirror/snapmanager option with our virtual center server. This feature backs-up our VM's with the great NetAPP snapshot functionality but temporarily suspends the vm's while doing it. By suspending the VM (for a second or two) there is no filesystem corruption.
To check the scheduling of your NetAPP shapshot-tasks, you can enter te following command on the NetAPP command line interface: