bcaa5b7b1c
writing data to the file system, if the "optimal" file system I/O operation block size is less than TP_BSIZE, leave fssize alone (i.e. at its default setting of MAXBSIZE). This was causing restore's stack to be trashed, because the end-of-buffer checking/flushing code around line 680 would never notice that the buffer was full (because it'd be comparing a buffer segment index, which would always be >= 1, to fssize / TP_BSIZE, which could be zero in that case), and would keep filling and filling and filling...