--- Ash <[EMAIL PROTECTED]> a �crit�:
> Hi
> I was running a kind of crash test on JFS in which
> I do a large number of filesystem operations with several
> threads and
> crash the machine with a direct poweroff.
>
> On reboot, I ran fsck.jfs firstly with default options simply
> to replay the log.
> This succeeded without reporting and problems and said that
> the
> filesystem was marked clean.
> <snip>
> **Phase 0 - Replay Journal Log
> Filesystem is clean.
> <snip>
>
Hmm. I had the same problem here.
I have no idea why the filesystem is marked clean when it's
dirty. My idea is (i might be wrong) that after replaying the
journal fsck thinks that the filesystem is clean (after all
replaying the journal log means that the journal reflects the
state of the filesystem). This could lead in time to severe
filesystem corruption because the journal is not in sync
with the filesystem (i had this problem a cople of times in
the past).
My problem appeared after a kernel crash (bad hardware). That's
why i didn't report it because i thought to be caused by the
bad hardware (i.e. a poinetr gets corrupted and erroneous
data together with journal is written to the filesystem until
the crash)
Bye
Calin
=====
--
A mouse is a device used to point at
the xterm you want to type in.
Kim Alm on a.s.r.
Vous manquez d�espace pour stocker vos mails ?
Yahoo! Mail vous offre GRATUITEMENT 100 Mo !
Cr�ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/
Le nouveau Yahoo! Messenger est arriv� ! D�couvrez toutes les nouveaut�s pour
dialoguer instantan�ment avec vos amis. A t�l�charger gratuitement sur
http://fr.messenger.yahoo.com
_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
