On Thu, 3 Mar 2005, McIlwrath, BK (Brian) wrote:
> Starlink development wrote on :
> >
> > So far this is only reproducable on Fedora Core 2
> > installations (I've checked 6 machines in various states)
> > running kernel 2.6.9 or later. I'm still fairly clueless
> > about what the exact problem is, or how to solve it properly,
> > as my only FC3 installation with the same kernel as the
> > machine the problem originally surfaced on, is working OK, as
> > are all the RHEL and RH machines I've tried and there are no
> > reports I can find about anything like this in the kernel
> > mailing lists (although there is a mention of some fixes for
> > MAP_SHARED in the 2.6.11 release notes).
>
> Peter - as it happens I just wiped out FC2 on my home system last
> weekend and installed FC3. There are a lot of changes in the way FC2 and
> 3 use the Ext2/3 file systems as they (or at least FC3) have options
> tuned on for ACL's on files (to support the built-in SELinux kernel
> extension) - Windows utilities like Partition Magic and Ghost with
> Ext2fs capability can no longer support FC2/3 partitions and I am not
> surprised that NFS has slightly broken!
Hi Brian,
thanks for the thought, but one point I didn't mentions is that I also see
the problem when writing to a disk mounted on a Solaris machine, wouldn't
that rule out an EXT2/3 issue?
> Are you saying that this problem seems to have gone away in FC3?
I only have one FC3 machine to try (my notebook) and that doesn't show the
problem, so, as far as I can tell, yes it has. That is the most confusing
part as I've done a source code comparison of that kernel with one under
FC2 and they are identical. I'll peer at the FC3 release notes a bit more.
Cheers,
Peter.
|