From: Forza <forza@tnonline.net>
To: Ulli Horlacher <framstag@rus.uni-stuttgart.de>,
linux-btrfs@vger.kernel.org
Subject: Re: cannot use btrfs for nfs server
Date: Fri, 9 Jul 2021 09:23:14 +0200 (GMT+02:00) [thread overview]
Message-ID: <475ccf1.ca37f515.17a8a262a72@tnonline.net> (raw)
In-Reply-To: <20210709065320.GC8249@tik.uni-stuttgart.de>
Hello everyone,
---- From: Ulli Horlacher <framstag@rus.uni-stuttgart.de> -- Sent: 2021-07-09 - 08:53 ----
> On Fri 2021-07-09 (01:05), Graham Cobb wrote:
>> On 08/07/2021 23:17, Ulli Horlacher wrote:
>>
>> >
>> > I have waited some time and some Ubuntu updates, but the bug is still there:
>>
>> Yes: find and du get confused about seeing inode numbers reused in what
>> they think is a single filesystem.
>
> A lot of tools aren't working correctly any more, even ls:
>
> root@tsmsrvj:~# ls -R /nfs/localhost/fex | wc
> ls: /nfs/localhost/fex/spool: not listing already-listed directory
>
> In consequence many cronjobs and montoring tools will fail :-(
>
>
>> You can eliminate the problems by exporting and mounting single
>> subvolumes only
>
> This is not possible at our site, we use rotating snapshots created by a
> cronjob.
>
>
Have you tried using the fsid= export option in /etc/exports?
Example:
/media/nfs/ 192.168.0.*(fsid=20000001,rw,sync,no_subtree_check,no_root_squash)
We're using this with Btrfs subvols without issues. We use NFSv4 so I do not know how this works with NFSv3.
Example:
## On the Ubuntu NFS server:
# btrfs sub list -o .
ID 5384 gen 345641 top level 258 path volume/nfs_ssd/132bbc3e-aed1-15a5-f30d-9515e490e62c/subvol1
ID 5385 gen 345640 top level 258 path volume/nfs_ssd/132bbc3e-aed1-15a5-f30d-9515e490e62c/subvol2
## On the NFS client:
[09:20 srv01 132bbc3e-aed1-15a5-f30d-9515e490e62c]# ll
total 0
drwxr-xr-x 1 root root 6 Jul 9 09:17 subvol1
drwxr-xr-x 1 root root 0 Jul 9 09:17 subvol2
[09:20 srv01 132bbc3e-aed1-15a5-f30d-9515e490e62c]# touch subvol1/foo
[09:20 srv01 132bbc3e-aed1-15a5-f30d-9515e490e62c]# touch subvol2/bar
[09:20 srv01 132bbc3e-aed1-15a5-f30d-9515e490e62c]# touch foobar
[09:20 srv01 132bbc3e-aed1-15a5-f30d-9515e490e62c]# ll -R
.:
total 0
-rw-r--r-- 1 root root 0 Jul 9 09:20 foobar
drwxr-xr-x 1 root root 12 Jul 9 09:20 subvol1
drwxr-xr-x 1 root root 6 Jul 9 09:20 subvol2
./subvol1:
total 0
-rw-r--r-- 1 root root 0 Jul 9 09:17 bar
-rw-r--r-- 1 root root 0 Jul 9 09:20 foo
./subvol2:
total 0
-rw-r--r-- 1 root root 0 Jul 9 09:20 bar
next prev parent reply other threads:[~2021-07-09 7:23 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210613115313.BC59.409509F4@e16-tech.com>
2021-03-10 7:46 ` nfs subvolume access? Ulli Horlacher
2021-03-10 7:59 ` Hugo Mills
2021-03-10 8:09 ` Ulli Horlacher
2021-03-10 9:35 ` Graham Cobb
2021-03-10 15:55 ` Ulli Horlacher
2021-03-10 17:29 ` Forza
2021-03-10 17:46 ` Ulli Horlacher
2021-03-10 8:17 ` Ulli Horlacher
2021-03-11 7:46 ` Ulli Horlacher
2021-07-08 22:17 ` cannot use btrfs for nfs server Ulli Horlacher
2021-07-09 0:05 ` Graham Cobb
2021-07-09 4:05 ` NeilBrown
2021-07-09 6:53 ` Ulli Horlacher
2021-07-09 7:23 ` Forza [this message]
2021-07-09 7:24 ` Hugo Mills
2021-07-09 7:34 ` Ulli Horlacher
2021-07-09 16:30 ` Chris Murphy
2021-07-10 6:35 ` Ulli Horlacher
2021-07-11 11:41 ` Forza
2021-07-12 7:17 ` Ulli Horlacher
2021-07-09 16:35 ` Chris Murphy
2021-07-10 6:56 ` Ulli Horlacher
2021-07-10 22:17 ` Chris Murphy
2021-07-12 7:25 ` Ulli Horlacher
2021-07-12 13:06 ` Graham Cobb
2021-07-12 16:16 ` Ulli Horlacher
2021-07-12 22:56 ` g.btrfs
2021-07-13 7:37 ` Ulli Horlacher
2021-07-19 12:06 ` Forza
2021-07-19 13:07 ` Forza
2021-07-19 13:35 ` Forza
2021-07-27 11:27 ` Ulli Horlacher
2021-07-09 16:06 ` Lord Vader
2021-07-10 7:03 ` Ulli Horlacher
[not found] ` <162632387205.13764.6196748476850020429@noble.neil.brown.name>
2021-07-15 14:09 ` [PATCH/RFC] NFSD: handle BTRFS subvolumes better Josef Bacik
2021-07-15 16:45 ` Christoph Hellwig
2021-07-15 17:11 ` Josef Bacik
2021-07-15 17:24 ` Christoph Hellwig
2021-07-15 18:01 ` Josef Bacik
2021-07-15 22:37 ` NeilBrown
2021-07-19 15:40 ` Josef Bacik
2021-07-19 20:00 ` J. Bruce Fields
2021-07-19 20:44 ` Josef Bacik
2021-07-19 23:53 ` NeilBrown
2021-07-19 15:49 ` J. Bruce Fields
2021-07-20 0:02 ` NeilBrown
2021-07-19 9:16 ` Christoph Hellwig
2021-07-19 23:54 ` NeilBrown
2021-07-20 6:23 ` Christoph Hellwig
2021-07-20 7:17 ` NeilBrown
2021-07-20 8:00 ` Christoph Hellwig
2021-07-20 23:11 ` NeilBrown
2021-07-20 22:10 ` J. Bruce Fields
2021-07-15 23:02 ` NeilBrown
2021-07-15 15:45 ` J. Bruce Fields
2021-07-15 23:08 ` NeilBrown
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=475ccf1.ca37f515.17a8a262a72@tnonline.net \
--to=forza@tnonline.net \
--cc=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@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