CEPH filesystem development
 help / color / mirror / Atom feed
From: Fyodor Ustinov <ufm@ufm.su>
To: ceph-devel@vger.kernel.org
Subject: Kernel 3.0.0 + ext4 + ceph == ...
Date: Sat, 30 Jul 2011 12:38:09 +0300	[thread overview]
Message-ID: <4E33D101.1050504@ufm.su> (raw)

fail. Epic fail.

Absolutely reproducible.

I have ceph cluster with this configuration:

8 physical servers
14 osd servers.
Each osd server have personal fs.
48T total size of ceph cluster.
17T used.

Now, step by step:

1. Stop ceph server osd0
/etc/init.d/ceph stop

2. Make fresh fs for osd
umount /osd.0
mkfs.ext4 /dev/sdc1
tune2fs -o journal_data_writeback /dev/sdc1
mount -a
# string from /etc/fstab:
# /dev/sdc1 /osd.0          ext4    
user_xattr,rw,noexec,nodev,noatime,nodiratime,data=writeback,barrier=0        
0       2
ceph mon getmap -o /tmp/monmap
cosd --mkfs -i 0 --monmap /tmp/monmap

3. Start ceph server osd0
/etc/init.d/ceph start

Now, make a big cup of coffee and begin to wait.

After completion of rebalancing do:
/etc/init.d/ceph stop
umount /osd.0
fsck.ext4 -fy /dev/sdc1

and see many-many messages like:

Inode 238551053, i_blocks is 24, should be 32.  Fix? yes

Inode 238551054, i_blocks is 40, should be 32.  Fix? yes

Inode 238551066, i_blocks is 24, should be 32.  Fix? yes

Inode 238944257, i_blocks is 8, should be 16.  Fix? yes

Inode 239206414, i_blocks is 8, should be 16.  Fix? yes

Inode 239206416, i_blocks is 40, should be 32.  Fix? yes

Inode 239206431, i_blocks is 8, should be 16.  Fix? yes

Inode 239206441, i_blocks is 24, should be 32.  Fix? yes

Voila.

P.S. No any message in syslog. No any message in console.

WBR,
     Fyodor.


             reply	other threads:[~2011-07-30  9:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30  9:38 Fyodor Ustinov [this message]
2011-07-30 14:37 ` Kernel 3.0.0 + ext4 + ceph == Christian Brunner
2011-07-30 14:53   ` Fwd: " Christian Brunner
2011-11-15 15:46     ` Eric Sandeen
2011-07-30 15:34 ` Theodore Tso
2011-07-30 16:36   ` Fyodor Ustinov
2011-07-30 16:50     ` Ted Ts'o
2011-07-30 17:16       ` Fyodor Ustinov
2011-07-30 17:21       ` Sage Weil
2011-07-30 17:27         ` Fyodor Ustinov
2011-07-30 17:54         ` Fyodor Ustinov
2011-07-30 22:19         ` Ted Ts'o
2011-07-31  4:54           ` Sage Weil
2011-07-31 11:33             ` Fyodor Ustinov
2011-07-31 17:04               ` Sage Weil
2011-07-31 17:32                 ` Fyodor Ustinov
2011-07-31 20:16                 ` Fyodor Ustinov
2011-07-31 20:42                   ` Sage Weil
2011-08-01 10:53                     ` Theodore Tso
2011-08-01 16:20                       ` Sage Weil
2011-08-03 14:16                         ` Christian Brunner
2011-08-03 15:41                           ` Yehuda Sadeh Weinraub
2011-08-08 20:07                             ` Christian Brunner
2011-08-18  9:19                               ` Christian Brunner
2011-07-30 18:33   ` Christian Brunner

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=4E33D101.1050504@ufm.su \
    --to=ufm@ufm.su \
    --cc=ceph-devel@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