public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Neuer <mneuer@web.de>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: xfs spanning over ssd and hdd
Date: Tue, 13 May 2014 09:07:40 +0200	[thread overview]
Message-ID: <5371C4BC.2010902@web.de> (raw)
In-Reply-To: <5370D8AA.2010003@sandeen.net>

Hi.

On 05/12/2014 04:20 PM, Eric Sandeen wrote:
> On 5/12/14, 7:58 AM, Matthias Neuer wrote:
>> Hi.
>>
>> I have a slow and big hdd and a fast but small ssd and want to test the following setup but don't know if it's possible.
>>
>> Use LVM to concatenate the ssd and the hdd linearly. Create a xfs filesystem on this device such that the sdd is filled first, i.e. data is written to the ssd as long as there is free space, otherwise the data is written to the hdd.
>>
>> I have applications which may benefit from this setup but I am not sure so I need to do some benchmarks.
>
> XFS doesn't fill from the front, so you can't configure things to fill the HDD first.
>
> Files in new directories rotor around the allocation groups on the filesystem, so all regions of the fs are filled more or less evenly.
>

Ok, thanks for the info. I fear that xfs is too intelligent because 
filling the device from front to rear seems to be a simple policy.
Maybe I should try FAT16 :)

Thanks
Matthias

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2014-05-13  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 12:58 xfs spanning over ssd and hdd Matthias Neuer
2014-05-12 14:13 ` Emmanuel Florac
2014-05-13  7:00   ` Matthias Neuer
2014-05-12 14:20 ` Eric Sandeen
2014-05-13  7:07   ` Matthias Neuer [this message]

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=5371C4BC.2010902@web.de \
    --to=mneuer@web.de \
    --cc=sandeen@sandeen.net \
    --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