From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3B8FD95C.60702@st-peter.stw.uni-erlangen.de> Date: Fri, 31 Aug 2001 20:37:16 +0200 From: svetljo MIME-Version: 1.0 Subject: Re: [linux-lvm] PBs with LVM over software RAID References: <3B8E3F0E.8050609@st-peter.stw.uni-erlangen.de> <20010830083546.A20989@sistina.com> <3B8EC633.40202@st-peter.stw.uni-erlangen.de> <3B8F8C5E.7030603@st-peter.stw.uni-erlangen.de> <20010831110512.V541@turbolinux.com> Content-Transfer-Encoding: 7bit Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-lvm@sistina.com hey that's it and what now do you think that i have to try with another kernel or FS for me xfs is the best Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010247 eax: 004ac1ab ebx: 004ac1ab ecx: 00000000 edx: 00000000 esi: d54eb320 edi: c188b928 ebp: 00958357 esp: d4eb3670 ds: 0018 es: 0018 ss: 0018 Process mount (pid: 5536, stackpage=d4eb3000) Stack: d54eb3e0 c023fa12 00000907 d54eb320 00000000 01c02000 c0278dcd dcec43c0 00000000 d54eb320 d54eb320 00000000 01c02000 c027fa0f 00000001 d54eb320 c023fd89 c03a7254 00000000 d54eb320 00000282 00000021 00000000 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: f7 f9 85 d2 74 24 55 51 68 c0 03 9c e2 e8 58 6c 75 dd 6a 00 >>EIP; e29c0266 <[linear]linear_make_request+36/f0> <===== Trace; c023fa12 <__make_request+412/6d0> Trace; c0278dcd Trace; c027fa0f Trace; c023fd89 Trace; c01a6814 <_pagebuf_page_io+1f4/370> Trace; c01a6a85 <_page_buf_page_apply+f5/1c0> Trace; c01a6fc1 Trace; c01a6c47 Trace; c01a6990 <_page_buf_page_apply+0/1c0> Trace; c0105dac <__down+bc/d0> Trace; c0105f1c <__down_failed+8/c> Trace; c02e2140 Trace; c021c10a Trace; c01fe5b8 Trace; c01ff2a4 Trace; c01a553e <_pagebuf_get_object+3e/170> Trace; c01feb6f Trace; c01feed8 Trace; c01fc322 Trace; c0201f40 Trace; c01fb8f3 Trace; c0202fdf Trace; c02026bf Trace; c01a60be Trace; c02026eb Trace; c021e674 Trace; c020b69c Trace; c020b843 Trace; c020b871 Trace; c021cf48 Trace; c01294e0 Trace; c0125f0e Trace; c0125d9d Trace; c013cd72 Trace; c013d01b Trace; c013dafc Trace; c01131e0 Trace; c010724c Trace; c013dd56 Trace; c013dbfc Trace; c013de13 Trace; c010715b Code; e29c0266 <[linear]linear_make_request+36/f0> 00000000 <_EIP>: Code; e29c0266 <[linear]linear_make_request+36/f0> <===== 0: f7 f9 idiv %ecx,%eax <===== Code; e29c0268 <[linear]linear_make_request+38/f0> 2: 85 d2 test %edx,%edx Code; e29c026a <[linear]linear_make_request+3a/f0> 4: 74 24 je 2a <_EIP+0x2a> e29c0290 <[linear]linear_make_request+60/f0> Code; e29c026c <[linear]linear_make_request+3c/f0> 6: 55 push %ebp Code; e29c026d <[linear]linear_make_request+3d/f0> 7: 51 push %ecx Code; e29c026e <[linear]linear_make_request+3e/f0> 8: 68 c0 03 9c e2 push $0xe29c03c0 Code; e29c0273 <[linear]linear_make_request+43/f0> d: e8 58 6c 75 dd call dd756c6a <_EIP+0xdd756c6a> c0116ed0 Code; e29c0278 <[linear]linear_make_request+48/f0> 12: 6a 00 push $0x0 Andreas Dilger wrote: >On Aug 31, 2001 15:08 +0200, svetljo wrote: > >>[root@svetljo mnt]# mount -t xfs /dev/myData/Music music >>Segmentation fault >> > >Generally this is a bad sign. Either mount is segfaulting (unlikely) >or you are getting an oops in the kernel. You need do run something >like "dmesg | ksymoops" in order to get some useful data about where >the problem is (could be xfs, LVM, or elsewhere in the kernel). > >Once you have an oops, you are best off rebooting the system, because >your kernel memory may be corrupted, and cause more oopses which do >not mean anything. If you look in /var/log/messages (or /var/log/kern.log >or some other place, depending on where kernel messages go), you can >decode the FIRST oops in the log with ksymoops. All subsequent ones are >useless. > > >>the LV ( lvcreate -i3 -I4 -L26G -nMusic ) >> >>the VG -> myData /dev/hdh10 /dev/linVG1/linLV1 /dev/linVG2/linLV2 >> >>/dev/hdh10 normal partition 14G >>/dev/linVG1/linLV1 -> linear LV 14G /dev/hde6 /dev/hde12 >>/dev/linVg2/linLV2 -> linear LV 14G /dev/hdg1 /dev/hdg5 /dev/hdg6 /dev/hdg12 >> > >There is absolutely no point in doing this (not that it is possible to do >so anyways). First of all, striping is almost never needed "for performance" >unless you are normally doing very large sequential I/Os, and even so most >disks today have very good sequential I/O rates (e.g. 15-30MB/s). Secondly, >you _should_ be able to just create a single LV that is striped across all >of the PVs above. You would likely need to build it in steps, to ensure >that it is striped across the disks correctly. > >Cheers, Andreas >