------- Additional Comments From driver@xxxxxxxxxxxx 2004-12-02 13:19 PDT
I got the error on the old kernel as well. I can reproduce easily with xfsdump.
Here is the output of xfsdump:
xfsdump: using file dump (drive_simple) strategy
xfsdump: version 3.0 - Running single-threaded
xfsdump: WARNING: no session label specified
xfsdump: level 0 dump of micro.jpl.nasa.gov:/
xfsdump: dump date: Thu Feb 12 11:18:21 2004
xfsdump: session id: d0d6ffd2-60bd-4c96-9a69-6ae71f242f00
xfsdump: session label: ""
xfsdump: ino map phase 1: skipping (no subtrees specified)
xfsdump: ino map phase 2: constructing initial dump list
xfsdump: WARNING: failed to get bulkstat information for inode 29360279
xfsdump: WARNING: failed to get bulkstat information for inode 29360289
xfsdump: WARNING: failed to get bulkstat information for inode 29360295
xfsdump: syssgi( SGI_FS_BULKSTAT ) on fsroot failed: Input/output error
xfsdump: Dump Status: ERROR
I ran badblocks on this disk (read-only) and it found no errors with the disk. I
didn't have time to-do a read-write test nor can I destroy data on the
I ran xfs repair and got this:
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
zero_log: head block 3029 tail block 3029
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost+found (if it exists) ...
- check for inodes claiming duplicate blocks...
- agno = 0
data fork in regular inode 3523176 claims used block 223904
xfs_repair: dinode.c:2429: process_dinode_int: Assertion `err == 0' failed.
Let me know what else I can do?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.