From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C6AC9C04AAC for ; Mon, 20 May 2019 18:04:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A45A320863 for ; Mon, 20 May 2019 18:04:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=samba.org header.i=@samba.org header.b="Z1UjkERz" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727216AbfETSED (ORCPT ); Mon, 20 May 2019 14:04:03 -0400 Received: from hr2.samba.org ([144.76.82.148]:24362 "EHLO hr2.samba.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726447AbfETSED (ORCPT ); Mon, 20 May 2019 14:04:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=samba.org; s=42627210; h=Message-ID:Cc:To:From:Date; bh=/+fAkpfIAuPfdoPWlu9IQvtkJ+y8CPWAVo4eXdGbj0g=; b=Z1UjkERzCUzdPmOBfLDD7IXcHh qTqL1dG9CNNPwA8bImn6yZgALYnoS+Aev1+rHth8EQFmNrlNZO3oIgdDLP+pyHEpCs+IPPBlTNRML A0w9KaWQuIyNZWn82xj83gSF8LT+XdPED04NMLUGFNvy34F2JcA5vvmGnT8x1+pDTzEY=; Received: from [127.0.0.2] (localhost [127.0.0.1]) by hr2.samba.org with esmtpsa (TLS1.3:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim) id 1hSmdl-0002dC-3m; Mon, 20 May 2019 18:04:01 +0000 Date: Mon, 20 May 2019 11:03:58 -0700 From: Jeremy Allison To: Hendrik Friedel Cc: Rowland penny , sambalist , Btrfs BTRFS Subject: Re: [Samba] Fw: Btrfs Samba and Quotas Message-ID: <20190520180358.GB257371@jra4> Reply-To: Jeremy Allison References: <5bbcabdc-ac46-7481-64a8-b515745d72b4@samba.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org 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.