influxdata / influxdata/influxdata-docker

upgrade fail with error: unlinkat /var/lib/influxdb2: device or resource busy

Open
#525 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
364
Forks
255
Avg merge
3h 18m
Merged PRs (30d)
7

Description

Hi all,
When we upgrading influxDB from 1.7 to 2.0 by using InfluxDB v2 Helm chart with old data mounted, statefulsets deployed successful but the container in status of unready with Pod log below, could someone can help on this ? thank you in advance.

`Error: couldn't delete existing file at "/var/lib/influxdb2": unlinkat /var/lib/influxdb2: device or resource busy
See 'influxd -h' for help
2021-09-07T09:24:25. warn cleaning bolt and engine files to prevent conflicts on retry {"system": "docker", "bolt_path": "/var/lib/influxdb2/influxd.bolt", "engine_path": "/var/lib/influxdb2"}
rm: can't remove '/var/lib/influxdb2': Resource busy`

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the InfluxDB v2 Helm chart upgrade and the pod log showing unlinkat failure on the mounted /var/lib/influxdb2 path. Compare the old data mount with the StatefulSet and container configuration; done means identifying a confirmed upgrade or mount configuration that lets the container become ready.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, helm, kubernetes
Domain
database, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.