Messages in this thread | | | Subject | Re: 2.4.23 + Preempt, JFS Corruption. | From | Dave Kleikamp <> | Date | Wed, 10 Dec 2003 11:40:12 -0600 |
| |
On Tue, 2003-12-09 at 15:34, Joshua Schmidlkofer wrote: > Howdy, > > We are migrating from ext3 to jfs and had a weird error. We have a > dual pentium III 1.4 ghz system. We have 4GB of ram, and a Mylex > AcceleRAID 170 [DAC960] controller. Intel pro/100 nics, nothing else too > special. The motherboard chipset is ServerWorks. We added a 40GB ide > drive to the onboard controller. It has jfs on it, and we are using > this for the migration. We have been backing up to it for a few days, > and it went read-only on us. > > I have dtree page corrupt errors, but no hardware errors. jfs fsck > errors out as well.
jfs_fsck reports the errors, but is running read-only. Did you run it with "-n"? In read-write mode, it should "fix" the problem (by removing the corrupt directory and placing its contents in lost+found).
I've seen a few scattered reports of corrupted directories lately, so there may be a race in the JFS code that I haven't found yet. I'd be interested if anyone has found a reproducible way of causing any JFS corruption.
Thanks, Shaggy -- David Kleikamp IBM Linux Technology Center
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |