xfs
[Top] [All Lists]

dmapi xfs mount issues

To: <linux-xfs@xxxxxxxxxxx>
Subject: dmapi xfs mount issues
From: "Tridib Chakravarty" <Tridib.Chakravarty@xxxxxxxxxxx>
Date: Wed, 17 May 2006 15:51:40 -0700
Sender: linux-xfs-bounce@xxxxxxxxxxx
Thread-index: AcZ6A4XTguutQncgSRKIbhNTBdKYngAAFRCg
Thread-topic: dmapi xfs mount issues
I am working off of the latest xfs tree and am having issues with dmapi.
I load xfs-dmapi and then on a mount I get a segfault. Upon turning on
debugging, I found that the fs_type that the fs is mounting (xfs) in
this case does not find a match to the ftype_list. The debug shows that
the list is fine but there probably is an issue with the super block
being passed by the xfs send_mount_event. I saw one other guy mention
this issue in the archive but I did'nt see an answer. Let me know if
somebody can help. 

Thanks.

-tC

TRACE STARTS HERE -----------------------------------------------------


May 17 14:27:14 linux kernel: SGI-XFS CVS-2006-05-16_07:00_UTC with
ACLs, security attributes, realtime, large block/inode numbers, tracing,
debug enab
led
May 17 14:27:14 linux kernel: xfs_dmapi: module license 'unspecified'
taints kernel.
May 17 14:27:14 linux kernel: SGI XFS Data Management API subsystem
May 17 14:27:14 linux kernel: ftype_list/348: Current ftype_list
May 17 14:27:14 linux kernel: ftype_list/351: FS 0xffff8100bb9e84e0,
ftype 0xffffffff8834eae0 xfs
May 17 14:27:14 linux kernel: ftype_list/353: Done ftype_list
May 17 14:27:38 linux kernel: SGI XFS Quota Management subsystem
May 17 14:27:38 linux kernel: XFS mounting filesystem hdd1
May 17 14:27:38 linux kernel: Ending clean XFS mount for filesystem:
hdd1
May 17 14:27:38 linux kernel: ftype_list/348: Current ftype_list
May 17 14:27:38 linux kernel: ftype_list/351: FS 0xffff8100bb9e84e0,
ftype 0xffffffff8834eae0 xfs
May 17 14:27:38 linux kernel: ftype_list/353: Done ftype_list
May 17 14:27:38 linux kernel: sb_list/330: Current sb_list
May 17 14:27:38 linux kernel: sb_list/335: Done sb_list
May 17 14:27:38 linux kernel: ftype_list/348: Current ftype_list
May 17 14:27:38 linux kernel: ftype_list/351: FS 0xffff8100bb9e84e0,
ftype 0xffffffff8834eae0 xfs
May 17 14:27:38 linux kernel: ftype_list/353: Done ftype_list
May 17 14:27:38 linux kernel: DMAPI assertion failed: proto, file:
fs/dmapi/dmapi_mountinfo.c, line: 328
May 17 14:27:38 linux kernel: ----------- [cut here ] --------- [please
bite here ] ---------
May 17 14:27:38 linux kernel: Kernel BUG at fs/dmapi/dmapi_port.h:72
May 17 14:27:38 linux kernel: invalid opcode: 0000 [1] SMP 
May 17 14:27:38 linux kernel: CPU 0 
May 17 14:27:38 linux kernel: Modules linked in: xfs_quota xfs_dmapi xfs
dmapi usbserial parport_pc lp parport floppy edd thermal processor fan
button 
battery ac snd_pcm_oss snd_mixer_oss snd_seq_midi snd_seq_midi_event
snd_seq snd_ens1371 gameport snd_rawmidi snd_seq_device snd_ac97_codec
snd_ac97_bu
s snd_pcm snd_timer snd soundcore snd_page_alloc af_packet
ip_conntrack_ftp ip_conntrack evdev joydev sg st sd_mod sr_mod scsi_mod
ipv6 ohci_hcd i2c_am
d8111 i2c_core hw_random dm_mod e100 mii usbcore reiserfs
May 17 14:27:38 linux kernel: Pid: 9068, comm: mount Tainted: P     
2.6.16 #7
May 17 14:27:38 linux kernel: RIP: 0010:[<ffffffff88262dc8>]
<ffffffff88262dc8>{:dmapi:dm_fsys_ops+88}
May 17 14:27:38 linux kernel: RSP: 0018:ffff8100be817a08  EFLAGS:
00010296
May 17 14:27:38 linux kernel: RAX: 000000000000004e RBX:
ffff81003ab9e4f8 RCX: 000000000003ffff
May 17 14:27:38 linux kernel: RDX: 0000000000000000 RSI:
0000000000000292 RDI: ffffffff8040a8c0
May 17 14:27:38 linux kernel: RBP: 0000000000000000 R08:
0000000000000034 R09: 0000000000000002
May 17 14:27:38 linux kernel: R10: 00000000ffffffff R11:
0000000000000000 R12: ffffffff8834e4c0
May 17 14:27:38 linux kernel: R13: 0000000000000000 R14:
0000000000000000 R15: 0000000000000000
May 17 14:27:38 linux kernel: FS:  00002b02b00f24c0(0000)
GS:ffffffff8050d000(0000) knlGS:0000000000000000
May 17 14:27:38 linux kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
000000008005003b
May 17 14:27:38 linux kernel: CR2: 00002b838901c728 CR3:
00000000bc216000 CR4: 00000000000006e0
May 17 14:27:38 linux kernel: Process mount (pid: 9068, threadinfo
ffff8100be816000, task ffff8100beaaf800)
May 17 14:27:38 linux kernel: Stack: ffff81003faffa8c 0000000000000001
000000d0bb9e84e0 ffff81003b905000 
May 17 14:27:38 linux kernel:        ffff81003faffa60 0000000000000010
ffff81003c3cd000 ffff81003ab9e4f8 
May 17 14:27:38 linux kernel:        ffff81003abbcbb0 ffff81003ab9e528 
May 17 14:27:38 linux kernel: Call Trace:
<ffffffff882641fa>{:dmapi:dm_ip_to_handle+42}
May 17 14:27:38 linux kernel:       
<ffffffff88261839>{:dmapi:dm_ip_data+249}
<ffffffff88261ee0>{:dmapi:dm_send_mount_event+128}
May 17 14:27:38 linux kernel:       
<ffffffff882f4af0>{:xfs:xfs_fs_fill_super+0}
<ffffffff882f4af0>{:xfs:xfs_fs_fill_super+0}
May 17 14:27:38 linux kernel:       
<ffffffff883512fd>{:xfs_dmapi:xfs_dm_mount+237}
<ffffffff882f5c65>{:xfs:vfs_mount+133}
May 17 14:27:38 linux kernel:       
<ffffffff882f4b88>{:xfs:xfs_fs_fill_super+152}
<ffffffff8037eb62>{__down_write+18}
May 17 14:27:38 linux kernel:        <ffffffff802263be>{strlcpy+78}
<ffffffff80199792>{get_filesystem+18}
May 17 14:27:38 linux kernel:        <ffffffff801842d1>{sget+945}
<ffffffff80183640>{set_bdev_super+0}
May 17 14:27:38 linux kernel:        <ffffffff801849bd>{get_sb_bdev+269}
<ffffffff80184657>{do_kern_mount+183}
May 17 14:27:38 linux kernel:        <ffffffff8019c013>{do_mount+1779}
<ffffffff80225da1>{__up_read+33}
May 17 14:27:38 linux kernel:       
<ffffffff8011c4e9>{do_page_fault+1017}
<ffffffff80216e30>{blk_end_sync_rq+0}
May 17 14:27:38 linux kernel:       
<ffffffff802cd189>{ide_cacheflush_p+105}
<ffffffff8015c6bf>{__alloc_pages+79}
May 17 14:27:38 linux kernel:       
<ffffffff8015c23f>{__get_free_pages+31}
<ffffffff8019c12c>{sys_mount+156}
May 17 14:27:38 linux kernel:        <ffffffff8010ad8e>{system_call+126}
May 17 14:27:38 linux kernel: 



<Prev in Thread] Current Thread [Next in Thread>
  • dmapi xfs mount issues, Tridib Chakravarty <=