--- Tony Harverson <[EMAIL PROTECTED]> wrote:
> Good morning,
>
> I'm noticing a problem which is probably related on my -current box. It
> seems to no longer be able to sync before shutting down. The config
> file for the kernel is attached to this message. When I shut it down,
> the final syn
ssage-
From: Pascal Giannakakis [mailto:[EMAIL PROTECTED]]
Sent: 12 February 2003 22:34
To: [EMAIL PROTECTED]
Subject: shutdown / reboot causes filesystem-errors
LO,
after I cvsupped the system to the most recent version, I found out what
the reason of locking during boot was (at least f
LO,
after I cvsupped the system to the most recent version, I found out what
the reason of locking during boot was (at least for me): corrupt FS. It
seems like a shutdown / reboot leaves the filesystem dirty, which means
to get the server up I need to run fsck from the fixit-image.
As usual th
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
Ollivier Robert <[EMAIL PROTECTED]>,
Mikhail Teterin <[EMAIL PROTECTED]>
Subject: fsck setting d_ino == 0 (was Re: filesystem errors)
In-Reply-T
In message <[EMAIL PROTECTED]>, Kirk McKusick writ
es:
>FFS will never set a directory ino == 0 at a location other
>than the first entry in a directory, but fsck will do so to
>get rid of an unwanted entry. The readdir routines know to
>skip over an ino == 0 entry no matter where in the directory
In message <[EMAIL PROTECTED]>, Michael Harnois writes:
>
>I don't have sufficient technical knowledge to know which of you is
>right; I would just ask that filesystem corruption caused by
>restarting from a hung system not cause a panic .
I removed the extra sanity check yesterday, so if you hav
On Sat, 28 Jul 2001 12:48:54 -0700, Kirk McKusick <[EMAIL PROTECTED]> said:
> FFS will never set a directory ino == 0 at a location other than
> the first entry in a directory, but fsck will do so to get rid
> of an unwanted entry. The readdir routines know to skip over an
> ino =
To: Michael Harnois <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: filesystem errors
In-Reply-To: Your message of "Wed, 25 Jul 2001 23:14:16 CDT."
<[EMAIL PROTECTED]>
Date: Thu, 26 J
In message <[EMAIL PROTECTED]>, Michael Harnois writes:
>
>The only result it generated was
>
>/usr/home/mdharnois off 120 ino 0 reclen 0x188 type 010 namelen 14 name '.fetc
>hmail.pid' [368]
>
>and that file is destroted and recreated every couple of minutes.
It's the directory (/usr/home/mdharn
On Thu, 26 Jul 2001 15:14:09 +0100, Ian Dowse <[EMAIL PROTECTED]> said:
> That should show up any directories that would fail that dirhash
> sanity check - there will probably just be one or two that
> resulted from some old filesystem corruption.
The only result it generated was
/u
In message <[EMAIL PROTECTED]>, Michael Harnois writes:
>I'm tearing my hair out trying to find a filesystem error that's
>causing me a panic: ufsdirhash_checkblock: bad dir inode.
>
>When I run fsck from a single user boot, it finds no errors.
>
>When I run it on the same filesystem mounted, it f
I'm tearing my hair out trying to find a filesystem error that's
causing me a panic: ufsdirhash_checkblock: bad dir inode.
When I run fsck from a single user boot, it finds no errors.
When I run it on the same filesystem mounted, it finds errors: but, of
course, it then can't correct them
--
M
12 matches
Mail list logo
