| To: | Stefan Ring <stefanrin@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS fragmentation on file append |
| From: | Keyur Govande <keyurgovande@xxxxxxxxx> |
| Date: | Thu, 24 Apr 2014 17:49:14 -0400 |
| Cc: | linux-fsdevel@xxxxxxxxxxxxxxx, Linux fs XFS <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MqBOoX53J+UlHGfir0l7MJjNfKwGkizv2+4cWUX27Js=; b=xNj5TxusCwovahPHTHGYHh1zdoBPOCjfqg1CcOXocnLp/LX/qk1fCMnI2s3CTLG0t3 GkiaXqeGmiYawpmQVOyQl4Xg9H9heoNDDF8VGAUzR+63CVawJmbazwRHTqslyNVvVThM xaOREFdIPJ9Idd8SWsA+PvNuun94YNn8yjqSTXzPAXo9pGd0+68/0M1vyIbWU5TRottR yDQC2dsHsGdDGCTAQ7ORbcgf1SXPvEEU6Tvb0U90Qw26uCYIMUu4S4XUuOcfTL3KxEco jcDlqa7fJGlZv1JWFiusKE5LAJEpob8FuUFiYOFW7EGxvIpjwf2rLHPhf8lol2UT1tgu Kftg== |
| In-reply-to: | <CAAxjCEzdYRug8CUjhmB7AHJCNAJs4ERRTLXGAHXqi1sw-vOriw@xxxxxxxxxxxxxx> |
| References: | <CAJhmKHmwvCBx=arJ6m2ZhuQVq=Jj-XbBGvEPjTPY5a1QtWRTCQ@xxxxxxxxxxxxxx> <20140408015012.GB22917@dastard> <CAJhmKHnap0vu8m4AXBxJr9L0RKoquFrm3NjKQdDBJwpRTYmfpw@xxxxxxxxxxxxxx> <20140408053117.GJ27017@dastard> <CAJhmKHk5fWVaDTEfL_oESULspavk83eBEsyw7=qEp8bC7f2S2g@xxxxxxxxxxxxxx> <CAAxjCEzdYRug8CUjhmB7AHJCNAJs4ERRTLXGAHXqi1sw-vOriw@xxxxxxxxxxxxxx> |
On Thu, Apr 24, 2014 at 2:54 AM, Stefan Ring <stefanrin@xxxxxxxxx> wrote: > I've become interested in this topic, as I'm also running MySQL with > O_DIRECT and innodb_file_per_table. Out of curiosity, I immediately > ran xfs_bmap on a moderately sized table space (34GB). It listed > around 30000 fragments, on average one for every MB. > > I want to report what happened then: A flurry of activity started on > both disks (root/swap lives on one of them, the data volume containing > the MySQL files on another) and lasted for about two minutes. > Afterwards, all memory previously allocated to the file cache has > become free, and also everything XFS seems to keep buffered internally > (I think it's called SReclaimable) was released. Swap usage increased > only slightly. dmesg was silent during that time. > > This is a 2.6.32-358.2.1.el6.x86_64 kernel with xfsprogs 3.1.1 (CentOS > 6.4). The machine has 64GB of RAM (2 NUMA nodes) and 24 (virtual) > cores. Is this known behavior of xfs_bmap? Interesting...it looks like your box flushed all of the OS buffer cache. I am unable to reproduce this behavior on my test box with the 3.10.37 kernel. I also tried with 2.6.32-358.18.1.el6.x86_64 and didn't hit the issue, but obviously our access patterns differ wildly. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC] libxfs: adding attribute fork frees xfs_inode ptr, Mark Tinguely |
|---|---|
| Next by Date: | How to find the inodes in XFS, Felipe Monteiro de Carvalho |
| Previous by Thread: | Re: XFS fragmentation on file append, Stefan Ring |
| Next by Thread: | Please upgrade to Webmail 5.2 (Important), Mail Admin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |