From: Eric Sandeen <sandeen@sandeen.net>
To: Raz <raziebe@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: XFS over SSD
Date: Mon, 08 Dec 2008 09:50:55 -0600 [thread overview]
Message-ID: <493D425F.2010904@sandeen.net> (raw)
In-Reply-To: <5d96567b0812080711x34bb93d6vd8e4f88d9b190e9@mail.gmail.com>
Raz wrote:
> On Mon, Dec 8, 2008 at 4:46 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>> Raz wrote:
>>> I am thinking of using XFS over a SSD disk.
>>> 1. Can I separate xfs meta data ( not just the logging) from the SSD ?
>>> can I put the meta on a different disk ?
>> Are you talking about just the log (see the mkfs man page for external
>> logs, as Justin suggested) or all metadata? For the latter, using the
>> realtime subvolume does accomplish this (data on one volume, metadata on
>> the other) but that's not used very often.
>>
>> -Eric
>>
> I am referring to all the meta data. 128K of erase block for some block map
> update is a big penalty. I do not like much rt volumes. I tried that and it is
> cumbersome. UBIFS cannot handle 80GB Flash disks ( well, they say it is up to
> 16GB in MTD web site) . I am about to start benchmarking the SSD with XFS
> ( versus raw access ) and see how performance degrades, in read and writes.
> If there was a way to set XFS meta data ( superblocks, allocation groups...
> on a different device) it would have been nice, since we plan to use the SSD
> as a fast IO device and data persistence is not the main thing here.
>
> we use XFS on all our SATA based servers, we tweak it ( extents and
> raid awareness).
> XFS proved to be the fastest file system for appliances that use
> Multimedia files
> and big IOs ( 1MB).
>
I have yet to play with xfs on ssd, but I would imagine that setting up
the fs geometry to match the ssd preferred IO sizes and/or erase block
sizes might at least help.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-08 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 12:42 XFS over SSD Raz
2008-12-08 13:31 ` Justin Piszcz
2008-12-08 14:46 ` Eric Sandeen
2008-12-08 15:11 ` Raz
2008-12-08 15:50 ` Eric Sandeen [this message]
2008-12-15 5:36 ` Dave Chinner
2008-12-09 7:53 ` Emmanuel Florac
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=493D425F.2010904@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=raziebe@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.