From: Joshua Schmidlkofer <joshua@imr-net.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.4.23 + Preempt, JFS Corruption.
Date: Tue, 09 Dec 2003 13:34:35 -0800 [thread overview]
Message-ID: <1071005675.32237.97.camel@bubbles.imr-net.com> (raw)
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.
We saw a load of errors like this in the dmesg:
ERROR: (device ide0(3,1)): DT_GETPAGE: dtree page corrupt
ERROR: (device ide0(3,1)): DT_GETPAGE: dtree page corrupt
ERROR: (device ide0(3,1)): DT_GETPAGE: dtree page corrupt
ERROR: (device ide0(3,1)): DT_GETPAGE: dtree page corrupt
ERROR: (device ide0(3,1)): DT_GETPAGE: dtree page corrupt
ERROR: (device ide0(3,1)): DT_GETPAGE: dtree page corrupt
ERROR: (device ide0(3,1)): DT_GETPAGE: dtree page corrupt
jfs fsck reports:
jfs_fsck version 1.1.4, 30-Oct-2003
processing started: 12/9/2003 9.3.38
The current device is: /dev/hda1
Block size in bytes: 4096
Filesystem size in blocks: 9769520
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
**Phase 2 - Count links
Incorrect link counts detected in the aggregate.
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
File system object DF1323074 is linked as:
/slash/home/virtual/[innocent protected]
cannot repair the data format error(s) in this directory.
cannot repair DF1323074.
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
**Phase 7 - Verify File/Directory Allocation Maps
**Phase 8 - Verify Disk Allocation Maps
Incorrect data detected in disk allocation structures.
Incorrect data detected in disk allocation control structures.
39078080 kilobytes total disk space.
292595 kilobytes in 88974 directories.
15368020 kilobytes in 1074664 user files.
0 kilobytes in extended attributes
633991 kilobytes reserved for system use.
23368664 kilobytes are available for use.
File system checked READ ONLY.
ERRORS HAVE BEEN DETECTED. Run fsck with the -f parameter to repair.
Filesystem is dirty.
(the [innocent protected] just obfuscates the path)
next reply other threads:[~2003-12-09 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 21:34 Joshua Schmidlkofer [this message]
2003-12-10 17:40 ` Dave Kleikamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1071005675.32237.97.camel@bubbles.imr-net.com \
--to=joshua@imr-net.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome