On Thu, Jun 03, 2004 at 09:28:35AM +1000, Nathan Scott wrote:
> On Wed, Jun 02, 2004 at 10:16:26AM +0200, Hendrik Visage wrote:
> > On Wed, Jun 02, 2004 at 06:10:13PM +1000, Nathan Scott wrote:
> > > still help me greatly. The common theme from the two folks
> > > who sent me info is use of rsync, and thats what I was using
> > > when I hit it too.. but subsequent runs on exactly the same
> > > data and devices has proved unsuccessful at reproducing. I'll
> > > keep plugging away.
> > I've found that when I do "ethernet" rsyncs, I use a different data set
> > (huge directories like the SuSE 9.1 DVDs), as I copy part, it hangs,
> > copy another part, it hangs etc.
> by "hangs" do you mean the kernel becomes unresponsive? panics?
> your shell prompt never returns?
Kernel and console unresponsive.
Nothing on console.
I initiated the rsync from another machine (ie. xterm or console), while I
watched the console on the x86_64. The moment the rsync stopped sending
data from the i386, the x86_64's console is also unresponsive. From then
on pings fail, I don't see any updates to the screens (were using "vmstat 1"
in one test), and a reset/power-cycle is needed to revive.
> are you seeing filesystem corruption or "just" these hangs?
Haven't yet noticed corruption, as I were rsyncing, so it checksummed and
sent, and the compressed files is difficult check for corruption if
only half sent in anycase :(