On Mon, Jan 05, 2015 at 12:19:13PM +0100, Otto Moerbeek wrote: > On Mon, Jan 05, 2015 at 11:33:13AM +0100, Jan Stary wrote: > > > On Jan 05 10:58:02, o...@drijf.net wrote: > > > On Mon, Jan 05, 2015 at 10:19:54AM +0100, Jan Stary wrote: > > > > > > > This is a daily mail from my Alix router. > > > > I do a dump in daily.local (see below) > > > > and most of the time it works just fine. > > > > Occasionaly though, the DUMP fails saying > > > > > > > > > DUMP: End of tape detected > > > > > DUMP: Volume 1 completed at: Mon Jan 5 01:30:44 2015 > > > > > DUMP: Volume 1 took 0:00:07 > > > > > DUMP: Volume 1 transfer rate: 2101 KB/s > > > > > DUMP: Change Volumes: Mount volume #2 > > > > > DUMP: fopen on /dev/tty fails: Device not configured > > > > > DUMP: The ENTIRE dump is aborted. > > > > > > > > That puzzles me, as I dump to stdout, > > > > redirecting to a file (see below). > > > > > > > > (I vaguely remember that the reason I switched from > > > > "dump -f file.dump ..." to "dump -f - ... > file.dump" > > > > was that I was advised her by a developer about > > > > the tape legacy of dump, but I forgot what exactly > > > > was the problem then and can't find it in archives.) > > > > > > > > Why would "dump -f - ... > file.dump" think > > > > that it reached an end of tape? > > > > > > Because dump is a bit dumb. You need to use -a, see man page. > > > > But I do, see the code below. > > Hmm indeed, then it's my guess you are running out of disk. The > numbers do not seems to warrant that, though. So I have no real clue. > Or did you play with tunefs -m ? > > -Otto
How about using the -n flag to find out what dump wants by being logged on as a user in group 'operator' while dump runs? / Raimo Niskanen, Erlang/OTP, Ericsson AB
