linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lin <mlin@kernel.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [bcachefs] Mounting the same device multiple times now works
Date: Wed, 12 Aug 2015 00:36:02 -0700	[thread overview]
Message-ID: <1439364962.5775.4.camel@hasee> (raw)
In-Reply-To: <20150812013853.GA2192@kmo-pixel>

On Tue, 2015-08-11 at 17:38 -0800, Kent Overstreet wrote:
> On Tue, Aug 11, 2015 at 10:59:42AM -0700, Ming Lin wrote:
> > On Tue, 2015-08-11 at 00:34 -0800, Kent Overstreet wrote:
> > > Like in other filesystems, you can now do
> > > 
> > > mount /dev/sda1 /foo
> > > mount /dev/sda1 /bar
> > > 
> > > What this really means is that if the udev hook has registered the bcache device
> > > via the old style sysfs interface for caching, you'll still be able to mount the
> > > device like normal.
> > 
> > Thanks!
> > 
> > BTW, could you share the bcachefs long term development plans and short
> > term high priority tasks?
> 
> Right now, my main priority is stabilizing it and making it usable - fixing all
> the things that people are going to trip over when they try it out. I want to
> get it somewhat more polished before I announce on linux-fsdevel.
> 
> The big thing I'm working on at the moment is debugging atomic renames, I had to
> back that code out at the last minute.
> 
> > I'd like to pick something to work on. Probably the debugfs tool you
> > mentioned or other things?
> 
> One thing that would actually be really helpful is more benchmarking vs.
> ext4/xfs - identifying areas where there's still more performance work to do.
> 
> The debugfs tool is definitely important but that's a longer term thing. If
> you're feeling productive like that feel free to keep going with it.
> 
> Really though right now the main thing we need is more testing and debugging.

I have run xfstests. Here is the results for generic tests.
http://minggr.net/pub/bcachefs/xfstests.log

One thing is fallocate not supported yet. Is it known?

root@bee:~# mount |grep bcache
/dev/sda on /mnt/test type bcache (rw,relatime)

root@bee:~# fallocate -l 4096 /mnt/test/hello.c
fallocate: /mnt/test/hello.c: fallocate failed: Operation not supported

  reply	other threads:[~2015-08-12  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  8:34 [bcachefs] Mounting the same device multiple times now works Kent Overstreet
2015-08-11 17:59 ` Ming Lin
2015-08-12  1:38   ` Kent Overstreet
2015-08-12  7:36     ` Ming Lin [this message]
2015-08-13  4:57       ` Ming Lin
2015-08-13  5:03       ` 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=1439364962.5775.4.camel@hasee \
    --to=mlin@kernel.org \
    --cc=kent.overstreet@gmail.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;
as well as URLs for NNTP newsgroup(s).