Marc G. Fournier | 1 Oct 01:00 2003

fsck stall'd?


should I be able to get something out of either 'gdb /sbin/fsck <pid>' or
'truss -p <pid>' for an fsck process?

I tried truss -p, and it just sits there ... and gdb shows:

jupiter# gdb /sbin/fsck 361
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)...

/usr/361: No such file or directory.
Attaching to program: /sbin/fsck, process 361
0x804d6c5 in ?? ()
(gdb) bt
#0  0x804d6c5 in ?? ()
#1  0x804ae76 in ?? ()
#2  0x804ab7c in ?? ()
#3  0x804813e in ?? ()
(gdb) quit
The program is running.  Quit anyway (and detach it)? (y or n) y
Detaching from program: /sbin/fsck, process 361

I'm up to a 3.5hr fsck on a 100gb file system, and am worried it might
have stalled or soething, since all I have on the screen is:

(Continue reading)

Ian Dowse | 1 Oct 01:36 2003
Picon
Picon

Re: fsck stall'd?

In message <20030930195635.H94686 <at> ganymede.hub.org>, "Marc G. Fournier" writes:
>I'm up to a 3.5hr fsck on a 100gb file system, and am worried it might
>have stalled or soething, since all I have on the screen is:
>
>jupiter# fsck -y /dev/da0s1h
>** /dev/da0s1h
>** Last Mounted on /vm
>** Phase 1 - Check Blocks and Sizes
>** Phase 2 - Check Pathnames
>** Phase 3 - Check Connectivity
>** Phase 4 - Check Reference Counts

What is displayed if you press Control-T? Usually phases 1 and 2
are the slow ones, so it's unusual for it to become stuck there.

Ian
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Richard Coleman | 1 Oct 01:51 2003
Picon

new versions of openssl released today

New versions of openssl were released today that fix several security 
problems.  Looking at the security advisory below, they sound pretty 
minor.  But that could change as people dig into it.

http://www.openssl.org/news/secadv_20030930.txt

I'm not sure if this is important enough to affect the release of 4.9 or 
not.

Richard Coleman
richardcoleman <at> mindspring.com

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Marc G. Fournier | 1 Oct 01:54 2003

Re: fsck stall'd?


I always forget abotu ctl-T ... but now sure what its telling me either:

load: 1.01  cmd: fsck 361 [running] 15561.58u 39.38s 99% 95516k

99% CPU could be 'stuck in a loop' ...

but, this just pop'd up:

/dev/da0s1h: phase 4: cyl group 404 of 668 (60%)

so its apparently doing something *wipe brow*

need faster computers :)

On Wed, 1 Oct 2003, Ian Dowse wrote:

> In message <20030930195635.H94686 <at> ganymede.hub.org>, "Marc G. Fournier" writes:
> >I'm up to a 3.5hr fsck on a 100gb file system, and am worried it might
> >have stalled or soething, since all I have on the screen is:
> >
> >jupiter# fsck -y /dev/da0s1h
> >** /dev/da0s1h
> >** Last Mounted on /vm
> >** Phase 1 - Check Blocks and Sizes
> >** Phase 2 - Check Pathnames
> >** Phase 3 - Check Connectivity
> >** Phase 4 - Check Reference Counts
>
> What is displayed if you press Control-T? Usually phases 1 and 2
(Continue reading)

Damon Permezel | 1 Oct 02:15 2003

Re: 4.9-RC and bge

John,
you are correct. There is a slew of devices on the same IRQ:

ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> port 0xe800-0xe8ff mem 
0xfe203000-0xfe203fff irq 10 at device 6.0 on pci0
bge0: <Broadcom BCM5700 Gigabit Ethernet, ASIC rev. 0x7104> mem 
0xfcf00000-0xfcf0ffff irq 10 at device 6.0 on pci1
pci2: <unknown card> (vendor=0x9005, dev=0x00c5) at 6.1 irq 10
isp0: <Qlogic ISP 2200 PCI FC-AL Adapter> port 0xbc00-0xbcff mem 
0xeff00000-0xeff00fff irq 10 at device 8.0 on pci3
bge1: <Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105> mem 
0xead00000-0xead0ffff irq 10 at device 6.0 on pci14

