Barrapunto

Problema: "Subject: 2.4.15 problem: deleted inodes still present in ext2 directories after shutdown"

Razón: "Sigh... Supposed fix to problems with stale inodes was completely broken (2.4.15-pre9 y 2.4.15)

Solución:

Subject: Re: 2.4.15 + fs corruption.

From: Alexander Viro

Date: Fri, 23 Nov 2001 17:56:43 -0500 (EST)

Return-Path:

Delivered-To: jdomingo@localhost

Delivered-To: jldomingo@softhome.net

X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs

To: war

cc: linux-kernel@vger.kernel.org

In-Reply-To:

Sender: linux-kernel-owner@vger.kernel.org

Precedence: bulk

X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, 23 Nov 2001, war wrote:

> Is 2.4.15 ok to use?

> Many people are experiencing filesystem corruption?

>

> As long as you patch the kernel with Al Viro's patch it should be ok,

> right?

In theory. Again, as a workaround - sync before umount (and don't boot

unpatched 2.4.15/2.4.15-pre9 again, obviously).

Breakage happens when you umount filesystem (_any_ local filesystem, be

it ext2, reiserfs, whatever) that still has dirty inodes.

IOW, if you are running 2.4.15 - build a patched kernel, install it and

do the following:

                * switch to single-user

                * sync

                * umount everything non-buys

                * remount the rest read-only

                * turn the thing off

                * boot with patched kernel or with anything before 2.4.15-pre9

-

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

the body of a message to majordomo@vger.kernel.org

More majordomo info at http://vger.kernel.org/majordomo-info.html

Please read the FAQ at http://www.tux.org/lkml/