From: Eric Sandeen <sandeen@redhat.com>
To: chb@muc.de
Cc: linux-ext4@vger.kernel.org, ceph-devel@vger.kernel.org
Subject: Re: Fwd: Kernel 3.0.0 + ext4 + ceph == ...
Date: Tue, 15 Nov 2011 09:46:44 -0600 [thread overview]
Message-ID: <4EC28964.7060200@redhat.com> (raw)
In-Reply-To: <CAO47_--yVuodQhMXknd2cEPpd-QkowVPV_D0+u4LM302r6SKFw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 7/30/11 9:53 AM, Christian Brunner wrote:
> Fyodor and I are struggling to get a fully stable ceph cluster up and running.
>
> When we run an Ceph-Objectstore (OSD) ontop of an ext4 filesystem, we
> get fsck errors, when we check the filesystem (see below).
BTW, this should be fixed now as of my commit 6d6a435190bdf2e04c9465cde5bdc3ac68cf11a4
ext4: fix race in xattr block allocation path
I think it made its way to a couple older -stable kernels, too.
- -Eric
> Fyodor is running 3.0.
> I am running a RHEL6.1 Kernel (2.6.32-131.6.1.el6.x86_64).
>
> Any help or hints on how to trace the bug would be appreciated.
>
> Thanks,
> Christian
>
> 2011/7/30 Fyodor Ustinov <ufm@ufm.su>:
>> 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.
>>
>> --
>> 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
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJOwoljAAoJECCuFpLhPd7gjxIQAJ7B+f7EYxBZ+48gUrncmB5r
Izkkv2ACza+27g/CUi9ku9j1o3pjZwLNhzo3Fj0gwweB3WaY9T+JMXnfInSFegeR
GCT/8XQqGWFVoRQKKc4wUBKGgW5f+3HTgYLqUY0Z38MqMHpIMXYswXdOSB1Wc4MC
p+jEjHmTWftklpIjv+Vm61AejpoUO93SFE5gUuBeKSZxwjifV1uTUXtaZCQXUG5N
EFz+sS7YvGrttAldK+lbiq7sa7IKINnB5lbDs5ChSZoytSF9hPIRgDOTLrkAZ+k8
YovLWbu2gwGMcZEhu3ZLJ7NdtZbn45A/fh/grNU8nezTo0cTHBTYZCLqtjsUDuMr
mwUIDNUEAv6LIz0OyeJMftDX4TzxjQyEQOgYg5wyCKCjE2Nyktyap2T5sAFKamJJ
pgTUt0JSpXgDnDBL7Y3M6RbY8DQsDHIir3A7aOwdINGKweNiJXBYC3LWYHIXY0bd
yoKXT6e/Bentlj+Peugg51bw91JtlqxJT4qJfk6HMF00uxrfWHlvzht7Lu61YxrW
LBQgNyQ+Gu1drHIHyIFu95UePhzEGQcLXB3YUe7BKFGe4Vde8Jcrwn1RSFmILU6H
o9jPncZVanQYy9URQqnrcHzqpRfViuVeyhuAUh3lPt4Q7jIrr+2Ug6xWxIkBrtTt
/iKT0p8+aR3HhakrGqp4
=VbZG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-15 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E33D101.1050504@ufm.su>
[not found] ` <CAO47_-_EC4s1HF1pOGNzPRitYGyigOd1hfgz1qDPy6dqwGMMQA@mail.gmail.com>
2011-07-30 14:53 ` Fwd: Kernel 3.0.0 + ext4 + ceph == Christian Brunner
2011-11-15 15:46 ` Eric Sandeen [this message]
[not found] ` <9BF9E529-C532-4A94-8362-93C2D1B778DB@mit.edu>
[not found] ` <4E3432FC.9030204@ufm.su>
[not found] ` <20110730165001.GI7361@thunk.org>
[not found] ` <Pine.LNX.4.64.1107301016120.23447@cobra.newdream.net>
[not found] ` <20110730221900.GK7361@thunk.org>
[not found] ` <Pine.LNX.4.64.1107302149430.23447@cobra.newdream.net>
[not found] ` <4E353D9E.5080802@ufm.su>
[not found] ` <Pine.LNX.4.64.1107310951550.2348@cobra.newdream.net>
[not found] ` <4E35B833.6070304@ufm.su>
[not found] ` <Pine.LNX.4.64.1107311339530.23447@cobra.newdream.net>
[not found] ` <80E3795B-C981-492F-9312-DC91D57E4017@mit.edu>
[not found] ` <Pine.LNX.4.64.1108010918580.6290@cobra.newdream.net>
[not found] ` <CAO47_-9DmxqfBsBF2K_8ScX_4d-HPz01QeQ-2FFwZS-nCDEOsw@mail.gmail.com>
[not found] ` <CAC-hyiHzmn25ryJkNUdzQvk7c7chwVDfmwDeo8X2+4zTbDuFGQ@mail.gmail.com>
2011-08-08 20:07 ` Christian Brunner
2011-08-18 9:19 ` 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=4EC28964.7060200@redhat.com \
--to=sandeen@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@muc.de \
--cc=linux-ext4@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).