Possible Filesystem Corruption
agley at optusnet.com.au
Wed Aug 10 03:51:46 PDT 2005
Matthew Dillon <dillon at xxxxxxxxxxxxxxxxxxxx> writes:
> : I am using HEAD last built about a week ago. For a while I have been
> : getting a random number of disks in the line that says syncing disks
> : when shutting down. Today I had a few more problems i.e. in /bin/csh
> : and /bin/tcsh I got
> How long as 'for a while' ? Did you mean you were getting a 'random
> number of errors' instead of a 'random number of disks' in the
> sentence above?
Probably about a week or 10 days, I meant sometimes it would say
syncing disks...9 sometimes syncing disks...22
> : /bin/pwd : 1 syntax error: ``( '' unexpected
> : also /usr/src was no longer seen as a directory and ls said it had a
> : bad file descriptor for /usr/src. Then when shutting down I got a
> : panic. I didn't know what to do at db> but typing panic ? got me a
> : reboot and the subsequent fsck seems to have fixed everything I can
> : check. There was something about a SUPERBLOCK but it was too fast for
> : me to record. Not all filesystems were checked probably because the
> : system was already in single user mode when it paniced ?.
> : Here is the panic FYI, it is hand transcribed.
> :syncing disks... 2
> :panic: umount: dangling vnode
> :Trace beginning at frame 0xc5423ae0
> :panic(c04f58af,c05b14a0,c04f7fc7,c5423b10,0) at panic+0x99
> :dounmount(c0df6588,80000,c5420f00,1,c0df6588) at dounmount+0x23a
> : Hope this helps,
> : John Duncan
> It kinda sounds like something got smashed in your filesystem, but
> the problem needs to be characterized more as I do not have any
> similar bug reports from anyone else.
> Check the disklabel on the disk to make sure the partitions are
> not overlapping (e.g. 'disklabel ad0').
# size offset fstype [fsize bsize bps/cpg]
a: 524288 0 4.2BSD 1024 8192 22 # (Cyl. 0 - 32*)
b: 524288 524288 swap # (Cyl. 32*- 65*)
c: 30713634 0 unused 0 0 # (Cyl. 0 - 1911*)
d: 524288 1048576 4.2BSD 1024 8192 22 # (Cyl. 65*- 97*)
e: 524288 1572864 4.2BSD 1024 8192 22 # (Cyl. 97*- 130*)
f: 16777216 2097152 4.2BSD 2048 16384 89 # (Cyl. 130*- 1174*)
g: 11839266 18874368 4.2BSD 1024 8192 22 # (Cyl. 1174*- 1911*)
f which is /usr looks a little strange ?
> Are you getting any disk error messages in the dmesg output or
> on the console during shutdown/reboot ?
No, though when booting I get CRC errors but FreeBSD gives me
them as well and also drops DMA, but NetBSD and OpenBSD operate in
DMA mode without a problem. At the moment I also have Debian
Stable on this disk as well, no problems.
> Also note that HEAD is going a lot of changes right now, though
> nothing we are doing should have the effect you've described.
Yes I know, I am running HEAD to try to learn something,
nothing ever goes wrong with Preview or Release for me but I
might be over my head.
All the best,
More information about the Users