Hello, XFS gurus!
I used XFS on Linux fileserver (RedHat 7.3 with 2.4.18 kernel from
sgi.com, XFS v1.1) more then 1 year with no problems.
This week I upgraded to hardware RAID Promise FastTrak SX4000
(3x80G IDE drives in RAID5). XFS is on top of /dev/sda.
When copying files to this RAID XFS over the network
kernel frequently logs error messages like this:
Mar 18 17:45:30 server kernel: xfs_btree_check_sblock: Not OK:
Mar 18 17:45:30 server kernel: magic 0xaba7e24f level 1736 numrecs 39369
leftsib -593020325 rightsib 924741638
Checking /dev/sda produce this results:
#xfs_check /dev/sda
bad magic # 0x9e32e249 in btbno block 37/1
bad magic # 0xaba7e24f in btcnt block 37/2
bad magic # 0x47491577 in inobt block 37/3
agf_freeblks 265180, counted 0 in ag 37
agf_longest 265180, counted 0 in ag 37
When I ran xfs_repair -n (no actual repair - just messages):
#xfs_repair -n /dev/sda
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- scan filesystem freespace and inode maps...
bad magic # 0x9e32e249 in btbno block 37/1
expected level 0 got 42641 in btbno block 37/1
bad magic # 0xaba7e24f in btcnt block 37/2
expected level 0 got 1736 in btcnt block 37/2
bad magic # 0x47491577 in inobt block 37/3
expected level 0 got 58941 in inobt block 37/3
dubious inode btree block header 37/3
badly aligned inode rec (starting inode = 4251520898)
bad starting inode # (4251520898 (0x25 0xdd690f82)) in ino rec, skipping rec
badly aligned inode rec (starting inode = 3184326952)
bad starting inode # (3184326952 (0x25 0xb8ccf928)) in ino rec, skipping rec
badly aligned inode rec (starting inode = 3981325857)
bad starting inode # (3981325857 (0x25 0xe84e3621)) in ino rec, skipping rec
badly aligned inode rec (starting inode = 1706848453)
.
. about 250 these errors....
.
badly aligned inode rec (starting inode = 3045813498)
bad starting inode # (3045813498 (0x25 0xb58b6cfa)) in ino rec, skipping rec
- found root inode chunk
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- agno = 32
- agno = 33
- agno = 34
- agno = 35
- agno = 36
- agno = 37
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- agno = 32
- agno = 33
- agno = 34
- agno = 35
- agno = 36
- agno = 37
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
No modify flag set, skipping phase 5
Inode allocation btrees are too corrupted, skipping phases 6 and 7
No modify flag set, skipping filesystem flush and exiting.
------------------------------
Is this a hardware problem, bug in FastTrak driver or it is XFS-related?
Must I run xfs_repair in this situation?
Recommendations to correct this problems?
Thank you for assistance.
--
Alexander mailto:an_ivanov@xxxxxxx
|