VMware Cloud Community
srnagu
Contributor
Contributor
Jump to solution

Filesystem in ESX 3.5i

Hi,

I n our ESX 3.5i server, if i issue df, I get below list of filesystems (I havent taken SAN filesys to considerations)

Filesystem Size Used Available Use% Mounted on

unknown 190.1M 128.7M 61.3M 68% /

unknown 63.5G 561.0M 63.0G 1% /vmfs/volumes/49604c81-3b4f2033-92f2-001cc4a6b6d8 -


No Contents

unknown 539.8M 252.3M 287.5M 47% /vmfs/volumes/3abb47ef-875ea67c-c948-7bf6ff8d3c38 -


conf; db; etc; opt; packages; var; vmupgrade

unknown 47.8M 38.3M 9.5M 80% /vmfs/volumes/5e67cf7d-cddfa83b-9693-7bb6ffc9233b -


binmod.tgz; checksum.md5; environ.tgz; oem.tgz; vmkernel.gz; boot.cfg; cim.tgz; license.tgz; state.tgz

unknown 47.8M 38.3M 9.5M 80% /vmfs/volumes/94b04e7e-2ba18633-fbca-f037d2f64924 -


binmod.tgz; boot.cfg; cim.tgz; environ.tgz license.tgz; oem.tgz; state.tgz; vmkernel.gz

unknown 4.0G 1.0G 3.0G 26% /vmfs/volumes/49604c80-e90b3c5a-880f-001cc4a6b6d8 -


downloads; uwswap; var

I'm little confused with the filesys architecture of ESX 3.5i and want to know, what are all these filesys? I have given the contents of each filesys

Yesterday, when we had problem with the server, we were not able to see the 3 filesystems. (out of above 6). After reboot we found all filesys.

Regards,

Nagu

0 Kudos
1 Solution

Accepted Solutions
Dave_Mishchenko
Immortal
Immortal
Jump to solution

This will give you a bit of background on some of the partitions - http://www.vm-help.com/esx/esx3i/check_system_partitions.php. The root partition (190 MB) in a RAM drive and the other partititions are mounted below it. Your large one will be your VMFS datastore and the others are bootbank / altbootbank / store and scratch.

In your case

Filesystem Size Used Available Use%

unknown 190.1M 128.7M 61.3M 68% RAM drive

unknown 63.5G 561.0M 63.0G 1% VMFS datastore

unknown 539.8M 252.3M 287.5M 47% store

unknown 47.8M 38.3M 9.5M 80% bootbank

unknown 47.8M 38.3M 9.5M 80% altbootbank

unknown 4.0G 1.0G 3.0G 26% scratch.

View solution in original post

0 Kudos
4 Replies
srnagu
Contributor
Contributor
Jump to solution

Hi,

Since it looked bit confusing, I have uploaded the df output and contents of filesys in excel format.

0 Kudos
Dave_Mishchenko
Immortal
Immortal
Jump to solution

This will give you a bit of background on some of the partitions - http://www.vm-help.com/esx/esx3i/check_system_partitions.php. The root partition (190 MB) in a RAM drive and the other partititions are mounted below it. Your large one will be your VMFS datastore and the others are bootbank / altbootbank / store and scratch.

In your case

Filesystem Size Used Available Use%

unknown 190.1M 128.7M 61.3M 68% RAM drive

unknown 63.5G 561.0M 63.0G 1% VMFS datastore

unknown 539.8M 252.3M 287.5M 47% store

unknown 47.8M 38.3M 9.5M 80% bootbank

unknown 47.8M 38.3M 9.5M 80% altbootbank

unknown 4.0G 1.0G 3.0G 26% scratch.

0 Kudos
srnagu
Contributor
Contributor
Jump to solution

thanks a lot

Under any circumstaces, is there any chance for filesystem missing?

Though all the filesys are in the same hard drive, yesterday 3 FAT filesys were missing. Reboot has fixed the issue.

/var/log/messages had SCSI TIME OUT errors like below..

Apr 1 05:33:26 Hostd: Storage data synchronization policy set to invalidate_change

Apr 1 05:33:26 Hostd: undoAttempts(15), timeoutMsec(2000)

Apr 1 05:33:33 vmkernel: 86:23:03:01.500 cpu2:32505986)WARNING: ScsiDevice: 2753: Failed for vmhba2:0:0: Timeout

Apr 1 05:33:33 vmkernel: 86:23:03:01.500 cpu2:32505986)WARNING: ScsiDevice: 3122: READ CAPACITY on device "vmhba2:0:0" from Plugin "legacyMP" failed. Timeout

Apr 1 05:33:33 vmkernel: 86:23:03:01.500 cpu2:32505986)FSS: 390: Failed with status Invalid handle for fa7 40 1 5e67cf7d cddfa83b b67b9693 3b23c9ff ffffffff 0 ffffffff 0 801b6780064096c 238f0640801d320 7a3d2d03c0bc54

Apr 1 05:34:06 vmkernel: 86:23:03:33.854 cpu3:31370399)WARNING: ScsiDevice: 2753: Failed for vmhba2:0:0: Timeout

Regards,

Nagu

0 Kudos
Dave_Mishchenko
Immortal
Immortal
Jump to solution

Under normal circumstances it should not disconnect. Might be worth running a hardware check on the server.

0 Kudos