[Top] [All Lists]

Re: problem with VMware -XFS guilty one - was: Re: XFS is innocen t

To: Olaf Frączyk <olaf@xxxxxxxxxxxxx>
Subject: Re: problem with VMware -XFS guilty one - was: Re: XFS is innocen t
From: Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Date: 17 Jan 2002 12:57:12 -0600
Cc: Stephen Lord <lord@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20020117194821.A3800@venus.local.navi.pl>
References: <20020117194821.A3800@venus.local.navi.pl>
Sender: owner-linux-xfs@xxxxxxxxxxx
Go the drive maker's web site and see if they have a diagnostic utility
you boot from a floppy(will probably be dos based, so be prepared), and
run that. That is the ONLY way to tell if it's truly bad or not.

On Thu, 2002-01-17 at 12:48, Olaf Frączyk wrote:
> On 2002.01.15 13:49:31 +0100 Stephen Lord wrote:
> > 
> > Please try this with the current cvs tree - there was a change in the 
> > last week which fixed
> > some problems with mmapped I/O under heavy memory pressure (the emacs 
> > build problem
> > mentioned on the list).
> Hi,
> It started to looks ugly :(
> Still problem, but ...
> I have 2 SCSI drives, and 1 IDE.
> The system is on sda and sdb drives, hda is for storage of unfrequently 
> needed things.
> So, my /tmp is on /sdb3.
> And, as I said,
> xfs on sdb3 + vmware = vmware crash
> ext2 on sdb3 + vmware = OK
> but I tried to put it on another partition, the only free I have is
> sda4, 
> and:
> both xfs and ext2 on sda4 + vmware = OK.
> So I supposed, there is some problem with the drive, so I ran badblocks
> -v 
> -w, but it didn't found any errors.
> And the only thing which crashes is vmware, all other stuff works 
> perfectly.
> So I think, that drive is OK.
> Anyone has any ideas?
> Regards,
> Olaf 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@xxxxxxxxxxxxxxx

"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb

Attachment: signature.asc
Description: This is a digitally signed message part

<Prev in Thread] Current Thread [Next in Thread>