March 14, 200818 yr I was doing a move from dis 3 to disk6, then opened another telnet window, and executed another move from a disk1 to disk6, and immediately got this in both wndows: Everything seems to be working, but thought It might be useful to post. Tower login: root Password: [Disconnect bypassed -- root login allowed.] Linux 2.6.22.5. root@Tower:~# cd /mnt root@Tower:/mnt# ls disk1/ disk2/ disk3/ disk4/ disk5/ disk6/ tmp/ user/ root@Tower:/mnt# cd disk1 root@Tower:/mnt/disk1# ls Backups/ Downloads/ Media/ Sage/ root@Tower:/mnt/disk1# mv Downloads ../disk6 & [1] 7511 root@Tower:/mnt/disk1# Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] ------------[ cut here ]------------ Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] invalid opcode: 0000 [#1] Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] CPU: 0 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] EIP: 0060:[<c01774a7>] Not tainted VLI Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] EFLAGS: 00010246 (2.6.22.5 #9) Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] EIP is at reiserfs_cache_bitmap_metadata+0x74/0x7c Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] eax: c2579000 ebx: debfa9d4 ecx: 00000000 edx : c2578ffc Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] esi: c9e40b38 edi: 00000000 ebp: debfa9d4 esp : dda99d74 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0068 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] Process mv (pid: 7511, ti=dda98000 task=dc371a70 ta sk.ti=dda98000) Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] Stack: c9e40b38 073a8000 c49b0800 c017755f 00001000 c49b0800 c4fa9a64 c03025e8 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] c49b0800 c4fa9a64 debfa9d4 c4fa9bcc c0176107 fffffff4 dda99edc c03025e8 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] c017f175 c3718ebc c01548e3 c1666ee4 c8356013 8bdbb9af c49b0800 000041c9 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] Call Trace: Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c017755f>] reiserfs_read_bitmap_block+0xb0/0xba Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c0176107>] reiserfs_choose_packing+0x43/0x72 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c017f175>] reiserfs_new_inode+0x65/0x4de Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c01548e3>] __d_lookup+0xaa/0xca Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c014c6e4>] do_lookup+0x45/0xa2 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c01548e3>] __d_lookup+0xaa/0xca Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c01945d6>] journal_begin+0x93/0xce Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c017b489>] reiserfs_mkdir+0x155/0x263 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c014c2cd>] permission+0xb6/0xbb Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c017b334>] reiserfs_mkdir+0x0/0x263 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c014e3d5>] vfs_mkdir+0x58/0x97 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c014e49d>] sys_mkdirat+0x89/0xc2 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c014f103>] sys_renameat+0x57/0x5e Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c014e4f5>] sys_mkdir+0x1f/0x23 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] [<c0103a62>] syscall_call+0x7/0xb Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] ======================= Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] Code: 40 74 d2 b9 1f 00 00 00 0f a3 0a 19 c0 85 c0 75 0f 8d 04 0f 66 89 03 0f b7 43 02 40 66 89 43 02 49 79 e5 eb b0 66 83 3b 00 75 04 <0f> 0b eb fe 5b 5e 5f c3 55 89 d1 57 89 c7 56 53 83 ec 10 8b 58 Message from syslogd@Tower at Thu Jan 10 20:14:46 2002 ... Tower kernel: [81841.640000] EIP: [<c01774a7>] reiserfs_cache_bitmap_metadata+0x 74/0x7c SS:ESP 0068:dda99d74
March 14, 200818 yr man I hate these kinds of problems. First thing I would do would be a memtest overnight.
March 15, 200818 yr Author Update: Turned out things were not ok. Trying to access some shares cause lock ups of windows explorer. Trying to remove user shares on the array (using the web interface) hung the interface. Tracked it down to a corrupted files system on disk6. I couldn't even enter the directory using the command line, with out the session hanging. Used the instructions in this thread: http://lime-technology.com/forum/index.php?topic=463.0 To fix the FS. Seems to be OK now. I beleive it was a problem with completely full disks, except disk 6, combined with doing multiple moves of data in user shares from the command line between disks. I've upgraded to 4.3-beta1. So far so good. Running the mem test is a good Idea. I'll do that one of these nights to rule out any issues with the memory.
March 16, 200818 yr Running the mem test is a good Idea. I'll do that one of these nights to rule out any issues with the memory. I highly recommend that just for safety sake. I've seen where a bad chunk of memory corrupts a segment in the file system. (remember data is first cached into memory, then written out). I'm dealing with something similar on a totally different machine.
Archived
This topic is now archived and is closed to further replies.