Hello all, I've a cluster with an oracle database. The shared filesystem is provided from a SAN and there's LVM and ext3 fs. I've experienced some problem. During a normal switch of my cluster remounting FS on second node gave me problem. FS is corrupted. During a normal switch, operations done are: - oracle shutdown abort - oracle listernet shutdown - umount fs (using umount -l ) Also, if a system crash (support for a power loss) I'm really not sure that FS can be remounted. In fact FS is mounted and become readonly. There's a way to prevent this problem? Maximize journal size? Removing the remount readonly due to a supposed FS problem? Thanks Stefano -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20090507/657565b2/attachment.htm>
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.