carlopmart wrote:
> Luke S Crawford wrote:
>> carlopmart <carlopmart@(protected):
>>>>> When I try to copy a 465MB's or 650MB's file to domU, md5sum is
>>>>> ok. But when I try to copy a 1GB file or more, md5sums are
>>>>> wrong. Same result if I try to copy from domU. for example:
>> ...
>>> Please any hints?? I need to deploy this system on a production
>>> environment with xen or with vmware server ...
>>
>> I can't reproduce the problem; several things to check:
>>
>> 1. ram. your problem could be caused by funky ram. run memtest86.
>>
>> 2. funky swap. run dmesg in the dom0. do you see funky problems related
>> to disk? run smartctl and see if your disks are dying.
>>
>> Of course both of those things should also cause periodic swaps, but
>> especially
>> if you don't use ECC ram, and you normally use less ram than you are
>> using
>> with virtualization, setting up virtualization could cause to to use
>> funky ram
>> that would otherwise be idle.
>> another thing to look at is dmesg in the DomU and see if there are any
>> interesting messages.
>> Also, The md5sum is wrong,but is the file size about right?
>>
>>
>
> Thanks Luke for your responses. My answers:
>
> 1) memtest86 doesn't reports any error with ram.
> 2) when I try to start smartd i see these errors:
>
> SCSI device sda: drive cache: write back
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
>       res 51/04:00:80:00:00/00:00:00:00:00/00 Emask 0x1 (device error)
> ata1.00: Host Protected Area detected:
>      current size: 312579695 sectors
>      native size: 312581808 sectors
> ata1.00: Host Protected Area detected:
>      current size: 312579695 sectors
>      native size: 312581808 sectors
> ata1.00: configured for UDMA/133
> ata1: EH complete
>
> 3) file size are ok, only md5sums are wrong. But If I try to execute,
> decompress, mount or I will try another operation to any file, all fails
> ...
>
> I have attached dmesg from dom0 and domU
>

Ok, it seems the problem isn't hardware related, I am not 100% sure but it
seems. I have installed vmware server beta2 on this rhel5.1 host. Afterwards I
have setup a rhel5.1 guest (without installing vmware tools) and all md5sums are
ok now (on guest and on host).

Any ideas why under vmware all works ok (an it is a beta product) and on rhel5.1
xen not???




--
CL Martinez
carlopmart {at} gmail {d0t} com

_______________________________________________
rhelv5-list mailing list
rhelv5-list@(protected)
https://www.redhat.com/mailman/listinfo/rhelv5-list