All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fyodor Ustinov <ufm@ufm.su>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: rbd
Date: Sat, 14 May 2011 15:36:02 +0300	[thread overview]
Message-ID: <4DCE7732.1060006@ufm.su> (raw)
In-Reply-To: <Pine.LNX.4.64.1105131208450.12286@cobra.newdream.net>

On 05/13/2011 10:11 PM, Sage Weil wrote:
> Fyodor,
>
> On Fri, 13 May 2011, Sage Weil wrote:
>> On Thu, 12 May 2011, Sage Weil wrote:
>>> On Thu, 12 May 2011, Sage Weil wrote:
>>>> equation.  I'm running iozone on ext3 now and not having any problems.
>>> I take it back.. I just reproduced a similar error on ext2:
>>>
>>>                                                              random  random
>>> bkwd   record   stride
>>>                KB  reclen   write rewrite    read    reread    read   write
>>> read  rewrite     read   fwrite frewrite   fread  freread
>>>           4194304      64    3570    3040    12640    13725
>>>
>>> Error in file: Found ?aaaaaaaaaaaaaaaa? Expecting ?3838383838383838? addr
>>> 40a00000
>>> Error in file: Position 2813329408
>>> Record # 42928 Record size 64 kb
>>> where 40a00000 loop 0
>>>
>>> I opened a tracker issue http://tracker.newdream.net/issues/1086
>> Just an update: we've identified the problem but a fix is still in the
>> works.  The bio coming down is spanning an object boundary, and we're
>> having trouble getting the block layer to either not do that or to handle
>> the bio splitting properly.
> Can you try the req_coll branch of
> git://ceph.newdream.net/git/ceph-client.git and see if that fixes things
> for you?  There's a memory leak fix and a fix for the split bio completion
> stuff.  If it checks out I want to send this to Linus quickly so it'll be
> included in 2.6.39 (which is imminent).
root@stb1:~# uname -a
Linux stb1 2.6.39-rc7-ufm-ceph #1 SMP Sat May 14 13:50:12 EEST 2011 
x86_64 x86_64 x86_64 GNU/Linux
root@stb1:~# modprobe rbd
root@stb1:~# echo "77.120.112.193 name=admin rbd tmt" > /sys/bus/rbd/add
root@stb1:~# mkfs.ocfs2 -M local -T vmstore --fs-features=local,sparse 
/dev/rbd0
mkfs.ocfs2 1.6.3
Overwriting existing ocfs2 partition.
Proceed (y/N): y
Filesystem Type of vmstore
Label:
Features: local sparse backup-super unwritten inline-data 
strict-journal-super xattr refcount
Block size: 4096 (12 bits)
Cluster size: 1048576 (20 bits)
Volume size: 1073741824000 (1024000 clusters) (262144000 blocks)
Cluster groups: 32 (tail covers 24064 clusters, rest cover 32256 clusters)
Extent allocator size: 3221225472 (768 groups)
Journal size: 134217728
Node slots: 1
Creating bitmaps: done
Initializing superblock: done
Writing system files: done
Writing superblock: done
Writing backup superblock: 5 block(s)
Formatting Journals: done
Growing extent allocator: done
Formatting slot map: done
Formatting quota files: done
Writing lost+found: done
mkfs.ocfs2 successful

root@stb1:~# mount /dev/rbd0 /mnt
root@stb1:~# cd /mnt
root@stb1:/mnt# iozone -a -n4g -g20g
         Iozone: Performance Test of File I/O
                 Version $Revision: 3.373 $
                 Compiled for 64 bit mode.
                 Build: linux-AMD64

         Contributors:William Norcott, Don Capps, Isom Crawford, Kirby 
Collins
                      Al Slater, Scott Rhine, Mike Wisner, Ken Goss
                      Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR,
                      Randy Dunlap, Mark Montague, Dan Million, Gavin 
Brebner,
                      Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, 
Dave Boone,
                      Erik Habbinga, Kris Strecker, Walter Wong, Joshua 
Root,
                      Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren 
Sawyer.

         Run began: Sat May 14 14:39:03 2011

         Auto Mode
         Using minimum file size of 4194304 kilobytes.
         Using maximum file size of 20971520 kilobytes.
         Command line used: iozone -a -n4g -g20g
         Output is in Kbytes/sec
         Time Resolution = 0.000001 seconds.
         Processor cache size set to 1024 Kbytes.
         Processor cache line size set to 32 bytes.
         File stride size set to 17 * record size.
                                                             random  
random    bkwd   record   stride
               KB  reclen   write rewrite    read    reread    read   
write    read  rewrite     read   fwrite frewrite   fread  freread
          4194304      64  134566  135254    53718    52836   14839   78946

And now it is 20 minutes in this state.In the logs clean. Incoming 
network traffic- 3Mbytes/s
But, we newer see this test before, likely an extremely low speed test 
"bkwd read" this is another problem.

As you can see - trouble with "Error in file" solved. :)

WBR,
     Fyodor.


  reply	other threads:[~2011-05-14 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 10:53 rbd Fyodor Ustinov
2011-05-12 16:08 ` rbd Sage Weil
2011-05-12 17:01   ` rbd Sage Weil
2011-05-13 15:51     ` rbd Sage Weil
2011-05-13 19:11       ` rbd Sage Weil
2011-05-14 12:36         ` Fyodor Ustinov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-03 18:49 rbd Yehuda Sadeh Weinraub

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=4DCE7732.1060006@ufm.su \
    --to=ufm@ufm.su \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.