Compiler Issues - 1st planned as: Actual CVS and LVM-1.0.2 snapshot problem

[Klaus Strebel <klaus.strebel@eigner.com>]

Hi everybody,

today i updated LVM-1.0.2 and my cvs tree for xfs and started playing
around with snapshots (i'm shure it worked with a little patch for
lvm-snap.c of lvm-1.0.1 quite some weeks ago, replacing blocks with
iobuf->blocks in the calls for lvm_snapshot_prepare_blocks and
__brw_kiovec for raw_read and raw_write).

Actually, mounting a snapshot of a XFS-filesystem works great, but the
umount segfaults and in the syslog i found this:

Feb  1 15:29:11 stb-mobil kernel: Mounting filesystem "lvm(58,9)" in
no-recovery mode.  Filesystem will be inconsistent.
Feb  1 15:29:23 stb-mobil kernel: lvm - lvm_map: ll_rw_blk write for
readonly LV /dev/vg00/snap
Feb  1 15:29:23 stb-mobil kernel: lvm - lvm_map: ll_rw_blk write for
readonly LV /dev/vg00/snap
Feb  1 15:29:23 stb-mobil kernel: I/O error in filesystem ("lvm(58,9)")
meta-data dev 0x3a09 block 0x200020
Feb  1 15:29:23 stb-mobil kernel:        ("xlog_iodone") error 5 buf
count 1024
Feb  1 15:29:23 stb-mobil kernel: xfs_force_shutdown(lvm(58,9),0x2)
called from line 939 of file xfs_log.c.  Return address = 0xd11250f6
Feb  1 15:29:23 stb-mobil kernel: Log I/O Error Detected.  Shutting down
filesystem: lvm(58,9)
Feb  1 15:29:23 stb-mobil kernel: Please umount the filesystem, and
rectify the problem(s)
Feb  1 15:29:23 stb-mobil kernel: kernel BUG at buffer.c:597!
Feb  1 15:29:23 stb-mobil kernel: invalid operand: 0000
Feb  1 15:29:23 stb-mobil kernel: CPU:    0
Feb  1 15:29:23 stb-mobil kernel: EIP:    0010:[<c013049d>]    Not tainted
Feb  1 15:29:23 stb-mobil kernel: EFLAGS: 00010282
Feb  1 15:29:23 stb-mobil kernel: eax: 0000001c   ebx: c0250f94   ecx:
c01fc2e0   edx: 000046d1
Feb  1 15:29:23 stb-mobil kernel: esi: cca8bd80   edi: 00000002   ebp:
00000001   esp: ccff3ed4
Feb  1 15:29:23 stb-mobil kernel: ds: 0018   es: 0018   ss: 0018
Feb  1 15:29:23 stb-mobil kernel: Process umount (pid: 1416,
stackpage=ccff3000)
Feb  1 15:29:23 stb-mobil kernel: Stack: c01d4c59 00000255 00000002
cca8bd80 cca8bd80 c0130dd0 cca8bd80 00000002
Feb  1 15:29:23 stb-mobil kernel:        cca8bd80 00000400 c0130de2
cca8bd80 c0131689 cca8bd80 00000035 cd08cbc0
Feb  1 15:29:23 stb-mobil kernel:        00000035 00000000 00000400
00000000 c0131b20 cd08cbc0 c133d780 00000000
Feb  1 15:29:23 stb-mobil kernel: Call Trace: [<c0130dd0>] [<c0130de2>]
[<c0131689>] [<c0131b20>] [<c01256b5>]
Feb  1 15:29:23 stb-mobil kernel:    [<c012f28b>] [<c0106b6b>]
Feb  1 15:29:23 stb-mobil kernel:
Feb  1 15:29:23 stb-mobil kernel: Code: 0f 0b 83 c4 08 83 3b 00 75 05 89
33 89 76 24 8b 03 89 46 20

(as you can see, i just mounted the fs, looked if its there and umounted).

I tried it with the patch mentioned above and without, with DMAPI as a
module and without.

then ... i found that i compiled using gcc-2.95.2, the standard of SuSE 
7.3 distribution (former compiles i made with kgcc from RedHat, but a 
month ago i removed my patched and patched kernel-tree and pulled 
linux-2.4-xfs anew (and forgot to uncommend the line for kgcc).

Conclusion: if you want to be sure, that all works right, compile the 
whole stuff using kgcc resp 2.91.66 !

Ciao
Klaus
-- 
Klaus Strebel
UNIX-Engineer
klaus.strebel@eigner.com
EIGNER - Precision Lifecycle Management -
<http://www.eigner.com>