public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lex \"x-demon\" Rivera" <x-demon@x-demon.org>
To: "Yan, Zheng" <yanzheng@21cn.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs fails randomly
Date: Tue, 29 Dec 2009 00:51:49 +0300	[thread overview]
Message-ID: <fcfb36620912281351h28f87b3cy2db815ffc6a47421@mail.gmail.com> (raw)
In-Reply-To: <fcfb36620912280137l3cab6b0du5678a6da77f7b301@mail.gmail.com>

Whole day running, no problems. Without patch it crashes 4-5 times/day.=
 Thanks!


Best regards, Lex "x-demon" Rivera
|| ICQ 625558 | Jabber x-demon@x-demon.org | http://x-demon.org ||




On Mon, Dec 28, 2009 at 12:37 PM, Lex "x-demon" Rivera
<x-demon@x-demon.org> wrote:
> Patched, installed, running. (After some sex with vermagic, but in wo=
rks)
> Will report after 6-7 hours of running without failures.
>
>
> Best regards, Lex "x-demon" Rivera
> || ICQ 625558 | Jabber x-demon@x-demon.org | http://x-demon.org ||
>
>
>
>
> On Mon, Dec 28, 2009 at 8:01 AM, Yan, Zheng <yanzheng@21cn.com> wrote=
:
>> On Sun, Dec 27, 2009 at 3:34 PM, Lex "x-demon" Rivera
>> <x-demon@x-demon.org> wrote:
>>> Btrfs fails randomly, after this error in dmesg i can't exec any ap=
ps,
>>> but can read/write to disc. Log attached, it's always the same, exc=
ept
>>> process that caused this.
>>>
>>> t fs/btrfs/ordered-data.c:672!
>>> invalid opcode: 0000 [#1] PREEMPT SMP
>>> last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_f=
req
>>> Modules linked in: ipv6 fuse aes_i586 aes_generic rfcomm sco bridge
>>> stp llc bnep l2cap crc16 ext3 jbd mbcache arc4 ecb b43 btusb
>>> snd_hda_codec_analog bluetooth snd_seq_dummy pciehp uvcvideo mac802=
11
>>> pci_hotplug videodev v4l1_compat cfg80211 snd_seq_oss rfkill
>>> snd_seq_midi_event cpufreq_conservative snd_hda_intel iTCO_wdt ssb
>>> snd_seq iTCO_vendor_support snd_hda_codec snd_seq_device joydev
>>> snd_hwdep snd_pcm_oss snd_mixer_oss hp_accel snd_pcm mmc_core
>>> lis3lv02d acpi_cpufreq snd_timer uhci_hcd snd ehci_hcd fan
>>> input_polldev pcmcia soundcore sky2 usbcore led_class wmi
>>> snd_page_alloc pcmcia_core evdev psmouse ac thermal battery serio_r=
aw
>>> pcspkr sg freq_table processor rtc_cmos rtc_core rtc_lib sd_mod
>>> ata_piix ahci libata scsi_mod btrfs crc32c libcrc32c zlib_deflate l=
zo
>>> lzo_decompress lzo_compress i915 drm_kms_helper drm i2c_algo_bit
>>> button i2c_core video output intel_agp agpgart
>>>
>>> Pid: 15778, comm: iron Not tainted (2.6.32-ZEN #1) HP 2140
>>> EIP: 0060:[<f85bd96b>] EFLAGS: 00210287 CPU: 1
>>> EIP is at btrfs_ordered_update_i_size+0x40b/0x750 [btrfs]
>>> EAX: 00006000 EBX: 00005e7d ECX: a40e8f80 EDX: 00000000
>>> ESI: 00000000 EDI: b2dc5684 EBP: 00000000 ESP: a3157e74
>>> =C2=A0DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
>>> =C2=A0Process iron (pid: 15778, ti=3Da3156000 task=3Db68e6bd0 task.=
ti=3Da3156000)
>>> =C2=A0Stack:
>>> =C2=A000005e7c 00000000 00000020 00000000 00000000 22222222 2222222=
2 b2dc5570
>>> =C2=A0<0> b2dc5550 00000000 b2dc55cc f858cd75 f6983000 00000000 000=
05e7d fffff000
>>> =C2=A0<0> b2dc5570 0000d000 00000000 a3157f34 00000000 b2dc5684 000=
00000 f85ac3f7
>>> =C2=A0Call Trace:
>>> [<f858cd75>] ? __find_space_info+0x55/0x60 [btrfs]
>>> [<f85ac3f7>] ? btrfs_setattr+0x1e7/0x310 [btrfs]
>>> [<810f7324>] ? notify_change+0x134/0x320
>>> [<812b144c>] ? __mutex_lock_slowpath+0x1ec/0x2c0
>>> [<810e1721>] ? do_truncate+0x61/0x90
>>> [<810cf186>] ? mmap_region+0x1b6/0x450
>>> [<810e1842>] ? do_sys_ftruncate+0xf2/0x150
>>> [<810e18cd>] ? sys_ftruncate64+0x2d/0x40
>>> [<810039f3>] ? sysenter_do_call+0x12/0x28
>>> Code: 9c 00 00 00 85 c0 74 30 8b 50 bc 8d 48 b8 8b 40 b8 39 d6 72 2=
3
>>> 77 04 39 c3 72 1d 03 41 10 13 51 14 39 d6 72 06 77 11 39 c3 73 0d <=
0f>
>>> 0b 8d 76 00 eb fb 8d b6 00 00 00 00 8b 44 24 20 8b 88 98 00
>>> EIP: [<f85bd96b>] btrfs_ordered_update_i_size+0x40b/0x750 [btrfs]
>>> SS:ESP 0068:a3157e74
>>> ---[ end trace 1adab407699b39c3 ]---
>>>
>>>
>> Thank you for reporting this. Please try patch attached below.
>>
>> Yan, Zheng
>>
>> ---
>> diff -urp 1/fs/btrfs/ordered-data.c 2/fs/btrfs/ordered-data.c
>> --- 1/fs/btrfs/ordered-data.c =C2=A0 2009-12-28 12:23:42.088546898 +=
0800
>> +++ 2/fs/btrfs/ordered-data.c =C2=A0 2009-12-28 12:57:24.250542741 +=
0800
>> @@ -626,6 +626,8 @@ int btrfs_ordered_update_i_size(struct i
>>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0if (ordered)
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0offset =3D en=
try_end(ordered);
>> + =C2=A0 =C2=A0 =C2=A0 else
>> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 offset =3D ALIGN(=
offset, BTRFS_I(inode)->root->sectorsize);
>>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0mutex_lock(&tree->mutex);
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0disk_i_size =3D BTRFS_I(inode)->disk_i_si=
ze;
>> ---
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-12-28 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fcfb36620912262329s73b1f1ffj5eb7f3ae8acb0013@mail.gmail.com>
2009-12-27  7:34 ` Btrfs fails randomly Lex "x-demon" Rivera
2009-12-28  5:01   ` Yan, Zheng 
2009-12-28  9:37     ` Lex "x-demon" Rivera
2009-12-28 21:51       ` Lex "x-demon" Rivera [this message]

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=fcfb36620912281351h28f87b3cy2db815ffc6a47421@mail.gmail.com \
    --to=x-demon@x-demon.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=yanzheng@21cn.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