Re: Problems after installing Coreutils 5.0.91 or other 5.0.x on Gentoo 1.4

[Edmund]

Hi Bob,

At first I thought it may be a filesystem problem too, but I did several
things
to verify that.  First, if I exited from the chrooted installation
environment, I
was able to see everything just fine.  Also I tried it on both ext3 and
reiserfs
on two seperate trials, and fsck was fine for both.  Also I copied the old
commands ls, cp, and such from the cd's fileutils-4.1.11 and then chrooted
back into the installation path and they worked just fine.  However
replacing
them with the coreutils' version, it broke again.

Please advise,
Edmund


----- Original Message ----- 
From: "Bob Proulx" <address@hidden>
To: "Edmund" <address@hidden>
Cc: <address@hidden>
Sent: Friday, November 07, 2003 1:26 PM
Subject: Re: Problems after installing Coreutils 5.0.91 or other 5.0.x on
Gentoo 1.4


> Edmund wrote:
> > I've experienced a very interesting bug with Coreutils.  The system is
running on Athlon XP, 1G ram with a 200MB WD IDE drive.  My linux is
 installed at the end of the drive (past 170GB) with Windows XP at the
beginning.
>
> In the future it would be most appreciated if you were to word wrap
> your messages in the area of 72 columns.  It is very hard to read your
> long lines otherwise.  Thanks.  (Alternatively set format=flowed which
> will indicate to receiving mailers that we should word wrap on our
> end.  But that is only good for text and not for bug reports including
> exact output.)
>
> > With the base installation's fileutils 4.1.11 everything is fine, but
after
 the system updates itself to coreutils, some of the file operations are
broken.
I'm suspecting this is due to problems with lba 48, but I'm not sure.
> >
> > ls returns all files with size "1759218604416"
> > cp says "skipping file "name", as it was replaced while being copied
> >
> > mv and rm seem to be okay
> > I'm not sure if any other commands are affected.
>
> This seems to be a problem with your filesystem.  Filesystems are part
> of the kernel.  Nothing an application space program like ls or cp can
> do about it if the filesystem is not behaving properly.
>
> > I have tried the installation on smaller non lba48 hard drives without
 incident, and maybe I'll try to install it on a partition under the 128GB
limit
 after I re-partition the drive.
>
> You will need to look at your filesystem closely.  But there is
> nothing that can be done in user space if it is not working.
>
> Bob