Ext3 corruption using cluster

Stefano Cislaghi s.cislaghi at gmail.com
Sat May 9 08:25:57 UTC 2009


Maybe... looking around some solutions can be:
- maximize journal size
- journaling all data and metadata (mount -o data=journal)


Ste


2009/5/9 Christian Kujau <lists at nerdbynature.de>

> On Thu, 7 May 2009, Stefano Cislaghi wrote:
> > During a normal switch, operations done are:
> > - oracle shutdown abort
> > - oracle listernet shutdown
> > - umount fs (using  umount -l )
>
> I'm not all too Oracle cluster savvy, but this lazy umount looks
> kinda suspicious. From the manpage:
>
>   > Detach the filesystem from the filesystem hierarchy now, and cleanup
>   > all references to the filesystem as soon as it is not busy anymore
>
> My wild guess: node1 has been shut down, did a lazy umount, so that
> node2 could mount it but node1 was still writing to the fs (i.e. it was
> still in use)?
>
> Christian.
> --
> Bruce Schneier's first program was encrypt world.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20090509/1a087de7/attachment.htm>


More information about the Ext3-users mailing list