I have one machine in particular of many running jfs, that every 1-2 weeks goes 
readonly after things like this:

ERROR: (device sdb): diUpdatePMap: inode 11015459 not marked as allocated in 
pmap!
ERROR: (device sdb): diUpdatePMap: inode 11015460 not marked as allocated in 
pmap!
ERROR: (device sdb): diUpdatePMap: inode 11015461 not marked as allocated in 
pmap!
ERROR: (device sdb): diUpdatePMap: inode 11015462 not marked as allocated in 
pmap!
ERROR: (device sdb): diUpdatePMap: inode 11015474 not marked as allocated in 
pmap!
ERROR: (device sdb): diUpdatePMap: inode 11015475 not marked as allocated in 
pmap!
ERROR: (device sdb): diUpdatePMap: inode 11015476 not marked as allocated in 
pmap!
ERROR: (device sdb): DT_GETPAGE: dtree page corrupt
ERROR: (device sdb): DT_GETPAGE: dtree page corrupt
ERROR: (device sdb): DT_GETPAGE: dtree page corrupt
ERROR: (device sdb): DT_GETPAGE: dtree page corrupt
ERROR: (device sdb): DT_GETPAGE: dtree page corrupt
ERROR: (device sdb): DT_GETPAGE: dtree page corrupt

The really fun part is every time we let fsck run (takes about 13 hours on the 
11T filesystem), it finds nothing.

I suspect bad ram, but week-long memtests rule it out.  I have replacment ram 
from a different manufacturer on the way.  

Could the above errors, with nothing found on fsck be because of ram, or should 
I be looking at something else?  The root filesystem is on the same raid 
controller (3ware) and nothing bad ever happens to it, but I'm open to 
alternate suggestions and will implement in cost order :)

tia,
dave



------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion

Reply via email to