From: Dave Chinner <david@fromorbit.com>
To: Tom Christensen <tom.christensen@storagecraft.com>
Cc: "swakefie@redhat.com" <swakefie@redhat.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: your mail
Date: Sun, 14 Jun 2015 08:39:21 +1000 [thread overview]
Message-ID: <20150613223921.GC20262@dastard> (raw)
In-Reply-To: <71962FC942A61D42A3DECDFB7CC94F61193F6F07@STC-EXCH.stc.local>
On Sat, Jun 13, 2015 at 01:02:51AM +0000, Tom Christensen wrote:
> We've run into a bit of an issue with xfs running Ceph. The following bug details what we are seeing:
> https://bugs.launchpad.net/ubuntu/+source/xfs/+bug/1464308
>
> Basically the Ceph OSD process gets hung in dstate due to the traceback in the bug.
>
> Here is additional info gathered:
>
> xfs bmap output for a random directory
> https://gist.github.com/dmmatson/e864252c7ff346df954a
>
> attr -l of the file dchinner indicated from the xfs bmap output
> (attr -l)
> (6:11:41 PM) dmatson: Attribute "cephos.spill_out" has a 2 byte value for rbd\udata.66039648e29a80.0000000000000d35__head_23EA10B8__5
> (6:11:45 PM) dmatson: Attribute "ceph.snapset@3" has a 263 byte value for rbd\udata.66039648e29a80.0000000000000d35__head_23EA10B8__5
> (6:11:49 PM) dmatson: Attribute "ceph.snapset@2" has a 1131 byte value for rbd\udata.66039648e29a80.0000000000000d35__head_23EA10B8__5
> (6:11:53 PM) dmatson: Attribute "ceph.snapset@1" has a 2048 byte value for rbd\udata.66039648e29a80.0000000000000d35__head_23EA10B8__5
> (6:11:56 PM) dmatson: Attribute "ceph._" has a 259 byte value for rbd\udata.66039648e29a80.0000000000000d35__head_23EA10B8__5
> (6:12:00 PM) dmatson: Attribute "ceph.snapset" has a 2048 byte value for rbd\udata.66039648e29a80.0000000000000d35__head_23EA10B8__5
>
> xfs_bmap -vp of same file
>
> rbd\udata.66039648e29a80.0000000000000d35__head_23EA10B8__5:
> (6:13:21 PM) dmatson: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL FLAGS
> (6:13:25 PM) dmatson: 0: [0..8191]: 2944471376..2944479567 16 (24445776..24453967) 8192 00000
And the attribute fork was:
rbd\udata.66039648e29a80.0000000000000d35__head_23EA10B8__5:
EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL FLAGS
0: [0..7]: 1461176488..1461176495 8 (1163688..1163695) 8 00000
1: [8..31]: 1461176504..1461176527 8 (1163704..1163727) 24 00000
I just created a filesystem and attribute list identical to the
above, and came up with a attribute fork that looks like:
/mnt/scratch/udata.66039648e29a80.0000000000000d35__head_23EA10B8__5:
EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL FLAGS
0: [0..7]: 120..127 0 (120..127) 8 00000
1: [8..15]: 112..119 0 (112..119) 8 00000
2: [16..23]: 104..111 0 (104..111) 8 00000
IOWs, there's an extra block in the attribute fork that is causing
problems than there needs to be. That tends to imply attribute
overwrites might be contributing here (the 3-phase overwrite
algorithm increases the space usage) so I'm going to need to try a
few different things to see if I can get an attribute fork into the
same shape....
> LVM configuration: None
>
> HGST 3TB
>
> meta-data=/dev/mapper/63e3300b-6b7b-41a0-bdf2-b64ec3c20c51 isize=2048 agcount=32, agsize=22812700 blks
agcount=32 will actually be slowing your disks down. The default of
4AGs is usually best for a single spindle as it has sufficient
allocation cncurrency but results in much fewer seeks than a higher
AG count....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-13 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 1:02 Tom Christensen
2015-06-13 22:39 ` Dave Chinner [this message]
2015-06-14 23:27 ` your mail Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2023-05-25 12:01 Murphy Zhou
2023-05-25 12:04 ` your mail Christoph Hellwig
2023-05-25 12:45 ` Murphy Zhou
[not found] <D3E576A1A7C7134694A0DDA7C2CA4B884C3985@hyd-mail2.bbnet.ad>
2006-10-23 9:02 ` Chris Wedgwood
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=20150613223921.GC20262@dastard \
--to=david@fromorbit.com \
--cc=swakefie@redhat.com \
--cc=tom.christensen@storagecraft.com \
--cc=xfs@oss.sgi.com \
/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