On Tue, 18 Mar 2003, John Straiton wrote:
> While I appreciate the background fsck's that 5.0 provides, it appears
> that there are problems with writing to a drive that is still under the
> scrutiny of a fsck (tell me if I'm wrong).
>
> 'Fer instance, today I brought up a machine that has a 119GB /home
> partition and then tried to FTP to it. The FTP got to 32kB and hung....
> Attempts to reconnect resulted in connections but the inability to STOR.
>
> When I do a top, I can see
>
> PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU
> COMMAND
> 450 root -4 4 632K 376K bufwai 0:01 0.00% 0.00% fsck_ufs
>
> So I guess it's still running.
Maybe not - 'bufwai' says that its waiting for something and 0.00%
indicates thats its not actually running anything on the CPU.
My guess is that the disk is dying and taking a long time to comlete IO.
Do a checkup on your disk..
> Here's the question:
> I need a solution so that this machine is immediately available when it
> starts taking connections into inetd. What options have I on this
> problem? Is there an override to the write-deny (and if so, what risks
> inclusive to it) or a way to keep the machine from coming up until the
> fsck is done? (ala 4.X style..)
>
> I have a machine at home where the boot drive is 160GB that would
> benefit from the answer as well. If it has to fsck, I have to currently
> take it to single-user because if I let it background fsck, the damn
> thing will hang (still process packets through the NATd but you can't
> type at all or login for example) a few moments after the login: prompt
> shows up.
>
> Thanks,
> John Straiton
> [EMAIL PROTECTED]
> Clickcom, Inc
> 704-365-9970x101
>
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
