All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Keller <grant.keller@sonic.com>
To: xfs@oss.sgi.com
Subject: rm Tainted warning after kernel update.
Date: Mon, 14 Sep 2015 11:57:37 -0700	[thread overview]
Message-ID: <55F718A1.10801@sonic.com> (raw)

Hello,

I have a server running Scientific Linux 6.7, and since updating to
kernel 2.6.32-573.3.1.el6.x86_64 the following error has begun appearing
in our message logs:

Sep 14 11:43:03 localhost kernel: ------------[ cut here ]------------
Sep 14 11:43:03 localhost kernel: WARNING: at fs/dcache.c:758
d_delete+0x260/0x2c0() (Tainted: G        W  -- ------------   )
Sep 14 11:43:03 localhost kernel: Hardware name: X7DB8
Sep 14 11:43:03 localhost kernel: Modules linked in: nfsd nfs_acl
auth_rpcgss autofs4 lockd sunrpc p4_clockmod freq_table speedstep_lib
nf_conntrack_ftp iptable_mangle xt_comment nf_conntrack_ipv4
nf_defrag_ipv4 xt_multiport iptable_filter ip_tables ip6t_REJECT
nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter
ip6_tables ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad rdma_cm ib_cm
iw_cm ib_sa ib_mad ib_core ib_addr ipv6 xfs exportfs ppdev parport_pc
parport sg e1000e microcode serio_raw iTCO_wdt iTCO_vendor_support ixgbe
ptp pps_core mdio i2c_i801 lpc_ich mfd_core i5000_edac edac_core i5k_amb
ioatdma dca shpchp ext4 jbd2 mbcache sd_mod crc_t10dif 3w_9xxx pata_acpi
ata_generic ata_piix radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core
dm_mirror dm_region_hash dm_log dm_mod [last unloaded: ipmi_msghandler]
Sep 14 11:43:03 localhost kernel: Pid: 15893, comm: rm Tainted: G       
W  -- ------------    2.6.32-573.3.1.el6.x86_64 #1
Sep 14 11:43:03 localhost kernel: Call Trace:
Sep 14 11:43:03 localhost kernel: [<ffffffff81077491>] ?
warn_slowpath_common+0x91/0xe0
Sep 14 11:43:03 localhost kernel: [<ffffffff810774fa>] ?
warn_slowpath_null+0x1a/0x20
Sep 14 11:43:03 localhost kernel: [<ffffffff811ae660>] ?
d_delete+0x260/0x2c0
Sep 14 11:43:03 localhost kernel: [<ffffffff811a0908>] ? vfs_rmdir+0xe8/0xf0
Sep 14 11:43:03 localhost kernel: [<ffffffff811a3b64>] ?
do_rmdir+0x184/0x1f0
Sep 14 11:43:03 localhost kernel: [<ffffffff81193511>] ? __fput+0x1a1/0x210
Sep 14 11:43:03 localhost kernel: [<ffffffff810e8ab7>] ?
audit_syscall_entry+0x1d7/0x200
Sep 14 11:43:03 localhost kernel: [<ffffffff811a3bfd>] ?
sys_unlinkat+0x2d/0x40
Sep 14 11:43:03 localhost kernel: [<ffffffff8100b0d2>] ?
system_call_fastpath+0x16/0x1b
Sep 14 11:43:03 localhost kernel: ---[ end trace 6080ec4a7ec5ec25 ]---

This happens when we are expiring older backups from the archives, so I
have quite a few of these. We have xfsprogs 3.1.1-16.el6.x86_64
installed. Looking for advice on how to proceed.

-- 
Grant Keller
System Operations
707-237-2451
grant.keller@sonic.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2015-09-14 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 18:57 Grant Keller [this message]
2015-09-15 11:00 ` rm Tainted warning after kernel update Brian Foster
2015-09-15 22:32   ` Grant Keller
2015-09-16 10:50     ` Brian Foster
2015-09-16 11:13       ` Lukáš Czerner
2015-09-16 11:42         ` Brian Foster
2015-09-16 12:21           ` Lukáš Czerner

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=55F718A1.10801@sonic.com \
    --to=grant.keller@sonic.com \
    --cc=xfs@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.