Bug 909553
Summary: | [abrt] kernel BUG at fs/buffer.c:1837! after EXT4_IOC_MOVE_EXT | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | monts <montosh.bisht> | ||||
Component: | kernel | Assignee: | fs-maint | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 18 | CC: | esandeen, evillagr, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, montosh.bisht, niein13 | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:7a1a5ef491f63f3033d4684dba9e86b513ca34f5 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Cause: was running e4defrag -v /dev/sda1 as a su -
when screen blanked out fs crash
Consequence: the process hangs and cannot be terminated.
Fix:
Result:
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-11-27 16:18:54 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
monts
2013-02-09 10:59:32 UTC
Created attachment 695413 [details]
File: dmesg
*** Bug 967256 has been marked as a duplicate of this bug. *** Description of problem: Probably an attempt to use the e4defrag tool on /dev/sda1 (boot) failed. Version-Release number of selected component: kernel Additional info: reporter: libreport-2.1.5 cmdline: BOOT_IMAGE=/vmlinuz-3.9.6-200.fc18.i686.PAE root=UUID=2ff4c219-bfef-40dc-8cc4-a1c2def67fe4 ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8 kernel: 3.9.6-200.fc18.i686.PAE runlevel: N 5 type: Kerneloops Truncated backtrace: kernel BUG at fs/buffer.c:1843! invalid opcode: 0000 [#1] SMP Modules linked in: vfat fat rfcomm ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast bnep bluetooth ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi arc4 snd_hda_codec_hdmi acpi_cpufreq mperf coretemp kvm_intel rt2800usb kvm rt2x00usb rt2800lib iTCO_wdt rt2x00lib iTCO_vendor_support ppdev mac80211 cfg80211 rfkill crc_ccitt snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep microcode snd_seq snd_seq_device snd_pcm serio_raw i2c_i801 snd_page_alloc lpc_ich mfd_core snd_timer snd mei soundcore parport_pc parport uinput binfmt_misc nouveau mxm_wmi wmi video crc32_pclmul i2c_algo_bit crc32c_intel drm_kms_helper ttm usb_storage r8169 drm mii i2c_core sunrpc Pid: 3361, comm: e4defrag Not tainted 3.9.6-200.fc18.i686.PAE #1 Gigabyte Technology Co., Ltd. H61M-DS2 REV 1.2/H61M-DS2 REV 1.2 EIP: 0060:[<c0588c11>] EFLAGS: 00010206 CPU: 0 EIP is at __block_write_begin+0x321/0x330 EAX: 80000029 EBX: 00000c00 ECX: 00000000 EDX: f3207ca0 ESI: 00001000 EDI: 00001000 EBP: f67cdd84 ESP: f67cdd2c DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 CR0: 80050033 CR2: b363f000 CR3: 2d1b8000 CR4: 000407f0 DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 DR6: ffff0ff0 DR7: 00000400 Process e4defrag (pid: 3361, ti=f67cc000 task=eded6600 task.ti=f67cc000) Stack: f67cdd6c 00001fff e80dc0a8 f3207ca0 f67cdd5c c061395b e8027be8 00000c00 00000001 00001c00 f3207ca0 e9df8580 e8027be8 00001fff 00000001 00090000 00001fff 00008001 00001efd 00000c00 00001000 00001000 f67cde98 c060797f Call Trace: [<c061395b>] ? jbd2_journal_try_to_free_buffers+0x8b/0x100 [<c060797f>] ext4_move_extents+0xbef/0x1130 [<c05cd730>] ? ext4_get_block_write+0x30/0x30 [<c061372f>] ? jbd2_journal_stop+0x24f/0x350 [<c05107f4>] ? zone_watermark_ok+0x34/0x40 [<c057587d>] ? __mnt_want_write_file+0x3d/0x50 [<c05d24e3>] ext4_ioctl+0x9e3/0xb20 [<c05d1b00>] ? ext4_bio_write_page+0x3d0/0x3d0 [<c056b34b>] do_vfs_ioctl+0x48b/0x590 [<c063e04a>] ? inode_has_perm.isra.32.constprop.63+0x3a/0x50 [<c063f858>] ? file_has_perm+0x98/0xb0 [<c063fc58>] ? selinux_file_ioctl+0x48/0xe0 [<c056b4bb>] sys_ioctl+0x6b/0x80 [<c09b0d0d>] sysenter_do_call+0x12/0x28 Code: 00 00 b8 04 b9 b4 c0 e8 de 5a ec ff 8b 55 e8 e9 28 fe ff ff 0f 0b 8b 4d cc 8b 55 c4 8b 45 d0 e8 96 f7 ff ff e9 4f ff ff ff 0f 0b <0f> 0b e8 58 a8 41 00 90 8d b4 26 00 00 00 00 55 89 e5 83 ec 1c EIP: [<c0588c11>] __block_write_begin+0x321/0x330 SS:ESP 0068:f67cdd2c Yep, that is on the defrag path. If this is for /boot it's probably not got sensitive information & not large. Could you unmount /boot, create an "e2image -r" image of the device, zip it, and attach it? *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |