From: "J. Bruce Fields" <bfields@fieldses.org>
To: Marc Meledandri <m.meledandri@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Issues with a rather unusual configured NFS server
Date: Tue, 1 Oct 2013 10:34:00 -0400 [thread overview]
Message-ID: <20131001143400.GI26382@fieldses.org> (raw)
In-Reply-To: <CACFbnrwWJz8her6a4PRn-a0sTF2ci2VY7xOdgRS3zhFpYfxfug@mail.gmail.com>
On Sat, Sep 28, 2013 at 11:37:40AM -0400, Marc Meledandri wrote:
> I was pointed at this thread by the linux-ext4 folks as relevant to my
> issue on kernels in
> the 3.10.x series. I see this commit was tagged for 3.12-rc2 on git,
> and wondering if it will be
> rebased for previous kernels? Maybe my issue (oops at shutdown) is
> caused by something
> else entirely? Thanks!
That patch probably should have been cc'd to stable for kernels since
3.10....
Do you have a reproduceable test case? Would it be possible for you to
confirm that this fixes your problem if applied on top of 3.10.x?
--b.
>
> [183727.974779] EXT4-fs (dm-0): sb orphan head is 47193630
> [183727.974864] sb_info orphan list:
> [183727.974932] inode dm-0:47193630 at ffff8802b98950f0: mode
> 100644, nlink 0, next 0
> [183727.975039] ------------[ cut here ]------------
> [183727.975108] kernel BUG at fs/ext4/super.c:804!
> [183727.975177] invalid opcode: 0000 [#1] SMP
> [183727.975341] Modules linked in: btrfs zlib_deflate ufs qnx4 hfsplus
> hfs minix ntfs vfat msdos fat jfs xfs libcrc32c reiserfs ext3 jbd ext2
> efivars cpuid fuse ecb pci_stub parport_pc ppdev lp parport
> cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave
> binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache
> sunrpc usblp hid_microsoft dm_crypt dm_mod loop ecryptfs joydev
> nvidia(PO) snd_hda_codec_realtek snd_hda_intel iTCO_wdt
> iTCO_vendor_support snd_hda_codec mxm_wmi evdev snd_hwdep snd_pcm
> snd_page_alloc coretemp snd_seq snd_timer snd_seq_device psmouse wmi
> serio_raw snd i2c_i801 lpc_ich soundcore mfd_core i2c_core ehci_pci
> ehci_hcd acpi_cpufreq mperf processor button thermal_sys ext4 crc16
> jbd2 mbcache raid456 async_raid6_recov async_memcpy async_pq async_xor
> async_tx xor raid6_pq md_mod sg sr_mod cdrom sd_mod crc_t10dif
> hid_generic usbhid hid crc32c_intel ghash_clmulni_intel ahci libahci
> libata scsi_mod aesni_intel xhci_hcd aes_x86_64 ablk_helper cryptd lrw
> gf128mul glue_helper microcode usbcore usb_common e1000e ptp pps_core
> [last unloaded: vboxdrv]
> [183727.981527] CPU: 2 PID: 24609 Comm: umount Tainted: P O
> 3.10.10+mfm #1
> [183727.981614] Hardware name: /DZ68BC, BIOS
> BCZ6810H.86A.0027.2011.1013.1636 10/13/2011
> [183727.981703] task: ffff8803e7b06810 ti: ffff8803fffe0000 task.ti:
> ffff8803fffe0000
> [183727.981790] RIP: 0010:[<ffffffffa0209b62>] [<ffffffffa0209b62>]
> ext4_put_super+0x256/0x310 [ext4]
> [183727.981933] RSP: 0018:ffff8803fffe1e78 EFLAGS: 00010287
> [183727.982003] RAX: 0000000000000047 RBX: ffff88040de47000 RCX:
> 00000000d2a7d2a7
> [183727.982088] RDX: 000000000000508c RSI: 0000000000000046 RDI:
> ffffffff817a94a4
> [183727.982174] RBP: ffff88040beb0800 R08: 0000000000000000 R09:
> 0000000000000100
> [183727.982260] R10: 0000000000000100 R11: 0000000000000100 R12:
> ffff88040de47200
> [183727.982345] R13: ffff88040de47200 R14: ffff88040de47190 R15:
> ffff8803fffe1f38
> [183727.982432] FS: 00007fb64bfc17e0(0000) GS:ffff88041f500000(0000)
> knlGS:0000000000000000
> [183727.982519] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [183727.982590] CR2: 00007f3fd0af4f80 CR3: 00000002e46b5000 CR4:
> 00000000000407e0
> [183727.982676] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> [183727.982762] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
> 0000000000000400
> [183727.982847] Stack:
> [183727.982911] ffff880300000000 ffff8803fffe1e78 ffff88040beb0800
> ffff88040beb08a0
> [183727.983190] ffffffffa0228fb0 ffff88040ea052a0 ffff88040ea05280
> ffffffff810f9415
> [183727.983468] ffff88041e59dbc0 0000000000000083 ffff88040ea05280
> ffffffff810f94ab
> [183727.983745] Call Trace:
> [183727.983813] [<ffffffff810f9415>] ? generic_shutdown_super+0x4d/0xc5
> [183727.983885] [<ffffffff810f94ab>] ? kill_block_super+0x1e/0x5f
> [183727.983958] [<ffffffff810f97b2>] ? deactivate_locked_super+0x1b/0x46
> [183727.984030] [<ffffffff8110e8b0>] ? SyS_umount+0x2d0/0x2f1
> [183727.984102] [<ffffffff8136b912>] ? system_call_fastpath+0x16/0x1b
> [183727.984173] Code: c7 c7 04 1b 23 a0 49 8b 54 24 78 48 81 c6 20 03
> 00 00 89 04 24 31 c0 e8 de 72 15 e1 4d 8b 24 24 4d 39 ec 0f 84 6e ff
> ff ff eb b7 <0f> 0b 48 8b bd 20 01 00 00 e8 b5 65 f1 e0 48 8b bb 50 02
> 00 00
> [183727.987403] RIP [<ffffffffa0209b62>] ext4_put_super+0x256/0x310 [ext4]
> [183727.987525] RSP <ffff8803fffe1e78>
> [183727.987597] ---[ end trace eb19380900af1108 ]---
> [183728.094179] EXT4-fs (sda2): re-mounted. Opts: (null)
> [184000.112039] SysRq : Keyboard mode set to system default
> [184001.631989] SysRq : Terminate All Tasks
> [184269.335155] EXT4-fs (sda2): re-mounted. Opts: discard,errors=remount-ro
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-10-01 14:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 15:37 Issues with a rather unusual configured NFS server Marc Meledandri
2013-10-01 14:34 ` J. Bruce Fields [this message]
2013-10-02 1:24 ` Marc Meledandri
2013-10-02 14:04 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2013-08-11 9:48 Toralf Förster
2013-08-12 14:36 ` Jan Kara
2013-08-13 21:53 ` J. Bruce Fields
2013-08-14 16:44 ` Toralf Förster
2013-08-27 18:06 ` J. Bruce Fields
2013-08-28 17:21 ` Toralf Förster
2013-09-07 20:44 ` Toralf Förster
2013-09-10 14:09 ` J. Bruce Fields
2013-09-10 15:51 ` Toralf Förster
2013-09-22 16:58 ` Toralf Förster
2013-09-23 17:41 ` J. Bruce Fields
2013-10-02 20:29 ` Toralf Förster
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=20131001143400.GI26382@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=m.meledandri@gmail.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 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).