Stale File Handle Error With Mounted Drives (fstab) #5417

Fabi1LH · 2025-08-27T18:14:35Z

Fabi1LH
Aug 27, 2025

Checklist

This is a bug report, not a question.
I have searched on the issue tracker for my bug.
I am running the latest FileBrowser version or have an issue updating.

Version

2.42.5

Description

Hello,

I have two hard drives that can mount a folder with Docker, but sometimes I can't use FileBrowser because I get the message "Ouch! Something went wrong."

I have to restart Docker to use FileBrowser for everything to work again.
I mounted two disks with CIF, and these two drives are accessible with no access issues.

My fstab :

//192.168.1.10/ssd /media/shield cifs x-systemd.automount,x-systemd.device-timeout=13,_netdev,rw,users,credentials=/home/xxx/.smb,iocharset=utf8,uid=1000,gid=1000,sec=ntlmv2,file_mode=0777,dir_mode=0777,vers=3.0 0 0


//freebox-server.local/FreePartage /media/freebox cifs x-systemd.automount,x-systemd.device-timeout=3,_netdev,rw,users,credentials=/home/xxx/.smbcredentials,iocharset=utf8,uid=1000,gid=1000,sec=ntlmv2,file_mode=0777,dir_mode=0777,vers=3.0 0 0

Log error docker Filebrowser :

2025/08/24 09:25:57 Listening on [::]:80
2025/08/24 15:32:38 /api/renew: 401 192.168.1.174 <nil>
2025/08/24 15:32:38 /api/renew: 401 192.168.1.174 <nil>
2025/08/24 22:48:42 /api/renew: 401 192.168.1.174 <nil>
2025/08/24 22:48:42 /api/renew: 401 192.168.1.174 <nil>
2025/08/24 22:48:45 /api/renew: 401 192.168.1.174 <nil>
2025/08/25 05:37:23 /api/renew: 401 192.168.1.174 <nil>
2025/08/25 05:37:23 /api/renew: 401 192.168.1.174 <nil>
2025/08/25 16:39:54 /api/renew: 401 192.168.27.67 <nil>
2025/08/25 16:39:54 /api/renew: 401 192.168.27.67 <nil>
2025/08/26 20:17:03 /api/renew: 401 192.168.1.174 <nil>
2025/08/26 20:17:03 /api/renew: 401 192.168.1.174 <nil>
2025/08/26 20:17:06 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/26 20:17:53 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/26 20:17:55 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/26 20:18:08 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/27 05:39:55 /api/renew: 401 192.168.1.174 <nil>
2025/08/27 05:39:55 /api/renew: 401 192.168.1.174 <nil>
2025/08/27 05:39:59 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/27 17:56:10 /api/renew: 401 192.168.1.97 <nil>
2025/08/27 17:56:10 /api/renew: 401 192.168.1.97 <nil>
2025/08/27 17:56:13 /: 500 192.168.1.97 lstat /srv/Shield: stale file handle

Compose :

services:
  filebrowser:
    container_name: filebrowser
    restart: always
    image: filebrowser/filebrowser
    ports:
      - 9090:80
    environment:
      - PGID=1000
      - PUID=1000
    volumes:
      - /opt/stacks/filebrowser/data:/database
      - /opt/stacks/filebrowser/config/:/config
      - /media/freebox/DDL:/srv/Free
      - /media/shield/DDL:/srv/Shield
    command: --disable-exec=false

Thanks for your help.

What did you expect to happen?

Control my config or debug it for use filebrowser without restart it

What actually happened?

Message :

Logs :

2025/08/24 09:25:57 Listening on [::]:80
2025/08/24 15:32:38 /api/renew: 401 192.168.1.174 <nil>
2025/08/24 15:32:38 /api/renew: 401 192.168.1.174 <nil>
2025/08/24 22:48:42 /api/renew: 401 192.168.1.174 <nil>
2025/08/24 22:48:42 /api/renew: 401 192.168.1.174 <nil>
2025/08/24 22:48:45 /api/renew: 401 192.168.1.174 <nil>
2025/08/25 05:37:23 /api/renew: 401 192.168.1.174 <nil>
2025/08/25 05:37:23 /api/renew: 401 192.168.1.174 <nil>
2025/08/25 16:39:54 /api/renew: 401 192.168.27.67 <nil>
2025/08/25 16:39:54 /api/renew: 401 192.168.27.67 <nil>
2025/08/26 20:17:03 /api/renew: 401 192.168.1.174 <nil>
2025/08/26 20:17:03 /api/renew: 401 192.168.1.174 <nil>
2025/08/26 20:17:06 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/26 20:17:53 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/26 20:17:55 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/26 20:18:08 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/27 05:39:55 /api/renew: 401 192.168.1.174 <nil>
2025/08/27 05:39:55 /api/renew: 401 192.168.1.174 <nil>
2025/08/27 05:39:59 /: 500 192.168.1.174 lstat /srv/Shield: stale file handle
2025/08/27 17:56:10 /api/renew: 401 192.168.1.97 <nil>
2025/08/27 17:56:10 /api/renew: 401 192.168.1.97 <nil>
2025/08/27 17:56:13 /: 500 192.168.1.97 lstat /srv/Shield: stale file handle

Reproduction Steps

Not easy because the problem is random

Files

No response

hacdias · 2025-08-28T05:54:12Z

hacdias
Aug 28, 2025
Maintainer

I don't think this is related to File Browser, but some other issue mounting this network devices into Docker.

I will move this to a discussion since this is not an issue with File Browser, and I can't really help you further. Maybe someone else can.

I'd advise you to search for "stale file handle fstab docker".

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Stale File Handle Error With Mounted Drives (fstab) #5417

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Stale File Handle Error With Mounted Drives (fstab) #5417

Uh oh!

Uh oh!

Fabi1LH Aug 27, 2025

Checklist

Version

Description

What did you expect to happen?

What actually happened?

Reproduction Steps

Files

Replies: 1 comment

Uh oh!

Uh oh!

hacdias Aug 28, 2025 Maintainer

Fabi1LH
Aug 27, 2025

hacdias
Aug 28, 2025
Maintainer