Hi, I want to thank people for their help in solving this problem. Using strace finally gave me enough evidence to form a theory of what was going on. It turns out that we had a corrupted file system! (ext2_new_block: Free blocks count corrupted for block group 37.)
After rebooting the system and repairing the disk, the problem appears to be finally solved. I no longer get the "No space left on device" error message when running reconstruct. Thanks again, Fred Bacon Aerodyne Research, Inc. --On Monday, January 21, 2002 08:02:50 AM -0500 Fred Bacon <[EMAIL PROTECTED]> wrote: > --On Sunday, January 20, 2002 10:18:32 PM +0100 Noll Janos > <[EMAIL PROTECTED]> wrote: > >> Now do a system call trace on reconstruct >> (strace -o logfile.txt reconstruct blabla... on Linux), and maybe this >> can help you narrow down the problem. >> > > Excellent idea. Okay, I've done the strace. I won't send all 141 lines > to the list, but the relevant lines seem to be > > 0) = 0x40190000 write(6, "\241\2\213\rCyrus mailbox header\n\"The be"..., > 144) = -1 ENOSPC (No space left on device) >
