search for: bcache

Dan Williams wrote: > The consensus from LSF was that bcache need not invent a new interface > when md and dm can both do the job. As mentioned in patch 7 this series > aims to be a minimal conversion. Other refactoring items like > deprecating register_lock for mddev->reconfig_mutex are deferred. > > This supports assembly of an already...

I''ve recently setup a system (Kernel 3.12.5-1-ARCH) which is layered as follows: /dev/sdb3 - cache0 (80 GB Intel SSD) /dev/sdc1 - backing device (2 TB WD HDD) sdb3+sdc1 => /dev/bcache0 On /dev/bcache0, there''s a btrfs filesystem with 2 subvolumes, mounted as / and /home. What''s been bothering me are the following entries in my kernel log: [13811.845540] incomplete page write in btrfs with offset 1536 and length 2560 [13870.326639] incomplete page write in btr...

...drivers/block/nbd.c | 12 +++--- drivers/block/nvme-core.c | 33 ++++++++------- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 ++++++++--------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 ++++++----- drivers/md/bcache/io.c | 69 ++++++++++++++------------------ drivers/md/bcache/request.c | 28 ++++++------- drivers/md/raid5.c | 12 +++--- drivers/s390/...

...drivers/block/nbd.c | 12 +++--- drivers/block/nvme-core.c | 33 ++++++++------- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 ++++++++--------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 ++++++----- drivers/md/bcache/io.c | 69 ++++++++++++++------------------ drivers/md/bcache/request.c | 28 ++++++------- drivers/md/raid5.c | 12 +++--- drivers/s390/...

...drivers/block/nbd.c | 12 +++--- drivers/block/nvme-core.c | 33 ++++++++------- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 ++++++++--------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 ++++++----- drivers/md/bcache/io.c | 69 ++++++++++++++------------------ drivers/md/bcache/request.c | 28 ++++++------- drivers/md/raid5.c | 12 +++--- drivers/s390/...

...ock/nbd.c | 12 ++--- drivers/block/nvme-core.c | 33 ++++++++------ drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 +++++++-------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 +++++----- drivers/md/bcache/io.c | 69 ++++++++++++----------------- drivers/md/bcache/request.c | 28 ++++++------ drivers/md/raid5.c | 12 ++--- driv...

...ock/nbd.c | 12 ++--- drivers/block/nvme-core.c | 33 ++++++++------ drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 +++++++-------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 +++++----- drivers/md/bcache/io.c | 69 ++++++++++++----------------- drivers/md/bcache/request.c | 28 ++++++------ drivers/md/raid5.c | 12 ++--- driv...

...ock/nbd.c | 12 ++--- drivers/block/nvme-core.c | 33 ++++++++------ drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 +++++++-------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 +++++----- drivers/md/bcache/io.c | 69 ++++++++++++----------------- drivers/md/bcache/request.c | 28 ++++++------ drivers/md/raid5.c | 12 ++--- driv...

...drivers/block/nvme-core.c | 33 ++++++++------- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 ++++++++--------- drivers/block/rsxx/dma.c | 11 ++--- drivers/block/xen-blkfront.c | 14 +++---- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 ++++++----- drivers/md/bcache/io.c | 69 ++++++++++++++------------------ drivers/md/bcache/request.c | 28 ++++++------- drivers/md/md.c | 16 ++++---- drivers/md/...

...drivers/block/nvme-core.c | 33 ++++++++------- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 ++++++++--------- drivers/block/rsxx/dma.c | 11 ++--- drivers/block/xen-blkfront.c | 14 +++---- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 ++++++----- drivers/md/bcache/io.c | 69 ++++++++++++++------------------ drivers/md/bcache/request.c | 28 ++++++------- drivers/md/md.c | 16 ++++---- drivers/md/...

...drivers/block/nvme-core.c | 33 ++++++++------- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 36 ++++++++--------- drivers/block/rsxx/dma.c | 11 ++--- drivers/block/xen-blkfront.c | 14 +++---- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 23 ++++++----- drivers/md/bcache/io.c | 69 ++++++++++++++------------------ drivers/md/bcache/request.c | 28 ++++++------- drivers/md/md.c | 16 ++++---- drivers/md/...

...e a specific use scenario > you are interested in, then please let us know. I was thinking of running some operations on the root filesystem by kexec-rebooting into an appliance to get exclusive access. I would like to do something like that for my blocks tool (which does conversions to LVM and bcache). https://github.com/g2p/blocks#readme

Hi Everyone, We are thinking of venturing into the world of hosting Windows DomUs on our Xen infrastructure. As Windows generally requires a lot more IOPS than Linux does, we are trying to do everything we can to improve performance. While using SSDs would solve the IOPS problem, SSDs suffer from limited write cycles. So, we have the idea of using Flashcache from Facebook to use a single SSD as

...ck/nvme-core.c | 33 ++++++++------ drivers/block/ps3disk.c | 10 ++--- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 38 ++++++++-------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 19 ++++---- drivers/md/bcache/io.c | 69 ++++++++++++----------------- drivers/md/bcache/request.c | 26 +++++------ drivers/md/raid5.c | 12 ++--- drivers...

...ck/nvme-core.c | 33 ++++++++------ drivers/block/ps3disk.c | 10 ++--- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 38 ++++++++-------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 19 ++++---- drivers/md/bcache/io.c | 69 ++++++++++++----------------- drivers/md/bcache/request.c | 26 +++++------ drivers/md/raid5.c | 12 ++--- drivers...

...ck/nvme-core.c | 33 ++++++++------ drivers/block/ps3disk.c | 10 ++--- drivers/block/ps3vram.c | 10 ++--- drivers/block/rbd.c | 38 ++++++++-------- drivers/block/rsxx/dma.c | 11 ++--- drivers/md/bcache/btree.c | 4 +- drivers/md/bcache/debug.c | 19 ++++---- drivers/md/bcache/io.c | 69 ++++++++++++----------------- drivers/md/bcache/request.c | 26 +++++------ drivers/md/raid5.c | 12 ++--- drivers...

What happened to the hot data tracking feature in btrfs? There are a lot of old patches from aug 2010, but it looks like the feature has been completly removed from the current version of btrfs. Is this feature still on the roadmap?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''ve been unable to find anything definitive about what happens if I use RAID0 to join an SSD and HDD together with respect to performance (latency, throughput). The future is obvious (hot data tracking, using most appropriate device for the data, data migration). In my specific case I have a 250GB SSD and a 500GB HDD, and about 250GB of

...k/xen-blkfront.c | 1 + drivers/block/xsysace.c | 1 + drivers/block/z2ram.c | 1 + drivers/cdrom/gdrom.c | 1 + drivers/ide/ide-cd.c | 1 + drivers/ide/ide-gd.c | 1 + drivers/lightnvm/gennvm.c | 1 + drivers/md/bcache/super.c | 2 ++ drivers/md/dm.c | 1 + drivers/md/md.c | 1 + drivers/memstick/core/ms_block.c | 1 + drivers/memstick/core/mspro_block.c | 1 + drivers/mmc/card/block.c | 1 + drivers/mtd/mtd_blkdevs.c | 1 + drivers/mtd/ubi...

Hello, I want to test bachefs file system on CentOS 7. ~$ cat /etc/system-release CentOS Linux release 7.6.1810 (Core) I'm following the bcachefs howto: https://bcachefs.org/Howto/. Having a problem trying to complete make && make install of the bcache-tools. After going through all the dependencies and insuring they are installed on Cent 7, I get the following output on make && make install: Package blkid was not found...