Very Computer

For the last few months I encounter this:

When doing rsync or cp _from_ system running 2.4 _to_ system running 2.5
get Input/output error errors with random files.

- 2-5 > 2.4 is OK!
- SRebootting, swapping kernel causes the error on the system running 2.4    
- Fast machine > slow machine or slow machine > fast machine
  is no different
- Both systems run same distribution
- Encountered since 2.4.20 with about 2.5.64 (my first 2.5 kernel)

Example:

/temp contains a couple of *files

system mhfl2 is running 2.5.6x to 2.5.70-mm3 mounted on
/mnt/mhfl2.

On system running 2.4.20 or 2.4.21-x:
  while ((1)); do cp -f /temp/* /mnt/mhfl2/temp; done

cp: cannot create regular file `/mnt/mhfl2/temp/blah: Input/output error
cp: writing `/mnt/mhfl2/temp/blah: Input/output error

Errors are random, so the files change every run, sometimes there are no errors,
sometimes thre are 3 errors

Q? Any (in)compatibility reason or should I investigate further?

Regards
Michael Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

Quote:> > When doing rsync or cp _from_ system running 2.4 _to_ system running 2.5
> > get Input/output error errors with random files.

> Do you use soft mounts?

Quote:

> If so, try hard instead. soft will fail, sooner or later.

Also, this does not explain why 2.5 > 2.4 (and 2.4 > 2.4) is OK - _never_ had any problem  

Regards
Michael

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Quote:

> > If so, try hard instead. soft will fail, sooner or later.

> I don't like hard mounts because these do not timeout.

Quote:

> Also, this does not explain why 2.5 > 2.4 (and 2.4 > 2.4) is OK - _never_ had any problem  

You just now found a case where sporadic errors show up more often.

soft-mount = fail upon (sporadic) error
hard-mount = retry (forever or until interrupted if used with 'intr') upon error

I always use hard,intr so that I can manually interrupt* jobs,
but also know that they do not randomly fail just because a few packets
get dropped on my network.  This seems to be the common setup, as far as
I know.

Cheers,

--
................................................................

:.........................: putrid forms of man                :
:   Jakob ?stergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

Quote:

> I always use hard,intr so that I can manually interrupt* jobs,
> but also know that they do not randomly fail just because a few packets
> get dropped on my network.  This seems to be the common setup, as far as
> I know.

I will try hard, intr

Regards
Michael

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

Please let the list know if it solves your problem or not - I'm sure
there are people who want to know if it doesn't, and if it does then the
solution will be in the archives for the next to find.

After all, I could be mistaken...  naaahh...   ;)

Cheers,

--
................................................................

:.........................: putrid forms of man                :
:   Jakob ?stergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

1. It worked to 2.4.20pre3 without a problem
2. Other OSes such as FreeBSD do not have issues writing to other OSes using
UDP soft mounts.

To me, there is something wrong with the changes that went in in 2.4.20pre4,
it should work as it does in pre3 and/or other unix OSes such as FreeBSD.
We should not have to work around the problem with hard links or using TCP
instead of UDP.

Andy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Even if I run them both against each other, the error only happens on 2.4 and
the frequency does not increase. This is not a simple timout problem.

I'll think it through and build some scripts so everone can reproduce it
and test it out.

Regards
Michael

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

     > To me, there is something wrong with the changes that went in
     > in 2.4.20pre4, it should work as it does in pre3 and/or other
     > unix OSes such as FreeBSD. We should not have to work around
     > the problem with hard links or using TCP instead of UDP.

Tough. 'soft' is not a priority of mine. It is a broken feature...

Cheers,
  Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Quote:

> Tough. 'soft' is not a priority of mine. It is a broken feature...

Regards
Michael

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

I've tried to debug and I have seen no timeouts.  I believe something is up
with the congestion routines that were added.

Yes, hard mounts work.  But so soft ones.  Linux should not have a
broken NFS.

Andy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

It is working dependably and I won't touch soft mounting mode again ...

Regards
Michael

--
Powered by linux-2.5.70-mm3, compiled with gcc-2.95-3 because it's rock solid

My current linux related activities in rough order of priority:
- Testing of Swsusp for 2.4
- Learning 2.5 kernel debugging with kgdb - it's in the -mm tree
- Studying 2.5 serial and ide drivers, ACPI, S3

The 2.5 kernel could use your usage. More info on setting up 2.5 kernel at
http://www.veryComputer.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/