linux-kernel - Re: ext3 corruption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200608092041.31359.mws@twisted-brains.org>
Date:	Wed, 9 Aug 2006 20:41:25 +0200
From:	Mws <mws@...sted-brains.org>
To:	"Molle Bestefich" <molle.bestefich@...il.com>
Cc:	"Michael Loftis" <mloftis@...ps.com>, linux-kernel@...r.kernel.org
Subject: Re: ext3 corruption

On Wednesday 09 August 2006 20:28, Molle Bestefich wrote:
> Michael Loftis wrote:
> > > Is there no intelligent ordering of
> > > shutdown events in Linux at all?
> >
> > The kernel doesn't perform those, your distro's init scripts do that.
> 
> Right.  It's all just "Linux" to me ;-).
> 
> (Maybe the kernel SHOULD coordinate it somehow,
>  seems like some of the distros are doing a pretty bad job as is.)
> 
> > And various distros have various success at doing the right thing.  I've had
> > the best luck with Debian and Ubuntu doing this in the right order.  RH
> > seems to insist on turning off the network then network services such as
> > sshd.
> 
> Seems things are worse than that.  Seems like it actually kills the
> block device before it has successfully (or forcefully) unmounted the
> filesystems.  Thus the killing must also be before stopping Samba,
> since that's what was (always is) holding the filesystem.
> 
> It's indeed a redhat, though - Red Hat Linux release 9 (Shrike).
> 
> > > Samba was serving files to remote computers and had no desire to let
> > > go of the filesystem while still running.  After 5 seconds or so,
> > > Linux just shutdown the MD device with the filesystem still mounted.
> >
> > The kernel probably didn't do this, usually by the time the kernel gets to
> > this point init has already sent kills to everything.  If it hasn't it
> > points to problems with your init scripts, not the kernel.
> 
> Ok, so LKML is not appropriate for the init script issue.
> Never mind that, I'll just try another distro when time comes.
> 
> I'd really like to know what the "Block bitmap for group not in group"
> message means (block bitmap is pretty self explanatory, but what's a
> group?).
> 
> And what will e2fsck do to my dear filesystem if I let it have a go at it?
> -
hi, 
what i am missing is a kind of information, what type of pc you own/use.

i personally builded a new one the last few days and also encountered
problems with ext3.

i do own a amd64 x2 5000+ with asus m2n32 ws pro motherboard.

i yesterday changed my root partition from ext3 to xfs and my problems
went away. so imho there might be some issues in having 64 bit systems,
dual processor and ext3 in combination.

kernel is 2.6.17

behaviour was like: 
filesystem became corrupted due to uncommitted transactions, resulting 
in manually "fsck" checking the partition, loads of errors i did correct, but
a lot of files got corrupted. i didn't check if the sata attached drives would also
fail on ext3 cause i had them already prepared for xfs.

regards
marcel





Content of type "application/pgp-signature" skipped