[Bug 659888] New: kernel bug in disk-io.c
https://bugzilla.novell.com/show_bug.cgi?id=659888 https://bugzilla.novell.com/show_bug.cgi?id=659888#c0 Summary: kernel bug in disk-io.c Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i586 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: cfarrell@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- The following dmesg message was displayed after all my bash shells crashed. The situation was that I was working in my /space directoy. mount says the following about the /space partition /dev/sda3 on /space type btrfs (rw) I also (previously) had a usb stick mounted at /dev/sdf also formatted as btrfs. This was however removed prior to the crash. I am not sure if the machine synced before I removed - but there is a string possibility that it did, because the usb stick carried a root filesystem for a dockstar, which is currently running fine with exactly that root filesystem. [1481279.763486] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on tmds encoder (output 2) [1482269.953907] lost page write due to I/O error on sdf1 [1482269.953916] end_request: I/O error, dev sdf, sector 131072 [1482269.953919] lost page write due to I/O error on sdf1 [1482269.953925] btrfs: 1 errors while writing supers [1482269.953965] ------------[ cut here ]------------ [1482269.953970] kernel BUG at /usr/src/packages/BUILD/kernel-default-2.6.34.7/linux-2.6.34/fs/btrfs/disk-io.c:2292! [1482269.953976] invalid opcode: 0000 [#1] SMP [1482269.953982] last sysfs file: /sys/devices/virtual/bdi/0:25/uevent [1482269.953986] Modules linked in: joydev st snd_seq_dummy nls_iso8859_1 nls_cp437 vfat fat iptable_filter ip_tables x_tables pl2303 usbserial nouveau ttm drm_kms_helper drm i2c_algo_bit fuse nfs lockd fscache nfs_acl auth_rpcgss sunrpc autofs4 rfcomm sco bridge stp llc bnep snd_pcm_oss snd_mixer_oss l2cap snd_seq snd_seq_device edd af_packet mperf btrfs zlib_deflate crc32c libcrc32c loop dm_mod snd_hda_codec_realtek parport_pc firewire_ohci firewire_core snd_hda_intel snd_hda_codec crc_itu_t snd_hwdep ppdev snd_pcm parport sr_mod snd_timer ohci1394 usbhid btusb cdrom sg floppy 8139too i2c_i801 bluetooth usb_storage snd rfkill pcspkr iTCO_wdt iTCO_vendor_support hid ieee1394 8139cp soundcore snd_page_alloc i2c_core intel_agp button sky2 ext4 jbd2 crc16 uhci_hcd rtc_cmos rtc_core rtc_lib ehci_hcd sd_mod usbcore fan processor ata_generic ata_piix ahci libata scsi_mod thermal thermal_sys hwmon [last unloaded: preloadtrace] [1482269.954100] [1482269.954104] Pid: 16201, comm: bash Not tainted 2.6.34.7-0.5-default #1 / [1482269.954108] EIP: 0060:[<f9736d22>] EFLAGS: 00010282 CPU: 1 [1482269.954125] EIP is at write_all_supers+0x262/0x270 [btrfs] [1482269.954128] EAX: 0000003c EBX: c3ea16d8 ECX: 00000086 EDX: 02515000 [1482269.954131] ESI: 00000001 EDI: c3ea16d8 EBP: 00000000 ESP: ed01deac [1482269.954135] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [1482269.954138] Process bash (pid: 16201, ti=ed01c000 task=ef849170 task.ti=ed01c000) [1482269.954141] Stack: [1482269.954143] f9782a60 00000001 c3ea1680 f625c000 00000001 cef1ad5b 00000000 00000000 [1482269.954151] <0> e7dd48c0 cef1ad59 cef1b884 f625c000 f973a3f2 00000000 e7dd490c e6f2ce50 [1482269.954160] <0> 00000000 00000001 00000000 00000000 ef849170 c025e070 ed01df04 ed01df04 [1482269.954170] Call Trace: [1482269.954213] [<f973a3f2>] btrfs_commit_transaction+0x462/0x6c0 [btrfs] [1482269.954240] [<c0338d10>] vfs_quota_sync+0x160/0x2a0 [1482269.954249] [<c031a3ac>] __sync_filesystem+0x3c/0xa0 [1482269.954257] [<c02fb58f>] generic_shutdown_super+0x1f/0xd0 [1482269.954264] [<c02fb689>] kill_anon_super+0x9/0x40 [1482269.954270] [<c02fc1b8>] deactivate_super+0x58/0x90 [1482269.954276] [<c031ae7d>] set_fs_pwd+0x4d/0x60 [1482269.954282] [<c02f8893>] sys_chdir+0x83/0x90 [1482269.954289] [<c0203190>] sysenter_do_call+0x12/0x22 [1482269.954301] [<ffffe430>] 0xffffe430 [1482269.954303] Code: c4 20 31 c0 5b 5e 5f 5d c3 89 6c 24 04 c7 04 24 60 2a 78 f9 e8 2b 33 e8 c6 0f 0b 89 74 24 04 c7 04 24 60 2a 78 f9 e8 19 33 e8 c6 <0f> 0b 8d b6 00 00 00 00 8d bf 00 00 00 00 89 d0 89 ca e9 87 fd [1482269.954355] EIP: [<f9736d22>] write_all_supers+0x262/0x270 [btrfs] SS:ESP 0068:ed01deac [1482269.954373] ---[ end trace a94d458d25379224 ]--- cfarrell@paddy:~/Documents> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=659888 https://bugzilla.novell.com/show_bug.cgi?id=659888#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jeffm@novell.com Resolution| |FEATURE --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2011-02-10 00:52:47 UTC --- Nope, it didn't. That's the oops you're seeing - it's trying to sync on your usb stick. Currently btrfs lacks graceful error handling and handles most error conditions with BUG_ON, which is what you're seeing. You should always eject your usb stick either with the eject command or your desktop environment's eject function. I'm going to close this as FEATURE because btrfs is, unfortunately, expected to behave this way for now. Novell FATE#306585 covers this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com