Date: Tue, 24 Sep 1996 15:34:38 +0200 (MET DST) From: "Julian H. Stacey" <jhs@freebsd.org> To: joerg@freebsd.org Cc: current@freebsd.org Subject: ctm & disc full Message-ID: <199609241334.PAA07476@vector.jhs.no_domain>
next in thread | raw e-mail | index | archive | help
Hi Joerg, This addressed to you (cc'd current), as you wrote CTM man page... Maybe we could add something to `man ctm' regarding if a disc gets full .... I ran (cd /pub/freebsd/work/current/src ; ctm -v \ /pub/freebsd/ref/current/ctm/ctm/src-cur/deltas/src-cur.22[0-9]*.gz ) & saw this: + > FN usr.sbin/adduser/adduser.perl + All done ok + Working on </pub/freebsd/ref/current/ctm/ctm/src-cur/deltas/src-cur.2215.gz> + > DM contrib/gcc + ..... + > FM contrib/gcc/obstack.h + + /usr2: write failed, file system is full + contrib/gcc/obstack.h: No space left on device + /pub/freebsd/ref/current/ctm/ctm/src-cur/deltas/src-cur.2215.gz Fatal error: Assert failed. + Exit(96) I then ran it again & it started to apply, not noticing that the .ctm_status represented a state the tree didnt really have. + Delta number 2215 is already applied; ignoring. + Working on </pub/freebsd/ref/current/ctm/ctm/src-cur/deltas/src-cur.2216.gz> + > FS .ctm_status + > FN contrib/tcl/README No great problem if applying manually, But could be problematic for those who have procmail applying ctm patches in background mode, if the disc fills up. In an ideal world .ctm_status could record both start of application & end of succesful application, but that'd need a patch, & some discussion, meantime, could you document the hazard ? Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609241334.PAA07476>