Dave, Thank you for you response. Frankly, I am also new to RHEL. I have been using FC* and SuSE. Since I need to fix this thing, I would appreciate if you could send me the patch, I can try that on failover machine. For now my options are to stay with RHEL. Management wants to use RHEL only and wants to keep emotional support they receive from Red Hat.
-Jai -----Original Message----- From: Dave Kleikamp [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2008 1:48 PM To: Jai Rangi Cc: [email protected] Subject: Re: [Jfs-discussion] JFS:Dtree error On Mon, 2008-03-31 at 12:18 -0700, Jai Rangi wrote: > Hello List, > > > > Just started using JFS few weeks back and have noticed the my server > crashes almost every week. I find this in the /var/log/messages. > > > > Mar 30 20:15:01 nfsgw2 crond(pam_unix)[3516]: session closed for user > root > > Mar 30 19:18:31 nfsgw2 kernel: ERROR: (device sdb1): JFS:Dtree error: > ino = 1102656, bn=67144499, index = -32746 > > Mar 30 19:18:31 nfsgw2 kernel: ERROR: (device sdb1): JFS:Dtree error: > ino = 1102656, bn=67144499, index = -32745 > > Mar 30 19:18:31 nfsgw2 kernel: ERROR: (device sdb1): JFS:Dtree error: > ino = 1102656, bn=67144499, index = -32744 > > Mar 30 19:18:31 nfsgw2 kernel: non-latin1 character 0x5351 found in > JFS file name > > Mar 30 19:18:31 nfsgw2 kernel: mount with iocharset=utf8 to access > > Mar 30 19:18:31 nfsgw2 kernel: non-latin1 character 0x174e found in > JFS file name > > Mar 30 19:18:31 nfsgw2 kernel: mount with iocharset=utf8 to access > > Mar 30 19:18:31 nfsgw2 kernel: non-latin1 character 0x174c found in > JFS file name > > Mar 30 19:18:31 nfsgw2 kernel: mount with iocharset=utf8 to access > > Mar 30 19:18:31 nfsgw2 kernel: non-latin1 character 0x174a found in > JFS file name > > Mar 30 19:18:31 nfsgw2 kernel: mount with iocharset=utf8 to access > > Mar 30 19:18:31 nfsgw2 kernel: ERROR: (device sdb1): JFS:Dtree error: > ino = 1102656, bn=67144499, index = -32743 > > Mar 30 19:18:31 nfsgw2 kernel: ERROR: (device sdb1): JFS:Dtree error: > ino = 1102656, bn=67144499, index = -32742 > > Mar 30 19:18:31 nfsgw2 kernel: ERROR: (device sdb1): JFS:Dtree error: > ino = 1102656, bn=67144499, index = -32741 > > > > From here the file system goes in Read Only mode. > > > > Here is the version information > > RedHat Enterprise 4.0 > > Kernel > > Linux nfsgw2 2.6.9-55.0.12.plus.c4smp #1 SMP Fri Nov 2 09:10:15 EDT > 2007 i686 i686 i386 GNU/Linux This is a really out-of-date kernel as far as jfs is concerned. Redhat maintains this kernel for the most part, but since they do not support JFS, they don't keep up with JFS bug fixes. (I don't know RHEL kernels that well, but I'm assuming this is one of their standard kernels.) > > fsck.jfs version 1.1.10, 19-Oct-2005 > > > > This is heavily used NFS server. Needless to say that one the drive > goes in Read Only mode, we are dead in water, until I fix it using > > fsck.jfs /dev/sdb1 > > Then everything works fine again for another week. > > > > Can anyone suggest the fix for this? I really can't recommend running jfs on a rhel 4 kernel. I did find a patch set of fifty patches that I once created against the 2.6.9-16.EL kernel, but that still only contains fixes as of September, 2005. I'd be happy to send it to you if you want to try to apply the patches, but I'm not sure what the results will be. You may also want to consider building a more modern mainline kernel for this server, since you're really not running something that Redhat supports anyway. > > Thank you, > > > > Jai Rangi -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
