On Mon, 22 Aug 2016, Jan Stary wrote: > Occasionally, this what tha daily dump of my 5.9-beta/i386 says: ...
> > DUMP: Volume 1 started at: Mon Aug 22 01:30:25 2016 > > DUMP: dumping (Pass III) [directories] > > DUMP: dumping (Pass IV) [regular files] > > DUMP: End of tape detected ... > The daily.local is below - basically just a wrapper > around the dumps and tars. The dump call itself is > > dump -$l -a -u -f - $fs > $f 2> $BKPLOG The "End of tape detected" message means write() failed or repeatedly refused to write the full output. For a disk file like you're using, that probably means one of these errors: - ENOSPC: file system full (out of disk blocks) - EDQUOT: reached user's disk quota - EFBIG: reached the file size limit (ala ulimit -f) - EIO: disk is dying If you're sure that it *can't* be any of those, then I suppose you could hack dump to report the exact error... ... > > DUMP: fopen on /dev/tty fails: Device not configured > > DUMP: The ENTIRE dump is aborted. ... > I wonder how exactly does dump find /dev/tty "not configured". Is the > redirection of stdout what makes dump deal with tty in the first place? > When I log into the machine an run sh /etc/daily.local manually, > everything goes fine. Most nights, the daily.local cronjob goes fine too. When a process opens /dev/tty, the kernel (mostly) acts like it opened its controlling terminal device, whichever that is. If it doesn't have a controlling terminal then you get that error. c.f. cttyopen() and the cttyvp() macro in sys/kern/tty_tty.c Philip Guenther
