Solved

FreeBSD doing a fsck after migration

Posted on 2008-10-02
12
746 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3
  • 3
12 Comments
 
LVL 18

Expert Comment

by:larstr
ID: 22632276
  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 62

Expert Comment

by:gheist
ID: 22635500
Have you shut down FreeBSD completely before migration?
0
 

Author Comment

by:Binero
ID: 22637116
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
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 62

Expert Comment

by:gheist
ID: 22637487
It is obviously DRS problem, not FreeBSD's
0
 
LVL 62

Expert Comment

by:gheist
ID: 22637532
0
 
LVL 18

Expert Comment

by:larstr
ID: 22638269
> 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
ID: 22640297
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
ID: 22647548
Several paths is a good thing, but the hosts will need to see these the LUNs at the same path.
0
 
LVL 62

Accepted Solution

by:
gheist earned 500 total points
ID: 22652970
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
ID: 22653081
Seems like that patch did the trick, thanks gheist
0
 
LVL 62

Expert Comment

by:gheist
ID: 22653126
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

Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

HOW TO: Connect to the VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere (HTML5 Web) Host Client 6.5, and perform a simple configuration task of adding a new VMFS 6 datastore.
Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…

632 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