Date: Tue, 31 May 2011 17:40:13 GMT From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= <kes-kes@yandex.ru> To: freebsd-i386@FreeBSD.org Subject: Re: i386/157460: system hungup while fsck background check Message-ID: <201105311740.p4VHeDum069681@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/157460; it has been noted by GNATS. From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= <kes-kes@yandex.ru> To: bug-followup@FreeBSD.org, kes-kes@yandex.ru Cc: Subject: Re: i386/157460: system hungup while fsck background check Date: Tue, 31 May 2011 20:39:43 +0300 Hi. I wait about one an hour. as you can see. #man kill does not show any info. it is locked, as I think, by fsck (see top) very interesting fack that #kill -KILL #kill -ABRT #kill -TERM those do not! kill a process, not 'man', not 'fsck' I just press CTRL+ALT+DEL and see that system stale on 'syncing disks 22 2 2 2 2 2 2 2 2 2 1 timeout 291 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 1 1 1 2 timeout 291 ' I wait one an hour yet, but nothing happen. I 'reset' computer. go to single mode. fsck -y it take about 10min to clean the disk. I reboto and get system to work. I think that 'fsck' do interactive fscking in backgroupd. so I add 'fsck_y_enable="YES"' to rc.conf as I did for my other systems. -- С уважением, Коньков mailto:kes-kes@yandex.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201105311740.p4VHeDum069681>