June 8, 201115 yr Running unraid 4.7 on a HP Proliant Microserver. Processor Dual-Core Processor AMD Athlon II Processor Model NEO N36L (1.30 GHz, 15W, 2MB) Cache Memory 2x 1MB Level 2 cache Chipset AMD RS785E/SB820M Memory Protection ECC Memory Type PC3-10600E unbuffered DDR3 ECC operating at 800MHz 1GB (1x1GB) Network Controller Embedded NC107i PCI Express Gigabit Ethernet Server Adapter 1 PCI-e x16 x16 1h Half height, half length slot 2 PCI-e x1 x1 2h Half height, half length slot Storage Controller Integrated SATA controller with embedded RAID (0, 1) Interfaces Graphics On board VGA USB 2.0 Ports 7 total (2 rear, 4 front panel, 1 internal) Network RJ-45 (Ethernet) 1 (10/100/1000 bits/s) eSATA Gen 2 1 rear Graphics 128MB shared supporting 1920x1200 @ 60Hz Industry Standard Compliance ACPI V2.0 Compliant PCI 2.3 Compliant PXE Support WOL Support IPMI 2.0 compliant USB 2.0 SATA Gen 2 I was trying to delete some files (actually move them from one physical disk to another). I found during the move it was setting that particular disk read only because reiserfs was crashing. Jun 8 11:34:39 Mars kernel: REISERFS error (device md2): vs-4080 _reiserfs_free_block: block 260637938: bit already cleared Jun 8 11:34:39 Mars kernel: REISERFS (device md2): Remounting filesystem read-only Jun 8 11:34:39 Mars kernel: REISERFS error (device md2): vs-4080 _reiserfs_free_block: block 260638041: bit already cleared Jun 8 11:34:39 Mars kernel: REISERFS error (device md2): vs-4080 _reiserfs_free_block: block 260643382: bit already cleared Jun 8 11:34:40 Mars kernel: ------------[ cut here ]------------ Jun 8 11:34:40 Mars kernel: WARNING: at fs/reiserfs/journal.c:3358 journal_end+0x5b/0xbc() Jun 8 11:34:40 Mars kernel: Hardware name: ProLiant MicroServer Jun 8 11:34:40 Mars kernel: Modules linked in: md_mod xor ahci Jun 8 11:34:40 Mars kernel: Pid: 3468, comm: rm Tainted: G W 2.6.32.9-unRAID #8 Jun 8 11:34:40 Mars kernel: Call Trace: Jun 8 11:34:40 Mars kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 Jun 8 11:34:40 Mars kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 Jun 8 11:34:40 Mars kernel: [<c10c0547>] journal_end+0x5b/0xbc Jun 8 11:34:40 Mars kernel: [<c10af87d>] reiserfs_delete_inode+0x7b/0xae Jun 8 11:34:40 Mars kernel: [<c10af802>] ? reiserfs_delete_inode+0x0/0xae Jun 8 11:34:40 Mars kernel: [<c107b14f>] generic_delete_inode+0x75/0xdb Jun 8 11:34:40 Mars kernel: [<c107b1c6>] generic_drop_inode+0x11/0x4c Jun 8 11:34:40 Mars kernel: [<c107aabd>] iput+0x4b/0x4e Jun 8 11:34:40 Mars kernel: [<c1074d88>] do_unlinkat+0xb4/0xf9 Jun 8 11:34:40 Mars kernel: [<c1046c30>] ? call_rcu_sched+0xd/0xf Jun 8 11:34:40 Mars kernel: [<c1046c3a>] ? call_rcu+0x8/0xa Jun 8 11:34:40 Mars kernel: [<c10372b2>] ? __put_cred+0x3c/0x3e Jun 8 11:34:40 Mars kernel: [<c10170af>] ? do_page_fault+0x1db/0x1e4 Jun 8 11:34:40 Mars kernel: [<c1074ec6>] sys_unlinkat+0x2d/0x2f Jun 8 11:34:40 Mars kernel: [<c1002935>] syscall_call+0x7/0xb Jun 8 11:34:40 Mars kernel: ---[ end trace b813ccaaf3f13a41 ]--- It's quite repeatable. As soon as I try to delete a particular file, it crashes. Regardless of the corruption it shouldn't crash should it? I've unmounted it and I'm currently running a reiserfsck --fix-fixable on the device and getting these sorts of corrections. What would cause these sorts of errors. There are aren't any other indications in the syslog. ########### reiserfsck --fix-fixable started at Wed Jun 8 11:35:44 2011 ########### Replaying journal: Trans replayed: mountid 99, transid 1892575, desc 1575, len 1, commit 1577, next trans offset 1560 Trans replayed: mountid 99, transid 1892576, desc 1578, len 1, commit 1580, next trans offset 1563 Trans replayed: mountid 99, transid 1892577, desc 1581, len 1, commit 1583, next trans offset 1566 Trans replayed: mountid 99, transid 1892578, desc 1584, len 1, commit 1586, next trans offset 1569 Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 4 transactions replayed Checking internal tree.. \/ 1 (of 11|/ 1 (of 161// 7 (of 165|bad_directory_item: block 37224453: The directory item [4 38255 0x1 DIR (3)] has a not properly hashed entry (4) bad_leaf: block 37224453, item 10: The corrupted item found (4 38255 0x1 DIR (3), len 712, location 1980 entry count 26, fsck need 0, format old) bad_directory_item: block 37224453: The directory item [4 72010 0x1 DIR (3)] has a not properly hashed entry (11) bad_leaf: block 37224453, item 12: The corrupted item found (4 72010 0x1 DIR (3), len 688, location 1248 entry count 18, fsck need 0, form/131 (of 161\/ 98 (of 170/bad_path: block 241369145, pointer 97: The used space (58275) of the child block (310476801) is not equal to the (blocksize (4096) - free space (0) - header size (24)) - corrected to (4072) / 2 (of 11//136 (of 170//109 (of 170-bad_indirect_item: block 220451472: The item (27314 207020 0x671001 IND (1), len 1992, location 2104 entry count 0, fsck need 0, format new) has the bad pointer (33) to the block (220400319), which is in tree already - zeroed / 4 (of 11|/116 (of 129|/ 32 (of 168|bad_indirect_item: block 164298762: The item (103348 103544 0x1 IND (1), len 736, location 632 entry count 0, fsck need 0, format new) has the bad pointer (29) to the block (159713031), which is in tree already - zeroed / 6 (of 11-/ 66 (of 170|/ 35 (of 170\ bad_indirect_item: block 69573480: The item (196168 196190 0x2d37f001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (990) to the block (69781823), which is in tree already - zeroed / 72 (of 170|bad_indirect_item: block 69573486: The item (196168 196190 0x2eb37001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (234) to the block (69787139), which is in tree already - zeroed bad_indirect_item: block 69573486: The item (196168 196190 0x2eb37001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (594) to the block (69787499), which is in tree already - zeroed / 10 (of 11|/ 77 (of 114\/ 43 (of 170-bad_indirect_item: block 49808069: The item (250227 250228 0xae2c7001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (283) to the block (50585914), which is in tree already - zeroed bad_indirect_item: block 49808069: The item (250227 250228 0xae2c7001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (724) to the block (50586355), which is in tree already - zeroed / 47 (of 170-bad_indirect_item: block 49808073: The item (250227 250228 0xaf297001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (178) to the block (50589857), which is in tree already - zeroed bad_indirect_item: block 49808073: The item (250227 250228 0xaf297001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (674) to the block (50590353), which is in tree already - zeroed bad_indirect_item: block 49808073: The item (250227 250228 0xaf297001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (997) to the block (50590676), which is in tree already - zeroed I don't think it's ever been shut down improperly so aside from a faulty disk is there anything else that might cause something like this? Thanks syslog.txt
Archived
This topic is now archived and is closed to further replies.