Hello, all. I'm thinking of rolling out a BackupPC server, and -- based
on the strength of the recent Phoronix benchmarks
(http://benchmarkreviews.com/index.php?option=com_content&task=view&id=11156&Itemid=23)
-- had been strongly considering btrfs. But I do seem to recall that
there was some sor
On Tue, 2010-07-27 at 15:29 -0700, Tracy Reed wrote:
> On Tue, Jul 27, 2010 at 05:00:18PM -0500, bchoc...@gmail.com spake thusly:
> > The long-term goal of these patches, as discussed in the Motivation
> > section at the end of this message, is to enable Btrfs to perform
> > automagic relocation o
In response to your original questions, btrfs currently gives no control
over the allocation of data or metadata. I'm sure someone will implement
more control eventually.
On Wed, Jul 28, 2010 at 11:49:33PM +0800, wks1986 wrote:
> Another issue is the speed of fsck. There will always be times when
Hi,
You are right. The single SSD would become a single point of failure.
But if metadata should be mirrored in order to gain reliablilty,
synchronizing between multiple devices may hurt performance.
Mirroring between two SSDs should be reasonable, but synchronizing
metadata between an SSD and a
Hi,
I have a question to your requirement:
If the meta is stored on the SSD and not on other HDDs, I think the SSD is must
to be "online" whenever you mount any of the HDDs. And in other words, without
the SSD, other HDDs are meaningless. Is that acceptable?
regards,
wengang.
On 10-07-28 17:32,
On Wed, 28 Jul 2010 09:18:23 am Ben Chociej wrote:
> Yes, that's correct. It's likely not going to be a cache in the
> traditional sense, since the entire capacity of both HDD and SSD would
> be available.
To me that sounds like an HSM type arrangement, with most frequently used data
on the high
Hello
Recently I am learning about the Btrfs.
My requirement is to construct a cross-device btrfs volume consisting
of a single SSD and many (much larger) HDDs. The tricky part is that
I want the SSD to be dedicated to metadata since SSDs are much faster
(and more expensive) than HDDs and metada