Then this is why you get the error
>
> >
> > If so, try hard instead. soft will fail, sooner or later.
>
> I don't like hard mounts because these do not timeout.
You get what you ask for, then: timeouts
>
> Also, this does not explain why 2.5 > 2.4 (and 2.4 > 2.4) is OK - _never_ had any problem
Leave it running for a million years, and I'm sure a sporadic error will
show up in those two situations as well.
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 hanging 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,
-- ................................................................ : jakob@unthought.net : And I see the elder races, : :.........................: 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 the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/