Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 148171 Details for
Bug 228956
F7 test1 stack traceback when mounting an xfs filesystem
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Stack traceback extracted from /var/log/messages.
xfs_messages.txt (text/plain), 2.43 KB, created by
David Keaton
on 2007-02-16 05:32:37 UTC
(
hide
)
Description:
Stack traceback extracted from /var/log/messages.
Filename:
MIME Type:
Creator:
David Keaton
Created:
2007-02-16 05:32:37 UTC
Size:
2.43 KB
patch
obsolete
>Feb 15 22:15:27 loess kernel: SGI XFS with ACLs, security attributes, large block numbers, no debug enabled >Feb 15 22:15:27 loess kernel: SGI XFS Quota Management subsystem >Feb 15 22:15:27 loess kernel: XFS mounting filesystem sda5 >Feb 15 22:15:28 loess kernel: >Feb 15 22:15:28 loess kernel: ============================================= >Feb 15 22:15:28 loess kernel: [ INFO: possible recursive locking detected ] >Feb 15 22:15:28 loess kernel: 2.6.20-1.2930.fc7 #1 >Feb 15 22:15:28 loess kernel: --------------------------------------------- >Feb 15 22:15:28 loess kernel: rm/1257 is trying to acquire lock: >Feb 15 22:15:28 loess kernel: (&(&ip->i_lock)->mr_lock){----}, at: [<e0b75e4d>] xfs_ilock+0x4a/0x68 [xfs] >Feb 15 22:15:28 loess kernel: >Feb 15 22:15:28 loess kernel: but task is already holding lock: >Feb 15 22:15:28 loess kernel: (&(&ip->i_lock)->mr_lock){----}, at: [<e0b75e4d>] xfs_ilock+0x4a/0x68 [xfs] >Feb 15 22:15:28 loess kernel: >Feb 15 22:15:28 loess kernel: other info that might help us debug this: >Feb 15 22:15:28 loess kernel: 3 locks held by rm/1257: >Feb 15 22:15:28 loess kernel: #0: (&inode->i_mutex/1){--..}, at: [<c04831db>] do_unlinkat+0x5e/0x123 >Feb 15 22:15:28 loess kernel: #1: (&inode->i_mutex){--..}, at: [<c060e879>] mutex_lock+0x21/0x24 >Feb 15 22:15:28 loess kernel: #2: (&(&ip->i_lock)->mr_lock){----}, at: [<e0b75e4d>] xfs_ilock+0x4a/0x68 [xfs] >Feb 15 22:15:28 loess kernel: >Feb 15 22:15:28 loess kernel: stack backtrace: >Feb 15 22:15:28 loess kernel: [<c04051c9>] show_trace_log_lvl+0x1a/0x2f >Feb 15 22:15:28 loess kernel: [<c040576e>] show_trace+0x12/0x14 >Feb 15 22:15:28 loess kernel: [<c04057f2>] dump_stack+0x16/0x18 >Feb 15 22:15:28 loess kernel: [<c043ed17>] __lock_acquire+0x11f/0xba4 >Feb 15 22:15:28 loess kernel: [<c043fb8e>] lock_acquire+0x56/0x6f >Feb 15 22:15:29 loess kernel: [<c043b397>] down_write+0x3f/0x59 >Feb 15 22:15:29 loess kernel: [<e0b75e4d>] xfs_ilock+0x4a/0x68 [xfs] >Feb 15 22:15:29 loess kernel: [<e0b964b7>] xfs_lock_dir_and_entry+0x8e/0xcc [xfs] >Feb 15 22:15:29 loess kernel: [<e0b96b78>] xfs_remove+0x21c/0x438 [xfs] >Feb 15 22:15:29 loess kernel: [<e0b9d07d>] xfs_vn_unlink+0x1c/0x44 [xfs] >Feb 15 22:15:29 loess kernel: [<c0481770>] vfs_unlink+0xa4/0xdf >Feb 15 22:15:29 loess kernel: [<c048320f>] do_unlinkat+0x92/0x123 >Feb 15 22:15:29 loess kernel: [<c048339f>] sys_unlinkat+0x2d/0x2f >Feb 15 22:15:29 loess kernel: [<c0404058>] syscall_call+0x7/0xb >Feb 15 22:15:29 loess kernel: =======================
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 228956
: 148171