"File system loop detected" with btrfs over NFS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
btrfs-progs (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
nfs-utils (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
tsmsrvi and tsmsrvj both run Ubuntu 20.04 with all updates applied.
When I try to access a btrfs filesystem via nfs, I get the error:
root@tsmsrvi:~# mount tsmsrvj:/data/fex /nfs/tsmsrvj/fex
root@tsmsrvi:~# find /nfs/tsmsrvj/fex
/nfs/tsmsrvj/fex
find: File system loop detected; '/nfs/tsmsrvj/
root@tsmsrvi:~# du -s /nfs/tsmsrvj/fex
du: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
/nfs/
0 /nfs/tsmsrvj/fex
root@tsmsrvi:~# ls -l /nfs/tsmsrvj/fex/
total 0
drwxr-xr-x 1 fex fex 261964 Mar 7 14:53 spool
On tsmsrvj I have in /etc/exports:
/data/fex localhost(
/data/fex tsmsrvi(
/data/fex is a btrfs filesystem with subvolumes:
root@tsmsrvj:~# mount | grep /data
/dev/sdb1 on /data type btrfs (rw,relatime,
root@tsmsrvj:~# btrfs subvolume list /data
ID 257 gen 35 top level 5 path fex
ID 270 gen 36 top level 257 path fex/spool
ID 271 gen 21 top level 270 path fex/spool/
ID 272 gen 23 top level 270 path fex/spool/
ID 273 gen 25 top level 270 path fex/spool/
ID 274 gen 27 top level 270 path fex/spool/
Accessing btrfs directly without nfs has no problems:
root@tsmsrvj:~# find /data/fex | wc -l
489887
root@tsmsrvj:~# lsb_release -rd
Description: Ubuntu 20.04.2 LTS
Release: 20.04
root@tsmsrvj:# uname -a
Linux tsmsrvj 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
root@tsmsrvj:# btrfs version
btrfs-progs v5.4.1
root@tsmsrvj:# dpkg -l | grep nfs-
ii nfs-common 1:1.3.4-
ii nfs-kernel-server 1:1.3.4-
affects: | ubuntu → nfs-utils (Ubuntu) |
tags: | added: focal |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1918599/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]