Re: bgfsck hosed (lockups) in -current?
- From: Robert Watson <rwatson@xxxxxxxxxxx>
- Date: Wed, 11 Jul 2007 22:37:54 +0100 (BST)
On Wed, 11 Jul 2007, Alfred Perlstein wrote:
I have current as of last week.
I noticed that if I needed a bgfsck on ufs when rebooting my system would lock up almost immediately. Everything would deadlock.
If I rebooted single user and did a regular "fsck -y" then continued to boot, I'd be OK.
Has anyone else experienced this? I'm going to update to the most recent current and get more information (which wait channels etc) but wanted to know if anyone knew about this.
I recall seeing a LOT of fixes for various deadlocks in snapshots and bgfsck going in lately, but nothing that looked to me as if it'd trigger a regression.
I'm not seeing this either -- have you tried running a manual fsck to see if it turns up anything deeply unsatisfying that could be causing bgfsck some bother?
Robert N M Watson
Computer Laboratory
University of Cambridge
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: bgfsck hosed (lockups) in -current?
- From: Alfred Perlstein
- Re: bgfsck hosed (lockups) in -current?
- References:
- bgfsck hosed (lockups) in -current?
- From: Alfred Perlstein
- bgfsck hosed (lockups) in -current?
- Prev by Date: Re: Nvidia-driver and current lead system reboot with no error message
- Next by Date: Re: bgfsck hosed (lockups) in -current?
- Previous by thread: Re: bgfsck hosed (lockups) in -current?
- Next by thread: Re: bgfsck hosed (lockups) in -current?
- Index(es):
Relevant Pages
|
