| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs spanning over ssd and hdd |
| From: | Matthias Neuer <mneuer@xxxxxx> |
| Date: | Tue, 13 May 2014 09:07:40 +0200 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <5370D8AA.2010003@xxxxxxxxxxx> |
| References: | <5370C592.6080402@xxxxxx> <5370D8AA.2010003@xxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0 |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS crash?, Austin Schuh |
|---|---|
| Next by Date: | [PATCH 4/9] xfs: correct error sign on COLLAPSE_RANGE errors, Dave Chinner |
| Previous by Thread: | Re: xfs spanning over ssd and hdd, Eric Sandeen |
| Next by Thread: | [xfstests PATCH 0/4] locktest: cleanup, bugfixes, and add new locking test, Jeff Layton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |