houghtp
Contributor
Contributor

creating .vmdks

Jump to solution

Can anyone tell me if creating a .vmdk the full size of a datastore would cause storage problems?

we're having problems with hosts crashing when we do a storage rescan and the only thing i can see are some errors about journal not being opened due to lack of space. for instance:

Oct 6 16:17:56 svr-vmh-crcla01 vmkernel: 52:13:09:01.060 cpu8:1047)WARNING: J3: 1378: No space for journal on volume

48b55210-d9384ee3-f0c8-001cc46d1b14. Opening in read-only mode with limited write support.

Oct 6 16:17:56 svr-vmh-crcla01 vmkernel: 52:13:09:01.060 cpu8:1047)WARNING: J3: 1381: Set 'OpenWithoutJournal' advan

ced option to 0 to attempt freeing up space for journal. If this fails, volume is not opened.

Oct 6 16:32:17 svr-vmh-crcla01 vmkernel: 0:T0:L49

Oct 6 16:32:17 svr-vmh-crcla01 vmkernel: 0:00:00:24.801 cpu4:1049)ScsiScan: 395: Path 'vmhba1:C0:T0:L50': Vendor: 'H

P ' Model: 'HSV210 ' Rev: '6110'

server crashed at 16:17, the volume in question has a .vmdk that takes up all space on LUN.

0 Kudos
1 Solution

Accepted Solutions
Troy_Clavell
Immortal
Immortal

thought so, do you hink this would cause a host to freeze up while we are doing rescans?looking at the KB it seems plausable?

yes, that is highly possible. My advise would be to try and free up space on that data store.

View solution in original post

0 Kudos
4 Replies
Troy_Clavell
Immortal
Immortal

you should never fill your datastore to full capacity, in my opinion there should be about 15% free space.

Have a look at this KB http://kb.vmware.com/kb/1003935 which shows you how to set your "OpenWithoutJournal"

0 Kudos
houghtp
Contributor
Contributor

thought so, do you hink this would cause a host to freeze up while we are doing rescans?looking at the KB it seems plausable?

0 Kudos
Troy_Clavell
Immortal
Immortal

thought so, do you hink this would cause a host to freeze up while we are doing rescans?looking at the KB it seems plausable?

yes, that is highly possible. My advise would be to try and free up space on that data store.

View solution in original post

0 Kudos
houghtp
Contributor
Contributor

thanks Troy, i think we'll move it to new datastore...

0 Kudos