Re: race-to-the-root, hello anyone out there?
On Mon, Aug 13, 2001 at 06:01:55PM -0400, Garrett Wollman wrote: > < said: > > I should have mentioned this. > > /tmp is on /, which is UFS, mounted noatime and with softupdates enabled. > > Plenty of freespace:/dev/da0s1a 1.3G 843M 361M 70% / > > Same thing happens to me, but it's when sending mail (!) so there's no > necessary correlation to the particulars of the filesystem. Typically I am doing mail also -- but my editor+MTA writes temp files before sending the mail out. > I note that it doesn't lock up all the way immediately, Same. I can do anything on the machine as long as it doesn't involve a disk access. Ctrl-Alt-F1 to get out of X works fine, but a C-A-D after that to reboot will hang. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: race-to-the-root, hello anyone out there?
< said: > I should have mentioned this. > /tmp is on /, which is UFS, mounted noatime and with softupdates enabled. > Plenty of freespace:/dev/da0s1a 1.3G 843M 361M 70% / Same thing happens to me, but it's when sending mail (!) so there's no necessary correlation to the particulars of the filesystem. I note that it doesn't lock up all the way immediately, but I can continue the race with a `ps' which gets it reliably all the way to the root. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: race-to-the-root, hello anyone out there?
I should have mentioned this. /tmp is on /, which is UFS, mounted noatime and with softupdates enabled. Plenty of freespace:/dev/da0s1a 1.3G 843M 361M 70% / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
race-to-the-root, hello anyone out there?
Hello?? Those that have committed to /sys in the past 1.5mo, awake? I am continuing to suffer thru what appears to be inode deadlocks where the resulting race-to-the-root soon locks everything up solid. Tried to figure out how to reproduce it on demand. All I can characterize is the file activity that FUBARs the system is in /tmp. What ideas do people have to solve the problem? crashdump are an impossibility due to the locked up disk system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
