Solved

FreeBSD doing a fsck after migration

Posted on 2008-10-02
12
709 Views
Last Modified: 2013-11-22
Hi,

we have 4 ESX 3.5u1-servers with VMotion and DRS activated, on these servers we have a lot of FreeBSD 6.3 amd64 version installed as guests, but when a migration is done from one host to another the servers starts to do an fsck. All disks are placed on a storage so the disks are never moved. We even saw that servers that didn't get moved started to do fsck when another server was moved.
So we have currently turned of DRS and they have stoped doing fsck.

What could be causing this behavior and how can we solve it? We havn't installed VmWare tools.
0
Comment
Question by:Binero
  • 6
  • 3
  • 3
12 Comments
 
LVL 18

Expert Comment

by:larstr
Comment Utility
  1. What kind of shared storage are you using?
  2. How many VMs per LUN?
  3. Any clustered disks?
  4. Any scsi reservation messages in the vmkernel log file of these esx hosts?
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
Have you shut down FreeBSD completely before migration?
0
 

Author Comment

by:Binero
Comment Utility
larstr:
1. We have 2 DELL MD3000i with 15x300GB SAS 15000rpm disks in RAID10 to each MD3000i we have connected a DELL MD1000 with the same disk setup, they're connected to the ESX through 2 dedicated DELL PowerConnect 5424, we're using iSCSI.
2. Not quite shure to be honest but we're trying to keep it low, I think somewhere around 10.
3. No
4. Have to check that up.

gheist:
Yes and when we do that it works, but we can't keep turning the servers of, the we'll loose the purpose with DRS.

I have 3 theories/thoughts:
1. I get the feeling that this happens when a virtual server is moved  from one host to another host and the hosts don't use the same iSCSI path to the storage.
Only thing to back this theory up is from an incident today. We replaced our switches between the hosts and the storage, from DELL PC 2708 to DELL PC 5424. We replaced one switch and when we saw that all paths could be found on the hosts we replaced the second one and when we did this almost all FreeBSD servers froze.

2. VmWare tools are missing on our FreeBSD-servers. Could this cause the issue, in windows there's a huge difference between with/without the tools, does the tools provide a closer co-operation between the host and guest?

3. We replaced our switches between the storage and ESX-servers today, could the problem have been caused by a to slow connection between the hosts and the storage?
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
It is obviously DRS problem, not FreeBSD's
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 18

Expert Comment

by:larstr
Comment Utility
> and the hosts don't use the same iSCSI path to the storage.

If the path's don't match you'll have worse problems so that can't be the issue here.
>  could the problem have been caused by a to slow connection between the hosts and the storage?
Yes, indeed.
0
 

Author Comment

by:Binero
Comment Utility
gheist, thanks I'll have a look at those links.

larstr, each has several paths to the storage for  redundancy.
0
 
LVL 18

Expert Comment

by:larstr
Comment Utility
Several paths is a good thing, but the hosts will need to see these the LUNs at the same path.
0
 
LVL 61

Accepted Solution

by:
gheist earned 500 total points
Comment Utility
Basically:
1) You have to apply patch to ESX to make FreeBSD/amd64 work at all
2) VMWare is unaware of FreeBSD v6.3, so go with 70 or 62 to be on supported path
0
 

Author Comment

by:Binero
Comment Utility
Seems like that patch did the trick, thanks gheist
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
As far as I have seen VMs jumps between ESX-es without problems. We have two of them and never had issues bringing one down correctly.
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Every server (virtual or physical) needs a console: and the console can be provided through hardware directly connected, software for remote connections, local connections, through a KVM, etc. This document explains the different types of consol…
This is an issue that we can get adding / removing permissions in the vCSA 6.0. We can also have issues searching for users / groups in the AD (using your identify sources). This is how one of the ways to handle this issues and fix it.
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now