However, prior to 1.3.2.28, I had zero spurious "link up" messages, and 
I have made no
h/w changes in the last 12 months.

I applied the patch to 1.3.2.28, and rebooted, and I am still suffering 
from the
spurious messages and intermittent lost packets.  Unfortunately, I have 
no idea what
version of if_bge.c I was running prior to the cvsup which landed me in 
this mess.

I have just reverted to 1.3.2.26, sans patch, and am about to boot 
that.....

On Wednesday, Oct 1, 2003, at 01:21 Australia/Brisbane, John Polstra 
wrote:

(Continue reading)

Shawn K. Quinn | 1 Oct 02:33 2003
Picon

Re: fsck stall'd?

On Tuesday 2003 September 30 18:00, Marc G. Fournier wrote:
> I'm up to a 3.5hr fsck on a 100gb file system, and am worried it
> might have stalled or soething, since all I have on the screen is:

The last time I had to fsck a filesytem anywhere near that big (60G+ /
var on a Usenet server running Linux), it took over a day. Would have 
been less had I not had to answer "yes" on the console every few 
minutes, take a break for lunch, or go home to sleep.

For future reference, I would only get worried if it's still there after 
a solid day.

--

-- 
Shawn K. Quinn
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Paul Saab | 1 Oct 02:48 2003

Re: 4.9-RC and bge

John Polstra (jdp <at> polstra.com) wrote:
> On 30-Sep-2003 Damon Anton Permezel wrote:
> > Recent SUP.
> > Installed on Dell PowerEdge 4600.
> > Getting tons of:
> > 
> > Sep 30 12:23:16 zige /kernel: bge0: gigabit link up
> > Sep 30 12:23:46 zige last message repeated 98 times
> 
> Check your dmesg output, and I bet you'll see that bge0 is sharing an
> IRQ with another device.  (If not, I'd like to hear about it.)  This
> bug was fixed in -current in revision 1.41 of if_bge.c, but it never
> got merged to -stable.  I have a patch for -stable that I am planning
> to commit after the source freeze lifts.  It is attached to this mail.
> Please let me know whether it solves your problem or not.

The only reason I never backported this was that loadandclear is not on
alpha and therefore would break on alpha.
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Michael W. Oliver | 1 Oct 03:12 2003

Re: panics on 24 hour boundaries

Folks,

I received grief a while back for not posting traces with panic reports, so 
would someone please confirm that what I posted last evening is what is 
needed?  If further information is required, I will do my best to help 
gather and post it.

Thanks much.

--

-- 
Mike
perl -e 'print unpack("u","88V]N=&%C=\"!I;F9O(&EN(&AE861E<G,*");'

Paul Saab | 1 Oct 03:13 2003

Re: 4.9-RC and bge

Damon Permezel (zeph <at> damon.com) wrote:
> The CVS log indicates that there have been 2 recent changes based on 
> BCM5701 errata.
> I suspect that this is hosing the 5700.

Without knowing what version you were running previously, it is hard to
say what broke you, but I dont think the No_CRC bit is the cause.

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Damon Permezel | 1 Oct 03:20 2003

Re: 4.9-RC and bge

I regressed all the way back to:

  * $FreeBSD: src/sys/dev/bge/if_bge.c,v 1.3.2.20 2003/02/06 21:36:40 ps 
Exp $
  * $FreeBSD: src/sys/dev/bge/if_bgereg.h,v 1.1.2.9 2003/02/06 21:36:40 
ps Exp $
  * $FreeBSD: src/sys/dev/mii/brgphy.c,v 1.1.2.6 2002/12/11 21:26:56 ps 
Exp $

and the problem went away.

I moved forward all the way back to the present, but modified the 
brgphy.c so as
not to enable Wirespeed ethernet, and that was not an issue.

I am moving back again so that I can get some work done.

I am willing to try whatever experiments you want.

Cheers.

On Wednesday, Oct 1, 2003, at 01:21 Australia/Brisbane, John Polstra 
wrote:

> On 30-Sep-2003 Damon Anton Permezel wrote:
>> Recent SUP.
>> Installed on Dell PowerEdge 4600.
>> Getting tons of:
>>
>> Sep 30 12:23:16 zige /kernel: bge0: gigabit link up
(Continue reading)


Gmane