public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hendrik Friedel" <hendrik@friedels.name>
To: "Rowland penny" <rpenny@samba.org>,
	sambalist <samba@lists.samba.org>,
	"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
	"Qu Wenruo" <quwenruo.btrfs@gmx.com>
Subject: Re[2]: [Samba] Fw: Btrfs Samba and Quotas
Date: Tue, 21 May 2019 20:00:55 +0000	[thread overview]
Message-ID: <em093fdc1c-abb5-4cc9-b346-ea270deca7c1@ryzen> (raw)
In-Reply-To: <c3c6eb4b-2af1-57d2-44ec-0596a2ac9c78@samba.org>

Hello,

 >> In my impression: Yes. Also, this problem seems to affect also zfs 
and
 >
 > I'm mostly interested in the claim that ZFS is affected.
 > I haven't followed this thread carefully, but what exactly is the problem we're
 > talking about, and how do we know it impacts ZFS?
 > [Something more than a single one-liner in that bug report?]

Indeed, I only find that one line. I can try to find out.

 > Is the extent of the issue that quotas won't work, while enforced from Samba
 > against a ZFS volume?
 >
 > Can someone perhaps enlighten me? :)

The explaination is:

 > That's because the concept of a btrfs "subvolume" completely
 > breaks the POSIX idioms that smbd depends on.

And wouldn't that also be applicable to zfs?

>  At least I hope you can understand why some bug reports seem to take forever to get fixed, it is all down to priorities, the highest  priority ones get fixed first,

Yes, I understand that.

 > What I was trying to say was (and failing, it would seem), this is a 
two way street
 > and if OMV cannot/will not help you, then it is hard to fix,

What is OMV specific here? Isn't the problem fully included already in linux (=kernel) and samba?

 > especially now that Jeremy has pointed out that it cannot be fixed as is. Now this
 > doesn't mean it can never be fixed, throw enough money and man hours at it
 > and a workaround can probably be found

Here, I could imagine that linking with linux-btrfs would be worthwhile.

 > but this would undoubtedly entail OMV getting involved

Why? OMV merely writes the smb.conf...

Greetings,
Hendrik


  parent reply	other threads:[~2019-05-21 20:01 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
2019-05-20 18:50             ` Re[2]: " 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 [this message]
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=em093fdc1c-abb5-4cc9-b346-ea270deca7c1@ryzen \
    --to=hendrik@friedels.name \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --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