From: Edilson Osorio Junior <ed.junior@oztechnology.com.br>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs problem - trace attached
Date: Wed, 18 Jan 2012 17:34:02 -0200 [thread overview]
Message-ID: <4F171EAA.2000201@oztechnology.com.br> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2641 bytes --]
Hi all,
I got this kernel dump when trying to remove some files.
Now, when I try to access the directory, or any file there I get:
---
[xxx@tyler vbox]$ ls
ls: cannot access machine: Stale NFS file handle
harddisk machine
[xxx@tyler vbox]$ cd machine
bash: cd: machine: Stale NFS file handle
[xxx@tyler vbox]$ ls -la
ls: cannot access machine: Stale NFS file handle
total 0
drwxrwxr-x 1 root root 30 Dec 22 2010 .
drwxrwxr-x 1 root root 112 Jan 18 16:29 ..
drwxrwxr-x 1 root root 154 Jan 18 16:30 harddisk
d????????? ? ? ? ? ? machine
---
On time: that is a local directory, that's not mounted over NFS at all.
---
My system:
Fedora release 15 (Lovelock)
Linux tyler.xxx 2.6.41.9-1.fc15.i686.PAE #1 SMP Fri Jan 13 16:35:57 UTC
2012 i686 i686 i386 GNU/Linux
Btrfs mount over raid0
[xxx@tyler vbox]$ cat /proc/mdstat
Personalities : [raid0]
md0 : active raid0 sdb1[0] sdc1[1]
312573952 blocks super 1.2 512k chunks
unused devices: <none>
[xxx@tyler vbox]$ mount
[cut]
/dev/md0 on /installed/utils type btrfs (rw,relatime)
[cut]
---
Hope it could be helpful to deploy.
Best regards,
Edilson
--
------------------------------------------------------------------------
*Edilson Osorio Junior*
Chief Information Officer
*OZ Technology*
Phone: +55 11 3892-8272
email: ed.junior@oztechnology.com.br
<mailto:ed.junior@oztechnology.com.br>
www: www.oztechnology.com.br <http://www.oztechnology.com.br>
[restrito]
while (!(succeed == try()))
*P* *Antes de imprimir pense em seu compromisso com o Meio Ambiente**//**P*
------------------------------------------------------------------------
As informações contidas nesta mensagem podem ser confidenciais e/ou
privilegiadas. Se você não é seu o destinatário final ou não está
autorizado a recebê-la em nome do destinatário, fica expressamente
vedado o direito de copiar, divulgar ou utilizar as informações nela
contidas. Caso tenha recebido esta mensagem por engano, favor entrar em
contato com o autor, utilizando endereço de correio ou telefone, e
comunicar o ocorrido, removendo-a em seguida. Obrigado pela cooperação.
This message may contain confidential and/or privileged information. If
you are not the address or a third-party person authorized to receive
this for the address, you must not use, copy, disclose or take any
action based on this message or any information here . If you have
received this message in error, please advise the sender immediately by
replying this e-mail and deleting this message. Thank you for the
comprehension.
[-- Attachment #1.2: btrfs-trace-20120118.txt --]
[-- Type: text/plain, Size: 3594 bytes --]
Jan 18 16:20:03 tyler kernel: [103530.372167] btrfs: corrupt leaf, bad key order: block=155084496896,root=1, slot=13
Jan 18 16:21:33 tyler kernel: [103620.374871] device eth0 entered promiscuous mode
Jan 18 16:31:51 tyler kernel: [104236.059293] ------------[ cut here ]------------
Jan 18 16:31:51 tyler kernel: [104236.059328] kernel BUG at fs/btrfs/transaction.c:1244!
Jan 18 16:31:51 tyler kernel: [104236.059361] invalid opcode: 0000 [#1] SMP
Jan 18 16:31:51 tyler kernel: [104236.059392] Modules linked in: tcp_lp fuse nfs lockd fscache auth_rpcgss nfs_acl tpm_infineon vboxpci vboxnetadp vboxnetflt sunrpc vboxdrv ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables btrfs zlib_deflate libcrc32c raid0 snd_hda_codec_hdmi snd_hda_codec_realtek ppdev gspca_zc3xx gspca_main videodev microcode media i2c_i801 serio_raw joydev snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device sundance mii snd_pcm iTCO_wdt iTCO_vendor_support snd_timer snd soundcore snd_page_alloc e1000e parport_pc parport virtio_net kvm_intel kvm ipv6 pata_acpi ata_generic i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: mperf]
Jan 18 16:31:51 tyler kernel: [104236.059902]
Jan 18 16:31:51 tyler kernel: [104236.059915] Pid: 853, comm: btrfs-transacti Tainted: G C 2.6.41.4-1.fc15.i686 #1 /DH55HC
Jan 18 16:31:51 tyler kernel: [104236.059982] EIP: 0060:[<fa3a418f>] EFLAGS: 00010282 CPU: 0
Jan 18 16:31:51 tyler kernel: [104236.060034] EIP is at btrfs_commit_transaction+0x1f0/0x68d [btrfs]
Jan 18 16:31:51 tyler kernel: [104236.060071] EAX: fffffffe EBX: f2049000 ECX: fffffffe EDX: 00040e92
Jan 18 16:31:51 tyler kernel: [104236.060108] ESI: 00000000 EDI: 00000000 EBP: f2699f84 ESP: f2699f38
Jan 18 16:31:51 tyler kernel: [104236.060146] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan 18 16:31:51 tyler kernel: [104236.060179] Process btrfs-transacti (pid: 853, ti=f2698000 task=f2127110 task.ti=f2698000)
Jan 18 16:31:51 tyler kernel: [104236.060226] Stack:
Jan 18 16:31:51 tyler kernel: [104236.060240] 00000000 00000298 00000000 d726c2b8 cd4926f0 d726c260 00000000 f2127110
Jan 18 16:31:51 tyler kernel: [104236.060304] c04548b1 f2699f5c f2699f5c 00000000 00000000 f2049000 f2127110 00000000
Jan 18 16:31:51 tyler kernel: [104236.060367] f2049000 f2127110 00000000 f2699fb8 fa39ef14 000086dc f2127110 f2699f9c
Jan 18 16:31:51 tyler kernel: [104236.060431] Call Trace:
Jan 18 16:31:51 tyler kernel: [104236.060453] [<c04548b1>] ? remove_wait_queue+0x2c/0x2c
Jan 18 16:31:51 tyler kernel: [104236.060500] [<fa39ef14>] transaction_kthread+0x138/0x1d3 [btrfs]
Jan 18 16:31:51 tyler kernel: [104236.060540] [<c07f9f2b>] ? _raw_spin_unlock_irqrestore+0x13/0x15
Jan 18 16:31:51 tyler kernel: [104236.060591] [<fa39eddc>] ? btrfs_congested_fn+0x68/0x68 [btrfs]
Jan 18 16:31:51 tyler kernel: [104236.060627] [<c04543ac>] kthread+0x67/0x6c
Jan 18 16:31:51 tyler kernel: [104236.060654] [<c0454345>] ? kthread_worker_fn+0x11d/0x11d
Jan 18 16:31:51 tyler kernel: [104236.060688] [<c080023e>] kernel_thread_helper+0x6/0x10
Jan 18 16:31:51 tyler kernel: [104236.060721] Code: 00 00 89 d8 e8 85 c1 00 00 31 d2 b9 01 00 00 00 89 d8 e8 99 60 01 00 85 c0 74 02 0f 0b 8b 45 c4 89 da e8 d9 87 03 00 85 c0 74 02 <0f> 0b ba 01 00 00 00 89 d8 e8 fb 64 01 00 8b 45 c0 8d 55 cc b9
Jan 18 16:31:51 tyler kernel: [104236.061012] EIP: [<fa3a418f>] btrfs_commit_transaction+0x1f0/0x68d [btrfs] SS:ESP 0068:f2699f38
Jan 18 16:31:51 tyler kernel: [104236.122706] ---[ end trace 324e53d6be740fbd ]---
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
reply other threads:[~2012-01-18 19:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F171EAA.2000201@oztechnology.com.br \
--to=ed.junior@oztechnology.com.br \
--cc=linux-btrfs@vger.kernel.org \
/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).