From: Jeremy Allison <jra@samba.org>
To: Hendrik Friedel <hendrik@friedels.name>
Cc: Rowland penny <rpenny@samba.org>,
sambalist <samba@lists.samba.org>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [Samba] Fw: Btrfs Samba and Quotas
Date: Mon, 20 May 2019 11:03:58 -0700 [thread overview]
Message-ID: <20190520180358.GB257371@jra4> (raw)
In-Reply-To: <em1a6d365f-4482-4553-81d9-dfa58a31f5d4@ryzen>
On Mon, May 20, 2019 at 05:54:13PM +0000, Hendrik Friedel via samba wrote:
> Hello,
>
> > Is btrfs becoming more common ?
> In my impression: Yes. Also, this problem seems to affect also zfs and thus
> all (?) file systems that support checksums and scrubbing in linux;
> consequently all filesystems that are the choice of users who need this for
> ensuring data consistency.
> > You posted this:
> >
> > I am using Openmediavault (debian based NAS distribution), which is not actively supporting btrfs
> >
> > It is this that I was referring to.
> Ah, yes.
> OMV intended to move to btrfs as the only choice with the next version. In
> order to pave the way, I intended to be an early adopter. The problem I
> report here, that there is good reason to.
>
> > > > it just a pain in the a.. Never use it together with quotas or CTDB it
> > > > will crash after short time. I only take xfs and have no problem at all.
> > > > I don't know wy, but it's not good idea to user brtfs with samba.
> > >
> > > Well, as long as this is not being reported and being improved, it will remain that way...
> > >
> > Possibly, but it works great with ext4
> Glad to hear that.
> > I suggest you sit down with a copy of 'man smb.conf' and remove all the default
> My intent is not to solve *my* problem, but to make developers aware of this
> issue and help getting this issue fixed.
>
> I feel a bit helpless though, as I perceive a lack of interest...
> I mean... This Bug is now celebrating its 5th aniversary.
> https://bugzilla.samba.org/show_bug.cgi?id=10541
That's because the concept of a btrfs "subvolume" completely
breaks the POSIX idioms that smbd depends on.
We absolutely identify a file by a dev/ino pair, and
expect the dev to remain consistent under an exported
share path.
If you sub-mount this also breaks smbd dfree/quotas, and
that's a lot more common.
This identity is baked into Samba in order to implement
leases/oplocks and it's not going to change.
If you want to do this (subvolumes/submounts) I think
you should get familiar with the:
dfree command:
set quota command:
set quota command:
scripts in smb.conf.
next prev parent reply other threads:[~2019-05-20 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <emee6c041c-adec-4106-b8f6-c4665299ea29@ryzen>
2019-05-18 9:22 ` [Samba] Fw: Btrfs Samba and Quotas Hendrik Friedel
2019-05-18 10:20 ` Qu Wenruo
[not found] ` <bd91e229-90cc-f30e-1709-d8c55818af1a@samba.org>
2019-05-18 13:19 ` Re[2]: " Hendrik Friedel
[not found] ` <5bbcabdc-ac46-7481-64a8-b515745d72b4@samba.org>
[not found] ` <em1a6d365f-4482-4553-81d9-dfa58a31f5d4@ryzen>
2019-05-20 18:03 ` Jeremy Allison [this message]
2019-05-20 18:50 ` Hendrik Friedel
[not found] ` <8954cf73-77a1-f313-6ea1-d9bdb142dced@samba.org>
2019-05-20 18:47 ` Hendrik Friedel
[not found] ` <c3c6eb4b-2af1-57d2-44ec-0596a2ac9c78@samba.org>
2019-05-21 20:00 ` Hendrik Friedel
2019-05-21 21:20 ` Chris Murphy
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=20190520180358.GB257371@jra4 \
--to=jra@samba.org \
--cc=hendrik@friedels.name \
--cc=linux-btrfs@vger.kernel.org \
--cc=rpenny@samba.org \
--cc=samba@lists.samba.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