Matt Dillon <[EMAIL PROTECTED]> writes:
> How fast a link was the cvsup running through?
A 640/384 kbps ADSL link.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:Matt Dillon <[EMAIL PROTECTED]> writes:
:> To date nearly all the reported corruption has been to directories
:> and not to file contents. Does this hold for you as well? Only
:> the directory was corrupted and not any files?
:
:Umm, the end of the cvsup log was padded with zeroes,
Matt Dillon <[EMAIL PROTECTED]> writes:
> To date nearly all the reported corruption has been to directories
> and not to file contents. Does this hold for you as well? Only
> the directory was corrupted and not any files?
Umm, the end of the cvsup log was padded with zeroes, but I
:Matt Dillon <[EMAIL PROTECTED]> writes:
:> How old a kernel are you running?
:
:Maybe five days old.
:
:DES
:--
:Dag-Erling Smorgrav - [EMAIL PROTECTED]
That has all of our fixes to date. It fits the M.O. of the problem I've
been trying to track down, but I have yet to be able to
Matt Dillon <[EMAIL PROTECTED]> writes:
> How old a kernel are you running?
Maybe five days old.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:
:On Wed, Mar 14, 2001 at 04:39:53PM -0800, Matt Dillon wrote:
:
:> fsck all of your filesystems from single-user to remove the possibility
:> of 'old' corruption (as in 'fsck', not 'fsck -p').
:
:So if an fsck -f doesn't bomb out, the filesystem should be in an okay
:state?
:
:- alex
On Wed, Mar 14, 2001 at 04:39:53PM -0800, Matt Dillon wrote:
> fsck all of your filesystems from single-user to remove the possibility
> of 'old' corruption (as in 'fsck', not 'fsck -p').
So if an fsck -f doesn't bomb out, the filesystem should be in an okay
state?
- alex
To Unsubscri
:I was cvsupping the GNATS database (the *entire* GNATS database, that
:is - I didn't already have a copy) when I got this panic:
How old a kernel are you running?
Kirk and I have been attempting to locate the filesystem bitmap
corruption for months. We've fixed a number of bugs but
I was cvsupping the GNATS database (the *entire* GNATS database, that
is - I didn't already have a copy) when I got this panic:
kernel: type 12 trap, code=0
Stopped at -0xfb8f:andb%al,0x73(%ecx,%ebp,2)
db> trace
APTmap(c5f763b8) at -0xfb8f
ffs_balloc(d06f9e3c,d0ab0de0,0,c22e7280,
