Re: kernel BUG at fs/btrfs/inode.c:2271!
Am 25.05.2011 um 21:25 schrieb Josef Back: Hrm well that's doubly weird, the root should be right so it should be able to find the orphan item to delete it for the bad inode, and why the hell are we looping on that orphan item? Remove the previous patch I gave you and apply this one instead and run with this please and provide me the log. Sorry in advance, it will likely give you a giant log file again. Thanks, The system didn't crash until now and all I got in the log was the following output. This is the expected correct behavior? May 26 03:10:13 mainframe kernel: found orphan item for 909457 on 267 May 26 03:10:13 mainframe kernel: lookup of inode was from disk May 26 03:10:13 mainframe kernel: inode needs to be truncated May 26 03:10:13 mainframe kernel: drop is 0 May 26 03:10:13 mainframe kernel: found orphan item for 909415 on 267 May 26 03:10:13 mainframe kernel: lookup of inode was from disk May 26 03:10:13 mainframe kernel: inode needs to be unlinked May 26 03:10:13 mainframe kernel: drop is 1 May 26 03:10:13 mainframe kernel: found orphan item for 909414 on 267 May 26 03:10:13 mainframe kernel: lookup of inode was from disk May 26 03:10:13 mainframe kernel: inode needs to be unlinked May 26 03:10:13 mainframe kernel: drop is 1 May 26 03:10:13 mainframe kernel: found orphan item for 899452 on 267 May 26 03:10:13 mainframe kernel: lookup of inode was from disk May 26 03:10:13 mainframe kernel: inode needs to be unlinked May 26 03:10:13 mainframe kernel: drop is 1 May 26 03:10:13 mainframe kernel: found orphan item for 899451 on 267 May 26 03:10:13 mainframe kernel: lookup of inode was from disk May 26 03:10:13 mainframe kernel: inode needs to be unlinked May 26 03:10:13 mainframe kernel: drop is 1 May 26 03:10:13 mainframe kernel: btrfs: unlinked 4 orphans May 26 03:10:13 mainframe kernel: btrfs: truncated 1 orphans May 26 03:10:46 mainframe kernel: drop is 0 I'll keep an eye on it. -marco -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: kernel BUG at fs/btrfs/inode.c:2271!
On 05/27/2011 03:23 PM, Marco Neubauer wrote: Am 25.05.2011 um 21:25 schrieb Josef Back: Hrm well that's doubly weird, the root should be right so it should be able to find the orphan item to delete it for the bad inode, and why the hell are we looping on that orphan item? Remove the previous patch I gave you and apply this one instead and run with this please and provide me the log. Sorry in advance, it will likely give you a giant log file again. Thanks, The system didn't crash until now and all I got in the log was the following output. This is the expected correct behavior? Well I was expecting a panic message and such, but if you didn't get any of that I'm stumped. I guess this means you've gotten past the mount section and are able to run for a while before it blows up? Thanks, Josef -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: kernel BUG at fs/btrfs/inode.c:2271!
On 05/24/2011 02:55 PM, Marco Neubauer wrote:
Am 23.05.2011 um 21:14 schrieb Josef Bacik:
On 05/22/2011 07:13 AM, Marco Neubauer wrote:
Am 03.05.2011 um 16:54 schrieb Josef Bacik:
On 04/27/2011 02:52 PM, Marco Neubauer wrote:
Hi,
this is happening mostly every night. I can't reproduce it right now.
vanilla kernel 2.6.38.4
Can you update to a newer kernel, this should be fixed there. Thanks,
It's happening again.
[ cut here ]
Can you apply this patch and reproduce and send me the output so I can
figure
out whats going wrong? Thanks,
Hrm well that's doubly weird, the root should be right so it should be
able to find the orphan item to delete it for the bad inode, and why the
hell are we looping on that orphan item? Remove the previous patch I
gave you and apply this one instead and run with this please and provide
me the log. Sorry in advance, it will likely give you a giant log file
again. Thanks,
Josef
diff --git a/fs/btrfs/btrfs_inode.h b/fs/btrfs/btrfs_inode.h
index 4bc852d..d85a309 100644
--- a/fs/btrfs/btrfs_inode.h
+++ b/fs/btrfs/btrfs_inode.h
@@ -149,6 +149,7 @@ struct btrfs_inode {
unsigned ordered_data_close:1;
unsigned orphan_meta_reserved:1;
unsigned dummy_inode:1;
+ unsigned orphaned:1;
/*
* always compress this one file
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index 5fa0ae7..a49f848 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -2314,6 +2314,8 @@ int btrfs_orphan_cleanup(struct btrfs_root *root)
key.offset = (u64)-1;
while (1) {
+ int new;
+
ret = btrfs_search_slot(NULL, root, key, path, 0, 0);
if (ret 0)
goto out;
@@ -2340,6 +2342,9 @@ int btrfs_orphan_cleanup(struct btrfs_root *root)
if (btrfs_key_type(found_key) != BTRFS_ORPHAN_ITEM_KEY)
break;
+ printk(KERN_ERR found orphan item for %llu on %llu\n,
+ found_key.offset, root-root_key.objectid);
+
/* release the path since we're done with it */
btrfs_release_path(root, path);
@@ -2351,12 +2356,15 @@ int btrfs_orphan_cleanup(struct btrfs_root *root)
found_key.objectid = found_key.offset;
found_key.type = BTRFS_INODE_ITEM_KEY;
found_key.offset = 0;
- inode = btrfs_iget(root-fs_info-sb, found_key, root, NULL);
+ inode = btrfs_iget(root-fs_info-sb, found_key, root, new);
if (IS_ERR(inode)) {
ret = PTR_ERR(inode);
goto out;
}
+ printk(KERN_ERR lookup of inode was%s from disk,
+ new ? : not);
+ BTRFS_I(inode)-orphaned = 1;
/*
* add this inode to the orphan list so btrfs_orphan_del does
* the proper thing when we hit it
@@ -2372,6 +2380,8 @@ int btrfs_orphan_cleanup(struct btrfs_root *root)
* do a destroy_inode
*/
if (is_bad_inode(inode)) {
+ printk(KERN_ERR %llu is a bad inode, root is %llu\n,
+ inode-i_ino,
BTRFS_I(inode)-root-root_key.objectid);
trans = btrfs_start_transaction(root, 0);
if (IS_ERR(trans)) {
ret = PTR_ERR(trans);
@@ -2385,7 +2395,10 @@ int btrfs_orphan_cleanup(struct btrfs_root *root)
/* if we have links, this was a truncate, lets do that */
if (inode-i_nlink) {
+ printk(KERN_ERR inode needs to be truncated\n);
if (!S_ISREG(inode-i_mode)) {
+ printk(KERN_ERR file mode is %lu, nlink is
+ %lu\n, inode-i_mode, inode-i_nlink);
WARN_ON(1);
iput(inode);
continue;
@@ -2393,6 +2406,7 @@ int btrfs_orphan_cleanup(struct btrfs_root *root)
nr_truncate++;
ret = btrfs_truncate(inode);
} else {
+ printk(KERN_ERR inode needs to be unlinked\n);
nr_unlink++;
}
@@ -3755,10 +3769,18 @@ void btrfs_evict_inode(struct inode *inode)
truncate_inode_pages(inode-i_data, 0);
if (inode-i_nlink (btrfs_root_refs(root-root_item) != 0 ||
- root == root-fs_info-tree_root))
+ root == root-fs_info-tree_root)) {
+ if (BTRFS_I(inode)-orphaned)
+ printk(KERN_ERR inode-i_nlink=%d, btrfs_root_refs=%d,
+ root==tree_root=%s\n, inode-i_nlink,
+ btrfs_root_refs(root-root_item),
+ (root ==
Re: kernel BUG at fs/btrfs/inode.c:2271!
Am 23.05.2011 um 21:14 schrieb Josef Bacik: On 05/22/2011 07:13 AM, Marco Neubauer wrote: Am 03.05.2011 um 16:54 schrieb Josef Bacik: On 04/27/2011 02:52 PM, Marco Neubauer wrote: Hi, this is happening mostly every night. I can't reproduce it right now. vanilla kernel 2.6.38.4 Can you update to a newer kernel, this should be fixed there. Thanks, It's happening again. [ cut here ] Can you apply this patch and reproduce and send me the output so I can figure out whats going wrong? Thanks, May 24 03:10:01 mainframe cron[13013]: (root) CMD (test -x /usr/sbin/run-crons /usr/sbin/run-crons ) May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 May 24 03:10:11 mainframe kernel: lookup of inode was from disk May 24 03:10:11 mainframe kernel: found orphan item for 899452 on 267 - cut - A lot more messages. The entire file is 5.19 GB. May 24 03:51:47 mainframe kernel: found orphan item for 899452 on 267 May 24 03:51:47 mainframe kernel: lookup of inode was from disk May 24 03:51:47 mainframe kernel: found orphan item for 899452 on 267 May 24 03:51:47 mainframe kernel: lookup of inode was from disk May 24 03:51:47 mainframe kernel: found orphan item for 909358 on 267 May 24 03:51:47 mainframe kernel: lookup of inode was from disk May 24 03:51:47 mainframe kernel: 909358 is a bad inode May 24 03:51:47 mainframe kernel: [ cut here ] May 24 03:51:47 mainframe kernel: kernel BUG at fs/btrfs/inode.c:2285! May 24 03:51:47 mainframe kernel: invalid opcode: [#1] PREEMPT SMP May 24 03:51:47 mainframe kernel: last sysfs file: /sys/devices/pci:00/:00:1f.2/host2/target2:0:0/2:0:0:0/block/sdc/sdc2/stat May 24 03:51:47 mainframe kernel: CPU 0 May 24 03:51:47 mainframe kernel: Modules linked in: w83627ehf hwmon_vid coretemp md4 cifs vboxnetadp vboxnetflt vboxdrv firewire_ohci firewire_core i915 asus_atk0110 hwmon drm_kms_helper video backlight May 24 03:51:47 mainframe kernel: May 24 03:51:47 mainframe kernel: Pid: 13541, comm: updatedb Tainted: G W 2.6.39 #2 System manufacturer System Product Name/V-P5G45 May 24 03:51:47 mainframe kernel: RIP: 0010:[8124b8e6] [8124b8e6] btrfs_orphan_del+0xe6/0xf0 May 24 03:51:47 mainframe kernel: RSP: 0018:88011be55ab8 EFLAGS: 00010282 May 24 03:51:47 mainframe kernel: RAX: fffe RBX: 880023fa8988 RCX: 0ab00490 May 24 03:51:47 mainframe kernel: RDX: 0ab0048c RSI: 000199b0 RDI: ea0007a2c268 May 24 03:51:47 mainframe kernel: RBP: R08: 8127b558 R09: 0238 May 24 03:51:47 mainframe kernel: R10: 0042 R11: R12: 8800c352d740 May 24 03:51:47 mainframe kernel: R13: 88022b47 R14: 88022b470330 R15: 0001 May 24 03:51:47 mainframe kernel: FS: 7f86a60d3700() GS:88022fc0() knlGS: May 24 03:51:47 mainframe kernel: CS: 0010 DS: ES: CR0: 8005003b May 24 03:51:47 mainframe kernel: CR2: 7f38a80c1000 CR3: 00011bf21000
Re: kernel BUG at fs/btrfs/inode.c:2271!
On 05/22/2011 07:13 AM, Marco Neubauer wrote: Am 03.05.2011 um 16:54 schrieb Josef Bacik: On 04/27/2011 02:52 PM, Marco Neubauer wrote: Hi, this is happening mostly every night. I can't reproduce it right now. vanilla kernel 2.6.38.4 Can you update to a newer kernel, this should be fixed there. Thanks, It's happening again. [ cut here ] WARNING: at fs/btrfs/inode.c:2394 btrfs_orphan_cleanup+0x1fe/0x3b0() Hardware name: System Product Name Modules linked in: w83627ehf hwmon_vid coretemp md4 cifs vboxnetadp vboxnetflt vboxdrv firewire_ohci firewire_core i915 asus_atk0110 hwmon drm_kms_helper video backlight Pid: 12355, comm: updatedb Not tainted 2.6.39 #1 Call Trace: [8103f16b] ? warn_slowpath_common+0x7b/0xc0 [81250fee] ? btrfs_orphan_cleanup+0x1fe/0x3b0 [812509a3] ? btrfs_iget+0x53/0x4a0 [812515b8] ? btrfs_lookup_dentry+0x418/0x490 [81251639] ? btrfs_lookup+0x9/0x20 [810f7e3c] ? d_alloc_and_lookup+0x3c/0x90 [81102a6e] ? d_lookup+0x2e/0x60 [810f98db] ? do_lookup+0xcb/0x2b0 [810f9c0b] ? path_init+0x14b/0x3d0 [810fbf74] ? path_lookupat+0x154/0x750 [810f99f0] ? do_lookup+0x1e0/0x2b0 [810fc59c] ? do_path_lookup+0x2c/0xd0 [810f8776] ? getname_flags+0x126/0x260 [810fd31c] ? user_path_at+0x5c/0xc0 [810fc59c] ? do_path_lookup+0x2c/0xd0 [810f1f50] ? cp_new_stat+0xe0/0x100 [810f2053] ? vfs_fstatat+0x43/0x80 [810f211f] ? sys_newlstat+0x1f/0x50 [8169e47b] ? system_call_fastpath+0x16/0x1b ---[ end trace dfa7e3e0b20f3e13 ]--- [ cut here ] kernel BUG at fs/btrfs/inode.c:2285! invalid opcode: [#1] PREEMPT SMP last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq CPU 0 Modules linked in: w83627ehf hwmon_vid coretemp md4 cifs vboxnetadp vboxnetflt vboxdrv firewire_ohci firewire_core i915 asus_atk0110 hwmon drm_kms_helper video backlight Pid: 12355, comm: updatedb Tainted: GW 2.6.39 #1 System manufacturer System Product Name/V-P5G45 RIP: 0010:[8124b8e6] [8124b8e6] btrfs_orphan_del+0xe6/0xf0 RSP: 0018:880186b81ab8 EFLAGS: 00010282 RAX: fffe RBX: 88007e72ed40 RCX: 00d14404 RDX: 00d14400 RSI: 000199b0 RDI: ea0007a2c310 RBP: R08: 8127b4b8 R09: 021f R10: 0047 R11: R12: 8801eae47640 R13: 88022dee5800 R14: 88022dee5b30 R15: 0001 FS: 7feb837fe700() GS:88022fc0() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0310b011 CR3: 000183fb6000 CR4: 000406f0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process updatedb (pid: 12355, threadinfo 880186b8, task 88021537c060) Stack: 880100da2158 88022dee5800 88022e80e900 88022dee5b30 88022dee5b38 880186b81b58 880186b81b18 8125104b 880186b80010 88007e72ed40 8801eae47640 159e523f Call Trace: [8125104b] ? btrfs_orphan_cleanup+0x25b/0x3b0 [812509a3] ? btrfs_iget+0x53/0x4a0 [812515b8] ? btrfs_lookup_dentry+0x418/0x490 [81251639] ? btrfs_lookup+0x9/0x20 [810f7e3c] ? d_alloc_and_lookup+0x3c/0x90 [81102a6e] ? d_lookup+0x2e/0x60 [810f98db] ? do_lookup+0xcb/0x2b0 [810f9c0b] ? path_init+0x14b/0x3d0 [810fbf74] ? path_lookupat+0x154/0x750 [810f99f0] ? do_lookup+0x1e0/0x2b0 [810fc59c] ? do_path_lookup+0x2c/0xd0 [810f8776] ? getname_flags+0x126/0x260 [810fd31c] ? user_path_at+0x5c/0xc0 [810fc59c] ? do_path_lookup+0x2c/0xd0 [810f1f50] ? cp_new_stat+0xe0/0x100 [810f2053] ? vfs_fstatat+0x43/0x80 [810f211f] ? sys_newlstat+0x1f/0x50 [8169e47b] ? system_call_fastpath+0x16/0x1b Code: 4c 8b 6c 24 20 4c 8b 74 24 28 4c 8b 7c 24 30 48 83 c4 38 c3 90 48 8b 93 a8 00 00 00 4c 89 ee 4c 89 e7 e8 5e fb 02 00 85 c0 74 b8 0f 0b eb fe 66 0f 1f 44 00 00 53 48 8d 86 38 03 00 00 48 89 f3 RIP [8124b8e6] btrfs_orphan_del+0xe6/0xf0 RSP 880186b81ab8 ---[ end trace dfa7e3e0b20f3e14 ]--- # btrfs fi show Label: 'ROOT' uuid: 0292b87e-84b3-457f-abae-c2eb03e9d08e Total devices 1 FS bytes used 15.73GB devid1 size 111.67GB used 49.79GB path /dev/sdc2 Label: 'DATA' uuid: 07f62881-5cc4-4f8f-b304-7e7a3aae4adc Total devices 1 FS bytes used 572.87GB devid1 size 592.25GB used 592.25GB path /dev/md1 Btrfs Btrfs v0.19 # btrfs sub list / ID 267 top level 5 path subvol/home # btrfs sub list /var/ ID 643 top level 5 path subvol/tmp ID 644 top level 5 path subvol/var ID 730 top level 5 path subvol/homedata # mount /dev/root
Re: kernel BUG at fs/btrfs/inode.c:2271!
Am 03.05.2011 um 16:54 schrieb Josef Bacik: On 04/27/2011 02:52 PM, Marco Neubauer wrote: Hi, this is happening mostly every night. I can't reproduce it right now. vanilla kernel 2.6.38.4 Can you update to a newer kernel, this should be fixed there. Thanks, It's happening again. [ cut here ] WARNING: at fs/btrfs/inode.c:2394 btrfs_orphan_cleanup+0x1fe/0x3b0() Hardware name: System Product Name Modules linked in: w83627ehf hwmon_vid coretemp md4 cifs vboxnetadp vboxnetflt vboxdrv firewire_ohci firewire_core i915 asus_atk0110 hwmon drm_kms_helper video backlight Pid: 12355, comm: updatedb Not tainted 2.6.39 #1 Call Trace: [8103f16b] ? warn_slowpath_common+0x7b/0xc0 [81250fee] ? btrfs_orphan_cleanup+0x1fe/0x3b0 [812509a3] ? btrfs_iget+0x53/0x4a0 [812515b8] ? btrfs_lookup_dentry+0x418/0x490 [81251639] ? btrfs_lookup+0x9/0x20 [810f7e3c] ? d_alloc_and_lookup+0x3c/0x90 [81102a6e] ? d_lookup+0x2e/0x60 [810f98db] ? do_lookup+0xcb/0x2b0 [810f9c0b] ? path_init+0x14b/0x3d0 [810fbf74] ? path_lookupat+0x154/0x750 [810f99f0] ? do_lookup+0x1e0/0x2b0 [810fc59c] ? do_path_lookup+0x2c/0xd0 [810f8776] ? getname_flags+0x126/0x260 [810fd31c] ? user_path_at+0x5c/0xc0 [810fc59c] ? do_path_lookup+0x2c/0xd0 [810f1f50] ? cp_new_stat+0xe0/0x100 [810f2053] ? vfs_fstatat+0x43/0x80 [810f211f] ? sys_newlstat+0x1f/0x50 [8169e47b] ? system_call_fastpath+0x16/0x1b ---[ end trace dfa7e3e0b20f3e13 ]--- [ cut here ] kernel BUG at fs/btrfs/inode.c:2285! invalid opcode: [#1] PREEMPT SMP last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq CPU 0 Modules linked in: w83627ehf hwmon_vid coretemp md4 cifs vboxnetadp vboxnetflt vboxdrv firewire_ohci firewire_core i915 asus_atk0110 hwmon drm_kms_helper video backlight Pid: 12355, comm: updatedb Tainted: GW 2.6.39 #1 System manufacturer System Product Name/V-P5G45 RIP: 0010:[8124b8e6] [8124b8e6] btrfs_orphan_del+0xe6/0xf0 RSP: 0018:880186b81ab8 EFLAGS: 00010282 RAX: fffe RBX: 88007e72ed40 RCX: 00d14404 RDX: 00d14400 RSI: 000199b0 RDI: ea0007a2c310 RBP: R08: 8127b4b8 R09: 021f R10: 0047 R11: R12: 8801eae47640 R13: 88022dee5800 R14: 88022dee5b30 R15: 0001 FS: 7feb837fe700() GS:88022fc0() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0310b011 CR3: 000183fb6000 CR4: 000406f0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process updatedb (pid: 12355, threadinfo 880186b8, task 88021537c060) Stack: 880100da2158 88022dee5800 88022e80e900 88022dee5b30 88022dee5b38 880186b81b58 880186b81b18 8125104b 880186b80010 88007e72ed40 8801eae47640 159e523f Call Trace: [8125104b] ? btrfs_orphan_cleanup+0x25b/0x3b0 [812509a3] ? btrfs_iget+0x53/0x4a0 [812515b8] ? btrfs_lookup_dentry+0x418/0x490 [81251639] ? btrfs_lookup+0x9/0x20 [810f7e3c] ? d_alloc_and_lookup+0x3c/0x90 [81102a6e] ? d_lookup+0x2e/0x60 [810f98db] ? do_lookup+0xcb/0x2b0 [810f9c0b] ? path_init+0x14b/0x3d0 [810fbf74] ? path_lookupat+0x154/0x750 [810f99f0] ? do_lookup+0x1e0/0x2b0 [810fc59c] ? do_path_lookup+0x2c/0xd0 [810f8776] ? getname_flags+0x126/0x260 [810fd31c] ? user_path_at+0x5c/0xc0 [810fc59c] ? do_path_lookup+0x2c/0xd0 [810f1f50] ? cp_new_stat+0xe0/0x100 [810f2053] ? vfs_fstatat+0x43/0x80 [810f211f] ? sys_newlstat+0x1f/0x50 [8169e47b] ? system_call_fastpath+0x16/0x1b Code: 4c 8b 6c 24 20 4c 8b 74 24 28 4c 8b 7c 24 30 48 83 c4 38 c3 90 48 8b 93 a8 00 00 00 4c 89 ee 4c 89 e7 e8 5e fb 02 00 85 c0 74 b8 0f 0b eb fe 66 0f 1f 44 00 00 53 48 8d 86 38 03 00 00 48 89 f3 RIP [8124b8e6] btrfs_orphan_del+0xe6/0xf0 RSP 880186b81ab8 ---[ end trace dfa7e3e0b20f3e14 ]--- # btrfs fi show Label: 'ROOT' uuid: 0292b87e-84b3-457f-abae-c2eb03e9d08e Total devices 1 FS bytes used 15.73GB devid1 size 111.67GB used 49.79GB path /dev/sdc2 Label: 'DATA' uuid: 07f62881-5cc4-4f8f-b304-7e7a3aae4adc Total devices 1 FS bytes used 572.87GB devid1 size 592.25GB used 592.25GB path /dev/md1 Btrfs Btrfs v0.19 # btrfs sub list / ID 267 top level 5 path subvol/home # btrfs sub list /var/ ID 643 top level 5 path subvol/tmp ID 644 top level 5 path subvol/var ID 730 top level 5 path subvol/homedata # mount /dev/root on / type btrfs (rw,relatime,compress=zlib,ssd,discard,space_cache) /dev/sdc2 on /home type btrfs (rw,subvolid=267,compress,space_cache,ssd,discard)
Re: kernel BUG at fs/btrfs/inode.c:2271!
On 04/27/2011 02:52 PM, Marco Neubauer wrote: Hi, this is happening mostly every night. I can't reproduce it right now. vanilla kernel 2.6.38.4 Can you update to a newer kernel, this should be fixed there. Thanks, Josef -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
