From: Nix <nix@esperi.org.uk>
To: FERNANDO FREDIANI <fernando.frediani@upx.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Add Bcache to an existing Filesystem
Date: Tue, 27 Jun 2017 14:45:08 +0100 [thread overview]
Message-ID: <878tkdy26z.fsf@esperi.org.uk> (raw)
In-Reply-To: <bbf7d8b5-5d0d-c4ae-7af4-9799b6a5ed25@upx.com> (FERNANDO FREDIANI's message of "Tue, 27 Jun 2017 10:37:47 -0300")
On 27 Jun 2017, FERNANDO FREDIANI said:
> Hello Nix
>
> What exactlly you mean by "exploded" ? Has it stopped working at all
> and has that stopped the systems running on the top of it or it just
> stopped the caching device and the backing continued to work well.
It stopped the caching device and refused to mount the rootfs atop it
until I explicitly dissociated it. I haven't reactivated it since (I
might do so once I've rejigged my shutdown process to fully unmount
everything via the early root filesystem, but this system is a crucial
machine in active use and it takes ages to get around to such things).
See <https://marc.info/?l=linux-bcache&m=149687387202378>.
> Regarding my scenario, just to clarify I have 4 x /dev/sdX forming a
> /dev/md124 in RAID 10. This /dev/md124 is the backing device of my
> bcache which in turn has /dev/nvme0n1 as the caching device making
> /dev/bcache0. I guess this would be the most coming scenario right ?
I think so: s/RAID 10/journalled RAID 6/ and you have my setup (well,
part of it: the start of the disk is in uncached RAID-0, and the end is
in unjournalled, uncached RAID-6 with a write bitmap, but the middle
portion is a RAID-6 with bcache -- albeit, presently, in 'none' mode.)
--
NULL && (void)
next prev parent reply other threads:[~2017-06-27 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 16:12 Add Bcache to an existing Filesystem FERNANDO FREDIANI
2017-06-26 17:58 ` Eric Wheeler
2017-06-26 18:06 ` FERNANDO FREDIANI
2017-06-26 18:05 ` Henk Slager
2017-06-26 18:14 ` FERNANDO FREDIANI
2017-06-26 19:19 ` Henk Slager
2017-06-27 10:46 ` Jens-U. Mozdzen
2017-06-27 13:23 ` Nix
2017-06-27 13:37 ` FERNANDO FREDIANI
2017-06-27 13:45 ` Nix [this message]
2017-06-27 14:41 ` Henk Slager
2017-06-27 23:43 ` Eric Wheeler
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=878tkdy26z.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=fernando.frediani@upx.com \
--cc=linux-bcache@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox