Austin S. Hemmelgarn posted on Mon, 21 Dec 2015 08:36:02 -0500 as
excerpted:
> On 2015-12-16 21:09, Christoph Anton Mitterer wrote:
>> On Tue, 2015-12-15 at 11:00 -0500, Austin S. Hemmelgarn wrote:
>>> nodatacow only [avoids fragmentation] if the file is
>>> pre-allocated, if it isn't, then it
On 2015-12-22 04:12, Duncan wrote:
Austin S. Hemmelgarn posted on Mon, 21 Dec 2015 08:36:02 -0500 as
excerpted:
On 2015-12-16 21:09, Christoph Anton Mitterer wrote:
On Tue, 2015-12-15 at 11:00 -0500, Austin S. Hemmelgarn wrote:
nodatacow only [avoids fragmentation] if the file is
On 2015-12-16 21:09, Christoph Anton Mitterer wrote:
On Tue, 2015-12-15 at 11:00 -0500, Austin S. Hemmelgarn wrote:
Well sure, I think we'de done most of this and have dedicated
controllers, at least of a quality that funding allows us ;-)
But regardless how much one tunes, and how good the
On Tue, 2015-12-15 at 11:00 -0500, Austin S. Hemmelgarn wrote:
> > Well sure, I think we'de done most of this and have dedicated
> > controllers, at least of a quality that funding allows us ;-)
> > But regardless how much one tunes, and how good the hardware is. If
> > you'd then loose always a
Austin S. Hemmelgarn posted on Tue, 15 Dec 2015 11:00:40 -0500 as
excerpted:
> And in particular, the only
> journaling filesystem that I know of that even allows the option of
> journaling the file contents instead of just metadata is ext4.
IIRC, ext3 was the first to have it in Linux mainline,
Austin S. Hemmelgarn posted on Tue, 15 Dec 2015 11:00:40 -0500 as
excerpted:
> AFAIUI, checksums are stored per-instance for every block. This is
> important in a multi-device filesystem in case you lose a device, so
> that you still have a checksum for the block. There should be no
>
On 2015-12-14 22:15, Christoph Anton Mitterer wrote:
On Mon, 2015-12-14 at 09:16 -0500, Austin S. Hemmelgarn wrote:
When one starts to get a bit deeper into btrfs (from the admin/end-
user
side) one sooner or later stumbles across the recommendation/need
to
use nodatacow for certain types of
On Mon, 2015-12-14 at 17:42 +1100, Russell Coker wrote:
> My understanding of BTRFS is that the metadata referencing data
> blocks has the
> checksums for those blocks, then the blocks which link to that
> metadata (EG
> directory entries referencing file metadata) has checksums of those.
You
On Mon, 2015-12-14 at 09:16 -0500, Austin S. Hemmelgarn wrote:
> > When one starts to get a bit deeper into btrfs (from the admin/end-
> > user
> > side) one sooner or later stumbles across the recommendation/need
> > to
> > use nodatacow for certain types of data (DBs, VM images, etc.) and
> >
On 2015-12-13 23:59, Christoph Anton Mitterer wrote:
(consider that question being asked with that face on: http://goo.gl/LQaOuA)
Hey.
I've had some discussions on the list these days about not having
checksumming with nodatacow (mostly with Hugo and Duncan).
They both basically told me it
(consider that question being asked with that face on: http://goo.gl/LQaOuA)
Hey.
I've had some discussions on the list these days about not having
checksumming with nodatacow (mostly with Hugo and Duncan).
They both basically told me it wouldn't be straight possible with CoW,
and Duncan thinks
On Mon, 14 Dec 2015 03:59:18 PM Christoph Anton Mitterer wrote:
> I've had some discussions on the list these days about not having
> checksumming with nodatacow (mostly with Hugo and Duncan).
>
> They both basically told me it wouldn't be straight possible with CoW,
> and Duncan thinks it may
12 matches
Mail list logo
