From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> To: David Rhodes Clymer <david-LEGOU7lN1jbY0TyS/+Ba5Q@public.gmane.org> Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: Resizing bcache backing store Date: Wed, 11 Apr 2012 19:55:54 -0400 [thread overview] Message-ID: <CAH+dOxJv-ajvLfbUSo8dqG0a8_grNBhfxJ1EbmSrYZz0YXJM2w@mail.gmail.com> (raw) In-Reply-To: <CAB7K1hH_o7koST7RYTbw9ya0GMEvmpb=TYAt1MqEVDhtBdRd1Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> For the backing device, I think things will just work - you'll just have to close and reopen the backing device in order for bcache to notice the new size. Bcache's superblock doesn't remember the size, it just goes off of what the size of the backing device is when it's registered. There's currently no way to make bcache notice the backing device has grown to do it at runtime, though that ought to be fairly simple too. On Wed, Apr 11, 2012 at 6:47 PM, David Rhodes Clymer <david-LEGOU7lN1jbY0TyS/+Ba5Q@public.gmane.org> wrote: > In the case where the bcache backing store is resizeable (eg. a > logical volume), is it possible to resize the backing store without > breaking bcache? Let's say, for example, that I would > unmount/unregister /dev/bcacheX, resize the backing store, > reregister/remount the cache. > > I imagine a better approach would be to layer LVM on the cache device > itself. However, in this particular case, I set up the bcache before I > had learned how to get LVM to use a bcache device as a PV. > > -davidc > -- > To unsubscribe from this list: send the line "unsubscribe linux-bcache" in > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-11 23:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-11 22:47 David Rhodes Clymer [not found] ` <CAB7K1hH_o7koST7RYTbw9ya0GMEvmpb=TYAt1MqEVDhtBdRd1Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2012-04-11 23:55 ` Kent Overstreet [this message] 2012-11-01 19:06 ` James Sefton [not found] ` <loom.20121101T195722-160-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org> 2012-11-02 15:20 ` Kent Overstreet
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=CAH+dOxJv-ajvLfbUSo8dqG0a8_grNBhfxJ1EbmSrYZz0YXJM2w@mail.gmail.com \ --firstname.lastname@example.org \ --cc=david-LEGOU7lN1jbY0TyS/+Ba5Q@public.gmane.org \ --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --subject='Re: Resizing bcache backing store' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).