From: Stelian P. <ste...@fr...> - 2002-11-18 08:33:44
|
On Sun, Nov 17, 2002 at 11:30:56AM -0800, Chris de Vidal wrote: > > > By the way, this: > > > dump 0bdsf 64 100000 100000 - /tmp | ssh > > user@remote > > > "dd bs=64k of=test.dump" > > > was already thought of. Won't work with this > > setup. > > > > Why ? It should work and it is definately the > > recommended way <snip> > > And it has worked well for me in the past. > > This setup, a web-based GUI backup, only allows me to > execute a pre and post backup script. The actual > backup uses dump and can't be altered to also include > ssh, so I had been testing out dumping through a FIFO. Ok. > As I said, it _almost_ works. I don't get it. > > So, do you have an idea why dump hangs when the output > file is a FIFO? The file system is ext2 and kernel is > 2.2.16. I'd really appreciate it. > > Do you suppose it matters that the FIFO is being > copied over SSH? Well, I just tried it here and it works correctly for me: mkfifo /tmp/FIFO dd bs=64k if=/tmp/FIFO | ssh user@host "dd bs=64k of=test.dump" & dump -0 -b 64 -f /tmp/FIFO / What version of dump are you using ? If it is not the latest one (0.4b32), please retry with it. Also, it could be useful to run strace (using strace -f dump...), it will show all open/read/write calls on the fifo, maybe this will show what happens. Stelian. -- Stelian Pop <ste...@fr...> Alcove - http://www.alcove.com |