RE: bcache not working on large files?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> From: matthew patton
> Sent: Tuesday, October 22, 2013 3:27 PM
>
> 'busted' in this case means errors on write. If the device disappears and
is no
> longer readable, then sure any un-committed blocks are gone and your
> filesystem/file is broken.

In other words, if you care about your data, don't use a nonredundant cache
device in writeback mode 8-/. I'm tentatively planning to use an md mirror
of two 256G SSD's to front end a raid10 of 4 2TB HD's, I'm still in the
investigate stage but hopefully will get to prototyping soon.
 
> If you're not running kernel 3.11.5 (or 3.11.4 with *all* the bcache
fixes)
> you're wasting your time.

Is there an intention to port all of these fixes back to an LTS 3.10 kernel,
or if you're going to run in production you're pretty much committed to the
latest stable?

Thanks.


--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM Kernel]     [Linux Filesystem Development]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux