On Aug 22 10:54:38, [email protected] wrote: > On Aug 22 00:34:49, [email protected] wrote: > > 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... > > Ah, I forgot I had this problem before: > https://www.mail-archive.com/[email protected]/msg135224.html > > I tend to think now it's the disk space. This was a Monday morning dump, > when the /backup is "most full" with the previous week's dumps.[0-6]. > I rm(1) them before doing the fresh dump, but that space probably > only becomes available a bit later due to softdeps (I think).
... and so dump(8) wants to ask about the next volume, but there is no terminal, as this is a crin job - resulting in the err msg.
