From: Juan Antonio Martinez <jantonio-oytJ0Z/vEwre5aOfsHch1g@public.gmane.org>
To: nbd-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache on NBD block devices
Date: Wed, 26 Feb 2014 09:31:50 +0100 [thread overview]
Message-ID: <1393403510.17548.15.camel@jonsy> (raw)
In-Reply-To: <CAECXXi68Q=5aXQ_NnubkMNsGxPPefCiz77pnYthNU-Jk88qQeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
El mar, 25-02-2014 a las 11:37 -0500, Paul Clements escribió:
> On Tue, Feb 25, 2014 at 9:40 AM, Juan Antonio Martinez
> <jantonio@dit.upm.es> wrote:
> > Hi all
> > (This is my first post on this list. I'm still a novice on bcache and
> > proper nettiquete on this list, so apologize for my mistakes)
> > Scenario: several NBD LTSP Fat Clients on (a bit) obsolete hardware
> > kernel 3.11.0-15 on Ubuntu 13.10
> > /dev/sda1 as local cache device
> > /dev/nbd1 as remote NBD backing bcache device
> > - I've created and registered /dev/sda1 as cache device without problems
> > - To create nbd file to be exported I've typed following sequence:
> > # create an empty file
> > root# dd if=/dev/zero of=bcache_test.img bs=1M count=64
> > # use it as loop block device
> > root# losetup /dev/loop0
> > # make it a backing bcache device
> > root# make-bcache -B /dev/loop0
> have you tried doing this step from the client machine instead, i.e.:
> make-bache -B /dev/nbd1
> after the nbd connection is up? does that work?
Just tested: works fine.... but only in the LTSP client where I did the
changes, and had to tell nbd-server to export imagefile in read-write
mode
Remember that my configuration consist in several (>250!) LTSP-NBD
clients sharing _the_same_ mounted squashfs image file. I cannot for
obious reasons make the image file to be shared read-write on every
clients at the same time... and seems that bcache needs write access to
the backing block device to work
¿Is this correct? If so, bcache is not for me :-( ¿Any alternatives?
Perhaps I coult try to create bcache'd image file, and then modify NBD
server permissions to export in copy-on-write-mode... but this would
work if bcache only writes in bcache superblock ( my image files are
typically 8Gb size each) as this will create one cow file per client on
server
Cheers
Juan Antonio
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Nbd-general mailing list
Nbd-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nbd-general
next prev parent reply other threads:[~2014-02-26 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 16:37 [Nbd] bcache on NBD block devices Paul Clements
[not found] ` <CAECXXi68Q=5aXQ_NnubkMNsGxPPefCiz77pnYthNU-Jk88qQeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-26 8:31 ` Juan Antonio Martinez [this message]
2014-02-26 10:18 ` Juan Antonio Martinez
-- strict thread matches above, loose matches on Subject: below --
2014-02-25 14:40 Juan Antonio Martinez
2014-02-25 16:33 ` Paul Clements
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=1393403510.17548.15.camel@jonsy \
--to=jantonio-oytj0z/vewre5aofshch1g@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nbd-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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