From: Nick Pasich <Nick@NickAndBarb.net>
To: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: WARNING: at fs/inode.c:280 drop_nlink+0x31/0x33()
Date: Wed, 29 Aug 2012 09:25:27 -0700 [thread overview]
Message-ID: <20120829162527.GA3635@NickAndBarb.net> (raw)
I'm using kernel 3.5.3 ...
It happens on 3.5.1 and 3.5.2 also.
I know that Nick Bowler has already reported this...
I'm experiencing the same thing.
It happens when moving files from one directory to another
on the same partition (NFS).
--( Nick Pasich )--
#############################################################################
##
## Happens when PSTs are moved from one directory to another on the ISCSI ...
##
#############################################################################
Aug 29 08:06:16 localhost kernel: ------------[ cut here ]------------
Aug 29 08:06:16 localhost kernel: WARNING: at fs/inode.c:280 drop_nlink+0x31/0x33()
Aug 29 08:06:16 localhost kernel: Hardware name: To Be Filled By O.E.M.
Aug 29 08:06:16 localhost kernel: Modules linked in: ecb md4 cifs w83627hf eeprom asb100 hwmon_vid hwmon nfsd exportfs ipv6 psmouse usb_storage io_edgeport usbserial sg r8169 mii evdev intel_agp uhci_hcd i2c_i801 i2c_core shpchp intel_gtt agpgart ehci_hcd microcode serio_raw
Aug 29 08:06:16 localhost kernel: Pid: 31477, comm: rm Tainted: G W 3.5.3 #1
Aug 29 08:06:16 localhost kernel: Call Trace:
Aug 29 08:06:16 localhost kernel: [<c10a53e2>] ? drop_nlink+0x31/0x33
Aug 29 08:06:16 localhost kernel: [<c1025dd2>] ? warn_slowpath_common+0x7b/0x90
Aug 29 08:06:16 localhost kernel: [<c10a53e2>] ? drop_nlink+0x31/0x33
Aug 29 08:06:16 localhost kernel: [<c1025e02>] ? warn_slowpath_null+0x1b/0x1f
Aug 29 08:06:16 localhost kernel: [<c10a53e2>] ? drop_nlink+0x31/0x33
Aug 29 08:06:16 localhost kernel: [<f83dfa81>] ? cifs_unlink+0x134/0x63d [cifs]
Aug 29 08:06:16 localhost kernel: [<c10a37d4>] ? dput+0x11/0x117
Aug 29 08:06:16 localhost kernel: [<c10a87d4>] ? mntput_no_expire+0xf/0xf7
Aug 29 08:06:16 localhost kernel: [<c109ca9b>] ? vfs_unlink+0x4e/0xb6
Aug 29 08:06:16 localhost kernel: [<c109b333>] ? __lookup_hash+0x54/0xac
Aug 29 08:06:16 localhost kernel: [<c109e8c2>] ? do_unlinkat+0x10a/0x12d
Aug 29 08:06:16 localhost kernel: [<c10a0124>] ? sys_ioctl+0x34/0x57
Aug 29 08:06:16 localhost kernel: [<c140a8ed>] ? syscall_call+0x7/0xb
Aug 29 08:06:16 localhost kernel: ---[ end trace 756b427e3bd671f9 ]---
next reply other threads:[~2012-08-29 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 16:25 Nick Pasich [this message]
2012-08-29 22:16 ` WARNING: at fs/inode.c:280 drop_nlink+0x31/0x33() Jeff Layton
2012-08-30 0:20 ` Nick Pasich
2012-08-31 4:33 ` Nick Pasich
2012-08-31 8:00 ` Pavel Shilovsky
2012-08-31 15:32 ` Nick Pasich
2012-08-31 16:21 ` Jeff Layton
2012-08-31 18:03 ` Nick Pasich
2012-09-06 11:58 ` Jeff Layton
2012-09-25 5:27 ` NeilBrown
2012-09-25 10:21 ` Jeff Layton
-- strict thread matches above, loose matches on Subject: below --
2012-08-29 16:16 Nick Pasich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120829162527.GA3635@NickAndBarb.net \
--to=nick@nickandbarb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).