A few weeks ago fs/super.c underwent a major reorganization. As a result,
the DMAPI mount code was broken. I was wondering how long we'd go before
someone noticed it :)
I'll try to get to it next week.
Dean
>From: Takayuki Sasaki <sasaki@xxxxxxxxxxxxxxxxxx>
>Hi there,
>
>While testing the XFS filesystem with dmapi option,
>I encountered panic with the following operations:
>
># mkfs.xfs /dev/foo
># mount -t xfs -o dmapi /dev/foo /mnt/foo
># umount /mnt/foo
>
>kernel panic: dm_change_fsys_entry: can't find DMAPI fsrp for vfsp c6965860
>
>backtrace process using KDB is:
> schedule+0x520 (0xc048fa40,0x0,0x0,0xc0382580)
> notifier_caller_chain+0x23(0xc0508da0,0x0,0x0,0x0)
> panic+0x87 (0xc0382580,0xc303e65c,0xc303e584)
> dm_change_fsys_entry+0x30 (0xc303e65c)
> dm_send_namesp_event+0x60 (0x2, 0xc1b26260,0x0,0xc1b26260,0x0)
> xfs_unmount+0x74 (0xc1248400,0x0,0xc05132c0)
> fs_dounmount+0x59
> linvfs_put_super+0x36
> kill_super+0x14d
> __mntput+0x39
> path_release+0x2a
> sys_umount+0x194
> sys_oldumount+0xe
> system_call+0x33
>
>Kernel: linux-2.4.10-xfs (20010925 CVS Tree)
>gcc: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>Box: Pentium III (Coppermine) 733MHz + SiS 630 chip set + 128MB RAM
>
>This is not critical issue so far for me, however, I couldn't
>find same errors in the archive, so report to the list.
>
>Cheers,
>
>Takayuki
>
|