freebsd stable - Sep 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:

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

Now, CPU usage seems to be continuing to climb, according to ps:

jupiter# !ps
ps aux | grep fsck
root      361 99.0  2.3 95572 95500  p0  R+    4:21PM 206:19.31 fsck -y
/dev/da0s1h
jupiter# !ps
ps aux | grep fsck
root      361 99.0  2.3 95572 95500  p0  R+    4:21PM 206:23.51 fsck -y
/dev/da0s1h

so I'm guessing that it is still working fine, and I'm being paranoid,
but
... ?

thanks ...

In message <20030930195635.H94686@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

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