CEPH filesystem development
 help / color / mirror / Atom feed
From: Martin Mailand <martin@tuxadero.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: rbd snap
Date: Fri, 16 Sep 2011 23:32:20 +0200	[thread overview]
Message-ID: <4E73C064.7020104@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1109160928170.11043@cobra.newdream.net>

Hi Sage,
yes, that fixes the btrfs problem. But now I have a new bug.

root@c-brick-001:~# rbd rm --snap=2011091601 test
*** Caught signal (Segmentation fault) **
  in thread 0x7f203d749740
  ceph version 0.34 (commit:2f039eeeb745622b866d80feda7afa055e15f6d6)
  1: rbd() [0x457062]
  2: (()+0xfc60) [0x7f203ccf6c60]
  3: (librbd::snap_set(librbd::ImageCtx*, char const*)+0x10) 
[0x7f203d32ecd0]
  4: (main()+0x59f) [0x4518ff]
  5: (__libc_start_main()+0xff) [0x7f203b6cdeff]
  6: rbd() [0x44d569]
Segmentation fault

I use the ceph ubuntu build from your site.

Best Regards,
  martin



Sage Weil schrieb:
> There is a patch for a btrfs bug in the clone ioctl reservation that 
> hasn't made it upstream yet.  See
> 
> 	http://marc.info/?l=linux-btrfs&m=131291225105499&w=2
> 
> That should sort you out!
> 
> sage
> 
> 
> On Fri, 16 Sep 2011, Martin Mailand wrote:
> 
>> Hi,
>> should rbd snap work? I created a snapshot and then I want to list it.
>> rbd snap create --snap=2011091601 lenny1
>> rbd snap ls lenny1
>>
>> But the ls command does not come back and I get a Kernel bug on 2 OSD.
>> It is reproducible.
>>
>>
>> [ 7658.115729] ------------[ cut here ]------------
>> [ 7658.115779] kernel BUG at fs/btrfs/delayed-inode.c:1693!
>> [ 7658.115812] invalid opcode: 0000 [#1] SMP
>> [ 7658.115846] CPU 1
>> [ 7658.115861] Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit
>> psmouse k8temp sp5100_tco edac_core edac_mce_amd serio_raw shpchp i2c_piix4 lp
>> parport ahci pata_atiixp libahci btrfs e1000e zlib_deflate libcrc32c
>> [ 7658.116080]
>> [ 7658.116095] Pid: 1418, comm: cosd Tainted: G        W   3.1.0-rc6 #1
>> MICRO-STAR INTERNATIONAL CO., LTD MS-96B3/MS-96B3
>> [ 7658.116167] RIP: 0010:[<ffffffffa007ffd0>]  [<ffffffffa007ffd0>]
>> btrfs_delayed_update_inode+0x2a0/0x2b0 [btrfs]
>> [ 7658.116278] RSP: 0018:ffff8801160efbc8  EFLAGS: 00010286
>> [ 7658.116311] RAX: 00000000ffffffe4 RBX: ffff8800777c0120 RCX:
>> 0000000000018000
>> [ 7658.116351] RDX: 000000000000f7e5 RSI: 0000000000018000 RDI:
>> ffff880116b10160
>> [ 7658.116389] RBP: ffff8801160efc08 R08: ffffe8ffffc81a40 R09:
>> ffff8800886826a0
>> [ 7658.116428] R10: 0000000000000000 R11: 0000000000000000 R12:
>> ffff880001e4af50
>> [ 7658.116467] R13: ffff8800777c0168 R14: ffff880117122ea0 R15:
>> ffff880115113000
>> [ 7658.116507] FS:  00007f80e30eb700(0000) GS:ffff88011fc80000(0000)
>> knlGS:0000000000000000
>> [ 7658.116550] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> [ 7658.116583] CR2: ffffffffff600400 CR3: 0000000116015000 CR4:
>> 00000000000006e0
>> [ 7658.116623] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
>> 0000000000000000
>> [ 7658.116662] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
>> 0000000000000400
>> [ 7658.116700] Process cosd (pid: 1418, threadinfo ffff8801160ee000, task
>> ffff880116aeade0)
>> [ 7658.116744] Stack:
>> [ 7658.116759]  0000000000000282 0000000000018000 ffff8801160efc18
>> ffff880001e4af50
>> [ 7658.116817]  ffff880117122ea0 ffff8800391b01e0 ffff8801171113f0
>> 0000000000000000
>> [ 7658.116875]  ffff8801160efc58 ffffffffa003f353 ffff8801160efc38
>> ffffffffa00677f8
>> [ 7658.116933] Call Trace:
>> [ 7658.116978]  [<ffffffffa003f353>] btrfs_update_inode+0x53/0x160 [btrfs]
>> [ 7658.117039]  [<ffffffffa00677f8>] ? btrfs_tree_unlock+0x78/0xb0 [btrfs]
>> [ 7658.117099]  [<ffffffffa0063184>] btrfs_ioctl_clone+0x9b4/0xd20 [btrfs]
>> [ 7658.117164]  [<ffffffffa00666f6>] btrfs_ioctl+0x306/0xe20 [btrfs]
>> [ 7658.117204]  [<ffffffff81175f32>] ? do_filp_open+0x42/0xa0
>> [ 7658.117240]  [<ffffffff81178048>] do_vfs_ioctl+0x98/0x540
>> [ 7658.117277]  [<ffffffff81156f40>] ? kmem_cache_free+0x20/0x100
>> [ 7658.117313]  [<ffffffff81178581>] sys_ioctl+0x91/0xa0
>> [ 7658.117347]  [<ffffffff815f02c2>] system_call_fastpath+0x16/0x1b
>> [ 7658.117381] Code: 00 03 00 00 8d 0c 49 48 89 ca 48 89 4d c8 e8 f8 7d fa ff
>> 85 c0 48 8b 4d c8 75 10 48 89 4b 08 e9 cc fd ff ff 0f 1f 80 00 00 00 00 <0f>
>> 0b 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 53
>> [ 7658.117814] RIP  [<ffffffffa007ffd0>]
>> btrfs_delayed_update_inode+0x2a0/0x2b0 [btrfs]
>> [ 7658.117883]  RSP <ffff8801160efbc8>
>> [ 7658.122364] ---[ end trace c8a580615cad6cbe ]---
>>
>> Best Regards,
>>  Martin
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" 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:[~2011-09-16 21:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 14:45 rbd snap Martin Mailand
2011-09-16 16:30 ` Sage Weil
2011-09-16 21:32   ` Martin Mailand [this message]
2011-09-16 22:23     ` Josh Durgin
2011-09-16 22:36       ` Martin Mailand
2011-09-17 16:09       ` Martin Mailand
2011-09-23 18:08         ` Martin Mailand
2011-09-23 18:21           ` Sage Weil
2011-09-23 18:48             ` Martin Mailand
2011-09-23 18:52               ` Sage Weil
2011-09-23 18:25           ` Josh Durgin

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=4E73C064.7020104@tuxadero.com \
    --to=martin@tuxadero.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    /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