On Fri, 22 Aug 2008 10:29:05 +0200 (CEST), Oliver Fromme <[EMAIL PROTECTED]>
wrote:
> Unfortunately fsck isn't able to cope with any arbitrary
> level of damage. If certain kinds of unexpected problems
> occur, it throws in the towel. In theory it might be
> possible to deal with your particular
Polytropon <[EMAIL PROTECTED]> wrote:
> Allthough fsck_ffs 5 does seem to be able to calloc() the needed
> memory, it fails with the same message as fsck_ffs 7:
>
> fsck_ffs: bad inode number 306176 to nextinode
>
> Don't know what to do next. I may gather all information I
> have,
On Thu, 21 Aug 2008 18:49:17 +0200 (CEST), Oliver Fromme <[EMAIL PROTECTED]>
wrote:
> Polytropon <[EMAIL PROTECTED]> wrote:
> > On Thu, 21 Aug 2008 17:23:41 +0200, Kris Kennaway <[EMAIL PROTECTED]>
> wrote:
> > > Increase kern.maxdsiz.
> >
> > It seems that I don't have kern.maxdsiz:
> >
Polytropon <[EMAIL PROTECTED]> wrote:
> On Thu, 21 Aug 2008 17:23:41 +0200, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > Increase kern.maxdsiz.
>
> It seems that I don't have kern.maxdsiz:
>
> # sysctl kern.maxdsiz
> sysctl: unknown oid 'kern.maxdsiz'
>
> Am I looking a
First, thanks for the quick reply.
On Thu, 21 Aug 2008 17:23:41 +0200, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> Increase kern.maxdsiz.
It seems that I don't have kern.maxdsiz:
# sysctl kern.maxdsiz
sysctl: unknown oid 'kern.maxdsiz'
Am I looking at the wrong place? Allthough
Polytropon wrote:
Hi again!
I had problems running fsck_ffs of FreeBSD 5. In my particular
problem, version 5 seemed to help me more than version 7, which
stopped with this:
fsck_ffs: bad inode number 306176 to nextinode
Version 5 didn't seem to have this problem, but it did complain:
Hi again!
I had problems running fsck_ffs of FreeBSD 5. In my particular
problem, version 5 seemed to help me more than version 7, which
stopped with this:
fsck_ffs: bad inode number 306176 to nextinode
Version 5 didn't seem to have this problem, but it did complain:
fsck_ffs: c
