Mailinglist Archive: opensuse-amd64 (194 mails)

[Alexander Karakas <akarak@xxxxxx>]

Hello,


I got the following stack trace in the log on an AMD64-File-Server
running SAMBA shares on (LVM2-Volumegroup with ReiserFS
v3.6 partitions) with quotas turned on.

The dump occured during a the copying of files from a SuSE Linux
9.1 Prof. client (smbclient) to a SAMBA share.
During this operation the user exceeded his quota.


##########################################################

Apr  6 10:01:30 kingarthur kernel: Kernel BUG at dquot:310
Apr  6 10:01:30 kingarthur kernel: invalid operand: 0000 [1] SMP
Apr  6 10:01:30 kingarthur kernel: CPU 0
Apr  6 10:01:30 kingarthur kernel: Pid: 25508, comm: quotaoff Not tainted 
(2.6.5-7.151-smp SLES9_SP1_BRANCH-200503181131210000)
Apr  6 10:01:30 kingarthur kernel: RIP: 0010:[vfs_quota_off+341/704] 
<ffffffff801be5c5>{vfs_quota_off+341}
Apr  6 10:01:30 kingarthur kernel: RIP: 0010:[<ffffffff801be5c5>] 
<ffffffff801be5c5>{vfs_quota_off+341}
Apr  6 10:01:30 kingarthur kernel: RSP: 0018:000001004ded9ca8  EFLAGS: 
00010202
Apr  6 10:01:30 kingarthur kernel: RAX: 0000000000000001 RBX: 000001003e2bf690 
RCX: 000001003e2bf490
Apr  6 10:01:30 kingarthur kernel: RDX: ffffffff803d89d0 RSI: 000001003e2bf980 
RDI: 000001007fd86700
Apr  6 10:01:30 kingarthur kernel: RBP: 00000100037b1c00 R08: 0000000000000000 
R09: 000001004ded9c28
Apr  6 10:01:30 kingarthur kernel: R10: 0000000000000000 R11: 0000000000000000 
R12: 000001004ded9cc8
Apr  6 10:01:30 kingarthur kernel: R13: 00000100037b1d28 R14: 00000100037b1d28 
R15: 0000000000000000
Apr  6 10:01:30 kingarthur kernel: FS:  0000002a9588d6e0(0000) 
GS:ffffffff80554200(0000) knlGS:00000000557be2a0
Apr  6 10:01:30 kingarthur kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 
000000008005003b
Apr  6 10:01:30 kingarthur kernel: CR2: 0000002a9556b000 CR3: 0000000000101000 
CR4: 00000000000006e0
Apr  6 10:01:30 kingarthur kernel: Process quotaoff (pid: 25508, threadinfo 
000001004ded8000, task 00000100104b40c0)
Apr  6 10:01:30 kingarthur kernel: Stack: 0000000100000001 00000100037b1d30 
00000100037b1d70 0000000000000010
Apr  6 10:01:30 kingarthur kernel:        000001004ded9cc8 000001004ded9cc8 
0000000000000000 0000000080000300
Apr  6 10:01:30 kingarthur kernel:        000001007ad5fc00 0000000000000000
Apr  6 10:01:30 kingarthur kernel: Call 
Trace:<ffffffff801bfeb9>{sys_quotactl+1385} <ffffffff8019a8e1>{do_lookup+49}
Apr  6 10:01:30 kingarthur kernel:        
<ffffffff8013cd00>{autoremove_wake_function+0} 
<ffffffff8019aad7>{permission+55}
Apr  6 10:01:30 kingarthur kernel:        <ffffffff8019bf2c>{may_open+108} 
<ffffffff8016b410>{file_ra_state_init+32}
Apr  6 10:01:30 kingarthur kernel:        
<ffffffff80187f86>{dentry_open_it+310} <ffffffff80188131>{filp_open+113}
Apr  6 10:01:30 kingarthur kernel:        <ffffffff801a5ce1>{dput+33} 
<ffffffff8018be2e>{__fput+270}
Apr  6 10:01:30 kingarthur kernel:        <ffffffff80187aae>{filp_close+126} 
<ffffffff80187bb5>{sys_close+229}
Apr  6 10:01:30 kingarthur kernel:        <ffffffff801106d4>{system_call+124}
Apr  6 10:01:30 kingarthur kernel:
Apr  6 10:01:30 kingarthur kernel: Code: 0f 0b 73 5c 38 80 ff ff ff ff 36 01 
48 8b 56 08 48 8b 06 48
Apr  6 10:01:30 kingarthur kernel: RIP <ffffffff801be5c5>{vfs_quota_off+341} 
RSP <000001004ded9ca8>

##########################################################


The system didn't crash completely but the access to all the partitions
of the volumegroup wasn't possible anymore.
As an workaround quota support has been disabled and all is running
quite well again.

There was an kernel update made (with YOU) on March, 18th 2005,
but he problem occured just today.

Maybe, somebody has a hint, how to get quota support up and running
again?


Thanks,


Alexander Karakas
akarak@xxxxxx